How to modify/clip roast data set within artisan

[prmango43]

I have "dirty" roast data sets I'd like to "edit/clip" within artisan, if possible. The data sets have either too much up front data because I started recording before the roaster was ready or have a tail of unwanted data because I failed to stop recording after the drop.
When I try to edit the exported xlsx file I get an exception error. Still working on using xlsx and cvs test files. Perhaps someone has already done this.

TIA

[poundy]

Those areas are OK to leave. There's no need to "clip" them. Artisan will graph for you exactly what you need, if that's the concern - what exactly is your concern ?

[prmango43]

I was trying to clean up the few roast I have done before adding them to roastetta. Unsure what will happen with the garbage data being included. Guess I can try one and then delete if those extra data/events appear on input.

[prmango43]

Seems roastetta has no problems with the extra data. Still, I would feel better if I was able to clean up those data points without loosing the event table entries. I'm just starting, but hope to learn enough to be able to do a good clean roast and later follow with a auto roast. I envision yearly maybe 20-25 roast for personal use and another 20 or so for my son -- so about 4/month.

Anyone running a server is always looking to reduce the data foot print. My clean file is less than 1/3 the size of the "dirty" file. Every bit/bite helps.

[prmango43]

One can remove unwanted data from roast file .alog. Export to csv, open file with Open Office with no delimiters and remove front end data leaving about 1 minute before charge. Save file keeping same format and exit OO, However, on import of truncated csv file the event table will not contain any events so I understand this becomes a problem for those who do back-to-back batches using background profile. And not what I had envisioned. I can provide input/output files if anyone is interested.

Why is this method causing the loss of event data. The roast data has been truncated and shows curves but no events.

[mrpenner]

I believe the CSV export only includes the temperature data. It wouldn't work very good to store everything from an .alog file into CSV.

You probably want to either work directly with the .alog file, or my preference would be the JSON export. That will be more complicated than opening a CSV in a spreadsheet program, but they do include all the data.

[MAKOMO]

What XLSX file format you are talking about? Only the specifically XLSX files exported from Stronghold machines can be imported by Artisan. Editing the Artisan .alog or the corresponding Artisan .json is not recommended and most likely breaks them as those are not simple file formats. The event data for example is linking to indices of the curve data. As mentioned, clipping is not needed. Just set the correct CHARGE and DROP evens and instruct Artisan to only display the data between CHARGE and DROP (menu Config >> Curves, 2nd tab "Filter" under "Display Filter").

[prmango43]

I had to go back to old notes to find the 1st instance for this discussion re "dirty" files. I may have hinted to this in another discussion re simulator. Anyway, this one particular roast has over 530 lines of front end "garbage" as a result of my recording while in auto burn. That amount of useless data becomes a time burden when using simulator, even at 4X.

So after several tests, initial results are that on csv import, the exported Artisan csv file does not contain (populate??) the event data table -- it does have a top line of the event markers, but nothing else for events. I then imported the csv file to save it as an .alog and then loaded it, but the event table did not get populated as I had hoped -- no markers/flags on the curve. I was attempting to clean up the files by using the Artisan export to csv option, but an empty event table is not what I expected. What was the general intent of the Artisan export feature and specifically the csv case??

Understood about the display filter in Artisan and this also seems to be the case when uploading roast into roastetta. I have not asked roastetta about the "dirty" data.

[jpdargent]

Hi! You can edit/delete every points using EVENTS in ROAST PROPERTIES (Roast >> Properties >> Events)

Is that what you were looking for?

[jpdargent]

jpdargent,

About ur suggestion (You can select several lines at once by holding CAPS Key + Click and delete all lines in seconds). Is this within Artisan or working with a csv file? Pls clarify. TIA

Within artisan ROAST PROPERTIES

[prmango43]

I apologize to everyone, but it seems some have taken my simple requests out of context. I'm not in the roasting business, unlikely to ever go into the roasting business, or have surplus money to hire consultants. I thought this was a forum where one could start a conversation regarding the use of Artisan and a civil exchange would ensue. I did not expect any of my "discussions" to be taken personally. Sadly, it appears I was mistaken on both points.

I love coffee. For me it's a cultural and a family thing -- planting, caring, picking, drying, all of it. I don't have, but some in my extended family still have holdings to our old coffee "fincas" going back many generations -- happy for them. Again, my sincere apologies.

[CarefreeBuzzBuzz]

Understood and appreciate your response. Moving forward the core team needs to focus on some critical development points and cannot solve every one off request. Hopefully some others will step in and help you out.

[poundy]

I thought this was a forum where one could start a conversation regarding the use of Artisan and a civil exchange would ensue. I did not expect any of my "discussions" to be taken personally.

This IS the place where ideas can be floated, and where operational questions can be discussed. It's however not a "fix everything" or "change this just for me" approach. Certainly, good ideas that get discussed and promoted here do get taken further, and bugs identified addressed.

Nobody has taken these things personally. We've just had to convince you that your idea is unique enough for it to not be relevant for the rest of us and that it would never make the list of things to spend development effort on.

[roasterdave]

I thought this was a forum where one could start a conversation regarding the use of Artisan and a civil exchange would ensue.

This is that kind of forum. Unfortunately the intent behind the words can often be misinterpreted. My thanks to you for your comments and ideas. My thanks also to the many who offer suggestions here, even where they have not directly solved your problem. This kind of involvement from the community only makes Artisan stronger.

[prmango43]

jpdargent,

If you have some spare time -- no hurry -- pls PM vnam43@yahoo.com. I tried ur instructions within the Artisan profile curve and in the data set, but was unsuccessful.

EDIT: No need now, thanks. I was trying to use your suggestion in the data set table which is what I wanted clipped, but found out it works only in the event marker table -- the one I wanted to keep intact. BTY, can mark lines for deletion with left button without need of caps button.

Merci