Strange behaviour exporting Math channel based on a user input [BUG?]
I have a async, Integer, user input where I enter a numeric value (dead weight load) then a math channel that inverts that load (allowing a negative numeric value).
Storage set to fast on trigger, slow otherwise.
Once armed the objective is to type in the value of a dead weight as its hanging on a strain gaged part, press and release trigger for a second's worth of data, load more weight, type in the new value, press and release trigger, etc... for a total of 4 "events" per data file
The problem I'm having is when I export to csv, the formula channel is not what is entered in the user input. Sometimes it is, mostly its not.
I've used this setup before on an older version of Dewesoft and never encountered this issue. Worked like a charm. Something must've broke in recent releases.
The machine I'm using this on is DS 2023.2
In the SS below are my 4 triggered events and the corresponding dead weight loads entered in the user input. The math channel is there because I need negative values when loading in compression.
Formula column should output 0, -50, -100, -150
The first two rows in the formula column are garbage, third row should be -100, 4th row is correct.
It does not always export garbage to the same rows either.
The above is a dummy data file just get screenshots for you but the issue is present regardless.
Attached files:
Dear Lemmy,
from the image I can see that you are exporting reduced data, average value. If you set the display type in Recorder to 'Average,' you can see how this data looks (they match the values in the exported table).
I recommend exporting the Full speed data, where you will obtain the values you are looking for.
Do you maybe know in which older versions of Dewesoft you got different export values - you can check the Dewesoft version which is displayed in Version Column under Analyze tab?
Best regards,
Eva
Eva, Thanks for the response. 2021.2 RC 210430 was the previous version but looking back on the old data I don't think I exported avg.
Are you saying in order to get the values I'm interested in, I need to EXPORT full speed? or change the display type in the recorder? Either way, this behaviour doesn't feel right and I almost passed this csv off as calibration data to another department. I'm glad I checked it!
The reason for exporting avg this time around is I want only 1 sample per event.
Dear Lemmy,
I apologize for any confusion regarding the CSV data. It's not a bug but rather a method of calculating reduced data. The calculation may seem less intuitive in combination with fast on triggers slow otherwise store types. Therefore, I recommend either using full-speed data export or incorporating additional basic statistics.
Best regards
Eva