(cd run_OMSimulator-cs-cvode && /home/hudson/saved_omc/OMSimulator/install/bin/OMSimulator --resultFile=../ScalableTestSuite_ScalableTestSuite.Electrical.BreakerCircuits.ScaledExperiments.BreakerNetwork_N_20_M_10_OMSimulator-cs-cvode_res.mat --stripRoot --tempDir=temp_ScalableTestSuite_ScalableTestSuite_Electrical_BreakerCircuits_ScaledExperiments_BreakerNetwork_N_20_M_10_OMSimulator-cs-cvode_fmu --startTime=0 --stopTime=2 --stepSize=0.0008 --mode=cs --timeout=240 --tolerance=1e-06 ../ScalableTestSuite_ScalableTestSuite_Electrical_BreakerCircuits_ScaledExperiments_BreakerNetwork_N_20_M_10_OMSimulator-cs-cvode.fmu) LOG_STDOUT | info | Using sparse solver for linear system 0, | | | | because density of 0.152 remains under threshold of 0.200. LOG_STDOUT | info | The simulation runtime does not have access to sparse solvers. Defaulting to a dense linear system solver instead. LOG_STDOUT | info | Using sparse solver for linear system 1, | | | | because density of 0.152 remains under threshold of 0.200. LOG_STDOUT | info | The simulation runtime does not have access to sparse solvers. Defaulting to a dense linear system solver instead. LOG_STDOUT | info | The maximum density for using sparse solvers can be specified | | | | using the runtime flag '<-lssMaxDensity=value>'. LOG_SOLVER | info | CVODE linear multistep method CV_BDF LOG_SOLVER | info | CVODE maximum integration order CV_ITER_NEWTON LOG_SOLVER | info | CVODE use equidistant time grid YES LOG_SOLVER | info | CVODE Using relative error tolerance 1.000000e-06 LOG_SOLVER | info | CVODE Using dense internal linear solver SUNLinSol_Dense. LOG_SOLVER | info | CVODE Use internal dense numeric jacobian method. LOG_SOLVER | info | CVODE uses internal root finding method NO LOG_SOLVER | info | CVODE maximum absolut step size 0 LOG_SOLVER | info | CVODE initial step size is set automatically LOG_SOLVER | info | CVODE maximum integration order 5 LOG_SOLVER | info | CVODE maximum number of nonlinear convergence failures permitted during one step 10 LOG_SOLVER | info | CVODE BDF stability limit detection algorithm OFF info: *** FMU Simulation Info *** - model : ScalableTestSuite.Electrical.BreakerCircuits.ScaledExperiments.BreakerNetwork_N_20_M_10 (co-simulation) - fmiVersion: 2.0 - startTime : 0.000000 - stopTime : 2.000000 - tolerance : 1e-06 - stepSize : 0.0008 info: Result file: ../ScalableTestSuite_ScalableTestSuite.Electrical.BreakerCircuits.ScaledExperiments.BreakerNetwork_N_20_M_10_OMSimulator-cs-cvode_res.mat (bufferSize=10) info: Parameter BreakerNetwork_N_20_M_10.B[1].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[2].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[3].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[4].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[5].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[6].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[7].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[8].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[9].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[10].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[11].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[12].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[13].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[14].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[15].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[16].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[17].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[18].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[19].name will not be stored in the result file, because the signal type is not supported info: Parameter BreakerNetwork_N_20_M_10.B[20].name will not be stored in the result file, because the signal type is not supported LOG_STDOUT | info | Breaker 20 opens at time = 0.4056 LOG_STDOUT | info | Breaker 19 opens at time = 0.4056 LOG_STDOUT | info | Breaker 18 opens at time = 0.4056 LOG_STDOUT | info | Breaker 17 opens at time = 0.4056 LOG_STDOUT | info | Breaker 16 opens at time = 0.4056 LOG_STDOUT | info | Breaker 15 opens at time = 0.4056 LOG_STDOUT | info | Breaker 14 opens at time = 0.4056 LOG_STDOUT | info | Breaker 13 opens at time = 0.4056 LOG_STDOUT | info | Breaker 12 opens at time = 0.4056 LOG_STDOUT | info | Breaker 11 opens at time = 0.4056