Skip to content

Commit

Permalink
change notes into minutes
Browse files Browse the repository at this point in the history
  • Loading branch information
AnnikaLau authored Dec 16, 2024
1 parent 6f36c0d commit e5b5f89
Showing 1 changed file with 35 additions and 54 deletions.
89 changes: 35 additions & 54 deletions docs/events/icon_meetings/2024-4.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,87 +51,68 @@ WS asks what needs to happen to get the trigger mechanism working. JJ explains t


## Will Sawyer
a lot going on at CSCS. Where do put test and run data. It's a bit of a mess right now.
WS reports that there is a lot happening at CSCS and raises concerns about where to store test and run data, describing the current situation as somewhat disorganized.

MK probably add mount point to Säntis and Balfrin on store or scratch
SK: would need to access tödi/säntis store from Balfrin.
MK suggests adding a mount point to Säntis and Balfrin for either the store or scratch space. SK notes that accessing Tödi or Säntis storage from Balfrin would be necessary. MK mentions ongoing discussions with André and Xavier to address these issues and suggests that storing data on Säntis might make the most sense.

MK discussion with André and Xavier.
WS asks if write access is required. SK responds that it likely isn’t and that read access should suffice. MK adds that if write access does become necessary, a solution could potentially be implemented.

MK probably makes sense to have data on säntis

WS do you need to write?
SK probably not. read access probably not

MK if write access required, there would maybe be a solution

DL same issue is also read-only access on CPU cluster on clariden

MK clariden and säntis access same store

DL: if you solve it for one, do you solve it for both?

MK: users on clariden and säntis will access same store
DL points out that a similar issue exists regarding read-only access on the CPU cluster Clariden. MK explains that Clariden and Säntis share the same store, so resolving the issue for one system should also address it for the other.


## Sven Kotlarski
Open question who will become EXCLAIM PI? Will Christoph continue or Andreas takes over

## Alina
Still working on data assimilation. Using EMVORADO
SK raises the open question of who will become the Principal Investigator (PI) for EXCLAIM. They ask whether Christoph will continue in the role or if Andreas will take over.

## CS
two topics: looked into new topography dataset for extpar. if you want to run hight resolution, rasta has serious ... effects
other dataset looks quite promosing for running high resolution
## Alina Yapparova
AY reports that they are still working on data assimilation and are using EMVORAD for this purpose.

lradtopo stuff. unified ICON code from cosmo. should be finished soon
## Christian Steger
CS reports two topics. First, they looked into a new topography dataset for EXTPAR. They note that if high-resolution runs are required, the RASTA (TODO ?) dataset has significant limitations. However, another dataset appears to be quite promising for high-resolution simulations.

## MikS
finished transition to alps for icon.ham. everything is running. did benchmarks for produciton proposal, looks quite nice, tested 90 levels, required 1000 gpus.
Second, CS mentions work on lradtopo and reports that the unified ICON code from COSMO is nearly complete and should be finished soon.

Moved back to old daint, to finish something with lohmann. 16% speedup on ham.
will finish a couple of cleanups
## Mikael Stellio
MikS reports that the transition to Alps for ICON-HAM has been completed, and everything is running smoothly. Benchmarks for the production proposal were conducted, showing promising results. Tests with 90 levels required 1,000 GPUs.

solve problems in the radiation inerface. 5 four-d fields whicht take up 30% of the memory. Have to use much less nproma, which is not great for performance
They temporarily moved back to the old Daint system to finish work with the Lohmann microphysics scheme, achieving a 16% speedup on HAM. MikS plans to complete a few cleanups.

MJ. on how many nodes do you run, what are results
MikS run on 44 nodes
They also addressed issues in the radiation interface, where five four-dimensional fields were consuming 30% of the memory. To mitigate this, they had to significantly reduce the use of nproma, which negatively impacts performance.

## DL
worked with Lukas on precipitation, two much spread on long lead-times. also see too intense precipitation on intentse events. very slow progress. CSCS proposal for TeamX, got declined, even though it had two excellent reviews. No contribution from Switzerland for winter. So not good news on this.
MJ asks how many nodes were used and about the results. MikS responds that they ran on 44 nodes.

TS: were discussing this with exclaim, question if we could take over the simulation but not sure if for winter
## David Leutwyler
DL reports working with Lukas on precipitation, noting too much spread on long lead times and excessively intense precipitation during extreme events. Progress has been very slow. DL also mentions that the CSCS proposal for TeamX was declined, despite receiving two excellent reviews, meaning there will be no contribution from Switzerland for the winter. This is disappointing news.

DL time window is closing, because the campaign is in February
TS shares that they discussed the issue with EXCLAIM and raised the possibility of taking over the simulation, though it is uncertain if this would be feasible for the winter.

TS will check with Oli and Anurag
DL points out that the time window is closing as the campaign is scheduled for February.

## NW
TS will check with Oli and Anurag to explore potential solutions.

still working on gettting mixed snow model into main branch from icon.
## Nander Wever
NW reports that they are still working on integrating the mixed snow model into the main branch of ICON.

## DF
not much to share, did becnhermarking for cscs-proposal with icon-exclaim code. r2b7. wnated to go higher but Tödi to unstable. Ported all icon code to new daint as they want to be ready, in case it's needed.
## Doris Folini
DF reports that they completed benchmarking for the CSCS proposal using the ICON-EXCLAIM code (R2B7). They had planned to go higher, but Tödi was too unstable. DF also mentions that all ICON code has been ported to the new Daint system to ensure readiness, in case it is needed.

## YY
wanted to do benchmark on tödi wih coarse resolution but tödi not very stable. will start euro-44 again next year.
## Yi Yao
YY reports that they wanted to run a benchmark on Tödi with coarse resolution, but Tödi has not been very stable. They plan to start the Euro-44 benchmark again next year.

## AH
managed to compile and run icon-art on Tödi. Managed to merge nwp matser branch. Hopefully next few days will open mr. will contact gatekeeper at KIT. Hopefully in the next OS release
## Arash Hamzehloo
AH reports that they successfully compiled and ran ICON-ART on Tödi and managed to merge the NWP master branch. They hope to open a merge request in the next few days and will contact the gatekeeper at KIT. They are optimistic that this will be included in the next open-source release.

next year trying to extent. chemistry part of ART
Next year, AH plans to work on extending the chemistry part of ART.

## EK
EK: not working on icon but with ICON. We can run atmospheric inversions for productin using processing chain.

## Erik Koene
EK clarifies that they are not working on ICON itself but with ICON. They mention that they can run atmospheric inversions for production using the processing chain.

## TS
will be official icon partners. Contract should be signed in February.
## Tina Schnadt
TS reports that C2SM will be an official ICON partner, with the contract expected to be signed in February.

## Matthias Kraushaar
MK reports that they have received new information. The MK cluster will have 500 nodes, and projects that use ICON will be placed on Säntis.

## MK
Got news now.
MK cluster will have 500 nodes. projects which use icon will end up on Säntis



0 comments on commit e5b5f89

Please sign in to comment.