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

Merge geometry/rich/richgeo into geometry/rich #513

Merged
merged 4 commits into from
Feb 27, 2023
Merged

Conversation

veprbl
Copy link
Member

@veprbl veprbl commented Feb 25, 2023

Briefly, what does this PR introduce?

Remove standalone library that is not an actual JANA2 plugin, but pretends to be one.

Resolves: #483

What kind of change does this PR introduce?

  • Bug fix (issue #__)
  • New feature (issue #__)
  • Documentation update
  • Other: __

Please check if this PR fulfills the following:

  • Tests for the changes have been added
  • Documentation has been added / updated
  • Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

No

Does this PR change default behavior?

No

@veprbl veprbl requested a review from c-dilks February 25, 2023 03:24
@c-dilks
Copy link
Member

c-dilks commented Feb 27, 2023

Thanks! Yes, this should be a single plugin.

Let's rename it to richgeo so it's not confused with a detector plugin. The README should also be updated (I can take care of these if you prefer).

Do we have to flatten it to one directory? It's not necessary, but I prefer to have a clearer separation between the JANA/EICrecon-dependent code and the JANA/EICrecon-independent code.

@c-dilks
Copy link
Member

c-dilks commented Feb 27, 2023

Let's rename it to richgeo so it's not confused with a detector plugin. The README should also be updated (I can take care of these if you prefer).

Done and done. Let's see what the CI says, and I should also test this with #393.

@veprbl veprbl enabled auto-merge (squash) February 27, 2023 17:53
@veprbl
Copy link
Member Author

veprbl commented Feb 27, 2023

@c-dilks If you think this is good, please approve

@c-dilks
Copy link
Member

c-dilks commented Feb 27, 2023

Do we have to flatten it to one directory?

Awaiting feedback on this.

@c-dilks
Copy link
Member

c-dilks commented Feb 27, 2023

I should also test this with #393.

I can no longer do this thanks to new upstream issues, so I'll deal with that later after this PR is merged.

@c-dilks
Copy link
Member

c-dilks commented Feb 27, 2023

Do we have to flatten it to one directory?

It would be nice to have a plugin_add_subdirectory macro, but with forthcoming refactoring let's not bother. A flat directory is fine with me and the README explains the separation.

@c-dilks c-dilks requested a review from DraTeots February 27, 2023 18:52
@c-dilks
Copy link
Member

c-dilks commented Feb 27, 2023

(need another reviewer since I pushed to this branch)

@veprbl
Copy link
Member Author

veprbl commented Feb 27, 2023

Do we have to flatten it to one directory?

Awaiting feedback on this.

You could set sources manually instead of calling plugin_glob_all. I just don't see the point. The separation should be already apparent from the filenames.

@veprbl veprbl merged commit 5b1692c into main Feb 27, 2023
@veprbl veprbl deleted the pr/merge_richgeo branch February 27, 2023 19:16
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.

Symbol not found: vtable for rich::IrtGeoDRICH
2 participants