-
Notifications
You must be signed in to change notification settings - Fork 31
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
MissingRfreeError: The following elements have no reference Rfree values #362
Comments
Hi @entropybit, Not all of the parameterisation protocols we published contain parameters for S and halogens only Hope this helps! |
Okay, after the changes in the other issue I was hopefully that this could work I tried the following:
which in the end produced this error:
I'll attach you a zip of the results folder again. Guess I'll also try out 5d and see if the same happens now. |
Hmh, no same error with 5d. Edit: Okay after just uninstalling openeye-toolkit it now seems to be working. (still running, we will see if it doesn't manage to produce some other errors ^^). But I find it a bit worrisome that qubekit stops if this package is available but the licencse is missing (at least I assume that is what causes it). You should probably build something in that catches |
Ok, @jthorton I got some new errors:
What I immediately notice is that thee is no qm_optimization subfolder, the 5d/5b protocols should still have that right ? |
Hi @jthorton,
I think this is the same error but if you think it helps I can also zip you one of those other result folders. |
Hi @entropybit, thanks for the report. For the hessian stage it seems to be an issue with gaussian calculation, in the zipped folder there is a gaussian.com file in the hessian folder which is generated by qubekit to run the calculation and a
|
Hey, I got the same error again after running it on our large memory node, so used the following specification:
1.2TB are apperently not enough if you are correct and this is a memory issue. Before I ran it with Best regards, PS: As before I have attached an zip of my according output folder. PPS: If this turns out to really be something about how the tools / algorithms work .... Any chance that we can run this as distributed computation ? |
Hey, I am not sure what the issue is with this then as the error message from gaussian is very cryptic! My only thought is that the optimisation works fine but the hessian fails and the only extra thing we do in the hessian stage is calculate the bond order. Can you try removing the bond order comands in the gaussian input file and run it manually to see if that works? (It would be strange if this is the issue as you reported being able to run a molecule all the way through before which should have included this step). Maybe also try removing parts of the input file/change the cores and memeory settings till you find a working combination? Lastly, Ill try and run this locally as well although I only have access to gaussian09 but if it is a memory issue I think I should see the same thing. |
Hey, I managed to run this exclusively on our 44 core node with 100GB of memory and it finished in around an hour, I used the input file from your zip folder and only changed the cores and memory lines so it might be something to do with the calculation setup. Did you have any luck running it manually? |
Thanks for that, I might take a bit longer with trying it out this time, just to let you know. But by next week I should have been able to do it. If it works: I assume I can simply continue then using --skip-stages or restart ? |
Okay, this is very weird. I did try it out with a batch job for running the gaussian file only.
and I get
I'll attach the gaussian.com file as well as log. The nodes have 96 cores and ~250GB so this should be enough... |
I think I found the problem, if I open the gaussian.com file in the first line it say %Mem 1200GB which of course none of our normal nodes can fulfill. How and from which parameters is the input number of cores and memory generated ? EDIT: Ok the 1200GB came from me running it on the large mem node, but it should have worked then, very weird indeed... |
Still don't understandt why the gaussian run didn't work before (maybe I really did something wrong with specifying to much memory but I don't think so). However when restarting I get errors again ^^'
I did restart like this after doing a cd to the QUBEKIT_... folder:
@jthorton is there something wrong with this ? |
@entropybit, it's been long since you asked your question, but I believe that the problem with Gaussian was indeed with memory You requested 2500 MB per CPU, which is 240 GB for your 96 nodes, but in Gaussian you set As for the QUBEKit part, you were trying to restart Consider trying to understand, how much memory Gaussian needs to calculate your molecule, and then specify the value for QUBEKit @jthorton, I believe that it might be useful in some scenarios to be able to run QUBEKit starting from already computed log/fchk file so it won't need to perform calculations itself |
Hi,
with the following molecule:
I get the error message
which I assume is becaue of the S in the molecule ?
Is this chanceless or do you have any pointers on how I could proceed to get to an parametrization ?
Best regards,
Ben
The text was updated successfully, but these errors were encountered: