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

Make debugging and checking optional through arguments #32

Open
Cosmopal opened this issue Oct 10, 2019 · 2 comments
Open

Make debugging and checking optional through arguments #32

Cosmopal opened this issue Oct 10, 2019 · 2 comments

Comments

@Cosmopal
Copy link

Cosmopal commented Oct 10, 2019

Currently, in both code and code_v1.0, debugging and checking is enabled, which results in a lot and lot of images being written to the disk which are just intermediate steps in the training/testing process of the model

(This is as far as I could understood, please correct me if I am wrong). My understanding is that the outputs 0_check_label 1_padding_img_with_detection_and_target 2_cropped_detection 3_resized_detection 4_pos_neg_anchors 5_all_anchors are all outputs representing intermediate steps and are not required for the actual training/testing)

  1. Need to make this optional. The user might not want the output. For reasonable size datasets, this debug output itself is into order of 100s of GBs... (personal experience using this model for training)

  2. Add in the Readme that this output is in fact a debug output..

Small changes, I can do that..

@Cosmopal
Copy link
Author

Just noticed, it's already added as part of options in code_v1. Thanks. Please delete this issue if possible..

@Cosmopal Cosmopal reopened this Oct 10, 2019
@Cosmopal
Copy link
Author

We can probably just add it in the readme that the images written are debug images and not required for training...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant