I am working on obtaining the neutron star mass and radius through the QLIMR module, and I am currently facing some issues and confusion from the documentation.
The first main issue I find is the input for the Equation of State “EoS” data. The documentation mentions two types of table inputs, one consisting with 10 columns, and the other with 2 columns for pressure and total energy only. Using the example data listed in the document, I am unable to obtain the output file using the 2 column table. While inputting the table with 10 columns I was able to obtain the output file (error output screenshot attached). Is there a way to only input the columns table only?
Secondly, I find some of the documentation a bit confusing on the requirements or with clarifications. I was not aware I needed a GitLab account to run the module (using the Docker container), causing a little confusion on what I needed to log in on. Then on the eos data naming, I was not sure whether the file should be called “eos” or “eos.csv”.
I understand these are small details, but have caused a some headache that I think some clarifications can help for new people attempting to install and utilize the module.
Thank you for reaching out and for sharing your feedback — it’s much appreciated!
To clarify your first question: if you’re providing a 2-column Equation of State (EoS) table (total energy density \varepsilon and pressure p in MeV/fm^3), the file should be named eos_validated.csv and placed in the input folder. The QLIMR module assumes that any file with this name contains already validated data and will proceed accordingly without further checks.
If you’re using the MUSES format (with 10 columns), the expected filename is either eos.csv or eos.h5. Just make sure that if you’re using the .h5 option, the file is actually in HDF5 format — not just named with a .h5 extension — as the module expects a valid binary HDF5 structure. In this case, QLIMR handles the validation internally and extracts the necessary columns for the C++ backend to run.
Regarding the GitLab account: yes, an account is required if you’re pulling the container image from the GitLab container registry. This step is mentioned in the Detailed Running section of the documentation, though I understand how it could be missed — I’ll work on making that clearer in future updates.
I’ll also update the documentation to include these naming conventions and other details more explicitly, particularly in the example section, to help new users avoid similar confusion.
Thanks again for your feedback — it really helps improve the experience for everyone.
