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
Are lines like this: for k in ['CPL', 'GLC', 'WAV', 'LND', 'ROF', 'ICE', 'ATM', 'OCN']:
appropriate in get_timing.py? They prevent get_timing from automatically picking up new component types (e.g., ESP).
The text was updated successfully, but these errors were encountered:
Compclasses cleanup
Get rid of hard coded comp_class settings and use get_values instead.
Punting on NCR test - it's broken, was broken before this PR will open a ticket.
Test suite: scripts_regression_tests.py, hand tests of PET and PEM tests. PEM.f19_g16.F1850.yellowstone_intel
PET.f19_g16.F1850.yellowstone_intel
Test baseline:
Test namelist changes:
Test status: bit for bit
Fixes#1170
User interface changes?:
Code review: gold2718
Are lines like this:
for k in ['CPL', 'GLC', 'WAV', 'LND', 'ROF', 'ICE', 'ATM', 'OCN']:
appropriate in get_timing.py? They prevent get_timing from automatically picking up new component types (e.g., ESP).
The text was updated successfully, but these errors were encountered: