GROMACS version:2020
GROMACS modification: No
Here post your question
Hi all,
I have written a python code which work previously:
pdb2gmx = gmx.commandline_operation(‘gmx_mpi’, arguments =[‘pdb2gmx’], input_files={’-f’:“XXX_fix.pdb”, ‘-water’:“tip3p”, ‘-ignh’:“yes”}, output_files={’-o’:“conf.gro”},stdin=‘1’)
Now it doesn’t work since I updated it and it is showing this error:
File “”, line 1, in
File “/home/yb87625/myvenv/lib64/python3.6/site-packages/gmxapi/commandline.py”, line 302, in commandline_operation
cli_result = cli(**cli_args)
File “/home/yb87625/myvenv/lib64/python3.6/site-packages/gmxapi/operation.py”, line 2838, in helper
handle = OperationDetails.operation_director(*args, context=context, label=None, **kwargs)
File “/home/yb87625/myvenv/lib64/python3.6/site-packages/gmxapi/operation.py”, line 1295, in operation_director
return construct()
File “/home/yb87625/myvenv/lib64/python3.6/site-packages/gmxapi/operation.py”, line 2568, in call
data_source_collection = node_input_factory(*self.args, **self.kwargs)
File “/home/yb87625/myvenv/lib64/python3.6/site-packages/gmxapi/operation.py”, line 457, in bind
raise exceptions.UsageError(‘Could not bind operation parameters to function signature.’) from e
gmxapi.exceptions.UsageError: Could not bind operation parameters to function signature.
I notice it will work if I delete " stdin=‘1’ ", but that is required for choosing forcefield for pdb2gmx command. Thus, is this a bug or something I did wrong?
Best,
Ben