Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Optimise the config files handling

See original GitHub issue

Subject of the feature

Reading and processing config file can be improved:

  • For those fields that are not required for individual options, warning/error should not be raised (tba): *global net does not need extract_levels or method (predicting dvf or conditional makes no difference to ddf, even enabled) *train does not require test (or even valid) dataset(s) *unet does not require extract_levels

  • The section dataset and train may be regrouped due to the requirement for train and predict, consider: *dataset: required for train and predict, but with different requirement **train requires train, train/val, train/test or train/val/test (this can be complicated, so minimally require no test) **predict requires only test dataset *model: required for both train and test and have to be consistent between the two, including current method and backbone *train: hyperparameters only required during training, and not required for predict, including current loss, optimizer, preprocess, epoch, save_period

  • Disable label_sample for predict, while predict will use all labels provided.

If the feature request is approved, would you be willing to submit a PR? (Help can be provided if you need assistance submitting a PR)


Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

mathpluscodecommented, Jan 17, 2021

Watch out for backcompatibility and modifs here

I got an idea for back-compatibility.

As we are doing config checks, we can add one function, to enable old -> latest config transformation automatically and print warnings to remind users! As a result, code will be back-compatible! @YipengHu @NMontanaBrown

NMontanaBrowncommented, Jan 17, 2021

Watch out for backcompatibility and modifs here

Read more comments on GitHub >

github_iconTop Results From Across the Web

6 optimization tips for your CI configuration - CircleCI
In this post, we will cover the six most effective ways to optimize your config file so you can build faster. You will...
Read more >
Configuration File Options and Optimizations - Logi Analytics
Configuration File Options and OptimizationsIn order to decrease the amount of resources needed to handle the configuration information,...
Read more >
- Optimize the Screen configuration file
Your configuration file can be optimized to exclude sections that don't apply to your system, and to the applications running on your system....
Read more >
Optimize GitLab CI/CD configuration files
You can reduce complexity and duplicated configuration in your GitLab CI/CD configuration files by using: YAML-specific features like anchors ( & ), aliases ......
Read more >
What is a config file? -
Parsing config files with Bash​​ Separating config files from code enables anyone to change their configurations without any special programming ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found