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

SinkhornProblem star policy wrong problem order #650

Open
ArinaDanilina opened this issue Jan 29, 2024 · 4 comments
Open

SinkhornProblem star policy wrong problem order #650

ArinaDanilina opened this issue Jan 29, 2024 · 4 comments
Assignees

Comments

@ArinaDanilina
Copy link
Collaborator

ArinaDanilina commented Jan 29, 2024

sp = SinkhornProblem(adata_red)
sp = sp.prepare(
    key="perturbation", joint_attr="X_pca", policy="star", reference="control"
)
sp = sp.solve(1e-2, 0.95, 0.95)
sp

generates SinkhornProblem[('Dacinostat (LAQ824)', 'control'), ('Givinostat (ITF2357)', 'control'), ('TAK-901', 'control'), ('Flavopiridol HCl', 'control')]
but should be SinkhornProblem[('control', 'Dacinostat (LAQ824)'), etc ]

@giovp
Copy link
Member

giovp commented Jan 30, 2024

@MUCDK why is this an issue? reference is always the target in star policy

class StarPolicy(SimplePlanPolicy[K]):

@MUCDK
Copy link
Collaborator

MUCDK commented Jan 30, 2024

should we make it more flexible then? Here, the control should always be the source.

@giovp
Copy link
Member

giovp commented Jan 30, 2024

I'd be ok with that, I just don't super see how this would change/unblock the perturbation setting. At the end of the day it is just convention right, since everything is symmetric in moscot?

@selmanozleyen
Copy link
Collaborator

selmanozleyen commented Sep 23, 2024

hi, I overlooked this issue from a long time ago. I don't understand if this is a design problem or a feature etc.

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

4 participants