Javier Galan

Personally, I find writing shell scripts handy, and using system variables allows to use RML as templates. Of course, the ` ` section will allow to define the variable in...

In the case above the variables are defined inside the script and are used for the execution of the command just afterwards. Perhaps there are other user cases which do...

>> Note that using this approach you should redefine these variables every time you launch the program. Not really, if it is defined at `` it might be redefined using...

Any improvement on this sense is really welcome. This big change will probably break forward/backward compatibility. So we could move towards a new 2.4.X release in that case. But who...

One could avoid that by accepting that the user will call `detectorEvent->GetHits()->GetNumberOfHitsY()`? Just removing the methods at `TRestDetectorHitsEvent` would force us to write the code that way.

I was thinking more on a RML file as the following one. https://github.com/rest-for-physics/axionlib/blob/mcpl_optics/pipeline/optics/setups.rml where I have several definitions that I could load at once in a `restRoot` session. So, that...

I was thinking about just parsing the file with a method that returns a `std::pair` with the `ClassName` and `name`. https://github.com/rest-for-physics/framework/commit/ba941ef939de0e8cb6d39c8be01c04e731aa87c3 Then, just Process it in `restRoot`

This PR is not passing the pipeline

Right, I believe `bar` should be the standard unit pressure for REST. Just because we are used to measure the pressure chamber in `bar`. However, for gas calculations I believe...

I see, then we will need to introduce a python script at the validation pipeline, similar to `validateProcesses.py`, or inside `validateProcesses.py` that certifies that no `any` statement appear at the...