Release Notes for November 2015 version of exportdata.html. 1. Added processing option hmiB2ptr and enabled flag in im_patch and maproj processing to signify that all segments should be processed if hmiB2ptr was enabled. NOTE other changes were made recently to deal with multiple segments in exportdata.html. Now if multiple segments are listed on the recordset query then they will all be processed in any processing steps enabled. If multiple segments are present and a segment list in '{...}' is not included then only the first segment will be subject or processing. ____________________________________________________________________ Release Notes for April-May 2015 version of exportdata.html. 1. Note that the '=' in keyword=value params in cgi-bin scripts must not be url_escaped. The '=' iself must be present. 2. the warning about Notify needed and large requests has been removed from the MOTD and is now here. If you are making large data requests please read: http://jsoc.stanford.edu/ajax/JSOC_LargeRequests.html Release Notes for 30 January 2015 version of exportdata.html. Contact Phil Scherrer or Art Amezcua if problems found in next few days. Exportdata changes: 1. A number of bugs introduced last fall have been cleaned up. These were mostly visible only when enabling processing upon export for e.g. im_patch. 2. Modifications were made to verify email addresses, which are now required for exports from jsoc and jsoc2. At the first use of an email addreess, mail will be sent to that address and until a reply is recieved exports will not be allowed with that address. This only needs to be done once and will usually take less than a minute. The address registration can also be done in a new page, jsoc.stanford.edu/ajax/register_email.html. Using the separate registration process will make it easier for those using scripts and the jsoc cgi-bin programs. 3. The jsoc_fetch cgi-bin command will also enforce valid email addresses in the Notify field. Requests without valid Notify addresses will be rejected. The email requirements will be turned on in stages over the next week or so. So do the registration as soon as possible to avoid scripting failures. 4. We no longer support exports of uncompressed FITS files containing integer types. Most data held in the JSOC are compressed. Files stored in a compressed format will be exported in a compressed format, and files stored in an uncompressed format will be exported in an uncompressed format. See section 4.6 of the Guide to SDO Data Analysis if you need assistance handling compressed FITS files. ____________________________________________________________________ Release Notes for 7 August 2014 version of exportdata.html. Exportdata changes: Several changes that have been developing in exportdata2.html, the test version, were released today. 1. The order of processing steps was changed to allow rebinning after im_patch or maproj to allow quicker gaussian smoothing of extracted regions. A future change will enable user specification of the order of processing steps. 2. the size of the expected export as a result of processing is now calculated more accurately. It is passed to jsoc_fetch via the sizeratio parameter. It is used by jsoc_fetch to etimate if the request will exceed the per-export size limits. Formerly a 100x100 pixel cutout was treated as if it were a full image when estimating the export size. This limited the number of cutout frames available for any given export. 3. The processing functions are no now available for certain series such as hmi.sharp_720s and hmi.sharp_cea_720s. the former due to bugs in the processing code that do not presently allow multiple segments to be processed correctly or the need to prevent impossible actions such as changing the plate scale of sharp_cea data. Series will be added to or removed from the list as code development and erroneous usage cases accrue. 4. Some typos in im_patch and maproj parameters were fixed. Usage will be more robust. 5. Better help info for AIA Scale and Resize. Details as always can be seen at http://jsoc2.stanford.edu/cvs/JSOC/proj/export/webapps/ ____________________________________________________________________ Release Notes for 12 Jan 2014 versions of lookdata.html and exportdata.html. Contact Phil Scherrer if problems found in next few days. Lookdata 1. Change in the sorting and selction of keywords in the Series Content tab. The keywords listed in the Record Select tab drop down lists will now be sorted by the sort button on the Series Content page. This allows one to change the order of columns in the reported table of values and the order of values in the graphs if desired. Sorting reselects all keys os choose the sort option before downselecting keywords. These capabilities are most useful in the few data series with hundreds of keywords such as some of the vector field series. 2. RecordSet selctions passed via the URL can now include recordset specs as well as seriesname. Encode as if a command line had ds= rs= n= Exportdata 1. Changes in the interaction of options selection and need to press the "Check Params for Export" button. this button is now needed everytime before the "Submit Export Request" button. There will be fewer strange cases of a user change not being incorporated into the request. 2. The URL sent to JSOC is now visible via a checkbox beneath the Submit button. This will enable easier development of scripts to do repeated similar exports. See also "Script Driven" in the "DataAccess" tab on the JSOC page. 3. In the "im_patch" - image patch - processing option the various option fields are not reset to defaults when the RecordSet is changed. This allows e.g. picking a region from both AIA and HMI without needing to reenter the location and box sizes. New buttons are added to force reset to defaults and to force getting the default times to match the RecordSet query. Note that the times do change when changing RecordSets. This is a byproduct of changing the Cadence which is needed since HMI and AIA have differing basic cadence. 4. A new button is added at the end of the RecordSet line to pass the chosen RecordSet to lookdata. This can be useful for those who go directly to exportdata.html but then decide they want more information about the keywords perhaps to build a filename for the exported files that is easier to parse than the default. The lookdata call will be placed in a different browser tab/window and may replace the first lookdata window in your current session. 5. Default Method is now url instead of url-quick