Let’s try breaking down this discussion, as there are several issues being mixed:
The particle properties file always interpolates the file that was passed as input and appends the lepton properties at the end. This means each module has a different number of columns in the particle properties. If you read the beta_equilibrium.ipynb script (download here) you’ll see Crust-DFT + Lepton outputs 29 columns in the particle properties, and CMF + Lepton has 157 columns. This is true both for charge neutrality and beta equilibrium outputs and has not changed with the update.
On the beta-equilibrium calculation, Eq. 11 from 2502.07902 enforces charge neutrality, but not beta-equilibrium.
By definition of the chemical potentials in the CE, you will always have \mu_Q = \mu_p - \mu_n. The beta-equilibrium condition will reduce the 2d table to 1d, by setting \mu_Q = - \mu_e, but in the charge neutrality files, this relation (\mu_Q = - \mu_e) does not hold.
My question would be: from which file are you reading the grid from? For which module? What is the config? You can also share the UUID if it’s a recent job, and I can find the config from here.
On the mu_Q grid, if you are talking about CMF, you should be able to run the muQ grid with
muQ_begin: -450.0
muQ_end: 0.0
muQ_step: 2.0
which is similar to the one shown in our tutorial. Since the module itself was not updated, any change in grid behavior must come from the input configuration or the post-processing scripts.
However, if you ran the code today and got this “nasty error”:
Error message
File "/home/ce/.local/lib/python3.11/site-packages/celery/app/trace.py", line 479, in trace_task R = retval = fun(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^ File "/home/ce/.local/lib/python3.11/site-packages/celery/app/trace.py", line 779, in __protected_call__ return self.run(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/app/calculation_engine/tasks.py", line 416, in run_module s3.store_folder( File "/opt/app/calculation_engine/object_store.py", line 55, in store_folder self.put_object( File "/opt/app/calculation_engine/object_store.py", line 75, in put_object self.client.fput_object(bucket_name=self.bucket, object_name=path, file_path=file_path) File "/home/ce/.local/lib/python3.11/site-packages/minio/api.py", line 1054, in fput_object return self.put_object( ^^^^^^^^^^^^^^^^ File "/home/ce/.local/lib/python3.11/site-packages/minio/api.py", line 2015, in put_object raise exc File "/home/ce/.local/lib/python3.11/site-packages/minio/api.py", line 1965, in put_object upload_id = self._create_multipart_upload( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ce/.local/lib/python3.11/site-packages/minio/api.py", line 1770, in _create_multipart_upload response = self._execute( ^^^^^^^^^^^^^^ File "/home/ce/.local/lib/python3.11/site-packages/minio/api.py", line 444, in _execute return self._url_open( ^^^^^^^^^^^^^^^ File "/home/ce/.local/lib/python3.11/site-packages/minio/api.py", line 427, in _url_open raise response_error minio.error.MinioException: S3 operation failed; code: SlowDown, message: , resource: None, request_id: tx00000853b1ef9c3f2f4d2-006980dbf7-8ed7a1-default, host_id: 8ed7a1-default-default
It is likely an issue with the deployment of the CE and not the modules themselves. It happened to many modules this morning, and it should be fixed soon.
Regarding the update, let me reiterate that it did not change the version of the modules we are referring to, which means they work exactly as before. Therefore, any change in output should come only from a change in the config files used or in the script used for reading and manipulating the files.
Unfortunately, since the original configuration file (from your previous run) was not saved, and there is no git history we can check, there is no way for us to reproduce the error and check your previous results. What I can say is that we have a large set of unit tests when the CE is updated to make sure workflows are running as expected, and on our side, no errors were spotted.
If you’d like to share the plotting scripts and the associated config files you used to generate the data, I’d be happy to take a look and help determine whether there are any issues in the setup, or in the modules themselves.
