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
Currently, the coupler summary table takes in run names from the command line and uses these to find the correct simulation output files to read in data from. It would be cleaner to take in one job/run ID, and use this to construct the correct run names inside the table script. This can also be used to get the resolution and dt of the simulation, instead of hardcoding them in the table
Note that in #776, the job ID will be passed into buildkite runs via the command line. This may change how we want to implement the table change, so we should wait until 776 is addressed before implementing this.
The text was updated successfully, but these errors were encountered:
Currently, the coupler summary table takes in run names from the command line and uses these to find the correct simulation output files to read in data from. It would be cleaner to take in one job/run ID, and use this to construct the correct run names inside the table script. This can also be used to get the resolution and dt of the simulation, instead of hardcoding them in the table
Note that in #776, the job ID will be passed into buildkite runs via the command line. This may change how we want to implement the table change, so we should wait until 776 is addressed before implementing this.
The text was updated successfully, but these errors were encountered: