home.social

#quartopub — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #quartopub, aggregated by home.social.

fetched live
  1. Well if you use GitHub to post to your Quarto blog on Netlify and have something time-sensitive (I do, for my neighborhood blog) . . . too bad, it won't update
    #QuartoPub #GitHub

  2. Well if you use GitHub to post to your Quarto blog on Netlify and have something time-sensitive (I do, for my neighborhood blog) . . . too bad, it won't update
    #QuartoPub #GitHub

  3. Well if you use GitHub to post to your Quarto blog on Netlify and have something time-sensitive (I do, for my neighborhood blog) . . . too bad, it won't update
    #QuartoPub #GitHub

  4. Well if you use GitHub to post to your Quarto blog on Netlify and have something time-sensitive (I do, for my neighborhood blog) . . . too bad, it won't update
    #QuartoPub #GitHub

  5. Well if you use GitHub to post to your Quarto blog on Netlify and have something time-sensitive (I do, for my neighborhood blog) . . . too bad, it won't update
    #QuartoPub #GitHub

  6. I've redesigned my personal homepage (done with #QuartoPub) to focus on being especially resource-light last month and I have had quite a bit of fun with it.

    marioangst.com

    Somewhat ironically or probably saying something about computing in these times, the redesign did involve quite a bit of LLM help and I am not so sure the emissions produced by doing so will ever be made up by the optimization of the page. It is not like thousands visit my page daily ;).

    Also, related and double the irony, I wanted to get the page small enough to serve from a solar-powered, really small raspberry Pi, but had to abandon this because serving it from a small DigitalOcean server is just so much less of a hassle (and I do think likely much more energy efficient) because I do not have to implement all the defenses against bots and AI scrapers myself, compared to *really* serving it myself.

  7. I've redesigned my personal homepage (done with #QuartoPub) to focus on being especially resource-light last month and I have had quite a bit of fun with it.

    marioangst.com

    Somewhat ironically or probably saying something about computing in these times, the redesign did involve quite a bit of LLM help and I am not so sure the emissions produced by doing so will ever be made up by the optimization of the page. It is not like thousands visit my page daily ;).

    Also, related and double the irony, I wanted to get the page small enough to serve from a solar-powered, really small raspberry Pi, but had to abandon this because serving it from a small DigitalOcean server is just so much less of a hassle (and I do think likely much more energy efficient) because I do not have to implement all the defenses against bots and AI scrapers myself, compared to *really* serving it myself.

  8. I've redesigned my personal homepage (done with #QuartoPub) to focus on being especially resource-light last month and I have had quite a bit of fun with it.

    marioangst.com

    Somewhat ironically or probably saying something about computing in these times, the redesign did involve quite a bit of LLM help and I am not so sure the emissions produced by doing so will ever be made up by the optimization of the page. It is not like thousands visit my page daily ;).

    Also, related and double the irony, I wanted to get the page small enough to serve from a solar-powered, really small raspberry Pi, but had to abandon this because serving it from a small DigitalOcean server is just so much less of a hassle (and I do think likely much more energy efficient) because I do not have to implement all the defenses against bots and AI scrapers myself, compared to *really* serving it myself.

  9. I've redesigned my personal homepage (done with #QuartoPub) to focus on being especially resource-light last month and I have had quite a bit of fun with it.

    marioangst.com

    Somewhat ironically or probably saying something about computing in these times, the redesign did involve quite a bit of LLM help and I am not so sure the emissions produced by doing so will ever be made up by the optimization of the page. It is not like thousands visit my page daily ;).

    Also, related and double the irony, I wanted to get the page small enough to serve from a solar-powered, really small raspberry Pi, but had to abandon this because serving it from a small DigitalOcean server is just so much less of a hassle (and I do think likely much more energy efficient) because I do not have to implement all the defenses against bots and AI scrapers myself, compared to *really* serving it myself.

  10. I've redesigned my personal homepage (done with #QuartoPub) to focus on being especially resource-light last month and I have had quite a bit of fun with it.

    marioangst.com

    Somewhat ironically or probably saying something about computing in these times, the redesign did involve quite a bit of LLM help and I am not so sure the emissions produced by doing so will ever be made up by the optimization of the page. It is not like thousands visit my page daily ;).

    Also, related and double the irony, I wanted to get the page small enough to serve from a solar-powered, really small raspberry Pi, but had to abandon this because serving it from a small DigitalOcean server is just so much less of a hassle (and I do think likely much more energy efficient) because I do not have to implement all the defenses against bots and AI scrapers myself, compared to *really* serving it myself.

  11. RE: mastodon.social/@rmflight/1170

    So this ended up saving us 30G of disk space, and cutting the generation time in 1/2, from over 48 hours to just over 24 hours. That's some nice savings in this really ginormouse #RStats {targets} pipeline.

    The actual #QuartoPub filter I'm using is here: github.com/klausbrunner/conver

  12. RE: mastodon.social/@rmflight/1170

    So this ended up saving us 30G of disk space, and cutting the generation time in 1/2, from over 48 hours to just over 24 hours. That's some nice savings in this really ginormouse #RStats {targets} pipeline.

    The actual #QuartoPub filter I'm using is here: github.com/klausbrunner/conver

  13. RE: mastodon.social/@rmflight/1170

    So this ended up saving us 30G of disk space, and cutting the generation time in 1/2, from over 48 hours to just over 24 hours. That's some nice savings in this really ginormouse #RStats {targets} pipeline.

    The actual #QuartoPub filter I'm using is here: github.com/klausbrunner/conver

  14. RE: mastodon.social/@rmflight/1170

    So this ended up saving us 30G of disk space, and cutting the generation time in 1/2, from over 48 hours to just over 24 hours. That's some nice savings in this really ginormouse #RStats {targets} pipeline.

    The actual #QuartoPub filter I'm using is here: github.com/klausbrunner/conver

  15. RE: mastodon.social/@rmflight/1170

    So this ended up saving us 30G of disk space, and cutting the generation time in 1/2, from over 48 hours to just over 24 hours. That's some nice savings in this really ginormouse #RStats {targets} pipeline.

    The actual #QuartoPub filter I'm using is here: github.com/klausbrunner/conver

  16. This makes sense, but I had to think about it.

    If you are creating #RStats #QuartoPub HTML reports that are self-contained, the images have to be created, **and embedded** in the document. The smaller the image file, **the less time it takes to embed it**, as well as making the result file smaller.

    Probably not really noticeable on a single report. But adds up to minutes saved when generating 200 docs, even in parallel.

  17. This makes sense, but I had to think about it.

    If you are creating #RStats #QuartoPub HTML reports that are self-contained, the images have to be created, **and embedded** in the document. The smaller the image file, **the less time it takes to embed it**, as well as making the result file smaller.

    Probably not really noticeable on a single report. But adds up to minutes saved when generating 200 docs, even in parallel.

  18. This makes sense, but I had to think about it.

    If you are creating #RStats #QuartoPub HTML reports that are self-contained, the images have to be created, **and embedded** in the document. The smaller the image file, **the less time it takes to embed it**, as well as making the result file smaller.

    Probably not really noticeable on a single report. But adds up to minutes saved when generating 200 docs, even in parallel.

  19. This makes sense, but I had to think about it.

    If you are creating #RStats #QuartoPub HTML reports that are self-contained, the images have to be created, **and embedded** in the document. The smaller the image file, **the less time it takes to embed it**, as well as making the result file smaller.

    Probably not really noticeable on a single report. But adds up to minutes saved when generating 200 docs, even in parallel.

  20. This makes sense, but I had to think about it.

    If you are creating #RStats #QuartoPub HTML reports that are self-contained, the images have to be created, **and embedded** in the document. The smaller the image file, **the less time it takes to embed it**, as well as making the result file smaller.

    Probably not really noticeable on a single report. But adds up to minutes saved when generating 200 docs, even in parallel.

  21. Wow. Thanks to webp and reduced resolution, went from 44 MB to 18 MB on one of the bigger QC/QA dataset html reports I'm generating.

    Seems really weird that I can't just plug in {ragg::agg_webp} into the device slot of the {knitr} options of my #QuartoPub files. But the filter someone else built seems to work well enough.

  22. Wow. Thanks to webp and reduced resolution, went from 44 MB to 18 MB on one of the bigger QC/QA dataset html reports I'm generating.

    Seems really weird that I can't just plug in {ragg::agg_webp} into the device slot of the {knitr} options of my #QuartoPub files. But the filter someone else built seems to work well enough.

  23. Wow. Thanks to webp and reduced resolution, went from 44 MB to 18 MB on one of the bigger QC/QA dataset html reports I'm generating.

    Seems really weird that I can't just plug in {ragg::agg_webp} into the device slot of the {knitr} options of my #QuartoPub files. But the filter someone else built seems to work well enough.

  24. Wow. Thanks to webp and reduced resolution, went from 44 MB to 18 MB on one of the bigger QC/QA dataset html reports I'm generating.

    Seems really weird that I can't just plug in {ragg::agg_webp} into the device slot of the {knitr} options of my #QuartoPub files. But the filter someone else built seems to work well enough.

  25. Wow. Thanks to webp and reduced resolution, went from 44 MB to 18 MB on one of the bigger QC/QA dataset html reports I'm generating.

    Seems really weird that I can't just plug in {ragg::agg_webp} into the device slot of the {knitr} options of my #QuartoPub files. But the filter someone else built seems to work well enough.

  26. The emojis never lie.
    I was excited to try Quartorium mentioned in this post: nrennie.rbind.io/blog/collabor
    Supposedly it provides WYSIWYG collaboration in #quartoPub documents. My spidey sense started tingling when I saw all the emojis in the readme. I tried it and the install script doesn't even work. Looking at the commit messages, the thing looks to be wholly vivecoded and semi-abandonned.

    #RStats

  27. The emojis never lie.
    I was excited to try Quartorium mentioned in this post: nrennie.rbind.io/blog/collabor
    Supposedly it provides WYSIWYG collaboration in #quartoPub documents. My spidey sense started tingling when I saw all the emojis in the readme. I tried it and the install script doesn't even work. Looking at the commit messages, the thing looks to be wholly vivecoded and semi-abandonned.

    #RStats

  28. The emojis never lie.
    I was excited to try Quartorium mentioned in this post: nrennie.rbind.io/blog/collabor
    Supposedly it provides WYSIWYG collaboration in #quartoPub documents. My spidey sense started tingling when I saw all the emojis in the readme. I tried it and the install script doesn't even work. Looking at the commit messages, the thing looks to be wholly vivecoded and semi-abandonned.

    #RStats

  29. The emojis never lie.
    I was excited to try Quartorium mentioned in this post: nrennie.rbind.io/blog/collabor
    Supposedly it provides WYSIWYG collaboration in #quartoPub documents. My spidey sense started tingling when I saw all the emojis in the readme. I tried it and the install script doesn't even work. Looking at the commit messages, the thing looks to be wholly vivecoded and semi-abandonned.

    #RStats

  30. The emojis never lie.
    I was excited to try Quartorium mentioned in this post: nrennie.rbind.io/blog/collabor
    Supposedly it provides WYSIWYG collaboration in #quartoPub documents. My spidey sense started tingling when I saw all the emojis in the readme. I tried it and the install script doesn't even work. Looking at the commit messages, the thing looks to be wholly vivecoded and semi-abandonned.

    #RStats

  31. Sneak peek at a new interactive project exploring historic temperature trends across Scotland

    #RStats #DataViz #ggplot2 #QuartoPub

  32. Sneak peek at a new interactive project exploring historic temperature trends across Scotland

  33. Sneak peek at a new interactive project exploring historic temperature trends across Scotland

    #RStats #DataViz #ggplot2 #QuartoPub

  34. Sneak peek at a new interactive project exploring historic temperature trends across Scotland

    #RStats #DataViz #ggplot2 #QuartoPub

  35. Sneak peek at a new interactive project exploring historic temperature trends across Scotland

    #RStats #DataViz #ggplot2 #QuartoPub

  36. I'm shortly about to generate ~6100 QC/QA reports for datasets in Metabolomics Workbench, and thank you so much for the rich HTML reporting ecosystem in #RStats + #QuartoPub that means I can easily have callouts and tabsets in my report to make it take up less space, and easily click through a variety of related tables.

  37. I'm shortly about to generate ~6100 QC/QA reports for datasets in Metabolomics Workbench, and thank you so much for the rich HTML reporting ecosystem in #RStats + #QuartoPub that means I can easily have callouts and tabsets in my report to make it take up less space, and easily click through a variety of related tables.

  38. I'm shortly about to generate ~6100 QC/QA reports for datasets in Metabolomics Workbench, and thank you so much for the rich HTML reporting ecosystem in #RStats + #QuartoPub that means I can easily have callouts and tabsets in my report to make it take up less space, and easily click through a variety of related tables.

  39. I'm shortly about to generate ~6100 QC/QA reports for datasets in Metabolomics Workbench, and thank you so much for the rich HTML reporting ecosystem in #RStats + #QuartoPub that means I can easily have callouts and tabsets in my report to make it take up less space, and easily click through a variety of related tables.

  40. I'm shortly about to generate ~6100 QC/QA reports for datasets in Metabolomics Workbench, and thank you so much for the rich HTML reporting ecosystem in #RStats + #QuartoPub that means I can easily have callouts and tabsets in my report to make it take up less space, and easily click through a variety of related tables.

  41. 🚨 New blog post! 🚨

    Collaborating on Quarto documents can be tricky, especially if you're working with people who don't need to write code 🫂 So I've pulled together some of the options for collaborating on Quarto documents into a blog post!

    Link: nrennie.rbind.io/blog/collabor

    #QuartoPub #RStats

  42. 🚨 New blog post! 🚨

    Collaborating on Quarto documents can be tricky, especially if you're working with people who don't need to write code 🫂 So I've pulled together some of the options for collaborating on Quarto documents into a blog post!

    Link: nrennie.rbind.io/blog/collabor

  43. 🚨 New blog post! 🚨

    Collaborating on Quarto documents can be tricky, especially if you're working with people who don't need to write code 🫂 So I've pulled together some of the options for collaborating on Quarto documents into a blog post!

    Link: nrennie.rbind.io/blog/collabor

    #QuartoPub #RStats

  44. 🚨 New blog post! 🚨

    Collaborating on Quarto documents can be tricky, especially if you're working with people who don't need to write code 🫂 So I've pulled together some of the options for collaborating on Quarto documents into a blog post!

    Link: nrennie.rbind.io/blog/collabor

    #QuartoPub #RStats

  45. 🚨 New blog post! 🚨

    Collaborating on Quarto documents can be tricky, especially if you're working with people who don't need to write code 🫂 So I've pulled together some of the options for collaborating on Quarto documents into a blog post!

    Link: nrennie.rbind.io/blog/collabor

    #QuartoPub #RStats

  46. I would have thought a perfect use case for #QuartoPub "includes" would be something like:

    ```{r}
    #| label: conditional-include
    if ( condition1) {
    {{< include _condition1.qmd >}}
    } else {
    {{< include _condition2.qmd >}}
    }
    ```

    But {quarto} complains about incomplete input if I actually do that. But both docs look fine.

    Guess it's figuring out the whole document pieces to include *outside* first, `cat` together, and then `render`.

    #RStats

  47. I would have thought a perfect use case for #QuartoPub "includes" would be something like:

    ```{r}
    #| label: conditional-include
    if ( condition1) {
    {{< include _condition1.qmd >}}
    } else {
    {{< include _condition2.qmd >}}
    }
    ```

    But {quarto} complains about incomplete input if I actually do that. But both docs look fine.

    Guess it's figuring out the whole document pieces to include *outside* first, `cat` together, and then `render`.

    #RStats

  48. I would have thought a perfect use case for #QuartoPub "includes" would be something like:

    ```{r}
    #| label: conditional-include
    if ( condition1) {
    {{< include _condition1.qmd >}}
    } else {
    {{< include _condition2.qmd >}}
    }
    ```

    But {quarto} complains about incomplete input if I actually do that. But both docs look fine.

    Guess it's figuring out the whole document pieces to include *outside* first, `cat` together, and then `render`.

    #RStats

  49. I would have thought a perfect use case for #QuartoPub "includes" would be something like:

    ```{r}
    #| label: conditional-include
    if ( condition1) {
    {{< include _condition1.qmd >}}
    } else {
    {{< include _condition2.qmd >}}
    }
    ```

    But {quarto} complains about incomplete input if I actually do that. But both docs look fine.

    Guess it's figuring out the whole document pieces to include *outside* first, `cat` together, and then `render`.

    #RStats

  50. I would have thought a perfect use case for #QuartoPub "includes" would be something like:

    ```{r}
    #| label: conditional-include
    if ( condition1) {
    {{< include _condition1.qmd >}}
    } else {
    {{< include _condition2.qmd >}}
    }
    ```

    But {quarto} complains about incomplete input if I actually do that. But both docs look fine.

    Guess it's figuring out the whole document pieces to include *outside* first, `cat` together, and then `render`.

    #RStats

  51. The entire article is data-driven using #RStats, and built with #QuartoPub. You can read the whole thing here: nrennie.rbind.io/data-stories/

  52. The entire article is data-driven using , and built with . You can read the whole thing here: nrennie.rbind.io/data-stories/

  53. The entire article is data-driven using #RStats, and built with #QuartoPub. You can read the whole thing here: nrennie.rbind.io/data-stories/

  54. The entire article is data-driven using #RStats, and built with #QuartoPub. You can read the whole thing here: nrennie.rbind.io/data-stories/

  55. The entire article is data-driven using #RStats, and built with #QuartoPub. You can read the whole thing here: nrennie.rbind.io/data-stories/

  56. This week's #TidyTuesday data compares baby names in Scotland, Northern Ireland, and England & Wales 📊

    One of the interesting things about this data is that you can often spot trends related to current events 👸

    Code: github.com/nrennie/tidytuesday

    #DataViz #ggplot2 #RStats #QuartoPub

  57. This week's data compares baby names in Scotland, Northern Ireland, and England & Wales 📊

    One of the interesting things about this data is that you can often spot trends related to current events 👸

    Code: github.com/nrennie/tidytuesday

  58. This week's #TidyTuesday data compares baby names in Scotland, Northern Ireland, and England & Wales 📊

    One of the interesting things about this data is that you can often spot trends related to current events 👸

    Code: github.com/nrennie/tidytuesday

    #DataViz #ggplot2 #RStats #QuartoPub

  59. This week's #TidyTuesday data compares baby names in Scotland, Northern Ireland, and England & Wales 📊

    One of the interesting things about this data is that you can often spot trends related to current events 👸

    Code: github.com/nrennie/tidytuesday

    #DataViz #ggplot2 #RStats #QuartoPub

  60. This week's #TidyTuesday data compares baby names in Scotland, Northern Ireland, and England & Wales 📊

    One of the interesting things about this data is that you can often spot trends related to current events 👸

    Code: github.com/nrennie/tidytuesday

    #DataViz #ggplot2 #RStats #QuartoPub