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
The benefit of 1_core_per_node_2_nodes is that it's crystal clear, but it is looooooong.
Would cpn make sense, so 1_cpn_2_nodes?
Or maybe both if we think that cpn may be too cryptic for some, with 1_cpn_2_nodes as alias for 1_core_per_node_2_nodes?
hm, adding aliases like this is annoying when filtering a subset of scales.
the alternative would be to use something else than strings for the keys, but i think it's not worth it,
so i'll just remove the aliases and keep the _cpn_ strings
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.