Closed JonasSchaub closed 2 months ago
@FelixBaensch the cause of the issue (after pipeline fragmentation, every fragment has only one parent molecule assigned to it) seems to be in the pipeline routine of the FragmentationService. I kind of fixed it but this routine is complex (props to you who wrote it), so I am unsure whether this is correct. Also, I feel like there is one parent molecule missing in the overview in some cases. Could you kindly check this?
Could you provide me your test set please
Could you provide me your test set please
It is our Caffeine Derivatives https://drive.google.com/file/d/1G8E8dsFJMyDwgxsf4wPAeoP6DjLpXE9z/view?usp=drive_link which I fragmented with a pipeline of SRU (return only aglycone) and Ertl (return only functional groups).
First, let's clarify what should be included in the parent overview after a pipeline run. Should it contain the original structures, the intermediate structures that emerge after each step, or just the final intermediate structures or ...? The same applies to the frequencies.
I'd say the original structures, i.e. structures from the imported molecule set. All intermediates are so far not defined in out logic and the "parents" are the imported molecules in every other place. The "molecule frequencies" should also relate to them. And the fragment frequencies to the final result, i.e. the last pipeline step result, whose fragments are displayed.
I'd say the original structures, i.e. structures from the imported molecule set. All intermediates are so far not defined in out logic and the "parents" are the imported molecules in every other place. The "molecule frequencies" should also relate to them. And the fragment frequencies to the final result, i.e. the last pipeline step result, whose fragments are displayed.
So we agree on that. I'll take care of it, because that seems to be the problem, disagreement on the situation.
Thank you so much.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Thank you so much.
Could you please test it, and check if the fragment frequencies are correct
From what I see, everything looks alright! Shall I merge?
If the fragment frequencies after the pipeline are also correct, please.
@FelixBaensch the cause of the issue (after pipeline fragmentation, every fragment has only one parent molecule assigned to it) seems to be in the pipeline routine of the FragmentationService. I kind of fixed it but this routine is complex (props to you who wrote it), so I am unsure whether this is correct. Also, I feel like there is one parent molecule missing in the overview in some cases. Could you kindly check this?