Would need same functionality as Bronx output.stager but uses yaml as config instead of c-shell variables (what output? where does it get staged?) - stages output .... - variables associated with outputStager: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/runscript.template.main?ref_type=heads#L98-115 - fre.properties: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/fre.properties?ref_type=heads#L161-176 - outputStager submit Options: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/runscript.template.main?ref_type=heads#L274-275 - setting outputStager alias: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/runscript.template.main?ref_type=heads#L301-303 - Used: - asciiArgFile usage: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/runscript.template.main?ref_type=heads#L1137 - restartArgFile usage: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/runscript.template.main?ref_type=heads#L1339 - historyargFile usage: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/runscript.template.main?ref_type=heads#L1673 - set historyResult: https://gitlab.gfdl.noaa.gov/fre-legacy/fre-commands/-/blob/main/site/ncrc5/runscript.template.main?ref_type=heads#L1727
Would need same functionality as Bronx output.stager but uses yaml as config instead of c-shell variables (what output? where does it get staged?)