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

Comparison of running scripts with stationary and non-stationary models in the background #19

Open
alexlafleur opened this issue Nov 3, 2016 · 7 comments

Comments

@alexlafleur
Copy link
Collaborator

The goal was to run the same script of evaluation with different models in the background (the normal stationary markov model, and the non-stationary markov model with delta parameter).
A delta parameter of 0 should yield the same results as the stationary model.

@alexlafleur
Copy link
Collaborator Author

alexlafleur commented Nov 3, 2016

##Performance using MMFamily1
performance

Performance using QMMFamily1 and delta=0

performance0

Error using MMFamily1

error

Error using QMMFamily1 and delta=0

error0

@alexlafleur
Copy link
Collaborator Author

alexlafleur commented Nov 8, 2016

Plots without reusing the mmf1_0 object from sampling the qmm

performance

performance0

error

error0

@greenTara
Copy link
Collaborator

greenTara commented Nov 10, 2016

OK, the behavior of the heatmap does make sense due to the increase in shift and window size with increasing taumeta along a row.

@greenTara
Copy link
Collaborator

To close this issue, we need to make a final set of calculations for mm and qmm with delta = 0, to verify that they are still producing the same thing, after the refactoring of the code. It is not clear if we can get exactly the same model and simulation by setting the random seed. If that would work, this could be used as a unit test, where we would compare the simulated data in each case, rather than perform any estimations. Otherwise, we need to look at the statistical results, (averaged over large num_trajectories and num_runs) in order to make a comparison.

@alexlafleur
Copy link
Collaborator Author

We do have the same Spectral MMs in both models, but the simulation does return different arrays for both models even though I set a seed.

If we go with the other possibility, what values do we assign num_trajectories and num_runs?

@greenTara
Copy link
Collaborator

Let's use numsims = 256.

num_runs = 1 (with verification that the transition matrix is the same for MM and QMM)

@alexlafleur
Copy link
Collaborator Author

What about num_trajs?

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

No branches or pull requests

2 participants