Branch of fesom2.6 including recom and tracer parallelisation #681

a270105 · 2025-01-29T15:56:11Z

Tracer parallelisation can be switched on by __usetp in fesom2/src/CMakeLists.txt and onlye used when recom is on.

Define new variables to track tracer changes due to advection and diffusion. We want to save for now diffusion and advection contribution to the tracer changes. Horizontal and vertical diffusion includes Redi parametrization (if it is set .true.).

Fill __ciso directive to ensure that carbon isotope code works. Medusa interface is added.

… io_restart.F90

…sation

a270105 · 2025-01-29T16:00:11Z

By compilation I found an issue regrading new compilations. I need to manually delete the executable file fesom.x in fesom2.build/bin and then compile the model. Otherwise, after a successful compilation I will still find the old fesom.x in fesom2/bin.

…atbox

JanStreffing

Summary of review:
There were a few places that need changing, some that may not need to change but would require a closer look that everything is indeed ok. There are a number of style improvements to be made. All comment that start with ! kh date should start without the name and date. Same for !YY, !O:G !OG and !.OG. Git blame can tell you this info.

In addition to the standalone FESOM2 CI tests, this branch needs to be tested by me as part of AWI-CM3, by @ackerlar as part of AWI-ESM2, by @sebastianbeyer or @suvarchal as part of IFS-FESOM, by @mbutzin with active tracers. I'm assuming here, that you have already tested this branch with recom and without _usetp

JanStreffing · 2025-02-03T18:39:02Z

CMakeLists.txt

 set(USE_ICEPACK OFF CACHE BOOL "compile fesom with the Iceapck modules for sea ice column physics.")
 set(OPENMP_REPRODUCIBLE OFF CACHE BOOL "serialize OpenMP loops that are critical for reproducible results")
-set(RECOM_COUPLED OFF CACHE BOOL "compile fesom including biogeochemistry, REcoM3")
+set(RECOM_COUPLED ON CACHE BOOL "compile fesom including biogeochemistry, REcoM3")


This should be turned back for the main branch.

JanStreffing · 2025-02-03T18:39:48Z

src/MOD_TRACER.F90

 integer                                       :: AB_order=2
 integer                                       :: ID
+!___________________________________________________________________________
+! TODO: Make it as a part of namelist.tra


Should be done before more?

need to clarify with Özgür

src/cpl_driver.F90

src/fesom_module.F90

src/gen_forcing_couple.F90

src/io_restart.F90

src/oce_ale_tracer.F90

JanStreffing · 2025-02-03T19:06:39Z

In addition to the changes of the review, the merge conflicts should be solved. Most of them look like simple double additions of new features that both have to be kept. e.g. parallel tracers and icebergs.

ackerlar · 2025-02-05T09:33:50Z

Is there any template fesom-recom yaml that I can use for testing?

ackerlar · 2025-02-05T09:46:03Z

I get this error during compilation:

/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/associate_mesh_ass.h(57): warning #5117: Bad # preprocessor line
#if defined(__async_icebergs)
-^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/associate_mesh_ass.h(59): warning #5117: Bad # preprocessor line
#endif
-^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(363): error #6784: The number of actual arguments cannot be greater than the number of dummy arguments.   [OASIS_INIT_COMP]
    CALL oasis_init_comp(comp_id, comp_name, ierror, num_program_groups = num_fesom_groups)
---------^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(961): error #6404: This name does not have a type, and must have an explicit type.   [MPI_COMM_FESOM_SAME_RANK_IN_GROUPS]
      call MPI_Bcast(action, 1, MPI_LOGICAL, 0, MPI_COMM_FESOM_SAME_RANK_IN_GROUPS, MPIerr)
------------------------------------------------^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(961): error #6404: This name does not have a type, and must have an explicit type.   [MPIERR]
      call MPI_Bcast(action, 1, MPI_LOGICAL, 0, MPI_COMM_FESOM_SAME_RANK_IN_GROUPS, MPIerr)
------------------------------------------------------------------------------------^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(976): error #6404: This name does not have a type, and must have an explicit type.   [MYDIM_NOD2D]
          call MPI_Bcast(data_array, myDim_nod2d, MPI_DOUBLE_PRECISION, 0, MPI_COMM_FESOM_SAME_RANK_IN_GROUPS, MPIerr)
-------------------------------------^
compilation aborted for /home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90 (code 1)
make[2]: *** [src/CMakeFiles/fesom.dir/build.make:205: src/CMakeFiles/fesom.dir/cpl_driver.F90.o] Error 1

a270105 · 2025-02-05T12:22:28Z

I am still testing the code. So far I can run ocean-only without __usetp in CMakeLists and compile the model with __usetp. But I have not yet tested the coupled setup.

a270105 · 2025-02-05T12:52:10Z

I get this error during compilation:

/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/associate_mesh_ass.h(57): warning #5117: Bad # preprocessor line
#if defined(__async_icebergs)
-^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/associate_mesh_ass.h(59): warning #5117: Bad # preprocessor line
#endif
-^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(363): error #6784: The number of actual arguments cannot be greater than the number of dummy arguments.   [OASIS_INIT_COMP]
    CALL oasis_init_comp(comp_id, comp_name, ierror, num_program_groups = num_fesom_groups)
---------^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(961): error #6404: This name does not have a type, and must have an explicit type.   [MPI_COMM_FESOM_SAME_RANK_IN_GROUPS]
      call MPI_Bcast(action, 1, MPI_LOGICAL, 0, MPI_COMM_FESOM_SAME_RANK_IN_GROUPS, MPIerr)
------------------------------------------------^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(961): error #6404: This name does not have a type, and must have an explicit type.   [MPIERR]
      call MPI_Bcast(action, 1, MPI_LOGICAL, 0, MPI_COMM_FESOM_SAME_RANK_IN_GROUPS, MPIerr)
------------------------------------------------------------------------------------^
/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(976): error #6404: This name does not have a type, and must have an explicit type.   [MYDIM_NOD2D]
          call MPI_Bcast(data_array, myDim_nod2d, MPI_DOUBLE_PRECISION, 0, MPI_COMM_FESOM_SAME_RANK_IN_GROUPS, MPIerr)
-------------------------------------^
compilation aborted for /home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90 (code 1)
make[2]: *** [src/CMakeFiles/fesom.dir/build.make:205: src/CMakeFiles/fesom.dir/cpl_driver.F90.o] Error 1

I just compiled it with FESOM_COUPLED ON and didn't get any error. Did you compile the model with esm-tools?

ackerlar · 2025-02-05T13:12:09Z

@a270105 yes, I used esm_tools: esm_master get-awiesm-2.6, changed the FESOM branch to fesom2.6_recom_tp and then esm_master comp-awiesm-2.6

which oasis version are you using?

ackerlar · 2025-02-05T19:21:05Z

I got at least rid of this error

/home/a/a270124/model_codes/testing_and_debugging/awiesm-2.6/fesom-2.6/src/cpl_driver.F90(363): error #6784: The number of actual arguments cannot be greater than the number of dummy arguments.   [OASIS_INIT_COMP]
    CALL oasis_init_comp(comp_id, comp_name, ierror, num_program_groups = num_fesom_groups)

when switching to oasis branch feat/multi-group-support. Before I used 2.8mct-awiesm-2.1. However, the other errors remain

ackerlar · 2025-02-05T19:54:59Z

src/fesom_module.F90

-        call cpl_oasis3mct_init(f%partit,f%partit%MPI_COMM_FESOM)
+!        call cpl_oasis3mct_init(f%partit,f%partit%MPI_COMM_FESOM)
+! kh 02.12.21
+#if defined(__recom) && defined(__usetp)


"localCommunicator" is neither defined in fesom_module nor in MOD_PARTIT. Should this really be "localCommunicator" or "f%partit%MPI_COMM_FESOM"?

I can't really answer this. These lines already exited in fesom2.5-recom and another earlier version where Özgür and I merged their complex recom version and my simpler paleo version. But I can't find them in my paleo version where Kai first time implemented tracer parallelisation. There this part of code is still in fvom_main.f90 and only contains:
#if defined (__oasis)

! kh 21.03.22 pass num_fesom_groups to coupler
call cpl_oasis3mct_init(MPI_COMM_FESOM, num_fesom_groups)
#endif
t1 = MPI_Wtime()

call par_init

......

So I think it should be for the case with tracer parallelisation:
call cpl_oasis3mct_init(f%partit, f%partit%MPI_COMM_FESOM, num_fesom_groups)

ackerlar · 2025-02-05T20:23:10Z

FESOM compiled for me with some minor changes in MPI calls. I also changed

-        call cpl_oasis3mct_init(f%partit, f%partit%localCommunicator, num_fesom_groups)
+        call cpl_oasis3mct_init(f%partit, f%partit%MPI_COMM_FESOM, num_fesom_groups)

in fesom_module as localCommunicator is not defined outside of cpl_driver. Please check whether this makes sense.

However, the model crashes as FESOM is missing some entries in namelist.config. Is there a recom specific namelist.config?

a270105 · 2025-02-05T20:58:09Z

@a270105 yes, I used esm_tools: esm_master get-awiesm-2.6, changed the FESOM branch to fesom2.6_recom_tp and then esm_master comp-awiesm-2.6

which oasis version are you using?

a270105 · 2025-02-05T21:22:27Z

FESOM compiled for me with some minor changes in MPI calls. I also changed
-        call cpl_oasis3mct_init(f%partit, f%partit%localCommunicator, num_fesom_groups)
+        call cpl_oasis3mct_init(f%partit, f%partit%MPI_COMM_FESOM, num_fesom_groups)
in fesom_module as localCommunicator is not defined outside of cpl_driver. Please check whether this makes sense.

However, the model crashes as FESOM is missing some entries in namelist.config. Is there a recom specific namelist.config?

Do you compile with __usetp? If not, there is no additional entry needed in namelist.config.

…nto fesom2.6_recom_tp

ackerlar · 2025-02-06T08:09:37Z

Do you compile with __usetp? If not, there is no additional entry needed in namelist.config.

Yes, I set RECOM_COUPLED=ON which gives

if(${RECOM_COUPLED})
#   target_compile_definitions(${PROJECT_NAME} PRIVATE __recom USE_PRECISION=2 __usetp)
#   target_compile_definitions(${PROJECT_NAME} PRIVATE __recom USE_PRECISION=2)
   target_compile_definitions(${PROJECT_NAME} PRIVATE __recom USE_PRECISION=2 __3Zoo2Det __coccos __usetp)
endif()

in src/CMakeLists.txt and __usetp should be used if I understand correctly.

JanStreffing · 2025-10-28T07:16:30Z

Good progress @a270105. @suvarchal, or maybe @sebastianbeyer, any chance you can try to run a day of ifs-fesom with this branch this week?

a270105 · 2025-10-28T11:18:49Z

The issue with copying recom restart files is fixed now and the changes are committed in the awiesm-2.6-recom branch.
A run without TP is finished for 5 days with daily restart.

JanStreffing · 2025-10-28T12:49:20Z

I tried the AWI-ESM3 part. I get stuck compiling:

/work/ab0246/a270092/model_codes/awiesm3-develop/fesom-2.6/src/cpl_driver.F90(362): error #6627: This is an actual argument keyword name, and not a dummy argument name.   [NUM_PROGRAM_GROUPS]
    CALL oasis_init_comp(comp_id, comp_name, ierror, num_program_groups = num_fesom_groups)
-----------------------------------------------------^
compilation aborted for /work/ab0246/a270092/model_codes/awiesm3-develop/fesom-2.6/src/cpl_driver.F90 (code 1)
make[2]: *** [src/CMakeFiles/fesom.dir/build.make:205: src/CMakeFiles/fesom.dir/cpl_driver.F90.o] Error 1
make[2]: *** Waiting for unfinished jobs....

Does that look familiar to you @a270105 ?

a270105 · 2025-10-28T13:33:15Z

No, I have never had problem with this line.
I checked the oasis code and found that 'num_program_groups' is defined for the subroutine oasis_init_comp in oasis/lib/psmile/src/mod_oasis_method.F90
Maybe you are using a different oasis version?

JanStreffing · 2025-10-28T14:42:27Z

Yes, we use oasis3mct5, not oasis3mct2.8

a270105 · 2025-10-28T14:49:09Z

Can you use the branch origin/feat/multi-group-support? Kai's changes for using multiple groups of the same program were added there 2022

JanStreffing · 2025-10-28T15:25:17Z

Can you link to that branch?
I can't see that online

a270105 · 2025-10-28T16:49:19Z

https://gitlab.awi.de/paleodyn/Models/oasis3-mct/-/tree/feat/multi-group-support?ref_type=heads

JanStreffing · 2025-10-28T16:50:53Z

This branch is many years out of date. We can not run the latest AWI-ESM3 with that. Even if we make that run, it would not help us for the merge request at hand. We need this to work with new oasis3mct versions that contain required features, such as CONSERV remapping. Maybe this is something Kai can tackle?

I am running with: https://git.smhi.se/ec-earth/vendor/oasis/oasis3-mct-5.git

a270105 · 2025-10-28T16:53:21Z

I am not suggesting to use that branch, just to see where Kai changed things related to tracer parallelisation. Maybe it is not too difficult to just add those in your oasis code.

JanStreffing · 2025-10-28T17:57:33Z

Basically this, right? https://gitlab.awi.de/paleodyn/Models/oasis3-mct/-/merge_requests/3/diffs?commit_id=52a228e100ebb2935136888111e26f5894565f9b

a270105 · 2025-10-28T19:45:27Z

yes, I also found his changes in these 3 files

JanStreffing · 2025-10-28T19:59:10Z

Can you give this a try @a270105 & @chrisdane? I might not have the time to do so before the model freeze.

a270105 · 2025-10-29T10:21:22Z

I can't run awiesm-2.6-recom with TP with the current oasis (from the branch 'multi-group-support') and got segmentation fault at the step FESOM: calling exchange_roots. So, at the moment the code works with TP compiled and num_fesom_groups = 1 (only one tracer groups, i.e. no MPI applied for tracers). For further steps I need help from Kai or someone else.

JanStreffing · 2025-10-29T10:39:35Z

I can't run awiesm-2.6-recom with TP with the current oasis (from the branch 'multi-group-support') and got segmentation fault at the step FESOM: calling exchange_roots. So, at the moment the code works with TP compiled and num_fesom_groups = 1 (only one tracer groups, i.e. no MPI applied for tracers). For further steps I need help from Kai or someone else.

Good to know. This does not block the merge, as that would be a new feature.

JanStreffing · 2025-10-30T16:17:24Z

I tried the AWI-ESM3 part. I get stuck compiling:

/work/ab0246/a270092/model_codes/awiesm3-develop/fesom-2.6/src/cpl_driver.F90(362): error #6627: This is an actual argument keyword name, and not a dummy argument name.   [NUM_PROGRAM_GROUPS]
    CALL oasis_init_comp(comp_id, comp_name, ierror, num_program_groups = num_fesom_groups)
-----------------------------------------------------^
compilation aborted for /work/ab0246/a270092/model_codes/awiesm3-develop/fesom-2.6/src/cpl_driver.F90 (code 1)
make[2]: *** [src/CMakeFiles/fesom.dir/build.make:205: src/CMakeFiles/fesom.dir/cpl_driver.F90.o] Error 1
make[2]: *** Waiting for unfinished jobs....

Does that look familiar to you @a270105 ?

I no longer get this error using the Group enabled version of OASIS3MCT5.
Next I got errors with preprocessing flags in the the .h files. Basically Intel compiler seems to ignore preprocessing flags inside .h files. When use_tp is not set, it then tries to access pieces of partit, that are not there, because the working preprocessor statements in the F90 code removed them:

/work/ab0246/a270092/model_codes/awiesm3-develop-cc/fesom-2.6/src/associate_part_ass.h(2): error #6460: This is not a component name that is defined in the encompassing structure.   [MPI_COMM_FESOM_WORLD]
MPI_COMM_FESOM_WORLD                => partit%MPI_COMM_FESOM_WORLD
----------------------------------------------^

…o fesom2.6_recom_tp

JanStreffing · 2025-10-30T17:06:19Z

I tried the AWI-ESM3 part. I get stuck compiling:
/work/ab0246/a270092/model_codes/awiesm3-develop/fesom-2.6/src/cpl_driver.F90(362): error #6627: This is an actual argument keyword name, and not a dummy argument name.   [NUM_PROGRAM_GROUPS]
    CALL oasis_init_comp(comp_id, comp_name, ierror, num_program_groups = num_fesom_groups)
-----------------------------------------------------^
compilation aborted for /work/ab0246/a270092/model_codes/awiesm3-develop/fesom-2.6/src/cpl_driver.F90 (code 1)
make[2]: *** [src/CMakeFiles/fesom.dir/build.make:205: src/CMakeFiles/fesom.dir/cpl_driver.F90.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Does that look familiar to you @a270105 ?
I no longer get this error using the Group enabled version of OASIS3MCT5. Next I got errors with preprocessing flags in the the .h files. Basically Intel compiler seems to ignore preprocessing flags inside .h files. When use_tp is not set, it then tries to access pieces of partit, that are not there, because the working preprocessor statements in the F90 code removed them:
/work/ab0246/a270092/model_codes/awiesm3-develop-cc/fesom-2.6/src/associate_part_ass.h(2): error #6460: This is not a component name that is defined in the encompassing structure.   [MPI_COMM_FESOM_WORLD]
MPI_COMM_FESOM_WORLD                => partit%MPI_COMM_FESOM_WORLD
----------------------------------------------^

I though I was able to fix this by switching from #ifdef to !DEC statements, But I think that broke the code even more. Consider reverting. We need a solution to have preprocessors statements in the .h files. Otherwise we need two versions and include those. But that would add over 300 preprocessors statements and back a clusterfuck. No way I want to do that.

Any idea how to do this @suvarchal?

a270105 · 2025-10-30T20:18:48Z

I just looked back in this merge request. Yes, I had the same issue and Lars as well. I tried with !DIR since I thought it would be good to not to be compiler specific...But for some reasons it did not work. So we decided to remove the preprocessor directives and let those pointers always defined. The same is done for the iceberg part. I just have these lines in the beginnging of my associate_part_ass.h:
MPI_COMM_FESOM_WORLD => partit%MPI_COMM_FESOM_WORLD MPI_COMM_FESOM_SAME_RANK_IN_GROUPS => partit%MPI_COMM_FESOM_SAME_RANK_IN_GROUPS MPI_COMM_FESOM => partit%MPI_COMM_FESOM MPI_COMM_FESOM_IB => partit%MPI_COMM_FESOM_IB
Do you have a different file?

JanStreffing · 2025-10-31T08:46:44Z

I have the version that is pushed onto the repo here.
Can you pull and fix that again? Sorry for the mess.

a270105 · 2025-10-31T21:08:28Z

The preprocessor directives in those two .h files are deleted and I compiled the code with usetp on and off.

JanStreffing · 2025-10-31T21:50:07Z

JanStreffing · 2025-11-01T15:37:14Z

Update, I was able to run AWI-ESM3 without TP on this branch, after a local merge of our CO2 coupling developments done on fesom2.6_recom_awiesm3_co2_coupling

I will not test AWI-ESM3 with TP. It will not work yet, but it does not have to for this PR.

a270105 · 2025-11-04T11:40:49Z

I have to report something really odd:
I added a new feature in the recom code (src/int_recom/recom_sms.F90) and recompiled fesom. However, a fully identical executable file was created (the build folder was deleted before compilation). This did not happen as I changed the fesom code (or cmake options in src/CMakeLists for recom). Somehow the recom files were not updated during recompilation. Others in the recom group have the same problem with other branches like fesom-2.6-recom-tra-diags.
This might need to be fixed before the release, right?

ogurses and others added 8 commits October 15, 2024 15:08

add recom_sms diag

3e84a88

feat(recom): add ciso and medusa components

434f0e6

Fill __ciso directive to ensure that carbon isotope code works. Medusa interface is added.

input to bc_surface from medusa added and Sed_input deleted

0864237

changes in src for tracer parallelisation

a3dfd9f

change defined(__recom)||defined(__usetp) to only defined(__usetp) in…

911fd3c

… io_restart.F90

corrections to compile with tracer parallelisation on

358082d

cleanup and small corrections of flags for recom and tracer paralleli…

0d3834a

…sation

corrections in array allocation for Diags and initialization for use_…

74a5e59

…atbox

JanStreffing previously requested changes Feb 3, 2025

View reviewed changes

JanStreffing assigned a270105 Feb 3, 2025

JanStreffing added the enhancement New feature or request label Feb 3, 2025

ackerlar reviewed Feb 5, 2025

View reviewed changes

make MPI calls consistent fix?? cpl_oasis3mct_init call in fesom_module

e8117d8

a270105 closed this Feb 5, 2025

a270105 reopened this Feb 5, 2025

a270105 added 2 commits February 6, 2025 00:04

localcommunicator removed in fesom_module.F90

604a88a

Merge branch 'fesom2.6_recom_tp' of https://github.com/FESOM/fesom2 i…

cb11456

…nto fesom2.6_recom_tp

add read_namelist_run_config back to fesom_module.F90

7ec55f2

JanStreffing added the RECOM label Oct 29, 2025

JanStreffing added 2 commits October 30, 2025 17:28

replace ifdef with DEC preprocessing flags in .h files

db9d64c

Merge branch 'fesom2.6_recom_tp' of ssh://github.com/FESOM/fesom2 int…

ed36284

…o fesom2.6_recom_tp

remove preprocessor directives in .h files

f04fabf

pH/DOC dependent parameterisation of Fe-binding ligands completed

e07391f

a270105 mentioned this pull request Nov 4, 2025

REcoM code is not updated during recompilation #808

Open

Branch of fesom2.6 including recom and tracer parallelisation #681

Are you sure you want to change the base?

Branch of fesom2.6 including recom and tracer parallelisation #681

Uh oh!

Conversation

a270105 commented Jan 29, 2025

Uh oh!

a270105 commented Jan 29, 2025

Uh oh!

JanStreffing left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

JanStreffing Feb 3, 2025

Choose a reason for hiding this comment

Uh oh!

JanStreffing Feb 3, 2025

Choose a reason for hiding this comment

Uh oh!

a270105 Feb 5, 2025

Choose a reason for hiding this comment

Uh oh!

suvarchal Sep 8, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

JanStreffing commented Feb 3, 2025

Uh oh!

ackerlar commented Feb 5, 2025

Uh oh!

ackerlar commented Feb 5, 2025

Uh oh!

a270105 commented Feb 5, 2025

Uh oh!

a270105 commented Feb 5, 2025

Uh oh!

ackerlar commented Feb 5, 2025

Uh oh!

ackerlar commented Feb 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ackerlar Feb 5, 2025

Choose a reason for hiding this comment

Uh oh!

a270105 Feb 5, 2025

Choose a reason for hiding this comment

Uh oh!

ackerlar commented Feb 5, 2025

Uh oh!

a270105 commented Feb 5, 2025

Uh oh!

a270105 commented Feb 5, 2025

Uh oh!

ackerlar commented Feb 6, 2025

Uh oh!

JanStreffing commented Oct 28, 2025

Uh oh!

a270105 commented Oct 28, 2025

Uh oh!

JanStreffing commented Oct 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

a270105 commented Oct 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JanStreffing commented Oct 28, 2025

Uh oh!

a270105 commented Oct 28, 2025

Uh oh!

JanStreffing commented Oct 28, 2025

Uh oh!

a270105 commented Oct 28, 2025

Uh oh!

JanStreffing left a comment •

edited

Loading

ackerlar commented Feb 5, 2025 •

edited

Loading

JanStreffing commented Oct 28, 2025 •

edited

Loading

a270105 commented Oct 28, 2025 •

edited

Loading

JanStreffing commented Oct 28, 2025 •

edited

Loading

a270105 commented Oct 29, 2025 •

edited

Loading

JanStreffing commented Oct 31, 2025 •

edited by a270105

Loading

a270105 commented Nov 4, 2025 •

edited

Loading