Batch RunParameterIdentification completes successfully but no .anyset file is saved

Dear AnyBody Team,

I’m running into the same problem described in this post.

I’m using batch processing for simulations of mocap data with anypytools.
From the python side, the RunParameterIdentificationfinishes successfully. Python reports the run as completed without errors. However, no .anyset file is written. Rerunning the RunParameterIdentification of the respective file via python does also not conclude in a .anyset file.

When I take the same trial and run the ParameterIdentification manually in AnyBody, everything works as expected.

Rerunning the whole batch with more or less files, this phenomenon occurs always for the exact same trial.

I was wondering if anyone found a solution or workaround for this.

Thank you very much in advance.

Best regards,

Ina

Hi @InaA !

Could you please provide what version of AnyBody Modeling System, AMMR and AnyPyTools you are using ?

If you are not on the latest AnyPyTools version (1.20.6 atm) please try to update that first. There has been some significant changes since the post you refer to in September 2025.

Best regards,

Bjørn

Hello Bjørn,

I am using the following versions:

  • anypytools: 1.20.6
  • python: 3.14.3
  • AnyBody: 8.1.4
  • AMMR 4-Beta

I also realized that my previous statement was a bit premature. When I tested the manual execution before, I only ran the marker optimization which resulted in an .anyset file. In the batch processing, however, I am running marker and anthropometric optimization.

When I now manually run RunParameterIdentification including the anthropometric optimization, I see the following message in the output:

“Failed to resolve kinematic constraints. Newton relaxation too small.”

The model does not abort, but does not seem to continue after this message.

From the Python side, I am only setting num_processes = 4 and do not specify any additional settings.

Could it be that, in the batch setup, the parameter identification effectively terminates before fully converging (i.e. not running as long as in the manual case), without raising an explicit error? That could explain why Python reports a successful run, but no .anyset file is written.

Does this sound like a plausible explanation, and is there a recommended way to handle or detect this more robustly when running anthropometric optimization in batch mode?

Best regards,
Ina