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

Creating parameter specific (Arscin) transformation values #124

Open
SforR opened this issue Sep 14, 2018 · 2 comments
Open

Creating parameter specific (Arscin) transformation values #124

SforR opened this issue Sep 14, 2018 · 2 comments

Comments

@SforR
Copy link

SforR commented Sep 14, 2018

Hi everyone,

With my (flowcytometry) data I see that some channels have an optimal Arcsin transformation
that differs from the others. So I actually want to use different transformCofactors.
Has some one experience with that?
I have tried using a code transformCofactor = c(150,500,1000....) but that doesn't seem to do the trick.

Best,

Sam

@SforR SforR changed the title S Creating parameter specific (Arscin) transformation values Sep 14, 2018
@SamGG
Copy link

SamGG commented Oct 11, 2018

Hi,
The main point I noticed very recently is that citrus does not manage compensation at all (@rbruggner correct me if I am wrong). Because it was designed for mass cytometry. So the FCS have to be compensated first.
I will estimate how much work your request requires.
Best.

@SforR
Copy link
Author

SforR commented Oct 15, 2018

Hi Sam,

I didn't know that actually, luckily I always first apply compensation on my FCS data together with some pre-gating.
But thanks in adavance for looking and estimating the amount of work.

Cheers.

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

2 participants