You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one sense, it makes sense to have it as a factor (you will often have tables where multiple neurons have the same type). However, factors unless for very well defined sets of levels (think male / female) can trip people up. Specifically @alexanderbates has some code here that is broken
I have decided that neuprint_list2df will have stringsAsFactors=FALSE as a default i.e. always character vector rather than factor. Then you can choose to make a factor explicitly if you want. I think that in the above example type (and name) should not be factors.
In one sense, it makes sense to have it as a factor (you will often have tables where multiple neurons have the same type). However, factors unless for very well defined sets of levels (think male / female) can trip people up. Specifically @alexanderbates has some code here that is broken
neuprintr/vignettes/hemibrain_opns.Rmd
Lines 90 to 91 in 007709c
because he is trying to add new levels to a factor. It would work as is if
type
were a character vector. Thoughts also @romainFr?The text was updated successfully, but these errors were encountered: