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
Ever since GOCART2G was introduced it is no longer possible for various reasons to selectively disable individual components as there are data dependencies between the components. For example, if you disable dust, something in nitrates was relying on dust having been run. In the main GOCART2G grid comp there's an assumption there's a nitrate instance. The list goes on.
In the old GOCART you would disable any component one wished without causing failure. This made debugging vastly easier as individual components could selectively be disable for any number of reasons that one might want to do this without restrictions. This is a HUGE hinderance for debugging purposes and incredibly frustrating as a first responder for GEOS when problems occur.
The text was updated successfully, but these errors were encountered:
Ever since GOCART2G was introduced it is no longer possible for various reasons to selectively disable individual components as there are data dependencies between the components. For example, if you disable dust, something in nitrates was relying on dust having been run. In the main GOCART2G grid comp there's an assumption there's a nitrate instance. The list goes on.
In the old GOCART you would disable any component one wished without causing failure. This made debugging vastly easier as individual components could selectively be disable for any number of reasons that one might want to do this without restrictions. This is a HUGE hinderance for debugging purposes and incredibly frustrating as a first responder for GEOS when problems occur.
The text was updated successfully, but these errors were encountered: