-
Notifications
You must be signed in to change notification settings - Fork 0
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
Need more details on the jobs #1
Comments
M06-2X/6-311+g(2df,2p) or better please |
Or the 6-311+g** basis set if the 6-311+g(2df,2p) basis set is unavailable |
I'll try out a few of these calculations to benchmark, but compared to the 6480 saddle point searches I'm already running, your tests are using a more expensive level of theory (I'm using B3LYP/6-31G) and have some larger molecules (my biggest molecules have 8 heavy atoms). There's a chance that your tests will scale better on KNL though, since they're bigger. Are all of these tests closed-shell? If not, how can I tell which are open shell and which are closed-shell? |
I believe they're all H-abstraction, so will all have a radical involved. |
Well, I found at least one geometry where NWChem said a multiplicity of 2 was invalid. I suppose I can just count the number of hydrogens and determine the multiplicity that way. |
Since all of the reactions are H-abstractions, does that mean systems with an even number of electrons should have a multiplicity of 3? |
@nateharms are some of them abstracting H from a radical, and thus have an even number of electrons overall? (And did you include abstraction by triplet O₂?) |
|
Can you give me some advice on how to determine which multiplicity to use for which geometries? |
Would it be easier if I provided a text file containing a dictionary of files and their corresponding multiplicity? |
If you can provide the multiplicities for each geometry, that would certainly be helpful. |
Okay, a text file has been added with corresponding file names and their multiplicities |
These calculations are going to take a lot of time. Unfortunately, NWChem's DFT routines (LCAO, not plane waves) are not at all optimized for many-core systems like Theta. Since the calculations in my test set are all fairly inexpensive, this wasn't a big problem, but testing M06-2X/6-311++G** I am seeing calculations take 10 minutes per single point on 2 nodes (128 cores). It will be difficult to do a meaningful amount of work in the span of a single job, given the very low time limits for jobs on Theta. My priority currently is getting my own test set completed. Once they are done, I can start working on these systems. I think it will be a lot easier to first optimize the saddle points using a less expensive level of theory, then re-optimize at M06-2X/6-311++G** -- possibly on a different cluster. |
Gotcha, how about run M06-2X/6-31G? Will that be less expensive? Either that or run it whatever you think seems suitable, we can re-optimize them later. Thanks for the help! |
I'll test a couple of different things to see if I can find something reasonably fast that is close to your desired settings. M06-2X being a meta-GGA also adds a nontrivial cost, particularly in terms of SCF convergence (Truhlar's functionals have notorious convergence difficulties). |
I've started running these calculations now. I'm going to start by optimizing the saddle points with B3LYP/6-31G, then refining with M06-2X/6-311+G**. I noticed there is a |
@ehermes an updated |
I'm having trouble parsing this file automatically. It seems like there's a strange character on line 2859. |
Hmmm... I'm not sure why it isn't working... I'm able to read in the file easily. But I'll try writing a new file and seeing if that helps |
@ehermes a file called |
Some seem to be missing: import pandas
import os
df = pandas.read_csv('mults.csv')
for dirpath, dirnames, filenames in os.walk('.'):
if './' not in dirpath or '.git' in dirpath: continue
_,d = dirpath.split('/')
for f in filenames:
if '.xyz' not in f:
continue
p = os.path.join(d,f)
found = (sum(df.file_name==p))
if found !=1:
print(p, found)
|
@rwest thanks for the catch, should be good now 👍 |
@ehermes just posted via the sandia gitlab thing:
The text was updated successfully, but these errors were encountered: