Jump to content

carl.abz.uk

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by carl.abz.uk

  1. OK I got there in the end, turning off gridding and the export works fine. Many thanks. Now the follow up questions.... You say you export "everything on the screen" - by experimentation I think the fact a trace is visible or greyed out (i.e.. not selected on the details pane) makes no difference to the export. The only way I can find to export just the bar graph (12 points per year = quick!) without including the other data (~500k points/year = SLOW) is to delete the other traces? I duplicated the page for this - see below - then deleted the original signal, capsules and conditions to leave just the bar graph, but this seems a long winded way of doing it. Is there no way in Export on my first page to select what I want to export? Also it's a minor point but when moving the cursor the width of the bar chart seems to change the time the value is reported over - in the example there is only one value written on 31-Aug for the result at end of August - yet the cursor returns the resuls as "far to the right" as 4th September but not form 5th September as by this point we are not on the width of the bar chart.
  2. So back to the topic at hand - unlike Sam / Lyndsay I'm trying to do the same thing but would like hours running per month over a year. Often the system can run for many days with no problem so with value search I use a max capsule duration of 40 days - the end result is SLOW! So i invert the logic and look for the number of hours the system is NOT flowing. I create monthly capsules and do the same trick. And I do indeed see a new (brown) signal of non running hour per month. End result looks good, I set the analysis range to 1 year - the trace follows up - but when I export to Excel SeeQ just sits there with the export wheel spinning, I gave up after 10 minutes All I want is a table with somthign like Jan. X hours Feb. Y hours Mar. X hours etc etc. But I suspect the problem is Seeq is trying to export everything? My signal is generally captured 1/min so over a year I have 1440 * 365 = 525,600 points so it's quitea lot of data? I get wanrings over the interpolation insterval, but then i can't change this - and indeed asI an showing step data I'm not sure why there is interpolation anyway? During the import of my original signal is there a way to resample the data to say 5 min resolution rather than 1 to keep the volume manageable (if indded this is the problem) Is there a way to only export one trace (i.e. the 12 values I want)?
  3. Trying to follow this but when I click on the screenshots It asks me to sign into Altassian and I have no account? BTW What's the link between Altassian and SeeQ - I see a few things like the SeeQ KB have altasian URL's?
  4. Ta, sorry I have absolutely no idea why I missed that given i could see both the "rocket" and the "i" next to it...
  5. Hello - I've searched but not found - this seems, to me at least, an abvious question but I can find no way to do it. In the example below (existing_traces.png) I have three traces - If I want to edit e.g. the histogram (number of buckets etc.) I can't see a way of going back to the screen i used to create it in the first place (original_histogram_window.png). If I click on the (i) in the details tab I then see all the underlying code under item properties (properties_pane.png) but what I want to get to is the original screeen of "Overview >>Historgram" where I can change the number of boxes etc. The only way I can see to do it is to delete the historgam and start again - this seems a long way round. Intuitively I would expect to be be able to "right click" or "long click" on the historgram and get a context sensitive menu to get to the overview>>histogram page Am I missing somthing obvious?
  6. Hi, Apprciate SeeQ is focused on real time data souces but sometimes I want to import CSV data to show alongside PI data - currently SeeQ is limited in the timestamps it can import https://seeq12.atlassian.net/wiki/spaces/KB/pages/112823079/Import+CSV+Files There are many Excel formats but all have the date in the "month first" e.g. M/d/yyyy format. I can of course play around with the CSV before I import it to convert to another format, however the vast majority of data in Europe is in the dd/mm/yyyy format. (and if I leave my data it in the "month first" format it's going to cause confusion for others usign it. How about a more flexible import routine e.g. I can define a string defining the date format before the import somthign like %d/%m/%Y %HH:%MM or %dd-%mm-%yy (if I have a different day month year delimiter etc.)
  7. THANKS! - got to like the response speed, post, go and get a coffee and the answer is in my inbox when I return... I think my problem is the format of the timestring. It's formatted for UK Excel: DATE_TIME,FILENAME,VAR_1,VAR_2 08/10/2018 15:34,ExampleFilename,10,20 But I see in the article all the Excel formats are in the US Month/Day format. M/d/yyyy HH:mm The CSV comes from a "pre processing" Python script so I can change the CSV format to say ISO 8601 but before I do just want to check if it will indeed only read month/day/year in excel format. Got to run now - to be continued.....
  8. Howdy SeeQers. I am going through the SeeQ Training - on the left I see "Resources" and I can download "SeeQ Workbench user Guide" - this is good I am much better at devouring the 112 page PDF searching for things I want to try with my own data than wroking through the "rigid" examples in the training. However this refers to a number of other articles e.g. "related article: Import CSV Files." on pp64. But the hyperlink in the PDF does not work. QUESTION : Where can I find this (and other) articles refered to in the training guide.
×
×
  • Create New...