-
Notifications
You must be signed in to change notification settings - Fork 27
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
Feat/multi batch processing #127
Conversation
@@ -37,6 +37,8 @@ class MapProcessingParameters: | |||
resolution_cm_per_px: float # image resolution to used during processing | |||
processed_area_type: ProcessedAreaType # whether to perform operation on the entire field or part | |||
tile_size_px: int # Tile size for processing (model input size) | |||
batch_size: int # Batch size for processing | |||
local_cache: bool # Whether to use local cache for tiles |
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.
How about adding in comment it is caching on disk?
params=params, | ||
) | ||
|
||
map_processor.run() |
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.
How about adding an assert for the result (also in the original non-batched test)
map_processor.run() | ||
result_img = map_processor.get_result_img() | ||
|
||
assert result_img.shape == (2351, 2068) |
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.
how about asserting some pixels also, to check the result?
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.
Check the last commit, please.
No description provided.