Differences between revisions 6 and 7
Revision 6 as of 2009-03-18 04:14:38
Size: 2726
Editor: solpc2
Comment:
Revision 7 as of 2009-08-05 04:01:13
Size: 3642
Editor: equinox
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:

=== Becoming a Remote DRMS ===

For some institutions, setting up a system or local network running NetDRMS may be beneficial. This is an involved commitment, and requires the establishment and configuration of a local Postgres database server, and the bulk data storage system. These should be one-time tasks for someone with administrative privileges on the systems on which these services will run. Once the services have been established, any user should be able to set up their own NetDRMS development environment. Becoming a netDRMS would be beneficial in cases where automated, regular data delivery for specific data series is needed, or if the institution plans to become a local download hub for others interested in JSOC data.

Learn more about netDRMS here: [http://jsoc.stanford.edu/netdrms/] [[BR]]
If you are already a netDRMS and need to get data clusters, please read: SetupForSlonyData

User Access to JSOC Managed Data

Places to add descriptions

Web access to data

See the [:LookData: lookdata wiki page] for usage help for the tool at http://jsoc.stanford.edu/ajax/lookdata.html. Lookdata can be used to browse names of DataSeries, lists of available keyword metadata for each series, to examine metadata for specifiable RecordSets, and to export user selected RecordSets in several forms. lookdata.html was written as a test platform for the javascript Ajax style access tools described at AjaxJsocConnect in this Wiki. We expect other web entry points will be developed in the future. Meanwhile, all JSOC data is accessible via http://jsoc.stanford.edu/ajax/lookdata.html.

Local access to data

JSOC data and metadata can be examined at the "shell" level via several general purpose commands. show_series and show_info are the most common and provide access to data series lists and all the information contained in a particular series respectively. There are "man" pages for both of these and other commands in the Doxygen generated documents at http://jsoc.stanford.edu/doxygen_html/ In the future there will be examples here.

Becoming a Remote DRMS

For some institutions, setting up a system or local network running NetDRMS may be beneficial. This is an involved commitment, and requires the establishment and configuration of a local Postgres database server, and the bulk data storage system. These should be one-time tasks for someone with administrative privileges on the systems on which these services will run. Once the services have been established, any user should be able to set up their own NetDRMS development environment. Becoming a netDRMS would be beneficial in cases where automated, regular data delivery for specific data series is needed, or if the institution plans to become a local download hub for others interested in JSOC data.

Learn more about netDRMS here: [http://jsoc.stanford.edu/netdrms/] BR If you are already a netDRMS and need to get data clusters, please read: SetupForSlonyData

Using JSOC data in c programs

The primary way to access JSOC data is via c programs using the DRMS API. There are a growing list of examples in the CVS software tree. Applications are found in the JSOC/proj subtree. In the future we will have a link to tutorials and examples here.

Using JSOC data in FORTRAN programs

We do support a FORTRAN API for DRMS. It provides most basic functions. One can write FORTRAN main programs and use this API or (and probably preferable) write a c main program using the c DRMS API and call FORTRAN computational functions. Examples of both methods will be linked here in the future.

Using JSOC data in IDL programs

Note, we no longer plan a full API for IDL. But there are several approaches to use for access to JSOC data from within IDL programs. At present there is no way to insert data into DRMS/SUMS from IDL other than shell level commands. There is now no plan to run IDL programs in the JSOC "Pipeline" processing. There can never be interactive IDL jobs in the main JSOC computing cluster since the only way to run programs is via the batch queue system.

  • If you need to use IDL SolarSoft Sam Freeland is developing tools for access JSOC data. This interface, still in development, is described at http://www.lmsal.com/solarsoft/jsoc/ssw_jsoc_routines.html.

  • If you need to run in IDL on a local (to Stanford or Lockheed) machine, see Jesper Schou who has developed techniques for accessing the data via shell commands.

JsocWiki: JsocDataAccess (last edited 2016-10-20 07:12:50 by MonicaBobra)