Implementation of particle 'set_id's within input.json file

[cw646]

Currently, the implementation of particle entity sets "set_id" is not working.

This would add the ability to define point entity sets that can have boundary conditions (load, velocity etc) at creation, and from multiple files.

The example is given below is how this implementation would look in the mpm.json file:

"particles": [
    {
      "generator": {
        "check_duplicates": false,
        "location": "3dparticles.txt",
        "io_type": "Ascii3D",
        "particle_type": "P3D",
        "material_id": 0,
        "type": "file"
      },
      "set_id": 0
    },
    {
      "generator": {
        "check_duplicates": false,
        "location": "cone_out.txt",
        "io_type": "Ascii3D",
        "particle_type": "P3D",
        "material_id": 1,
        "type": "file"
      },
      "set_id": 1
    }
  ],

[kks32]

      "generator": {
        "check_duplicates": true,
        "location": "particles.txt",
        "io_type": "Ascii2D",
        "particle_type": "P2D",
        "material_id": 1,
        "pset_id": 0,
        "type": "file"
      }

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.