I have recently installed nco via my anaconda prompt. Everything seems to have downloaded and installed properly, except ncclimo (and ncremap), which just downloaded as a 'file' (no file extensions), as opposed to an executable. So when I input the command 'ncclimo' into the prompt, it says it's not recognised as a program or executable.
So I did the obvious thing and converted them into .exe files by changing the file extension. However, when I then enter the command 'ncclimo', it says it is not compatible with my (64-bit) version of Windows 10, claiming the .exe is 16-bit. I've tried going into settings>compatability>compatability mode> run this program in compataibility mode for Windows X, and that doesn't appear to help either.
I would really appreciate any advice on how to resolve this issue. Thanks.
Natasha
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ncclimo and ncremap are Bash scripts, more similar to Windows .bat than to .exe. I do not expect Bash scripts to work at all on Windows except if run in a shell that supports Bash. My understanding is the Windows does support a Ubuntu Bash terminal or something like, but I'm vague on the specifics, and do not have a Windows machine to test on. Anyhow, I suggest you look into that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks. I installed Debian, so I think I can theoretically use bash through anaconda. However when I do ' bash ncclimo' I get:
ncclimo: ERROR Unable to find NCO, ${nco_exe} =
ncclimo: HINT Carefully examine your environment setup (e.g., .bashrc) to avoid inadvertently overriding (with, e.g., conda-initialization) paths intended to be provided by an analysis-package environment (e.g., E3SM-Unified)
I'm not really sure why this is happening, I am actually using the E3SM-Unified environment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's a good step, I think. However, you may need to install the Linux Anaconda in your home directory on Debian. I'm just not sure how Debian works on Windows. I suspect it gives you a /usr/bin directory and other hallmarks of Linux, and does not pay much attention to the Windows binaries in your Windows home directory. Can anyone verify this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there,
I have recently installed nco via my anaconda prompt. Everything seems to have downloaded and installed properly, except ncclimo (and ncremap), which just downloaded as a 'file' (no file extensions), as opposed to an executable. So when I input the command 'ncclimo' into the prompt, it says it's not recognised as a program or executable.
So I did the obvious thing and converted them into .exe files by changing the file extension. However, when I then enter the command 'ncclimo', it says it is not compatible with my (64-bit) version of Windows 10, claiming the .exe is 16-bit. I've tried going into settings>compatability>compatability mode> run this program in compataibility mode for Windows X, and that doesn't appear to help either.
I would really appreciate any advice on how to resolve this issue. Thanks.
Natasha
ncclimoandncremapare Bash scripts, more similar to Windows.batthan to.exe. I do not expect Bash scripts to work at all on Windows except if run in a shell that supports Bash. My understanding is the Windows does support a Ubuntu Bash terminal or something like, but I'm vague on the specifics, and do not have a Windows machine to test on. Anyhow, I suggest you look into that.Thanks. I installed Debian, so I think I can theoretically use bash through anaconda. However when I do ' bash ncclimo' I get:
ncclimo: ERROR Unable to find NCO, ${nco_exe} =
ncclimo: HINT Carefully examine your environment setup (e.g., .bashrc) to avoid inadvertently overriding (with, e.g., conda-initialization) paths intended to be provided by an analysis-package environment (e.g., E3SM-Unified)
I'm not really sure why this is happening, I am actually using the E3SM-Unified environment.
That's a good step, I think. However, you may need to install the Linux Anaconda in your home directory on Debian. I'm just not sure how Debian works on Windows. I suspect it gives you a /usr/bin directory and other hallmarks of Linux, and does not pay much attention to the Windows binaries in your Windows home directory. Can anyone verify this?