Skip to content

round up the number of batches per epoch#30

Open
gdarkwah wants to merge 1 commit intoshervinea:masterfrom
gdarkwah:patch-1
Open

round up the number of batches per epoch#30
gdarkwah wants to merge 1 commit intoshervinea:masterfrom
gdarkwah:patch-1

Conversation

@gdarkwah
Copy link

Instead of np.floor, I think np.ceil is the right form of rounding to use. this is with reference to the tensorflow/keras documentation (https://www.tensorflow.org/api_docs/python/tf/keras/utils/Sequence)

Example explanation:
given a sample size (or the length of list_enzymes in this context) of 35 and a batch_size of 10, using np.floor will result in 3 batches. This leaves out the remaining 5 samples in the list_enzymes. meanwhile, using the ceil will result in 4 batches which covers the last 5 samples. You may be wondering about indexing in getitem but since the self.indexes is a numpy array, indexing beyond the length of that array will just truncate at the end of the arra.

Instead of np.floor, I think np.ceil is the right form of rounding to use. this is with reference to the tensorflow/keras documentation (https://www.tensorflow.org/api_docs/python/tf/keras/utils/Sequence)

Example explanation:
given a sample size (or the length of list_enzymes in this context) of 35 and a batch_size of 10, using np.floor will result in 3 batches. This leaves out the remaining 5 samples in the list_enzymes. meanwhile, using the ceil will result in 4 batches which covers the last 5 samples. You may be wondering about indexing in __getitem__ but since the self.indexes is a numpy array, indexing beyond the length of that array will just truncate at the end of the arra.
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

Successfully merging this pull request may close these issues.

1 participant