Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update TRestGeant4AnalysisProcess.cxx #76

Merged
merged 3 commits into from
Nov 30, 2022
Merged

Conversation

glorialuzon
Copy link
Contributor

@glorialuzon glorialuzon commented Nov 29, 2022

glorialuzon Ok: 32

I have added a string declaration in all the "SetObservableValue((string)obsName, *)". Those without weren't working properly (the corresponding observable branches were empty)

I have added a string declaration in all the "SetObservableValue((string)obsName, *)". Those without weren't working properly (the corresponding observable branches were empty)
@glorialuzon glorialuzon requested review from jgalan and lobis November 29, 2022 12:28
@lobis
Copy link
Member

lobis commented Nov 29, 2022

glorialuzon Ok: 3

I have added a string declaration in all the "SetObservableValue((string)obsName, *)". Those without weren't working properly (the corresponding observable branches were empty)

Please, REMOVE this text! This is just a template to serve as a reminder.

Please, give as much detail as possible at your PR and create the simplest possible PR to facilitate reviewing.

If your PR fixes a given issue, please specify the number followed by #

Fixes #

Give a detailed list of changes proposed in this pull-request. For example:

  • Feature added ...
  • Upgraded class TRestXYZ to ...
  • Added pipeline validation ...
  • Documented ...
  • Example added at ...
  • Script ...

Once your PR is approved remember to increase this library version version following these instructions. Remember to have a look to our general contribution guide.

Reminder: Please, new features and upgrades should be sufficiently documented and a corresponding validation test at the pipeline should be implemented.

Reminder: Adding this to your PR description will notify members at the library_dev team: @rest-for-physics/restG4

Reminder: When writing your PR description remember to leave any necessary instructions to test the new implementation.

Reminder: to set-up the PR in the draft state when there is still work in progress, and make it ready once all pipelines have suceeded.

I don't understand why we need an explicit casting to std::string if the variable is already a std::string by construction... any idea why @jgalan @juanangp ?

@juanangp
Copy link
Member

I don't understand why we need an explicit casting to std::string if the variable is already a std::string by construction... any idea why @jgalan @juanangp ?

As far as I understand the cast shouldn't be necessary.

I would suggest to make obsName constant --> const string obsName = ... but this shouldn't be the issue either.

@lobis
Copy link
Member

lobis commented Nov 29, 2022

I don't understand why we need an explicit casting to std::string if the variable is already a std::string by construction... any idea why @jgalan @juanangp ?

As far as I understand the cast shouldn't be necessary.

I would suggest to make obsName constant --> const string obsName = ... but this shouldn't be the issue either.

I updated this PR and made rest-for-physics/framework#339 to do a more correct handling of strings.

I should have no effect, but it would be nice if @glorialuzon can confirm if the problem motivating this PR exists on the branch glorialuzon-patch-1 (also update framework to glorialuzon-patch-1).

@glorialuzon glorialuzon merged commit 0da85ea into master Nov 30, 2022
@lobis lobis deleted the glorialuzon-patch-1 branch November 30, 2022 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants