Dear all,
I managed to isolate the problem in my code: I use an added vector to a system
(third order CLOUGH) as the loading for one of systems; I did two tests
1)
- I used system.project_vector to initialize this vector at each time
step.
- Solved with this loading.
2)
Code a)
- I used system.project_vector to initialize this vector at each time
step.
- I wrote this in a binary XDR file using:
equation_system.write(xdr_file_name.str(),
EquationSystems::WRITE_DATA |
EquationSystems::WRITE_ADDITIONAL_DATA);
Code b)
- I read this additional vector at the beginning of the time step using:
equation_system.read(xdr_file_name.str(),
EquationSystems::READ_HEADER |EquationSystems::READ_DATA |
EquationSystems::READ_ADDITIONAL_DATA);
- Solve with this loading.
even though, everything else is unchanged between case 1 and 2, the solutions
are different and you can see that the solution of case 2 visibly deteriorates
at mesh partition boundaries. I'm attaching the solutions at the 1st time step
from both cases.
Thanks,
Ata
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
