Methods: To tackle this problem, we developed Metabolite AutoPlotter, a tool to process and visualise quantified metabolite data. Other than with bulk data visualisations, such as heat maps, the aim of the tool is to generate single plots for each metabolite. For this purpose, it reads as input pre-processed metabolite-intensity tables and accepts different experimental designs, with respect to the number of metabolites, conditions and replicates. The code was written in the R-scripting language and wrapped into a shiny application that can be run online in a web browser on
Results: We demonstrate the main features and the ease of use with two different metabolite datasets, for quantitative experiments and for stable isotope tracing experiments. We show how the plots generated by the tool can be interactively modified with respect to plot type, colours, text labels and the shown statistics. We also demonstrate the application towards 13C-tracing experiments and the seamless integration of natural abundance correction, which facilitates the better interpretation of stable isotope tracing experiments. The output of the tool is a zip-file containing one single plot for each metabolite as well as restructured tables that can be used for further analysis.
This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the cookie policy. By closing this banner, clicking a link or continuing to browse otherwise, you agree to the use of cookies.
Whether you want to get your topographical map with contours and 3D terrain model, or you are looking for sections, or cadastral maps, AutoPlotter can do it all for you in a way which you will always appreciate, the easy way.
No wonder then that after the introduction of AutoPlotter seven years back in India, it has gained popularity with more than 5000 installations in the field of route survey, topographical survey, revenue survey, mining, city survey, grade planning 3D modeling, Road Construction and project planning Salient Features:- Supports file formats generated from different type of total stations (Pentax, Trimble, Sokkia, Topcon, Nikon, Leica).
Auto creation of plan with features, colors, hatch and symbols for cadastral, route, pipeline, city and revenue surveys with interactive traverse adjustment Generation of volume between surfaces which useful for stock taking with user defined boundary.
@TonyParakka:
thanks buddy, it is always good to know the software can help people with their ideas Using the Autoplotter is fantastic. Very few people seemed to have used that yet.
The way I use the Autoplotter in my example is to move the data set of the graph around to only display the latest values. I never thought about a way before to move the data like a LIFO system around. I can think of several ideas now, some being more complex or less performant then others. The "best" one (although not the prettiest one) would be to use the CustomDevPoint to check if more then 240 data rows are already receiverd, and in case yes, put the new data to row #242 and delete row #2. That way you would have just the correct amount of data. Might be that the graph's data set will not cope well with rows being deleted, therefore I guess it would be best to rewrite the data set anew every iteration as well (to use e.g. B2 to B242).
I hope this will work for you as an entry point to coding things for the time being.
@jdechow:
Hi Hannes, and thanks for the feedback, much appreciated
You are right with what you figured out: too much data is not being supported by the current version of PLX DAQ. Every ms will flood the inbound API call. Are you really sure you need that much data? I mean .... can you even handle that on the human side ?
Maybe you could collect the data in Arduino every ms, make a meridian / middle value of it every 50ms and send that to Excel?
To reduce overhead you could also collect e.g. 10 data in an array and send array to Excel every 10ms (thus the amount of communication gets reduced). But you have to parse the array on Excel side and split the values one by one yourself (although the PC is generally capable of processing that little bit of operation).
Last idea would be to get back to the original Serial.print without using the (String)-converter. This will mainly save ressources on the Arduino side but could maybe improve stability as well since communication might be smoother (because Arduino is quicker in responding / acknowledging to send data).
I tried [1] create new row at 2 with shift down, and [2] add new data to row2
New data addition worked nicely and the data shows on the graph, but graph stretches vertically with every added rows! Yikes!
I tried placing the graph at top, and adding new data from some row further down e.g. 40).. in this case the graph stayed blank I tried placing the graph on a separate worksheet; here too, the graph stayed blank
I also tried the shift up method -on a small scale.
In "DATA" section, I check if row > 40; if not, then add new data at row=row+1; and if yes, then delete row2 with shift up, and add new data at row 42.
So far, the graph stays blank even as data comes in..
You need to check how Excel handles the deletion of the rows with regards to the data set of the diagram. In case your diagram is set to e.g. A2:A42, then deleting rows may result in moving the grid to A1:A41.
In my PowerDemo (included in the ZIP file) I used to set the data grid anew with every data read. The command is a bit cryptic and reads something like this:ChartObjects("MyMainDiagram").Chart.FullSeriesCollection(1).XValues = "='Simple Data'!$C$" & IIf(newRow - 1
I've done this. However, it does not do what I've wanted originally, partly. I want to make the Arduino stops sending data to PLX-DAQ at 11:55:00 pm and then resume logging at 12:00:00 mn automatically. I've read from your reply #26 at page 2 of this thread, a somehow of what I want to do but not with Sensorvalue but rather based at the real-time clock of the pc/laptop.
I've searched that the delay() function has limited uses and that millis() function is the better choice when working with intervals. But I can't seem to make this work (the one above). And the time frame of 11:55:01 pm to 11:59:59 pm, I will save all the data gathered in that day into an excel file and then use another excel to resume logging at 12:00:00 mn
You can use the real time clock as a module to connect to your Arduino, yes. On the other hand you could use one cell within Excel as a "Do sending: yes/no" information that is passed back and forth from Excel to Arduino. Nevertheless you need you Arduino to run 24/7 as well as your PC and they need to be connection with each other throughout the time.
What I would is to use a cell e.g. A10 and write a "Yes" or "No" in the cell by VBA based on the PC time. You can use the loops running in PLX DAQ for that. In Arduino I would use a millis counter to send a query for cell A10 like every one minute. Based on what is returned to the Arduino it should or shouldn't send data to Excel.
"D" is not a cell but a whole column. Getting all data from one column is tricky and would require some change in code. However getting only the data from cell D7 (or as above A10) is within the standards of PLX DAQ. The Beginners Guide does have some example data for that.
Delay will typically pause the whole code running on Arduino for the time that should be waited. Total disaster of course as you want to continue logging . Using millis is better as you can just save the current value of millis, add (10006060*25) to it (one full day) and place in variable x and in your loop function check if the current millis is larger then x (thus the day has passed). However this will result in pretty large numbers. I might think that my way (Cell A10 with Yes/No value) is a bit more stable.
@tgod2100:
yeah I would totally suggest this to be an issue with the old Excel version. That version of Excel is older then many users on this board
Do you have any option to try to switch to a more up to date version? Maybe 2013?
@JackSilva:
Brazilian, nice I should start a world map and put pins in and try to get as many continents as possible
My first guess is that Excel 365 is a problem. However I haven't used it myself... it is a native running client or a cloud service? Does PLX DAQ work with it in general (fetching / receiving data) but crashes only when using graphics?
Just to be sure: by graphics you mean graphs and plots and diagrams? Not pictures? But your goal is to receive data and visualize it? Does your graph auto-update while receiving data or do you receive data, stop the connection, then create a graph of the data and by that Excel crashes?
that is an interesting idea, yeah. Having a look at your linked thread I see that the possibilities of Libxlsxwriter go way beyond "just" creating a valid xls file (Autofilters, merged cells, charts, they go the full way). That is a full blown solution for creation on the device itself.
PLX-DAQ's intention was to simply collect data with as little overhead as possible. "DAQ" stands for "Data Acquisition" by the way The intention was to visualize real time data or collect and store data periodically without adjusting too much on the Arduino code itself.