Veda2.0 Released!


UC_CAP LO read as UP in VEDA-FE
#1
Dear all,

perhaps I found a bug in VEDA-FE.
I have UC on capacity shares as below. The problem is that VEDA reads also the SL_Car_2015 as limit time UP.
I have tried it several times even after restart of VEDA-FE.

If I change the limit time of SL_Car_2015 in dd file, it works fine.

I do not know, if the error is in my procedure or in Veda.

Lukas
Code:
~UC_SETS: R_E: CZ                                                                        
                                                        ~UC_T                                                    
UC_N             Pset_PN    UC_ATTR~RHS    Side       LimTipe    Attribute    UC_RHSRT~2016    UC_RHSRT~0    2016    2017    2018    2019    2020    2021    2022    2023    2024    2025    UC_Desc
SU_Car_2007    CAR*2007*    CAP,SYNC    LHS         UP            UC_CAP                    0        5             7            7            7    8    8    10    Max share of car vnt 2007
            CAR*                        RHS                UC_CAP                        1                                        
SL_Car_2015    CAR*2015*    CAP,SYNC    LHS         LO            UC_CAP                    0        5             13    9    9    6    4    3    3    2    2    2    Min share of car vnt 2015
            CAR*                        RHS                UC_CAP                        1
Reply
#2
I am not a VEDA developer, but would be curious to see if I can reproduce the problem.

Unfortunately, the table columns and layout are not clear to me from the post above. Could you thus post an image, or the Excel sheet?
Reply
#3
Sorry,
it was fine on my screen.

An Excel sheet is attached.

Lukas


Attached Files
.xlsx   Veda_prombem.xlsx (Size: 9.41 KB / Downloads: 18)
Reply
#4
Thanks!

Ok, now I was immediately able to spot a suspicious column header: LimTipe

I think it should read LimType, and I am pretty confident this typo is causing the problem, but I will test it to be sure.

The default is UP, which would explain that you got UPs.

[EDIT:] Yes, it worked fine for me when using LimType.
Reply
#5
(13-01-2017, 08:23 PM)Antti-L Wrote: Thanks!

Ok, now I was immediately able to spot a suspicious column header: LimTipe

I think it should read LimType, and I am pretty confident this typo is causing the problem, but I will test it to be sure.

The default is UP, which would explain that you got UPs.

[EDIT:] Yes, it worked fine for me when using LimType.

Ou, thank you very much!
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Veda Help Saad Awan 2 1,303 11-07-2023, 02:51 PM
Last Post: Saad Awan
  Veda Help Saad Awan 15 6,145 11-07-2023, 12:55 PM
Last Post: AKanudia
  Veda Errors Saad Awan 0 746 03-07-2023, 06:10 PM
Last Post: Saad Awan
  Veda Errors Saad Awan 2 1,475 16-06-2023, 04:06 PM
Last Post: Saad Awan
  CSV Export in Veda olexandr 4 4,813 21-04-2021, 08:36 PM
Last Post: AKanudia
  MAC vs. Windows for VEDA-TIMES FE & BE? mbr1818 5 10,558 22-02-2021, 01:52 PM
Last Post: AKanudia
  problem with (re)SYNC of previous working models/DB after reinstall of VEDA Koen Smekens 9 8,843 29-12-2020, 08:01 PM
Last Post: Antti-L
  Fatal error in VEDA opening vahid.aryanpur 2 4,387 15-07-2020, 06:05 PM
Last Post: vahid.aryanpur
  Unexpected termination of the VEDA-FE run seckg 3 5,968 21-09-2019, 07:25 PM
Last Post: Antti-L
  Results in VEDA BE MohammedAbiAfthab 0 2,345 02-07-2019, 05:39 PM
Last Post: MohammedAbiAfthab

Forum Jump:


Users browsing this thread: 1 Guest(s)