-
Notifications
You must be signed in to change notification settings - Fork 330
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
Exception: Unknown Error code xxxx xxx using reticulate with python and nrel-pysam #1369
Comments
Hi, thank you for reporting. I can reproduce locally. This issue will require some investigation. In a debugger I was able to trace the error to this function. Specifically from the The
This looks like a tricky issue requiring investigation. I'm happy to patch what's needed in reticulate to make this work, but any help with investigation and diagnosing the root cause would be appreciated. |
Update here, this appears NOT to be an issue on windows. I conducted a similar test using python 3.11.3 and R 4.3.0 on a windows 10 vm:
|
Cross-listed this issue on NREL/pysam: |
I'm attempting to use reticulate within R to interface with NREL's SAM library via PySAM (nrel-pysam on pypi); however, I cannot interface with any of the compute modules, resulting in an error that says simply:
Though the exact code changes each time I run it, making me think it has something to do with RAM addressing.
Here's an example of what I've tried, using AlmaLinux 9.1 (a clean, fresh install), which comes with python version 3.9:
a full traceback yields something that looks like
I have attempted to do more or less the following on a variety of OSes (Fedora 38, Ubuntu 20.04, AlmaLinux 9.1 to name a fiew) with a variety of python versions (3.8 - 3.11), I've tried both the CRAN version of reticulate and the current (as of 2023-05-08) main branch version on Github, I've installed nrel-pysam with pip and with conda (not having both at the same time of course), have only ever seen this error message. Here's a sample session info:
Happy to include any/all other information as necessary.
The text was updated successfully, but these errors were encountered: