Topic: "LOAD FACTOR ERROR"Subscribe | Previous | Next
Karla Cassandra Borjal 7/25/2022
Good day!
I am currently using the Leap 2020.1.0.69 (64bit) version and following the Training Exercise Video #1
I used the exact given on the training exercise but I still encountered this Load Factor Problem.
I hope you can help me with this to continue to finish my output.
Thank you very much,
Karla Borjal
Charlie Heaps 7/25/2022
Could you send me a copy of that data set Karla (backup as a .leap file) so I can look into this? Please send to leap@sei.org.
Thanks!
Charlie
Karla Cassandra Borjal 7/26/2022
Karla Cassandra Borjal 7/29/2022
Good day Sir!
i would like to follow up regarding this issue.
I already sent you the file that I am currently working on.
Hope you can help me!
Thank you and Best Regards,
kARLA
Muhammad Kashif Shahzad 8/3/2022
Dear Karla,
I am in hands-on training of LEAP and encountered the same problem, The trainer tried to fix it and the same has been referred back to support guys and an answer is awaited. I encountered the same error on "Transformation".
However, i deleted the branches and sub-branches and followed the video while i was back from training .............. the error was gone, i concluded that while following the video we sometimes miss something (parametrization), e.g. feedstock has to be 100 which is by default 100 and if not will get us to the same error.
I suggest you remove the branches and sub-branches and redo while following the video and every time save the project and click on results so that you know what results in this error.
If you manage to find or encounter the same error do share it with the community.
Regards,
Kashif
Muhammad Kashif Shahzad 8/3/2022
Dear Karla,
Just came across please check the demand, capacity and historical production units ............ when units gets mismatched available capcity and demand gets to a mis match until unless we have put a sufficent reserve margin.
Be very careful with the units.
Regrads,
Kshif
Charlie Heaps 8/16/2022
Hi all - this issue should now be fixed in LEAP v2020.1.73 and later. Sorry for the problems!
Charlie