Merge branch '2084-update-matid' into 'develop'

Updated MatID version, increased clustering size limit.

Closes #2084

See merge request !1995

nomad/config/defaults.yaml

@@ -134,7 +134,7 @@ normalize:
   angle_rounding: 10.0
   band_structure_energy_tolerance: 8.01088e-21
   cluster_threshold: 2.5
-  clustering_size_limit: 600
+  clustering_size_limit: 1000
   flat_dim_threshold: 0.1
   k_space_precision: 150000000.0
   max_2d_single_cell_size: 7

pyproject.toml

@@ -28,7 +28,7 @@ dependencies = [
     'jmespath>=0.10.0',
     'lxml>=5.2',
     'lxml-html-clean>=0.1.0',
-    'matid>=2.0.1',
+    'matid>=2.1.0',
     'mdanalysis==2.5.0',
     'networkx>=2.6.3',
     'nptyping~=1.4.4',

[Theodore Chang]

It looks like that, with different python versions in different virtual environments, uv pip compile -U --universal generates different outputs. This is going to result in chaotic git history for requirements.txt if one uses for example 3.9, the other uses 3.11 and they update requirements in turns. The original simple list may be more preferable? What's your take? @ahmil

[Ahmed Ilyas]

--universal flag should generate a single set of universal requirements that fits our requires-python>=3.9 and supports all python platforms requirement regardless of the virtual env / OS you use.

The issue here is different though, the markers blow up so each line ended up being very long. There's an issue to track this https://github.com/astral-sh/uv/issues/5660. But i'll revert to targetting py311 for now then.