Differences between revisions 3 and 58 (spanning 55 versions)
⇤ ← Revision 3 as of 2007-10-25 09:28:31 →
Size: 8964
Editor: solpc2
Comment:
← Revision 58 as of 2010-10-07 04:16:09 → ⇥
Size: 12947
Editor: arta-mbp
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Welcome to Trac for JSOC software development = == Welcome to the Wiki for JSOC software development ==
Line 7: Line 7:
 * JSOC 3.2 released -- Sep 15, 2006 See [http://jsoc.stanford.edu/release-3.2.notes release notes]
 * JSOC 3.1 released -- Aug 24, 2006 See [http://jsoc.stanford.edu/release-3.1.notes release notes]
 * JSOC 3.0 released -- Aug 14, 2006. See [http://jsoc.stanford.edu/release-3.0.notes release notes]
 * JSOC 2.3 released -- Aug 10, 2006. See [http://jsoc.stanford.edu/release-2.3.notes release notes]
 * JSOC 2.2 released -- May 30, 2006. See [http://jsoc.stanford.edu/release-2.2.notes release notes]
 * JSOC 2.1 released -- May 24, 2006. See [http://jsoc.stanford.edu/release-2.1.notes release notes]
 * JSOC 2.0 released -- February 03, 2006. See [http://jsoc.stanford.edu/release-2.0.notes release notes]
 * JSOC 1.0 released -- October 19, 2005. See [http://jsoc.stanford.edu/release-1.0.notes release notes]		  * JSOC 5.11 released -- October 6, 2010 See [http://jsoc.stanford.edu/release_notes/release-5.11.notes release notes]
 * JSOC 5.10 released -- September 1, 2010 See [http://jsoc.stanford.edu/release_notes/release-5.10.notes release notes]
 * JSOC 5.8 released -- Mar 16, 2010 See [http://jsoc.stanford.edu/release_notes/release-5.8.notes release notes]
 * JSOC 5.7 released -- Mar 12, 2010 See [http://jsoc.stanford.edu/release_notes/release-5.7.notes release notes]
 * JSOC 5.6 released -- Jan 28, 2010 (quick rel notes: jsoc_sync.pl should work better, remove a use /auto/homeX paths, added qdecoder lib (so modules can parse HTTP input), cmdparams - fix mem corruption, track which arguments actually, used, slony subscribe_series, subscribe_manage, and server code, pass original cmd args not used by drms_run to the drms_run script, cntrl-C now shuts down modue quickly, sort keywords, segments according to jsd order (in code that lists those items, like show_info -j), improve hash-table implementation (hash function wasn't working, removed unnecessary complexity that was running inefficiently), don't call SUM_put() on a SU if there are no files in the SU, fixes for VARDIM bugs, delete_series checks for series existence before doing anything, modify_series won't change series that are slonied, remove CFITSIO TFORM1 hack (this workaround was no longer necessary as we incorporated a new CFITSIO that had a bug fixed), some jsoc_fetch bugs fixed, several enhancements to lookdata and exportdata (tar export, upload of file containing rec-queries, etc.), completion of iorbit (lev0) code, addition of the rings project.)
 * JSOC 5.5 released -- Oct 09, 2009 See [http://jsoc.stanford.edu/release_notes/release-5.5.notes release notes]
 * JSOC 5.3 released -- Aug 05, 2009 See [http://jsoc.stanford.edu/release_notes/release-5.3.notes release notes]
 * JSOC 5.2 released -- Aug 04, 2009 See [http://jsoc.stanford.edu/release_notes/release-5.2.notes release notes]
 * JSOC 5.1 released -- May 01, 2009 See [http://jsoc.stanford.edu/release_notes/release-5.1.notes release notes]
 * JSOC 5.0 released -- Jan 30, 2009 See [http://jsoc.stanford.edu/release_notes/release-5.0.notes release notes]
 * JSOC 4.7 released -- Oct 16, 2008 See [http://jsoc.stanford.edu/release_notes/release-4.7.notes release notes]
 * JSOC 4.6 released -- Sep 03, 2008 See [http://jsoc.stanford.edu/release_notes/release-4.6.notes release notes]
 * JSOC 4.5 released -- Jul 16, 2008 See [http://jsoc.stanford.edu/release_notes/release-4.5.notes release notes]
 * JSOC 4.4 released -- Jun 09, 2008 See [http://jsoc.stanford.edu/release_notes/release-4.4.notes release notes]
 * JSOC 4.3 released -- May 26, 2008 See [http://jsoc.stanford.edu/release_notes/release-4.3.notes release notes]
 * JSOC 4.2 released -- Apr 08, 2008 See [http://jsoc.stanford.edu/release_notes/release-4.2.notes release notes]
 * JSOC 4.1 released -- Mar 03, 2008 See [http://jsoc.stanford.edu/release_notes/release-4.1.notes release notes]
 * JSOC 4.0 released -- Dec 07, 2007 See [http://jsoc.stanford.edu/release_notes/release-4.0.notes release notes]
 * JSOC 3.8 released -- Sep 12, 2007 See [http://jsoc.stanford.edu/release_notes/release-3.8.notes release notes]
 * JSOC 3.3 released -- Nov 03, 2006 See [http://jsoc.stanford.edu/release_notes/release-3.3.notes release notes]
 * JSOC 3.2 released -- Sep 15, 2006 See [http://jsoc.stanford.edu/release_notes/release-3.2.notes release notes]
 * JSOC 3.1 released -- Aug 24, 2006 See [http://jsoc.stanford.edu/release_notes/release-3.1.notes release notes]
 * JSOC 3.0 released -- Aug 14, 2006. See [http://jsoc.stanford.edu/release_notes/release-3.0.notes release notes]
 * JSOC 2.3 released -- Aug 10, 2006. See [http://jsoc.stanford.edu/release_notes/release-2.3.notes release notes]
 * JSOC 2.2 released -- May 30, 2006. See [http://jsoc.stanford.edu/release_notes/release-2.2.notes release notes]
 * JSOC 2.1 released -- May 24, 2006. See [http://jsoc.stanford.edu/release_notes/release-2.1.notes release notes]
 * JSOC 2.0 released -- Feb 03, 2006. See [http://jsoc.stanford.edu/release_notes/release-2.0.notes release notes]
 * JSOC 1.0 released -- Oct 19, 2005. See [http://jsoc.stanford.edu/release_notes/release-1.0.notes release notes]
Line 18: Line 38:
 * [http://jsoc.stanford.edu/doc/DRMSreport_html/index.html DRMS (html)] -- DRMS Overview[http://hmi.stanford.edu/development/JSOC_Documents/DRMS_V10.pdf (as pdf)] - old doc, contents being verified and included in these pages.
 * [wiki:DrmsNames DRMS Names] -- DRMS Dataset Names and Queries
 * [wiki:DrmsSeriesNames DRMS Series Names] -- Data Series Reserved Names
 * Data Storage, Archive, On-Line Retention, EtC.		  A. '''DRMS Overview'''
  * [http://jsoc.stanford.edu/doc/DRMSreport_html/index.html DRMS (html)] -- DRMS Overview[http://hmi.stanford.edu/development    /JSOC_Documents/DRMS_V10.pdf (as pdf)] - old doc, contents being verified and included in these pages.

 A. '''Names'''
  * [wiki:DrmsNames DRMS Names Summary] -- DRMS Dataset Names and Queries BNF summary
  * [http://hmi.stanford.edu/doc/JSOC/DRMS_dataset_names.pdf DRMS Dataset Names] -- Full description (pdf)
  * [wiki:DrmsSeriesNames DRMS Series Names] -- Data Series Reserved Names
  * SUMS Info -- Data Storage, Archive, On-Line Retention, Etc.
Line 24: Line 49:
 * [wiki:Jsd .jsd] -- JSOC Series Definition Files
 * Data series utilities to be run from a user's shell
   * [wiki:DrmsCreateSeriesCmd create_series] -- Create entries and tables for a new series in the DRMS database
   * [wiki:DrmsDescribeSeriesCmd describe_series] -- Prints a verbose description of the
named series and its current highest record number on stdout.
   * [wiki:DrmsDeleteSeriesCmd delete_series] -- Removes a series and all its associated entries from DRMS.		  A. '''JSD Format'''
  * [wiki:Jsd .jsd -- JSOC Series Definition Files]
Line 31: Line 52:
== JSOC Sessions, Pipelines, and Modules ("''Oh my!''") ==  A. '''JSOC Sessions, Pipelines, and Modules (''Oh my!'')'''
Line 33: Line 54:
JSOC programs that use DRMS to operate on DataSeries are called "modules". Modules are run in "sessions". HMI and AIA major processing tasks are accomplished in "pipelines" consisting of one or more sessions. Pipelines are started by "PUI" (Pipeline User Interface) usually by the JSOC production team. Pipelines may also be initiated by users requesting [wiki:DataSet DataSets] via the web or by team members running locally or remotely. A DataSet is a collection of records selected by a query. In essence a dataset name is simply the query that describes it.  JSOC programs that use DRMS to operate on DataSeries are called "modules". Modules are run in "sessions". HMI and AIA major
 processing tasks are accomplished in "pipelines" consisting of one or more sessions. Pipelines are started by "PUI"
 (Pipeline User Interface) usually by the JSOC production team. Pipelines may also be initiated by users requesting
 [wiki:DataSet DataSets] via the web or by team members running locally or remotely. A DataSet is a collection of records
 selected by a query. In essence a dataset name is simply the query that describes it.
Line 35: Line 60:
A DRMS Session is the basic unit of computing that interracts with DRMS and SUMS. At the start of a session the user connects to the DRMS database. During the session the user runs one or more modules which read or create [wiki:DataRecord DataRecords] in DataSeries. Access to the actual data stored in SUMS is accomplished within a module via the DRMS API. At the end of a session, SUMS is notified to save any new records online and/or on tape, or to delete records marked temporary to the session.  . A DRMS Session is the basic unit of computing that interracts with DRMS and SUMS. At the start of a session the user
 connects to the DRMS database. During the session the user runs one or more modules which read or create   [wiki:DataRecord DataRecords] in DataSeries. Access to the actual data stored in SUMS is accomplished within a   module via the DRMS API. At the end of a session, SUMS is notified to save any new records online and/or on tape,
 or to delete records marked temporary to the session.
Line 37: Line 66:
Actually using the JSOC DRMS requires running a program or module. By "program" we mean a normal shell command and by "module" we mean a program built to run within a DRMS session and communication to a drms_server. There are four types
of programs/modules:
 * '''Modules''' - Most programs that do the work of the user of JSOC are what we call "modules". On the outside modules look like programs. They must run in a DRMS session. If they are built with the normal jsoc_main program they will use an existing session if they are run from a Session Provider or will start their own use-once session if they are called stand-alone from the shell.
 * '''Utility programs''' like [wiki:DrmsCreateSeriesCmd create_series] and [wiki:DrmsDescribeSeriesCmd describe_series] which are usually used to manage the existence of dataseries, not to use dataseries. These programs talk directly to the database.
 * '''Session Providers''' like [wiki:DrmsRunCmd drms_run] or later the [wiki:JsocPui Pipeline User Interface] start DRMS sessions and execute a script file. They can also be used to execute a single instance of a module.
 * '''[wiki:DrmsServerCmd drms_server]''' which connects connects to the database and serves sessions. Most users will not need to start drms_server explicitly.		  . Actually using the JSOC DRMS requires running a program or module. By "program" we mean a normal shell command and by
 "module" we mean a program built to run within a DRMS session and communication to a drms_server. There are four types 
 of programs/modules:
  * '''Modules''' - Most programs that do the work of the user of JSOC are what we call "modules". On the outside modules
  look like programs. They must run in a DRMS session. If they are built with the normal jsoc_main program they will use an
  existing session if they are run from a Session Provider or will start their own use-once session if they are called
  stand-alone from the shell.
  * '''Utility programs''' like [http://jsoc.stanford.edu/doxygen_html/group__create__series.html create_series] and [http://jsoc.stanford.edu/doxygen_html/group__describe__series.html describe_series]
  which are usually used to manage the existence of dataseries, not to use dataseries. These programs talk directly to the database.
  * '''Session Providers''' like [wiki:DrmsRunCmd drms_run] or later the [wiki:JsocPui Pipeline User Interface] start
  DRMS sessions and execute a script file. They can also be used to execute a single instance of a module.
  * '''[http://jsoc.stanford.edu/doxygen_html/group__drms__server.html drms_server]''' which connects connects to the database and serves sessions.
  Most users will not need to start drms_server explicitly.
Line 44: Line 80:
 The benefit of running programs as "modules" will hopefully become apparent when we start running
 complex pipelines using hundreds of processors.
Line 45: Line 83:
The benefit of running programs as "modules" will hopefully become apparent when we start running
complex pipelines using hundreds of processors.		 == General Development Information - Using Modules ==
 A. '''DRMS Man Pages'''
 All the JSOC "man" pages are now maintained with [http://www.stack.nl/~dimitri/doxygen/index.html doxygen], a semi-automatic
 documentation tool. They are available in html form via:
  * [http://jsoc.stanford.edu/doxygen_html/ Drms Developer's Documentation][[BR]]
Line 48: Line 89:
== [wiki:DRMSSetup Setting up Your Own DRMS] ==  All programs and functions have entries in the doxygen generated pages.
Line 50: Line 91:
Information for developers outside the JSOC who wish to construct an independent data archive
that can work in cooperation with the JSOC and other archives (or completely independently)		  A. '''Limits'''
 . There are limits ...
  * memory limits on number of records in the cache (512Meg / (2.5*record size) ). While this may seem like a lot, for datasets with a lot of keywords (e.g. mdi_vw_V_06h) it can be a real limit to the number of records that can be open at a time. For the vw_V example it means that DRMS_QUERY_MEM should be set to at lest 2500 (yes 2.5 gig) to open 100 days of one-minute data. Modules expecting to need tens of thousands of records opened should arrange to do the work in blocks with drms_close_records used to empty the record cache to free memory.
  * length of names of series, keywords, etc. (64 chars)
  * length of comma sep list of prime key names (1024 chars)
  * length of descriptions of series, keywords, links, and segments (254 chars)
  * length of string values of keywords (dont know)
  * number of keywords in a record (dont know)
  * number of records in a series (no fixed limit)
  * length of segment filename (255 chars)
  * length of path (511 chars)
Line 53: Line 103:
= General Information =
== DRMS Man Pages ==		  A. '''Log Files - Processing meta-data'''
 .There are log files. Stdout and Stderr are captured in files as well as shown during processing (depending on module
 and -v flag). These are all put into a SUMS directory and indexed in DRMS by session ID. The session ID is stored in
 each record so the log files can be retrieved if/when needed. Unless otherwise specified, the default retention time
 for log files is 10 days. The log files are archived if any one of the SUs in the current session is to be archived.
  * drms_server logs --
  . The default is no logging. When the logging option is turned on (-L), stdout and stderr are redirected to files in SU directory.
  * module logs --
  . The default is no logging. When the logging option is turned on (-L), stdout and stderr are tee-ed to files in SU directory.
Line 56: Line 113:
 * [http://jsoc.stanford.edu/man/index.html#man1 Drms Program/Module Man Pages, man1][[BR]]
 * [http://jsoc.stanford.edu/man/index.html#man3 Drms Subroutine Man Pages, man3]		 == Software Development - Building Modules ==
 
 A. '''DRMS Applications Programming Interface]'''
 Descriptions of the API developed for the underlying JSOC database, and how to code with it.
  * [:DrmsApi:DRMS API summary] - ''old''
  * [http://jsoc.stanford.edu/doxygen_html/modules.html DRMS API Manual]
  -- More detailed information for users and developers of specific JSOC software programs or interfaces using the '''Doxygen''' tools.
  Please use the search engine there to find documentations for any API functions.
Line 59: Line 122:
   All programs and modules should have unix-style man pages at [http://jsoc.stanford.edu/man/index.html#man1 man1] but Some do not yet:
   * [wiki:DrmsServerCmd drms_server],
   * [wiki:DrmsQueryCmd drms_query],
   * [wiki:DrmsCreateSeriesCmd create_series],
   * [wiki:DrmsDescribeSeriesCmd describe_series],
   * [wiki:DrmsDeleteSeriesCmd delete_series]		  A. '''SUMS API'''
  * [:SumsApi]
 
 A. '''JSOC Software Tree'''
  * [wiki:FileStruct Software File Tree] -- Organization of files and cvs tree.
  * [http://jsoc.stanford.edu/cvs/ GUI for JSOC CVS] -- GUI access to DRMS and SUMS software
  * [http://jsoc.stanford.edu/cvs/*checkout*/jsoc/src/base/libdrms/drms_types.h?rev=HEAD&content-type=text/plain drms_types.h]
  . -- DRMS types and structure defintions.
Line 66: Line 131:
   Note that all modules built with jsoc_main share a basic set of flags and command line keywords. See module.1 in man1.  A. '''Making a JSOC/DRMS Module'''
  * [wiki:DrmsModule DRMS Module] -- DRMS Module Structure and Overview
  * [wiki:DrmsApi DRMS API] -- DRMS Data Types and Structures and API
  * [wiki:DrmsMakeModule DRMS Module Compilation] -- Running 'make' for modules
Line 68: Line 136:
 A. '''JSOC make system'''
  * [wiki:JsocMakefileBackground Background/Reference]
  * [wiki:JsocMakeSystem JSOC make system understood]
Line 69: Line 140:
== Limits ==  A. '''Web Exports via AJAX API'''
  * [wiki:AjaxJsocConnect AJAX Style Web Access for JSOC] used by [http://jsoc.stanford.edu/ajax/lookdata.html lookdata.html]
Line 71: Line 143:
There are limits ...
 * memory limits on number of records in the cache (512Meg / (2.5*record size) ). While this may seem like a lot, for datasets with a lot of keywords (e.g. mdi_vw_V_06h) it can be a real limit to the number of records that can be open at a time. For the vw_V example it means that DRMS_QUERY_MEM should be set to at lest 2500 (yes 2.5 gig) to open 100 days of one-minute data. Modules expecting to need tens of thousands of records opened should arrange to do the work in blocks with drms_close_records used to empty the record cache to free memory.
 * length of names of series, keywords, etc. (31 chars)
 * length of descriptions of series, keywords, links, and segments (254 chars)
 * length of string values of keywords (dont know)
 * number of keywords in a record (dont know)
 * number of records in a series (no fixed limit)
 * length of segment filename (255 chars)
 * length of path (511 chars)		 == Developers' Weekly Progress Reports ==
  * DeveloperProgressReports -- An archive of developers' weekly progress reports
Line 81: Line 146:
== Log Files - Processing meta-data == == JSOC Development Projects ==
Line 83: Line 148:
There are log files. Stdout and Stderr are captured in files as well as shown during processing (depending on module and -v flag). These are all put into a SUMS directory and indexed in DRMS by session ID. The session ID is stored in each record so the log files can be retrieved if/when needed. Unless otherwise specified, the default retention time for log files is the maximum retention time of all SUs processed in the current session. The log files are archived if any one of the SUs in the current session is to be archived.
 * drms_server logs --
   The default is no logging. When the logging option is turned on (-L), stdout and stderr are redirected to files in SU directory.
 * module logs --
   The default is no logging. When the logging option is turned on (-L), stdout and stderr are tee-ed to files in SU directory.
= Software Development - Building Modules =
 
== JSOC Software Tree ==
 * [wiki:FileStruct Software File Tree] -- Organization of files and cvs tree.
 * [http://jsoc.stanford.edu/cvs/ GUI for JSOC CVS] -- GUI access to DRMS and SUMS software
 * [http://jsoc.stanford.edu/cvs/*checkout*/jsoc/src/base/libdrms/drms_types.h?rev=HEAD&content-type=text/plain drms_types.h] -- DRMS types and structure defintions.
== Making a JSOC/DRMS Module ==
 * [wiki:DrmsModule DRMS Module] -- DRMS Module Structure and Overview
 * [wiki:DrmsApi DRMS API] -- DRMS Data Types and Structures and API
 * [wiki:DrmsMakeModule DRMS Module Compilation] -- Running 'make' for modules		  A. '''DSDS-Data Access from JSOC'''
  * [http://hmi.stanford.edu/development/JSOC_Documents/JSOC_DSDS_Interface_Specification.pdf Interface Specification (.pdf)]
  . -- Details for builders of modules that will access MDI data directly from DRMS code.
Line 99: Line 152:
== Making a JSOC/DRMS Library ==
 * [wiki:JsocLibrary JSOC LIbrary] -- Creating and using a JSOC library		  A. '''Remote DRMS/SUMS - netDRMS'''
  * See Rick Bogart and the collection of web pages on NetDRMS at http://jsoc.stanford.edu/netdrms/
Line 102: Line 155:
== Notes on JSOC Makefile ==
 * [wiki:JsocMakefileBackground Background/Reference]
 * [wiki:JsocMakefileAdd How to add a sub directory]		 == JSOC Operator's Guide ==
Line 106: Line 157:
== Development Notes ==
 * [wiki:DevNotes Development Notes Page]		  A. JSOC Administration
 '''[:JsocAdministration: JSOC Administration]''' -- Information for management and installation of DRMS/SUMS
Line 109: Line 160:
== [wiki:PgDBAdmin PostgreSQL Database Administration] ==

 
== JSOC Backup and Restore ==
 * [wiki:JSOC Backup/Restore Notes Page]

== SUM API ==
 * [http://sun.stanford.edu/web.hmi/development/SU_Development_Plan/SUM_API.html API web page]

== DSDS-Data Access from JSOC ==
 * [http://hmi.stanford.edu/development/JSOC_Documents/JSOC_DSDS_Interface_Specification.pdf Interface Specification (.pdf)]		  A. '''Running Datacapture and lev0 Pipeline during SDI I&T'''
  * [http://jsoc.stanford.edu/production/whattodolev0.txt][[BR]]

Welcome to the Wiki for JSOC software development

TableOfContents

For general information including the basic setup to get started see the [wiki:JsocUsersGuide Users Guide].

News

DRMS Data Series

  1. DRMS Overview

  2. Names

  3. JSD Format

    • [wiki:Jsd .jsd -- JSOC Series Definition Files]

  4. JSOC Sessions, Pipelines, and Modules (Oh my!)

    JSOC programs that use DRMS to operate on DataSeries are called "modules". Modules are run in "sessions". HMI and AIA major processing tasks are accomplished in "pipelines" consisting of one or more sessions. Pipelines are started by "PUI" (Pipeline User Interface) usually by the JSOC production team. Pipelines may also be initiated by users requesting [wiki:DataSet DataSets] via the web or by team members running locally or remotely. A DataSet is a collection of records selected by a query. In essence a dataset name is simply the query that describes it.

  5. A DRMS Session is the basic unit of computing that interracts with DRMS and SUMS. At the start of a session the user connects to the DRMS database. During the session the user runs one or more modules which read or create

    [wiki:DataRecord DataRecords] in DataSeries. Access to the actual data stored in SUMS is accomplished within a module via the DRMS API. At the end of a session, SUMS is notified to save any new records online and/or on tape, or to delete records marked temporary to the session.

  6. Actually using the JSOC DRMS requires running a program or module. By "program" we mean a normal shell command and by "module" we mean a program built to run within a DRMS session and communication to a drms_server. There are four types of programs/modules:

    • Modules - Most programs that do the work of the user of JSOC are what we call "modules". On the outside modules look like programs. They must run in a DRMS session. If they are built with the normal jsoc_main program they will use an existing session if they are run from a Session Provider or will start their own use-once session if they are called stand-alone from the shell.

    • Utility programs like [http://jsoc.stanford.edu/doxygen_html/group__create__series.html create_series] and [http://jsoc.stanford.edu/doxygen_html/group__describe__series.html describe_series] which are usually used to manage the existence of dataseries, not to use dataseries. These programs talk directly to the database.

    • Session Providers like [wiki:DrmsRunCmd drms_run] or later the [wiki:JsocPui Pipeline User Interface] start DRMS sessions and execute a script file. They can also be used to execute a single instance of a module.

    • [http://jsoc.stanford.edu/doxygen_html/group__drms__server.html drms_server] which connects connects to the database and serves sessions. Most users will not need to start drms_server explicitly.

    The benefit of running programs as "modules" will hopefully become apparent when we start running complex pipelines using hundreds of processors.

General Development Information - Using Modules

  1. DRMS Man Pages All the JSOC "man" pages are now maintained with [http://www.stack.nl/~dimitri/doxygen/index.html doxygen], a semi-automatic documentation tool. They are available in html form via:

    All programs and functions have entries in the doxygen generated pages.

  2. Limits

  3. There are limits ...
    • memory limits on number of records in the cache (512Meg / (2.5*record size) ). While this may seem like a lot, for datasets with a lot of keywords (e.g. mdi_vw_V_06h) it can be a real limit to the number of records that can be open at a time. For the vw_V example it means that DRMS_QUERY_MEM should be set to at lest 2500 (yes 2.5 gig) to open 100 days of one-minute data. Modules expecting to need tens of thousands of records opened should arrange to do the work in blocks with drms_close_records used to empty the record cache to free memory.
    • length of names of series, keywords, etc. (64 chars)
    • length of comma sep list of prime key names (1024 chars)
    • length of descriptions of series, keywords, links, and segments (254 chars)
    • length of string values of keywords (dont know)
    • number of keywords in a record (dont know)
    • number of records in a series (no fixed limit)
    • length of segment filename (255 chars)
    • length of path (511 chars)

  4. Log Files - Processing meta-data

  5. There are log files. Stdout and Stderr are captured in files as well as shown during processing (depending on module and -v flag). These are all put into a SUMS directory and indexed in DRMS by session ID. The session ID is stored in each record so the log files can be retrieved if/when needed. Unless otherwise specified, the default retention time for log files is 10 days. The log files are archived if any one of the SUs in the current session is to be archived.
    • drms_server logs --
    • The default is no logging. When the logging option is turned on (-L), stdout and stderr are redirected to files in SU directory.
    • module logs --
    • The default is no logging. When the logging option is turned on (-L), stdout and stderr are tee-ed to files in SU directory.

Software Development - Building Modules

  1. DRMS Applications Programming Interface] Descriptions of the API developed for the underlying JSOC database, and how to code with it.

    • [:DrmsApi:DRMS API summary] - old

    • [http://jsoc.stanford.edu/doxygen_html/modules.html DRMS API Manual] -- More detailed information for users and developers of specific JSOC software programs or interfaces using the Doxygen tools. Please use the search engine there to find documentations for any API functions.

  2. SUMS API

  3. JSOC Software Tree

  4. Making a JSOC/DRMS Module

    • [wiki:DrmsModule DRMS Module] -- DRMS Module Structure and Overview

    • [wiki:DrmsApi DRMS API] -- DRMS Data Types and Structures and API

    • [wiki:DrmsMakeModule DRMS Module Compilation] -- Running 'make' for modules

  5. JSOC make system

  6. Web Exports via AJAX API

Developers' Weekly Progress Reports

JSOC Development Projects

  1. DSDS-Data Access from JSOC

  2. Remote DRMS/SUMS - netDRMS

JSOC Operator's Guide

  1. JSOC Administration

    [:JsocAdministration: JSOC Administration] -- Information for management and installation of DRMS/SUMS

  2. Running Datacapture and lev0 Pipeline during SDI I&T

JsocWiki: JsocDevelopersGuide (last edited 2021-11-16 01:34:32 by ArtAmezcua)