SimTK: OpenMM: [#1505] Cuda board not cleared after OpenMM exception is thrown

Share
Follow	Project Follow publicly Follow privately Unfollow See followers (63) List Map More info

Trackers

Date:
2011-08-02 23:13

Priority:
3

State:
Open

Submitted by:
Mark Friedrichs (friedrim)

Assigned to:
Mark Friedrichs (friedrim)

Resolution:
none

Summary:
Cuda board not cleared after OpenMM exception is thrown

Detailed description
When running PyOpenMM if an OpenMM exception is thrown while initializing a Cuda context, then the next time a Cuda context is created, the program dies during initialization of the board w/ the error message: Cuda Error setting device flags setting the device when a process is active is not allowed. This suggests the board has not been marked as being inactive. This behavior was first observed by John Chodera on a Cuda MacBook Pro; it was reproduced on the SIMBIOS cluster machine t0.
When running PyOpenMM if an OpenMM exception is thrown while initializing a Cuda context, then the next time a Cuda context is created, the program dies during initialization of the board w/ the error message: Cuda Error setting device flags setting the device when a process is active is not allowed. This suggests the board has not been marked as being inactive. This behavior was first observed by John Chodera on a Cuda MacBook Pro; it was reproduced on the SIMBIOS cluster machine t0.

Comments
Attachments
Changes

Add A Comment:
No Comments Have Been Posted

No Changes Have Been Made to This Item

SimTK is maintained through Grant R01GM124443 01A1 from the National Institutes of Health (NIH). It was initially developed as part of the Simbios project funded by the NIH as part of the NIH Roadmap for Medical Research, Grant U54 GM072970.

Version 4.2.2. Website design by Viewfarm. Icons created by SimTK team using art by GraphBerry from www.flaticon.com under a CC BY 3.0 license. Forked from FusionForge 6.0.5.