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
Add the ability to run forge-py even when useEcs (running in fargate) is set to true, and also add check for granule size to run fargate or lambda for forge, forge-py and tig
#41
Open
jamesfwood opened this issue
Dec 20, 2024
· 0 comments
This collection COWVR_STPH8_L1_TSDR_V10.0 has useEcs set to true in cumulus-configurations but it is set to use forge-py in its forge config and is failing to generate footprints. Please fix this.
Also add the check like in dmrpp, to check for granule size and run fargate on large granules. Add this for forge, forge-py, and tig workflows
Also make sure the workflows in cumulus and backfill tool match.
The text was updated successfully, but these errors were encountered:
jamesfwood
changed the title
Add the ability to run forge-py even when useEcs (running in fargate) is set to true
Add the ability to run forge-py even when useEcs (running in fargate) is set to true, and also add check for granule size to run fargate or lambda
Dec 20, 2024
jamesfwood
changed the title
Add the ability to run forge-py even when useEcs (running in fargate) is set to true, and also add check for granule size to run fargate or lambda
Add the ability to run forge-py even when useEcs (running in fargate) is set to true, and also add check for granule size to run fargate or lambda for forge and tig
Dec 20, 2024
jamesfwood
changed the title
Add the ability to run forge-py even when useEcs (running in fargate) is set to true, and also add check for granule size to run fargate or lambda for forge and tig
Add the ability to run forge-py even when useEcs (running in fargate) is set to true, and also add check for granule size to run fargate or lambda for forge, forge-py and tig
Dec 20, 2024
This collection COWVR_STPH8_L1_TSDR_V10.0 has useEcs set to true in cumulus-configurations but it is set to use forge-py in its forge config and is failing to generate footprints. Please fix this.
Also add the check like in dmrpp, to check for granule size and run fargate on large granules. Add this for forge, forge-py, and tig workflows
Also make sure the workflows in cumulus and backfill tool match.
The text was updated successfully, but these errors were encountered: