-
Notifications
You must be signed in to change notification settings - Fork 11
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
allow SSMSE to work with SS3.30.21 #215
Comments
i wondering to know if do you have some news about this issue. maybe i pressing a little bit. |
I made progress on this awhile ago but reached a road block with one of the SSMSE functions that I had to pass on to @k-doering-NOAA to see if she could sort out the issue. I hope 🙏 that will be the last step in getting SSMSE working with SS3 v 3.30.21. |
Cool. i guess is a tricky issue. thanks anyway for the progress. I will be with an eye on. |
im trying to run the example with 3.30.18 v but this message appear when run what mean? |
I ran the example in the README.md on both my local windows machine and on a linux machine using GitHub codespaces but I didn't run into that message. Maybe it's a folder permission issue on your computer. |
Could it be an issue with the executable? Do I need to manually place it in a specific directory or the function generates it? |
SSMSE uses the executable that's in the package.
too see if that does anything. |
@k-doering-NOAA could you help with this issue before you go on leave? There is just one test (test-interim) that seems to not pass and I'm at a loss as to why. See failed action here with details on failed testthat. |
@e-perl-NOAA is working on making SSMSE compatible with SS3.30.21. This is because a user needs a feature that is only available in 3.30.21 and newer.
SSMSE will continue to work and will be distributed with the 3.30.18 binaries. However, users will be able to swap in the 3.30.21 exes instead, if they would like, and should expect SSMSE to work once this issue is completed.
@e-perl-NOAA feel free to add to this/edit if I missed something or got something wrong!
The text was updated successfully, but these errors were encountered: