13-06-2017, 01:10 AM (This post was last modified: 13-06-2017, 01:18 AM by Pacarval.)
Dear Antti,
I am runninng my model with 108 timeslices (12 seasons, 3 weekdays (weekday, saturday, sunday) and 3 day periods (morning, day, night). I have a load curve for the electricity sector with 108 timeslices and for the moment I am using the same load curve for all ELC demands (residential, commercial, industry, etc.). When I use the COM_FR to set the load curve the model only 'reads' 48 timeslices instead of 108. Sixty timeslices are left out. The model however correclty reads, for example, the 108 timeslices for the PV technology process. Which would mean that the timeslices are well defined in the syssettings template....
Do you know why this might be happening?
I am attaching the VT for the residential sector so you can see the timeslices, as well as the syssettings template. I also attach a screenshot of the commodity master showing how the model only picks 48 timeslices. I am getting errors when I sync: INVALID TS. (Also attached)
I have the same problem. Would you mind letting us know how to solve this issue? This error isn't explained anywhere on your website. When I added timeslices to shape the demand, as explained in demo_004, it ignores it by throwing this error: "Invalid TS!"
(29-06-2017, 12:42 PM)AKanudia Wrote: Region and TimeSlice definitions (~BookRegions_Map and ~TimeSlices Tags) are read only when SYNC starts from scratch.
So, Tools - Start from scratch should solve the issue for both Pablo and you.
Actually, I tried it last night and also right now. Again, it gives same error but the number of errors decreases to 4 from 16. When I click on the check. It shows FAD (Fall, days) and FAN (Fall, nights) for 2014 and 2015.
I almost lost my mind with this issue, haha. The fix is actually pretty simple. You must check thoroughly your timeslice names in the SYSSETTINGS template (e.g. JAN,WK,DAY,NITE,etc.). I discovered that if you leave a blank space after the timeslice name the space is considered as part of the name, so when VEDA syncs it does not recognize any COM_FR that don't have a blank space after the name. Does that make sense? For example my day timeslice was represented with letter D, but when I looked at the cell where I defined it, I actually typed in D_ (letter D + a blank space). I deleted all blank spaces after any timeslice name definition, and the veda synced correctly. Try this out!
I almost lost my mind with this issue, haha. The fix is actually pretty simple. You must check thoroughly your timeslice names in the SYSSETTINGS template (e.g. JAN,WK,DAY,NITE,etc.). I discovered that if you leave a blank space after the timeslice name the space is considered as part of the name, so when VEDA syncs it does not recognize any COM_FR that don't have a blank space after the name. Does that make sense? For example my day timeslice was represented with letter D, but when I looked at the cell where I defined it, I actually typed in D_ (letter D + a blank space). I deleted all blank spaces after any timeslice name definition, and the veda synced correctly. Try this out!
Cheers,
Pablo
Yes. Exactly after Fall (FA), I had blank space. I hope it will solve my problem. Thank you so much.
AKanudia, I guess it would be a good idea to use "Trim" command to get rid of invisible free space before or after time slices. It is really hard to detect with naked eyes.
