Results 40 issues of Javier Galan

![jgalan](https://badgen.net/badge/PR%20submitted%20by%3A/jgalan/blue) ![Ok: 4](https://badgen.net/badge/PR%20Size/Ok%3A%204/green) [![](https://gitlab.cern.ch/rest-for-physics/framework/badges/jgalan-new-logos/pipeline.svg)](https://gitlab.cern.ch/rest-for-physics/framework/-/commits/jgalan-new-logos) [![](https://github.com/rest-for-physics/framework/actions/workflows/validation.yml/badge.svg?branch=jgalan-new-logos)](https://github.com/rest-for-physics/framework/commits/jgalan-new-logos) Perhaps it is a good moment to update the text on the acknowledgments. If done, it would be also good to keep it synced with...

![jgalan](https://badgen.net/badge/PR%20submitted%20by%3A/jgalan/blue) ![Medium: 139](https://badgen.net/badge/PR%20Size/Medium%3A%20139/orange) [![](https://gitlab.cern.ch/rest-for-physics/framework/badges/detector_template_project/pipeline.svg)](https://gitlab.cern.ch/rest-for-physics/framework/-/commits/detector_template_project) [![](https://github.com/rest-for-physics/framework/actions/workflows/validation.yml/badge.svg?branch=detector_template_project)](https://github.com/rest-for-physics/framework/commits/detector_template_project) We should take it as a good chance to review the base/template project for `detector-project`. I use `detector-project` and not `template-project` because it might happen...

![jgalan](https://badgen.net/badge/PR%20submitted%20by%3A/jgalan/blue) ![Ok: 25](https://badgen.net/badge/PR%20Size/Ok%3A%2025/green) [![](https://gitlab.cern.ch/rest-for-physics/framework/badges/jgalan_smear_review/pipeline.svg)](https://gitlab.cern.ch/rest-for-physics/framework/-/commits/jgalan_smear_review) [![](https://github.com/rest-for-physics/framework/actions/workflows/validation.yml/badge.svg?branch=jgalan_smear_review)](https://github.com/rest-for-physics/framework/commits/jgalan_smear_review)

This issue comes after some discussions present at the following PR https://github.com/rest-for-physics/axionlib/pull/56#issuecomment-1517527380 I think a way around to solve this problem could be having a script that identifies if the...

The `startTime` and `endTime` metadata members do not read properly the date if we do not provide full formatting. E.g. if we use `` it will work fine. However, if...

good first issue
invalid

The following issue should introduce the use of `TRestCut` inside the `TRestDataSet` definition. This way we could define our config file as: ``` .... ... ```

There are other places where > needs to be used, for example inside the `globalCut` definition, inside TRestAnalysisPlot, the condition value can be something like `>10`. This could be solved...

invalid

We need to define new classes that allow us to create datasets. A dataset is a class that allows to define some rules and a period of time to filter...

development

![jgalan](https://badgen.net/badge/PR%20submitted%20by%3A/jgalan/blue) ![Ok: 46](https://badgen.net/badge/PR%20Size/Ok%3A%2046/green) [![](https://gitlab.cern.ch/rest-for-physics/framework/badges/jgalan_run_members/pipeline.svg)](https://gitlab.cern.ch/rest-for-physics/framework/-/commits/jgalan_run_members) [![](https://github.com/rest-for-physics/framework/actions/workflows/validation.yml/badge.svg?branch=jgalan_run_members)](https://github.com/rest-for-physics/framework/commits/jgalan_run_members) A MAJOR update adding a NEW metadata member (fRunDuration) inside TRestRun and REMOVING an unused data member (fRunClassName), I reviewed also the documentation of the...

This might be a minor issue, but when doing ray-tracing using axionlib it would be convenient that the observables inside the analysis tree are ordered in the same way as...

enhancement
invalid