-
-
Notifications
You must be signed in to change notification settings - Fork 41
one torch dataset & target data schema #375
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
Conversation
| location_id: id for location | ||
| """ | ||
| # Check the user has asked for a sample which we have the data for | ||
| if t0 not in self.valid_t0_times or self.valid_t0_and_location_ids: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this might need a little more care. If self.complete_generation==True we can check for t0 in self.complete_generation but I think for self.complete_generation==False we should really check if the pair (t0, location_id) is in self.valid_t0_and_location_ids.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep that's fair, I've added a stronger check now
|
Thanks for taking a look at this @dfulu, I have addressed all the comments now so hopefully this is good to go |
dfulu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Thanks Sukh!
Pull Request
Description
Changes to support one torch dataset/input data schema this is a development branch which has had two major commits into it which were already reviewed, those were:
Fixes #334
How Has This Been Tested?
Through unit tests and also running training with the new changes