9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Let me start by saying I'm new to gnuplot and not very good at unix at all..
Anyway, I'm each minute measuring temperature and humidity and saves the last 60 readings along with time in a textfile, values_minute.
The contents of the file is formatted like this: time temperature humidity
... (8 Replies)
Discussion started by: hakro807
8 Replies
2. Shell Programming and Scripting
Hi,
Is there a way to find out the line number from where the data starts?
like if the data contains column header, irrespective of the text in the column header we should get the line number from which contains the column header.
I am sorry if I haven't explained the problem clearly.
... (8 Replies)
Discussion started by: kedar_laveti
8 Replies
3. Programming
For example, I have a file called data.txt. And the content is:
Iker_Casillas 181
Raphael_Varane 182
Sergio_Ramos 182May I know how to write a script for gnuplot, so I can have a bar graph as the column 1 will be the x and column 2 will be the y? And I hope that the x value can be seen clearly.... (0 Replies)
Discussion started by: Tzeronone
0 Replies
4. UNIX and Linux Applications
Hi,
i would like to change color depending from the valuerange.
a gnuplot-script will generate a multiplot and in one graph,
the ranges should have different colors, e.g.
100 ... 133 --> red
200 ... 233 --> blue
300 ... 333 --> orange
400 ... 433 --> green
#Partikeldata - Partikel... (1 Reply)
Discussion started by: IMPe
1 Replies
5. Programming
I have a piece of code here that should create a line graph consisting of two lines. It will not render the lines and neither the dates on the x-axis. The y-axis is apparently already scaled for the y-values, so the data interpretation went correctly for at least some of the data.
Does anybody see... (0 Replies)
Discussion started by: figaro
0 Replies
6. Solaris
Hi, I need to generate graph from the text file in Unix server.
The file contains the following data,
Fri Feb 03 07:01:00 PST 2012|3325
Fri Feb 03 07:02:00 PST 2012|3349
Fri Feb 03 07:03:00 PST 2012|3290
Fri Feb 03 07:04:00 PST 2012|3496
Fri Feb 03 07:05:00 PST 2012|3362
Fri Feb 03 07:06:00... (2 Replies)
Discussion started by: gkn
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I want to remove the first line from a flat file using unix command as simple as possible. Can anybody give me a hand ?
Thanks in advance.
xli (21 Replies)
Discussion started by: xli
21 Replies
8. Shell Programming and Scripting
Hi,
below is the software list of lines I have,
MozillaSrc 1.7.8.00.00 Mozilla 1.78 Source Distribution
NFS B.11.11 ONC/NFS; Network-File System,Information Services,Utilities
NParProvider B.11.11.01.04.01.01 nPartition Provider
NPartition ... (7 Replies)
Discussion started by: acomd2
7 Replies
9. Shell Programming and Scripting
Hi, I have a flat text file which contains blank line between each text line. Is there any command to get rid of it?
Thanks for your help (11 Replies)
Discussion started by: xfang
11 Replies
PLOTCHANGELOG(1) General Commands Manual PLOTCHANGELOG(1)
NAME
plotchangelog - graph debian changelogs
SYNOPSIS
plotchangelog [options] changelog ...
DESCRIPTION
plotchangelog is a tool to aid in visualizing a Debian changelog. The changelogs are graphed with gnuplot(1) , with the X axis of the graph
denoting time of release and the Y axis denoting the debian version number of the package. Each individual release of the package is repre-
sented by a point, and the points are color coded to indicate who released that version of the package. The upstream version number of the
package can also be labeled on the graph.
Alternatively, the Y axis can be configured to display the size of the changelog entry for each new version. Or it can be configured to
display approximately how many bugs were fixed for each new version.
Note that if the package is a debian-specific package, the entire package version will be used for the Y axis. This does not always work
perfectly.
READING THE GRAPH
The general outline of a package's graph is typically a series of peaks, starting at 1, going up to n, and then returning abruptly to 1.
The higher the peaks, the more releases the maintainer made between new upstream versions of the package. If a package is debian-only, it's
graph will just grow upwards without ever falling (although a bug in this program may cause it to fall sometimes, if the version number
goes from say, 0.9 to say, 0.10 - this is interpreted wrong..)
If the graph dips below 1, someone made a NMU of the package and upgraded it to a new upstream version, thus setting the debian version to
0. NMU's in general appear as fractional points like 1.1, 2.1, etc. A NMU can also be easily detected by looking at the points that repre-
sent which maintainer uploaded the package -- a solitary point of a different type than the points before and after it is typically a NMU.
It's also easy to tell by looking at the points when a package changes maintainers.
OPTIONS
-l, --linecount
Instead of using the debian version number as the Y axis, use the number of lines in the changelog entry for each version. Cannot
be used together with --bugcount.
-b, --bugcount
Instead of using the debian version number as the Y axis, use the number of bugs that were closed by each changelog entry. Note that
this number is obtained by searching for "#dddd" in the changelog, and so it may be inaccurate. Cannot be used together with
--linecount.
-c, --cumulative
When used together with either --bugcount or --linecount, graphs the cumulative count rather than the count in each individual
changelog entry.
-v, --no-version
Do not show upstream version labels. Useful if the graph gets too crowded.
-m, --no-maint
Do not differentiate between different maintainers of the package.
-s file, --save=file
Save the graph to file in postscript format instead of immediately displaying it.
-u, --urgency
Use larger points when displaying higher-urgency package uploads.
--verbose
Output the gnuplot script that is fed into gnuplot (for debugging purposes).
-gcommands, --gnuplot=commands
This allows you to insert gnuplot(1) commands into the gnuplot script that is used to generate the graph. The commands are placed
after all initialization but before the final plot command. This can be used to override the default look provided by this program
in arbitrary ways. You can also use things like "set terminal png color" to change the output file type, which is useful in conjunc-
tion with the -s option.
--help Show a usage summary.
--version
Display version, author and copyright information.
--noconf, --no-conf
Do not read any configuration files (see below).
changelog ...
The changelog files to graph. If multiple files are specified they will all be display on the same graph. The files may be com-
pressed with gzip. Any text in them that is not in Debian changelog format will be ignored.
CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables.
The --no-conf option can be used to prevent reading these files. Environment variable settings are ignored when these configuration files
are read. The currently recognised variables are:
PLOTCHANGELOG_OPTIONS
This is a space-separated list of options to always use, for example -l -b. Do not include -g or --gnuplot among this list as it
may be ignored; see the next variable instead.
PLOTCHANGELOG_GNUPLOT
These are gnuplot commands which will be prepended to any such commands given on the command line.
SEE ALSO
devscripts.conf(5).
AUTHOR
Joey Hess <joey@kitenet.net>
DEBIAN
Debian Utilities PLOTCHANGELOG(1)