Calculation of Fuel Consumption

[Robotoks]

Thank you for your contribution. It really helps.
However, few data are available for the Fuel Rate attribute.
Almost all records has no fuel rate value.

[gsoh]

Hi,

Fuel consumptions are obtained through 3 different ways as described in our VED paper (Algorithm 1), using three attributes of the data "Mass-air flow" and/or "Absolute Load" and/or "Fuel Rate".

Note, the data attribute "Fuel Rate" should not be confused with the availability of the fuel consumption information. In this sense, the populated percentage of the attribute "Fuel rate" in the Table 2 does not represent the availability of "fuel consumption rate" or "fuel consumption". Because, for most vehicles, the estimation of fuel consumption & fuel consumption rate is obtained through "Mass-air flow" and/or "Absolute Load".

Please refer to the paper for the details.

[Robotoks]

Hi, Thank you for your reply. It really helps. Is it possible to compute the fuel consumption based on speed ? Is there a relation between speed and fuel consumption ? According to Algorithm 1 in your paper, fuel consumption is related to MAF or fuel rate or AbsLoad and RPM. Best regards Le jeu. 10 oct. 2019 à 00:33, GS Oh <notifications@github.com> a écrit :

…

Hi, There are 3 ways to obtain fuel consumptions & fuel consumption rates of vehicles: as described in our VED paper (Algorithm 1). You can calculate fuel consumptions and fuel consumption rates using "Mass-air flow" and/or "Absolute Load". Note, the populated percentage of the attribute "Fuel rate" in Table 2 does not represent the availability of "fuel consumption rate" since fuel consumption & fuel consumption rate can be estimated through "Mass-air flow" and/or "Absolute Load". The "Fuel rate" attribute in Table 2 rather represents the "Fuel rate" records directly reported by vehicles (only a few vehicles directly reported the "Fuel rate" attribute; thus we estimate fuel consumption rate using "Mass-air flow" and/or "Absolute Load") Please refer to the paper for the details. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=ANN3AYEEHGG2GCMLEUIZW2LQNYBXBA5CNFSM4I63YUK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAYP7BY#issuecomment-540082055>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANN3AYCBINIPVHZVFPAUJIDQNYBXBANCNFSM4I63YUKQ> .

[gsoh]

Hi,

You could "approximate" fuel consumption using speed based on a set of assumptions about the vehicle types, powertrains, mass in a specific scenario. However, since the approximation involves simplications, you would not obtain as accurate fuel consumption as you would when you use MAF/AbsLoad/RPM with correction factors.

One of the motivations behind making this dataset public is to share accurate fuel-consumption big-data. In this sense, we recommend using Algorithm 1 of our paper to compute fuel consumption as accurately as possible.

Thanks!

[Robotoks]

Any data of Michigan road network please ? (i.e., links, start-node-id, end-node-id) Thank you. Le jeu. 10 oct. 2019 à 22:07, GS Oh <notifications@github.com> a écrit :

…

Hi, You could "approximate" fuel consumption using speed based on a set of assumptions on vehicle types, powertrains, mass in a specific scenario. However, since such a relationship between fuel consumption and speed is highly approximated and simplified, you would not obtain as accurate fuel consumption as you would when you use MAF/AbsLoad/RPM. One of the motivations behind making this dataset public is to share accurate fuel-consumption big-data. In this sense, we recommend using Algorithm 1 of our paper to compute fuel consumption as accurately as possible. Thanks! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=ANN3AYF2HLJDYPNKTE6FKLTQN4ZL7A5CNFSM4I63YUK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA4PNWI#issuecomment-540604121>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANN3AYCLOWU4JEZAPPTXT4LQN4ZL7ANCNFSM4I63YUKQ> .

[Robotoks]

Hi.. 1/ For STFT and LTFT attributes, in your dataset, there are two values for each measure (Short Term Fuel Trim Bank 1[%] and Short Term Fuel Trim Bank 2[%], etc..) Please, what is the difference between them? and which one should we use to calculate correction ? 2/ Some records of STFT have negative values, should we use | STFT | or keep them ? 3/ In the data set, which attribute representing the Engine Cylinder Displacement ? 3/ For correction calculation, i observed that even MAF is available or could be calculated, in some records, STFT and LTFT are not. So i think that the algorithm can be rectified to consider this issue. To Thank you again for your effort in collecting this data-set. Best regards,

[gsoh]

Hello,

While we appreciate your questions, you will be able to find answers for the questions.

1. Please refer to the paper for brief explanations on STFT and LTFT. It's up to you which one to use.
2. You should not take the absolute value of STFT. You should just use STFT.
3. The "engine configuration & displacement" attribute of VED_Static_Data_ICE&HEV.xlsx and/or VED_Static_Data_PHEV&EV.xlsx files. The paper also mentions it.
4. You are correct that STFT and LTFT are not always available when MAF is available. One way (but not the only way) to compute the correction term is as follows:

flag = 0
if STFT1 and LTFT1 are available, flag = 1
if STFT2 and LTFT2 are available, flag += 2
if flag == 1:
correction = (1+0.01STFT1+0.01LTFT1)/AFR
elif flag == 2:
correction = (1+0.01STFT2+0.01LTFT2)/AFR
elif flag == 3:
correction = (1+0.005STFT1+0.005LTFT1+0.005STFT2+0.005LTFT2)/AFR
elif flag == 0:
correction = 1

Even though we used the above algorithm to obtain the results presented in the paper, we did not describe the algorithm in the paper simply because we wanted the algorithm to be general, since there are other ways to compute the correction terms.

Thanks.

[Robotoks]

Hi All, After applying Algorithm 1, we get FCR in [L/H] or [g/sec] or [L*rev/min] ? Thank you Le mer. 27 nov. 2019 à 07:14, GS Oh <notifications@github.com> a écrit :

…

Closed #1 <#1>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=ANN3AYG7PBHN4UEXGLXZFOTQVWUV5A5CNFSM4I63YUK2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVDT6PPQ#event-2833770430>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANN3AYHQWU7LB7YAN5UZOHLQVWUV5ANCNFSM4I63YUKQ> .