Leaving partition_agnostic=true gives me the same assertion error on
SerialMesh as well.

Sincerely,

Miguel A. Salazar de Troya
Graduate Scholar, Lawrence Livermore National Laboratory
Ph.D. Candidate, University of Illinois at Urbana-Champaign
T1878
Rm: 112
Ext: 2-6411
L-code: 288




On 1/14/16, 8:24 AM, "Salazar De Troya, Miguel" <salazardet...@llnl.gov>
wrote:

>In that case, what would be the compatible way to restart the mesh if I
>still leave partition_agnostic=false? What would be the way to fix the
>code? Leaving partition_agnostic=true doesn¹t avoid the assertion either
>for me.
>
>Sincerely,
>
>Miguel A. Salazar de Troya
>Graduate Scholar, Lawrence Livermore National Laboratory
>Ph.D. Candidate, University of Illinois at Urbana-Champaign
>T1878
>Rm: 112
>Ext: 2-6411
>L-code: 288
>
>
>
>
>On 1/13/16, 3:08 PM, "Roy Stogner" <royst...@ices.utexas.edu> wrote:
>
>>
>>On Wed, 13 Jan 2016, Roy Stogner wrote:
>>
>>> On Tue, 12 Jan 2016, Salazar De Troya, Miguel wrote:
>>>
>>>>  I¹m attaching a simple code that illustrates the problem. I open a
>>>>  mesh (l_problem.xda) and perform a uniform refinement (if I don¹t,
>>>>  there are no problems), then I create an ExplicitSystem and assign
>>>>  random values to its solution. I print the solution for verification
>>>>  purposes. I save both the equation system and the refined mesh. Then
>>>>  I rerun the code reading the saved data and the saved mesh and print
>>>>  the solution to compare it with the previous run. Running the code
>>>>  in parallel, if my mesh is SerialMesh, both solutions coincide,
>>>>  however if my mesh is plain Mesh, I get this assertion error:
>>>> 
>>>>
>>>>  Assertion `cnt < io_buffer.size()' failed.
>>>>
>>>>  cnt = 12755
>>>>
>>>>  io_buffer.size() = 12755
>>>> 
>>>>
>>>>  The program would be run with the following flags
>>>>
>>>>  mpirun ­n 2 ./program ­uniref 1 ­read_sol 0 > output1.txt
>>>> 
>>>>
>>>>  Rerun:
>>>>
>>>>  mpirun ­n 2 ./program ­uniref 1 ­read_sol 1 > output2.txt
>>>
>>> Thanks!
>>>
>>> I can reproduce this with the latest libMesh.  I'll see if I can
>>> bisect it.
>>
>>I can't go back far enough to bisect it (it fails the same way with at
>>least 0.9.3), but I've found why I hadn't seen it before: when editing
>>your code to be compatible with 0.9.2.2, I discovered that the failure
>>only occurs when you set partition_agnostic=false in the
>>EquationSystems::write() call.  If you tell libMesh not to renumber
>>the restart solution consistently with how it renumbers the restart
>>mesh, I'm not at all surprised when assertions fail afterwards.
>>---
>>Roy
>
>
>--------------------------------------------------------------------------
>----
>Site24x7 APM Insight: Get Deep Visibility into Application Performance
>APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>Monitor end-to-end web transactions and take corrective actions now
>Troubleshoot faster and improve end-user experience. Signup Now!
>http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
>_______________________________________________
>Libmesh-users mailing list
>Libmesh-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/libmesh-users

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to