OpenNHM

Bevor you keep reading here, head over to the release info of version 1.1 to get all changes that went into it. These changes are basically what we mainly worked on during this month.

However, two additional bits went on:

• the ongoing writing of peer-reviewed papers
• and in relation to that, the EGU 2022 took place. The following contributions are related to AvaFrame:
  • Tonnel, M., Wirbel, A., Oesterle, F., and Fischer, J.-T.: Are avalanche models correct? An uncertain view on convergence, EGU General Assembly 2022, Vienna, Austria, 23–27 May 2022, https://doi.org/10.5194/egusphere-egu22-7745 , 2022.
  • Neuhauser, M., Neurauter, R., Tuermer, S., Gerstmayr, J., Adams, M., Koehler, A., and Fischer, J.-T.: Investigating the potential of GNSS-modules for inflow avalanche measurements, EGU General Assembly 2022, Vienna, Austria, 23–27 May 2022, EGU22-6416, https://doi.org/10.5194/egusphere-egu22-6416 , 2022.

That’s it for this month, and thanks for all the fruitful discussions at the EGU!

Today we released Version 1.1

The benchmark and thickness release. There are two main changes:

• The benchmarks (i.e. reference results) are updated and originate from com1DFA now. Previously these were produced by com1DFAOrig.
• All references to depth are now switched to thickness. This is done to be more consistent and precise. It also means result types switch from pfd / fd (peak flow depth / flow depth) to pft / ft (peak flow thickness / flow thickness). Note that this is purely a naming change; nothing changed regarding the computation!

ENHANCEMENTS

On April 6. we released Version 1.0 !

As you might guess, this is very exciting for us, but what does this mean?

• First of all, you can find all changes in our documentation release notes . As one might expect with a first full release, the list is long!

• Version 1.0 means we can partly fulfil a vital topic of our mission , namely the replicating … current simulation procedures… part. The core computation module com1DFA for dense flow computations is in a state that allows it to be used in operational settings. In this regard, we published a report detailing differences between the currently operationally used com1DFAOrig (i.e. SamosAT) results and our rewritten com1DFA results. See reports for a link to the report (or head over to the assets of the version 1.0 release on Github ). In this document, we detail the steps taken to ensure the similarity of the results, highlight the differences we found, the investigations into numerical issues and our recommendations for operational application.

The info in here is a bit short… This is because there’s a separate post about the main event this month: Version 1.0 is out!! Please head over there to get the full info.

Apart from this we worked on:

• a few fixes regarding init files
• reworking a few AIMEC functions and calculating real areas
• a few minor bugs are fixed
• added various documentation bits, especially the installation instructions. Currently we are offering two different setups for you to choose. One for operational settings and on for development purposes. Please head over to our documentation https://docs.avaframe.org to find out more
• we are in the process of writing peer reviewed papers. Will take a while :-)

And now on to the version 1.0 announcement.

Link to Youtube

The example data set mentioned during the workshop can be found here: example data

If you want to contact us for more information see here: AvaFrame communications .

Your AvaFrame core team

It takes place via a zoom meeting: ZOOMLINK (Login via browser is possible, no app installation necessary). The workshop will be held in English.

If you want to follow the hands on demo:

• please prepare by following the installation instructions on our documentation: standard installation .

• you can bring your own data if you want, but we will also provide test data.

Our focus this month was the preparation for our upcoming version 1.0 release. We finished the month by publishing the first release candidate. See github releases for a full changelog.

• For the final release of version 1.0 we worked on a difference report, investigating our numerics and comparing it to com1DFAOrig.

• We streamlined and improved the way release thickness is being set in the DFA module com1DFA