Login or Register to Ask a Question and Join Our Community


UNIX and Linux Applications

gnuplot limitations

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications gnuplot limitations
# 1  
Old 09-03-2009
gnuplot limitations
I'm running a simulation (programmed in C) which makes calls to gnuplot periodically to plot data I have stored.

First I open a pipe to gnuplot and set it to multiplot:

FILE * pipe = popen("gnuplot", "w");
fprintf(pipe, "set multiplot\n");
fflush(pipe);

(this pipe stays open until the end of the program when I open it)

Next I use fopen to open a file called "plot". Write all the commands I want to have plotted (there's quite a few of them as many of them are just plotting 1 point with a specific color and point style). Once I've written all the commands to plot I close "plot"

Then I use the pipe again to load my file

fprintf(pipe, "load \"plot\"\n");

I'm running it like this so I can constantly plot on the same window and see my plots in real time as the program runs.

Functionally it works but a delay starts to build up and eventually becomes extremely significant.

My load commands are generally on the order of 2000 lines.

So to actually get to a question, does gnuplot have strange behavior for very large loads or can plot take a long time with that. My guess is that my program is piping loads to gnuplot before previous commands are finished completing. Has anyone had experience with this kind of situation, or can anyone suggest a better method for real time plotting in C.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Solaris limitations

Hi, I recently started working with Solaris, and what I noticed is that a lot of commands I used to regularly use don't work, like sed -i and grep -r. I have found work arounds for these problems though but it's a pain in the ass. I'm just wondering why they decided not to include these handy... (4 Replies)
Discussion started by: Subbeh
4 Replies

2. Red Hat

Eth0 Limitations

Hi, I have noticed some performance issues on my RHEL5 server but the memory and CPU utilization on the box is fine. I have a 1G full duplexed eth0 card and I am suspicious that this may be causing the problem. My eth0 settings are as follows: Settings for eth0: Supported ports: ... (12 Replies)
Discussion started by: Duffs22
12 Replies

3. Shell Programming and Scripting

perl limitations vs. bash?

I've building a bunch of bash scripts, and am thinking about "converting" to perl, and have a couple questions first: 1. Is there anything bash will do that perl won't? 2. How steep is the learning curve? 3. If perl's more powerful, why? 4. I've built a small app in python, which seemed nice,... (18 Replies)
Discussion started by: unclecameron
18 Replies

4. Red Hat

Limitations on the partition of linux

Hi, I need a documentation about limitations on the linux partition. On how many primary and extended I could create. And also on different type of storage, how many big capacity I can create. Thanks. (3 Replies)
Discussion started by: itik
3 Replies

5. Solaris

Solaris 9 or 10 LUN Limitations

Is there a limit to the number of LUNS that can be concatenated using Solaris Volume manager with Soft partitions? I have worked with some AIX admins in the past and there was such a limitation therefore limiting the size the filesystem could grow to. Is there such a limitation in Solaris 9... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies

6. UNIX for Dummies Questions & Answers

Password limitations.

I would like to set my minimum password length to on Linux and AIX. However, doing this normally would only make it so newly added users will be affected by this. I would like for when I make this change, it either truncates everyone elses password, or prompts them to change it to 8+ characters.... (2 Replies)
Discussion started by: syndex
2 Replies

7. UNIX for Dummies Questions & Answers

csplit limitations

I am trying to use the csplit file on a file that contains records that have more than 2048 characters on a line. The resultant split file seems to ignore the rest of the line and I lose the data. Is there any way that csplit can handle record lengths greater than 2048? Thanks (0 Replies)
Discussion started by: ravagga
0 Replies

8. UNIX for Dummies Questions & Answers

Unix Sort - Limitations

Hi All, I want to sort a flat file which will contain millions of records based on a key/field. For this I want to use unix sort command and before that I want to make sure that unix sort command has any file size limitations. And also please let me know whether I have to change any... (2 Replies)
Discussion started by: chprvkmr
2 Replies

9. IP Networking

need help with 32 bit IP address limitations

32 bit IP addresses with class based allocation schemes have limitations. does anyone know where i could get some info on this or if you have time to spare and really want to help me, a couple of sentences. thanks milos (1 Reply)
Discussion started by: 30177005
1 Replies

10. UNIX for Dummies Questions & Answers

mkdir limitations

What characters can't be used with a mkdir? Any limits on length of name? Thank you, Randy M. Zeitman http://www.StoneRoseDesign.com (12 Replies)
Discussion started by: flignar
12 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

gpsprof

GPSPROF(1)							GPSD Documentation							GPSPROF(1)

NAME

       gpsprof - profile a GPS and gpsd, plotting latency information

SYNOPSIS

       gpsprof [-f plot_type] [-m threshold] [-n packetcount] [-t title] [-T terminal] [-d dumpfile] [-l logfile] [-r] [-D debuglevel] [-h]
	       [[server[:port[:device]]]]

DESCRIPTION

       gpsprof performs accuracy and latency profiling on a GPS. It emits to standard output a GNUPLOT program that draws an illustrative graph.
       It can also be told to emit the raw profile data. The information it provides can be useful for establishing an upper bound on latency, and
       thus on position accuracy of a GPS in motion.

       gpsprof uses instrumentation built into gpsd.

       To display the graph, use gnuplot(1). Thus, for example, to display the default spatial scatter plot, do this:

	   gpsprof | gnuplot -persist

       To generate an image file:

	   gpsprof -T png | gnuplot >image.png

OPTIONS

       The -f option sets the plot type. The X axis is samples (sentences with timestamps). The Y axis is normally latency in seconds. Currently
       the following plot types are defined:

       space
	   Generate a scattergram of fixes and plot a probable-error circle. This data is only meaningful if the GPS is held stationary while
	   gpsprof is running. This is the default.

       uninstrumented
	   Plot total latency without instrumentation. Useful mainly as a check that the instrumentation is not producing significant distortion.
	   It only plots times for reports that contain fixes; staircase-like artifacts in the plot are created when elapsed time from reports
	   without fixes is lumped in.

       instrumented
	   Plot instrumented profile. Plots various components of the total latency between the GPS's fix time fix and when the client receives
	   the fix.

       For purposes of the description, below, start-of-reporting-cycle (SORC) is when a device's reporting cycle begins. This time is detected by
       watching to see when data availability follows a long enough amount of quiet time that we can be sure we've seen the gap at the end of the
       sensor's previous report-transmission cycle. Detecting this gap requires a device running at 9600bps or faster.

       Similarly, EORC is end-of-reporting-cycle; when the daemon has seen the last sentence it needs in the reporting cycle and ready to ship a
       fix to the client.

       The components of the instrumented plot are as follows:

       Fix latency
	   Delta between GPS time and SORC.

       RS232 time
	   RS232 transmission time for data shipped during the cycle (computed from character volume and baud rate).

       Analysis time
	   EORC, minus SORC, minus RS232 time. The amount of real time the daemon spent on computation rather than I/O.

       Reception time
	   Shipping time from the daemon to when it was received by gpsprof.

       Because of RS232 buffering effects, the profiler sometimes generates reports of ridiculously high latencies right at the beginning of a
       session. The -m option lets you set a latency threshold, in multiples of the cycle time, above which reports are discarded.

       The -n option sets the number of packets to sample. The default is 100.

       The -t option sets a text string to be included in the plot title.

       The -T option generates a terminal type setting into the gnuplot code. Typical usage is "-T png" telling gnuplot to write a PNG file.
       Without this option gnuplot will call its X11 display code.

       The -d option dumps the plot data, without attached gnuplot code, to a specified file for post-analysis.

       The -l option dumps the raw JSON reports collected from the device to a specified file.

       The -r option replots from a JSON logfile (such as -l produces) on standard input. Both -n and -l options are ignored when this one is
       selected.

       The -h option makes gpsprof print a usage message and exit.

       The -D sets debug level.

       Sending SIGUSR1 to a running instance causes it to write a completion message to standard error and resume processing. The first number in
       the startup message is the process ID to signal.

SEE ALSO

       gpsd(8), gps(1), libgps(3), libgpsd(3), gpsfake(1), gpsctl(1), gpscat(1), gnuplot(1).

AUTHOR

       Eric S. Raymond esr@thyrsus.com.

The GPSD Project						    10 Feb 2005 							GPSPROF(1)