Skip to content
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

New test-case too unspecific #145

Open
haesleinhuepf opened this issue Nov 21, 2024 · 0 comments
Open

New test-case too unspecific #145

haesleinhuepf opened this issue Nov 21, 2024 · 0 comments

Comments

@haesleinhuepf
Copy link
Owner

Hi Riccardo @rmassei,

in a new test-case suggested in #142, the test seems impossible to pass for me. I'd say that humans could not solve this with the given set of instructions and the expected solution:

image_metadata_reading.ipynb.txt

I'm in particular concerned about the docstring and the assert statement.

docstring:

Read images proprieties (i.e. shape, dimensions) from a tif file

assert:

expected_proprieties = "ImageProperties(shape=(20, 10), dtype=dtype('uint8'), n_images=None, is_batch=False, spacing=(5.0, 5.0))"
assert result_proprieties == expected_proprieties

If generated code would return a dictionary with dtype and shape, it would fulfill the description, but the test would fail. If you have time, please rephrase the docstring and the assert-statement so that humans and LLMs could pass the test, ideally without using this exact syntax from imageio.

Thanks!

Best,
Robert

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

No branches or pull requests

1 participant