ODM Tools: Deriving new data series is slow
- Dominant language
- Visual Basic .NET
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
horsburgh[CodePlex]
My name is Christopher Tennant and I am working with Ben Crosby at Idaho State University on a hydrologic climate change study in the Salmon River basin. We have recently created an ODM database on our local HIS server and have uploaded our data to the
database. I am using ODM Tools 1.1 to connect to the database and process our data. I am having a problem when I try to quotderive a new data setquot to edit erroneous values. I can get to the point where a small box titled quotCreating the Data Series
...quot with a progress bar appears. The progress bar proceeds to ~10% complete and then stalls. I have yet to receive an error message from ODM tools, I have let this process run for ~1.5 hours and there is never any change. Essentially I am following the
steps outlined in your ODM Tools Version 1.1 (July 2008) help document that detail the process for creating a derived data set. Everything is like your tutorial describes, except that once I select the quotCreate a Quality Controlled Data Series for Editingquot
radio button in the quotDerive A New Data Seriesquot pop-up window it does not automatically switch to quot1 - Quality controlled dataquot within the quotQuality Control Level:quot drop down menu. To activate this menu I have to select the quotAutomatically
generate a Method Descriptionquot radio button before the Data Series Attributes become interactive. Once I select a quality control level the quotDerive New Data Seriesquot button becomes interactive, I activate this function and then I run into the
dilemma described above.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the ODM Tools 1.1 workflow described in the issue and the referenced July 2008 help document, including the quality-control level selections. Investigate why creating the derived data series stalls near 10% without an error; the work is done when the series completes or reports a useful failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- visualbasic
- Domain
- databases, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100