-
Notifications
You must be signed in to change notification settings - Fork 13
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
process_solution not working with PLEXOS v8.2R01 #66
Comments
Not sure it's advisable, but I turned off the correct_length() check and now got this error: Error: Problem reading interval binary data (reached end of file). 720 values requested, 390 returned. This is likely a bug in rplexos. Please report it.
|
I had this same issue, but this repository hasn't been pushed to since 2017 so...... Please post here if you find a solution though! |
Hey @jennielu92 and @samjohnson12, we encountered the same issue and I'm not sure what the package's original developer, @eibanez is up to these days, so I cloned this repo and rewrote its query functions to query HDF5 databases created in Julia using NREL/H5PLEXOS.jl instead of SQLite databases. This allows us to a) access solutions created with PLEXOS v8.2 and higher and b) access the same databases from R as we do from Python (where we use h5plexos). If you want to check it out and give it a shot, it's the |
Just a note that it's still under development, but we've successfully been using it for a few projects at NREL for the past six months or so. |
Thanks @mattirish, I was able to find a fix by rolling back to an earlier version of PLEXOS but I'll pass this on to a colleague who is still using PLEXOS. Glad to hear there's an updated solution! |
Hi @mattirish, I'll be trying this out soon! Thanks for the heads up on this. |
process_solution does not seem to work with the newest version of PLEXOS, v8.2R01. I get this error:
Error: $ operator not defined for this S4 class
In debugging with the source code, it seems like it originates in the function correct_length() although I'm not sure if that's the only issue, or just the first one.
The text was updated successfully, but these errors were encountered: