Identifying the source of infeasibility in FlexTool input.

[hbshrestha]

Hi. I am running a model scenario - the model solve is infeasible and I get the following error message at the end:

GLPSOL wrote the results into csv files

INFO:flextoolrunner.py:1866:Success!
ERROR:run_flextool.py:64:Model run failed: [WinError 2] The system cannot find the file specified: 'output/annualized_dispatch_costs__period__t.csv'
Traceback:
Traceback (most recent call last):
  File "run_flextool.py", line 62, in main
    return_code = runner.run_model()
                  ^^^^^^^^^^^^^^^^^^
  File "C:\Users\HShrestha\.spinetoolbox\work\flextool3__1ac5064c820c409bb9b32ddaef8894f7__toolbox\flextool/flextoolrunner.py", line 1918, in run_model
    os.remove("output/annualized_dispatch_costs__period__t.csv")
FileNotFoundError: [WinError 2] The system cannot find the file specified: 'output/annualized_dispatch_costs__period__t.csv'

Kernel died (×_×)
>>> 

The model status is infeasible as shown:

In the console, I also saw following conflict messages. I tried to remove storage availability in input, but the error still persists. Is there a way to identify the precise source and location of infeasibility from the console message? I am attaching the input file and console log.

Console log.txt

[hbshrestha]

After excluding battery investment option, my model is infeasible.

As stated in the documentation, I am considering if the infeasibility is caused because I am using multiple storage methods.

Having multiple storage methods can create infeasible problems. This is why some of the combinations shouldn't (and cannot) be used at the same time. If multiple methods are used, some of them might be ignored by the method hierarchy.

[hbshrestha]

Removing these storage methods, or using only 1 or 2 of them did not work.
I noticed that I had not specified invest_periods.
Now testing by setting realize_periods to yes in solve_period sheet.

[jkiviluo]

If I still remember correctly, the issue was about storage methods that ended up being conflicting. These can be bit difficult to get right. The recommendation is to copy from https://irena-flextool.github.io/flextool/how_to/#how-to-add-a-storage-unit-battery or some later storage how-to depending on your needs. Also, test first with one storage, change things step-by-step, so you can see when an infeasibility might pop-up.

[ArttuTupala]

Hi,

I wondered that that the storage methods should not cause infeasibilities anymore, so I checked the data.
The real problem here is that you have flow groups with investment constraints. These are Battery_Storage_Group, PV_Tracking_Generic and Wind Generic. By flow group I mean that they include connection__nodes or unit__nodes. It is unclear to which part of the pair the constraint limits. They should include nodes, units or connections to work with the investment constraints.
I added a check to catch this specific problem.