 |
Version: SMASH-3.3
|
|
- Member smash::ColliderModus::ColliderModus (Configuration modus_config, const ExperimentParameters ¶meters)
- include a check that only one method of specifying impact is used
- Member smash::Configuration::Value::node_
- (steinberg) What is that?
- Member smash::CrossSections::NNbar_annihilation (double current_xs, double scale_xs) const
- Same assumption made by string_excitation. Resolve.
- Member smash::CrossSections::string_excitation (double total_string_xs, StringProcess *string_process, const ScatterActionsFinderParameters &finder_parameters) const
- Same assumption made by NNbar_annihilation. Resolve.
- Member smash::details::write_in_chunk_impl (const Range &particles, const OutputFormatter< Converter > &formatter, std::function< void(const typename Converter::type &)> write, std::size_t max_buffer_bytes=1 '000 '000 '000)
- Once the hierarchy is cleaned up, move this into a common base class that OscarOutput and BinaryOutput inherit from.
- Member smash::GrandCanThermalizer::sample_multinomial (HadronClass particle_class, int N)
- (oliiny) what to do with this output?
- Member smash::kminusp_pi0lambda (double sqrts)
- clarify this
- Class smash::ModusDefault
- JB: many of these functions could/should be virtual (contradicts description given above, Vinzent says (in a nice way): does not make any sense whatsoever anyway)
- Member smash::ParticleType::spectral_function_const_width (double m) const
- unused The spectral function with a constant width (= width at pole).
- Member smash::RectangularLattice< T >::value_at (const ThreeVector &r, T &value) const
- (oliiny): maybe 1-order interpolation instead of 0-order?
- Member smash::StringProcess::set_pmin_gluon_lightcone (double p_light_cone_min)
- The following set_ functions are replaced with constructor with arguments.
- Member smash::ThermLatticeNode::compute_rest_frame_quantities (HadronGasEos &eos)
- (oliiny): use Newton's method instead of these iterations