Common MDI #381

aciarma · 2024-08-26T12:26:28Z

Added Lumical, quadrupoles and magnetic fields to the common MDI folder for FCCee.

[OK] Move LumiCal (from CLD_o2_v07) to common folder
[OK] Add file with dimensions/materials related to MDI elements
[OK] Add solenoids Fieldmap
[OK] Add simple quadrupoles (these will change with the lattice, both field and position/dimension)
[OK] Add a standalone master for MDI elements only (mainly for debug processes and tracking in LumiCal)
Change detectors master xml to point to the common MDI files, and remove old MDI files from the detector folders
- CLD (which version?)
- [OK] IDEA_o1_v03
- [OK] ALLEGRO_o1_v03

update from master

FCCee/MDI/compact/MDI_o1_v00/fields_solenoid.xml

aciarma · 2024-09-03T09:27:41Z

I've changed the master compact file for IDEA_o1_v03 and ALLEGRO_o1_v03 to point to the common MDI folder for all the related elements, removed the files for LumiCal/beam pipe/beam instrumentation from the experiment folders and modified accordingly the DectDimensions.xml files.

Should I do the same for CLD? If yes, which version?

aciarma · 2024-09-05T10:50:39Z

the file FFQuads_v01 (default include) now is not a sensitive element anymore. If for specific needs the hits in the quadrupoles need to be studied, FFQuads_v01_sens.xml is the sensitive version to be used instead.

danieljeans · 2024-09-09T06:45:22Z

are these MDI models expected to be overlap-free yet? @Victor-Schwan and I think we are seeing several overlaps when using the overlap.mac macros in ddsim on both the MDI_standalone_o1_v01 and MDI_standalone_o1_v00 models.

I attach the output of the overlap checker for the two standalone models. (search for "detected" and you'll see the overlaps).

overlap_MDI_standalone_o1_v00.log
-> looks like up to ~2 cm overlaps around HOMabsorber

overlap_MDI_standalone_o1_v01.log
-> many 10~1000 micron overlaps between CAD elements

danieljeans · 2024-09-12T02:16:07Z

I propose applying g4 step limits to the interior of the beampipe, and the whole MDI region (in my experience this helps achieve accurate simulation of beamstrahlung (ie low pT charged particles) in non-uniform fields).
Adding something like:

<limitset name="mdi_limits">
   <limit name="step_length_max" particles="*" value="5.0" unit="mm" />
</limitset>

and adding the limits to the different MDI detectors, e.g. changing

<detector name="BeBeampipe" type="DD4hep_Beampipe_o1_v01" insideTrackingVolume="true" nocore="true" vis="BeamPipeVis">

to

<detector name="BeBeampipe" type="DD4hep_Beampipe_o1_v01" insideTrackingVolume="true" limits="mdi_limits" nocore="true" vis="BeamPipeVis">

should work OK, I think.

BrieucF · 2024-10-09T06:34:40Z

fieldmaps/FCCee_fieldMapXYZ_120218.root

Are we sure this map contains only the fields from the anti-solenoid and assume a 0 detector field when produced? Otherwise we will "double count" the detector field there. By the way, "fieldMap" is very generic, can you find a more descriptive name for this file.

atolosadelgado · 2024-10-17T15:48:50Z

Hi @aciarma ,

Thank you for making this very complete PR!

Here are few comments:
v00:

Overlaps are found with the HOM absorber. However, CLD has no overlaps in its MDI, how is it possible?

          Overlap is detected for volume AV_4!BeamPipeShield_assembly_3#3!tube_TaShield_0_0#0:4 (G4SubtractionSolid) with HOMAbsorber_envelope_11:11 (G4UnionSolid)
          overlap at local point (38.0487,-33.0895,1241.63) by 4.41048 mm  (max of 124 cases)
--
          Overlap is detected for volume AV_4!BeamPipeShield_assembly_3#3!tube_TaShield_1_1#1:5 (G4SubtractionSolid) with HOMAbsorber_envelope_11:11 (G4UnionSolid)
          overlap at local point (-37.5385,-32.9308,-1209.05) by 4.5692 mm  (max of 94 cases)
--
          Overlap is detected for volume HOMAbsorber_envelope_11:11 (G4UnionSolid) with AV_4!BeamPipeShield_assembly_3#3!tube_TaShield_0_0#0:4 (G4SubtractionSolid)
          overlap at local point (-12.5365,34.1472,-389.019) by 1.48998 cm  (max of 4272 cases)
--
          Overlap is detected for volume AV_8!HOMAbsorbers_PunchThrough_assembly_12#12!tube_HOM1_0_0#0:13 (G4SubtractionSolid) with AV_4!BeamPipeShield_assembly_3#3!tube_TaShield_0_0#0:4 (G4SubtractionSolid)
          overlap at local point (0.553117,-31.1543,-388.835) by 1.96526 cm  (max of 5628 cases)
--
          Overlap is detected for volume AV_8!HOMAbsorbers_PunchThrough_assembly_12#12!tube_HOM1_1_1#1:14 (G4SubtractionSolid) with AV_4!BeamPipeShield_assembly_3#3!tube_TaShield_1_1#1:5 (G4SubtractionSolid)
          overlap at local point (0.785344,-31.6609,-388.835) by 1.96071 cm  (max of 5595 cases)

Variable QD0 min/max are defined twice, can we centralize it into the Dimensions and material compact file?
These variables QD0 have a comment that says potentially outdated, do you know if it means that the value is not valid anymore?
Centralize size variables from solenoid and antisolenoid in Dimensions and Materials compact file?
Move the definition of magnetic field of FFQ to another file, to be coherent with the solenoid/antisolenoid elements?

v01:
6. CAD design corresponding to water and AlBeMet volumes seem to have at least 1 facet with the wrong orientation, as reported during initializing the geometry:

-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomSolids1001
      issued by : G4TessellatedSolid::SetSolidClosed()
Defects in solid: "Componente1"_shape_0xd5bd950 - some facets have wrong orientation!
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------


-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomSolids1001
      issued by : G4TessellatedSolid::SetSolidClosed()
Defects in solid: "Componente1"_shape_0xe064510 - some facets have wrong orientation!
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------

I am not sure if it is related to the previous point, but the Geant4 navigator reports error around point r~25, z=+/-1111 (I think the units are mm). Please see the the attached file named MDI_v01_error_points.txt
MDI_v01_error_points.txt
Regarding Daniel comment about region limits, I can take care of it in a future PR.
Regarding your question if CLD should be modified, we can leave it as it is for the moment, and let the CLD responsibles change to the central MDI.

Please, let me know if I can help somehow.

Fix segmentation position calculation for Allegro ECal.

aciarma · 2025-02-11T17:05:11Z

New CAD models now have the latest description for elliptoconical chamber cooling manifolds, and the flange at the end of the albemet part

Added preliminar model for Bellows

Central chamber from ±90mm is now made using DD4hep_Mask instead of CAD to remove issues due to mismatch of facets of the different volumes

Added "beam" volume fitting the CAD beam pipe model to fix air in beam pipe

Tungsten SR mask reworked, and the notch on the other side of the beam pipe has been removed.

How can I upload the STL files for the new CAD models?

atolosadelgado · 2025-02-11T18:17:26Z

New CAD models now have the latest description for elliptoconical chamber cooling manifolds, and the flange at the end of the albemet part

Added preliminar model for Bellows

Central chamber from ±90mm is now made using DD4hep_Mask instead of CAD to remove issues due to mismatch of facets of the different volumes

Added "beam" volume fitting the CAD beam pipe model to fix air in beam pipe

Tungsten SR mask reworked, and the notch on the other side of the beam pipe has been removed.

How can I upload the STL files for the new CAD models?

Thank @aciarma for this PR. I am checking your files before moving them to www-eos. I have some questions about the new model:

Can you fix this error?

Evaluator        WARN  +++ Overwriting variable: name=QD0_min_z value=2000*mm  Evaluator::Object : existing variable [setVariable error]
Detector         WARN  +++ Object 'QD0_min_z' is already defined. New value will be ignored
Evaluator        WARN  +++ Overwriting variable: name=QD0_max_z value=5400*mm  Evaluator::Object : existing variable [setVariable error]
Detector         WARN  +++ Object 'QD0_max_z' is already defined. New value will be ignored

Can you confirm that the placement of 4 lumicals is expected?

dd4hep::Ref_t create_detector(dd4hep::Detector&, xml_h, dd4hep::SensitiveDetector)
Here is my LumiCal
 and this is the sensitive detector: 0x7ffdf517f868
 The crossing angle is: 0.03 radian
Total Length 11.25 cm
Layer Thickness 0.45 cm
Compact          INFO  ++ Converted subdetector:LumiCal of type LumiCal_o1_v01 [calorimeter]
dd4hep::Ref_t create_detector(dd4hep::Detector&, xml_h, dd4hep::SensitiveDetector)
Here is my LumiCal
 and this is the sensitive detector: 0x7ffdf517f868
 The crossing angle is: 0.03 radian
Total Length 11.25 cm
Layer Thickness 0.45 cm
Compact          INFO  ++ Converted subdetector:LumiCalInstrumentation of type LumiCal_o1_v01 [calorimeter]
dd4hep::Ref_t create_detector(dd4hep::Detector&, xml_h, dd4hep::SensitiveDetector)
Here is my LumiCal
 and this is the sensitive detector: 0x7ffdf517f868
 The crossing angle is: 0.03 radian
Total Length 11.25 cm
Layer Thickness 0.45 cm
Compact          INFO  ++ Converted subdetector:LumiCalCooling of type LumiCal_o1_v01 [calorimeter]
dd4hep::Ref_t create_detector(dd4hep::Detector&, xml_h, dd4hep::SensitiveDetector)
Here is my LumiCal
 and this is the sensitive detector: 0x7ffdf517f868
 The crossing angle is: 0.03 radian
Total Length 0.35 cm
Layer Thickness 0.35 cm
Compact          INFO  ++ Converted subdetector:LumiCalBackShield of type LumiCal_o1_v01 [calorimeter]

I noticed that there are some overlaps, up to 9mm, could you please take a look to it?

-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomVol1002
      issued by : G4PVPlacement::CheckOverlaps()
Overlap with volume already placed !
          Overlap is detected for volume AV_8!Beampipe_STL_0#0!ASCII_0#0:0 (G4TessellatedSolid) with AV_14!Beam_STL_6#6!ASCII_0#0:0 (G4TessellatedSolid)
          overlap at local point (14.0421,-8.71044,659.727) by 3.37392 mm  (max of 1115 cases)
NOTE: Reached maximum fixed number -1- of overlaps reports for this volume !
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
--
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomVol1002
      issued by : G4PVPlacement::CheckOverlaps()
Overlap with volume already placed !
          Overlap is detected for volume AV_14!Beam_STL_6#6!ASCII_0#0:0 (G4TessellatedSolid) with AV_8!Beampipe_STL_0#0!ASCII_0#0:0 (G4TessellatedSolid)
          overlap at local point (14.6671,-12.8952,862.223) by 2.16673 mm  (max of 2759 cases)
NOTE: Reached maximum fixed number -1- of overlaps reports for this volume !
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
--
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomVol1002
      issued by : G4PVPlacement::CheckOverlaps()
Overlap with volume already placed !
          Overlap is detected for volume AV_15!Paraffin_STL_7#7!ASCII_0#0:0 (G4TessellatedSolid) with AV_8!Beampipe_STL_0#0!ASCII_0#0:0 (G4TessellatedSolid)
          overlap at local point (12.416,-3.81531,117.483) by 506.795 um  (max of 4403 cases)
NOTE: Reached maximum fixed number -1- of overlaps reports for this volume !
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
--
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomVol1002
      issued by : G4PVPlacement::CheckOverlaps()
Overlap with volume already placed !
          Overlap is detected for volume AV_16!Water_STL_8#8!ASCII_0#0:0 (G4TessellatedSolid) with AV_8!Beampipe_STL_0#0!ASCII_0#0:0 (G4TessellatedSolid)
          overlap at local point (-18.312,11.0271,681.066) by 36.7902 um  (max of 2395 cases)
NOTE: Reached maximum fixed number -1- of overlaps reports for this volume !
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
--
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomVol1002
      issued by : G4PVPlacement::CheckOverlaps()
Overlap with volume already placed !
          Overlap is detected for volume AV_17!Bellows_STL_9#9!ASCII_0#0:0 (G4TessellatedSolid) with AV_8!Beampipe_STL_0#0!ASCII_0#0:0 (G4TessellatedSolid)
          overlap at local point (8.8925,-47.5236,1225.23) by 8.56756 mm  (max of 52 cases)
NOTE: Reached maximum fixed number -1- of overlaps reports for this volume !
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
--
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomVol1002
      issued by : G4PVPlacement::CheckOverlaps()
Overlap with volume already placed !
          Overlap is detected for volume AV_18!Beampipe_crotch_STL_10#10!ASCII_0#0:0 (G4TessellatedSolid) with AV_14!Beam_STL_6#6!ASCII_0#0:0 (G4TessellatedSolid)
          overlap at local point (-14.8662,-12.1879,-1323.04) by 944.42 um  (max of 3559 cases)
NOTE: Reached maximum fixed number -1- of overlaps reports for this volume !
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
--
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomVol1002
      issued by : G4PVPlacement::CheckOverlaps()
Overlap with volume already placed !
          Overlap is detected for volume AV_19!Tungsten_STL_11#11!ASCII_0#0:0 (G4TessellatedSolid) with AV_14!Beam_STL_6#6!ASCII_0#0:0 (G4TessellatedSolid)
          overlap at local point (-44.6705,1.14337,2069.84) by 3.08147 um  (max of 1403 cases)
NOTE: Reached maximum fixed number -1- of overlaps reports for this volume !
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------

I think the complaint about the facets with wrong orientation persists, could you confirm if the shapes giving this problem before are the same?

-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomSolids1001
      issued by : G4TessellatedSolid::SetSolidClosed()
Defects in solid: ASCII_shape_0xdde5530 - some facets have wrong orientation!
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------


-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomSolids1001
      issued by : G4TessellatedSolid::SetSolidClosed()
Defects in solid: ASCII_shape_0xf00fe90 - some facets have wrong orientation!
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------

aciarma · 2025-02-12T11:03:16Z

hello @atolosadelgado, on the above points:

I fixed this
It should be correct because they are 4 different parts of LumiCal (main, Instrumentation, Cooling and BackShield), but I did not do anything on that, I just moved the latest version in the MDI folder
on my side if I do checkOverlap -c MDI_standalone_o1_v01.xml I get no overlaps, how did you get those warnings?
on the facets orientation, I did not understood why this comes up... from CAD it does not seems that there are such problems, and I also tried to use tools I found online (trimesh python package) but it had no effect apparently.

atolosadelgado · 2025-02-12T11:32:28Z

hello @atolosadelgado, on the above points:

1. I fixed this

2. It should be correct because they are 4 different parts of LumiCal (main, Instrumentation, Cooling and BackShield), but I did not do anything on that, I just moved the latest version in the MDI folder

3. on my side if I do `checkOverlap -c MDI_standalone_o1_v01.xml` I get no overlaps, how did you get those warnings?

4. on the facets orientation, I did not understood why this comes up... from CAD it does not seems that there are such problems, and I also tried to use tools I found online (trimesh python package) but it had no effect apparently.

Hi @aciarma

thanks a lot for your quick response! The wrong facet orientation, if I remember correctly, happened at z=+/-1111mm. I will check again running with geantinos.

Regarding the overlaps, I run first few events with geantinos and Geant4 tracking already complained about it. Then, I check the overlaps using Geant4 with the following command:

ddsim --compactFile FCCee/MDI/compact/MDI_o1_v01/MDI_standalone_o1_v01.xml --runType run --macroFile utils/overlap.mac > overlapdump.txt

Please let me know if I can help further. Thanks for your quick reply!

aciarma · 2025-02-12T16:53:09Z

Thank you, I see the same overlaps now. We are investigating a way to avoid this but it seems not trivial. Geometries are obtained from CAD where there are no overlaps, but once it is translated to STL they appear due to the facets not being aligned, and boolean operations on meshes are not working nicely. I will follow up on this.

(this is also why I decided to use DD4hep shapes for the central chamber)

atolosadelgado · 2025-02-12T17:26:41Z

Thank you, I see the same overlaps now. We are investigating a way to avoid this but it seems not trivial. Geometries are obtained from CAD where there are no overlaps, but once it is translated to STL they appear due to the facets not being aligned, and boolean operations on meshes are not working nicely. I will follow up on this.

(this is also why I decided to use DD4hep shapes for the central chamber)

Thank you very much for crosschecking! Please let me know if I can help further :)

aciarma · 2025-02-14T11:51:12Z

We are trying different export strategies using STL, still we are observing small overlaps, now ~20um.
We are thinking of tapering a little bit the light materials to leave a small tolerance between touching volumes (would be filled by world volume air). Do you think it would be an acceptable solution?

AutoCAD Inventor can export also in OBJ of the ddsim supported formats, but when I try to run the overlap macro on the test file I get a crash. Is OBJ still supported? Or are there good formats other than those in the DDCAD/examples list?

aciarma · 2025-02-17T11:12:40Z

ok I realized that the spider.obj file called by the OBJ example in DDCAD does not actually exist. Anyway, following that example I tried to read a simple OBJ file we generated with AutoCAD,

<detector id="1" name="Shape_OBJ" type="DD4hep_TestShape_Creator">
      <check vis="AlBeMet_vis">
        <shape type="CAD_MultiVolume" ref="${K4GEO}/FCCee/MDI/compact/MDI_o1_v01/stl_files/PROVE/prova1_stlOBJ.obj" unit="mm">
          <volume id="0"  name="v1" material="Gold" vis="AlBeMet_vis"/>
         </shape>
      </check>
    </detector>

but got the following error

Compact          ERROR ++ FAILED    to convert subdetector: Shape_OBJ: Cannot find a material referenced by name:191,191,191

where 191,191,191 I highly suspect it is the RGB color code of the volume (a light grey).

Is there a way to overwrite such fields? I defined Gold as material but it clearly did not work.
Also, why the Check_Shapes_OBJ_spider.xml exists but the .obj file does not? There was some problem with that format?

atolosadelgado · 2025-02-28T23:01:09Z

We are trying different export strategies using STL, still we are observing small overlaps, now ~20um. We are thinking of tapering a little bit the light materials to leave a small tolerance between touching volumes (would be filled by world volume air). Do you think it would be an acceptable solution?

AutoCAD Inventor can export also in OBJ of the ddsim supported formats, but when I try to run the overlap macro on the test file I get a crash. Is OBJ still supported? Or are there good formats other than those in the DDCAD/examples list?

Hi @aciarma

Sorry for the late reply! I believe DDCAD is built on top of ASSIMP, so it should support many formats [1].

If you could share the OBJ file privately, I'd be happy to take a look at it.

[1] https://github.com/assimp/assimp/blob/master/doc/Fileformats.md

aciarma and others added 21 commits August 26, 2024 14:12

Merge pull request #7 from key4hep/main

3a73b48

update from master

taken lumical from CLD_o2_v06

b46055a

Merge branch 'key4hep:main' into master

c603c39

Merge branch 'key4hep:main' into commonMDI

a05f5e7

dimensions compact + standalone compact

6a4bf57

Merge branch 'commonMDI' of github.com:aciarma/k4geo into commonMDI

e704601

Merge branch 'key4hep:main' into commonMDI

fd3c79a

Merge branch 'key4hep:main' into master

7205e28

updated for LumiCal_o3_v05

f424af0

added field maps (to fix) and quadrupoles

e15659e

change name FFQuads

b33ed0d

fix FFQ file name

4f52f42

addded FFQ magnetic field for different optics

5854a26

Merge branch 'key4hep:main' into master

bd28642

Merge branch 'key4hep:main' into commonMDI

b1660ee

field map correctly read. fix a variable in FFQ

b1cad71

add 2T detector solenoid field

51825b6

fix ideal antisolenoid field

b121ae3

apply also to MDI_o1_v01

a5dfeeb

fix identical files

e8957b4

fix v01

f3ff764

BrieucF reviewed Sep 2, 2024

View reviewed changes

FCCee/MDI/compact/MDI_o1_v00/fields_solenoid.xml Show resolved Hide resolved

aciarma added 7 commits September 2, 2024 15:50

update README

a9776a3

update README

2438088

add MDI elements to ALLEGRO_o1_v03

0858110

update on ALLEGRO_o1_v03

775610d

add MDI elements to IDEA_o1_v03

9f7db07

fixed paths in IDEA test

5b3554f

fix IDEA_withDRC test

41863a4

aciarma and others added 2 commits September 5, 2024 12:48

Merge branch 'commonMDI' of github.com:aciarma/k4geo into commonMDI

5d0f568

Merge branch 'key4hep:main' into master

a2672c6

aciarma added 2 commits September 5, 2024 13:10

fix non sensitive quads

fb48223

fix non sensitive quads

4967b9d

Victor-Schwan mentioned this pull request Oct 9, 2024

experimental ILD models for FCCee #390

Merged

BrieucF reviewed Oct 9, 2024

View reviewed changes

Merge branch 'key4hep:main' into master

d961353

atolosadelgado mentioned this pull request Jan 29, 2025

Collect files of different MDI versions in a config file for each version #424

Merged

danieljeans mentioned this pull request Jan 31, 2025

MDI_o1_v01 : beampipe filled with air #430

Open

1 task

aciarma and others added 4 commits January 31, 2025 11:23

Merge branch 'key4hep:main' into master

1941082

Resolved merge conflicts with master

25310fe

Merge pull request #8 from key4hep/main

cd40867

Fix segmentation position calculation for Allegro ECal.

DD4hep_Mask for central chamber, CAD updates, beam inside pipe

9c5dc57

aciarma and others added 3 commits February 12, 2025 11:05

removed double definition of QD0_min_z and QD0_max_z

049464d

removed double definition of QD0_min_z and QD0_max_z

c21342a

Merge branch 'key4hep:main' into commonMDI

a16c1a9

Merge branch 'main' into commonMDI

36466d6

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Common MDI #381

Common MDI #381

aciarma commented Aug 26, 2024 •

edited

Loading

aciarma commented Sep 3, 2024

aciarma commented Sep 5, 2024

danieljeans commented Sep 9, 2024 •

edited

Loading

danieljeans commented Sep 12, 2024

BrieucF Oct 9, 2024

atolosadelgado commented Oct 17, 2024

aciarma commented Feb 11, 2025

atolosadelgado commented Feb 11, 2025

aciarma commented Feb 12, 2025

atolosadelgado commented Feb 12, 2025

aciarma commented Feb 12, 2025 •

edited

Loading

atolosadelgado commented Feb 12, 2025

aciarma commented Feb 14, 2025

aciarma commented Feb 17, 2025 •

edited

Loading

atolosadelgado commented Feb 28, 2025

Common MDI #381

Are you sure you want to change the base?

Common MDI #381

Conversation

aciarma commented Aug 26, 2024 • edited Loading

aciarma commented Sep 3, 2024

aciarma commented Sep 5, 2024

danieljeans commented Sep 9, 2024 • edited Loading

danieljeans commented Sep 12, 2024

BrieucF Oct 9, 2024

Choose a reason for hiding this comment

atolosadelgado commented Oct 17, 2024

aciarma commented Feb 11, 2025

atolosadelgado commented Feb 11, 2025

aciarma commented Feb 12, 2025

atolosadelgado commented Feb 12, 2025

aciarma commented Feb 12, 2025 • edited Loading

atolosadelgado commented Feb 12, 2025

aciarma commented Feb 14, 2025

aciarma commented Feb 17, 2025 • edited Loading

atolosadelgado commented Feb 28, 2025

aciarma commented Aug 26, 2024 •

edited

Loading

danieljeans commented Sep 9, 2024 •

edited

Loading

aciarma commented Feb 12, 2025 •

edited

Loading

aciarma commented Feb 17, 2025 •

edited

Loading