Hello, everyone.
I'm trying to build a 2D free energy diagram out of a COLVAR file that has records for 7 CVs.
The default options work, but are very slow. My sigmas are tiny, so sum_hills guesses lots of bins.
I'd like to set the number of bins/min/max/spacing manually, but the code seems to expect different
numbers of arguments for those settings at different times during execution.
$plumed sum_hills --histo COLVAR --mintozero --outhisto fes_2D.dat --kt 2.4943500 --sigma 0.02,0.01 --idw cv1,cv2 --min 0,0 --max
10,3 --spacing 0.1,0.02
+++ Internal PLUMED error
+++ file core/../../core/CLTool.h, line 140
+++ message: vector read in for keyword --min has wrong size
I put a printf statement right before to check what condition was causing this and turns out the input
parser expects bins/min/max/spacing to have 7 arguments, one for each CV in the file. So I tried:
$plumed sum_hills --histo COLVAR --mintozero --outhisto fes_2D.dat --kt 2.4943500 --sigma 0.02,0.01 --idw cv1,cv2 --min 0,0,0,0,0,0,0 --max 10,1,1,1,1,1,1 --spacing 0.1,1,1,1,1,1,1
+++ Internal PLUMED error
+++ file Grid.cpp, line 45
+++ message: assertion failed args.size()==gmin.size(), grid min dimensions in input do not match number of arguments
Similar things happen when trying to do a 1D energy surface.
$plumed sum_hills --histo COLVAR --mintozero --outhisto fes.dat --kt 2.4943500 --sigma 0.02 --idw cv1 --spacing 0.1
+++ Internal PLUMED error
+++ file core/../../core/CLTool.h, line 140
+++ message: vector read in for keyword --spacing has wrong size
$plumed sum_hills --histo COLVAR --mintozero --outhisto fes.dat --kt 2.4943500 --sigma 0.02 --idw cv1 --spacing 0.1,1,1,1,1,1,1
...
PLUMED: Action FUNCSUMHILLS
PLUMED: with label @7
PLUMED: with arguments cv1 cv2 cv3 cv4 cv5 cv6 cv7
PLUMED: Output format is %14.9f
PLUMED: The number of bins will be estimated from GRID_SPACING
[*] *** Process received signal ***
[*] Signal: Segmentation fault (11)
[*] Signal code: Address not mapped (1)
[*] Failing at address: 0x8
...
Default binning settings work though.
I'm not sure if this is a bug or I'm doing something wrong.
I've seen this behavior with tags v2.3.1, v.2.4.0, and v2.4.1 cloned from github, so it's not something new.
Minimal COLVAR file to reproduce the problem is attached.
Cheers,
Yuriy Khalak.