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

RunComputeProfiles and RunVIP concurrence #7

Closed
stephane-caron opened this issue Nov 21, 2013 · 3 comments
Closed

RunComputeProfiles and RunVIP concurrence #7

stephane-caron opened this issue Nov 21, 2013 · 3 comments
Labels

Comments

@stephane-caron
Copy link
Collaborator

In the current version,

ret = x.RunComputeProfiles(0, 1e-4)
print "RunComputeProfiles:", ret
ret = x.RunVIP(sdbeg_min, sdbeg_max)
print "RunVIP:", ret

Yields incorrect VIP results (because RunComputeProfiles affects x in a way that RunVIP does not detect). We should make the two independent in the future.

@quangounet
Copy link
Owner

Could you provide an example?

@stephane-caron
Copy link
Collaborator Author

Sure:

discrtimestep = 1e-4
sdbeg_min, sdbeg_max = 0., 1e-4
trajectorystring = """1.000000
2
1.02380743853 -0.621211430375 6.66133814775e-16 -4.4408920985e-16
-0.294007923442 -0.228798693785 1.66533453694e-16 0.0"""

When I run it with only RunVIP, I get:

sdendmin = 4.79738632613
sdendmax = 9.42902801911

If there is a call to RunComputeProfiles before, it becomes:

sdendmin = 0.0095855458967
sdendmax = 0.306737468694

@quangounet
Copy link
Owner

I reset resprofileslist at the beginning of Preprocess and it solved the bug on this instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants