Improve CLI and separate into sub-scripts#1255
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1255 +/- ##
==========================================
- Coverage 87.16% 86.95% -0.21%
==========================================
Files 21 24 +3
Lines 2851 3005 +154
==========================================
+ Hits 2485 2613 +128
- Misses 366 392 +26
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
61d822a to
0bdff68
Compare
0bdff68 to
6cc4ad9
Compare
d9b6efd to
37b7a6d
Compare
f4198ca to
1d7e2a9
Compare
|
This is squashed and ready for review. These are new public features so feel encouraged to try them out and we can tweak behavior to suit. |
bw4sz
left a comment
There was a problem hiding this comment.
I agree. There are some options that I never personally use, like tensorboard, but I don't think that should limit merging. The whole point here is that the user is not looking at the script, they are using the CLI, so I care less about the large amount of code, since the user doesn't engage with it directy.
Description
This is a cleaned up version of the training script I used for LIDAR pre-training. I took some inspiration from the bird branch as well to add some more comet features. Docs are updated for all three scripts.
My goal is that users should never need to write scripts and we can be opinionated about defaults that we commonly use ourselves.
./lightning_logs(as opposed to $PWD).AI-Assisted Development
Some use of Claude Code for assisted testing (e.g. checking it can start training jobs).