-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too similar file names on macos #147
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
Thanks for the additional input. Searching for this error message, I came across this suggestion to set up a new, case-sensitive volume on macos that can host the existing code. |
There's also a git config variable that we could play around with to see if some setting satisfies our needs locally. |
This is an unfortunate consequence of the fact that the MESSAGE GAMS code uses both a parameter named The model data snapshot published on Zenodo contains data for both, and so the 'exploded' or 'unpacked' version of that file stored in this repo has both. AFAIK, the variable |
Hi all, thanks for addressing this. I think I'm the source of the issue because I'm a macOS user 🥲 Like @glatterf42 said, my computer does not allow me to have files with the same spelling/name (even if they have different capitalizations). I've tried to deal with this a few times while working on my PR in |
I think we can leave this open since the merged mitigation PR is likely just a temporary fix; however, for the time being, this issue should be solved on main :) |
As pointed out by @measrainsey last year and now by @ravitby, this repository currently contains both demand.csv.gz and DEMAND.csv.gz in
data/test/MESSAGEix-GLOBIOM_1.1_R11_no-policy_baseline
. This seems to cause git conflicts on macos systems as they don't distinguish between capitalized and non-capitalized file names.I'm not immediately sure how we can remedy this, possibly by renaming a file, but I'm not sure if the exact names are somehow important (e.g., correspond to some model parameter and need to be exactly the way they are for the file to be found).
The text was updated successfully, but these errors were encountered: