Set log level when confusion occurs with the templated log params

This commit is contained in:
Guillaume Giudicelli 2020-08-31 16:23:49 -06:00
parent d183a25376
commit 8dfbc0662b
2 changed files with 5 additions and 5 deletions

View file

@ -98,7 +98,7 @@ has a collision. For example, if you received this error at cycle 5, generation
<trace>5 1 4032</trace>
For large runs it is often advantageous to run only the offending particle by
using particle restart mode with the ``-r`` command-line options in conjunction
using particle restart mode with the ``-r`` command-line option in conjunction
with the particle restart files that are created when particles are lost with
this error.

View file

@ -410,7 +410,7 @@ Particle::cross_surface()
// TODO: off-by-one
const auto& surf {model::surfaces[i_surface - 1].get()};
if (settings::verbosity >= 10 || trace_) {
write_message(" Crossing surface {}", surf->id_);
write_message(1, " Crossing surface {}", surf->id_);
}
if (surf->bc_ == Surface::BoundaryType::VACUUM && (settings::run_mode != RunMode::PLOTTING)) {
@ -437,7 +437,7 @@ Particle::cross_surface()
// Display message
if (settings::verbosity >= 10 || trace_) {
write_message(" Leaked out of surface {}", surf->id_);
write_message(1, " Leaked out of surface {}", surf->id_);
}
return;
@ -502,7 +502,7 @@ Particle::cross_surface()
// Diagnostic message
if (settings::verbosity >= 10 || trace_) {
write_message(" Reflected from surface {}", surf->id_);
write_message(1, " Reflected from surface {}", surf->id_);
}
return;
@ -556,7 +556,7 @@ Particle::cross_surface()
// Diagnostic message
if (settings::verbosity >= 10 || trace_) {
write_message(" Hit periodic boundary on surface {}", surf->id_);
write_message(1, " Hit periodic boundary on surface {}", surf->id_);
}
return;
}