They are migrating the api to a new domain and browning out the old one to get folks to switch over and figure out if there are any issues. There is also another infrastructure change going on as well.
Normally those would be posted on https://www.weather.gov/notification/ but that’s having hiccups, but the email list for announcements still works.
For as much improvement as there has been with what can be distributed via PyPI, there are still some domains that have gnarlier dependencies than wheels happily handle alone, and you either need to reach for the system package manager (and loose the ability to really control the dependency environment from that mismatch), or take advantage of the Conda ecosystem.
My org does a lot of work combining machine learning with oceanographic and climate modeling, which are both domains that have deep dependency chains that don't always mesh well, especially as our researchers mix in R and other languages as the same time, and the Conda ecosystem helps us a ton with that, but there are issues that `conda` and `mamba` don't help us out with.
Pixi takes a swing at some of what the Conda ecosystem hasn't been great at (at least without a lot of manual custom ceremony) that Cargo, Poetry, Pipenv, PDM, and other dependency and workflow management tools have demonstrated can be done such as lock files, cross platform dependency management, task running, and defining multiple related environments.
Have you tried https://pixi.sh/ ? It brings Cargo/NPM/Poetry like commands and lock files to the Conda ecosystem, and now can manage and lock PyPI dependencies alongside by using uv under the hood.
I haven't been using anything CUDA, but the scientific geospatial stack is often a similar mess to install, and it's been handling it really well.
I gotthe habit of using 4” barrier webbing tape with gaffers on either side to make wire chases. That way there was nothing stuck to the cables and if another cable needed to run the same route, one side could be lifted, the cable slid in, and then reapplied.
I remember reading that paper when I was trying to figure out why we were having issues with a wireless link down in the Patagonia fjords.
Unfortunately we didn't have the hardware or enough control over the link (it took negotiating access with armed forces to work on either end) to try to implement any of their ideas.
Gaia GPS is fantastic. You can mix and match layers, and specify what bounds you want to download for a trip.
Right now I've got 3 GB stored locally, some of that for the usual locations that I wander out of connectivity, and some for a trip next week.
Garmin (formerly Delorme) Earthmate despite their other issues is great for state or province wide vector maps. Not as great for fine navigation and tracking (as it's designed to be paired with and control an InReach), but good for point of interest exploration.
Gulf of Maine Research Institute | Web Application Developer | Portland, ME | Full Time
If you like science or the ocean, know technology, and want to use tech to push science forwards, we’re looking for a Web Application Developer at Gulf of Maine Research Institute as part of the Ocean Data Products team.
GMRI is right on the waterfront in Portland Maine, where we work at the intersection of people and the ocean.
For a little detail of what the ODP team does, here’s a little of what I’ve been working on recently:
- Testing knowledge graph ontologies for a NSF project that is trying to push the domains of scientific modeling forwards
- Developing a citizen science platform designed to support classrooms and projects that need a coverage to prove presence vs absence
- Geeked out with USGS about low cost sensor platforms at the ESIP conference
- Evolving the user focused components of NERACOOS’s interface to the buoys in the Gulf of Maine and beyond to make it more approachable to regular mariners (fishermen, sailors, surfers) than just scientists.
- Prototyping transitioning our primary data service (ERDDAP) for NERACOOS to run on Kubernetes.
Or in the tech stack flavor: AWS, Digital Ocean, Kubernetes, Python, JavaScript, ERDDAP, THREDDS, Django, PostGIS, some flavor of graph database to be decided soon...
For a sense of scale, roughly 5,000 live on my peninsula between the towns. The summer populations is probably about 10x that plus any weekend visitors.
It makes it really hard for restaurants to stay open during the off season, and even the Hannaford's market can't be sized right. It's a bit big for the population right now, but it feels like Black Friday on weekends during the summer.
The towns have been working to bring more off season events to even things out, but most aren't working (the one notable exception brought in 160,000ish customers in it's second 6 week run).
The total seismic moment energy for a 8.1 magnitude quake is roughly 1.7 * 10^21 Joules.
For comparison, Tsar Bomba (the largest nuke ever built) as tested was around 50 megatons of TNT or 210 Petajoules 2.1 * 10^17.
So you would roughly need 8000 Tsar Bombas triggered in just the right pattern to make their force additive in order to release that much energy into the plate.
I have a sneaking suspicion that if you could mine all the material for those Tsar Bombas in the same place, isostasy would give you equal or greater response from the plate, but I'm not going to do those equations right now.
I'm working on one. I am waiting for a PR to land and a release to get generated for a bug that I found.
If the master pod in a StatefulSet is deleted, and kubernetes sets up a new one too fast, it currently keeps the master lock and failover never happens (it also tries to bootstrap from itself).
Once those land I'll work on a writeup of that setup
I've got a few Postgres instances running as single node Deployments and StatefulSets right now that backup and restore using pghoard for simple services that I've documented here http://alexkerney.com/2016/10/pghoard-kubernetes.html I do need to add a note about using livenessprobes to make sure the restore completed successfully. Sometimes these pods are cycled every day as half my K8S cluster is preemptable.
It's a bit scary when you're using K8S ephemeral storage and depending on a basebackup from another pod, but you can also set it up to restore from your usual backup system (WAL-E, pghoard, barman, pgBackrest). That way any time you lose a pod, you get a test of your backup system on restore.
Normally those would be posted on https://www.weather.gov/notification/ but that’s having hiccups, but the email list for announcements still works.
A few of the recent announcements: - https://www.weather.gov/media/notification/pdf_2023_24/scn24... - https://www.weather.gov/media/notification/pdf_2023_24/scn24... - https://www.weather.gov/media/notification/pdf_2023_24/scn24...