home.social

Search

19 results for “hughagraham”

  1. @hughagraham @esa Depending on what type of SAR data you'll use, you can often (application dependent) get away with using already RTC'ed ARD data (e.g., from #PlanetaryComputer), and by using fairly simple speckle reduction filters (mostly, they are ways of cleverly blurring images). For polarimetric or interferometic data, things are more complex. Let us know how you're getting on!

  2. Anyone else having a load of breaking changes with the new geometry handling in >1.5.0?

  3. @mdsumner am I being silly or would all of this be solved already if we could serialize the vsicache and reuse it between sessions?

  4. @mdsumner am I being silly or would all of this be solved already if we could serialize the #gdal vsicache and reuse it between sessions?

  5. @mdsumner am I being silly or would all of this be solved already if we could serialize the #gdal vsicache and reuse it between sessions?

  6. Getting very into a5 right now, its such a clever geospatial index when you get into it! A bunch of new functions have landed in {a5R} including new traversal functions and paired cell distance calculation. belian-earth.github.io/a5R/art

  7. If you use and I'd love to know what you think of this:

    `duckdb-r-editor` a Positron extension for duckdb SQL code highlighting and completion within R files.

    github.com/belian-earth/duckdb

    A big chunk of this has been vibe coded, I know this gets a bad rep on mastodon but this extension makes writing SQL in R so much nicer (for me at least) so in theory it'll mean I can use less AI from here on ...
    ✌️

  8. So today I vibe coded a /vscode extension to detect SQL strings (in R scripts) called by {DBI} and other common packages with functions that call SQL strings, it then provides code completion/suggestions. It also has super buggy code highlighting. Oh and it only really works with . It's so rough right now but I feel like it would be amazingly useful if it worked well, does anything like this already exist / can someone build a stable version of it please 🤣 ?

  9. So today I vibe coded a #positron /vscode extension to detect SQL strings (in R scripts) called by {DBI} and other common packages with functions that call SQL strings, it then provides code completion/suggestions. It also has super buggy code highlighting. Oh and it only really works with #duckdb. It's so rough right now but I feel like it would be amazingly useful if it worked well, does anything like this already exist / can someone build a stable version of it please 🤣 ? #rstats #posit

  10. So today I vibe coded a #positron /vscode extension to detect SQL strings (in R scripts) called by {DBI} and other common packages with functions that call SQL strings, it then provides code completion/suggestions. It also has super buggy code highlighting. Oh and it only really works with #duckdb. It's so rough right now but I feel like it would be amazingly useful if it worked well, does anything like this already exist / can someone build a stable version of it please 🤣 ? #rstats #posit

  11. So today I vibe coded a #positron /vscode extension to detect SQL strings (in R scripts) called by {DBI} and other common packages with functions that call SQL strings, it then provides code completion/suggestions. It also has super buggy code highlighting. Oh and it only really works with #duckdb. It's so rough right now but I feel like it would be amazingly useful if it worked well, does anything like this already exist / can someone build a stable version of it please 🤣 ? #rstats #posit

  12. So today I vibe coded a #positron /vscode extension to detect SQL strings (in R scripts) called by {DBI} and other common packages with functions that call SQL strings, it then provides code completion/suggestions. It also has super buggy code highlighting. Oh and it only really works with #duckdb. It's so rough right now but I feel like it would be amazingly useful if it worked well, does anything like this already exist / can someone build a stable version of it please 🤣 ? #rstats #posit

  13. Hey fam! If anyone fancies kicking the tyres of this in-development R package for downloading data, I'd love any feedback. Still a bit rough around the edges but keen to improve it however possible! github.com/Permian-Global-Rese

  14. Hey #rstats #rspatial fam! If anyone fancies kicking the tyres of this in-development R package for downloading #gedi data, I'd love any feedback. Still a bit rough around the edges but keen to improve it however possible! github.com/Permian-Global-Rese

  15. Hey #rstats #rspatial fam! If anyone fancies kicking the tyres of this in-development R package for downloading #gedi data, I'd love any feedback. Still a bit rough around the edges but keen to improve it however possible! github.com/Permian-Global-Rese

  16. Hey #rstats #rspatial fam! If anyone fancies kicking the tyres of this in-development R package for downloading #gedi data, I'd love any feedback. Still a bit rough around the edges but keen to improve it however possible! github.com/Permian-Global-Rese

  17. Hey #rstats #rspatial fam! If anyone fancies kicking the tyres of this in-development R package for downloading #gedi data, I'd love any feedback. Still a bit rough around the edges but keen to improve it however possible! github.com/Permian-Global-Rese

  18. hey folks, is there an issue with the ecosystem at the moment - I'm having a lot of compatibility issues and can see that there is a lot of refactoring going on with some core dependencies... anyone else experiencing this?

  19. Hey fam, I have just posted a question about generating bootsrapped resamples for ensemble models - any help would be a massive help - thankyou!
    stackoverflow.com/questions/75