How embarrassing!!!
Thank you, Peter!!
Search found 10 matches
- Tue Sep 22, 2020 12:48 am
- Forum: OpenMM
- Topic: setParameter leads to AttributeError
- Replies: 3
- Views: 77
- Sun Sep 20, 2020 7:47 am
- Forum: OpenMM
- Topic: setParameter leads to AttributeError
- Replies: 3
- Views: 77
Re: setParameter leads to AttributeError
An add-on: This error seems related to the use of set.Parameter() in the context of a Simulation object. The following works just fine: # Build system system = psf.createSystem(params, nonbondedMethod=inputs.coulomb, nonbondedCutoff=inputs.r_off*nanometers, constraints=inputs.cons, ewaldErrorToleran...
- Sun Sep 20, 2020 7:20 am
- Forum: OpenMM
- Topic: setParameter leads to AttributeError
- Replies: 3
- Views: 77
setParameter leads to AttributeError
Hi, all, I am experiencing a problem with OpenMM, version -7.4.2-py37_cuda101_rc1. I tested the platforms CPU and CUDA, both have the same issue: I want to update a global parameter with context.setParamter() which fails with the following error: Traceback (most recent call last): File "openmm_run.p...
- Thu Nov 05, 2015 1:18 am
- Forum: OpenMM
- Topic: GBn2 & nonpolar solvation terms
- Replies: 2
- Views: 1038
Re: GBn2 & nonpolar solvation terms
Thanks, Peter, that was very helpful!
Best,
Martin
Best,
Martin
- Tue Oct 20, 2015 8:07 am
- Forum: OpenMM
- Topic: GBn2 & nonpolar solvation terms
- Replies: 2
- Views: 1038
GBn2 & nonpolar solvation terms
Hi everybody, I would have a question regarding OpenMM's implementation of the implicit solvation model GBn2. Are there any terms for the nonpolar solvation (proportional to the SASA)? In their article preseneting GBn2 [ J. Chem. Theory Comput., 2013, 9 (4), pp 2020–2034; DOI: 10.1021/ct3010485 ] Ca...
- Tue Mar 31, 2015 9:57 am
- Forum: OpenMM
- Topic: GBSA using the python wrapper
- Replies: 5
- Views: 236
Re: GBSA using the python wrapper
Hi, Peter,
OK, this is clear now!
Thanks for the speedy reply,
Martin
OK, this is clear now!
Thanks for the speedy reply,
Martin
- Tue Mar 31, 2015 7:55 am
- Forum: OpenMM
- Topic: GBSA using the python wrapper
- Replies: 5
- Views: 236
Re: GBSA using the python wrapper
Hi, Peter, If I understand your post correctly, using amber99_obc.xml (with forcefield object) and the argument implicitSolvent=OBC2 (with AmberPrmtopFile) should give the same solvation model. In the User Guid documentation of OpenMM 6.2, it says, however, that *_obc.xml uses specialized GBSA-Param...
- Tue Feb 11, 2014 6:10 am
- Forum: OpenMM
- Topic: CudaDevice is always 0
- Replies: 10
- Views: 467
Re: CudaDevice is always 0
Hi, Lee-Ping,
Yes, indeed, the proprties wer4e not added in the Simulation object, how embarrassing!
It's now working fine.
Best,
Martin
Yes, indeed, the proprties wer4e not added in the Simulation object, how embarrassing!
It's now working fine.
Best,
Martin
- Mon Jan 27, 2014 1:12 am
- Forum: OpenMM
- Topic: CudaDevice is always 0
- Replies: 10
- Views: 467
Re: CudaDevice is always 0
Hi, Peter, Thanks for your response! Please find below the information you asked for. Best, Martin Here is the Python code (it is based on the test case simulateAmber.py): *** from simtk.openmm.app import * from simtk.openmm import * from simtk.unit import * from sys import stdout platform = Platfor...
- Fri Jan 24, 2014 11:28 am
- Forum: OpenMM
- Topic: CudaDevice is always 0
- Replies: 10
- Views: 467
Re: CudaDevice is always 0
Hi, Peter,
I have actually the same problem; I have two GPU cards but whatever I specify with
properties = {'CudaDeviceIndex': 'X'}
with X=0,1
has no impact on which GPU card OpenMM is executed; it's always the first card ('0').
Best,
Martin
I have actually the same problem; I have two GPU cards but whatever I specify with
properties = {'CudaDeviceIndex': 'X'}
with X=0,1
has no impact on which GPU card OpenMM is executed; it's always the first card ('0').
Best,
Martin