Time Dashboard - Calculation/Visualization Question (Level of Detail) - calculation

I’m reaching out to see if you can help me get unstuck on a Tableau visualization and calculation.
We are trying to calculate and visualize utilization rate as defined as a numerator (“Projects” + “Initiatives” charged time) divided by denominator (Number of timesheets submitted times 40 hours).
The screenshots below detail what is currently occurring vs what we want to show.
Currently
The denominator is understated because it is identifying unique timesheets times 40 hours separately for “Projects & Initiatives” and “Remaining Time” pie chart pieces.
Results in higher inaccurate utilization rate of 73% (50,584 / 69,400). These red numbers are not what we want.
What we want
First screenshot below shows how we want utilization rate to be calculated to result in 69% (50,584 / 73,080). Bold numbers are what we want. I tried playing around with FIXED and INCLUDE Level of Detail calculations, but couldn’t get it to work as intended.
I included more supporting screenshots below to provide more context.
Any guidance would be truly appreciated!
Summary of Issue
Visual
Tableau Visual
Denominator details
This is what we want to see in Tableau.
Denominator manual details
This is the current denominator calculation.
c.ChargeableHours
Here are some relevant key fields. Note that “Time Charged” is the same as “Time_Logged_Project_Total” (Just renamed). Also, we don’t want to use the 73,097 total below as some individuals charge more than 40 hours in some of their weekly timesheets. We want our calculation to max at 40 as indicated in the screenshot above using unique timesheets.
Key Fields

Related

MQL4 gets different data than the MT4 History Center shows

I'm quite new to MQL so this may be a misunderstanding.
This code:
Print( TimeToStr( iTime(NULL,PERIOD_M5,i), TIME_DATE|TIME_MINUTES), iOpen(NULL,PERIOD_M5,i), iHigh(NULL,PERIOD_M5,i), iLow(NULL,PERIOD_M5,i), iClose(NULL,PERIOD_M5,i) );
Prints this:
2023.01.05 23:25, 0.91648, 0.91678, 0.91636, 0.91676
If I export data from the History Center I get slightly different numbers:
2023.01.05T23:25, 0.91646 ,0.91675, 0.91633 ,0.91675, 146
The values are just a tiny bit smaller. This is consistent - ALL of the values exported from the History Center are a bit lower than what I see when I examine the data with iOpen() etc. The difference seems to range from 0.1 to 0.3 pips.
I assume this is a Bid vs Ask thing. Is it? I understand the iOpen() etc returns Bid prices. But does the History database contain both Bid and Ask? Is there a way to see both prices?
Or it it just guessing? If so, it does not seem to be adjusting the prices consistently.
Edit: I am running in the Strategy Tester.
Edit2: Today I downloaded a bunch of M1 data from Dukascopy and imported it into MT4 History Center. Now I get exactly the results I expect from my program.
But my question stands, about the data MT4 downloads from the broker.

Plot raw time series with Kibanan Timelion

I might not get something. How can I plot a raw time series with Timelion without applying any further aggregation? Just the raw data of a field over time that I have in an index. Of course I select the proper time window for the data.
I was trying to achieve the same thing, but didn't fully get what I wanted, but maybe these steps will help you.
My data was on by minute basis, so I don't want any more frequent fragmentation. Selecting interval = 1m helps only for short periods of time, but adding "interval=1m" into .es() block works on long periods, too.
To have lines not to return to 0 in between points, use .es().fit(carry)
.es().scale_interval(1m).fit(scale) - this is my chart to return to 0 if there were no data for certain period rather than carrying the line on the same level.
.es(metric=max:value_field) helps not to sum up the values, but show the max of the aggregated set.
My charts are still weirdly aggregated, but maybe it'll help someone.
Useful links:
Sparse time series in timelion
https://www.elastic.co/blog/sparse-timeseries-and-timelion
Scaling issue 1
https://discuss.elastic.co/t/diferent-value-on-y-axis-depending-on-time-interval/67785
Scaling issue 2
https://discuss.elastic.co/t/timelion-giving-wrong-metric-aggregate-value-on-enlarging/132789
Scaling issue 3
https://discuss.elastic.co/t/re-timelion-giving-wrong-metric-aggregate-value-on-enlarging/132925

Precise definition of HL7(v2) field RXE-25?

Can anyone explain what the field of RXE-25 in HL-7v2 means? The description is "Give strength". I have read the official explanation, but I feel this is ambiguous. I am not sure whether this field should contain a)the strength of a single tablet/dose form vs b)the total strength to administer.
For example, hydroxychloroquine [HCQ] is a lupus medication that comes in 200 mg tablets. Lupus patients are frequently started off on 400 mg of this per day (ie 2 tablets).
Let's say RXE-3 ("Give Amount - Minimum") is "2", and RXE-5 ("Give Units") is "tablet". And let's assume there are multiple tablet strengths, so we don't know what dose that is. Would one put the per-tablet dose in RXE-25 (ie "200" mg), or instead put the entire dose (2 tablets="400" mg)?
My understanding of all the 'Give' fields is they represent the amount given per dose. So to answer your questions:
b)the total strength to administer
AND
put the entire dose (2 tablets="400" mg)
Actually, I found the answer hidden in another part of the HL7 documentation, specifically under the RXO segment (RXO-18 Requested Give Strength). Per that documentation, this applies to various RX_ segments.
The example given:
One way would be: "Ampicillin 250 mg capsules, 2 capsules four times a
day." In this case the give amount would be 2, the give units would be
capsules, the strength would be 250 and the strength units would
milligrams.
So it seems the GIVE STRENGTH AMOUNT (if present, and no GIVE DRUG STRENGTH VOLUME is specified) is multiplied by the GIVE AMOUNT to come up with the total dose. So I believe the answer to the example in the question would be a) 200 mg.

Find multiples of given values with minimum mismatch in making desired total number

I am new to google sheets and question which I am asking is typical math question.
I have a value (in d3) which refers to total gram of gas required, now I have to release this much (d3) gas from number of gas Cans. Gas Cans are of two kinds bigger one contains 680 grams gas and small one contains 454 grams of gas.
Now once we open the gas CAN then whole gas will be released mean to say that we cannot release part portion of gas however we can minimize wastage if we use exact (or near to exact) amount of gas required by using some big cans and some small cans. I have worked hard and found a way (see in c3:c5 and also see in b12:c12) but that is too long & that has been shown in below mentioned link.
Now I want total no. of big cans and small cans in d4 & d5 with a formula so that same criteria can be applied to all values.
It has been explained in detail with example in following link:
https://docs.google.com/spreadsheets/d/1zZiKMqb33kDSOIduBMayZ0NMqibcvMF-UBYYvn7VVBs/edit
Thanks in advance.
For D4 you can have =FLOOR(FLOOR(G3/680)+MOD(G3, 680)/454) and for D5 you can have =IF(G3 > G4*680, CEILING(MOD((G3-G4*680)/454, 454)), 0).
Not sure if it will work for all cases though, so make sure you do some testing. In D4, it does the same thing you did where you find the whole number of big cans. It then also calculates if the remainder is larger than one small can, then another big can will be added (it is effectively your "> 66.76" calculation). In D5, the remaining grams are calculating after taking into account how many big cans there already are. If there are remaining grams, then one small can would be calculated. If there are enough big cans to hold the gas, no small cans are necessary. It includes some calculation, but =IF(G3 > G4*680, 1, 0) should work the same, since there should only be one or zero small cans.

Interpreting results from contiki's powertrace app

I am using contiki's powertrace (that in turn uses ENERGEST) to get power consumption. I came across the formula for that to be= ((rxon)*(RXi)*Vcc)/(cpu+lpm).
Where rxon, cpu and lpm are obtained from powertrace (i.e. times the mote spends in these states) and RXi (current) and Vcc (voltage) from datasheet.
My question is if I need to obtain total current consumption do I just remove the Vcc or do i need to remove Vcc and divide the whole thing by RTIMER_ARCH_SECOND. Since i read somewhere that powertrace results time in Rtimer ticks.
Thank you,
Avijit
If your formula is the calculation of the average total power consumption where (cpu+lpm) is the whole period, then you do not have to convert the time values in real seconds. The formula is a ratio and if your divide the numerator by RTIMER_ARCH_SECOND you need equally to divide the denominator, which brings you to the same result.
The following link explains in detail and with examples how to use powertrace. It provides the formula that you need:
http://thingschat.blogspot.de/2015/04/contiki-os-using-powertrace-and.html

Resources