Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • CIGALE CIGALE
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cigale
  • CIGALECIGALE
  • Issues
  • #6

Closed
Open
Created Nov 23, 2015 by Yannick Roehlly@yroehllyOwner

Fail to use entry table with integer values

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:

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.

Assignee
Assign to
Time tracking