ViewVC Help
View File | Revision Log | Show Annotations | Root Listing
root/JSOC/CM/V8.0/release.notes
Revision: 1.2
Committed: Mon Apr 22 16:46:47 2013 UTC (10 years, 5 months ago) by arta
Branch: MAIN
CVS Tags: NetDRMS_Ver_8-0, NetDRMS_Ver_8-8, Ver_8-5, Ver_LATEST, NetDRMS_Ver_LATEST, NetDRMS_Ver_8-12, NetDRMS_Ver_8-10, NetDRMS_Ver_8-11, NetDRMS_Ver_9-1, NetDRMS_Ver_9-0, NetDRMS_Ver_9-3, NetDRMS_Ver_9-2, NetDRMS_Ver_9-5, NetDRMS_Ver_9-4, NetDRMS_Ver_9-41, Ver_9-41, Ver_DRMSLATEST, NetDRMS_Ver_8-4, NetDRMS_Ver_8-5, NetDRMS_Ver_8-6, Ver_8-8, NetDRMS_Ver_8-7, Ver_8-2, Ver_9-3, Ver_8-0, Ver_8-1, Ver_8-6, Ver_8-7, Ver_8-4, Ver_8-11, Ver_9-1, Ver_8-3, Ver_9-5, Ver_9-4, Ver_8-10, Ver_9-2, Ver_8-12, Ver_9-0, HEAD
Changes since 1.1: +17 -1 lines
Log Message:
Incorporate ricks release notes into the general version 8.0 release notes

File Contents

# Content
1 Release Notes JSOC V8.00 17APR013
2 ------------------------ --------
3
4
5 A release is a set of files, each having a specific version. And a release typcially
6 has a version number because over time you have newer and newer releases of the
7 same product. For example, a hypothetical 1.3 release may contain fileA#1.8,
8 fileB#1.2, fileC#2.2 and a 1.4 release may contain fileA#2.5, fileB#2.1, fileC#2.9.
9 JSOC releases are similarly versioned and contain a set of such files. JSOC release
10 code is guaranteed to compile on cluster nodes (eg., n00, n02). At the
11 time of the creation of the release, the release versions of each file
12 will be the most recent. But as time passes, newer versions of some
13 files will be made, and there is no guarantee that these changes will
14 not destabilize JSOC (ie., they may cause JSOC to no longer compile or execute
15 properly).
16
17 There are several ways to use this release. If you wish to simply use pre-built
18 binaries, you can simply use the production binaries, which are located at
19 /home/jsoc/cvs/Development/JSOC (The release binaries are actually in
20 /home/jsoc/cvs/JSOC, but as our production code changes emore quickly
21 than releases are generated, we put critical fixes in the
22 "Development" tree. To be sure you use code that has been built with
23 these critical fixes, you'll need to use the "Development" tree. As
24 time passes our production code will stabilize. When that happens, you should use
25 /home/jsoc/cvs/JSOC. But for now, you should use the "Development"
26 tree.). Every time a release is created, the binaries in
27 this location get updated. Only the jsoc user can update these binaries.
28 You could run /home/production/cvs/JSOC/Development/bin/linux_x86_64/show_keys,
29 for example.
30
31 If instead you want to work with stable source files, then you must have a sandbox,
32 which is a local copy (in your home directory) of the files in the cvs depot.
33 You would probably want to work with a sandbox if you plan on making eventual
34 changes to the depot files. Changes you make to your sandbox files are not visible
35 to other users until you "commit" those changes back to the cvs depot. Please see
36 "If You Don't Have a Sandbox" below for more information on how to create a sandbox.
37
38 Obtaining the Release
39 ---------------------
40 To update your working directory to this release, or to check-out this release anew,
41 please visit http://jsoc.stanford.edu/jsocwiki/CvsInit (please see the section entitled
42 Update Your Existing Working Directory ("Sandbox")). Please keep in mind that
43 users may have modified files since the release was created, so use of the
44 scripts documented in the web page may result in a working directory whose
45 content is not identical to the release.
46
47 Additional Info
48 ---------------
49 Use the Apache cvs gui to see the diffs between file revisions. For
50 example, go to http://jsoc.stanford.edu/cvs/JSOC/base/drms/
51 and click on the name in the File column and then click on
52 "diffs to previous #" to see the diffs.
53
54 Changes since previous release (V7.0 - August 28, 2012)
55 ----------------------------------------------------------
56
57 NEW FEATURES:
58
59 + Support for the linux-avx architecture was added. To build avx binaries for NetDRMS, you must have properly edited your config.local file. Please see config.local.template for an example.
60 + Support for shadow tables was added (FULL JSOC RELEASE ONLY - NOT NetDRMS). A shadow table is a database table that acts as a cache for most database queries that DRMS uses when DRMS dataseries are queried. It allows DRMS to bypass doing expensive database operations. It is helpful for series that large and on which queries take a long time to complete.
61 + The limbfit code now builds with icc only.
62 + Added a json parser for C code (jsmn).
63 + Added the module rawingest to be used for ingesting raw SUMS files.
64 + Added the module jsoc_export_clone.
65 + Added code to track "old" modules. DRMS will not let old modules run. This new code logs instances where a module was rejected.
66 + Added support to libdsds.so for DSDS records that have no data files.
67 + Added support to drms_count_records() for record-set queries that contain comma-separated sub-queries.
68 + The slony-log parser (parse_slon_logs.pl) now supports UPDATE statements. If a record is updated in the original series table, that update will be propagated to the remote sites subscribed to the series.
69 + Added a new script, addkeys.pl, that will add keywords to existing series, even if the series is currently being replicated.
70 + Added the timestamp to all log entries written by jsoc_fetch.
71 + Added support for cmdparams_get_mask64() - a function to retrieve 64-bit masks.
72 + Added support to DRMS perl library for creating read-only and write-only pipes.
73 + Added new SUMS API function - SUMLIB_PavailOn.
74 + Several improvements were made to ingest_dsds_to_drms.
75 + The global helioseismology code now supports CALVER64.
76 + The global helioseimsology code now tracks source file versions.
77 + Add support for IRIS to a bunch of code.
78 + The limbfit code was re-organized to store many small data files into one larger TAS file.
79 + Support for CALVER64 was added to the sharp code.
80 + Updated the harp pipelines with changes from Mike Turmon.
81 + Added a new module, m2m3harp.
82 + Added a new module, aia_fixCROTA2.
83 + Added support to the script that checks out files from the JSOC repository for a JSOC root directory that has a name other than "JSOC".
84 + Added a script, findsessionrecs.pl, that will find all records in all series created within a time window. This is used for examining records that were created during a hardware crash.
85 + Added a script, prodbuild.pl, that simplifies updating and building in the production CVS tree.
86
87 + Added ring-diagram documentation (apps/datavg): added writing of verbose output to log segment if present, and recording of input recnum's; added logging of CalVer64 values used; added support for specification of tmid in date_time format; Documentation at http://hmi.stanford.edu/teams/rings/mod_datavg.html.
88 + Added ring-diagram functionality (apps/gentargs): implemented Stonyhurst longitude reporting option for grids timed* Documentation at http://hmi.stanford.edu/teams/rings/mod_datavg.html.
89 + Added ring-diagram functionality (apps/mtrack): added recording of recnums of mapped images to log; Added recording of calling params info to comment or history key; Added support for acceptance and/or rejection of records with certain values of CalVer64 (or other equivalent key); Added logging of image rejection cause summaries and CalVer64 values used; Documentation at http://hmi.stanford.edu/teams/rings/mod_datavg.html.
90 + Added ring-diagram functionality (apps/rdcover): added pangle selection options as for datavg; Documentation at http://hmi.stanford.edu/teams/rings/mod_datavg.html.
91 + Added time-distance functionality (apps/invert_td_hr): added option for selection of keywords to propagate, with standard list, including WCS keys for first two dimensions.
92 + Added time-distance functionality (apps/travel_times): added option for selection of keywords to propagate from input.
93 + Added time-distance functionality (scripts/tdsynop): changed default from test to non-test; Use hmi.TDKernels for inversion kernels; require version 1100; Use Stonyhurst rather than Carrington longitudes for targets in traveltimes (fixes problem due to rounding of slotted prime keys).
94
95
96 DEFECTS FIXED:
97 + In serverdefs.h: do not use Stanford-specific values as defaults, otherwise for localized builds, which may be remote sites, Stanford-specific values would be used.
98 + Remove the requirement that a production-user table exists in the DRMS.
99 + The "dontwait" flag that causes SUMS to asynchronously fetch storage units was disabled. The flag appears in multiple functions at multiple levels in the DRMS code. SUMS does not support asynchronous fetching.
100 + Added code to disallow further SUMS access after DRMS times-out waiting for a SUM_get() call to resolve.
101 + The implementation for DRMS cursory queries must strip off a SQL limit statement from an existing SQL query. In doing so, a parser was improperly searching for the limit statement, and finding a keyword named "LO_LIMIT". The code now properly finds the limit statement.
102 + DRMS now rejects sunums of -1 when sending a list of sunums to SUMS via the SUM_infoEx() call.
103 + DRMS now rejects the writing of a slice to a FITS file if the scaling of the slice does not match the existing scaling of the file.
104 + A deadlock was discovered and fixed in the module-termination code. The SUMS thread was attempting to lock the server after drms_server_commit() had already done so.
105 + There was a bug in the slony-log parser (parse_slon_logs.pl) in which it miscalculated the last-parsed log number. This was fixed.
106 + Made all jsoc_export_as_fits arguments optional (except that either reqid or rsquery must be provided).
107 + The export manager code (jsoc_export_manage) was improperly sending email notifications (messages announcing the completion of an export request) to email addresses formed by appending "j1.stanford.edu" to all file names in /home/jsoc. This was fixed by checking for a failure in a show_info call that wasn't being checked before.
108 + The code that determines the current time in jsoc_fetch was fixed.
109 + jsoc_fetch had been confusing the source and target records when exporting a linked segment.
110 + Removed a redundant definition of drms_sprint_rec_query().
111 + Made fixes for bugs in jsoc_info.
112 + Fixed issues with the exports of TAS files.
113 + Fixed issues with font sizes in jsoc_export_as_movie.
114 + Fixed issues with the cmdparams_get_intXX-function family.
115 + Fixed error-reporting issues in the fitsrw_getfptr() function and in code that runs when errors occur when closing FITS files.
116 + Fixed a buffer-overflow in libdsds.so.
117 + Removed modify_series from our releases. - it is currently non-functional.
118 + Fixed a bug in show_info in which the code was ignoring an error returned by drms_open_recordset().
119 + In show_info, removed repetitive and unneeded calls to SUM_get().
120 + A series filter was being prematurely freed in show_series.
121 + Spurious error messages were removed from ingest_dsds_to_drms.
122 + Fixed validation errors in exportdata.html, the export web page.
123 + Fixed issues with a reset button in exportdata.html, the export web page.
124 + Fixed issues with case-sensitivity when searching for words in exportdata.html, the export web page.
125 + Updated the help messages in exportdata.html, the export web page.
126 + Fixed memory leaks in the global helioseismology code.
127 + Fixed very large memory leak in the sharp code.
128 + We made two fixes to large numbers of records in the HARP series.
129 + Fixed a bug in the code that maintains run logs.
130 + Make the vfisv_filter() and invert_() declarations conform with the C99 standard.
131
132 + Ring-diagram bug fixes (apps/mtrack): fixed bug in bscale-bzero overrides.
133 + Ring-diagram bug fixes (apps/pspec3): fixed bug in test for minimum values out of scaling range (zero); Documentation at
134 http://hmi.stanford.edu/teams/rings/mod_datavg.html.
135 + Ring-diagram bug fixes (scripts/avg120): fixed qmask argument bug; previously was only using default value of 80000000 rather than desired value of 80004000; set pkey to T_REC instead of default T_OBS; Documentation at http://hmi.stanford.edu/teams/rings/pipe_avg120.html etc.
136 + Ring-diagram bug fixes (scripts/rdday): improved/fixed record accounting when reprocessing or restarting; Documentation at http://hmi.stanford.edu/teams/rings/pipe_avg120.html etc.
137 + Ring-diagram bug fixes (scripts/runrdsyn): fixed bug involved with continuation over CR boundary; added notification on last submission.