Elements from within PROCS are causing problems when reading in network components.
Open
bug
good first issue
Nexus
- Dominant language
- Python
- Stars
- 23
- Forks
- 8
- Avg merge
- 16d 4h
- Merged PRs (30d)
- 1
Description
**Describe the bug**
Constraints were given date values equal to ">" as
**To Reproduce**
Steps to reproduce the behavior:
The following data in the network file would cause the problem when reading in the constraints using a model.network.constraints.get_all().
NexusConstraint(name='WELL1', date='>', max_surface_liquid_rate=6100.7)
```
TIME 04/10/2019
PROCS NAME PROCNAME
IF(TIME > 0.0) THEN
DO something
ENDPROCS
CONSTRAINTS
WELL1 QOSMAX 6100.7
ENDCONSTRAINTS
```
**Expected behavior**
Content within PROCS routines should be ignored for now.
the constraint should be NexusConstraint(name='WELL1', date='04/10/2019', max_surface_liquid_rate=6100.7)
Contributor guide
Assessment
This issue has not been assessed yet.