Description
While reviewing the RFNet and ERFNet Sedna integration scripts, I noticed that several sedna_predict.py files reference BaseDataSource in pre_data_process() but only import IndexDataParse from sedna.datasources.
This appears inconsistent with other files in the repository that use BaseDataSource and explicitly import it.
Affected Files
examples/robot/lifelong_learning_bench/semantic-segmentation/testalgorithms/rfnet/RFNet/sedna_predict.py
examples/cityscapes-synthia/lifelong_learning_bench/curb-detection/testalgorithms/rfnet/RFNet/sedna_predict.py
examples/cityscapes-synthia/lifelong_learning_bench/semantic-segmentation/testalgorithms/rfnet/RFNet/sedna_predict.py
examples/cityscapes-synthia/scene-based-unknown-task-recognition/curb-detection/testalgorithms/rfnet/RFNet/sedna_predict.py
Evidence
These files contain:
from sedna.datasources import IndexDataParse
and later:
data = BaseDataSource(data_type="test")
I could not find a local definition or import of BaseDataSource in these files.
Other RFNet/ERFNet modules in the repository explicitly import:
from sedna.datasources import BaseDataSource
Proposed Fix
Update the import statement:
# Before
from sedna.datasources import IndexDataParse
# After
from sedna.datasources import IndexDataParse, BaseDataSource
Notes
This issue was identified through code inspection and repository-wide searches while investigating similar missing-import patterns.
Related
Potential Runtime Impact
pre_data_process() contains:
data = BaseDataSource(data_type="test")
but BaseDataSource is not imported in the affected files.
If this code path is executed and BaseDataSource is not provided by the runtime environment, Python is expected to raise:
NameError: name 'BaseDataSource' is not defined
based on standard Python name resolution and import behavior.
Description
While reviewing the RFNet and ERFNet Sedna integration scripts, I noticed that several
sedna_predict.pyfiles referenceBaseDataSourceinpre_data_process()but only importIndexDataParsefromsedna.datasources.This appears inconsistent with other files in the repository that use
BaseDataSourceand explicitly import it.Affected Files
examples/robot/lifelong_learning_bench/semantic-segmentation/testalgorithms/rfnet/RFNet/sedna_predict.pyexamples/cityscapes-synthia/lifelong_learning_bench/curb-detection/testalgorithms/rfnet/RFNet/sedna_predict.pyexamples/cityscapes-synthia/lifelong_learning_bench/semantic-segmentation/testalgorithms/rfnet/RFNet/sedna_predict.pyexamples/cityscapes-synthia/scene-based-unknown-task-recognition/curb-detection/testalgorithms/rfnet/RFNet/sedna_predict.pyEvidence
These files contain:
and later:
I could not find a local definition or import of
BaseDataSourcein these files.Other RFNet/ERFNet modules in the repository explicitly import:
Proposed Fix
Update the import statement:
Notes
This issue was identified through code inspection and repository-wide searches while investigating similar missing-import patterns.
Related
robot-cityscapes-synthiapath: [robot-cityscapes-synthia] NameError: 'BaseDataSource' is not defined in sedna_predict.py — missing import at line 46 #466 (PR fix(examples): add missing BaseDataSource import in sedna_predict.py #512)Potential Runtime Impact
pre_data_process()contains:but BaseDataSource is not imported in the affected files.
If this code path is executed and BaseDataSource is not provided by the runtime environment, Python is expected to raise:
NameError: name 'BaseDataSource' is not defined
based on standard Python name resolution and import behavior.