Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test run on more program ids with new hst pipeline under hst dir #76

Merged

Conversation

juzen2003
Copy link
Collaborator

…inform

the user that pipeline stops if pipeline dir exists and we don't proceed
with the next pipeline task.
avaible, if there is no description, the target description tag won't
show up in the newly created target label.
 the YYYY_MM_DD_HH_MM_SS_PATTERN for the cases like 5217 with some files
 having IRAF-TLM value "2010-02-17T16:49:27".
…pport.py

when trying to figure out the filter name.
remove the undefined function call (citation_information_from_pro)
error and keep the scidata variable to None (line 616-619 in
product_labels/__init__.py)
…nning

HST pipeline tasks
- Add requirements.txt for setup
#65)
- In product_labels/__init__.py (line 489-494, 505-510), remove ipppssoot
that doesn't have trl timetags from info_by_ipppssoot & info_by_basename
to bypass the raise error and continue to run the rest of the pipeline.
so that they can be shared across multiple Popen subprocess.
- In task_queue_db.py (line 56-78), define the schema of SubprocessList
table.
- In task_queue_db.py (line 268-304), create functions of operations for
SubprocessList table.
- In __init__.py (line 157-196), replace actions on SUBPROCESS_LIST with
different operations for SubprocessList table to fetch/update/delete all
the subprocesses.
previous task if the next task is to be executed at the end of previous
task.
- Make sure subprocess list of a proposal id is clear when there is an
error raised for that specific proposal id.
- Properly remove the subprocess of from db after each task is done.
update-hst-visit, we will wait until all the visits have completed before
queueing finalize-hst-bundle
- Make sure when we walked through all the downloaded files from MAST in
the staging folder and move them over to the bundles folder, we will
remove the organize files in the staging folder.
@juzen2003
Copy link
Collaborator Author

  • Fixed some errors caused by validator.

Modifications:

  • In PRODUCT_LABEL.xml
    • Change hst:moving_target_keyword to hst:moving_target_keywords
    • Remove attribute nilReason in hst:gain_setting tag (attribute is not allowed)
    • Remove attribute unit in hst:plate_scale tag (attribute is not allowed)
    • Remove attribute nilReason in hst:spectral_resolution tag (attribute is not allowed)
    • Remove attribute nilReason in hst:center_filter_wavelength tag (attribute is not allowed)
    • Remove attribute nilReason in hst:bandwidth tag (attribute is not allowed)
    • Add unit="byte" to record_length, field_location, and field_location tags
  • In hst_dictionary_support.py
    • Change hst:observation_type from SPECTROSCOPIC back to SPECTROGRAPHIC
    • Change Array_1D to Array
  • In PRODUCT_LABEL.xml
    • Change File_Area to File_Area_Ancillary tag if processing level is "Ancillary"
  • In all labels templates, keep logical_identifier tag and its content in one line to avoid validator complaining about the unexpected carriage returns

Issues that needs to be reviewed/discussed:

  • hst:gain_setting, hst:spectral_resolution, hst:center_filter_wavelength, and hst:bandwidth values need to match this pattern r'(\+|-)?([0-9]+(\.[0-9]*)?|\.[0-9]+)([Ee](\+|-)?[0-9]+)?|[^aFIN,]* ', what should we put if it's not applicable? Remove the tag? (empty string is not a valid value)
  • No child element allowed for these tags" hst:visit_id & hst:Processing_Parameters
  • For hst:observation_type, it must exists, and the validator requires the value to be one of these: 'IMAGING', 'SPECTROGRAPHIC', 'TIME-SERIES', so 'UNK' will fail the validator.
  • For data class, these are the available values: {Array, Array_2D, Array_2D_Image, Array_2D_Map, Array_2D_Spectrum, Array_3D, Array_3D_Image, Array_3D_Movie, Array_3D_Spectrum, Checksum_Manifest, Encoded_Header, Encoded_Image, Header, Stream_Text, Table_Binary, Table_Character, Table_Delimited}. Should we modify DATA_CLASS_TO_NOUN in hdu_data_descriptions.py? What value should we put for Array_1D_Spectrum?

@juzen2003
Copy link
Collaborator Author

juzen2003 commented Jan 22, 2024

Current changes: (updates after 1/19/24 meeting)

  • In PRODUCT_LABEL.xml
    • Change hst:moving_target_keyword to hst:moving_target_keywords
    • Add unit="byte" to record_length, field_location, and field_location tags
  • In hst_dictionary_support.py
    • Change hst:observation_type value SPECTROSCOPIC to SPECTROGRAPHIC
    • Change File_Area to File_Area_Ancillary tag if processing level is "Ancillary"
  • In all labels templates, keep logical_identifier tag and its content in one line to avoid validator complaining about the unexpected carriage returns
  • All other changes made in previous comment except the above listed ones are reverted.

Pending items:

  • Get HST dicitonary definition update

- Remove unused SCHEMAS & SCHEMATRONS
- Remove unit attribute in the hst:plate_scale tag, will put it back later.
label_hst_context_directory function in finalize_context.py
change it back to 'Array_1D_Spectrum' once DDWG has an update.
<Observing_System> in the bundle, product collection, and product label
templates.
tag content under <Identification_Area> tag to <Context_Area>.<comment>
will have value_data_type for hst:moving_target_description changed
from ASCII_Short_String_Collapsed to ASCII_String
@juzen2003
Copy link
Collaborator Author

Details of the new updates in #56 (comments on 06/17/24)

@matthewtiscareno
Copy link
Collaborator

Details of the new updates in #56 (comments on 06/17/24)

Yes, those look good. So do all the tests pass now?

of parsing the name tag using the removed get_clean_target_text function
files for different proposal ids. This will avoid failure caused by
multiple bundles trying to update tmp-context-products.json at the same
time when running the validator.
@juzen2003
Copy link
Collaborator Author

06/21/24 updates:
When creating the target label that doesn't exist in https://pds.nasa.gov/data/pds4/context-pds4/target/ , obtain the correct type and name from lid for the target label.

@juzen2003 juzen2003 merged commit 96b683e into main Jun 21, 2024
@juzen2003 juzen2003 deleted the test_run_on_more_program_ids_with_new_hst_pipeline_under_HST_dir branch June 21, 2024 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants