Currently, if I try to provide only a single .psf file to load all trajectories in a simlist, later it will cause errors in metric projection, which does not happen if I provide a .pdb (but then bond information might be missing).
A solution for this is to provide the input folders, but doesn't work when used with filtered trajectories from simfilter, since only a single .psf and .pdb file are created. Passing both of them as a list doesn't work, as the function expects a directory/molfile for each trajectory. I could manually create them with the filtered molfiles, but would be much better if I could just provide a single .psf file.
Currently, if I try to provide only a single
.psf
file to load all trajectories in asimlist
, later it will cause errors in metric projection, which does not happen if I provide a.pdb
(but then bond information might be missing).A solution for this is to provide the input folders, but doesn't work when used with filtered trajectories from
simfilter
, since only a single.psf
and.pdb
file are created. Passing both of them as a list doesn't work, as the function expects a directory/molfile for each trajectory. I could manually create them with the filtered molfiles, but would be much better if I could just provide a single .psf file.Error reproduction: test_simlist_issue.tar.gz