-
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
Want to join this working group? #2
Comments
Thanks for the invitation to join. . Happy to help in any way I can! R's Serialisation powers some things I've written: e.g. {xxhashlite}, rlang::hash(). I'm also interested in some low level aspects of R e.g. {rbytecode}. |
Hey yall—more than happy to tag along. Simon from Chicago, IL, USA—I work on packages for predictive modeling at Posit. We end up thinking about marshaling/serialization a good bit in the context of model deployment and training in parallel. Re: model deployment, we put together a package for marshaling model objects last year that standardizes interfaces to serialization methods from different modeling packages. The issue of serialization also comes up in our support for parallel processing, where various models may be fitted in several R processes but handed back to a parent process for analysis. cc @juliasilge and @topepo. I won't be able to make it to useR! in person, but Max will be there for the in-person meeting. |
Not sure how much time I'll have to participate, but I'll try to follow what goes on and chip in from time to time. I developed the current serialization framework a number of years ago. The main goals of that redesign of what came before were to support parallel computation and separate loading of objects in a collection while maintaining identity of mutable objects, mainly environments (i.e. lazy loading). |
This feature was originally motivated by parallel computations involving torch tensors, as described in https://shikokuchuo.net/mirai/articles/torch.html, and following helpful discussions with @dfalbel. Permitted usage was subsequently broadened to a much wider class of serialization functions, as described in https://shikokuchuo.net/mirai/articles/mirai.html#serialization-arrow-polars-and-beyond, which also benefited from input by @eitsupi. Finally, it also allows hosting of ADBC database connections in parallel processes as described in https://shikokuchuo.net/mirai/articles/databases.html, where @krlmlr was instrumental in proposing and verifying this use case. |
Thanks for the invite. I develop |
Thanks for the invite. I'm one of the developers in Great to meet with you @wlandau. I am using your package |
Hi all, Tomasz here from mlverse at Posit. I'm more than happy to help out too. I am particularly interested in making sure S7, reticulate, TensorFlow/Jax/Keras, torch, and things like it (R external ptrs, potentially complex environment requirements) work well with whatever the final solution is. |
@HenrikBengtsson can you add @t-kalinowski to the team, I don't have the rights to do so |
Welcome Tomasz - great to have you on board.
Invite sent for the https://github.com/orgs/RConsortium/teams/marshalling-wg/ team.
Hmm... that's odd. You've got the "admin" role for this repository, which is the same as I have. It's also the highest possible I can set - there is no "owner" option. It could be that I have higher privileges through my formal membership of the R Consortium, which is why I can send the invite. |
I think that if someone is not part of the org yet then an owner needs to invite them to the org first before a team admin can do any addition. Feel free to email operations@r-consortium.org whenever you need someone added. |
Hi all,
let us know if you'd like to join this working group on 'Marshaling and Serialization in R'. To join, just add a comment below with a very brief introduction of yourself and your interest is in this topic.
The text was updated successfully, but these errors were encountered: