Skip to content

Splitting one job into smaller pieces leads to loss of some trajectories #1

@Alexsp32

Description

@Alexsp32

Splitting a job with 100 trajectories loses some trajectories from the total after splitting when total_trajectories % processes !=0.
Probably something I messed up in the routine to handle these cases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions