Ben Matthews

  • New here on lemmy, will add more info later …
  • Also on mdon: @[email protected]
  • Try my interactive climate / futures model: SWIM
  • 0 Posts
  • 28 Comments
Joined 10 months ago
cake
Cake day: September 15th, 2023

help-circle


  • Hi, excuse me for replying so late, but i’ve been away from lemmy for.a while. Well, to summarise, the model calculates the future trajectories, of population, economy, emissions, atmospheric gases, and climate response etc., according to a set of (hundreds of) diverse options and uncertainties which you can adjust - the key feature is that the change shows rapidly enough to let you follow cause -> effect, to understand how the system responds in a quasi-mechanical way.
    Indeed you are right, complexity is beautiful, but hard. A challenge with such tools is to adjust gradually from simple to complex. Although SWIM has four complexity levels, they are no longer systematically implemented - also what seems simple or complex varies depending where each person is coming from, so i think to adapt the complexity filter into a topic-focus filter. Much todo …




  • I can relate to this, having developed a coupled socio-emissions-carbon-climate model, which evolved for 20 years in java, until recently converted to scala3. You can have a look here. The problem is that “coupling” in such models of complex systems is a ‘good’ thing, as there are feedbacks - for example atmospheric co2 drives climate warming but the latter also changes the carbon cycle, demography drives economic growth but the latter influences fertility and migration, etc… (some feedbacks are solved by extrapolating from the previous timestep - the delay is anyway realistic). There are also policy feedbacks - between top-down climate-stabilisation goals, and bottom up trends and national policies, the choice affects the logical calculation order. All this has to work fast within the browser (now scala.js - originally java applet), responding interactively to parameter adjustments, only recalculating curves which changed - getting all these interactions right is hard.
    If restarting in scala3 I’d structure it differently, but having a lot of legacy science code known to work, it’s hard to pull it apart. Wish I’d known such principles at the beginning, but as it grew gradually, one doesn’t anticipate such complexity.


  • There is no climate panacea, only baskets of solutions. Bamboo has remarkable properties from an engineering pov - strong light hollow tubes, and so could be used more to substitute for plastics and metals, in relatively short-lived products (which most are). You are right that it’s not so durable as wood from trees, and it’s more suited to wet climates. I have several kinds in my garden, green in winter, grape vines dangle along it in summer, a shallow root barrier (old tiles) contain it.




  • No. Sea-level is rising, much of Lagos will be underwater. So they’ll have to relocate. It’s slow so more people could live there for the next few decades, but mega-construction not be a wise investment.
    Demographic projections have a lot of inertia, but sea-level rise (transfer of heat into the deep ocean and icecaps) has even more inertia (in my model i explore both, although sorry SLR is out-of-date and not yet detail at city level, but the inertia is there).









  • Too true.
    I still remember when java5 came out, many new features, great potential for a massive refactoring of my interactive climate model. Within that, I had an idea called “parallel worlds” for comparing scenarios, whereby for efficiency data was shared for parts of the system, and split across parts that varied as user adjusted parameters. So I pulled apart the whole codebase, and joined it back together again… - about two years later, by which time colleagues had given up interest.
    [ story simplified to relate to point of OP - not only task in two years! ].
    Now I develop a derivative climate system model in scala, but evidently it’s more interesting to develop some new complex part of the science code, than fix a graphical interface for beginners. But moods vary - some days lacking energy for refactoring, could be satisfied ticking off a few small tasks in a todo list. Yet after some time, brain craving for another big new complex idea…



  • It’s only 5th December, seems unusually early for -58º. From Wikipedia - Yakutsk, maybe daily min should be about -37º now. I recall crossing Siberia by train in early December, rain in west, fresh snow in east, lakes still water, yet coming back in April you could still walk on Baikal. Seems odd, but they get extra problem of fires in winter, as fire hoses freeze, can’t extinguish them. Anyway polar vortex went wobbly recently, so we get alternating cold and warm waves - always look for both sides of regional anomalies.