Good morning, Urs - I am working with @meghansharris@jacquietran, and Antonio Sanchez on a book on generative art using R.
As part of the book, we would like to interview a few generative artists that we like and ask for permission to use their responses in the text. We believe that this will give a broader perspective on current trends on generative art. We have a preliminary questionnaire, and we'd be happy if you wanted to respond in writing, or to chat with us.
@paezha@meghansharris@jacquietran
Hi Antonio
Good morning from Berlin! :)
That sounds really interesting. Thanks for contacting me! Feel free to send me the questionnaire, or if you prefer to chat, that would also be nice. ☺️
Looking for beginner resources for R package development. Specifically, I've got a package where I need to make some moderately large changes in a function, and I need to keep the package usable in its current stage on my machine while I develop and test the new version. How does one do this? I don't think this is a git question, I think this is an R question. #rstats
I also like the approach to develop new functionality directly in the debugger where it happens. Like @tylermorganwall suggested but not with functions but rather new dev objects that can be successively developed and compared next to the original ones.
As soon as you have what you want you can then move the new code to its own functions etc. and finally remove and replace the old functionality when everything works
It's the beginnings of an #rstats package for experimental mangling of #MIDI files. TBH, it's my personal experimental hacky-code base wrapped in R package clothing. I'm messing with it constantly, and sharing in case others are interested. #genRativemusic#Rmuzak#rstatsmusic
Soo nice to see you doing all these things with midi in R. I'm really happy to have contributed to your adventures and feel honoured that you dived so deeply into my packages.
I meant to write much earlier, but every time I looked back at your posts you had already produced new things and I wanted to catch up first. Really love the energy how you write about your journeys on your blog. Seeing this new package now is truly amazing! Congrats!!
I might need to manipulate and synthesize midi in R, so I spent the afternoon trying to make various packages work. They are all wrappers for python stuff. It wasn't a cake walk, but I finally made an mp3 of the top gun theme song = declaring victory
Really nice to hear that you used the pyramidi package I've written some time ago!
I hope it wasn't too frustrating. You have to feel adventurous to use it.
The package is highly experimental and doesn't work for all sorts of midi files. And it was a bit cumbersome to harmonize the development with the related python package...
Thanks for the kind words! I'm really glad if it could help.
I think I was about to learn OOP when writing this package 😺
And I have looked at your blog post again. Super nice to see you using these packages and pivoting notes on your own and got something working out!! (this was my main motivation writing these packages: I thought having note_on & _off events on the same line in a dataframe could help wrangling with #midi data..)
Regarding the silence at the end of the track, I checked the R code and everything seems right. I also guess it has to do something with the python code.
Has any #RStats user within reach has used the groundhog package? I tested it and it was very hard to get it going (I had to run R with R --vainilla) and then it botched my user library. Perhaps I did something very wrong.
Anyone know if there is a way to make a pkgdown site hosted on GitHub private? So people can’t just go to packagename.github.io/packagename willy nilly? I set it up with usethis::use_pkgdown_github_pages
@jimgar but iiuc it's a local site and not a website then - strictly speaking :)
and how do you make sure that the pkgdown site is up-to-date? - that's what I like most about deploying it on github/gitlab: I don't need to rerun
pkgdown::build_site()
after updating the code.
and I also prefer browsing the pkgdown sites rather than the R help in RStudio for instance
The important part is to put the $ at the end of the line and not in the next line, as R then continues to parse the following line and perceive it as one expression,
(Like with pipes, but also works for other stuff like +, &, etc...).
In other words: as long as it's not a complete expression at the end of the line, the parser continues adding the following line.
I think I recently read that somewhere but I forgot where
I think I need to start muting white cishet men talking about how [insert name of social media site that is grossly toxic to minorities] is fun for them. I can't deal with that in my life right now