Skip to content
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

typo prevents writing input files #2531

Open
sevyharris opened this issue Aug 21, 2023 · 4 comments · May be fixed by #2532
Open

typo prevents writing input files #2531

sevyharris opened this issue Aug 21, 2023 · 4 comments · May be fixed by #2532
Assignees

Comments

@sevyharris
Copy link
Contributor

Bug Description

I'm trying to read, edit, and write RMG input files using the rmgpy.rmg.input module, but the writing portion gives me the following error:

Traceback (most recent call last):
  File "edit_input_file.py", line 14, in <module>
    rmgpy.rmg.input.save_input_file(new_input_file, rmg0)
  File "/home/moon/rmg/RMG-Py/rmgpy/rmg/input.py", line 1665, in save_input_file
    if rmg.surfaceSiteDenisty or rmg.binding_energies:
AttributeError: 'RMG' object has no attribute 'surfaceSiteDenisty'

There's obviously the misspelled word. I think the attribute is supposed to be surface_site_density.
I'm running into some other issues with this module (can't write files with a temperature range, using this module is painfully slow because of the hidden and unnecessary Julia dependency), and will try adding a few unit tests to cover my tracks here.

How To Reproduce

This is my Python script for reproducing the error (input.py is the superminimal example):

import os
import rmgpy.rmg.input
import rmgpy.rmg.main

# reset with  cp ~/rmg/RMG-Py/examples/rmg/superminimal/input.py .
my_input_file = os.path.join('input.py')

rmg0 = rmgpy.rmg.main.RMG()
rmgpy.rmg.input.read_input_file(my_input_file, rmg0)

print('read RMG input file')

new_input_file = 'new_input.py'
rmgpy.rmg.input.save_input_file(new_input_file, rmg0)
print('wrote RMG input file')

Expected Behavior

It'd be really convenient to be able to use the RMG API to edit input files. I expected to be able to read and write the simplest input file without any errors.

Installation Information

Describe your installation method and system information.

  • OS (include version if known): WSL: Ubuntu 20.04.1 LTS
  • Installation method: source
  • RMG version information:
    • RMG-Py: 3.2.0-112-g8ba4c0dd3
    • RMG-database: 3.1.0-618-gb7ff16364
Copy link

This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days.

@github-actions github-actions bot added the stale stale issue/PR as determined by actions bot label Nov 20, 2023
@github-actions github-actions bot added the abandoned abandoned issue/PR as determined by actions bot label Dec 21, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 21, 2023
@sevyharris sevyharris reopened this May 30, 2024
@sevyharris sevyharris removed stale stale issue/PR as determined by actions bot abandoned abandoned issue/PR as determined by actions bot labels May 30, 2024
@JacksonBurns
Copy link
Contributor

I'm running into some other issues with this module (can't write files with a temperature range, using this module is painfully slow because of the hidden and unnecessary Julia dependency), and will try adding a few unit tests to cover my tracks here.

We are getting close to merging #2631 which would resolve at least the slow part! Might want to rebase your ongoing PR after we merge that one to simplify development.

@sevyharris
Copy link
Contributor Author

I'm running into some other issues with this module (can't write files with a temperature range, using this module is painfully slow because of the hidden and unnecessary Julia dependency), and will try adding a few unit tests to cover my tracks here.

We are getting close to merging #2631 which would resolve at least the slow part! Might want to rebase your ongoing PR after we merge that one to simplify development.

That's excellent news!

Copy link

This issue is being automatically marked as stale because it has not received any interaction in the last 90 days. Please leave a comment if this is still a relevant issue, otherwise it will automatically be closed in 30 days.

@github-actions github-actions bot added the stale stale issue/PR as determined by actions bot label Sep 11, 2024
@sevyharris sevyharris removed the stale stale issue/PR as determined by actions bot label Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants