Skip to content

Update params.json saved paths to relative while preserving run environment metadata #29

@riley-1995

Description

@riley-1995

This committed params.json includes absolute TFRecord paths under /expanse/... which are environment-specific and won’t be meaningful for most users running locally. If these artifacts are meant to be portable/shareable, consider storing relative paths (e.g., under the repo’s data root) or redacting to basenames plus a note on how to regenerate paths.

  "tfrecord_train": "data/tfrecords/tfrecords_spectrogram/model3/train.tfrecord",
  "tfrecord_val": "data/tfrecords/tfrecords_spectrogram/model3/validate.tfrecord",
  "tfrecord_test": "data/tfrecords/tfrecords_spectrogram/model3/test.tfrecord"

Originally posted by @Copilot in #27 (comment)

Relevant files:

  • src/elp_rumble/training/train_cnn.py

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