Skip to content

relative paths in config files confusing #8

@natelust

Description

@natelust

The relative paths in BART.cfg in the example and demo directory are misleading. I.E. func = hack BARTfunc ../../code/ specify a path relative to the directory in which the function which reads the config file resides rather than the directory which contains the config file (i think, the path may be broken all together). By this i mean within the BART/examples/ directory the BART.cfg file specifies the path ../../code/ for the location of the BARTfunc, however from this location in the directory structure the path to code would be ../code . Specifying the path in this manor may be necessary for running the program, but it is not obvious to someone reading the code to use or modify it. If possible use some variable to specify a base directory and do things relative to that variable, or put a code comment helping the reader understand where that function is contained.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions