cigale issueshttps://gitlab.lam.fr/groups/cigale/-/issues2020-04-07T12:09:56Zhttps://gitlab.lam.fr/cigale/cigale/-/issues/22pCIGALE incompatible with numpy==1.182020-04-07T12:09:56ZAlexandre BeelenpCIGALE incompatible with numpy==1.18Due to changes in the handling of `np.linspace` and `np.logspace`, https://github.com/numpy/numpy/commit/f4dfe833e3e037bb69113f7250fad3699f918cfc pcigale-2018.0.1 fails with
```python
self.wave = np.logspace(5., 9., 1000.)
File “<__arra...Due to changes in the handling of `np.linspace` and `np.logspace`, https://github.com/numpy/numpy/commit/f4dfe833e3e037bb69113f7250fad3699f918cfc pcigale-2018.0.1 fails with
```python
self.wave = np.logspace(5., 9., 1000.)
File “<__array_function__ internals>“, line 6, in logspace
[...]
TypeError: object of type <class ‘float’> cannot be safely interpreted as an integer.
````https://gitlab.lam.fr/cigale/cigale/-/issues/20The shape of SPIRE filters depends on the extension of the source2018-02-19T14:39:27ZMédéric BoquienThe shape of SPIRE filters depends on the extension of the sourceThe actual effective shape of the SPIRE filters depends on the extension of the source. Currently cigale only has the point-source version. It would be better to include both versions.The actual effective shape of the SPIRE filters depends on the extension of the source. Currently cigale only has the point-source version. It would be better to include both versions.https://gitlab.lam.fr/cigale/cigale/-/issues/19Exit gracefully when pcigale.ini is not found2017-05-18T11:24:59ZMédéric BoquienExit gracefully when pcigale.ini is not foundWhen launching pcigale from a directory missing the pcigale.ini file, rather than a clear indication of the issue, cigale gives a cryptic backtrace:
```
Traceback (most recent call last):
File "/home/mederic/.local/bin/pcigale", lin...When launching pcigale from a directory missing the pcigale.ini file, rather than a clear indication of the issue, cigale gives a cryptic backtrace:
```
Traceback (most recent call last):
File "/home/mederic/.local/bin/pcigale", line 9, in <module>
load_entry_point('pcigale', 'console_scripts', 'pcigale')()
File "/home/mederic/pcigale/pcigale/__init__.py", line 104, in main
run(config)
File "/home/mederic/pcigale/pcigale/__init__.py", line 49, in run
configuration = config.configuration
File "/home/mederic/pcigale/pcigale/session/configuration.py", line 223, in configuration
self.complete_redshifts()
File "/home/mederic/pcigale/pcigale/session/configuration.py", line 286, in complete_redshifts
z_mod = self.config['sed_modules_params']['redshifting']['redshift']
File "/usr/lib/python3.5/site-packages/configobj.py", line 554, in __getitem__
val = dict.__getitem__(self, key)
KeyError: 'sed_modules_params'
```
It would be better to indicate what is the issue.https://gitlab.lam.fr/cigale/cigale/-/issues/7Can't use FITS files as input2017-05-18T11:24:59ZYannick Roehllyyannick.roehlly@lam.frCan't use FITS files as inputIt's no more possible to use a FITS file as observable input. CIGALE fails with:
```python
TypeError: read_table_fits() got an unexpected keyword argument 'delimiter'
```It's no more possible to use a FITS file as observable input. CIGALE fails with:
```python
TypeError: read_table_fits() got an unexpected keyword argument 'delimiter'
```https://gitlab.lam.fr/cigale/cigale/-/issues/6Fail to use entry table with integer values2017-05-18T11:24:59ZYannick Roehllyyannick.roehlly@lam.frFail to use entry table with integer valuesWhen CIGALE reads an input catalogue is replaces all the -9999 cells by NaN. When the input catalogue contains an error column containing -9999 everywhere, if this catalogue uses an ASCII format astropy things the column contains an inte...When CIGALE reads an input catalogue is replaces all the -9999 cells by NaN. When the input catalogue contains an error column containing -9999 everywhere, if this catalogue uses an ASCII format astropy things the column contains an integer which can not be replace by NaN. In that case, a CIGALE run stops:
```python
ValueError: cannot convert float NaN to integer
```
It may have no meaning to have a column with only -9999 and to use it. Nevertheless, this can occur when processing a lot of catalogues with the same work-flow.
The problem occur whenever a flux or error column is interpreted as integer and CIGALE has to mask the incorrect values.https://gitlab.lam.fr/cigale/cigale/-/issues/5Make the filter list optional in the param module2017-05-18T11:24:59ZYannick Roehllyyannick.roehlly@lam.frMake the filter list optional in the param moduleIf the filter list is empty or is not given when the param module is used CIGALE won't run. This list must not be mandatory.If the filter list is empty or is not given when the param module is used CIGALE won't run. This list must not be mandatory.Yannick Roehllyyannick.roehlly@lam.frYannick Roehllyyannick.roehlly@lam.frhttps://gitlab.lam.fr/cigale/cigale/-/issues/4Wrong names for SED components in VO-table export2017-05-18T11:24:59ZYannick Roehllyyannick.roehlly@lam.frWrong names for SED components in VO-table exportWhen exporting a SED to VO-table, one table in named “Flambda” but actually contain luminosities. It should either be renamed or contain the fluxes.When exporting a SED to VO-table, one table in named “Flambda” but actually contain luminosities. It should either be renamed or contain the fluxes.https://gitlab.lam.fr/cigale/cigale/-/issues/3Attenuation below Lyman limit2017-05-18T11:24:59ZYannick Roehllyyannick.roehlly@lam.frAttenuation below Lyman limitThe attenuation modules attenuate the SED below the Lyman limit (for instance the dustatt_calzleit module use the Leitherer formula even if it is not defined below 912 Å). But this attenuation should be treated differently, like it's don...The attenuation modules attenuate the SED below the Lyman limit (for instance the dustatt_calzleit module use the Leitherer formula even if it is not defined below 912 Å). But this attenuation should be treated differently, like it's done in the nebular module with a parameter giving the fraction of Lyman continuum photos absorbed by dust.
First the attenuation modules should exclude the Lyman continuum from the attenuation. Then we should decide either between:
- We assume that no Lyman continuum photon is absorbed by dust. Users needing a more precise attenuation should use the nebular module.
- We take the “fraction of Lyman continuum photons absorbed by dust” out of the nebular module and add it to the attenuation modules.https://gitlab.lam.fr/cigale/cigale/-/issues/2SFH quenching fails if quenching age is greater than galaxy age2017-05-18T11:24:59ZYannick Roehllyyannick.roehlly@lam.frSFH quenching fails if quenching age is greater than galaxy ageWhen one uses the SFH quenching module if the quenching age is superior to the galaxy age there is an error and the computing stops. Of course, the quenching age must be smaller than the galaxy age but we may need to find a way to deal w...When one uses the SFH quenching module if the quenching age is superior to the galaxy age there is an error and the computing stops. Of course, the quenching age must be smaller than the galaxy age but we may need to find a way to deal with this case.Yannick Roehllyyannick.roehlly@lam.frYannick Roehllyyannick.roehlly@lam.frhttps://gitlab.lam.fr/cigale/cigale/-/issues/1The redshifting module should not be mandatory to compute the Fnu2017-05-18T11:24:59ZYannick Roehllyyannick.roehlly@lam.frThe redshifting module should not be mandatory to compute the FnuIf one tries to get the fnu property of a SED that did not pass through the redshifting module, it fails because the SED info dictionary does not contain 'universe.luminosity_distance' which is added by the redshifting module. This modul...If one tries to get the fnu property of a SED that did not pass through the redshifting module, it fails because the SED info dictionary does not contain 'universe.luminosity_distance' which is added by the redshifting module. This module should not be mandatory.