CPLEX Error 1707 - Infeasibility, but can't find where

[henriqueanjos]

Hello guys,

I am getting this 1707 error message when I try to run my model, but don't know the origin of the error, could you guys support me on this issue, please?

The QA CHECK file contains the following message: 

*** RPC in TOP not found in any ACTFLO/FLO_SHAR/FLO_FUNC/FLO_SUM

*01 WARNING      -    R=BRI          P=CCGTLNG00    C=GASREG      IO=IN

However, I tried to manual inspect the BY file with this process and it seems to be ok. I believe I might be inputting something wrongly, I am attaching in case you want to check it.

The model period is between 2012 and 2035. When I run through 2015, I get a normal completion, but after that I got this message.

Another weird thing is that I upload an AF with low limit type for this process, but when I look into Basic Functions>Browse/Edit>Times View, the AF is uploaded with UP limit type. Why does it happen? I am attaching a screenshot of it.

Let me know if more information is required.
Thanks a lot in advance.

[AKanudia]

In VEDA_FE, parameter indexes are expected only in columns that are under or to the left of the FI_T tag. The LimType col is being ignored and default value of UP is showing up.

Are you planning to migrate to Veda2.0?

[Antti-L]

Concerning the warning:

*** RPC in TOP not found in any ACTFLO/FLO_SHAR/FLO_FUNC/FLO_SUM
*01 WARNING      -    R=BRI          P=CCGTLNG00    C=GASREG      IO=IN

Such a warning is issued if the GASREG flow of the process CCGTLNG00 is not found to be tied to any other flow of the process.  However, you are defining ACT_EFF for the process, and so this warning should not appear.  I just tested with a similar DAYNITE level power plant process (with ELC as an output, ELCGAS as an input and ACT_EFF(ACT)=0.5), and did not get any such warning issued. Therefore, it seems there is probably some subtle problem in your model with respect to this process, which I am not able to see from your screenshot or your Excel file.  But if you like, I can take a look and explain it, if you provide me with all the model input files (*.DD and *.RUN) for the case where you get this warning.

[Antti-L]

Ahhh... I guess it is just because of the erroneous AF(UP)=0 for all timeslices!  That makes the ACT_EFF "disappear" because there are no process timeslices left....