Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • SWIFTsim SWIFTsim
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

gitlab has been updated to version 16

  • SWIFT
  • SWIFTsimSWIFTsim
  • Issues
  • #192
Closed
Open
Issue created Jul 26, 2016 by Peter W. Draper@pdraperOwner

Entropy flag is a vector for all particle types, but not handled as such.

It seems that when we read the flag_entropy:

readAttribute(h_grp, "Flag_Entropy_ICs", INT, flag_entropy);

we have room for a single int, whereas the stored value is an vector with a value for each particle type. Worked around that and this test now runs. Does this value really need to be a vector?

Issue came up in tests for merge request !203 (merged).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking