Skip to content
This repository was archived by the owner on Jan 26, 2022. It is now read-only.
This repository was archived by the owner on Jan 26, 2022. It is now read-only.

CalculateImpliedTimeScale failed with "k must be between 1 and ndim(A)-1" #420

Open
@Serilin

Description

@Serilin

Hi, everyone
I'm working with my system using msmbuilder2.8.2. The cluster process has succeed with the commond " msmb Cluster rmsd hybrid -d 0.045 -l 50" . But the command "CalculateImpliedTimeScales -l 1,25 -i 1 -o Data/ImpliedTimeScales.dat" failed, telling the following
{'assignments': 'Data/Assignments.h5',
'eigvals': 10,
'interval': 1,
'lagtime': '1,25',
'notrim': False,
'output': 'Data/ImpliedTimescales.dat',
'procs': 1,
'quiet': False,
'symmetrize': 'MLE'}
09:04:17 - Getting 10 eigenvalues (timescales) for each lagtime...
09:04:17 - Building MSMs at the following lag times: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25]
09:04:17 - Calculating implied timescales at lagtime 1
09:04:17 - Selected component 58 with population 0.080616
09:04:18 - BFGS likelihood maximization terminated after 17 function calls. Initial and final log likelihoods: -79.490250, -78.928102.
09:04:18 - You cannot calculate 11 eigenvectors from a 5 x 5 matrix.
09:04:18 - Instead, calculating 5 eigenvectors.
09:04:18 - Calculating implied timescales at lagtime 8
09:04:18 - Selected component 72 with population 0.056490
Traceback (most recent call last):
File "/home/tim/anaconda/bin/msmb", line 9, in
load_entry_point('msmbuilder==2.8.2', 'console_scripts', 'msmb')()
File "/home/tim/anaconda/lib/python2.7/site-packages/msmbuilder-2.8.2-py2.7.egg/msmbuilder/scripts/msmb.py", line 51, in entry_point
getattr(scripts, args.subparser_name).entry_point()
File "/home/tim/anaconda/lib/python2.7/site-packages/msmbuilder-2.8.2-py2.7.egg/msmbuilder/scripts/CalculateImpliedTimescales.py", line 85, in entry_point
(not args.notrim), args.symmetrize, args.procs)
File "/home/tim/anaconda/lib/python2.7/site-packages/msmbuilder-2.8.2-py2.7.egg/msmbuilder/scripts/CalculateImpliedTimescales.py", line 67, in run
trimming=trimming, symmetrize=symmetrize, n_procs=nProc)
File "/home/tim/anaconda/lib/python2.7/site-packages/msmbuilder-2.8.2-py2.7.egg/msmbuilder/msm_analysis.py", line 237, in get_implied_timescales
lags = result.get(999999)
File "/home/tim/anaconda/lib/python2.7/multiprocessing/pool.py", line 554, in get
raise self._value
ValueError: k must be between 1 and ndim(A)-1
09:04:18 - BFGS likelihood maximization terminated after 13 function calls. Initial and final log likelihoods: -82.038017, -75.611886.
09:04:18 - You cannot calculate 11 eigenvectors from a 3 x 3 matrix.
09:04:18 - Instead, calculating 3 eigenvectors.

I has tried the cluster with ’-d 0.2” and ‘-d 0.1“, and both failed. I don't know why.

I noted that when I ran the alanine dipeptide tutorial of msmbuilder2.8, "msmb CalculateImpliedTimescales -l 1,25 -i 1 -o Data/ImpliedTimescales.dat" gave out the
07:17:18 - Calculating implied timescales at lagtime 24
07:17:18 - Selected component 0 with population 1.000000
07:17:19 - BFGS likelihood maximization terminated after 157 function calls. Initial and final log likelihoods: -163578.487091, -163577.602213.
07:17:19 - Calculating implied timescales at lagtime 25
07:17:19 - Selected component 0 with population 1.000000
07:17:20 - BFGS likelihood maximization terminated after 185 function calls. Initial and final log likelihoods: -163322.252035, -163321.354107.
07:17:20 - Abnormal termination of BFGS likelihood maximization. Error code 2
07:17:20 - Saved output to Data/ImpliedTimescales.dat
This tutorial is successful in my computer, so why my system was wrong ? Anyone can give some suggestion?

ps My trajectory has not solvent and was saved every 5 ps for total 200 ns. How should I define the number of min and max lagtime? Is it alway from 1 to 25?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions