You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to recent changes on the JWST and/or MAST end, there are two potential issues with the data being returned by our JWST_get_spec function, described below. More detail is in #360, including input from MAST folks. The result is that our notebook gets different JWST data than it used to for the same targets. A scientist should check whether the current results are appropriate and make adjustments if needed.
Some of the files we were previously retrieving no longer exist in the archive due to JWST reprocessing ("which can cause some source extractions to no longer exist"). For now, we've relaxed our requirements to include calibration level 2 data (in addition to levels 3 and 4) in order to get results back for some of our targets.
Some of the query results have a calibration level of "-1" (remove the calib_level filter to see this). The JWST doc Processing Levels and Product Stages says "-1 = Planned, but not yet executed". That makes me wonder if it's related to the reprocessing and indicates that those results are forthcoming. But, I don't know whether these "-1" values are new or whether it's an issue we even need to address.
Also, this function now takes about 14 min (on Fornax), while all the other archive calls in the notebook take about 3 min total. I don't know how long this was taking before the recent changes. If this is unexpectedly long, maybe one option is to change our target sample?
The text was updated successfully, but these errors were encountered:
It sounds to me like you have done a good job with the tech review of this code, and maybe it is time to ask some of the JWST experts on the Fornax team for help with these questions as well as the timeout error in #339
Due to recent changes on the JWST and/or MAST end, there are two potential issues with the data being returned by our
JWST_get_spec
function, described below. More detail is in #360, including input from MAST folks. The result is that our notebook gets different JWST data than it used to for the same targets. A scientist should check whether the current results are appropriate and make adjustments if needed.Some of the files we were previously retrieving no longer exist in the archive due to JWST reprocessing ("which can cause some source extractions to no longer exist"). For now, we've relaxed our requirements to include calibration level 2 data (in addition to levels 3 and 4) in order to get results back for some of our targets.
Some of the query results have a calibration level of "-1" (remove the
calib_level
filter to see this). The JWST doc Processing Levels and Product Stages says "-1 = Planned, but not yet executed". That makes me wonder if it's related to the reprocessing and indicates that those results are forthcoming. But, I don't know whether these "-1" values are new or whether it's an issue we even need to address.Also, this function now takes about 14 min (on Fornax), while all the other archive calls in the notebook take about 3 min total. I don't know how long this was taking before the recent changes. If this is unexpectedly long, maybe one option is to change our target sample?
The text was updated successfully, but these errors were encountered: