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
It might be nice if we could arrange our repos such that we can more easily automate things like timings, as well as form reliable driver-independent instructions so that developers can pick up the drivers and use them to develop stuff like lazy eval.
This current repo has a nice internal structure. Can we make this repo the template on how drivers should be arranged (specific to CEESD official drivers), and then add this current driver as the first example? Something like illinois-ceesd/experiments/y1/nozzle or i-c/exp/y1-nozzle?
The text was updated successfully, but these errors were encountered:
It might be nice if we could arrange our repos such that we can more easily automate things like timings, as well as form reliable driver-independent instructions so that developers can pick up the drivers and use them to develop stuff like lazy eval.
This current repo has a nice internal structure. Can we make this repo the template on how drivers should be arranged (specific to CEESD official drivers), and then add this current driver as the first example? Something like illinois-ceesd/experiments/y1/nozzle or i-c/exp/y1-nozzle?
The text was updated successfully, but these errors were encountered: