-
Notifications
You must be signed in to change notification settings - Fork 5
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
Can lower bound in FAUST step five be negtive? #15
Comments
Hi
Negative values are allowed and values are considered if they are admitted
by the channel bounds.
The increased computation time is caused by the large number of zeros and
the fact that this introduces many ties in the data set.
@evangreene can provide more insight to this.
What is your goal with including the zeros? Knowing this might help us find
a solution.
Greg Finak
…On Tue, Mar 17, 2020, 00:03 zl7515 ***@***.***> wrote:
Hi,
In step five of the work example, you set the lower bound to 0. Now I want
zeros to be considered so I changed 0 to -0.01. However, it turned out that
the code chunk in step seven keeps running without any warning/error
message. The chunk has been running for more than 5 hours. Previously, with
the lower boundary equal 0, the chunk was done within 10 minutes. So is it
because there is too much computation involved as 0s are being considered,
or simply because the algorithm doesn't accept negative values?
P.S. I noted a tiny contradiction in step five. At the very beginning, you
said
"For example, we would expect any cell populations with a median
fluorescence intensity (MFI) below 0 in a channel to be annotated as “Low”
for that channel."
However, later you stated
"Expression values in a channel less than or equal to the value in the
“Low” row are treated as low, by default, and not actively considered when
FAUST processes the data."
So 0s are actually considered as active or not in your algorithm?
Thanks in advance for your help.
Allen
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#15>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKSI6IUS6ABO3CKOXFFDZ3RH4OCLANCNFSM4LNCZDDQ>
.
|
Hi Greg, Thanks for your continuing assistance. It seems that the program kept running until the server was down. Best, Allen |
Hi @zl7515 , Can you provide some details about the dataset you are analyzing? In particular, how many samples are in the gating set, and how many cells (on average) are in the starting node of your analysis across experimental units? When processing CyTOF datasets, you can set the lower bound in the channel bounds matrix to a negative value in order to explicitly model the spike at zero, but this will increase processing time. The increase in processing time can be ameliorated by increasing the setting of the Thanks, |
Hi Evan, Thanks for your speedy response. Best, Allen |
Hi Evan, I have changed the thread number to maximum but it seems like my program is proceeding hopeless running again. I suspect that the algorithm is super slow when 0s are being considered and will be eventually kicked out of the server. It is unfair for other researchers so the server took some mandatory actions. I will try it on virtual machine later. Have you ever run FAUST with 0s on any server? Thanks. Allen |
Hi Allen, Yes I have processed CyTOF datasets with FAUST where I've modified the channel bounds in order to allow zeros to be modeled. It can be computationally demanding: how many threads are you able to allocate for the computation? Beyond the zeros, increased computational time may be a result of the modal structure of your dataset. However, it's difficult to say if that is occurring here without actually seeing the dataset itself. Thanks, |
Hi, |
@SamGG FAUST already randomizes ties internally. |
Hi @SamGG, FAUST is non-parametric. The For CyTOF datasets where randomization has not been performed (by the instrument or by the analyst), FAUST will treat the exact 0's as the known "lowest" expression category by default. By modifying the Hope this helps, |
Thanks for your answers. I think you achieved your best. So, my questions are just curiosity, because I feel there a point I'm missing. |
@SamGG @evangreene @gfinak Best, Allen |
Hi,
In step five of the work example, you set the lower bound to 0. Now I want zeros to be considered so I changed 0 to -0.01. However, it turned out that the code chunk in step seven keeps running without any warning/error message. The chunk has been running for more than 5 hours. Previously, with the lower boundary equal 0, the chunk was done within 10 minutes. So is it because there is too much computation involved as 0s are being considered, or simply because the algorithm doesn't accept negative values?
P.S. I noted a tiny contradiction in step five. At the very beginning, you said
"For example, we would expect any cell populations with a median fluorescence intensity (MFI) below 0 in a channel to be annotated as “Low” for that channel."
However, later you stated
"Expression values in a channel less than or equal to the value in the “Low” row are treated as low, by default, and not actively considered when FAUST processes the data."
So 0s are actually considered as active or not in your algorithm?
Thanks in advance for your help.
Allen
The text was updated successfully, but these errors were encountered: