Unnormal results

[Antti-L]

Have you not read the documentation about TIMES attributes?
AFA is a VEDA alias name for NCAP_AFA(r,y,p,bd).  It does not have any timeslice index. It defines an ANNUAL utilization factor, as I already reminded above. I guess VEDA just needs to discard the values in the previous lines, because you define values for the same parameter instances repeatedly, 12 times in a row.

[[email protected]]

Have you not read the documentation about TIMES attributes?
AFA is a VEDA alias name for NCAP_AFA(r,y,p,bd).  It does not have any timeslice index. It defines an ANNUAL utilization factor, as I already reminded above. I guess VEDA just needs to discard the values in the previous lines, because you define values for the same parameter instances repeatedly, 12 times in a row.

Yes you have reminded me before, where could I find the documentation? 
By the way, it is strange that these two days when I am using the sync from VEDAONLINE, there is no window showing the process and I cannot go ahead to the run-manager.

Best,]
Xiao

[AKanudia]

TIMES doc: https://iea-etsap.org/index.php/documentation

Attribute Master tab on Veda online has summary details of TIMES attributes.

[Ravinder]

Have you not read the documentation about TIMES attributes?
AFA is a VEDA alias name for NCAP_AFA(r,y,p,bd).  It does not have any timeslice index. It defines an ANNUAL utilization factor, as I already reminded above. I guess VEDA just needs to discard the values in the previous lines, because you define values for the same parameter instances repeatedly, 12 times in a row.

Yes you have reminded me before, where could I find the documentation? 
By the way, it is strange that these two days when I am using the sync from VEDAONLINE, there is no window showing the process and I cannot go ahead to the run-manager.

Best,]
Xiao

Dear Xiao,

We can arrange a web meeting with you to address the VedaOnline issue.

[[email protected]]

Have you not read the documentation about TIMES attributes?
AFA is a VEDA alias name for NCAP_AFA(r,y,p,bd).  It does not have any timeslice index. It defines an ANNUAL utilization factor, as I already reminded above. I guess VEDA just needs to discard the values in the previous lines, because you define values for the same parameter instances repeatedly, 12 times in a row.

Yes you have reminded me before, where could I find the documentation? 
By the way, it is strange that these two days when I am using the sync from VEDAONLINE, there is no window showing the process and I cannot go ahead to the run-manager.

Best,]
Xiao

Dear Xiao,

We can arrange a web meeting with you to address the VedaOnline issue.

Hi!

Thank you! What time are you available?

Best,
Xiao

[[email protected]]

TIMES doc: https://iea-etsap.org/index.php/documentation

Attribute Master tab on Veda online has summary details of TIMES attributes.

Hi Dr. Amit,

Thank you! 

Best,
Xiao

[Ravinder]

Have you not read the documentation about TIMES attributes?
AFA is a VEDA alias name for NCAP_AFA(r,y,p,bd).  It does not have any timeslice index. It defines an ANNUAL utilization factor, as I already reminded above. I guess VEDA just needs to discard the values in the previous lines, because you define values for the same parameter instances repeatedly, 12 times in a row.

Yes you have reminded me before, where could I find the documentation? 
By the way, it is strange that these two days when I am using the sync from VEDAONLINE, there is no window showing the process and I cannot go ahead to the run-manager.

Best,]
Xiao

Dear Xiao,

We can arrange a web meeting with you to address the VedaOnline issue.

Dear Xiao,

I will be available on Monday from 9:30-18:30 IST (Indian Standard Time).

[[email protected]]

Have you not read the documentation about TIMES attributes?
AFA is a VEDA alias name for NCAP_AFA(r,y,p,bd).  It does not have any timeslice index. It defines an ANNUAL utilization factor, as I already reminded above. I guess VEDA just needs to discard the values in the previous lines, because you define values for the same parameter instances repeatedly, 12 times in a row.

Hi Antti,

If so I think TIMES could not simulate the intermittency of Variable renewable energy (solar and wind). How can we describe the available factor for solar and wind in different time slice?

Best,
Xiao

[Antti-L]

Read the documentation, once again. The annual utilization factors and timeslice-specific availability factors are defined with different parameters, as I have tried to point out. Why did you choose to use the wrong parameter?

[[email protected]]

Read the documentation, once again. The annual utilization factors and timeslice-specific availability factors are defined with different parameters, as I have tried to point out.  Why did you choose to use the wrong parameter?

Okay, it should be NCAP_AF rather than NCAP_AFA. They are different. Thank you!

[[email protected]]

Have you not read the documentation about TIMES attributes?
AFA is a VEDA alias name for NCAP_AFA(r,y,p,bd).  It does not have any timeslice index. It defines an ANNUAL utilization factor, as I already reminded above. I guess VEDA just needs to discard the values in the previous lines, because you define values for the same parameter instances repeatedly, 12 times in a row.

Yes you have reminded me before, where could I find the documentation? 
By the way, it is strange that these two days when I am using the sync from VEDAONLINE, there is no window showing the process and I cannot go ahead to the run-manager.

Best,]
Xiao

Dear Xiao,

We can arrange a web meeting with you to address the VedaOnline issue.

Dear Xiao,

I will be available on Monday from 9:30-18:30 IST (Indian Standard Time).

Thank you! It has been resolved!

[[email protected]]

Hi guys. What attribute should I use to fix-limit the CAP_NEW to a constant (like limit the new wind technology to 10GW). It seems the NCAP_BND with a FX limit type doesn’t work.

[Antti-L]

> It seems the NCAP_BND with a FX limit type doesn’t work.

NCAP_BND(r,y,p,'FX') works very well for me.  It fixes the VAR_NCAP varibale to the desired amount of new capacity.  I am not aware of any case where it would not work, it has simply always worked for me.  However, it is of course not actually fix-limiting CAP_NEW to a constant, because CAP_NEW is not a variable but a reporting attribute, and it represents quantities different from VAR_NCAP.

[[email protected]]

> It seems the NCAP_BND with a FX limit type doesn’t work.

NCAP_BND(r,y,p,'FX') works very well for me.  It fixes the VAR_NCAP varibale to the desired amount of new capacity.  I am not aware of any case where it would not work, it has simply always worked for me.  However, it is of course not actually fix-limiting CAP_NEW to a constant, because CAP_NEW is not a variable but a reporting attribute, and it represents quantities different from VAR_NCAP.

Thank you Antti! It has been addressed!