-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update needed for FlowSOM object update? #24
Comments
Hi Jake,
I just pushed the fixes I had locally, but they are not yet fully tested
(the reason I kept postponing the push).
Let me know if you still find any other bugs!
All the best,
Sofie
…On Fri, 4 Jun 2021 at 00:37, Jake Wagner ***@***.***> wrote:
Hi Sofie,
I could be wrong, but it seems like CytoNorm's internal handling of
FlowSOM objects may need to be updated after the Big Update
<SofieVG/FlowSOM@ce17ea6>
commit to FlowSOM reorganized the list structure.
If I install both packages from the current GitHub master branches (or
FlowSOM from Bioconductor 3.13) and attempt to run through the examples
from the README, I run into issues from testCV or CytoNorm.train. For
example, from CytoNorm.train, I get one of these:
Error in UpdateFlowSOM(fsom) : fsom should be a FlowSOM object.
It's not hard to trace the cause of this to here
<https://github.com/saeyslab/CytoNorm/blob/e94732cec4ce26c44d167c530978b2c5b296e55c/R/CytoNorm.R#L252>,
where fsom$FlowSOM will yield a NULL for the newer format fsom object
generated by prepareFlowSOM. There are also a few other locations that
seem to directly depend on the old FlowSOM object structure.
Please let me know if I'm just missing something. I could also probably
put together a quick patch PR as this should be pretty straightforward.
Thanks,
Jake
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOS72ZCYDALIQIKUVE7KDTTQ773ZANCNFSM46BUN4LQ>
.
|
Thanks! It looked like there were just a few more simple changes needed in some of the evaluation functions. I put those in #25, just as an easy way to highlight them. |
Sorry for the delay in closing this. I didn't see that you had merged that PR. Thanks again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Sofie,
I could be wrong, but it seems like CytoNorm's internal handling of FlowSOM objects may need to be updated after the Big Update commit to FlowSOM reorganized the list structure.
If I install both packages from the current GitHub master branches (or FlowSOM from Bioconductor 3.13) and attempt to run through the examples from the README, I run into issues from
testCV
orCytoNorm.train
. For example, fromCytoNorm.train
, I get one of these:It's not hard to trace the cause of this to here, where
fsom$FlowSOM
will yield aNULL
for the newer formatfsom
object generated byprepareFlowSOM
. There are also a few other locations that seem to directly depend on the oldFlowSOM
object structure.Please let me know if I'm just missing something. I could also probably put together a quick patch PR as this should be pretty straightforward.
Thanks,
Jake
The text was updated successfully, but these errors were encountered: