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
I wonder what does "allow functions to retain order" mean?
This can be a good option if we have a lot of functions and some may have namespace collision with other packages. I doubt if that's necessary for now.
Let's bring this up in the next talk.
Good idea.
ditto
ditto; do we want to test the water with a creating package for BIDS? I've taken a look at their Python package, it's pretty simple compared to WFDB.
I wonder what does "allow functions to retain order" mean?
I think it means we don't have to reorganize the order of functions within .R scripts.
This can be a good option if we have a lot of functions and some may have namespace collision with other packages. I doubt if that's necessary for now.
It could also help with user-friendliness; newer users who aren't as familiar with function names and purposes might like the tab-completion option of psyphr_* or psyphr_tidy_*.
She said creating geoms is difficult and would help when the time came.
ditto
Ditto what? Good idea or paste on Monday's agenda?
ditto; do we want to test the water with a creating package for BIDS? I've taken a look at their Python package, it's pretty simple compared to WFDB.
I think we should get this package out the door first then explore the modular options. We should be very deliberate in how we name things, though. Maybe "psyphr" should be the umbrella package.
In addition to reading
consider (@geanders suggestions):
psyphr_read_wb()
)mutate
to allow users to bring in non-MindWare datalubridate
ortidyr
for examples of maintaining consistency across functions and packages (e.g.,verbose = TRUE
option within function)The text was updated successfully, but these errors were encountered: