Skip to content

use individually named dir instead of GeNNworkspace #137

Description

@tnowotny

This makes sense for at least two reasons:

  • It will allow the GeNN caching system to reduce recompilations
  • it will avoid errors when the contents of GeNNworkspace are partially overwritten for different models
    We need to find the optimal naming convention of the working directory that is model-specific.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    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