Closed bhaskar2443053 closed 1 year ago
Merging #79 (87c6ede) into master (68cdac6) will increase coverage by
0.77%
. The diff coverage is95.55%
.:exclamation: Current head 87c6ede differs from pull request most recent head cf68e4d. Consider uploading reports for the commit cf68e4d to get more accurate results
@@ Coverage Diff @@
## master #79 +/- ##
==========================================
+ Coverage 87.89% 88.66% +0.77%
==========================================
Files 14 16 +2
Lines 735 803 +68
==========================================
+ Hits 646 712 +66
- Misses 89 91 +2
Impacted Files | Coverage Δ | |
---|---|---|
...ests/fortex/health/readers/CT_image_reader_test.py | 95.45% <95.45%> (ø) |
|
fortex/health/readers/CT_image_reader.py | 95.65% <95.65%> (ø) |
|
...ortex/health/processors/scispacy_processor_test.py | 100.00% <0.00%> (ø) |
|
fortex/health/processors/scispacy_processor.py | 98.63% <0.00%> (+0.38%) |
:arrow_up: |
ftx/medical/clinical_ontology.py | 69.91% <0.00%> (+0.49%) |
:arrow_up: |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Hi @Piyush13y and @hunterhector I am facing this new error with already merged processors.
E AttributeError: module 'numpy' has no attribute 'object'
is there something we can do ?
Hi @Piyush13y and @hunterhector I am facing this new error with already merged processors.
E AttributeError: module 'numpy' has no attribute 'object'
is there something we can do ?
Could you try to narrow down the error? Most likely there are some new environment upgrades that cause this. I cannot easily figure it out just looking at the error.
Hi @Piyush13y and @hunterhector I am facing this new error with already merged processors. E AttributeError: module 'numpy' has no attribute 'object' is there something we can do ?
Could you try to narrow down the error? Most likely there are some new environment upgrades that cause this. I cannot easily figure it out just looking at the error.
Run coverage run -m pytest tests/fortex/health/processors/scispacy_processor_test.py ============================= test session starts ============================== platform linux -- Python 3.8.15, pytest-5.1.3, py-1.11.0, pluggy-0.13.1 rootdir: /home/runner/work/ForteHealth/ForteHealth collected 0 items / 1 errors
==================================== ERRORS ====================================
ERROR collecting tests/fortex/health/processors/scispacy_processor_test.py
tests/fortex/health/processors/scispacy_processor_test.py:26: in
/opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/site-packages/tensorflow/python/pywrap_tensorflow_internal.py:15 /opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/site-packages/tensorflow/python/pywrap_tensorflow_internal.py:15: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp
/opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/site-packages/tensorflow/python/framework/dtypes.py:223
/opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/site-packages/tensorflow/python/framework/dtypes.py:223: DeprecationWarning: np.bool8
is a deprecated alias for np.bool_
. (Deprecated NumPy 1.24)
np.bool8: (False, True),
/opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/site-packages/tensorflow/python/framework/dtypes.py:513
/opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/site-packages/tensorflow/python/framework/dtypes.py:513: FutureWarning: In the future np.object
will be defined as the corresponding NumPy scalar. (This may have returned Python scalars in past versions.
np.object,
-- Docs: https://docs.pytest.org/en/latest/warnings.html !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!! ========================= 4 warnings, 1 error in 2.39s ========================= Error: Process completed with exit code 2.
The same error with xray processor test case
After a quick glance it looks like it is the spacy and numpy have some version conflicts. I would recommend recreating this issue locally and find out the right version combination.
To be honest, we haven't upgraded some library versions for a long time. We should spend a sprint on that alone.
After a quick glance it looks like it is the spacy and numpy have some version conflicts. I would recommend recreating this issue locally and find out the right version combination.
To be honest, we haven't upgraded some library versions for a long time. We should spend a sprint on that alone.
also got it with x-ray processor test too. it was added last month.
Run coverage run -m pytest tests/fortex/health/processors/xray_processor_test.py ============================= test session starts ============================== platform linux -- Python 3.8.15, pytest-5.1.3, py-1.11.0, pluggy-0.13.1 rootdir: /home/runner/work/ForteHealth/ForteHealth collected 0 items / 1 errors
==================================== ERRORS ==================================== ERROR collecting tests/fortex/health/processors/xray_processor_test.py /opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/site-packages/transformers/utils/import_utils.py:857: in _get_module return importlib.import_module("." + module_name, self.name) /opt/hostedtoolcache/Python/3.8.15/x64/lib/python3.8/importlib/init.py:127: in import_module return _bootstrap._gcd_import(name[level:], package, level)
This PR fixes #78 .
Description of changes
This a new CT image reader implementation using pydicom lib.
Possible influences of this PR.
The sample data is a bit huge, even for one instance.
Test Conducted
the test case verifies the existence of the image path from the reader in the source folder.