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
There is no information about whether engines cannot take in case sensitive strings, in particular condition labels. (reported by @lipnikov)
Neither CrunchFlow nor PFLOTRAN are case-sensitive for condition labels. The problem with CrunchFlow was that I did not implement the appropriate function in the Crunchflow alquimia interface. Technically, a bug. Fixed in pull request (closes #68)
We need to add a new functionality variable that tells the user whether one can pass driver-derived strings as case sensitive or not. Engine-derived strings may need to be assumed case-sensitive.
We need to decide how general this variable can be (task: go over every string that goes into Alquimia). At the very least, the variable will indicate whether condition%name is case-sensitive or not, e.g. "bool functionality%label_case_sensitive".
The text was updated successfully, but these errors were encountered:
There is no information about whether engines cannot take in case sensitive strings, in particular condition labels. (reported by @lipnikov)
Neither CrunchFlow nor PFLOTRAN are case-sensitive for condition labels. The problem with CrunchFlow was that I did not implement the appropriate function in the Crunchflow alquimia interface. Technically, a bug. Fixed in pull request (closes #68)
We need to add a new functionality variable that tells the user whether one can pass driver-derived strings as case sensitive or not. Engine-derived strings may need to be assumed case-sensitive.
We need to decide how general this variable can be (task: go over every string that goes into Alquimia). At the very least, the variable will indicate whether condition%name is case-sensitive or not, e.g. "bool functionality%label_case_sensitive".
The text was updated successfully, but these errors were encountered: