1 страниц (5 вхождений)
Vlookup Delay - Сообщения
#1 Опубликовано: 18.02.2018 12:15:39
An automatic electronic device had been installed on the bank of a stream to record and transmit Water Levels (at half hour intervals) to a control center, where the readings were converted to discharge values, for further analysis, using an already established Rating Table. These data are given in an Excel file.
The attached SS file takes nearly 2 minutes to convert 1 month data values (48x31=1488).
I have tried this with several previous SS versions also.
Can this be improved, as we have to deal with data recorded for over 5 years?
My system: Win 10 Pro, 64 bit, Core i5, 6 GB Ram Laptop.
Any help will be much appreciated please
WL To Q.sm (18 КиБ) скачан 42 раз(а).
1.July WL&RT.xlsx (29 КиБ) скачан 61 раз(а).
Файл не найден. Файл не найден.
The attached SS file takes nearly 2 minutes to convert 1 month data values (48x31=1488).
I have tried this with several previous SS versions also.
Can this be improved, as we have to deal with data recorded for over 5 years?
My system: Win 10 Pro, 64 bit, Core i5, 6 GB Ram Laptop.
Any help will be much appreciated please
WL To Q.sm (18 КиБ) скачан 42 раз(а).
1.July WL&RT.xlsx (29 КиБ) скачан 61 раз(а).
Файл не найден. Файл не найден.
Look within!... The secret is inside you.
Best Regards
Eng. NDTM Amarasekera - Sri Lanka
#2 Опубликовано: 18.02.2018 15:42:00
Hello.
First impression is that you should try using findrows(...) function (built in into the program) in this case.

Before change:
2 min. 14 sec.
After change:
2.4 sec.
But I see different results of using vlookup implemented in your worksheet (returns 1488 rows vector) and findrows (returns 2976 rows vector). Unfortunately I have no chance to deep into the logic, but this may be a good starting point.
Best regards.
First impression is that you should try using findrows(...) function (built in into the program) in this case.
vlookup(value,table,column):line(findrows(table,value,column-1),1,1)
Before change:
2 min. 14 sec.
After change:
2.4 sec.
But I see different results of using vlookup implemented in your worksheet (returns 1488 rows vector) and findrows (returns 2976 rows vector). Unfortunately I have no chance to deep into the logic, but this may be a good starting point.
Best regards.
#3 Опубликовано: 18.02.2018 16:23:08
Did find 5 minutes more to look into it and finally I did it:
WL To Q_mod1.sm (16 КиБ) скачан 62 раз(а).
Takes 1.7 sec. on my environment.
Best regards.
WL To Q_mod1.sm (16 КиБ) скачан 62 раз(а).
Takes 1.7 sec. on my environment.
Best regards.
#4 Опубликовано: 18.02.2018 17:19:13
WroteFirst impression is that you should try using findrows(...) function (built in into the program) in this case.
Maybe the other way around => vlookup needs be doctored.
Mine works fine 0.06 s scanning 9 rows for one value
FindRows => 2.4 s scanning 31 rows ... for ONE value, is it ?
Utilities Matrix lookup.sm (11 КиБ) скачан 58 раз(а).
#5 Опубликовано: 18.02.2018 23:16:33
WroteDid find 5 minutes more to look into it and finally I did it:
Look within!... The secret is inside you. Best Regards Eng. NDTM Amarasekera - Sri Lanka
1 страниц (5 вхождений)
-
Новые сообщения
-
Нет новых сообщений