-
Notifications
You must be signed in to change notification settings - Fork 2
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
How to identify gaps or critical dyads on the lower level? #65
Comments
Thanks for writing in! If you could provide a reprex, that would be great so we can investigate further. Also check that the motif even exists in that configuration. Could it be that you might be helped by specifying the levels in the motif signature? see here: https://marioangst.github.io/motifr/articles/motif_zoo.html under "A word of caution on counting: Position matching". So possibly "1:1,2:0[I.C]" would work. When in doubt, use show_motif to see that your motif label does what you expect it to do. |
Thank you @marioangst for the suggestion. I was able to achieve what I hoped for by specifying the levels. See sample code below:
I still wonder how the |
@meefen the focal level argument is only useful when you have motif where the location of the gap is not apparent. Eg. in a four-cycle, where a gap can be on either level. For triangles, the gap can only be on the level where there are two nodes. Does this make sense? |
Thanks for the reply. Yes it does make sense. For four-node motifs of two nodes for each level, is there a way to capture gaps on a specific level? |
Yes, in this case, the |
It didn't work for me even with the example dataset. I do not have access to my computer right now and can post sample code if needed. |
Oh that would be great, please give us a reprex so we can investigate! |
The motifr documentation does provide useful guidance on how to identify gaps and critical dyads. See example code below:
However, I could not get it to find gaps or critical dyads on the lower level (e.g., level 0). When I tweak the
level
parameter, errors are often reported.Is there a way to identify gaps or critical dyads on the lower level? Thanks.
The text was updated successfully, but these errors were encountered: