sylv/fyp
1
0
Fork 0
Code Issues 29 Pull Requests Packages Projects 1 Releases Wiki Activity

Make sure the model only loads training data #41

New Issue
Closed
opened 2023-10-19 10:43:45 +00:00 by sylv · 1 comment
sylv commented 2023-10-19 10:43:45 +00:00
Owner
Copy Link

Make sure that the model only loads training data by separating the training data from the testing data.

  • update the add function so that when data is added it only adds on the right folder
  • update the training script so that the data is loaded from the corect folder
Make sure that the model only loads training data by separating the training data from the testing data. - [ ] update the add function so that when data is added it only adds on the right folder - [ ] update the training script so that the data is loaded from the corect folder
sylv added the Kind/Enhancement
Priority
High
 labels 2023-10-19 10:43:54 +00:00
sylv added this to the FYP project 2023-10-19 10:43:56 +00:00
sylv added this to the MVP milestone 2023-10-19 10:44:00 +00:00
sylv started working 2023-10-20 11:50:06 +00:00
sylv commented 2023-10-20 12:11:14 +00:00
Author
Owner
Copy Link

I changed the original plan the files are still stored in the same path but now the python script only loads the correct ones

I changed the original plan the files are still stored in the same path but now the python script only loads the correct ones
sylv referenced this issue from a commit 2023-10-20 12:11:28 +00:00
closes #41
sylv closed this issue 2023-10-20 12:11:28 +00:00
sylv worked for 21 minutes 22 seconds 2023-10-20 12:11:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Done But Enhancement Blocking
The issue is done but there is another issue that is an enhancement blocking it
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label Kind/Enhancement
Priority
High
Milestone
No items
No Milestone MVP
Projects
Clear projects
No project FYP
Assignees
Clear assignees
sylv
No Assignees
1 Participants
Notifications
Total Time Spent: 21 minutes
sylv
21 minutes
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sylv/fyp#41
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?