Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use some sort of self construct to allow blueprint index to survive renames? #1295

Open
cyrush opened this issue Jul 12, 2024 · 0 comments
Open
Labels

Comments

@cyrush
Copy link
Member

cyrush commented Jul 12, 2024

blueprint_index: 
  mesh: 
    state: 
      time: 0.0
      path: "mesh/state"
      number_of_domains: 1
      partition_pattern: "example_yaml.root:/"
    coordsets: 
      coords: 
        type: "uniform"
        coord_system: 
          axes: 
            x: 
            y: 
            z: 
          type: "cartesian"
        path: "mesh/coordsets/coords"
    topologies: 
      topo: 
        type: "uniform"
        coordset: "coords"
        path: "mesh/topologies/topo"
protocol: 
  name: "yaml"
  version: "0.9.2"
number_of_files: 1
number_of_trees: 1
file_pattern: "example_yaml.root"
tree_pattern: "/"

When someone renames example_yaml.root to something else, the patterns are broken.

Ideas?

   partition_pattern: "{self}:/"
file_pattern: "{self}"

or empty refers to self?

@cyrush cyrush added the feature label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant