Fadi Bitar 7/1/2014

Like

1711 Views

Hi,

I'm trying to replicate an existing (non-LEAP) model into LEAP, and started importing the area's load curves as Yearly Shapes from Excel.

When I look at the resulting shapes in LEAP, they seem rather off however.
So for the sake of trying to understand the four kinds of yearly shapes available, I did a small test where I built an hourly time series with 8760 times 100 values (basically a constant function with 8760 time steps), and imported it four times using the "Import Hourly Shape" function, once for each shape type.

My time slices are as follows: "4 Seasons, Day and Night, Weekdays, Saturday and Sunday", resulting in 24 time slices.

The resulting curves make very little sense to me. For instance the Winter Weekday Day and Winter Weekday Night time slices have different values for all types of shapes, even though they have the same number of hours (and again, we're dealing with a constant function).

I can provide some data on this, but again this is fairly easy to reproduce, and I'm not sure if this is a bug in the system or if I'm missing something.

I appreciate the feedback, with an explanation of how the different shape types are calculated if possible.
I'm using version 2014.0.5

Thanks !

Taylor Binnington 7/2/2014
 

Like

1707 Views

Hi Fadi,

You are correct - the results you are seeing in your imported yearly shapes are due to a small bug in LEAP when hourly values are imported into time slices with night/day divisions. We are aware of it, but it is still unresolved. We hope to have it fixed as soon as possible, and very much apologize for any inconvenience in the meantime.

By the way (although it would not have helped this time), be sure you're using the most recent version of LEAP, by clicking Help: Check for Updates.

All the best, and we'll be in touch when the issue is resolved,

Taylor

Fadi Bitar 7/3/2014
 

Like

1690 Views

Ok thanks for the quick feedback.

By the way, I noticed something as well if I set up my time slices to 8760 hours instead. When I try importing a yearly shape, it takes forever to create the new shape, and eventually crashes LEAP.

Is that also something that you're aware of and planning to fix?

Thanks !

Taylor Binnington 7/7/2014
 

Like

1689 Views

Hi Fadi,

This is a good question, and one that several users have asked about. See this recent post for a short description of why we caution users against using hourly time slices:

http://www.energycommunity.org/default.asp?action=9&read=2998&fid=22

We do not necessarily consider it a 'bug', and therefore we are not planning to fix this issue, but instead suggest that users avoid using hourly slices.

Taylor