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

Misleading label propagation #488

Open
delarosatrevin opened this issue Dec 12, 2023 · 2 comments
Open

Misleading label propagation #488

delarosatrevin opened this issue Dec 12, 2023 · 2 comments
Assignees

Comments

@delarosatrevin
Copy link
Member

I have found another behavior (new to me) that, in my opinion, is a bit misleading and confusing
I have run an abnitio job in CS from Scipion, then selected one of the volumes and ran xmipp preprocess (flip hand)
Both the selection (where I choose 'vol2' as label and the preprocess operation keep propagating the 'cryospac abinitio ... ' label
I don't know if that might be useful in other scenarios, but then searching for a volume produced by xmipp preprocess with 'cryosparc abnitio ...' label is quite confusing

@pconesa
Copy link
Contributor

pconesa commented Dec 15, 2023

I see, the motivaion of this was the following:
When you have volumes, mainly in initial volume methods.....we have setOfvolumes....if you use volume alignment protocol or a join set.... those volue are joined and then it was not possible or easy to identify which volume was which.

Maybe, the xmipp postprocess should update the label in this case? Or prefix it?

@delarosatrevin
Copy link
Member Author

I would say it is the other way around. That align-volumes protocol should propagate it if not better label. But other protocols do not. I found it misleading in the subset case, where the users explicitly set a label (like in my case) but it is ignored and not shown in the search dialog.

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

No branches or pull requests

3 participants