-
Notifications
You must be signed in to change notification settings - Fork 36
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
Unexpected keyword argument 'image_size' when running benchmark #74
Comments
Tried tag v1.0.1 and it still happens. Also tried to update all OS packages but still nothing. The parameter "image_size" doesn't exist in |
diff --git a/dlio_benchmark/utils/utility.py b/dlio_benchmark/utils/utility.py
index 8872f2e..267ba19 100644
--- a/dlio_benchmark/utils/utility.py
+++ b/dlio_benchmark/utils/utility.py
@@ -49,7 +49,7 @@ except:
return
def __exit__(self, type, value, traceback):
return
- def update(self, *, epoch=0, step=0, size=0, default=None):
+ def update(self, *, epoch=0, step=0, size=0, default=None, image_size=0):
return
class dftracer(object):
def __init__(self,): That fixes the issue. Not sure if "image_size" is supposed to be "size" or the other way around, but just adding it (since the test isn't using a profiler) is the easiest fix. |
You can do pip install -r requirements.txt to fix the issue |
This is a current bug to DLIO if dftracer is not installed. So when switching over to 1.0.1, please make sure to do |
For unet3d runs, should 1.0 or 1.0.1 be used before running pip install -r requirements.txt? |
Hey folks!
I saw that someone asked the same question yesterday on the mailinglist, but nobody has answered so I thought I bring it here since I'm running into the same issue.
When I try to run the benchmark, the process stops when trying to read the training data and complains about a "TypeError: Profile.update() got an unexpected keyword argument 'image_size'".
Generated the data as
And running the benchmark fails as
Running the benchmark in a venv with Python 3.12.3, Ubuntu 24.04 LTS, on kernel 6.8.0-1009-aws #9-Ubuntu SMP Fri May 17 14:39:23 UTC 2024.
Anyone an idea? It feels like the data format is wrong, but not sure.
The text was updated successfully, but these errors were encountered: