Monitor data parse error

September 19, 2007, 10:12

I am running a simulation using results form a previous one as initial conditions. The solver is giving such kind of error: 'Monitor data parse error.Size mismatch.Expected 1136 values, but found 1137.' But the solver is running still and giving results.

Can someone please tell me where to search for the problem? Thanks Nena

-Maxim- · May 31, 2018, 10:18

I know this thread is over 10 years old but I just ran across the same error and found a solution - so my post is for the purpose of documentation.

I started a calculation with Ansys 19.1 and wanted to monitor the run with the SolverManager of version 19.0.
Monitoring the run with the SolverManager 19.1 solved the problem.

September 19, 2007, 10:12	Monitor data parse error	#1
Nena Guest Posts: n/a	I am running a simulation using results form a previous one as initial conditions. The solver is giving such kind of error: 'Monitor data parse error.Size mismatch.Expected 1136 values, but found 1137.' But the solver is running still and giving results. Can someone please tell me where to search for the problem? Thanks Nena

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[OpenFOAM] Native ParaView Reader Bugs	tj22	ParaView	270	January 4, 2016 11:39
nonNewtonian viscosity model	mhassani	OpenFOAM Programming & Development	5	January 7, 2013 09:27
Accessing phi from a fvPatchField at same patch	johndeas	OpenFOAM	1	September 13, 2010 20:23
compile errors of boundary condition "expDirectionMixed"	liying02ts	OpenFOAM Bugs	2	February 1, 2010 20:11
user defined function	cfduser	CFX	0	April 29, 2006 10:58

May 31, 2018, 10:18		#2
-Maxim- Senior Member Maxim Join Date: Aug 2015 Location: Germany Posts: 415 Rep Power: 12	I know this thread is over 10 years old but I just ran across the same error and found a solution - so my post is for the purpose of documentation. I started a calculation with Ansys 19.1 and wanted to monitor the run with the SolverManager of version 19.0. Monitoring the run with the SolverManager 19.1 solved the problem.