Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content
Snippets Groups Projects
Commit 94832e54 authored by adelmann's avatar adelmann :reminder_ribbon:
Browse files

Releases memory solves out of memory in large simulations with a lot of particles and monitors

parent 1ac44311
No related branches found
No related tags found
1 merge request!650Resolve "OPAL Monitor Memory Usage"
...@@ -364,14 +364,15 @@ void LossDataSink::save(unsigned int numSets, OpalData::OpenMode openMode) { ...@@ -364,14 +364,15 @@ void LossDataSink::save(unsigned int numSets, OpalData::OpenMode openMode) {
Ippl::Comm->barrier(); Ippl::Comm->barrier();
particles_m.clear(); /// clear and return memory
turnNumber_m.clear(); particles_m = std::vector<OpalParticle>();
bunchNumber_m.clear(); turnNumber_m = std::vector<size_t>();
spos_m.clear(); bunchNumber_m = std::vector<size_t>();
refTime_m.clear(); spos_m = std::vector<double>();
RefPartR_m.clear(); refTime_m = std::vector<double>();
RefPartP_m.clear(); RefPartR_m = std::vector<Vector_t>();
globalTrackStep_m.clear(); RefPartR_m = std::vector<Vector_t>();
globalTrackStep_m = std::vector<h5_int64_t>();
} }
// Note: This was changed to calculate the global number of dumped particles // Note: This was changed to calculate the global number of dumped particles
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment