/usr/share/gnuplot/gnuplot-x11.gih is in gnuplot-x11 5.2.2+dfsg1-2ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 5997 5998 5999 6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 6208 6209 6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 6288 6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 6389 6390 6391 6392 6393 6394 6395 6396 6397 6398 6399 6400 6401 6402 6403 6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451 6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468 6469 6470 6471 6472 6473 6474 6475 6476 6477 6478 6479 6480 6481 6482 6483 6484 6485 6486 6487 6488 6489 6490 6491 6492 6493 6494 6495 6496 6497 6498 6499 6500 6501 6502 6503 6504 6505 6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517 6518 6519 6520 6521 6522 6523 6524 6525 6526 6527 6528 6529 6530 6531 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542 6543 6544 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557 6558 6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570 6571 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 6585 6586 6587 6588 6589 6590 6591 6592 6593 6594 6595 6596 6597 6598 6599 6600 6601 6602 6603 6604 6605 6606 6607 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625 6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348 8349 8350 8351 8352 8353 8354 8355 8356 8357 8358 8359 8360 8361 8362 8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 8378 8379 8380 8381 8382 8383 8384 8385 8386 8387 8388 8389 8390 8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406 8407 8408 8409 8410 8411 8412 8413 8414 8415 8416 8417 8418 8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432 8433 8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 8473 8474 8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516 8517 8518 8519 8520 8521 8522 8523 8524 8525 8526 8527 8528 8529 8530 8531 8532 8533 8534 8535 8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563 8564 8565 8566 8567 8568 8569 8570 8571 8572 8573 8574 8575 8576 8577 8578 8579 8580 8581 8582 8583 8584 8585 8586 8587 8588 8589 8590 8591 8592 8593 8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605 8606 8607 8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 8647 8648 8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684 8685 8686 8687 8688 8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705 8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 8780 8781 8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874 8875 8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914 8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987 8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000 9001 9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062 9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141 9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 9153 9154 9155 9156 9157 9158 9159 9160 9161 9162 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188 9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218 9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 9274 9275 9276 9277 9278 9279 9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294 9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 9326 9327 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 9345 9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356 9357 9358 9359 9360 9361 9362 9363 9364 9365 9366 9367 9368 9369 9370 9371 9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444 9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467 9468 9469 9470 9471 9472 9473 9474 9475 9476 9477 9478 9479 9480 9481 9482 9483 9484 9485 9486 9487 9488 9489 9490 9491 9492 9493 9494 9495 9496 9497 9498 9499 9500 9501 9502 9503 9504 9505 9506 9507 9508 9509 9510 9511 9512 9513 9514 9515 9516 9517 9518 9519 9520 9521 9522 9523 9524 9525 9526 9527 9528 9529 9530 9531 9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552 9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595 9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608 9609 9610 9611 9612 9613 9614 9615 9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626 9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666 9667 9668 9669 9670 9671 9672 9673 9674 9675 9676 9677 9678 9679 9680 9681 9682 9683 9684 9685 9686 9687 9688 9689 9690 9691 9692 9693 9694 9695 9696 9697 9698 9699 9700 9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738 9739 9740 9741 9742 9743 9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775 9776 9777 9778 9779 9780 9781 9782 9783 9784 9785 9786 9787 9788 9789 9790 9791 9792 9793 9794 9795 9796 9797 9798 9799 9800 9801 9802 9803 9804 9805 9806 9807 9808 9809 9810 9811 9812 9813 9814 9815 9816 9817 9818 9819 9820 9821 9822 9823 9824 9825 9826 9827 9828 9829 9830 9831 9832 9833 9834 9835 9836 9837 9838 9839 9840 9841 9842 9843 9844 9845 9846 9847 9848 9849 9850 9851 9852 9853 9854 9855 9856 9857 9858 9859 9860 9861 9862 9863 9864 9865 9866 9867 9868 9869 9870 9871 9872 9873 9874 9875 9876 9877 9878 9879 9880 9881 9882 9883 9884 9885 9886 9887 9888 9889 9890 9891 9892 9893 9894 9895 9896 9897 9898 9899 9900 9901 9902 9903 9904 9905 9906 9907 9908 9909 9910 9911 9912 9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9954 9955 9956 9957 9958 9959 9960 9961 9962 9963 9964 9965 9966 9967 9968 9969 9970 9971 9972 9973 9974 9975 9976 9977 9978 9979 9980 9981 9982 9983 9984 9985 9986 9987 9988 9989 9990 9991 9992 9993 9994 9995 9996 9997 9998 9999 10000 10001 10002 10003 10004 10005 10006 10007 10008 10009 10010 10011 10012 10013 10014 10015 10016 10017 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 10066 10067 10068 10069 10070 10071 10072 10073 10074 10075 10076 10077 10078 10079 10080 10081 10082 10083 10084 10085 10086 10087 10088 10089 10090 10091 10092 10093 10094 10095 10096 10097 10098 10099 10100 10101 10102 10103 10104 10105 10106 10107 10108 10109 10110 10111 10112 10113 10114 10115 10116 10117 10118 10119 10120 10121 10122 10123 10124 10125 10126 10127 10128 10129 10130 10131 10132 10133 10134 10135 10136 10137 10138 10139 10140 10141 10142 10143 10144 10145 10146 10147 10148 10149 10150 10151 10152 10153 10154 10155 10156 10157 10158 10159 10160 10161 10162 10163 10164 10165 10166 10167 10168 10169 10170 10171 10172 10173 10174 10175 10176 10177 10178 10179 10180 10181 10182 10183 10184 10185 10186 10187 10188 10189 10190 10191 10192 10193 10194 10195 10196 10197 10198 10199 10200 10201 10202 10203 10204 10205 10206 10207 10208 10209 10210 10211 10212 10213 10214 10215 10216 10217 10218 10219 10220 10221 10222 10223 10224 10225 10226 10227 10228 10229 10230 10231 10232 10233 10234 10235 10236 10237 10238 10239 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10252 10253 10254 10255 10256 10257 10258 10259 10260 10261 10262 10263 10264 10265 10266 10267 10268 10269 10270 10271 10272 10273 10274 10275 10276 10277 10278 10279 10280 10281 10282 10283 10284 10285 10286 10287 10288 10289 10290 10291 10292 10293 10294 10295 10296 10297 10298 10299 10300 10301 10302 10303 10304 10305 10306 10307 10308 10309 10310 10311 10312 10313 10314 10315 10316 10317 10318 10319 10320 10321 10322 10323 10324 10325 10326 10327 10328 10329 10330 10331 10332 10333 10334 10335 10336 10337 10338 10339 10340 10341 10342 10343 10344 10345 10346 10347 10348 10349 10350 10351 10352 10353 10354 10355 10356 10357 10358 10359 10360 10361 10362 10363 10364 10365 10366 10367 10368 10369 10370 10371 10372 10373 10374 10375 10376 10377 10378 10379 10380 10381 10382 10383 10384 10385 10386 10387 10388 10389 10390 10391 10392 10393 10394 10395 10396 10397 10398 10399 10400 10401 10402 10403 10404 10405 10406 10407 10408 10409 10410 10411 10412 10413 10414 10415 10416 10417 10418 10419 10420 10421 10422 10423 10424 10425 10426 10427 10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 10445 10446 10447 10448 10449 10450 10451 10452 10453 10454 10455 10456 10457 10458 10459 10460 10461 10462 10463 10464 10465 10466 10467 10468 10469 10470 10471 10472 10473 10474 10475 10476 10477 10478 10479 10480 10481 10482 10483 10484 10485 10486 10487 10488 10489 10490 10491 10492 10493 10494 10495 10496 10497 10498 10499 10500 10501 10502 10503 10504 10505 10506 10507 10508 10509 10510 10511 10512 10513 10514 10515 10516 10517 10518 10519 10520 10521 10522 10523 10524 10525 10526 10527 10528 10529 10530 10531 10532 10533 10534 10535 10536 10537 10538 10539 10540 10541 10542 10543 10544 10545 10546 10547 10548 10549 10550 10551 10552 10553 10554 10555 10556 10557 10558 10559 10560 10561 10562 10563 10564 10565 10566 10567 10568 10569 10570 10571 10572 10573 10574 10575 10576 10577 10578 10579 10580 10581 10582 10583 10584 10585 10586 10587 10588 10589 10590 10591 10592 10593 10594 10595 10596 10597 10598 10599 10600 10601 10602 10603 10604 10605 10606 10607 10608 10609 10610 10611 10612 10613 10614 10615 10616 10617 10618 10619 10620 10621 10622 10623 10624 10625 10626 10627 10628 10629 10630 10631 10632 10633 10634 10635 10636 10637 10638 10639 10640 10641 10642 10643 10644 10645 10646 10647 10648 10649 10650 10651 10652 10653 10654 10655 10656 10657 10658 10659 10660 10661 10662 10663 10664 10665 10666 10667 10668 10669 10670 10671 10672 10673 10674 10675 10676 10677 10678 10679 10680 10681 10682 10683 10684 10685 10686 10687 10688 10689 10690 10691 10692 10693 10694 10695 10696 10697 10698 10699 10700 10701 10702 10703 10704 10705 10706 10707 10708 10709 10710 10711 10712 10713 10714 10715 10716 10717 10718 10719 10720 10721 10722 10723 10724 10725 10726 10727 10728 10729 10730 10731 10732 10733 10734 10735 10736 10737 10738 10739 10740 10741 10742 10743 10744 10745 10746 10747 10748 10749 10750 10751 10752 10753 10754 10755 10756 10757 10758 10759 10760 10761 10762 10763 10764 10765 10766 10767 10768 10769 10770 10771 10772 10773 10774 10775 10776 10777 10778 10779 10780 10781 10782 10783 10784 10785 10786 10787 10788 10789 10790 10791 10792 10793 10794 10795 10796 10797 10798 10799 10800 10801 10802 10803 10804 10805 10806 10807 10808 10809 10810 10811 10812 10813 10814 10815 10816 10817 10818 10819 10820 10821 10822 10823 10824 10825 10826 10827 10828 10829 10830 10831 10832 10833 10834 10835 10836 10837 10838 10839 10840 10841 10842 10843 10844 10845 10846 10847 10848 10849 10850 10851 10852 10853 10854 10855 10856 10857 10858 10859 10860 10861 10862 10863 10864 10865 10866 10867 10868 10869 10870 10871 10872 10873 10874 10875 10876 10877 10878 10879 10880 10881 10882 10883 10884 10885 10886 10887 10888 10889 10890 10891 10892 10893 10894 10895 10896 10897 10898 10899 10900 10901 10902 10903 10904 10905 10906 10907 10908 10909 10910 10911 10912 10913 10914 10915 10916 10917 10918 10919 10920 10921 10922 10923 10924 10925 10926 10927 10928 10929 10930 10931 10932 10933 10934 10935 10936 10937 10938 10939 10940 10941 10942 10943 10944 10945 10946 10947 10948 10949 10950 10951 10952 10953 10954 10955 10956 10957 10958 10959 10960 10961 10962 10963 10964 10965 10966 10967 10968 10969 10970 10971 10972 10973 10974 10975 10976 10977 10978 10979 10980 10981 10982 10983 10984 10985 10986 10987 10988 10989 10990 10991 10992 10993 10994 10995 10996 10997 10998 10999 11000 11001 11002 11003 11004 11005 11006 11007 11008 11009 11010 11011 11012 11013 11014 11015 11016 11017 11018 11019 11020 11021 11022 11023 11024 11025 11026 11027 11028 11029 11030 11031 11032 11033 11034 11035 11036 11037 11038 11039 11040 11041 11042 11043 11044 11045 11046 11047 11048 11049 11050 11051 11052 11053 11054 11055 11056 11057 11058 11059 11060 11061 11062 11063 11064 11065 11066 11067 11068 11069 11070 11071 11072 11073 11074 11075 11076 11077 11078 11079 11080 11081 11082 11083 11084 11085 11086 11087 11088 11089 11090 11091 11092 11093 11094 11095 11096 11097 11098 11099 11100 11101 11102 11103 11104 11105 11106 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11118 11119 11120 11121 11122 11123 11124 11125 11126 11127 11128 11129 11130 11131 11132 11133 11134 11135 11136 11137 11138 11139 11140 11141 11142 11143 11144 11145 11146 11147 11148 11149 11150 11151 11152 11153 11154 11155 11156 11157 11158 11159 11160 11161 11162 11163 11164 11165 11166 11167 11168 11169 11170 11171 11172 11173 11174 11175 11176 11177 11178 11179 11180 11181 11182 11183 11184 11185 11186 11187 11188 11189 11190 11191 11192 11193 11194 11195 11196 11197 11198 11199 11200 11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216 11217 11218 11219 11220 11221 11222 11223 11224 11225 11226 11227 11228 11229 11230 11231 11232 11233 11234 11235 11236 11237 11238 11239 11240 11241 11242 11243 11244 11245 11246 11247 11248 11249 11250 11251 11252 11253 11254 11255 11256 11257 11258 11259 11260 11261 11262 11263 11264 11265 11266 11267 11268 11269 11270 11271 11272 11273 11274 11275 11276 11277 11278 11279 11280 11281 11282 11283 11284 11285 11286 11287 11288 11289 11290 11291 11292 11293 11294 11295 11296 11297 11298 11299 11300 11301 11302 11303 11304 11305 11306 11307 11308 11309 11310 11311 11312 11313 11314 11315 11316 11317 11318 11319 11320 11321 11322 11323 11324 11325 11326 11327 11328 11329 11330 11331 11332 11333 11334 11335 11336 11337 11338 11339 11340 11341 11342 11343 11344 11345 11346 11347 11348 11349 11350 11351 11352 11353 11354 11355 11356 11357 11358 11359 11360 11361 11362 11363 11364 11365 11366 11367 11368 11369 11370 11371 11372 11373 11374 11375 11376 11377 11378 11379 11380 11381 11382 11383 11384 11385 11386 11387 11388 11389 11390 11391 11392 11393 11394 11395 11396 11397 11398 11399 11400 11401 11402 11403 11404 11405 11406 11407 11408 11409 11410 11411 11412 11413 11414 11415 11416 11417 11418 11419 11420 11421 11422 11423 11424 11425 11426 11427 11428 11429 11430 11431 11432 11433 11434 11435 11436 11437 11438 11439 11440 11441 11442 11443 11444 11445 11446 11447 11448 11449 11450 11451 11452 11453 11454 11455 11456 11457 11458 11459 11460 11461 11462 11463 11464 11465 11466 11467 11468 11469 11470 11471 11472 11473 11474 11475 11476 11477 11478 11479 11480 11481 11482 11483 11484 11485 11486 11487 11488 11489 11490 11491 11492 11493 11494 11495 11496 11497 11498 11499 11500 11501 11502 11503 11504 11505 11506 11507 11508 11509 11510 11511 11512 11513 11514 11515 11516 11517 11518 11519 11520 11521 11522 11523 11524 11525 11526 11527 11528 11529 11530 11531 11532 11533 11534 11535 11536 11537 11538 11539 11540 11541 11542 11543 11544 11545 11546 11547 11548 11549 11550 11551 11552 11553 11554 11555 11556 11557 11558 11559 11560 11561 11562 11563 11564 11565 11566 11567 11568 11569 11570 11571 11572 11573 11574 11575 11576 11577 11578 11579 11580 11581 11582 11583 11584 11585 11586 11587 11588 11589 11590 11591 11592 11593 11594 11595 11596 11597 11598 11599 11600 11601 11602 11603 11604 11605 11606 11607 11608 11609 11610 11611 11612 11613 11614 11615 11616 11617 11618 11619 11620 11621 11622 11623 11624 11625 11626 11627 11628 11629 11630 11631 11632 11633 11634 11635 11636 11637 11638 11639 11640 11641 11642 11643 11644 11645 11646 11647 11648 11649 11650 11651 11652 11653 11654 11655 11656 11657 11658 11659 11660 11661 11662 11663 11664 11665 11666 11667 11668 11669 11670 11671 11672 11673 11674 11675 11676 11677 11678 11679 11680 11681 11682 11683 11684 11685 11686 11687 11688 11689 11690 11691 11692 11693 11694 11695 11696 11697 11698 11699 11700 11701 11702 11703 11704 11705 11706 11707 11708 11709 11710 11711 11712 11713 11714 11715 11716 11717 11718 11719 11720 11721 11722 11723 11724 11725 11726 11727 11728 11729 11730 11731 11732 11733 11734 11735 11736 11737 11738 11739 11740 11741 11742 11743 11744 11745 11746 11747 11748 11749 11750 11751 11752 11753 11754 11755 11756 11757 11758 11759 11760 11761 11762 11763 11764 11765 11766 11767 11768 11769 11770 11771 11772 11773 11774 11775 11776 11777 11778 11779 11780 11781 11782 11783 11784 11785 11786 11787 11788 11789 11790 11791 11792 11793 11794 11795 11796 11797 11798 11799 11800 11801 11802 11803 11804 11805 11806 11807 11808 11809 11810 11811 11812 11813 11814 11815 11816 11817 11818 11819 11820 11821 11822 11823 11824 11825 11826 11827 11828 11829 11830 11831 11832 11833 11834 11835 11836 11837 11838 11839 11840 11841 11842 11843 11844 11845 11846 11847 11848 11849 11850 11851 11852 11853 11854 11855 11856 11857 11858 11859 11860 11861 11862 11863 11864 11865 11866 11867 11868 11869 11870 11871 11872 11873 11874 11875 11876 11877 11878 11879 11880 11881 11882 11883 11884 11885 11886 11887 11888 11889 11890 11891 11892 11893 11894 11895 11896 11897 11898 11899 11900 11901 11902 11903 11904 11905 11906 11907 11908 11909 11910 11911 11912 11913 11914 11915 11916 11917 11918 11919 11920 11921 11922 11923 11924 11925 11926 11927 11928 11929 11930 11931 11932 11933 11934 11935 11936 11937 11938 11939 11940 11941 11942 11943 11944 11945 11946 11947 11948 11949 11950 11951 11952 11953 11954 11955 11956 11957 11958 11959 11960 11961 11962 11963 11964 11965 11966 11967 11968 11969 11970 11971 11972 11973 11974 11975 11976 11977 11978 11979 11980 11981 11982 11983 11984 11985 11986 11987 11988 11989 11990 11991 11992 11993 11994 11995 11996 11997 11998 11999 12000 12001 12002 12003 12004 12005 12006 12007 12008 12009 12010 12011 12012 12013 12014 12015 12016 12017 12018 12019 12020 12021 12022 12023 12024 12025 12026 12027 12028 12029 12030 12031 12032 12033 12034 12035 12036 12037 12038 12039 12040 12041 12042 12043 12044 12045 12046 12047 12048 12049 12050 12051 12052 12053 12054 12055 12056 12057 12058 12059 12060 12061 12062 12063 12064 12065 12066 12067 12068 12069 12070 12071 12072 12073 12074 12075 12076 12077 12078 12079 12080 12081 12082 12083 12084 12085 12086 12087 12088 12089 12090 12091 12092 12093 12094 12095 12096 12097 12098 12099 12100 12101 12102 12103 12104 12105 12106 12107 12108 12109 12110 12111 12112 12113 12114 12115 12116 12117 12118 12119 12120 12121 12122 12123 12124 12125 12126 12127 12128 12129 12130 12131 12132 12133 12134 12135 12136 12137 12138 12139 12140 12141 12142 12143 12144 12145 12146 12147 12148 12149 12150 12151 12152 12153 12154 12155 12156 12157 12158 12159 12160 12161 12162 12163 12164 12165 12166 12167 12168 12169 12170 12171 12172 12173 12174 12175 12176 12177 12178 12179 12180 12181 12182 12183 12184 12185 12186 12187 12188 12189 12190 12191 12192 12193 12194 12195 12196 12197 12198 12199 12200 12201 12202 12203 12204 12205 12206 12207 12208 12209 12210 12211 12212 12213 12214 12215 12216 12217 12218 12219 12220 12221 12222 12223 12224 12225 12226 12227 12228 12229 12230 12231 12232 12233 12234 12235 12236 12237 12238 12239 12240 12241 12242 12243 12244 12245 12246 12247 12248 12249 12250 12251 12252 12253 12254 12255 12256 12257 12258 12259 12260 12261 12262 12263 12264 12265 12266 12267 12268 12269 12270 12271 12272 12273 12274 12275 12276 12277 12278 12279 12280 12281 12282 12283 12284 12285 12286 12287 12288 12289 12290 12291 12292 12293 12294 12295 12296 12297 12298 12299 12300 12301 12302 12303 12304 12305 12306 12307 12308 12309 12310 12311 12312 12313 12314 12315 12316 12317 12318 12319 12320 12321 12322 12323 12324 12325 12326 12327 12328 12329 12330 12331 12332 12333 12334 12335 12336 12337 12338 12339 12340 12341 12342 12343 12344 12345 12346 12347 12348 12349 12350 12351 12352 12353 12354 12355 12356 12357 12358 12359 12360 12361 12362 12363 12364 12365 12366 12367 12368 12369 12370 12371 12372 12373 12374 12375 12376 12377 12378 12379 12380 12381 12382 12383 12384 12385 12386 12387 12388 12389 12390 12391 12392 12393 12394 12395 12396 12397 12398 12399 12400 12401 12402 12403 12404 12405 12406 12407 12408 12409 12410 12411 12412 12413 12414 12415 12416 12417 12418 12419 12420 12421 12422 12423 12424 12425 12426 12427 12428 12429 12430 12431 12432 12433 12434 12435 12436 12437 12438 12439 12440 12441 12442 12443 12444 12445 12446 12447 12448 12449 12450 12451 12452 12453 12454 12455 12456 12457 12458 12459 12460 12461 12462 12463 12464 12465 12466 12467 12468 12469 12470 12471 12472 12473 12474 12475 12476 12477 12478 12479 12480 12481 12482 12483 12484 12485 12486 12487 12488 12489 12490 12491 12492 12493 12494 12495 12496 12497 12498 12499 12500 12501 12502 12503 12504 12505 12506 12507 12508 12509 12510 12511 12512 12513 12514 12515 12516 12517 12518 12519 12520 12521 12522 12523 12524 12525 12526 12527 12528 12529 12530 12531 12532 12533 12534 12535 12536 12537 12538 12539 12540 12541 12542 12543 12544 12545 12546 12547 12548 12549 12550 12551 12552 12553 12554 12555 12556 12557 12558 12559 12560 12561 12562 12563 12564 12565 12566 12567 12568 12569 12570 12571 12572 12573 12574 12575 12576 12577 12578 12579 12580 12581 12582 12583 12584 12585 12586 12587 12588 12589 12590 12591 12592 12593 12594 12595 12596 12597 12598 12599 12600 12601 12602 12603 12604 12605 12606 12607 12608 12609 12610 12611 12612 12613 12614 12615 12616 12617 12618 12619 12620 12621 12622 12623 12624 12625 12626 12627 12628 12629 12630 12631 12632 12633 12634 12635 12636 12637 12638 12639 12640 12641 12642 12643 12644 12645 12646 12647 12648 12649 12650 12651 12652 12653 12654 12655 12656 12657 12658 12659 12660 12661 12662 12663 12664 12665 12666 12667 12668 12669 12670 12671 12672 12673 12674 12675 12676 12677 12678 12679 12680 12681 12682 12683 12684 12685 12686 12687 12688 12689 12690 12691 12692 12693 12694 12695 12696 12697 12698 12699 12700 12701 12702 12703 12704 12705 12706 12707 12708 12709 12710 12711 12712 12713 12714 12715 12716 12717 12718 12719 12720 12721 12722 12723 12724 12725 12726 12727 12728 12729 12730 12731 12732 12733 12734 12735 12736 12737 12738 12739 12740 12741 12742 12743 12744 12745 12746 12747 12748 12749 12750 12751 12752 12753 12754 12755 12756 12757 12758 12759 12760 12761 12762 12763 12764 12765 12766 12767 12768 12769 12770 12771 12772 12773 12774 12775 12776 12777 12778 12779 12780 12781 12782 12783 12784 12785 12786 12787 12788 12789 12790 12791 12792 12793 12794 12795 12796 12797 12798 12799 12800 12801 12802 12803 12804 12805 12806 12807 12808 12809 12810 12811 12812 12813 12814 12815 12816 12817 12818 12819 12820 12821 12822 12823 12824 12825 12826 12827 12828 12829 12830 12831 12832 12833 12834 12835 12836 12837 12838 12839 12840 12841 12842 12843 12844 12845 12846 12847 12848 12849 12850 12851 12852 12853 12854 12855 12856 12857 12858 12859 12860 12861 12862 12863 12864 12865 12866 12867 12868 12869 12870 12871 12872 12873 12874 12875 12876 12877 12878 12879 12880 12881 12882 12883 12884 12885 12886 12887 12888 12889 12890 12891 12892 12893 12894 12895 12896 12897 12898 12899 12900 12901 12902 12903 12904 12905 12906 12907 12908 12909 12910 12911 12912 12913 12914 12915 12916 12917 12918 12919 12920 12921 12922 12923 12924 12925 12926 12927 12928 12929 12930 12931 12932 12933 12934 12935 12936 12937 12938 12939 12940 12941 12942 12943 12944 12945 12946 12947 12948 12949 12950 12951 12952 12953 12954 12955 12956 12957 12958 12959 12960 12961 12962 12963 12964 12965 12966 12967 12968 12969 12970 12971 12972 12973 12974 12975 12976 12977 12978 12979 12980 12981 12982 12983 12984 12985 12986 12987 12988 12989 12990 12991 12992 12993 12994 12995 12996 12997 12998 12999 13000 13001 13002 13003 13004 13005 13006 13007 13008 13009 13010 13011 13012 13013 13014 13015 13016 13017 13018 13019 13020 13021 13022 13023 13024 13025 13026 13027 13028 13029 13030 13031 13032 13033 13034 13035 13036 13037 13038 13039 13040 13041 13042 13043 13044 13045 13046 13047 13048 13049 13050 13051 13052 13053 13054 13055 13056 13057 13058 13059 13060 13061 13062 13063 13064 13065 13066 13067 13068 13069 13070 13071 13072 13073 13074 13075 13076 13077 13078 13079 13080 13081 13082 13083 13084 13085 13086 13087 13088 13089 13090 13091 13092 13093 13094 13095 13096 13097 13098 13099 13100 13101 13102 13103 13104 13105 13106 13107 13108 13109 13110 13111 13112 13113 13114 13115 13116 13117 13118 13119 13120 13121 13122 13123 13124 13125 13126 13127 13128 13129 13130 13131 13132 13133 13134 13135 13136 13137 13138 13139 13140 13141 13142 13143 13144 13145 13146 13147 13148 13149 13150 13151 13152 13153 13154 13155 13156 13157 13158 13159 13160 13161 13162 13163 13164 13165 13166 13167 13168 13169 13170 13171 13172 13173 13174 13175 13176 13177 13178 13179 13180 13181 13182 13183 13184 13185 13186 13187 13188 13189 13190 13191 13192 13193 13194 13195 13196 13197 13198 13199 13200 13201 13202 13203 13204 13205 13206 13207 13208 13209 13210 13211 13212 13213 13214 13215 13216 13217 13218 13219 13220 13221 13222 13223 13224 13225 13226 13227 13228 13229 13230 13231 13232 13233 13234 13235 13236 13237 13238 13239 13240 13241 13242 13243 13244 13245 13246 13247 13248 13249 13250 13251 13252 13253 13254 13255 13256 13257 13258 13259 13260 13261 13262 13263 13264 13265 13266 13267 13268 13269 13270 13271 13272 13273 13274 13275 13276 13277 13278 13279 13280 13281 13282 13283 13284 13285 13286 13287 13288 13289 13290 13291 13292 13293 13294 13295 13296 13297 13298 13299 13300 13301 13302 13303 13304 13305 13306 13307 13308 13309 13310 13311 13312 13313 13314 13315 13316 13317 13318 13319 13320 13321 13322 13323 13324 13325 13326 13327 13328 13329 13330 13331 13332 13333 13334 13335 13336 13337 13338 13339 13340 13341 13342 13343 13344 13345 13346 13347 13348 13349 13350 13351 13352 13353 13354 13355 13356 13357 13358 13359 13360 13361 13362 13363 13364 13365 13366 13367 13368 13369 13370 13371 13372 13373 13374 13375 13376 13377 13378 13379 13380 13381 13382 13383 13384 13385 13386 13387 13388 13389 13390 13391 13392 13393 13394 13395 13396 13397 13398 13399 13400 13401 13402 13403 13404 13405 13406 13407 13408 13409 13410 13411 13412 13413 13414 13415 13416 13417 13418 13419 13420 13421 13422 13423 13424 13425 13426 13427 13428 13429 13430 13431 13432 13433 13434 13435 13436 13437 13438 13439 13440 13441 13442 13443 13444 13445 13446 13447 13448 13449 13450 13451 13452 13453 13454 13455 13456 13457 13458 13459 13460 13461 13462 13463 13464 13465 13466 13467 13468 13469 13470 13471 13472 13473 13474 13475 13476 13477 13478 13479 13480 13481 13482 13483 13484 13485 13486 13487 13488 13489 13490 13491 13492 13493 13494 13495 13496 13497 13498 13499 13500 13501 13502 13503 13504 13505 13506 13507 13508 13509 13510 13511 13512 13513 13514 13515 13516 13517 13518 13519 13520 13521 13522 13523 13524 13525 13526 13527 13528 13529 13530 13531 13532 13533 13534 13535 13536 13537 13538 13539 13540 13541 13542 13543 13544 13545 13546 13547 13548 13549 13550 13551 13552 13553 13554 13555 13556 13557 13558 13559 13560 13561 13562 13563 13564 13565 13566 13567 13568 13569 13570 13571 13572 13573 13574 13575 13576 13577 13578 13579 13580 13581 13582 13583 13584 13585 13586 13587 13588 13589 13590 13591 13592 13593 13594 13595 13596 13597 13598 13599 13600 13601 13602 13603 13604 13605 13606 13607 13608 13609 13610 13611 13612 13613 13614 13615 13616 13617 13618 13619 13620 13621 13622 13623 13624 13625 13626 13627 13628 13629 13630 13631 13632 13633 13634 13635 13636 13637 13638 13639 13640 13641 13642 13643 13644 13645 13646 13647 13648 13649 13650 13651 13652 13653 13654 13655 13656 13657 13658 13659 13660 13661 13662 13663 13664 13665 13666 13667 13668 13669 13670 13671 13672 13673 13674 13675 13676 13677 13678 13679 13680 13681 13682 13683 13684 13685 13686 13687 13688 13689 13690 13691 13692 13693 13694 13695 13696 13697 13698 13699 13700 13701 13702 13703 13704 13705 13706 13707 13708 13709 13710 13711 13712 13713 13714 13715 13716 13717 13718 13719 13720 13721 13722 13723 13724 13725 13726 13727 13728 13729 13730 13731 13732 13733 13734 13735 13736 13737 13738 13739 13740 13741 13742 13743 13744 13745 13746 13747 13748 13749 13750 13751 13752 13753 13754 13755 13756 13757 13758 13759 13760 13761 13762 13763 13764 13765 13766 13767 13768 13769 13770 13771 13772 13773 13774 13775 13776 13777 13778 13779 13780 13781 13782 13783 13784 13785 13786 13787 13788 13789 13790 13791 13792 13793 13794 13795 13796 13797 13798 13799 13800 13801 13802 13803 13804 13805 13806 13807 13808 13809 13810 13811 13812 13813 13814 13815 13816 13817 13818 13819 13820 13821 13822 13823 13824 13825 13826 13827 13828 13829 13830 13831 13832 13833 13834 13835 13836 13837 13838 13839 13840 13841 13842 13843 13844 13845 13846 13847 13848 13849 13850 13851 13852 13853 13854 13855 13856 13857 13858 13859 13860 13861 13862 13863 13864 13865 13866 13867 13868 13869 13870 13871 13872 13873 13874 13875 13876 13877 13878 13879 13880 13881 13882 13883 13884 13885 13886 13887 13888 13889 13890 13891 13892 13893 13894 13895 13896 13897 13898 13899 13900 13901 13902 13903 13904 13905 13906 13907 13908 13909 13910 13911 13912 13913 13914 13915 13916 13917 13918 13919 13920 13921 13922 13923 13924 13925 13926 13927 13928 13929 13930 13931 13932 13933 13934 13935 13936 13937 13938 13939 13940 13941 13942 13943 13944 13945 13946 13947 13948 13949 13950 13951 13952 13953 13954 13955 13956 13957 13958 13959 13960 13961 13962 13963 13964 13965 13966 13967 13968 13969 13970 13971 13972 13973 13974 13975 13976 13977 13978 13979 13980 13981 13982 13983 13984 13985 13986 13987 13988 13989 13990 13991 13992 13993 13994 13995 13996 13997 13998 13999 14000 14001 14002 14003 14004 14005 14006 14007 14008 14009 14010 14011 14012 14013 14014 14015 14016 14017 14018 14019 14020 14021 14022 14023 14024 14025 14026 14027 14028 14029 14030 14031 14032 14033 14034 14035 14036 14037 14038 14039 14040 14041 14042 14043 14044 14045 14046 14047 14048 14049 14050 14051 14052 14053 14054 14055 14056 14057 14058 14059 14060 14061 14062 14063 14064 14065 14066 14067 14068 14069 14070 14071 14072 14073 14074 14075 14076 14077 14078 14079 14080 14081 14082 14083 14084 14085 14086 14087 14088 14089 14090 14091 14092 14093 14094 14095 14096 14097 14098 14099 14100 14101 14102 14103 14104 14105 14106 14107 14108 14109 14110 14111 14112 14113 14114 14115 14116 14117 14118 14119 14120 14121 14122 14123 14124 14125 14126 14127 14128 14129 14130 14131 14132 14133 14134 14135 14136 14137 14138 14139 14140 14141 14142 14143 14144 14145 14146 14147 14148 14149 14150 14151 14152 14153 14154 14155 14156 14157 14158 14159 14160 14161 14162 14163 14164 14165 14166 14167 14168 14169 14170 14171 14172 14173 14174 14175 14176 14177 14178 14179 14180 14181 14182 14183 14184 14185 14186 14187 14188 14189 14190 14191 14192 14193 14194 14195 14196 14197 14198 14199 14200 14201 14202 14203 14204 14205 14206 14207 14208 14209 14210 14211 14212 14213 14214 14215 14216 14217 14218 14219 14220 14221 14222 14223 14224 14225 14226 14227 14228 14229 14230 14231 14232 14233 14234 14235 14236 14237 14238 14239 14240 14241 14242 14243 14244 14245 14246 14247 14248 14249 14250 14251 14252 14253 14254 14255 14256 14257 14258 14259 14260 14261 14262 14263 14264 14265 14266 14267 14268 14269 14270 14271 14272 14273 14274 14275 14276 14277 14278 14279 14280 14281 14282 14283 14284 14285 14286 14287 14288 14289 14290 14291 14292 14293 14294 14295 14296 14297 14298 14299 14300 14301 14302 14303 14304 14305 14306 14307 14308 14309 14310 14311 14312 14313 14314 14315 14316 14317 14318 14319 14320 14321 14322 14323 14324 14325 14326 14327 14328 14329 14330 14331 14332 14333 14334 14335 14336 14337 14338 14339 14340 14341 14342 14343 14344 14345 14346 14347 14348 14349 14350 14351 14352 14353 14354 14355 14356 14357 14358 14359 14360 14361 14362 14363 14364 14365 14366 14367 14368 14369 14370 14371 14372 14373 14374 14375 14376 14377 14378 14379 14380 14381 14382 14383 14384 14385 14386 14387 14388 14389 14390 14391 14392 14393 14394 14395 14396 14397 14398 14399 14400 14401 14402 14403 14404 14405 14406 14407 14408 14409 14410 14411 14412 14413 14414 14415 14416 14417 14418 14419 14420 14421 14422 14423 14424 14425 14426 14427 14428 14429 14430 14431 14432 14433 14434 14435 14436 14437 14438 14439 14440 14441 14442 14443 14444 14445 14446 14447 14448 14449 14450 14451 14452 14453 14454 14455 14456 14457 14458 14459 14460 14461 14462 14463 14464 14465 14466 14467 14468 14469 14470 14471 14472 14473 14474 14475 14476 14477 14478 14479 14480 14481 14482 14483 14484 14485 14486 14487 14488 14489 14490 14491 14492 14493 14494 14495 14496 14497 14498 14499 14500 14501 14502 14503 14504 14505 14506 14507 14508 14509 14510 14511 14512 14513 14514 14515 14516 14517 14518 14519 14520 14521 14522 14523 14524 14525 14526 14527 14528 14529 14530 14531 14532 14533 14534 14535 14536 14537 14538 14539 14540 14541 14542 14543 14544 14545 14546 14547 14548 14549 14550 14551 14552 14553 14554 14555 14556 14557 14558 14559 14560 14561 14562 14563 14564 14565 14566 14567 14568 14569 14570 14571 14572 14573 14574 14575 14576 14577 14578 14579 14580 14581 14582 14583 14584 14585 14586 14587 14588 14589 14590 14591 14592 14593 14594 14595 14596 14597 14598 14599 14600 14601 14602 14603 14604 14605 14606 14607 14608 14609 14610 14611 14612 14613 14614 14615 14616 14617 14618 14619 14620 14621 14622 14623 14624 14625 14626 14627 14628 14629 14630 14631 14632 14633 14634 14635 14636 14637 14638 14639 14640 14641 14642 14643 14644 14645 14646 14647 14648 14649 14650 14651 14652 14653 14654 14655 14656 14657 14658 14659 14660 14661 14662 14663 14664 14665 14666 14667 14668 14669 14670 14671 14672 14673 14674 14675 14676 14677 14678 14679 14680 14681 14682 14683 14684 14685 14686 14687 14688 14689 14690 14691 14692 14693 14694 14695 14696 14697 14698 14699 14700 14701 14702 14703 14704 14705 14706 14707 14708 14709 14710 14711 14712 14713 14714 14715 14716 14717 14718 14719 14720 14721 14722 14723 14724 14725 14726 14727 14728 14729 14730 14731 14732 14733 14734 14735 14736 14737 14738 14739 14740 14741 14742 14743 14744 14745 14746 14747 14748 14749 14750 14751 14752 14753 14754 14755 14756 14757 14758 14759 14760 14761 14762 14763 14764 14765 14766 14767 14768 14769 14770 14771 14772 14773 14774 14775 14776 14777 14778 14779 14780 14781 14782 14783 14784 14785 14786 14787 14788 14789 14790 14791 14792 14793 14794 14795 14796 14797 14798 14799 14800 14801 14802 14803 14804 14805 14806 14807 14808 14809 14810 14811 14812 14813 14814 14815 14816 14817 14818 14819 14820 14821 14822 14823 14824 14825 14826 14827 14828 14829 14830 14831 14832 14833 14834 14835 14836 14837 14838 14839 14840 14841 14842 14843 14844 14845 14846 14847 14848 14849 14850 14851 14852 14853 14854 14855 14856 14857 14858 14859 14860 14861 14862 14863 14864 14865 14866 14867 14868 14869 14870 14871 14872 14873 14874 14875 14876 14877 14878 14879 14880 14881 14882 14883 14884 14885 14886 14887 14888 14889 14890 14891 14892 14893 14894 14895 14896 14897 14898 14899 14900 14901 14902 14903 14904 14905 14906 14907 14908 14909 14910 14911 14912 14913 14914 14915 14916 14917 14918 14919 14920 14921 14922 14923 14924 14925 14926 14927 14928 14929 14930 14931 14932 14933 14934 14935 14936 14937 14938 14939 14940 14941 14942 14943 14944 14945 14946 14947 14948 14949 14950 14951 14952 14953 14954 14955 14956 14957 14958 14959 14960 14961 14962 14963 14964 14965 14966 14967 14968 14969 14970 14971 14972 14973 14974 14975 14976 14977 14978 14979 14980 14981 14982 14983 14984 14985 14986 14987 14988 14989 14990 14991 14992 14993 14994 14995 14996 14997 14998 14999 15000 15001 15002 15003 15004 15005 15006 15007 15008 15009 15010 15011 15012 15013 15014 15015 15016 15017 15018 15019 15020 15021 15022 15023 15024 15025 15026 15027 15028 15029 15030 15031 15032 15033 15034 15035 15036 15037 15038 15039 15040 15041 15042 15043 15044 15045 15046 15047 15048 15049 15050 15051 15052 15053 15054 15055 15056 15057 15058 15059 15060 15061 15062 15063 15064 15065 15066 15067 15068 15069 15070 15071 15072 15073 15074 15075 15076 15077 15078 15079 15080 15081 15082 15083 15084 15085 15086 15087 15088 15089 15090 15091 15092 15093 15094 15095 15096 15097 15098 15099 15100 15101 15102 15103 15104 15105 15106 15107 15108 15109 15110 15111 15112 15113 15114 15115 15116 15117 15118 15119 15120 15121 15122 15123 15124 15125 15126 15127 15128 15129 15130 15131 15132 15133 15134 15135 15136 15137 15138 15139 15140 15141 15142 15143 15144 15145 15146 15147 15148 15149 15150 15151 15152 15153 15154 15155 15156 15157 15158 15159 15160 15161 15162 15163 15164 15165 15166 15167 15168 15169 15170 15171 15172 15173 15174 15175 15176 15177 15178 15179 15180 15181 15182 15183 15184 15185 15186 15187 15188 15189 15190 15191 15192 15193 15194 15195 15196 15197 15198 15199 15200 15201 15202 15203 15204 15205 15206 15207 15208 15209 15210 15211 15212 15213 15214 15215 15216 15217 15218 15219 15220 15221 15222 15223 15224 15225 15226 15227 15228 15229 15230 15231 15232 15233 15234 15235 15236 15237 15238 15239 15240 15241 15242 15243 15244 15245 15246 15247 15248 15249 15250 15251 15252 15253 15254 15255 15256 15257 15258 15259 15260 15261 15262 15263 15264 15265 15266 15267 15268 15269 15270 15271 15272 15273 15274 15275 15276 15277 15278 15279 15280 15281 15282 15283 15284 15285 15286 15287 15288 15289 15290 15291 15292 15293 15294 15295 15296 15297 15298 15299 15300 15301 15302 15303 15304 15305 15306 15307 15308 15309 15310 15311 15312 15313 15314 15315 15316 15317 15318 15319 15320 15321 15322 15323 15324 15325 15326 15327 15328 15329 15330 15331 15332 15333 15334 15335 15336 15337 15338 15339 15340 15341 15342 15343 15344 15345 15346 15347 15348 15349 15350 15351 15352 15353 15354 15355 15356 15357 15358 15359 15360 15361 15362 15363 15364 15365 15366 15367 15368 15369 15370 15371 15372 15373 15374 15375 15376 15377 15378 15379 15380 15381 15382 15383 15384 15385 15386 15387 15388 15389 15390 15391 15392 15393 15394 15395 15396 15397 15398 15399 15400 15401 15402 15403 15404 15405 15406 15407 15408 15409 15410 15411 15412 15413 15414 15415 15416 15417 15418 15419 15420 15421 15422 15423 15424 15425 15426 15427 15428 15429 15430 15431 15432 15433 15434 15435 15436 15437 15438 15439 15440 15441 15442 15443 15444 15445 15446 15447 15448 15449 15450 15451 15452 15453 15454 15455 15456 15457 15458 15459 15460 15461 15462 15463 15464 15465 15466 15467 15468 15469 15470 15471 15472 15473 15474 15475 15476 15477 15478 15479 15480 15481 15482 15483 15484 15485 15486 15487 15488 15489 15490 15491 15492 15493 15494 15495 15496 15497 15498 15499 15500 15501 15502 15503 15504 15505 15506 15507 15508 15509 15510 15511 15512 15513 15514 15515 15516 15517 15518 15519 15520 15521 15522 15523 15524 15525 15526 15527 15528 15529 15530 15531 15532 15533 15534 15535 15536 15537 15538 15539 15540 15541 15542 15543 15544 15545 15546 15547 15548 15549 15550 15551 15552 15553 15554 15555 15556 15557 15558 15559 15560 15561 15562 15563 15564 15565 15566 15567 15568 15569 15570 15571 15572 15573 15574 15575 15576 15577 15578 15579 15580 15581 15582 15583 15584 15585 15586 15587 15588 15589 15590 15591 15592 15593 15594 15595 15596 15597 15598 15599 15600 15601 15602 15603 15604 15605 15606 15607 15608 15609 15610 15611 15612 15613 15614 15615 15616 15617 15618 15619 15620 15621 15622 15623 15624 15625 15626 15627 15628 15629 15630 15631 15632 15633 15634 15635 15636 15637 15638 15639 15640 15641 15642 15643 15644 15645 15646 15647 15648 15649 15650 15651 15652 15653 15654 15655 15656 15657 15658 15659 15660 15661 15662 15663 15664 15665 15666 15667 15668 15669 15670 15671 15672 15673 15674 15675 15676 15677 15678 15679 15680 15681 15682 15683 15684 15685 15686 15687 15688 15689 15690 15691 15692 15693 15694 15695 15696 15697 15698 15699 15700 15701 15702 15703 15704 15705 15706 15707 15708 15709 15710 15711 15712 15713 15714 15715 15716 15717 15718 15719 15720 15721 15722 15723 15724 15725 15726 15727 15728 15729 15730 15731 15732 15733 15734 15735 15736 15737 15738 15739 15740 15741 15742 15743 15744 15745 15746 15747 15748 15749 15750 15751 15752 15753 15754 15755 15756 15757 15758 15759 15760 15761 15762 15763 15764 15765 15766 15767 15768 15769 15770 15771 15772 15773 15774 15775 15776 15777 15778 15779 15780 15781 15782 15783 15784 15785 15786 15787 15788 15789 15790 15791 15792 15793 15794 15795 15796 15797 15798 15799 15800 15801 15802 15803 15804 15805 15806 15807 15808 15809 15810 15811 15812 15813 15814 15815 15816 15817 15818 15819 15820 15821 15822 15823 15824 15825 15826 15827 15828 15829 15830 15831 15832 15833 15834 15835 15836 15837 15838 15839 15840 15841 15842 15843 15844 15845 15846 15847 15848 15849 15850 15851 15852 15853 15854 15855 15856 15857 15858 15859 15860 15861 15862 15863 15864 15865 15866 15867 15868 15869 15870 15871 15872 15873 15874 15875 15876 15877 15878 15879 15880 15881 15882 15883 15884 15885 15886 15887 15888 15889 15890 15891 15892 15893 15894 15895 15896 15897 15898 15899 15900 15901 15902 15903 15904 15905 15906 15907 15908 15909 15910 15911 15912 15913 15914 15915 15916 15917 15918 15919 15920 15921 15922 15923 15924 15925 15926 15927 15928 15929 15930 15931 15932 15933 15934 15935 15936 15937 15938 15939 15940 15941 15942 15943 15944 15945 15946 15947 15948 15949 15950 15951 15952 15953 15954 15955 15956 15957 15958 15959 15960 15961 15962 15963 15964 15965 15966 15967 15968 15969 15970 15971 15972 15973 15974 15975 15976 15977 15978 15979 15980 15981 15982 15983 15984 15985 15986 15987 15988 15989 15990 15991 15992 15993 15994 15995 15996 15997 15998 15999 16000 16001 16002 16003 16004 16005 16006 16007 16008 16009 16010 16011 16012 16013 16014 16015 16016 16017 16018 16019 16020 16021 16022 16023 16024 16025 16026 16027 16028 16029 16030 16031 16032 16033 16034 16035 16036 16037 16038 16039 16040 16041 16042 16043 16044 16045 16046 16047 16048 16049 16050 16051 16052 16053 16054 16055 16056 16057 16058 16059 16060 16061 16062 16063 16064 16065 16066 16067 16068 16069 16070 16071 16072 16073 16074 16075 16076 16077 16078 16079 16080 16081 16082 16083 16084 16085 16086 16087 16088 16089 16090 16091 16092 16093 16094 16095 16096 16097 16098 16099 16100 16101 16102 16103 16104 16105 16106 16107 16108 16109 16110 16111 16112 16113 16114 16115 16116 16117 16118 16119 16120 16121 16122 16123 16124 16125 16126 16127 16128 16129 16130 16131 16132 16133 16134 16135 16136 16137 16138 16139 16140 16141 16142 16143 16144 16145 16146 16147 16148 16149 16150 16151 16152 16153 16154 16155 16156 16157 16158 16159 16160 16161 16162 16163 16164 16165 16166 16167 16168 16169 16170 16171 16172 16173 16174 16175 16176 16177 16178 16179 16180 16181 16182 16183 16184 16185 16186 16187 16188 16189 16190 16191 16192 16193 16194 16195 16196 16197 16198 16199 16200 16201 16202 16203 16204 16205 16206 16207 16208 16209 16210 16211 16212 16213 16214 16215 16216 16217 16218 16219 16220 16221 16222 16223 16224 16225 16226 16227 16228 16229 16230 16231 16232 16233 16234 16235 16236 16237 16238 16239 16240 16241 16242 16243 16244 16245 16246 16247 16248 16249 16250 16251 16252 16253 16254 16255 16256 16257 16258 16259 16260 16261 16262 16263 16264 16265 16266 16267 16268 16269 16270 16271 16272 16273 16274 16275 16276 16277 16278 16279 16280 16281 16282 16283 16284 16285 16286 16287 16288 16289 16290 16291 16292 16293 16294 16295 16296 16297 16298 16299 16300 16301 16302 16303 16304 16305 16306 16307 16308 16309 16310 16311 16312 16313 16314 16315 16316 16317 16318 16319 16320 16321 16322 16323 16324 16325 16326 16327 16328 16329 16330 16331 16332 16333 16334 16335 16336 16337 16338 16339 16340 16341 16342 16343 16344 16345 16346 16347 16348 16349 16350 16351 16352 16353 16354 16355 16356 16357 16358 16359 16360 16361 16362 16363 16364 16365 16366 16367 16368 16369 16370 16371 16372 16373 16374 16375 16376 16377 16378 16379 16380 16381 16382 16383 16384 16385 16386 16387 16388 16389 16390 16391 16392 16393 16394 16395 16396 16397 16398 16399 16400 16401 16402 16403 16404 16405 16406 16407 16408 16409 16410 16411 16412 16413 16414 16415 16416 16417 16418 16419 16420 16421 16422 16423 16424 16425 16426 16427 16428 16429 16430 16431 16432 16433 16434 16435 16436 16437 16438 16439 16440 16441 16442 16443 16444 16445 16446 16447 16448 16449 16450 16451 16452 16453 16454 16455 16456 16457 16458 16459 16460 16461 16462 16463 16464 16465 16466 16467 16468 16469 16470 16471 16472 16473 16474 16475 16476 16477 16478 16479 16480 16481 16482 16483 16484 16485 16486 16487 16488 16489 16490 16491 16492 16493 16494 16495 16496 16497 16498 16499 16500 16501 16502 16503 16504 16505 16506 16507 16508 16509 16510 16511 16512 16513 16514 16515 16516 16517 16518 16519 16520 16521 16522 16523 16524 16525 16526 16527 16528 16529 16530 16531 16532 16533 16534 16535 16536 16537 16538 16539 16540 16541 16542 16543 16544 16545 16546 16547 16548 16549 16550 16551 16552 16553 16554 16555 16556 16557 16558 16559 16560 16561 16562 16563 16564 16565 16566 16567 16568 16569 16570 16571 16572 16573 16574 16575 16576 16577 16578 16579 16580 16581 16582 16583 16584 16585 16586 16587 16588 16589 16590 16591 16592 16593 16594 16595 16596 16597 16598 16599 16600 16601 16602 16603 16604 16605 16606 16607 16608 16609 16610 16611 16612 16613 16614 16615 16616 16617 16618 16619 16620 16621 16622 16623 16624 16625 16626 16627 16628 16629 16630 16631 16632 16633 16634 16635 16636 16637 16638 16639 16640 16641 16642 16643 16644 16645 16646 16647 16648 16649 16650 16651 16652 16653 16654 16655 16656 16657 16658 16659 16660 16661 16662 16663 16664 16665 16666 16667 16668 16669 16670 16671 16672 16673 16674 16675 16676 16677 16678 16679 16680 16681 16682 16683 16684 16685 16686 16687 16688 16689 16690 16691 16692 16693 16694 16695 16696 16697 16698 16699 16700 16701 16702 16703 16704 16705 16706 16707 16708 16709 16710 16711 16712 16713 16714 16715 16716 16717 16718 16719 16720 16721 16722 16723 16724 16725 16726 16727 16728 16729 16730 16731 16732 16733 16734 16735 16736 16737 16738 16739 16740 16741 16742 16743 16744 16745 16746 16747 16748 16749 16750 16751 16752 16753 16754 16755 16756 16757 16758 16759 16760 16761 16762 16763 16764 16765 16766 16767 16768 16769 16770 16771 16772 16773 16774 16775 16776 16777 16778 16779 16780 16781 16782 16783 16784 16785 16786 16787 16788 16789 16790 16791 16792 16793 16794 | ?gnuplot
?copyright
?license
Copyright (C) 1986 - 1993, 1998, 2004, 2007 Thomas Williams, Colin Kelley
Permission to use, copy, and distribute this software and its
documentation for any purpose with or without fee is hereby granted,
provided that the above copyright notice appear in all copies and
that both that copyright notice and this permission notice appear
in supporting documentation.
Permission to modify the software is granted, but not the right to
distribute the complete modified source code. Modifications are to
be distributed as patches to the released version. Permission to
distribute binaries produced by compiling modified sources is granted,
provided you
1. distribute the corresponding source modifications from the
released version in the form of a patch file along with the binaries,
2. add special version identification to distinguish your version
in addition to the base release version number,
3. provide your name and address as the primary contact for the
support of your modified version, and
4. retain our contact information in regard to use of the base software.
Permission to distribute the released version of the source code along
with corresponding source modifications in the form of a patch file is
granted with same provisions 2 through 4 for binary distributions.
This software is provided "as is" without express or implied warranty
to the extent permitted by applicable law.
AUTHORS
Original Software:
Thomas Williams, Colin Kelley.
Gnuplot 2.0 additions:
Russell Lang, Dave Kotz, John Campbell.
Gnuplot 3.0 additions:
Gershon Elber and many others.
Gnuplot 4.0 and 5.0 additions:
See list of contributors at head of this document.
?introduction
?
`Gnuplot` is a portable command-line driven graphing utility for Linux, OS/2,
MS Windows, OSX, VMS, and many other platforms. The source code is copyrighted
but freely distributed (i.e., you don't have to pay for it). It was originally
created to allow scientists and students to visualize mathematical functions
and data interactively, but has grown to support many non-interactive uses
such as web scripting. It is also used as a plotting engine by third-party
applications like Octave. Gnuplot has been supported and under active
development since 1986.
Gnuplot supports many types of plots in either 2D and 3D. It can draw using
lines, points, boxes, contours, vector fields, surfaces, and various
associated text. It also supports various specialized plot types.
Gnuplot supports many different types of output: interactive screen terminals
(with mouse and hotkey input), direct output to pen plotters or modern
printers, and output to many file formats (eps, emf, fig, jpeg, LaTeX, pdf, png,
postscript, ...). Gnuplot is easily extensible to include new output modes.
Recent additions include interactive terminals based on wxWidgets (usable
on multiple platforms), and Qt. Mouseable plots embedded in web pages
can be generated using the svg or HTML5 canvas terminal drivers.
The command language of `gnuplot` is case sensitive, i.e. commands and
function names written in lowercase are not the same as those written in
capitals. All command names may be abbreviated as long as the abbreviation is
not ambiguous. Any number of commands may appear on a line, separated by
semicolons (;). Strings may be set off by either single or double quotes,
although there are some subtle differences. See `syntax` and `quotes` for
more details. Example:
set title "My First Plot"; plot 'data'; print "all done!"
Commands may extend over several input lines by ending each line but the last
with a backslash (\). The backslash must be the _last_ character on each
line. The effect is as if the backslash and newline were not there. That
is, no white space is implied, nor is a comment terminated. Therefore,
commenting out a continued line comments out the entire command
(see `comments`). But note that if an error occurs somewhere on a multi-line
command, the parser may not be able to locate precisely where the error is
and in that case will not necessarily point to the correct line.
In this document, curly braces ({}) denote optional arguments and a vertical
bar (|) separates mutually exclusive choices. `Gnuplot` keywords or `help`
topics are indicated by backquotes or `boldface` (where available). Angle
brackets (<>) are used to mark replaceable tokens. In many cases, a default
value of the token will be taken for optional arguments if the token is
omitted, but these cases are not always denoted with braces around the angle
brackets.
For built-in help on any topic, type `help` followed by the name of the topic
or `help ?` to get a menu of available topics.
A large set of demo plots is available on the web page
http://www.gnuplot.info/demo/
When run from command line, gnuplot is invoked using the syntax
gnuplot {OPTIONS} file1 file2 ...
where file1, file2, etc. are input file as in the `load` command.
On X11-based systems, you can use
gnuplot {X11OPTIONS} {OPTIONS} file1 file2 ...
see your X11 documentation and `x11` in this document.
Options interpreted by gnuplot may come anywhere on the line. Files are
executed in the order specified, as are commands supplied by the -e option,
for example
gnuplot file1.in -e "reset" file2.in
The special filename "-" is used to force reading from stdin. `Gnuplot` exits
after the last file is processed. If no load files are named, `Gnuplot` takes
interactive input from stdin. See help `batch/interactive` for more details.
The options specific to gnuplot can be listed by typing
gnuplot --help
See `command line options` for more details.
In sessions with an interactive plot window you can hit 'h' anywhere on the
plot for help about `hotkeys` and `mousing` features.
Section `seeking-assistance` will help you to find further information, help
and FAQ.
?help-desk
?faq
?FAQ
?seeking-assistance
The canonical gnuplot web page can be found at
http://www.gnuplot.info
Before seeking help, please check file FAQ.pdf or the above website for
FAQ (Frequently Asked Questions) list.
If you need help as a gnuplot user, please use the newsgroup
comp.graphics.apps.gnuplot
Instructions for subscribing to gnuplot mailing lists may be
found via the gnuplot development website on SourceForge
http://sourceforge.net/projects/gnuplot
Please note that before you write to any of the gnuplot mailing lists,
you have to subscribe to the list first. This is necessary to keep the
spam level down.
The address for mailing to list members is:
gnuplot-info@lists.sourceforge.net
Bug reports and code contributions should be uploaded to the trackers at
http://sourceforge.net/projects/gnuplot/support
Please check previous bug reports if the bug you want to report has not been
already fixed in a newer version.
A mailing list for those interested in development version of gnuplot is:
gnuplot-beta@lists.sourceforge.net
When posting a question, please include full details of the gnuplot version,
the terminal type, and the operating system you are using. A short
self-contained script demonstrating the problem is often helpful.
?new version_5.2
?new
Version 5.2 is the current stable release series for gnuplot.
The following list of new features is up to date as of May 2017.
?new plot styles
* 3D plot style `with zerrorfill`. See `zerrorfill`, `fenceplots` and
zerror demo.
* Beeswarm plots. See `set jitter`, `beeswarm` and
beeswarm plot demo
* The symbol used for individual points in a plot can be controlled by data values
(see `pointtype variable`)
?new filters
* Normalized frequency of occurrence in a data set (see `smooth fnormal`)
* Automated binning of data (see `bins`)
?new polar mode features
* Polar coordinates may be used in label, arrow, and object definitions
* `set [m]ttics` places ticmarks and labels on the perimeter of a polar plot. See
* `set rlabel` places a label above the r axis
* Inverted `rrange` (i.e. set rrange [90:0]) allows use of celestial horizontal
coordinates. See
* `set border polar` draws a solid line around the perimeter of a polar plot
* `set theta` controls the position of theta = 0 around the perimeter of a
polar plot and the sense (clockwise or anti-clockwise) of increasing theta
?new nonlinear coordinates
* Any plot axis can be assigned a pair of functions, possibly nonlinear, that
describe the forward and reverse mapping to a linear range (see `set nonlinear`)
Nonlinear x/y axis demo
* The familiar command `set logscale` is re-implemented as a special case of a
nonlinear axis where the paired functions are log(x) and exp(x).
?new commands
* Inside the bracketed clause of an iteration, `continue` jumps immediately
to the next iteration, `break` immediately exits from the iteration
* `toggle {<plotno> | "plottitle" | all}"` interactively enables or disables
display of one element of the current plot (see `toggle`)
* `save fit` replaces deprecated command `update`
* `set table "outfile.name" append` will append subsequent tabulated plots to
an existing text file rather replacing its contents
* `set pm3d lighting` describes a lighting model with specular highlighting
(see `lighting`)
* `set minussign` tells gnuplot to use a special symbol in the current
encoding to replace the ascii character '-' in negative numbers
* `set micro` tells gnuplot to use a special symbol in the current encoding to
replace the ascii character 'u' for the scientific notation prefix "micro"
The special typographic symbols for micro and minussign are used only in axis
tic labels and strings explicitly created with gprintf(). The byte sequence
used to represent these characters depends on the current encoding.
?new features
* This gnuplot version introduces a new data type `array name[size]`.
An array must be declared before use. Each array element A[i] may be a string,
an integer, a real number, or a complex value. A single array may contain
elements with different types. The cardinality operator |A| returns the size
of array A. See `arrays`.
* See `sixelgd` for description of a new terminal that supports interleaving
plots with the command lines that generated them if gnuplot is run inside a
vt340-compatible terminal emulator
* The `domterm` terminal supports interleaving plots with the command lines
that generated them if gnuplot is run inside an svg-aware terminal emulator
* The `windows` terminal supports saving the current graph to a bitmap file
* The `windows` terminal graph window can be docked to the wgnuplot text window
* New (experimental) Direct2D/DirectWrite backend for the `windows` terminal
* The `wxt` terminal supports exporting to an EMF file or printer on Windows
* The `dumb` terminal supports ANSI colors for lines and fill area
* The `tkcanvas` terminal has been rewritten to support many more modern gnuplot
features, as well as new languages. (Since 5.0.3)
* An additional rotation angle `azimuth` affects the orientation of 3D plots.
This can be set from the command line (see `set view azimuth`) or by dragging
with the right mouse button.
* gnuplot running under Windows can interpret Unicode (BMP) input scripts by
converting them to the current encoding from `set encoding`, including UTF-8
* Textboxes can be assigned a border color and fill color (see `set style textbox`)
* Customized plot legends (see `plot title`, `set key`, `multiple keys`)
* A sampling range specifier for plotting with pseudofile '+' can include a
sampling interval. For example:
plot sample [t=0:100:10] '+' using (t):(1):(label[t]) with labels
* Pseudo-file '++' generates samples on the u and v axes, rather than x and y.
This allows placement of multiple parametric surfaces in 3D that occupy
distinct regions of Cartesian space. See `sampling.dem`.
* ^R initiates a reverse-search through the history for the built-in readline
which is used on Windows, too, see `command-line-editing`.
* Revised printing support on Windows using `set output "PRN"`,
see `windows printing`.
?Features introduced in version 5.0
* The dot-dash pattern of a line can now be specified independent of other
line properties. See `dashtype`, `set dashtype`, `set linetype`
* The default sequence of colors used for successive elements in a plot is
more easily distinguished by users with color-vision defects.
The color sequence is under user control (see `set colorsequence`).
This mechanism can also be used to generate monochrome plots
(see `set monochrome`). In previous gnuplot versions `monochrome` could only
be selected when changing the current terminal via `set terminal`.
* New plot styles `with parallelaxes`, `with table`, and labeled contours.
* New data pre-processing filter for monotonic cubic splines (see `smooth mcsplines`)
* Text markup now supports bold and italic font settings in addition to
subscript, superscript, font size and other previously available properties.
Enhanced text mode is now enabled by default. See `enhanced text`.
Text elements can be enclosed in a box (see `set style textbox`).
* Interactive terminals support hypertext labels that only appear when the
mouse hovers over the label's anchor point.
* New coordinate system (Degrees, Minutes, Seconds). See `set xtics geographic`.
* The default format for axis labels is "% h" ("$%h$" for LaTeX terminals).
This format is like the C standard format %g except that the exponential term,
if present, is written using a superscript. E.g. 1.2 x 10^5 rather than 1.2E05.
* Command scripts may place in-line data in a named data block for repeated
plotting. See `inline data`.
* Support for 32-bit Alpha channel + RGB color #AARRGGBB. See `colorspec`.
* Support for HSV color space via a translation function hsv2rgb(H,S,V).
* Secondary axes (x2, y2) may be locked to the primary axis via a mapping
function. In the simplest case this guarantees that the primary and secondary
axis ranges are identical. In the general case it allows you to define a
non-linear axis, something that previously was possible only for log scaling.
See `set link`.
* Each function in a plot command may optionally be preceded by a sampling
range. This does not affect the overall range of the plot, only the range
over which this function is sampled. See `plot` and `piecewise.dem`.
* If the external library libcerf is available, it is used to provide complex
math routines cerf, cdawson, erfi, faddeeva, and the Voigt profile
VP(x,sigma,gamma).
* The `import` command attaches a user-defined function name to a function
provided by an external shared object (support is operating-system dependent).
A template header and example source and make files for creating a suitable
external shared object are provided in the demo collection.
* Previous commands in the history list of an interactive session can be
reexecuted by number. For example, `history !5` will reexecute the command
numbered 5 in the `history` list.
* Bit-shift operators >> and <<.
* Shell invocation of gnuplot can pass parameters to a gnuplot script.
gnuplot -c scriptfile.gp ARG1 ARG2 ARG3 ...
?changes
?differences
Some changes introduced in version 5 may cause certain scripts written
for earlier versions of gnuplot to behave differently.
* Revised handling of input data containing NaN, inconsistent number of data
columns, or other unexpected content. See Note under `missing` for examples
and figures.
* Time coordinates are stored internally as the number of seconds relative to
the standard unix epoch 1-Jan-1970. Earlier versions of gnuplot used a
different epoch internally (1-Jan-2000). This change resolves inconsistencies
introduced whenever time in seconds was generated externally. The epoch
convention used by a particular gnuplot installation can be determined using
the command `print strftime("%F",0)`. Time is now stored to at least
millisecond precision.
* The function `timecolumn(N,"timeformat")` now has 2 parameters. Because the
new second parameter is not associated with any particular data axis, this
allows using the `timecolumn` function to read time data for reasons other than
specifying the x or y coordinate. This functionality replaces the command
sequence `set xdata time; set timefmt "timeformat"`. It allows combining time
data read from multiple files with different formats within a single plot.
* The `reverse` keyword of the `set [axis]range` command affects only
autoscaling. It does not invert or otherwise alter the meaning of a command
such as `set xrange [0:1]`. If you want to reverse the direction of the
x axis in such a case, say instead `set xrange [1:0]`.
* The `call` command is implemented by providing a set of variables ARGC,
ARG0, ..., ARG9. ARG0 holds the name of the script file being executed.
ARG1 to ARG9 are string variables and thus may either be referenced directly
or expanded as macros, e.g. @ARG1. The older convention for referencing
call parameters as tokens $0 ... $9 is deprecated.
* The optional bandwidth for the kernel density smoothing option is taken from
a keyword rather than a data column. See `smooth kdensity`.
?deprecated syntax
?backwards compatibility
?compatibility
Gnuplot version 4 deprecated certain syntax used in earlier versions but
provided a configuration option that allowed backward compatibility.
Support for the old syntax has now been removed.
Deprecated in version 4 and removed in version 5:
set title "Old" 0,-1
set data linespoints
plot 1 2 4 # horizontal line at y=1
Current equivalent:
TITLE = "New"
set title TITLE offset char 0, char -1
set style data linespoints
plot 1 linetype 2 pointtype 4
Deprecated, present in version 5.0 if configured --enable-backwards-compatibility
if (defined(VARNAME)) ...
set style increment user
plot 'file' thru f(x)
call 'script' 1.23 ABC
(in script: print $0, "$1", "number of args = $#")
Current equivalent:
if (exists("VARNAME")) ...
set linetype
plot 'file' using 1:(f(column(2)))
call 'script' 1.23 "ABC"
(in script: print ARG1, ARG2, "number of args = ", ARGC
?demos
?online examples
?examples
The `gnuplot` distribution contains a collection of examples in the `demo`
directory. You can browse on-line versions of these examples produced by the
png, svg, and canvas terminals at
http://gnuplot.info/demos
The commands that produced each demo plot are shown next to the plot, and
the corresponding gnuplot script can be downloaded to serve as a model for
generating similar plots.
?batch/interactive
?command line options
`Gnuplot` may be executed in either batch or interactive modes, and the two
may even be mixed together on many systems.
Any command-line arguments are assumed to be either program options (first
character is -) or names of files containing `gnuplot` commands. The option
-e "command" may be used to force execution of a gnuplot command. Each file
or command string will be executed in the order specified. The special
filename "-" is indicates that commands are to be read from stdin.
`Gnuplot` exits after the last file is processed. If no load files and no
command strings are specified, `gnuplot` accepts interactive input from
stdin.
Both the `exit` and `quit` commands terminate the current command file and
`load` the next one, until all have been processed.
Examples:
To launch an interactive session:
gnuplot
To launch a batch session using two command files "input1" and "input2":
gnuplot input1 input2
To launch an interactive session after an initialization file "header" and
followed by another command file "trailer":
gnuplot header - trailer
To give `gnuplot` commands directly in the command line, using the "-persist"
option so that the plot remains on the screen afterwards:
gnuplot -persist -e "set title 'Sine curve'; plot sin(x)"
To set user-defined variables a and s prior to executing commands from a file:
gnuplot -e "a=2; s='file.png'" input.gpl
?canvas size
?canvas
?set term size
In earlier versions of gnuplot, some terminal types used the values from
`set size` to control also the size of the output canvas; others did not.
The use of 'set size' for this purpose was deprecated in version 4.2.
Almost all terminals now behave as follows:
`set term <terminal_type> size <XX>, <YY>` controls the size of the output
file, or "canvas". By default, the plot will fill this canvas.
`set size <XX>, <YY>` scales the plot itself relative to the size of the
canvas. Scale values less than 1 will cause the plot to not fill the entire
canvas. Scale values larger than 1 will cause only a portion of the plot to
fit on the canvas. Please be aware that setting scale values larger than 1
may cause problems.
The major exception to this convention is the PostScript driver, which
by default continues to act as it did in earlier versions. Be warned that
some future version of gnuplot may change the default behaviour of the
PostScript driver as well.
Example:
set size 0.5, 0.5
set term png size 600, 400
set output "figure.png"
plot "data" with lines
These commands produce an output file "figure.png" that is 600 pixels
wide and 400 pixels tall. The plot will fill the lower left quarter of this
canvas. This is consistent with the way multiplot mode has always worked.
?line-editing
?editing
?command-line-editing
Command-line editing and command history are supported using either an
external gnu readline library, an external BSD libedit library, or a
built-in equivalent. This choice is a configuration option at the time
gnuplot is built.
The editing commands of the built-in version are given below. Please note that
the action of the DEL key is system-dependent. The gnu readline and BSD libedit
libraries have their own documentation.
`Line-editing`:
^B moves back a single character.
^F moves forward a single character.
^A moves to the beginning of the line.
^E moves to the end of the line.
^H deletes the previous character.
DEL deletes the current character.
^D deletes current character, sends EOF if the line is empty.
^K deletes from current position to the end of line.
^L redraws line in case it gets trashed.
^U deletes the entire line.
^W deletes previous word.
^V inhibits the interpretation of the following key as editing command.
TAB performs filename-completion.
`History`:
^P moves back through history.
^N moves forward through history.
^R starts a backward-search.
?comments
The comment character `#` may appear almost anywhere in a command line, and
`gnuplot` will ignore the rest of that line. A `#` does not have this effect
inside a quoted string. Note that if a commented line ends in '\' then the
subsequent line is also treated as part of the comment.
See also `set datafile commentschars` for specifying a comment character for
data files.
?coordinates
The commands `set arrow`, `set key`, `set label` and `set object` allow you
to draw something at an arbitrary position on the graph. This position is
specified by the syntax:
{<system>} <x>, {<system>} <y> {,{<system>} <z>}
Each <system> can either be `first`, `second`, `polar`, `graph`, `screen`, or
`character`.
`first` places the x, y, or z coordinate in the system defined by the left
and bottom axes; `second` places it in the system defined by the x2,y2 axes
(top and right); `graph` specifies the area within the axes---0,0 is bottom
left and 1,1 is top right (for splot, 0,0,0 is bottom left of plotting area;
use negative z to get to the base---see `set xyplane`); `screen`
specifies the screen area (the entire area---not just the portion selected by
`set size`), with 0,0 at bottom left and 1,1 at top right. `character`
coordinates are used primarily for offsets, not absoute positions.
The `character` vertical and horizontal size depend on the current font.
`polar` causes the first two values to be interpreted as angle theta and radius
r rather than as x and y. This could be used, for example, to place labels on
a 2D plot in polar coordinates or a 3D plot in cylindrical coordinates.
If the coordinate system for x is not specified, `first` is used. If the
system for y is not specified, the one used for x is adopted.
In some cases, the given coordinate is not an absolute position but a
relative value (e.g., the second position in `set arrow` ... `rto`). In
most cases, the given value serves as difference to the first position.
If the given coordinate belongs to a log-scaled axis, a relative value is
interpreted as multiplier. For example,
set logscale x
set arrow 100,5 rto 10,2
plots an arrow from position 100,5 to position 1000,7 since the x axis is
logarithmic while the y axis is linear.
If one (or more) axis is timeseries, the appropriate coordinate should
be given as a quoted time string according to the `timefmt` format string.
See `set xdata` and `set timefmt`. `Gnuplot` will also accept an integer
expression, which will be interpreted as seconds relative to 1 January 1970.
?datastrings
Data files may contain string data consisting of either an arbitrary string
of printable characters containing no whitespace or an arbitrary string of
characters, possibly including whitespace, delimited by double quotes.
The following line from a datafile is interpreted to contain four
columns, with a text field in column 3:
1.000 2.000 "Third column is all of this text" 4.00
Text fields can be positioned within a 2-D or 3-D plot using the commands:
plot 'datafile' using 1:2:4 with labels
splot 'datafile' using 1:2:3:4 with labels
A column of text data can also be used to label the ticmarks along one or more
of the plot axes. The example below plots a line through a series of points
with (X,Y) coordinates taken from columns 3 and 4 of the input datafile.
However, rather than generating regularly spaced tics along the x axis
labeled numerically, gnuplot will position a tic mark along the x axis at the
X coordinate of each point and label the tic mark with text taken from column
1 of the input datafile.
set xtics
plot 'datafile' using 3:4:xticlabels(1) with linespoints
There is also an option that will interpret the first entry in a column of
input data (i.e. the column heading) as a text field, and use it as the key
title for data plotted from that column. The example given below will use the
first entry in column 2 to generate a title in the key box, while processing
the remainder of columns 2 and 4 to draw the required line:
plot 'datafile' using 1:(f($2)/$4) with lines title columnhead(2)
Another example:
plot for [i=2:6] 'datafile' using i title "Results for ".columnhead(i)
This use of column headings is automated by `set key autotitle columnhead`.
See `labels`, `using xticlabels`, `plot title`, `using`, `key autotitle`.
?enhanced text
?enhanced
?text_markup
?markup
?bold
?italic
Many terminal types support an enhanced text mode in which additional
formatting information is embedded in the text string. For example, "x^2"
will write x-squared as we are used to seeing it, with a superscript 2.
This mode is selected by default when you set the terminal, but may be
toggled afterward using "set termoption [no]enhanced", or by marking
individual strings as in "set label 'x_2' noenhanced".
Control Examples Explanation
^ a^x superscript
_ a_x subscript
@ @x or a@^b_{cd} phantom box (occupies no width)
& &{space} inserts space of specified length
~ ~a{.8-} overprints '-' on 'a', raised by .8
times the current fontsize
{/Times abc} print abc in font Times at current size
{/Times*2 abc} print abc in font Times at twice current size
{/Times:Italic abc} print abc in font Times with style italic
{/Arial:Bold=20 abc} print abc in boldface Arial font size 20
The markup control characers act on the following single character or
bracketed clause. The bracketed clause may contain a string of characters with
no additional markup, e.g. 2^{10}, or it may contain additional markup that
changes font properties. This example illustrates nesting one bracketed clause
inside another to produce a boldface A with an italic subscript i, all in the
current font. If the clause introduced by :Normal were omitted the subscript
would be both italic and boldface.
{/:Bold A_{/:Normal{/:Italic i}}}
Font specifiers MUST be preceeded by a '/' character that immediately follows
the opening '{'.
The phantom box is useful for a@^b_c to align superscripts and subscripts
but does not work well for overwriting an accent on a letter. For the latter,
it is much better to use an encoding (e.g. iso_8859_1 or utf8) that contains
a large variety of letters with accents or other diacritical marks. See
`set encoding`. Since the box is non-spacing, it is sensible to put the shorter
of the subscript or superscript in the box (that is, after the @).
Space equal in length to a string can be inserted using the '&' character.
Thus
'abc&{def}ghi'
would produce
'abc ghi'.
The '~' character causes the next character or bracketed text to be
overprinted by the following character or bracketed text. The second text
will be horizontally centered on the first. Thus '~a/' will result in an 'a'
with a slash through it. You can also shift the second text vertically by
preceding the second text with a number, which will define the fraction of the
current fontsize by which the text will be raised or lowered. In this case
the number and text must be enclosed in brackets because more than one
character is necessary. If the overprinted text begins with a number, put a
space between the vertical offset and the text ('~{abc}{.5 000}'); otherwise
no space is needed ('~{abc}{.5---}'). You can change the font for one or
both strings ('~a{.5 /*.2 o}'---an 'a' with a one-fifth-size 'o' on top---and
the space between the number and the slash is necessary), but you can't
change it after the beginning of the string. Neither can you use any other
special syntax within either string. You can, of course, use control
characters by escaping them (see below), such as '~a{\^}'
You can specify special symbols numerically by giving a character code in
octal, e.g. {/Symbol \245} is the symbol for infinity in the Adobe Symbol font.
This does not work for multibyte encodings like UTF-8, however. In a UTF-8
environment, you should be able to enter multibyte sequences implicitly by
typing or otherwise selecting the character you want.
You can escape control characters using \, e.g., \\, \{, and so on.
Note that strings in double-quotes are parsed differently than those enclosed
in single-quotes. The major difference is that backslashes may need to be
doubled when in double-quoted strings.
The file "ps_guide.ps" in the /docs/psdoc subdirectory of the gnuplot source
distribution contains more examples of the enhanced syntax, as does the demo
`enhanced_utf8.dem`
?environment
A number of shell environment variables are understood by `gnuplot`. None of
these are required, but may be useful.
GNUTERM, if defined, is used to set the terminal type on start-up.
Starting with version 5.2 the entire string in GNUTERM is passed to
"set term" so that terminal options may be included. E.g.
GNUTERM="postscript eps color size 5in, 3in"
This can be overridden by the ~/.gnuplot (or equivalent) start-up file
(see `startup`) and of course by later explicit `set term` commands.
GNUHELP may be defined to be the pathname of the HELP file (gnuplot.gih).
On VMS, the logical name GNUPLOT$HELP should be defined as the name of the
help library for `gnuplot`. The `gnuplot` help can be put inside any VMS
system help library.
On Unix, HOME is used as the name of a directory to search for a .gnuplot
file if none is found in the current directory. On MS-DOS, Windows and OS/2,
GNUPLOT is used. On Windows, the NT-specific variable USERPROFILE is also
tried. VMS, SYS$LOGIN: is used. Type `help startup`.
On Unix, PAGER is used as an output filter for help messages.
On Unix, SHELL is used for the `shell` command. On MS-DOS and OS/2, COMSPEC
is used for the `shell` command.
`FIT_SCRIPT` may be used to specify a `gnuplot` command to be executed when a
fit is interrupted---see `fit`. `FIT_LOG` specifies the default filename of the
logfile maintained by fit.
GNUPLOT_LIB may be used to define additional search directories for data
and command files. The variable may contain a single directory name, or
a list of directories separated by a platform-specific path separator,
eg. ':' on Unix, or ';' on DOS/Windows/OS/2 platforms. The contents
of GNUPLOT_LIB are appended to the `loadpath` variable, but not saved
with the `save` and `save set` commands.
Several gnuplot terminal drivers access TrueType fonts via the gd library.
For these drivers the font search path is controlled by the environmental
variable GDFONTPATH. Furthermore, a default font for these drivers may be
set via the environmental variable GNUPLOT_DEFAULT_GDFONT.
The postscript terminal uses its own font search path. It is controlled by
the environmental variable GNUPLOT_FONTPATH. The format is the same as for
GNUPLOT_LIB. The contents of GNUPLOT_FONTPATH are appended to the `fontpath`
variable, but not saved with the `save` and `save set` commands.
GNUPLOT_PS_DIR is used by the postscript driver to search for external
prologue files. Depending on the build process, gnuplot contains either a
built-in copy of those files or a default hardcoded path. You can use this
variable have the postscript terminal use custom prologue files rather than
the default files. See `postscript prologue`.
?expressions
?division
In general, any mathematical expression accepted by C, FORTRAN, Pascal, or
BASIC is valid. The precedence of these operators is determined by the
specifications of the C programming language. White space (spaces and tabs)
is ignored inside expressions.
Note that gnuplot uses both "real" and "integer" arithmetic, like FORTRAN and
C. Integers are entered as "1", "-10", etc; reals as "1.0", "-10.0", "1e1",
3.5e-1, etc. The most important difference between the two forms is in
division: division of integers truncates: 5/2 = 2; division of reals does
not: 5.0/2.0 = 2.5. In mixed expressions, integers are "promoted" to reals
before evaluation: 5/2e0 = 2.5. The result of division of a negative integer
by a positive one may vary among compilers. Try a test like "print -5/2" to
determine if your system always rounds down (-5/2 yields -3) or always rounds
toward zero (-5/2 yields -2).
The integer expression "1/0" may be used to generate an "undefined" flag,
which causes a point to be ignored. Or you can use the pre-defined variable
NaN to achieve the same result. See `using` for an example.
Gnuplot can also perform simple operations on strings and string variables.
For example, the expression ("A" . "B" eq "AB") evaluates as true, illustrating
the string concatenation operator and the string equality operator.
A string which contains a numerical value is promoted to the corresponding
integer or real value if used in a numerical expression. Thus ("3" + "4" == 7)
and (6.78 == "6.78") both evaluate to true. An integer, but not a real or
complex value, is promoted to a string if used in string concatenation.
A typical case is the use of integers to construct file names or other strings;
e.g. ("file" . 4 eq "file4") is true.
Substrings can be specified using a postfixed range descriptor [beg:end].
For example, "ABCDEF"[3:4] == "CD" and "ABCDEF"[4:*] == "DEF"
The syntax "string"[beg:end] is exactly equivalent to calling the built-in
string-valued function substr("string",beg,end), except that you cannot
omit either beg or end from the function call.
?constants
?expressions constants
?octal
?hexadecimal
?complex
Integer constants are interpreted via the C library routine strtoll().
This means that constants beginning with "0" are interpreted as octal,
and constants beginning with "0x" or "0X" are interpreted as hexadecimal.
Floating point constants are interpreted via the C library routine atof().
Complex constants are expressed as {<real>,<imag>}, where <real> and <imag>
must be numerical constants. For example, {3,2} represents 3 + 2i; {0,1}
represents 'i' itself. The curly braces are explicitly required here.
String constants consist of any sequence of characters enclosed either in
single quotes or double quotes. The distinction between single and double
quotes is important. See `quotes`.
Examples:
1 -10 0xffaabb # integer constants
1.0 -10. 1e1 3.5e-1 # floating point constants
{1.2, -3.4} # complex constant
"Line 1\nLine 2" # string constant (\n is expanded to newline)
'123\n456' # string constant (\ and n are ordinary characters)
?expressions functions
Arguments to math functions in `gnuplot` can be integer, real, or complex
unless otherwise noted. Functions that accept or return angles (e.g. sin(x))
treat angle values as radians, but this may be changed to degrees using the
command `set angles`.
?expressions functions abs
?abs
The `abs(x)` function returns the absolute value of its argument. The
returned value is of the same type as the argument.
For complex arguments, abs(x) is defined as the length of x in the complex
plane [i.e., sqrt(real(x)**2 + imag(x)**2) ]. This is also known as the norm
or complex modulus of x.
?expressions functions acos
?acos
The `acos(x)` function returns the arc cosine (inverse cosine) of its
argument. `acos` returns its argument in radians or degrees, as selected by
`set angles`.
?expressions functions acosh
?acosh
The `acosh(x)` function returns the inverse hyperbolic cosine of its argument
in radians.
?expressions functions airy
?airy
The `airy(x)` function returns the value of the Airy function Ai(x) of its
argument. The function Ai(x) is that solution of the equation y'' - x y = 0
which is everywhere finite. If the argument is complex, its imaginary part
is ignored.
?expressions functions arg
?arg
The `arg(x)` function returns the phase of a complex number in radians or
degrees, as selected by `set angles`.
?expressions functions asin
?asin
The `asin(x)` function returns the arc sin (inverse sin) of its argument.
`asin` returns its argument in radians or degrees, as selected by `set
angles`.
?expressions functions asinh
?asinh
The `asinh(x)` function returns the inverse hyperbolic sin of its argument in
radians.
?expressions functions atan
?atan
The `atan(x)` function returns the arc tangent (inverse tangent) of its
argument. `atan` returns its argument in radians or degrees, as selected by
`set angles`.
?expressions functions atan2
?atan2
The `atan2(y,x)` function returns the arc tangent (inverse tangent) of the
ratio of the real parts of its arguments. `atan2` returns its argument in
radians or degrees, as selected by `set angles`, in the correct quadrant.
?expressions functions atanh
?atanh
The `atanh(x)` function returns the inverse hyperbolic tangent of its
argument in radians.
?expressions functions EllipticK
?EllipticK
The `EllipticK(k)` function returns the complete elliptic integral of the
first kind. See `elliptic integrals` for more details.
?expressions functions EllipticE
?EllipticE
The `EllipticE(k)` function returns the complete elliptic integral of the
second kind. See `elliptic integrals` for more details.
?expressions functions EllipticPi
?EllipticPi
The `EllipticPi(n,k)` function returns the complete elliptic integral of the
third kind. See `elliptic integrals` for more details.
?expressions functions besj0
?besj0
The `besj0(x)` function returns the J0th Bessel function of its argument.
`besj0` expects its argument to be in radians.
?expressions functions besj1
?besj1
The `besj1(x)` function returns the J1st Bessel function of its argument.
`besj1` expects its argument to be in radians.
?expressions functions besy0
?besy0
The `besy0(x)` function returns the Y0th Bessel function of its argument.
`besy0` expects its argument to be in radians.
?expressions functions besy1
?besy1
The `besy1(x)` function returns the Y1st Bessel function of its argument.
`besy1` expects its argument to be in radians.
?expressions functions ceil
?ceil
The `ceil(x)` function returns the smallest integer that is not less than its
argument. For complex numbers, `ceil` returns the smallest integer not less
than the real part of its argument.
?expressions functions cos
?cos
The `cos(x)` function returns the cosine of its argument. `cos` accepts its
argument in radians or degrees, as selected by `set angles`.
?expressions functions cosh
?cosh
The `cosh(x)` function returns the hyperbolic cosine of its argument. `cosh`
expects its argument to be in radians.
?expressions functions erf
?erf
The `erf(x)` function returns the error function of the real part of its
argument. If the argument is a complex value, the imaginary component is
ignored. See `erfc`, `inverf`, and `norm`.
?expressions functions erfc
?erfc
The `erfc(x)` function returns 1.0 - the error function of the real part of
its argument. If the argument is a complex value, the imaginary component is
ignored. See `erf`, `inverf`, and `norm`.
?expressions functions exp
?exp
The `exp(x)` function returns the exponential function of its argument (`e`
raised to the power of its argument). On some implementations (notably
suns), exp(-x) returns undefined for very large x. A user-defined function
like safe(x) = x<-100 ? 0 : exp(x) might prove useful in these cases.
?expressions functions expint
?expint
The `expint(n,x)` function returns the exponential integral of the real
part of its argument: integral from 1 to infinity of t^(-n) e^(-tx) dt.
n must be a nonnegative integer, x>=0, and either x>0 or n>1.
?expressions functions floor
?floor
The `floor(x)` function returns the largest integer not greater than its
argument. For complex numbers, `floor` returns the largest integer not
greater than the real part of its argument.
?expressions functions gamma
?gamma
The `gamma(x)` function returns the gamma function of the real part of its
argument. For integer n, gamma(n+1) = n!. If the argument is a complex
value, the imaginary component is ignored.
?expressions functions ibeta
?ibeta
The `ibeta(p,q,x)` function returns the incomplete beta function of the real
parts of its arguments. p, q > 0 and x in [0:1]. If the arguments are
complex, the imaginary components are ignored. The function is approximated by
the method of continued fractions (Abramowitz and Stegun, 1964).
The approximation is only accurate in the region x < (p-1)/(p+q-2).
?expressions functions inverf
?inverf
The `inverf(x)` function returns the inverse error function of the real part
of its argument. See `erf` and `invnorm`.
?expressions functions igamma
?igamma
The `igamma(a,x)` function returns the normalized incomplete gamma
function of the real parts of its arguments, where a > 0 and x >= 0.
The standard notation is P(a,x), e.g. Abramowitz and Stegun (6.5.1),
with limiting value of 1 as x approaches infinity. If the arguments
are complex, the imaginary components are ignored.
?expressions functions imag
?imag
The `imag(x)` function returns the imaginary part of its argument as a real
number.
?expressions functions invnorm
?invnorm
The `invnorm(x)` function returns the inverse cumulative normal (Gaussian)
distribution function of the real part of its argument. See `norm`.
?expressions functions int
?int
The `int(x)` function returns the integer part of its argument, truncated
toward zero.
?expressions functions lambertw
?lambertw
The `lambertw(x)` function returns the value of the principal branch of
Lambert's W function, which is defined by the equation (W(x)*exp(W(x))=x.
x must be a real number with x >= -exp(-1).
?expressions functions lgamma
?lgamma
The `lgamma(x)` function returns the natural logarithm of the gamma function
of the real part of its argument. If the argument is a complex value, the
imaginary component is ignored.
?expressions functions log
?log
The `log(x)` function returns the natural logarithm (base `e`) of its
argument. See `log10`.
?expressions functions log10
?log10
The `log10(x)` function returns the logarithm (base 10) of its argument.
?expressions functions norm
?norm
The `norm(x)` function returns the cumulative normal (Gaussian) distribution
function of the real part of its argument. See `invnorm`, `erf` and `erfc`.
?expressions functions rand
?rand
The `rand(x)` function returns a pseudo random number in the interval [0:1].
See `random` for more details.
?expressions functions real
?real
The `real(x)` function returns the real part of its argument.
?expressions functions sgn
?sgn
The `sgn(x)` function returns 1 if its argument is positive, -1 if its
argument is negative, and 0 if its argument is 0. If the argument is a
complex value, the imaginary component is ignored.
?expressions functions sin
?sin
The `sin(x)` function returns the sine of its argument. `sin` expects its
argument to be in radians or degrees, as selected by `set angles`.
?expressions functions sinh
?sinh
The `sinh(x)` function returns the hyperbolic sine of its argument. `sinh`
expects its argument to be in radians.
?expressions functions sqrt
?sqrt
The `sqrt(x)` function returns the square root of its argument. If the
x is a complex value, this always returns the root with positive real
part.
?expressions functions tan
?tan
The `tan(x)` function returns the tangent of its argument. `tan` expects
its argument to be in radians or degrees, as selected by `set angles`.
?expressions functions tanh
?tanh
The `tanh(x)` function returns the hyperbolic tangent of its argument. `tanh`
expects its argument to be in radians.
?expressions functions voigt
?voigt
The function `voigt(x,y)` returns an approximation to the Voigt/Faddeeva
function used in spectral analysis. The approximation is accurate to
one part in 10^4. If the libcerf routines are available, the re_w_of_z()
routine is used to provide a more accurate value.
Note that voigt(x,y) = real(faddeeva( x + y*{0,1} )).
?expressions functions cerf
?cerf
`cerf(z)` is the complex version of the error function erf(x)
?expressions functions cdawson
?cdawson
`cdawson(z)` returns Dawson's Integral evaluated for the complex argument z.
cdawson(z) = sqrt(pi)/2 * exp(-z^2) * erfi(z)
?expressions functions faddeeva
?faddeeva
The `faddeeva(z)` function returns the rescaled complex error function
faddeeva(z) = exp(-z^2) * erfc(-i*z)
This corresponds to Eqs 7.1.3 and 7.1.4 of Abramowitz and Stegun.
?expressions functions erfi
?erfi
Imaginary error function erfi(x) = -i * erf(ix)
?expressions functions VP
?VP
`VP(x,sigma,gamma)` corresponds to the Voigt profile defined by convolution of
a Gaussian G(x;sigma) with a Lorentzian L(x;gamma).
?expressions functions gprintf
`gprintf("format",x)` applies gnuplot's own format specifiers to the single
variable x and returns the resulting string. If you want standard C-language
format specifiers, you must instead use `sprintf("format",x)`.
See `format specifiers`.
?expressions functions sprintf
?sprintf
`sprintf("format",var1,var2,...)` applies standard C-language format specifiers
to multiple arguments and returns the resulting string. If you want to
use gnuplot's own format specifiers, you must instead call `gprintf()`.
For information on sprintf format specifiers, please see standard C-language
documentation or the unix sprintf man page.
?expressions functions strlen
?strlen
`strlen("string")` returns the number of characters in a string taking into
account the current encoding. If the current encoding supports multibyte
characters (SJIS UTF8), this may be less than the number of bytes in the string.
If the string contains multibyte UTF8 characters but the current encoding is set
set to something other than UTF8, strlen("utf8string") will return a value that
is larger than the actual number of characters.
?expressions functions strstrt
?strstrt
`strstrt("string","key")` searches for the character string "key" in "string"
and returns the index to the first character of "key". If "key" is not found,
returns 0. Similar to C library function strstr except that it returns an
index rather than a string pointer. strstrt("hayneedlestack","needle") = 4.
?expressions functions substr
?substr
`substr("string",beg,end)` returns the substring consisting of characters
beg through end of the original string. This is exactly equivalent to the
expression "string"[beg:end] except that you do not have the option of
omitting beg or end.
?expressions functions strftime
?strftime
`strftime("timeformat",t)` applies the timeformat specifiers to the time t
given in seconds since the year 1970.
See `time_specifiers` and `strptime`.
?expressions functions strptime
?strptime
`strptime("timeformat",s)` reads the time from the string s using the
timeformat specifiers and converts it into seconds since the year 1970.
See `time_specifiers` and `strftime`.
?expressions functions system
`system("command")` executes "command" using the standard shell and returns
the resulting character stream from stdout as string variable.
One optional trailing newline is ignored.
This can be used to import external functions into gnuplot scripts using
'f(x) = real(system(sprintf("somecommand %f", x)))'.
`word("string",n)` returns the nth word in string. For example,
`word("one two three",2)` returns the string "two".
`words("string")` returns the number of words in string. For example,
`words(" a b c d")` returns 4.
?expressions functions column
?column
`column(x)` may be used only as part of a plot, splot, or stats command.
It evaluates to the numerical value of the content of column x.
See `plot datafile using`.
?expressions functions columnhead
?columnhead
`columnhead(x)` may only be used as part of a plot, splot, or stats command.
It evaluates to a string containing the content of column x in the first line
of a data file. See `plot datafile using`.
?expressions functions exists
?exists
The argument to `exists()` is a string constant or a string variable;
if the string contains the name of a defined variable, the function returns 1.
Otherwise the function returns 0.
?expressions functions hsv2rgb
?hsv2rgb
?hsv
The `hsv2rgb(h,s,v)` function converts HSV (Hue/Saturation/Value) triplet
to an equivalent RGB value.
?expressions functions stringcolumn
?stringcolumn
?expressions functions strcol
?strcol
`stringcolumn(x)` may be used only in expressions as part of `using` manipulations
to fits or datafile plots. It returns the content of column x as a string variable.
`strcol(x)` is shorthand for `stringcolumn(x)`.
See `plot datafile using`.
?expressions functions timecolumn
?timecolumn
`timecolumn(N,"timeformat")` may be used only in expressions as part of `using`
manipulations to fits or datafile plots. See `plot datafile using`.
It reads string data starting at column N as a time/date value and uses "timeformat"
to interpret this as "seconds since the epoch" to millisecond precision.
Note: prior to version 5 this function took only a single parameter and worked only
for columns that contained purely an axis coordinate.
?expressions functions tm_hour
?tm_hour
The `tm_hour(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the hour (an integer in the range 0--23) as a real.
?expressions functions tm_mday
?tm_mday
The `tm_mday(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the day of the month (an integer in the range 1--31)
as a real.
?expressions functions tm_min
?tm_min
The `tm_min(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the minute (an integer in the range 0--59) as a real.
?expressions functions tm_mon
?tm_mon
The `tm_mon(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the month (an integer in the range 0--11) as a real.
?expressions functions tm_sec
?tm_sec
The `tm_sec(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the second (an integer in the range 0--59) as a real.
?expressions functions tm_wday
?tm_wday
The `tm_wday(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the day of the week (an integer in the range 0--6) as
a real.
?expressions functions tm_yday
?tm_yday
The `tm_yday(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the day of the year (an integer in the range 1--366)
as a real.
?expressions functions tm_year
?tm_year
The `tm_year(x)` function interprets its argument as a time, in seconds from
1 Jan 1970. It returns the year (an integer) as a real.
?expressions functions time
?time
The `time(x)` function returns the current system time. This value can be
converted to a date string with the `strftime` function, or it can be used
in conjunction with `timecolumn` to generate relative time/date plots.
The type of the argument determines what is returned. If the argument is an
integer, time() returns the current time as an integer, in seconds from
1 Jan 1970. If the argument is real (or complex), the result is real as well.
If the argument is a string, it is assumed to be a format string,
and it is passed to `strftime` to provide a formatted time string.
?expressions functions valid
?valid
`valid(x)` may be used only in expressions as part of `using` manipulations
to fits or datafile plots. See `plot datafile using`.
?elliptic integrals
The `EllipticK(k)` function returns the complete elliptic integral of the first
kind, i.e. the definite integral between 0 and pi/2 of the function
`(1-(k*sin(p))**2)**(-0.5)`. The domain of `k` is -1 to 1 (exclusive).
The `EllipticE(k)` function returns the complete elliptic integral of the
second kind, i.e. the definite integral between 0 and pi/2 of the function
`(1-(k*sin(p))**2)**0.5`. The domain of `k` is -1 to 1 (inclusive).
The `EllipticPi(n,k)` function returns the complete elliptic integral of the
third kind, i.e. the definite integral between 0 and pi/2 of the function
`(1-(k*sin(p))**2)**(-0.5)/(1-n*sin(p)**2)`. The parameter `n` must be less
than 1, while `k` must lie between -1 and 1 (exclusive). Note that by
definition EllipticPi(0,k) == EllipticK(k) for all possible values of `k`.
?expressions random
?random
The function `rand()` produces a sequence of pseudo-random numbers between
0 and 1 using an algorithm from P. L'Ecuyer and S. Cote, "Implementing a
random number package with splitting facilities", ACM Transactions on
Mathematical Software, 17:98-111 (1991).
rand(0) returns a pseudo random number in the interval [0:1]
generated from the current value of two internal
32-bit seeds.
rand(-1) resets both seeds to a standard value.
rand(x) for integer 0 < x < 2^31-1 sets both internal seeds
to x.
rand({x,y}) for integer 0 < x,y < 2^31-1 sets seed1 to x and
seed2 to y.
?expressions functions value
?value
B = value("A") is effectively the same as B = A, where A is the name of a
user-defined variable. This is useful when the name of the variable is itself
held in a string variable. See `user-defined variables`. It also allows you to
read the name of a variable from a data file. If the argument is a numerical
expression, value() returns the value of that expression. If the argument is a
string that does not correspond to a currently defined variable,
value() returns NaN.
?expressions functions word
?expressions functions words
?words
?word
`word("string",n)` returns the nth word in string. For example,
`word("one two three",2)` returns the string "two".
`words("string")` returns the number of words in string. For example,
`words(" a b c d")` returns 4.
The `word` and `words` functions provide limited support for quoted strings,
both single and double quotes can be used:
print words("\"double quotes\" or 'single quotes'") # 3
A starting quote must either be preceeded by a white space, or start the
string. This means that apostrophes in the middle or at the end of words are
considered as parts of the respective word:
print words("Alexis' phone doesn't work") # 4
Escaping quote characters is not supported. If you want to keep certain quotes,
the respective section must be surrounded by the other kind of quotes:
s = "Keep \"'single quotes'\" or '\"double quotes\"'"
print word(s, 2) # 'single quotes'
print word(s, 4) # "double quotes"
Note, that in this last example the escaped quotes are necessary only for the
string definition.
?expressions operators
?operators
The operators in `gnuplot` are the same as the corresponding operators in the
C programming language, except that all operators accept integer, real, and
complex arguments, unless otherwise noted. The ** operator (exponentiation)
is supported, as in FORTRAN.
Parentheses may be used to change order of evaluation.
?expressions operators unary
?operators unary
?unary
The following is a list of all the unary operators and their usages:
Symbol Example Explanation
- -a unary minus
+ +a unary plus (no-operation)
~ ~a * one's complement
! !a * logical negation
! a! * factorial
$ $3 * call arg/column during `using` manipulation
|| |A| cardinality of array A
(*) Starred explanations indicate that the operator requires an integer
argument.
Operator precedence is the same as in Fortran and C. As in those languages,
parentheses may be used to change the order of operation. Thus -2**2 = -4,
but (-2)**2 = 4.
The factorial operator returns a real number to allow a greater range.
?expressions operators binary
?operators binary
The following is a list of all the binary operators and their usages:
Symbol Example Explanation
** a**b exponentiation
* a*b multiplication
/ a/b division
% a%b * modulo
+ a+b addition
- a-b subtraction
== a==b equality
!= a!=b inequality
< a<b less than
<= a<=b less than or equal to
> a>b greater than
>= a>=b greater than or equal to
<< 0xff<<1 left shift unsigned
>> 0xff>>2 right shift unsigned
& a&b * bitwise AND
^ a^b * bitwise exclusive OR
| a|b * bitwise inclusive OR
&& a&&b * logical AND
|| a||b * logical OR
= a = b assignment
, (a,b) serial evaluation
. A.B string concatenation
eq A eq B string equality
ne A ne B string inequality
(*) Starred explanations indicate that the operator requires integer
arguments.
Capital letters A and B indicate that the operator requires string arguments.
Logical AND (&&) and OR (||) short-circuit the way they do in C. That is,
the second `&&` operand is not evaluated if the first is false; the second
`||` operand is not evaluated if the first is true.
Serial evaluation occurs only in parentheses and is guaranteed to proceed
in left to right order. The value of the rightmost subexpression is returned.
?expressions operators ternary
?operators ternary
?ternary
There is a single ternary operator:
Symbol Example Explanation
?: a?b:c ternary operation
The ternary operator behaves as it does in C. The first argument (a), which
must be an integer, is evaluated. If it is true (non-zero), the second
argument (b) is evaluated and returned; otherwise the third argument (c) is
evaluated and returned.
The ternary operator is very useful both in constructing piecewise functions
and in plotting points only when certain conditions are met.
Examples:
Plot a function that is to equal sin(x) for 0 <= x < 1, 1/x for 1 <= x < 2,
and undefined elsewhere:
f(x) = 0<=x && x<1 ? sin(x) : 1<=x && x<2 ? 1/x : 1/0
plot f(x)
Note that `gnuplot` quietly ignores undefined values, so the final branch of
the function (1/0) will produce no plottable points. Note also that f(x)
will be plotted as a continuous function across the discontinuity if a line
style is used. To plot it discontinuously, create separate functions for the
two pieces. (Parametric functions are also useful for this purpose.)
For data in a file, plot the average of the data in columns 2 and 3 against
the datum in column 1, but only if the datum in column 4 is non-negative:
plot 'file' using 1:( $4<0 ? 1/0 : ($2+$3)/2 )
For an explanation of the `using` syntax, please see `plot datafile using`.
?expressions operators summation
?operators summation
?summation
A summation expression has the form
sum [<var> = <start> : <end>] <expression>
<var> is treated as an integer variable that takes on successive integral
values from <start> to <end>. For each of these, the current value of
<expression> is added to a running total whose final value becomes the value
of the summation expression.
Examples:
print sum [i=1:10] i
55.
# Equivalent to plot 'data' using 1:($2+$3+$4+$5+$6+...)
plot 'data' using 1 : (sum [col=2:MAXCOL] column(col))
It is not necessary that <expression> contain the variable <var>.
Although <start> and <end> can be specified as variables or expressions,
their value cannot be changed dynamically as a side-effect of carrying
out the summation. If <end> is less than <start> then the value of the
summation is zero.
?expressions gnuplot-defined
?gnuplot-defined
?gnuplot-defined variables
?GPVAL
?gpval
Gnuplot maintains a number of read-only variables that reflect the current
internal state of the program and the most recent plot. These variables begin
with the prefix "GPVAL_".
Examples include GPVAL_TERM, GPVAL_X_MIN, GPVAL_X_MAX, GPVAL_Y_MIN.
Type `show variables all` to display the complete list and current values.
Values related to axes parameters (ranges, log base) are values used during the
last plot, not those currently `set`.
Example: To calculate the fractional screen coordinates of the point [X,Y]
GRAPH_X = (X - GPVAL_X_MIN) / (GPVAL_X_MAX - GPVAL_X_MIN)
GRAPH_Y = (Y - GPVAL_Y_MIN) / (GPVAL_Y_MAX - GPVAL_Y_MIN)
SCREEN_X = GPVAL_TERM_XMIN + GRAPH_X * (GPVAL_TERM_XMAX - GPVAL_TERM_XMIN)
SCREEN_Y = GPVAL_TERM_YMIN + GRAPH_Y * (GPVAL_TERM_YMAX - GPVAL_TERM_YMIN)
FRAC_X = SCREEN_X * GPVAL_TERM_SCALE / GPVAL_TERM_XSIZE
FRAC_Y = SCREEN_Y * GPVAL_TERM_SCALE / GPVAL_TERM_YSIZE
The read-only variable GPVAL_ERRNO is set to a non-zero value if any gnuplot
command terminates early due to an error. The most recent error message is
stored in the string variable GPVAL_ERRMSG. Both GPVAL_ERRNO and GPVAL_ERRMSG
can be cleared using the command `reset errors`.
Interactive terminals with `mouse` functionality maintain read-only variables
with the prefix "MOUSE_". See `mouse variables` for details.
The `fit` mechanism uses several variables with names that begin "FIT_". It
is safest to avoid using such names. When using `set fit errorvariables`, the
error for each fitted parameter will be stored in a variable named like the
parameter, but with "_err" appended. See the documentation on `fit` and
`set fit` for details.
See `user-defined variables`, `reset errors`, `mouse variables`, and `fit`.
?expressions user-defined
?user-defined variables
?user-defined
?variables
New user-defined variables and functions of one through twelve variables may
be declared and used anywhere, including on the `plot` command itself.
User-defined function syntax:
<func-name>( <dummy1> {,<dummy2>} ... {,<dummy12>} ) = <expression>
where <expression> is defined in terms of <dummy1> through <dummy12>.
User-defined variable syntax:
<variable-name> = <constant-expression>
Examples:
w = 2
q = floor(tan(pi/2 - 0.1))
f(x) = sin(w*x)
sinc(x) = sin(pi*x)/(pi*x)
delta(t) = (t == 0)
ramp(t) = (t > 0) ? t : 0
min(a,b) = (a < b) ? a : b
comb(n,k) = n!/(k!*(n-k)!)
len3d(x,y,z) = sqrt(x*x+y*y+z*z)
plot f(x) = sin(x*a), a = 0.2, f(x), a = 0.4, f(x)
file = "mydata.inp"
file(n) = sprintf("run_%d.dat",n)
The final two examples illustrate a user-defined string variable and a
user-defined string function.
Note that the variables `pi` (3.14159...) and `NaN` (IEEE "Not a Number") are
already defined. You can redefine these to something else if you really need
to. The original values can be recovered by setting:
NaN = GPVAL_NaN
pi = GPVAL_pi
Other variables may be defined under various gnuplot operations like mousing in
interactive terminals or fitting; see `gnuplot-defined variables` for details.
You can check for existence of a given variable V by the exists("V")
expression. For example
a = 10
if (exists("a")) print "a is defined"
if (!exists("b")) print "b is not defined"
Valid names are the same as in most programming languages: they must begin
with a letter, but subsequent characters may be letters, digits, or "_".
Each function definition is made available as a special string-valued
variable with the prefix 'GPFUN_'.
Example:
set label GPFUN_sinc at graph .05,.95
See `show functions`, `functions`, `gnuplot-defined variables`, `macros`,
`value`.
?arrays
?cardinality
Arrays are implemented as indexed lists of user variables. The elements in an
array are not limited to a single type of variable. Arrays must be created
explicitly before being referenced. The size of an array cannot be changed
after creation. All elements are initially undefined. In most places an array
element can be used instead of a named user variable.
The cardinality (number of elements) of array A is given by the expression |A|.
Example:
array A[6]
A[1] = 1
A[2] = 2.0
A[3] = {3.0, 3.0}
A[4] = "four"
A[6] = A[2]**3
array B[6] = [ 1, 2.0, A[3], "four", , B[2]**3 ]
do for [i=1:6] { print A[i], B[i] }
1 1
2.0 2.0
{3.0, 3.0} {3.0, 3.0}
four four
<undefined> <undefined>
8.0 8.0
Note: Arrays and variables share the same namespace. For example, assignment
of a string variable named FOO will destroy any previously created array with
name FOO.
The name of an array can be used in a `plot`, `splot`, `fit`, or `stats`
command. This is equivalent to providing a file in which column 1 holds the
array index (from 1 to size) and column 2 holds the value of A[i].
Example:
array A[200]
do for [i=1:200] { A[i] = sin(i * pi/100.) }
plot A title "sin(x) in centiradians"
To preserve the imaginary component of complex array values when plotting,
the value must be referenced as A[$1] rather than $2. For example
plot A using (F1(real(A[$1])) : (F2(imag(A[$1]))
?fonts
Gnuplot does not provide any fonts of its own. It relies on external font
handling, the details of which unfortunately vary from one terminal type to
another. Brief documentation of font mechanisms that apply to more than one
terminal type is given here. For information on font use by other individual
terminals, see the documentation for that terminal.
Although it is possible to include non-alphabetic symbols by temporarily
switching to a special font, e.g. the Adobe Symbol font, the preferred method
is now to specify the unicode entry point for the desired symbols using their
UTF-8 encoding. See `encoding` and `locale`.
?fonts cairo
These terminals find and access fonts using the external fontconfig tool set.
Please see the
It is usually sufficient in gnuplot to request a font by a generic name and
size, letting fontconfig substitute a similar font if necessary. The following
will probably all work:
set term pdfcairo font "sans,12"
set term pdfcairo font "Times,12"
set term pdfcairo font "Times-New-Roman,12"
?gd
?fonts gd
Font handling for the png, gif, jpeg, and sixelgd terminals is done by the
library libgd. Five basic fonts are provided directly by libgd. These are
`tiny` (5x8 pixels), `small` (6x12 pixels), `medium`, (7x13 Bold), `large`
(8x16) or `giant` (9x15 pixels). These fonts cannot be scaled or rotated.
Use one of these keywords instead of the `font` keyword. E.g.
set term png tiny
On most systems libgd also provides access to Adobe Type 1 fonts (*.pfa) and
TrueType fonts (*.ttf). You must give the name of the font file, not the name
of the font inside it, in the form "<face> {,<pointsize>}".
<face> is either the full pathname to the font file, or the first part of a
filename in one of the directories listed in the GDFONTPATH environmental
variable. That is, 'set term png font "Face"' will look for a font file named
either <somedirectory>/Face.ttf or <somedirectory>/Face.pfa.
For example, if GDFONTPATH contains `/usr/local/fonts/ttf:/usr/local/fonts/pfa`
then the following pairs of commands are equivalent
set term png font "arial"
set term png font "/usr/local/fonts/ttf/arial.ttf"
set term png font "Helvetica"
set term png font "/usr/local/fonts/pfa/Helvetica.pfa"
To request a default font size at the same time:
set term png font "arial,11"
Both TrueType and Adobe Type 1 fonts are fully scalable and rotatable.
If no specific font is requested in the "set term" command, gnuplot checks
the environmental variable GNUPLOT_DEFAULT_GDFONT to see if there is a
preferred default font.
?fonts postscript
PostScript font handling is done by the printer or viewing program.
Gnuplot can create valid PostScript or encapsulated PostScript (*.eps) even if
no fonts at all are installed on your computer. Gnuplot simply refers to the
font by name in the output file, and assumes that the printer or viewing
program will know how to find or approximate a font by that name.
All PostScript printers or viewers should know about the standard set of Adobe
fonts `Times-Roman`, `Helvetica`, `Courier`, and `Symbol`. It is likely that
many additional fonts are also available, but the specific set depends on your
system or printer configuration. Gnuplot does not know or care about this;
the output *.ps or *.eps files that it creates will simply refer to whatever
font names you request.
Thus
set term postscript eps font "Times-Roman,12"
will produce output that is suitable for all printers and viewers.
On the other hand
set term postscript eps font "Garamond-Premier-Pro-Italic"
will produce an output file that contains valid PostScript, but since it
refers to a specialized font, only some printers or viewers will be able to
display the specific font that was requested. Most will substitute a
different font.
However, it is possible to embed a specific font in the output file so that
all printers will be able to use it. This requires that the a suitable font
description file is available on your system. Note that some font files require
specific licensing if they are to be embedded in this way.
See `postscript fontfile` for more detailed description and examples.
?glossary
Throughout this document an attempt has been made to maintain consistency of
nomenclature. This cannot be wholly successful because as `gnuplot` has
evolved over time, certain command and keyword names have been adopted that
preclude such perfection. This section contains explanations of the way
some of these terms are used.
A "page" or "screen" or "canvas" is the entire area addressable by `gnuplot`.
On a desktop it is a full window; on a plotter, it is a single sheet of paper;
in svga mode it is the full monitor screen.
A screen may contain one or more "plots". A plot is defined by an abscissa
and an ordinate, although these need not actually appear on it, as well as
the margins and any text written therein.
A plot contains one "graph". A graph is defined by an abscissa and an
ordinate, although these need not actually appear on it.
A graph may contain one or more "lines". A line is a single function or
data set. "Line" is also a plotting style. The word will also be used in
sense "a line of text". Presumably the context will remove any ambiguity.
The lines on a graph may have individual names. These may be listed
together with a sample of the plotting style used to represent them in
the "key", sometimes also called the "legend".
The word "title" occurs with multiple meanings in `gnuplot`. In this
document, it will always be preceded by the adjective "plot", "line", or
"key" to differentiate among them.
A 2D graph may have up to four labeled `axes`. The names of the four axes
are "x" for the axis along the bottom border of the plot, "y" for the axis
along the left border, "x2" for the top border, and "y2" for the right border.
See `axes`.
A 3D graph may have up to three labeled `axes` -- "x", "y" and "z". It is
not possible to say where on the graph any particular axis will fall because
you can change the direction from which the graph is seen with `set view`.
When discussing data files, the term "record" will be resurrected and used
to denote a single line of text in the file, that is, the characters between
newline or end-of-record characters. A "point" is the datum extracted from
a single record. A "block" of data is a set of consecutive records delimited
by blank records. A line, when referred to in the context of a data file,
is a subset of a block. Note that the term "data block" may also be used to
refer to a named block inline data (see `datablocks`).
?inline data
?inline
?datablocks
There are two mechanisms for embedding data into a stream of gnuplot commands.
If the special filename '-' appears in a plot command, then the lines
immediately following the plot command are interpreted as inline data.
See `special-filenames`. Data provided in this way can only be used once, by
the plot command it follows.
The second mechanism defines a named data block as a here-document. The named
data is persistent and may be referred to by more than one plot command.
Example:
$Mydata << EOD
11 22 33 first line of data
44 55 66 second line of data
# comments work just as in a data file
77 88 99
EOD
stats $Mydata using 1:3
plot $Mydata using 1:3 with points, $Mydata using 1:2 with impulses
Data block names must begin with a $ character, which distinguishes them from
other types of persistent variables. The end-of-data delimiter (EOD in the
example) may be any sequence of alphanumeric characters.
The storage associated with named data blocks can be released using `undefine`
command. `undefine $*` frees all named data blocks at once.
?iteration
?iterate
Version 4.6 of gnuplot introduced command iteration and block-structured
if/else/while/do constructs. See `if`, `while`, and `do`.
Simple iteration is possible inside `plot` or `set` commands.
See `plot for`. General iteration spanning multiple
commands is possible using a block construct as shown below.
For a related new feature, see the `summation` expression type.
Here is an example using several of these new syntax features:
set multiplot layout 2,2
fourier(k, x) = sin(3./2*k)/k * 2./3*cos(k*x)
do for [power = 0:3] {
TERMS = 10**power
set title sprintf("%g term Fourier series",TERMS)
plot 0.5 + sum [k=1:TERMS] fourier(k,x) notitle
}
unset multiplot
Iteration is controlled by an iteration specifier with syntax
for [<var> in "string of N elements"]
or
for [<var> = <start> : <end> { : <increment> }]
In the first case <var> is a string variable that successively evaluates to
single-word substrings 1 to N of the string in the iteration specifier.
In the second case <start>, <end>, and <increment> are integers or integer
expressions.
?scope
With one exception, gnuplot variables are global.
There is a single, persistent, list of active variables indexed by name.
Assignment to a variable creates or replaces an entry in that list.
The only way to remove a variable from that list is the `undefine` command.
The single exception to this is the variable used in an iteration specifier.
The scope of the iteration variable is private to that iteration.
You cannot permanently change the value of the iteration variable inside the
iterated clause. If the iteration variable has a value prior to iteration,
that value will be retained or restored at the end of the iteration.
For example, the following commands will print 1 2 3 4 5 6 7 8 9 10 A.
i = "A"
do for [i=1:10] { print i; i=10; }
print i
?linetypes
?colors
In older gnuplot versions, each terminal type provided a set of distinct
"linetypes" that could differ in color, in thickness, in dot/dash pattern, or
in some combination of color and dot/dash. These colors and patterns were not
guaranteed to be consistent across different terminal types although most
used the color sequence red/green/blue/magenta/cyan/yellow. You can select
this old behaviour via the command `set colorsequence classic`, but by default
gnuplot version 5 uses a terminal-independent sequence of 8 colors.
You can further customize the sequence of linetype properties interactively or
in an initialization file. See `set linetype`. Several sample initialization
files are provided in the distribution package.
The current linetype properties for a particular terminal can be previewed by
issuing the `test` command after setting the terminal type.
Successive functions or datafiles plotted by a single command will be assigned
successive linetypes in the current default sequence. You can override this
for any individual function, datafile, or plot element by giving explicit line
prooperties in the plot command.
Examples:
plot "foo", "bar" # plot two files using linetypes 1, 2
plot sin(x) linetype 4 # use linetype color 4
In general, colors can be specified using named colors, rgb (red, green, blue)
components, hsv (hue, saturation, value) components, or a coordinate along the
current pm3d palette.
Examples:
plot sin(x) lt rgb "violet" # one of gnuplot's named colors
plot sin(x) lt rgb "#FF00FF" # explicit RGB triple in hexadecimal
plot sin(x) lt palette cb -45 # whatever color corresponds to -45
# in the current cbrange of the palette
plot sin(x) lt palette frac 0.3 # fractional value along the palette
See `colorspec`, `show colornames`, `hsv`, `set palette`, `cbrange`.
See also `set monochrome`.
Linetypes also have an associated dot-dash pattern although not all terminal
types are capable of using it. Gnuplot version 5 allows you to specify the
dot-dash pattern independent of the line color. See `dashtype`.
?colorspec
?rgbcolor
?lc
?linecolor
?tc
?textcolor
Many commands allow you to specify a linetype with an explicit color.
Syntax:
... {linecolor | lc} {"colorname" | <colorspec> | <n>}
... {textcolor | tc} {<colorspec> | {linetype | lt} <n>}
where <colorspec> has one of the following forms:
rgbcolor "colorname" # e.g. "blue"
rgbcolor "0xRRGGBB" # string containing hexadecimal constant
rgbcolor "0xAARRGGBB" # string containing hexadecimal constant
rgbcolor "#RRGGBB" # string containing hexadecimal in x11 format
rgbcolor "#AARRGGBB" # string containing hexadecimal in x11 format
rgbcolor <integer val> # integer value representing AARRGGBB
rgbcolor variable # integer value is read from input file
palette frac <val> # <val> runs from 0 to 1
palette cb <value> # <val> lies within cbrange
palette z
variable # color index is read from input file
bgnd # background color
black
The "<n>" is the linetype number the color of which is used, see `test`.
"colorname" refers to one of the color names built in to gnuplot. For a list
of the available names, see `show colornames`.
Hexadecimal constants can be given in quotes as "#RRGGBB" or "0xRRGGBB", where
RRGGBB represents the red, green, and blue components of the color and must be
between 00 and FF. For example, magenta = full-scale red + full-scale blue
could be represented by "0xFF00FF", which is the hexadecimal representation of
(255 << 16) + (0 << 8) + (255).
"#AARRGGBB" represents an RGB color with an alpha channel (transparency)
value in the high bits. An alpha value of 0 represents a fully opaque color;
i.e., "#00RRGGBB" is the same as "#RRGGBB". An alpha value of 255 (FF)
represents full transparency. `Note`: This convention for the alpha channel
is backwards from that used by the "with rgbalpha" image plot mode in earlier
versions of gnuplot.
The color palette is a linear gradient of colors that smoothly maps a
single numerical value onto a particular color. Two such mappings are always
in effect. `palette frac` maps a fractional value between 0 and 1 onto the
full range of the color palette. `palette cb` maps the range of the color
axis onto the same palette. See `set cbrange`. See also `set colorbox`.
You can use either of these to select a constant color from the current
palette.
"palette z" maps the z value of each plot segment or plot element into the
cbrange mapping of the palette. This allows smoothly-varying color along a
3d line or surface. It also allows coloring 2D plots by palette values read
from an extra column of data (not all 2D plot styles allow an extra column).
There are two special color specifiers: `bgnd` for background color and `black`.
?background
?bgnd
Most terminals allow you to set an explicit background color for the plot.
The special linetype `bgnd` will draw in this color, and `bgnd` is also
recognized as a color.
Examples:
# This will erase a section of the canvas by writing over it in the
# background color
set term wxt background rgb "gray75"
set object 1 rectangle from x0,y0 to x1,y1 fillstyle solid fillcolor bgnd
# This will draw an "invisible" line along the x axis
plot 0 lt bgnd
?linecolor variable
?lc variable
?textcolor variable
?tc variable
?variable linecolor
`lc variable` tells the program to use the value read from one column of the
input data as a linetype index, and use the color belonging to that linetype.
This requires a corresponding additional column in the `using` specifier.
Text colors can be set similarly using `tc variable`.
Examples:
# Use the third column of data to assign colors to individual points
plot 'data' using 1:2:3 with points lc variable
# A single data file may contain multiple sets of data, separated by two
# blank lines. Each data set is assigned as index value (see `index`)
# that can be retrieved via the `using` specifier `column(-2)`.
# See `pseudocolumns`. This example uses to value in column -2 to
# draw each data set in a different line color.
plot 'data' using 1:2:(column(-2)) with lines lc variable
?rgbcolor variable
?lc rgbcolor variable
?tc rgbcolor variable
?variable rgbcolor
?variable textcolor
You can assign a separate color for each data point, line segment, or label in
your plot. `lc rgbcolor variable` tells the program to read RGB color
information for each line in the data file. This requires a corresponding
additional column in the `using` specifier. The extra column is interpreted as
a 24-bit packed RGB triple. If the value is provided directly in the data file
it is easiest to give it as a hexidecimal value (see `rgbcolor`).
Alternatively, the `using` specifier can contain an expression that evaluates
to a 24-bit RGB color as in the example below.
Text colors are similarly set using `tc rgbcolor variable`.
Example:
# Place colored points in 3D at the x,y,z coordinates corresponding to
# their red, green, and blue components
rgb(r,g,b) = 65536 * int(r) + 256 * int(g) + int(b)
splot "data" using 1:2:3:(rgb($1,$2,$3)) with points lc rgb variable
?dashtype
In gnuplot version 5 the dash pattern (`dashtype`) is a separate property
associated with each line, analogous to `linecolor` or `linewidth`. It is not
necessary to place the current terminal in a special mode just to draw dashed
lines. I.e. the command `set term <termname> {solid|dashed}` is now ignored.
If backwards compatibility with old scripts written for version 4 is required,
the following lines can be used instead:
if (GPVAL_VERSION >= 5.0) set for [i=1:9] linetype i dashtype i
if (GPVAL_VERSION < 5.0) set termoption dashed
All lines have the property `dashtype solid` unless you specify otherwise.
You can change the default for a particular linetype using the command
`set linetype` so that it affects all subsequent commands, or you can include
the desired dashtype as part of the `plot` or other command.
Syntax:
dashtype N # predefined dashtype invoked by number
dashtype "pattern" # string containing a combination of the characters
# dot (.) hyphen (-) underscore(_) and space.
dashtype (s1,e1,s2,e2,s3,e3,s4,e4) # dash pattern specified by 1 to 4
# numerical pairs <solid length>, <emptyspace length>
Example:
# Two functions using linetype 1 but distinguished by dashtype
plot f1(x) with lines lt 1 dt solid, f2(x) with lines lt 1 dt 3
Some terminals support user-defined dash patterns in addition to whatever
set of predefined dash patterns they offer.
Examples:
plot f(x) dt 3 # use terminal-specific dash pattern 3
plot f(x) dt ".. " # construct a dash pattern on the spot
plot f(x) dt (2,5,2,15) # numerical representation of the same pattern
set dashtype 11 (2,4,4,7) # define new dashtype to be called by index
plot f(x) dt 11 # plot using our new dashtype
If you specify a dash pattern using a string the program will convert this to
a sequence of <solid>,<empty> pairs. Dot "." becomes (2,5), dash "-" becomes
(10,10), underscore "_" becomes (20,10), and each space character " " adds 10
to the previous <empty> value. The command `show dashtype` will show both the
original string and the converted numerical sequence.
?linestyles vs linetypes
A `linestyle` is a temporary association of properties linecolor, linewidth,
dashtype, and pointtype. It is defined using the command `set style line`.
Once you have defined a linestyle, you can use it in a plot command to control
the appearance of one or more plot elements. In other words, it is just like
a linetype except for its lifetime. Whereas `linetypes` are permanent (they
last until you explicitly redefine them), `linestyles` last until the next
reset of the graphics state.
Examples:
# define a new line style with terminal-independent color cyan,
# linewidth 3, and associated point type 6 (a circle with a dot in it).
set style line 5 lt rgb "cyan" lw 3 pt 6
plot sin(x) with linespoints ls 5 # user-defined line style 5
?layers
?behind
?front
?back
A gnuplot plot is built up by drawing its various components in a fixed order.
This order can be modified by assigning some components to a specific layer
using the keywords `behind`, `back`, or `front`. For example, to replace the
background color of the plot area you could define a colored rectangle with the
attribute `behind`.
set object 1 rectangle from graph 0,0 to graph 1,1 fc rgb "gray" behind
The order of drawing is
behind
back
the plot itself
the plot legend (`key`)
front
Within each layer elements are drawn in the order
objects (rectangles, circles, ellipses, polygons) in numerical order
labels in numerical order
arrows in numerical order
In the case of multiple plots on a single page (multiplot mode) this order
applies separately to each component plot, not to the multiplot as a whole.
?mouse input
Many terminals allow interaction with the current plot using the mouse. Some
also support the definition of hotkeys to activate pre-defined functions by
hitting a single key while the mouse focus is in the active plot window.
It is even possible to combine mouse input with `batch` command scripts, by
invoking the command `pause mouse` and then using the mouse variables returned
by mouse clicking as parameters for subsequent scripted actions.
See `bind` and `mouse variables`. See also the command `set mouse`.
?commands bind
?hotkey
?hotkeys
?bind
Syntax:
bind {allwindows} [<key-sequence>] ["<gnuplot commands>"]
bind <key-sequence> ""
reset bind
The `bind` allows defining or redefining a hotkey, i.e. a sequence of gnuplot
commands which will be executed when a certain key or key sequence is pressed
while the driver's window has the input focus. Note that `bind` is only
available if gnuplot was compiled with `mouse` support and it is used by all
mouse-capable terminals. A user-specified binding supersedes any builtin
bindings, except that <space> and 'q' cannot normally be rebound. For an
exception, see `bind space`.
Only mouse button 1 can be bound, and only for 2D plots.
You get the list of all hotkeys by typing `show bind` or `bind` or by typing
the hotkey 'h' in the graph window.
Key bindings are restored to their default state by `reset bind`.
Note that multikey-bindings with modifiers must be given in quotes.
Normally hotkeys are only recognized when the currently active plot window
has focus. `bind allwindows <key> ...` (short form: `bind all <key> ...`)
causes the binding for <key> to apply to all gnuplot plot windows, active
or not. In this case gnuplot variable MOUSE_KEY_WINDOW is set to the ID
of the originating window, and may be used by the bound command.
Examples:
- set bindings:
bind a "replot"
bind "ctrl-a" "plot x*x"
bind "ctrl-alt-a" 'print "great"'
bind Home "set view 60,30; replot"
bind all Home 'print "This is window ",MOUSE_KEY_WINDOW'
- show bindings:
bind "ctrl-a" # shows the binding for ctrl-a
bind # shows all bindings
show bind # show all bindings
- remove bindings:
bind "ctrl-alt-a" "" # removes binding for ctrl-alt-a
(note that builtins cannot be removed)
reset bind # installs default (builtin) bindings
- bind a key to toggle something:
v=0
bind "ctrl-r" "v=v+1;if(v%2)set term x11 noraise; else set term x11 raise"
Modifiers (ctrl / alt) are case insensitive, keys not:
ctrl-alt-a == CtRl-alT-a
ctrl-alt-a != ctrl-alt-A
List of modifiers (alt == meta):
ctrl, alt, shift (only valid for Button1)
List of supported special keys:
"BackSpace", "Tab", "Linefeed", "Clear", "Return", "Pause", "Scroll_Lock",
"Sys_Req", "Escape", "Delete", "Home", "Left", "Up", "Right", "Down",
"PageUp", "PageDown", "End", "Begin",
"KP_Space", "KP_Tab", "KP_Enter", "KP_F1", "KP_F2", "KP_F3", "KP_F4",
"KP_Home", "KP_Left", "KP_Up", "KP_Right", "KP_Down", "KP_PageUp",
"KP_PageDown", "KP_End", "KP_Begin", "KP_Insert", "KP_Delete", "KP_Equal",
"KP_Multiply", "KP_Add", "KP_Separator", "KP_Subtract", "KP_Decimal",
"KP_Divide",
"KP_1" - "KP_9", "F1" - "F12"
The following are window events rather than actual keys
"Button1" "Close"
See also help for `mouse`.
?commands bind space
?bind space
If gnuplot was built with configuration option --enable-raise-console, then
typing <space> in the plot window raises gnuplot's command window. This hotkey
can be changed to ctrl-space by starting gnuplot as 'gnuplot -ctrlq', or by
setting the XResource 'gnuplot*ctrlq'. See `x11 command-line-options`.
?mouse variables
When `mousing` is active, clicking in the active window will set several user
variables that can be accessed from the gnuplot command line. The coordinates
of the mouse at the time of the click are stored in MOUSE_X MOUSE_Y MOUSE_X2
and MOUSE_Y2. The mouse button clicked, and any meta-keys active at that time,
are stored in MOUSE_BUTTON MOUSE_SHIFT MOUSE_ALT and MOUSE_CTRL. These
variables are set to undefined at the start of every plot, and only become
defined in the event of a mouse click in the active plot window. To determine
from a script if the mouse has been clicked in the active plot window, it is
sufficient to test for any one of these variables being defined.
plot 'something'
pause mouse
if (exists("MOUSE_BUTTON")) call 'something_else'; \
else print "No mouse click."
It is also possible to track keystrokes in the plot window using the mousing
code.
plot 'something'
pause mouse keypress
print "Keystroke ", MOUSE_KEY, " at ", MOUSE_X, " ", MOUSE_Y
When `pause mouse keypress` is terminated by a keypress, then MOUSE_KEY will
contain the ascii character value of the key that was pressed. MOUSE_CHAR will
contain the character itself as a string variable. If the pause command is
terminated abnormally (e.g. by ctrl-C or by externally closing the plot window)
then MOUSE_KEY will equal -1.
Note that after a zoom by mouse, you can read the new ranges as GPVAL_X_MIN,
GPVAL_X_MAX, GPVAL_Y_MIN, and GPVAL_Y_MAX, see `gnuplot-defined variables`.
?persist
Many gnuplot terminals (aqua, pm, qt, x11, windows, wxt, ...) open separate
display windows on the screen into which plots are drawn. The `persist` option
tells gnuplot to leave these windows open when the main program exits.
It has no effect on non-interactive terminal output.
For example if you issue the command
gnuplot -persist -e 'plot [-5:5] sinh(x)'
gnuplot will open a display window, draw the plot into it, and then exit,
leaving the display window containing the plot on the screen. Depending on
the terminal type, some mousing operations may still be possible in the
persistent window. However operations like zoom/unzoom that require redrawing
the plot are generally not possible because the main program has already exited.
You can also specify `persist` or `nopersist` at the time you set a new terminal
type. For example
set term qt persist size 700,500
?plotting
There are four `gnuplot` commands which actually create a plot: `plot`,
`splot`, `replot`, and `refresh`. Other commands control the layout, style,
and content of the plot that will eventually be created.
`plot` generates 2D plots. `splot` generates 3D plots (actually 2D projections,
of course). `replot` reexecutes the previous `plot` or `splot` command.
`refresh` is similar to `replot` but it reuses any previously stored data
rather than rereading data from a file or input stream.
Each time you issue one of these four commands it will redraw the screen or
generate a new page of output containing all of the currently defined axes,
labels, titles, and all of the various functions or data sources listed in the
original plot command. If instead you need to place several complete plots next
to each other on the same page, e.g. to make a panel of sub-figures or to inset
a small plot inside a larger plot, use the command `set multiplot` to suppress
generation of a new page for each plot command.
Much of the general information about plotting can be found in the discussion
of `plot`; information specific to 3D can be found in the `splot` section.
`plot` operates in either rectangular or polar coordinates -- see `set polar`.
`splot` operates in Cartesian coordinates, but will accept azimuthal or
cylindrical coordinates on input. See `set mapping`.
`plot` also lets you use each of the four borders -- x (bottom), x2 (top), y
(left) and y2 (right) -- as an independent axis. The `axes` option lets you
choose which pair of axes a given function or data set is plotted against. A
full complement of `set` commands exists to give you complete control over
the scales and labeling of each axis. Some commands have the name of an
axis built into their names, such as `set xlabel`. Other commands have one
or more axis names as options, such as `set logscale xy`. Commands and
options controlling the z axis have no effect on 2D graphs.
`splot` can plot surfaces and contours in addition to points and/or lines.
See `set isosamples` for information about defining the grid for a 3D function.
See `splot datafile` for information about the requisite file structure for 3D
data. For contours see `set contour`, `set cntrlabel`, and `set cntrparam`.
In `splot`, control over the scales and labels of the axes are the same as
with `plot` except that there is also a z axis and labeling the x2 and y2 axes
is possible only for pseudo-2D plots created using `set view map`.
?startup
?start
?start-up
?initialization
?.gnuplot
When gnuplot is run, it first looks for a system-wide initialization file
`gnuplotrc`. The location of this file is determined when the program is built
and is reported by `show loadpath`. The program then looks in the user's HOME
directory for a file called `.gnuplot` on Unix-like systems or `GNUPLOT.INI` on
other systems. (OS/2 will look for it in the directory named in
the environment variable `GNUPLOT`; Windows will use `APPDATA`).
Note: The program can be configured to look first in the current directory,
but this is not recommended because it is bad security practice.
?strings
?string variables
In addition to string constants, most gnuplot commands also accept a string
variable, a string expression, or a function that returns a string.
For example, the following four methods of creating a plot all result in the
same plot title:
four = "4"
graph4 = "Title for plot #4"
graph(n) = sprintf("Title for plot #%d",n)
plot 'data.4' title "Title for plot #4"
plot 'data.4' title graph4
plot 'data.4' title "Title for plot #".four
plot 'data.4' title graph(4)
Since integers are promoted to strings when operated on by the string
concatenation operator, the following method also works:
N = 4
plot 'data.'.N title "Title for plot #".N
In general, elements on the command line will only be evaluated as possible
string variables if they are not otherwise recognizable as part of the normal
gnuplot syntax. So the following sequence of commands is legal, although
probably should be avoided so as not to cause confusion:
plot = "my_datafile.dat"
title = "My Title"
plot plot title title
Three binary operators require string operands: the string concatenation
operator ".", the string equality operator "eq" and the string inequality
operator "ne". The following example will print TRUE.
if ("A"."B" eq "AB") print "TRUE"
See also the two string formatting functions `gprintf` and `sprintf`.
Substrings can be specified by appending a range specifier to any string,
string variable, or string-valued function. The range specifier has the
form [begin:end], where begin is the index of the first character of the
substring and end is the index of the last character of the substring.
The first character has index 1. The begin or end fields may be empty, or
contain '*', to indicate the true start or end of the original string.
E.g. str[:] and str[*:*] both describe the full string str.
?substitution
When a command line to gnuplot is first read, i.e. before it is interpreted
or executed, two forms of lexical substitution are performed. These are
triggered by the presence of text in backquotes (ascii character 96) or
preceded by @ (ascii character 64).
?substitution backquotes
?backquotes
?shell commands
Command-line substitution is specified by a system command enclosed in
backquotes. This command is spawned and the output it produces replaces
the backquoted text on the command line. Exit status of the system command
is returned in variables GPVAL_SYSTEM_ERRNO and GPVAL_SYSTEM_ERRMSG.
See `system`.
Command-line substitution can be used anywhere on the `gnuplot` command
line, except inside strings delimited by single quotes.
Example:
This will run the program `leastsq` and replace `leastsq` (including
backquotes) on the command line with its output:
f(x) = `leastsq`
or, in VMS
f(x) = `run leastsq`
These will generate labels with the current time and userid:
set label "generated on `date +%Y-%m-%d` by `whoami`" at 1,1
set timestamp "generated on %Y-%m-%d by `whoami`"
?substitution macros
?macros
The character @ is used to trigger substitution of the current value of a
string variable into the command line. The text in the string variable may
contain any number of lexical elements. This allows string variables to be
used as command line macros. Only string constants may be expanded using this
mechanism, not string-valued expressions.
For example:
style1 = "lines lt 4 lw 2"
style2 = "points lt 3 pt 5 ps 2"
range1 = "using 1:3"
range2 = "using 1:5"
plot "foo" @range1 with @style1, "bar" @range2 with @style2
The line containing @ symbols is expanded on input, so that by the time it is
executed the effect is identical to having typed in full
plot "foo" using 1:3 with lines lt 4 lw 2, \
"bar" using 1:5 with points lt 3 pt 5 ps 2
The function exists() may be useful in connection with macro evaluation.
The following example checks that C can safely be expanded as the name of
a user-defined variable:
C = "pi"
if (exists(C)) print C," = ", @C
Macro expansion does not occur inside either single or double quotes.
However macro expansion does occur inside backquotes.
Macro expansion is handled as the very first thing the interpreter does when
looking at a new line of commands and is only done once. Therefore, code like
the following will execute correctly:
A = "c=1"
@A
but this line will not, since the macro is defined on the same line
and will not be expanded in time
A = "c=1"; @A # will not expand to c=1
For execution of complete commands the `evaluate` command may also be handy.
?mixing_macros_backquotes
?substitution mixing_macros_backquotes
The interaction of string variables, backquotes and macro substitution is
somewhat complicated. Backquotes do not block macro substitution, so
filename = "mydata.inp"
lines = ` wc --lines @filename | sed "s/ .*//" `
results in the number of lines in mydata.inp being stored in the integer
variable lines. And double quotes do not block backquote substitution, so
mycomputer = "`uname -n`"
results in the string returned by the system command `uname -n` being stored
in the string variable mycomputer.
However, macro substitution is not performed inside double quotes, so you
cannot define a system command as a macro and then use both macro and backquote
substitution at the same time.
machine_id = "uname -n"
mycomputer = "`@machine_id`" # doesn't work!!
This fails because the double quotes prevent @machine_id from being interpreted
as a macro. To store a system command as a macro and execute it later you must
instead include the backquotes as part of the macro itself. This is
accomplished by defining the macro as shown below. Notice that the sprintf
format nests all three types of quotes.
machine_id = sprintf('"`uname -n`"')
mycomputer = @machine_id
?syntax
?specify
?punctuation
Options and any accompanying parameters are separated by spaces whereas lists
and coordinates are separated by commas. Ranges are separated by colons and
enclosed in brackets [], text and file names are enclosed in quotes, and a
few miscellaneous things are enclosed in parentheses.
Commas are used to separate coordinates on the `set` commands `arrow`,
`key`, and `label`; the list of variables being fitted (the list after the
`via` keyword on the `fit` command); lists of discrete contours or the loop
parameters which specify them on the `set cntrparam` command; the arguments
of the `set` commands `dgrid3d`, `dummy`, `isosamples`, `offsets`, `origin`,
`samples`, `size`, `time`, and `view`; lists of tics or the loop parameters
which specify them; the offsets for titles and axis labels; parametric
functions to be used to calculate the x, y, and z coordinates on the `plot`,
`replot` and `splot` commands; and the complete sets of keywords specifying
individual plots (data sets or functions) on the `plot`, `replot` and `splot`
commands.
Parentheses are used to delimit sets of explicit tics (as opposed to loop
parameters) and to indicate computations in the `using` filter of the `fit`,
`plot`, `replot` and `splot` commands.
(Parentheses and commas are also used as usual in function notation.)
Square brackets are used to delimit ranges given in `set`, `plot`
or `splot` commands.
Colons are used to separate extrema in `range` specifications (whether they
are given on `set`, `plot` or `splot` commands) and to separate entries in
the `using` filter of the `plot`, `replot`, `splot` and `fit` commands.
Semicolons are used to separate commands given on a single command line.
Curly braces are used in the syntax for enhanced text mode and to delimit
blocks in if/then/else statements. They are also used to denote complex
numbers: {3,2} = 3 + 2i.
The EEPIC, Imagen, Uniplex, LaTeX, and TPIC drivers allow a newline to be
specified by \\ in a single-quoted string or \\\\ in a double-quoted string.
?quotes
?syntax quotes
Gnuplot uses three forms of quote marks for delimiting text strings,
double-quote (ascii 34), single-quote (ascii 39), and backquote (ascii 96).
Filenames may be entered with either single- or double-quotes. In this
manual the command examples generally single-quote filenames and double-quote
other string tokens for clarity.
String constants and text strings used for labels, titles, or other plot
elements may be enclosed in either single quotes or double quotes. Further
processing of the quoted text depends on the choice of quote marks.
Backslash processing of special characters like \n (newline) and
\345 (octal character code) is performed only for double-quoted strings.
In single-quoted strings, backslashes are just ordinary characters. To get
a single-quote (ascii 39) in a single-quoted string, it must be doubled.
Thus the strings "d\" s' b\\" and 'd" s'' b\' are completely equivalent.
Text justification is the same for each line of a multi-line string.
Thus the center-justified string
"This is the first line of text.\nThis is the second line."
will produce
This is the first line of text.
This is the second line.
but
'This is the first line of text.\nThis is the second line.'
will produce
This is the first line of text.\nThis is the second line.
Enhanced text processing is performed for both double-quoted text and
single-quoted text, but only by terminals supporting this mode.
See `enhanced text`.
Back-quotes are used to enclose system commands for substitution into the
command line. See `substitution`.
?time/date
`gnuplot` supports the use of time and/or date information as input data.
This feature is activated by the commands `set xdata time`, `set ydata time`,
etc.
Internally all times and dates are converted to the number of seconds from
the year 1970. The command `set timefmt` defines the default format for all
inputs: data files, ranges, tics, label positions -- anything that accepts a
time data value defaults to receiving it in this format. Only one default
format can be in effect at a given time. Thus if both x and y data in a file
are time/date, by default they are interpreted in the same format. However
this default can be replaced when reading any particular file or column of
input using the `timecolumn` function in the corresponding `using` specifier.
The conversion to and from seconds assumes Universal Time (which is the same
as Greenwich Standard Time). There is no provision for changing the time
zone or for daylight savings. If all your data refer to the same time zone
(and are all either daylight or standard) you don't need to worry about these
things. But if the absolute time is crucial for your application, you'll
need to convert to UT yourself.
Commands like `show xrange` will re-interpret the integer according to
`timefmt`. If you change `timefmt`, and then `show` the quantity again, it
will be displayed in the new `timefmt`. For that matter, if you reset the
data type flag for that axis (e.g. `set xdata`), the quantity will be shown
in its numerical form.
The commands `set format` or `set tics format` define the format that will be
used for tic labels, whether or not input for the specified axis is time/date.
If time/date information is to be plotted from a file, the `using` option
_must_ be used on the `plot` or `splot` command. These commands simply use
white space to separate columns, but white space may be embedded within the
time/date string. If you use tabs as a separator, some trial-and-error may
be necessary to discover how your system treats them.
The `time` function can be used to get the current system time. This value
can be converted to a date string with the `strftime` function, or it can be
used in conjunction with `timecolumn` to generate relative time/date plots.
The type of the argument determines what is returned. If the argument is an
integer, `time` returns the current time as an integer, in seconds from
1 Jan 1970. If the argument is real (or complex), the result is real as well.
The precision of the fractional (sub-second) part depends on your operating
system. If the argument is a string, it is assumed to be a format string,
and it is passed to `strftime` to provide a formatted time/date string.
The following example demonstrates time/date plotting.
Suppose the file "data" contains records like
03/21/95 10:00 6.02e23
This file can be plotted by
set xdata time
set timefmt "%m/%d/%y"
set xrange ["03/21/95":"03/22/95"]
set format x "%m/%d"
set timefmt "%m/%d/%y %H:%M"
plot "data" using 1:3
which will produce xtic labels that look like "03/21".
Gnuplot tracks time to millisecond precision. Time formats have been
modified to match this.
Example: print the current time to msec precision
print strftime("%H:%M:%.3S %d-%b-%Y",time(0.0))
18:15:04.253 16-Apr-2011
See `time_specifiers`.
?plotting styles
Many plotting styles are available in gnuplot.
They are listed alphabetically below.
The commands `set style data` and `set style function` change the
default plotting style for subsequent `plot` and `splot` commands.
You can also specify the plot style explicitly as part of
the `plot` or `splot` command. If you want to mix plot styles within a
single plot, you must specify the plot style for each component.
Example:
plot 'data' with boxes, sin(x) with lines
Each plot style has its own expected set of data entries in a data file.
For example, by default the `lines` style expects either a single column of
y values (with implicit x ordering) or a pair of columns with x in the first
and y in the second. For more information on how to fine-tune how columns in a
file are interpreted as plot data, see `using`.
?plotting styles boxerrorbars
?style boxerrorbars
?boxerrorbars
The `boxerrorbars` style is only relevant to 2D data plotting. It is a
combination of the `boxes` and `yerrorbars` styles. It requires 3, 4, or 5
columns of data.
An additional (4th, 5th or 6th) input column may be used to provide variable
(per-datapoint) color information (see `linecolor` and `rgbcolor variable`).
The error bar will be drawn in the same color as the border of the box.
3 columns: x y ydelta
4 columns: x y ydelta xdelta # boxwidth != -2
4 columns: x y ylow yhigh # boxwidth == -2
5 columns: x y ylow yhigh xdelta
The boxwidth will come from the fourth column if the y errors are given as
"ydelta" and the boxwidth was not previously set to -2.0 (`set boxwidth -2.0`)
or from the fifth column if the y errors are in the form of "ylow yhigh". The
special case `boxwidth = -2.0` is for four-column data with y errors in the
form "ylow yhigh". In this case the boxwidth will be calculated so that each
box touches the adjacent boxes. The width will also be calculated in cases
where three-column data are used.
The box height is determined from the y error in the same way as it is for
the `yerrorbars` style---either from y-ydelta to y+ydelta or from ylow to
yhigh, depending on how many data columns are provided.
?plotting styles boxes
?style boxes
?boxes
The `boxes` style is only relevant to 2D plotting. It draws a box centered
about the given x coordinate that extends from the x axis (not from the graph
border) to the given y coordinate. It uses 2 or 3 columns of basic data.
Additional input columns may be used to provide information such as
variable line or fill color (see `rgbcolor variable`).
2 columns: x y
3 columns: x y x_width
The width of the box is obtained in one of three ways. If the input data has a
third column, this will be used to set the width of the box. If not, if a
width has been set using the `set boxwidth` command, this will be used.
If neither of these is available, the width of each box will be calculated
automatically so that it touches the adjacent boxes.
The interior of the boxes is drawn according to the current fillstyle.
See `set style fill` for details. Alternatively a new fillstyle
may be specified in the plot command.
For fillstyle `empty` the box is not filled.
For fillstyle `solid` the box is filled with a solid rectangle of the
current drawing color. An optional fillstyle parameter controls the fill density;
it runs from 0 (background color) to 1 (current drawing color).
For fillstyle `pattern` the box is filled in the current drawing color with
a pattern.
Examples:
To plot a data file with solid filled boxes with a small vertical space
separating them (bargraph):
set boxwidth 0.9 relative
set style fill solid 1.0
plot 'file.dat' with boxes
To plot a sine and a cosine curve in pattern-filled boxes style:
set style fill pattern
plot sin(x) with boxes, cos(x) with boxes
The sin plot will use pattern 0; the cos plot will use pattern 1.
Any additional plots would cycle through the patterns supported by the
terminal driver.
To specify explicit fillstyles for each dataset:
plot 'file1' with boxes fs solid 0.25, \
'file2' with boxes fs solid 0.50, \
'file3' with boxes fs solid 0.75, \
'file4' with boxes fill pattern 1, \
'file5' with boxes fill empty
?plotting styles boxplot
?style boxplot
?boxplot
Boxplots are a common way to represent a statistical distribution of values.
Quartile boundaries are determined such that 1/4 of the points have a value
equal or less than the first quartile boundary, 1/2 of the points have a value
equal or less than the second quartile (median) value, etc. A box is drawn
around the region between the first and third quartiles, with a horizontal line
at the median value. Whiskers extend from the box to user-specified limits.
Points that lie outside these limits are drawn individually.
Examples
# Place a boxplot at x coordinate 1.0 representing the y values in column 5
plot 'data' using (1.0):5
# Same plot but suppress outliers and force the width of the boxplot to 0.3
set style boxplot nooutliers
plot 'data' using (1.0):5:(0.3)
By default only one boxplot is produced that represents all y values from the
second column of the using specification. However, an additional (fourth)
column can be added to the specification. If present, the values of that
column will be interpreted as the discrete levels of a factor variable.
As many boxplots will be drawn as there are levels in the factor variable.
The separation between these boxplots is 1.0 by default, but it can be changed
by `set style boxplot separation`. By default, the value of the factor variable
is shown as a tic label below (or above) each boxplot.
Example
# Suppose that column 2 of 'data' contains either "control" or "treatment"
# The following example produces two boxplots, one for each level of the
# factor
plot 'data' using (1.0):5:(0):2
The default width of the box can be set via `set boxwidth <width>` or may be
specified as an optional 3rd column in the `using` clause of the plot command.
The first and third columns (x coordinate and width) are normally provided as
constants rather than as data columns.
By default the whiskers extend from the ends of the box to the most distant
point whose y value lies within 1.5 times the interquartile range. By default
outliers are drawn as circles (point type 7). The width of the bars at the
end of the whiskers may be controlled using `set bars` or `set errorbars`.
These default properties may be changed using the `set style boxplot` command.
See `set style boxplot`, `bars`, `boxwidth`, `fillstyle`, `candlesticks`.
?plotting styles boxxyerror
?style boxxyerror
?boxxyerror
The `boxxyerror` plot style is only relevant to 2D data plotting.
It is similar to the `xyerrorbars` style except that it draws rectangular areas
rather than crosses. It uses either 4 or 6 basic columns of input data.
Additional input columns may be used to provide information such as
variable line or fill color (see `rgbcolor variable`).
4 columns: x y xdelta ydelta
6 columns: x y xlow xhigh ylow yhigh
The box width and height are determined from the x and y errors in the same
way as they are for the `xyerrorbars` style---either from xlow to xhigh and
from ylow to yhigh, or from x-xdelta to x+xdelta and from y-ydelta to
y+ydelta, depending on how many data columns are provided.
The 6 column form of the command provides a convenient way to plot rectangles
with arbitrary x and y bounds.
An additional (5th or 7th) input column may be used to provide variable
(per-datapoint) color information (see `linecolor` and `rgbcolor variable`).
The interior of the boxes is drawn according to the current fillstyle.
See `set style fill` and `boxes` for details. Alternatively a new fillstyle
may be specified in the plot command.
?plotting styles candlesticks
?style candlesticks
?candlesticks
The `candlesticks` style can be used for 2D data plotting of financial
data or for generating box-and-whisker plots of statistical data.
The symbol is a rectangular box, centered horizontally at the x
coordinate and limited vertically by the opening and closing prices. A
vertical line segment at the x coordinate extends up from the top of the
rectangle to the high price and another down to the low. The vertical line
will be unchanged if the low and high prices are interchanged.
Five columns of basic data are required:
financial data: date open low high close
whisker plot: x box_min whisker_min whisker_high box_high
The width of the rectangle can be controlled by the `set boxwidth` command.
For backwards compatibility with earlier gnuplot versions, when the
boxwidth parameter has not been set then the width of the candlestick
rectangle is controlled by `set errorbars <width>`.
Alternatively, an explicit width for each box-and-whiskers grouping may be
specified in an optional 6th column of data. The width must be given in the
same units as the x coordinate.
An additional (6th, or 7th if the 6th column is used for width data)
input column may be used to provide variable (per-datapoint) color
information (see `linecolor` and `rgbcolor variable`).
By default the vertical line segments have no crossbars at the top and
bottom. If you want crossbars, which are typically used for box-and-whisker
plots, then add the keyword `whiskerbars` to the plot command. By default
these whiskerbars extend the full horizontal width of the candlestick, but
you can modify this by specifying a fraction of the full width.
The usual convention for financial data is that the rectangle is empty
if (open < close) and solid fill if (close < open). This is the behavior you
will get if the current fillstyle is set to "empty". See `fillstyle`.
If you set the fillstyle to solid or pattern, then this will be used for
all boxes independent of open and close values.
See also `set errorbars` and `financebars`. See also the
candlestick
and
finance
demos.
Note: To place additional symbols, such as the median value, on a
box-and-whisker plot requires additional plot commands as in this example:
# Data columns:X Min 1stQuartile Median 3rdQuartile Max
set errorbars 4.0
set style fill empty
plot 'stat.dat' using 1:3:2:6:5 with candlesticks title 'Quartiles', \
'' using 1:4:4:4:4 with candlesticks lt -1 notitle
# Plot with crossbars on the whiskers, crossbars are 50% of full width
plot 'stat.dat' using 1:3:2:6:5 with candlesticks whiskerbars 0.5
See `set boxwidth`, `set errorbars`, `set style fill`, and `boxplot`.
?plotting styles circles
?style circles
?circles
The `circles` style plots a circle with an explicit radius at each data point.
If three columns of data are present, they are interpreted as x, y, radius.
The radius is always interpreted in the units of the plot's horizontal axis
(x or x2). The scale on y and the aspect ratio of the plot are both ignored.
If only two columns are present, the radius is taken from `set style circle`.
In this case the radius may be given in graph or screen coordinates.
By default a full circle will be drawn. It is possible to plot arc segments
instead of full circles by specifying a start and end angle in the 4th and 5th
columns. An optional 4th or 6th column can specify per-circle color.
The start and end angles of the circle segments must be specified in degrees.
See `set style circle` and `set style fill`.
Examples:
# draws circles whose area is proportional to the value in column 3
set style fill transparent solid 0.2 noborder
plot 'data' using 1:2:(sqrt($3)) with circles, \
'data' using 1:2 with linespoints
# draws Pac-men instead of circles
plot 'data' using 1:2:(10):(40):(320) with circles
# draw a pie chart with inline data
set xrange [-15:15]
set style fill transparent solid 0.9 noborder
plot '-' using 1:2:3:4:5:6 with circles lc var
0 0 5 0 30 1
0 0 5 30 70 2
0 0 5 70 120 3
0 0 5 120 230 4
0 0 5 230 360 5
e
The result is similar to using a `points` plot with variable size points and
pointstyle 7, except that the circles will scale with the x axis range.
See also `set object circle` and `fillstyle`.
?plotting styles ellipses
?style ellipses
?ellipses
The `ellipses` style plots an ellipse at each data point. This style is
only relevant for 2D plotting. Each ellipse is described in terms of its
center, major and minor diameters, and the angle between its major diameter
and the x axis.
2 columns: x y
3 columns: x y major_diam
4 columns: x y major_diam minor_diam
5 columns: x y major_diam minor_diam angle
If only two input columns are present, they are taken as the coordinates of
the centers, and the ellipses will be drawn with the default extent
(see `set style ellipse`). The orientation of the ellipse, which is
defined as the angle between the major diameter and the plot's x axis,
is taken from the default ellipse style (see `set style ellipse`).
If three input columns are provided, the third column is used for both
diameters. The orientation angle defaults to zero.
If four columns are present, they are interpreted as x, y, major diameter,
minor diameter. Note that these are diameters, not radii.
An optional 5th column may be used to specify the orientation angle
in degrees.
The ellipses will also be drawn with their default extent if either of the
supplied diameters in the 3-4-5 column form is negative.
In all of the above cases, optional variable color data may be given in an
additional last (3th, 4th, 5th or 6th) column. See `colorspec` for further
information.
By default, the major diameter is interpreted in the units of the plot's
horizontal axis (x or x2) while the minor diameter in that of the vertical
(y or y2). This implies that if the x and y axis scales are not equal,
then the major/minor diameter ratio will no longer be correct after rotation.
This behavior can be changed with the `units` keyword, however.
There are three alternatives:
if `units xy` is included in the plot specification, the axes will be scaled
as described above. `units xx` ensures that both diameters are interpreted
in units of the x axis, while `units yy` means that both diameters are
interpreted in units of the y axis. In the latter two cases the ellipses
will have the correct aspect ratio, even if the plot is resized.
If `units` is omitted, the default setting will be used, which is equivalent
to `units xy`. This can be redefined by `set style ellipse`.
Example (draws ellipses, cycling through the available line types):
plot 'data' using 1:2:3:4:(0):0 with ellipses
See also `set object ellipse`, `set style ellipse` and `fillstyle`.
?plotting styles dots
?style dots
?dots
The `dots` style plots a tiny dot at each point; this is useful for scatter
plots with many points. Either 1 or 2 columns of input data are required in
2D. Three columns are required in 3D.
For some terminals (post, pdf) the size of the dot can be controlled by
changing the linewidth.
1 column y # x is row number
2 columns: x y
3 columns: x y z # 3D only (splot)
?plotting styles filledcurves
?style filledcurves
?filledcurves
The `filledcurves` style is only used for 2D plotting. It has three variants.
The first two variants require either a single function or two columns (x,y)
of input data, and may be further modified by the options listed below.
Syntax:
plot ... with filledcurves [option]
where the option can be one of the following
[closed | {above | below}
{x1 | x2 | y | r}[=<a>] | xy=<x>,<y>]
The first variant, `closed`, treats the curve itself as a closed polygon.
This is the default if there are two columns of input data.
The second variant is to fill the area between the curve and a given axis,
a horizontal or vertical line, or a point.
filledcurves closed ... just filled closed curve,
filledcurves x1 ... x1 axis,
filledcurves x2 ... x2 axis, etc for y1 and y2 axes,
filledcurves y=42 ... line at y=42, i.e. parallel to x axis,
filledcurves xy=10,20 ... point 10,20 of x1,y1 axes (arc-like shape).
filledcurves above r=1.5 the area of a polar plot outside radius 1.5
The third variant fills the area between two curves sampled at the same set of
x coordinates. It requires three columns of input data (x, y1, y2).
This is the default if there are three or more columns of input data.
If you have a y value in column 2 and an associated error value in column 3
the area of uncertainty can be represented by shading.
See also the similar 3D plot style `zerrorfill`.
3 columns: x y yerror
plot $DAT using 1:($2-$3):($2+$3) with filledcurves, \
$DAT using 1:2 smooth mcs with lines
The `above` and `below` options apply both to commands of the form
... filledcurves above {x1|x2|y|r}=<val>
and to commands of the form
... using 1:2:3 with filledcurves below
In either case the option limits the filled area to one side of the bounding
line or curve.
Notes: Not all terminal types support this plotting mode.
The x= and y= keywords are ignored for 3 columns data plots
Zooming a filled curve drawn from a datafile may produce empty or incorrect
areas because gnuplot is clipping points and lines, and not areas.
If the values <x>, <y>, or <a> are outside the drawing boundary they are
moved to the graph boundary. Then the actual fill area in the case
of option xy=<x>,<y> will depend on xrange and yrange.
?filledcurves border
Plotting `with filledcurves` can be further customized by giving a fillstyle
(solid/transparent/pattern) or a fillcolor. If no fillstyle (`fs`)
is given in the plot command then the current default fill style is used.
See `set style fill`. If no fillcolor (`fc`) is given in the plot command,
the usual linetype color sequence is followed.
The {{no}border} property of the fillstyle is honored by filledcurves mode
`closed`, the default. It is ignored by all other filledcurves modes.
Example:
plot 'data' with filledcurves fc "cyan" fs solid 0.5 border lc "blue"
?plotting styles financebars
?style financebars
?financebars
The `financebars` style is only relevant for 2D data plotting of financial
data. It requires 1 x coordinate (usually a date) and 4 y values (prices).
5 columns: date open low high close
An additional (6th) input column may be used to provide variable
(per-record) color information (see `linecolor` and `rgbcolor variable`).
The symbol is a vertical line segment, located horizontally at the x
coordinate and limited vertically by the high and low prices. A horizontal
tic on the left marks the opening price and one on the right marks the
closing price. The length of these tics may be changed by `set errorbars`.
The symbol will be unchanged if the high and low prices are interchanged.
See `set errorbars` and `candlesticks`, and also the
finance demo.
?plotting styles fsteps
?style fsteps
?fsteps
The `fsteps` style is only relevant to 2D plotting. It connects consecutive
points with two line segments: the first from (x1,y1) to (x1,y2) and the
second from (x1,y2) to (x2,y2). The input column requires are the same as for
plot styles `lines` and `points`. The difference between `fsteps` and `steps`
is that `fsteps` traces first the change in y and then the change in x.
`steps` traces first the change in x and then the change in y.
See also
steps demo.
?style fillsteps
?fillsteps
The `fillsteps` style is exactly like `steps` except that the area between
the curve and y=0 is filled in the current fill style. See `steps`.
?plotting styles histeps
?style histeps
?histeps
The `histeps` style is only relevant to 2D plotting. It is intended for
plotting histograms. Y-values are assumed to be centered at the x-values;
the point at x1 is represented as a horizontal line from ((x0+x1)/2,y1) to
((x1+x2)/2,y1). The lines representing the end points are extended so that
the step is centered on at x. Adjacent points are connected by a vertical
line at their average x, that is, from ((x1+x2)/2,y1) to ((x1+x2)/2,y2).
The input column requires are the same as for plot styles `lines` and `points`.
If `autoscale` is in effect, it selects the xrange from the data rather than
the steps, so the end points will appear only half as wide as the others.
See also
steps demo.
?style histograms
?set style histogram
?plotting styles histograms
?histograms
The `histograms` style is only relevant to 2D plotting. It produces a bar
chart from a sequence of parallel data columns. Each element of the `plot`
command must specify a single input data source (e.g. one column of the input
file), possibly with associated tic values or key titles.
Four styles of histogram layout are currently supported.
set style histogram clustered {gap <gapsize>}
set style histogram errorbars {gap <gapsize>} {<linewidth>}
set style histogram rowstacked
set style histogram columnstacked
set style histogram {title font "name,size" tc <colorspec>}
The default style corresponds to `set style histogram clustered gap 2`.
In this style, each set of parallel data values is collected into a group of
boxes clustered at the x-axis coordinate corresponding to their sequential
position (row #) in the selected datafile columns. Thus if <n> datacolumns are
selected, the first cluster is centered about x=1, and contains <n> boxes whose
heights are taken from the first entry in the corresponding <n> data columns.
This is followed by a gap and then a second cluster of boxes centered about x=2
corresponding to the second entry in the respective data columns, and so on.
The default gap width of 2 indicates that the empty space between clusters is
equivalent to the width of 2 boxes. All boxes derived from any one column
are given the same fill color and/or pattern (see `set style fill`).
Each cluster of boxes is derived from a single row of the input data file.
It is common in such input files that the first element of each row is a
label. Labels from this column may be placed along the x-axis underneath
the appropriate cluster of boxes with the `xticlabels` option to `using`.
The `errorbars` style is very similar to the `clustered` style, except that it
requires additional columns of input for each entry. The first column holds
the height (y value) of that box, exactly as for the `clustered` style.
2 columns: y yerr bar extends from y-yerr to y+err
3 columns: y ymin ymax bar extends from ymin to ymax
The appearance of the error bars is controlled by the current value of
`set errorbars` and by the optional <linewidth> specification.
Two styles of stacked histogram are supported, chosen by the command
`set style histogram {rowstacked|columnstacked}`. In these styles the data
values from the selected columns are collected into stacks of boxes.
Positive values stack upwards from y=0; negative values stack downwards.
Mixed positive and negative values will produce both an upward stack and a
downward stack. The default stacking mode is `rowstacked`.
The `rowstacked` style places a box resting on the x-axis for each
data value in the first selected column; the first data value results in
a box a x=1, the second at x=2, and so on. Boxes corresponding to the
second and subsequent data columns are layered on top of these, resulting
in a stack of boxes at x=1 representing the first data value from each
column, a stack of boxes at x=2 representing the second data value from
each column, and so on. All boxes derived from any one column are given the
same fill color and/or pattern (see `set style fill`).
The `columnstacked` style is similar, except that each stack of boxes is
built up from a single data column. Each data value from the first specified
column yields a box in the stack at x=1, each data value from the second
specified column yields a box in the stack at x=2, and so on. In this style
the color of each box is taken from the row number, rather than the column
number, of the corresponding data field.
Box widths may be modified using the `set boxwidth` command.
Box fill styles may be set using the `set style fill` command.
Histograms always use the x1 axis, but may use either y1 or y2.
If a plot contains both histograms and other plot styles, the non-histogram
plot elements may use either the x1 or the x2 axis.
Examples:
Suppose that the input file contains data values in columns 2, 4, 6, ...
and error estimates in columns 3, 5, 7, ... This example plots the values
in columns 2 and 4 as a histogram of clustered boxes (the default style).
Because we use iteration in the plot command, any number of data columns can
be handled in a single command. See `plot for`.
set boxwidth 0.9 relative
set style data histograms
set style histogram cluster
set style fill solid 1.0 border lt -1
plot for [COL=2:4:2] 'file.dat' using COL
This will produce a plot with clusters of two boxes (vertical bars) centered
at each integral value on the x axis. If the first column of the input file
contains labels, they may be placed along the x-axis using the variant command
plot for [COL=2:4:2] 'file.dat' using COL:xticlabels(1)
If the file contains both magnitude and range information for each value,
then error bars can be added to the plot. The following commands will add
error bars extending from (y-<error>) to (y+<error>), capped by horizontal bar
ends drawn the same width as the box itself. The error bars and bar ends are
drawn with linewidth 2, using the border linetype from the current fill style.
set errorbars fullwidth
set style fill solid 1 border lt -1
set style histogram errorbars gap 2 lw 2
plot for [COL=2:4:2] 'file.dat' using COL:COL+1
This shows how to plot the same data as a rowstacked histogram. Just to be
different, this example lists the separate columns explicitly rather than using
iteration.
set style histogram rowstacked
plot 'file.dat' using 2, '' using 4:xtic(1)
This will produce a plot in which each vertical bar corresponds to one row of
data. Each vertical bar contains a stack of two segments, corresponding in
height to the values found in columns 2 and 4 of the datafile.
Finally, the commands
set style histogram columnstacked
plot 'file.dat' using 2, '' using 4
will produce two vertical stacks, one for each column of data. The stack at
x=1 will contain a box for each entry in column 2 of the datafile. The stack
at x=2 will contain a box for each parallel entry in column 4 of the datafile.
Because this interchanges gnuplot's usual interpretation of input rows and
columns, the specification of key titles and x-axis tic labels must also be
modified accordingly. See the comments given below.
set style histogram columnstacked
plot '' u 5:key(1) # uses first column to generate key titles
plot '' u 5 title columnhead # uses first row to generate xtic labels
Note that the two examples just given present exactly the same data values,
but in different formats.
?newhistogram
?histograms newhistogram
?plotting style histograms newhistogram
Syntax:
newhistogram {"<title>" {font "name,size"} {tc <colorspec>}}
{lt <linetype>} {fs <fillstyle>} {at <x-coord>}
More than one set of histograms can appear in a single plot. In this case you
can force a gap between them, and a separate label for each set, by using the
`newhistogram` command.
For example
set style histogram cluster
plot newhistogram "Set A", 'a' using 1, '' using 2, '' using 3, \
newhistogram "Set B", 'b' using 1, '' using 2, '' using 3
The labels "Set A" and "Set B" will appear beneath the respective sets of
histograms, under the overall x axis label.
The newhistogram command can also be used to force histogram coloring to
begin with a specific color (linetype). By default colors will continue to
increment successively even across histogram boundaries. Here is an example
using the same coloring for multiple histograms
plot newhistogram "Set A" lt 4, 'a' using 1, '' using 2, '' using 3, \
newhistogram "Set B" lt 4, 'b' using 1, '' using 2, '' using 3
Similarly you can force the next histogram to begin with a specified fillstyle.
If the fillstyle is set to `pattern`, then the pattern used for filling will
be incremented automatically.
The `at <x-coord>` option sets the x coordinate position of the following
histogram to <x-coord>. For example
set style histogram cluster
set style data histogram
set style fill solid 1.0 border -1
set xtic 1 offset character 0,0.3
plot newhistogram "Set A", \
'file.dat' u 1 t 1, '' u 2 t 2, \
newhistogram "Set B" at 8, \
'file.dat' u 2 t 2, '' u 2 t 2
will position the second histogram to start at x=8.
?automated
?histograms automated
?styles histograms automated
?plotting styles histograms automated
If you want to create a histogram from many columns of data in a single file,
it is very convenient to use the plot iteration feature. See `plot for`.
For example, to create stacked histograms of the data in columns 3 through 8
set style histogram columnstacked
plot for [i=3:8] "datafile" using i title columnhead
?plotting styles image
?style image
?image
?rgbimage
?rgbalpha
The `image`, `rgbimage`, and `rgbalpha` plotting styles all project a
uniformly sampled grid of data values onto a plane in either 2D or 3D.
The input data may be an actual bitmapped image, perhaps converted from a
standard format such as PNG, or a simple array of numerical values.
This figure illustrates generation of a heat map from an array of scalar values.
The current palette is used to map each value onto the color assigned to the
corresponding pixel.
plot '-' matrix with image
5 4 3 1 0
2 2 0 0 1
0 0 0 1 0
0 1 2 4 3
e
e
Each pixel (data point) of the input 2D image will become a rectangle or
parallelipiped in the plot. The coordinates of each data point will determine
the center of the parallelipiped. That is, an M x N set of data will form an
image with M x N pixels. This is different from the pm3d plotting style, where
an M x N set of data will form a surface of (M-1) x (N-1) elements. The scan
directions for a binary image data grid can be further controlled by additional
keywords. See `binary keywords flipx`, `keywords center`, and `keywords rotate`.
Image data can be scaled to fill a particular rectangle within a 2D plot
coordinate system by specifying the x and y extent of each pixel.
See `binary keywords dx` and `dy`. To generate the figure at the right,
the same input image was placed multiple times, each with a specified dx, dy,
and origin. The input PNG image of a building is 50x128 pixels. The tall
building was drawn by mapping this using `dx=0.5 dy=1.5`. The short building
used a mapping `dx=0.5 dy=0.35`.
The `image` style handles input pixels containing a grayscale or color palette
value. Thus 2D plots (`plot` command) require 3 columns of data (x,y,value),
while 3D plots (`splot` command) require 4 columns of data (x,y,z,value).
The `rgbimage` style handles input pixels that are described by three separate
values for the red, green, and blue components. Thus 5D data (x,y,r,g,b) is
needed for `plot` and 6D data (x,y,z,r,g,b) for `splot`. The individual red,
green, and blue components are assumed to lie in the range [0:255].
This matches the convention used in PNG and JPEG files (see `binary filetype`).
However some data files use an alternative convention in which RGB components
are floating point values in the range [0:1]. To use the `rgbimage` style with
such data, the color component values must be rescaled to the range [0:255].
The `rgbalpha` style handles input pixels that contain alpha channel
(transparency) information in addition to the red, green, and blue components.
Thus 6D data (x,y,r,g,b,a) is needed for `plot` and 7D data (x,y,z,r,g,b,a)
for `splot`. The r, g, b, and alpha components are assumed to lie in the range
[0:255]. To plot data for which RGBA components are floating point values in
the range [0:1] you must rescale the components to lie in the range [0:255].
?image transparency
?transparency
?alpha channel
The `rgbalpha` plotting style assumes that each pixel of input data contains
an alpha value in the range [0:255]. A pixel with alpha = 0 is purely
transparent and does not alter the underlying contents of the plot. A pixel
with alpha = 255 is purely opaque. All terminal types can handle these two
extreme cases. A pixel with 0 < alpha < 255 is partially transparent.
Terminal types that do not support partial transparency will round this value
to 0 or 255.
?plotting styles image pixels
?style image pixels
?image pixels
?pixels
?plotting styles image failsafe
?style image failsafe
?image failsafe
?failsafe
Some terminals use device- or library-specific optimizations to render image
data within a rectangular 2D area. This sometimes produces undesirable output,
e.g. bad clipping or scaling, missing edges. The `pixels` keyword tells
gnuplot to use generic code that renders the image pixel-by-pixel instead.
This rendering mode is slower and may result in much larger output files, but
should produce a consistent rendered view on all terminals.
(The `pixels` options was called `failsafe` mode in previous gnuplot versions.)
Example:
plot 'data' with image pixels
?plotting styles impulses
?style impulses
?impulses
The `impulses` style displays a vertical line from y=0 to the y value of each
point (2D) or from z=0 to the z value of each point (3D). Note that the y or z
values may be negative. Data from additional columns can be used to control
the color of each impulse. To use this style effectively in 3D plots, it is
useful to choose thick lines (linewidth > 1). This approximates a 3D bar chart.
1 column: y
2 columns: x y # line from [x,0] to [x,y] (2D)
3 columns: x y z # line from [x,y,0] to [x,y,z] (3D)
?plotting styles labels
?style labels
?labels
The `labels` style reads coordinates and text from a data file and places
the text string at the corresponding 2D or 3D position. 3 or 4 input columns
of basic data are required. Additional input columns may be used to provide
properties that vary point by point such as text rotation angle (keywords
`rotate variable`) or color (see `textcolor variable`).
3 columns: x y string # 2D version
4 columns: x y z string # 3D version
The font, color, rotation angle and other properties of the printed text
may be specified as additional command options (see `set label`). The example
below generates a 2D plot with text labels constructed from the city whose
name is taken from column 1 of the input file, and whose geographic coordinates
are in columns 4 and 5. The font size is calculated from the value in column 3,
in this case the population.
CityName(String,Size) = sprintf("{/=%d %s}", Scale(Size), String)
plot 'cities.dat' using 5:4:(CityName(stringcolumn(1),$3)) with labels
If we did not want to adjust the font size to a different size for each city
name, the command would be much simpler:
plot 'cities.dat' using 5:4:1 with labels font "Times,8"
If the labels are marked as `hypertext` then the text only appears if the
mouse is hovering over the corresponding anchor point. See `hypertext`.
In this case you must enable the label's `point` attribute so that there is
a point to act as the hypertext anchor:
plot 'cities.dat' using 5:4:1 with labels hypertext point pt 7
The `labels` style can also be used in place of the `points` style when the
set of predefined point symbols is not suitable or not sufficiently flexible.
For example, here we define a set of chosen single-character symbols and assign
one of them to each point in a plot based on the value in data column 3:
set encoding utf8
symbol(z) = "∙□+⊙♠♣♡♢"[int(z):int(z)]
splot 'file' using 1:2:(symbol($3)) with labels
This example shows use of labels with variable rotation angle in column 4 and
textcolor ("tc") in column 5. Note that variable color is always taken from
the last column in the `using` specifier.
plot $Data using 1:2:3:4:5 with labels tc variable rotate variable
?plotting styles lines
?style lines
?lines
The `lines` style connects adjacent points with straight line segments.
It may be used in either 2D or 3D plots. The basic form requires 1, 2, or 3
columns of input data.
Additional input columns may be used to provide information such as
variable line color (see `rgbcolor variable`).
2D form (no "using" spec)
1 column: y # implicit x from row number
2 columns: x y
3D form (no "using" spec)
1 column: z # implicit x from row, y from index
3 columns: x y z
See also `linetype`, `linewidth`, and `linestyle`.
?plotting styles linespoints
?style linespoints
?style lp
?linespoints
?lp
?pointinterval
?pointnumber
The `linespoints` style (short form `lp`) connects adjacent points with
straight line segments and then goes back to draw a small symbol at each point.
Points are drawn with the default size determined by `set pointsize` unless a
specific point size is given in the plot command or a variable point size is
provided in an additional column of input data. Additional input columns may
also be used to provide information such as variable line color.
See `lines` and `points`.
Two keywords control whether or not every point in the plot is marked with a
symbol, `pointinterval` (short form `pi`) and `pointnumber` (short form `pn`).
`pi N` or `pi -N` tells gnuplot to only place a symbol on every Nth point.
A negative value for N will erase the portion of line segment that passes
underneath the symbol. The size of the erased portion is controlled by
`set pointintervalbox`.
`pn N` or `pn -N` tells gnuplot to label only N of the data points, evenly
spaced over the data set. As with `pi`, a negative value for N will erase the
portion of line segment that passes underneath the symbol.
?plotting style parallelaxes
?style parallelaxes
?parallelaxes
Parallel axis plots can highlight correlation in a multidimensional data set.
Each input column is associated with a separately scaled vertical axis.
The column values read from each line of input are connected by line segments
drawn from axis 1 to axis 2 to axis 3 and so on. That is, each line of input
is represented by a separate line in the parallel axes plot.
It is common to use some discrete categorization to assign line colors,
allowing visual exploration of the correlation between this categorization and
the axis dimensions.
By default gnuplot will automatically determine the range and scale of the
individual axes from the input data, but the usual `set axis range` commands
can be used to customize this. See `set paxis`.
The maximum number of parallel axes is fixed at the time the program is built.
The maximum for this copy of gnuplot is reported by `show version long`.
?plotting styles points
?style points
?points
?point type
?pointtype
The `points` style displays a small symbol at each point. The command `set
pointsize` may be used to change the default size of the points. The point type
defaults to that of the linetype. See `linetype`. If no `using` spec is found
in the plot command, input data columns are interpreted implicitly.
See `style lines`.
The first 8 point types are shared by all terminals. Individual terminals may
provide a much larger number of distinct point types. Use the `test` command
to show what is provided by the current terminal settings. Alternatively any
single printable character may be given instead of a numerical point type,
as in the example below. Longer strings may be plotted using the plot style
`labels` rather than `points`.
plot sin(x) with points pt "#"
You may use any utf-8 character as the pointtype. See `utf8`.
?variable
?variable pointtype
?variable pointsize
?pointtype variable
?pointsize variable
When using the keywords `pointtype`, `pointsize`, or `linecolor` in a plot
command, the additional keyword `variable` may be given instead of a number.
In this case the corresponding properties of each point are assigned by
additional columns of input data. Variable pointsize is always taken from the
first additional column provided in a `using` spec. Variable color is always
taken from the last additional column. When plotting with style `linespoints`
it is not currently possible to specify separate colors for the lines and the
points. If all three properties are specified for each point, the order of
input data columns is thus
plot DATA using x:y:pointsize:pointtype:color \
with points lc variable pt variable ps variable
Note: for information on user-defined program variables, see `variables`.
?plotting styles steps
?style steps
?steps
The `steps` style is only relevant to 2D plotting. It connects consecutive
points with two line segments: the first from (x1,y1) to (x2,y1) and the
second from (x2,y1) to (x2,y2). The input column requires are the same as for
plot styles `lines` and `points`. The difference between `fsteps` and `steps`
is that `fsteps` traces first the change in y and then the change in x.
`steps` traces first the change in x and then the change in y. To fill the
area between the curve and the baseline at y=0, use `fillsteps`.
See also
steps demo.
?plotting styles rgbalpha
?style rgbalpha
See `image`.
?plotting styles rgbimage
?style rgbimage
See `image`.
?plotting styles vectors
?style vectors
?vectors
The 2D `vectors` style draws a vector from (x,y) to (x+xdelta,y+ydelta).
The 3D `vectors` style is similar, but requires six columns of basic data.
In both cases, an additional input column (5th in 2D, 7th in 3D) may be used
to provide variable (per-datapoint) color information.
(see `linecolor` and `rgbcolor variable`).
A small arrowhead is drawn at the end of each vector.
4 columns: x y xdelta ydelta
6 columns: x y z xdelta ydelta zdelta
The keywords "with vectors" may be followed by an inline arrow style
specifications, a reference to a predefined arrow style, or a request to read
the index of the desired arrow style for each vector from a separate column.
Note: If you choose "arrowstyle variable" it will fill in all arrow properties
at the time the corresponding vector is drawn; you cannot mix this keyword with
other line or arrow style qualifiers in the plot command.
plot ... with vectors filled heads
plot ... with vectors arrowstyle 3
plot ... using 1:2:3:4:5 with vectors arrowstyle variable
Example:
plot 'file.dat' using 1:2:3:4 with vectors head filled lt 2
splot 'file.dat' using 1:2:3:(1):(1):(1) with vectors filled head lw 2
splot with vectors is supported only for `set mapping cartesian`.
`set clip one` and `set clip two` affect vectors drawn in 2D.
See `set clip` and `arrowstyle`.
?plotting styles xerrorbars
?style xerrorbars
?xerrorbars
The `xerrorbars` style is only relevant to 2D data plots. `xerrorbars` is
like `points`, except that a horizontal error bar is also drawn. At each point
(x,y), a line is drawn from (xlow,y) to (xhigh,y) or from (x-xdelta,y) to
(x+xdelta,y), depending on how many data columns are provided. The appearance
of the tic mark at the ends of the bar is controlled by `set errorbars`.
The basic style requires either 3 or 4 columns:
3 columns: x y xdelta
4 columns: x y xlow xhigh
An additional input column (4th or 5th) may be used to provide information
such as variable point color.
?plotting styles xyerrorbars
?style xyerrorbars
?xyerrorbars
The `xyerrorbars` style is only relevant to 2D data plots. `xyerrorbars` is
like `points`, except that horizontal and vertical error bars are also drawn.
At each point (x,y), lines are drawn from (x,y-ydelta) to (x,y+ydelta) and
from (x-xdelta,y) to (x+xdelta,y) or from (x,ylow) to (x,yhigh) and from
(xlow,y) to (xhigh,y), depending upon the number of data columns provided.
The appearance of the tic mark at the ends of the bar is controlled by
`set errorbars`. Either 4 or 6 input columns are required.
4 columns: x y xdelta ydelta
6 columns: x y xlow xhigh ylow yhigh
If data are provided in an unsupported mixed form, the `using` filter on the
`plot` command should be used to set up the appropriate form. For example,
if the data are of the form (x,y,xdelta,ylow,yhigh), then you can use
plot 'data' using 1:2:($1-$3):($1+$3):4:5 with xyerrorbars
An additional input column (5th or 7th) may be used to provide variable
(per-datapoint) color information.
?plotting styles yerrorbars
?plotting styles errorbars
?style yerrorbars
?style errorbars
?yerrorbars
The `yerrorbars` (or `errorbars`) style is only relevant to 2D data plots.
`yerrorbars` is like `points`, except that a vertical error bar is also drawn.
At each point (x,y), a line is drawn from (x,y-ydelta) to (x,y+ydelta) or
from (x,ylow) to (x,yhigh), depending on how many data columns are provided.
The appearance of the tic mark at the ends of the bar is controlled by
`set errorbars`.
2 columns: [implicit x] y ydelta
3 columns: x y ydelta
4 columns: x y ylow yhigh
An additional input column (4th or 5th) may be used to provide information
such as variable point color.
See also
errorbar demo.
?plotting styles xerrorlines
?style xerrorlines
?xerrorlines
The `xerrorlines` style is only relevant to 2D data plots.
`xerrorlines` is like `linespoints`, except that a horizontal error line is
also drawn. At each point (x,y), a line is drawn from (xlow,y) to (xhigh,y)
or from (x-xdelta,y) to (x+xdelta,y), depending on how many data columns are
provided. The appearance of the tic mark at the ends of the bar is controlled
by `set errorbars`. The basic style requires either 3 or 4 columns:
3 columns: x y xdelta
4 columns: x y xlow xhigh
An additional input column (4th or 5th) may be used to provide information
such as variable point color.
?plotting styles xyerrorlines
?style xyerrorlines
?xyerrorlines
The `xyerrorlines` style is only relevant to 2D data plots.
`xyerrorlines` is like `linespoints`, except that horizontal and vertical
error bars are also drawn. At each point (x,y), lines are drawn from
(x,y-ydelta) to (x,y+ydelta) and from (x-xdelta,y) to (x+xdelta,y) or from
(x,ylow) to (x,yhigh) and from (xlow,y) to (xhigh,y), depending upon the
number of data columns provided. The appearance of the tic mark at the ends
of the bar is controlled by `set errorbars`.
Either 4 or 6 input columns are required.
4 columns: x y xdelta ydelta
6 columns: x y xlow xhigh ylow yhigh
If data are provided in an unsupported mixed form, the `using` filter on the
`plot` command should be used to set up the appropriate form. For example,
if the data are of the form (x,y,xdelta,ylow,yhigh), then you can use
plot 'data' using 1:2:($1-$3):($1+$3):4:5 with xyerrorlines
An additional input column (5th or 7th) may be used to provide variable
(per-datapoint) color information.
?plotting styles yerrorlines
?plotting styles errorlines
?style yerrorlines
?style errorlines
?yerrorlines
The `yerrorlines` (or `errorlines`) style is only relevant to 2D data
plots. `yerrorlines` is like `linespoints`, except that a vertical error line
is also drawn. At each point (x,y), a line is drawn from (x,y-ydelta) to
(x,y+ydelta) or from (x,ylow) to (x,yhigh), depending on how many data columns
are provided. The appearance of the tic mark at the ends of the bar is
controlled by `set errorbars`. Either 3 or 4 input columns are required.
3 columns: x y ydelta
4 columns: x y ylow yhigh
An additional input column (4th or 5th) may be used to provide information
such as variable point color.
See also
errorbar demo.
?plotting styles zerrorfill
?style zerrorfill
?zerrorfill
Syntax:
splot DATA using 1:2:3:4[:5] with zerrorfill {fc|fillcolor <colorspec>}
{lt|linetype <n>} {<line properties>}
The `zerrorfill` plot style is similar to one variant of the 2D plot style
`filledcurves`. It fills the area between two functions or data lines that
are sampled at the same x and y points. It requires 4 or 5 input columns:
4 columns: x y z zdelta
5 columns: x y z zlow zhigh
The area between zlow and zhigh is filled and then a line is drawn through the
z values. By default both the line and the fill area use the same color, but
you can change this in the splot command. The fill area properties are also
affected by the global fill style; see `set style fill`.
If there are multiple curves in the splot command each new curve may occlude
all previous curves. To get proper depth sorting so that curves can only be
occluded by curves closer to the viewer, use the command `set pm3d depthorder`.
Unfortunately this causes all the filled areas to be drawn after all of the
corresponding lines of z values. In order to see both the lines and the
depth-sorted fill areas you probably will need to make the fill areas
partially transparent or use pattern fill rather than solid fill.
The fill area in the first two examples below is the same.
splot 'data' using 1:2:3:4 with zerrorfill fillcolor "grey" lt black
splot 'data' using 1:2:3:($3-$4):($3+$4) with zerrorfill
splot '+' using 1:(const):(func1($1)):(func2($1)) with zerrorfill
splot for [k=1:5] datafile[k] with zerrorfill lt black fc lt (k+1)
This plot style can also be used to create fence plots. See `fenceplots`.
?3D plots
?plotting styles 3D plots
3D plots are generated using the command `splot` rather than `plot`.
Many of the 2D plot styles (points, images, impulse, labels, vectors) can also
be used in 3D by providing an extra column of data containing z coordinate.
Some plot types (pm3d coloring, surfaces, contours) must be generated using the
`splot` command even if only a 2D projection is wanted.
?surface plots
The styles `splot with lines` and `splot with surface` both generate a surface
made from a grid of lines. Solid surfaces can be generated using the style
`splot with pm3d`. Usually the surface is displayed at some convenient viewing
angle, such that it clearly represents a 3D surface. See `set view`.
In this case the X, Y, and Z axes are all visible in the plot.
The illusion of 3D is enhanced by choosing hidden line removal or depth-sorted
surface elements. See `hidden3d` and the `depthorder` option of `set pm3d`.
The `splot` command can also calculate and draw contour lines corresponding
to constant Z values. These contour lines may be drawn onto the surface
itself, or projected onto the XY plane. See `set contour`.
?2D projection (set view map)
?projection
An important special case of the `splot` command is to map the Z coordinate
onto a 2D surface by projecting the plot along the Z axis. See `set view map`.
This plot mode can be used to generate contour plots and heat maps. This figure
shows contours plotted once with plot style `lines`, once with style `labels`.
Polar plots are generated by changing the current coordinate system to
polar before issuing a plot command. The option `set polar` tells gnuplot to
interpret input 2D coordinates as <angle>,<radius> rather than <x>,<y>.
Many, but not all, of the 2D plotting styles work in polar mode.
The figure shows a combination of plot styles `lines` and `filledcurves`.
See `set polar`, `set rrange`, `set size square`, `set theta`, `set ttics`.
?beeswarm
?bee swarm
"Bee swarm" plots result from applying jitter to separate overlapping points.
A typical use is to compare the distribution of y values exhibited by two or
more categories of points, where the category determines the x coordinate.
See the `set jitter` command for how to control the overlap criteria and the
displacement pattern used for jittering. The plots in the figure were created
by the same plot command but different jitter settings.
`plot $data using 1:2:1 lc variable`
?fenceplots
Fence plots combine several 2D plots by aligning their Y coordinates and
separating them from each other by a displacement along X. Filling the area
between a base value and each plot's series of Z values enhances the visual
impact of the alignment on Y and comparison on Z. There are several ways
such plots can be created in gnuplot. The simplest is to use the 5 column
variant of the `zerrorfill` style. Suppose there are separate curves z = Fi(y)
indexed by i. A fence plot is generated by `splot with zerrorfill` using
input columns
i y z_base z_base Fi(y)
?commands
This section lists the commands acceptable to `gnuplot` in alphabetical
order. Printed versions of this document contain all commands; the text
available interactively may not be complete. Indeed, on some systems there may
be no commands at all listed under this heading.
Note that in most cases unambiguous abbreviations for command names and their
options are permissible, i.e., "`p f(x) w li`" instead of "`plot f(x) with
lines`".
In the syntax descriptions, braces ({}) denote optional arguments and a
vertical bar (|) separates mutually exclusive choices.
?commands break
?break
The `break` command is only meaningful inside the bracketed iteration clause
of a `do` or `while` statement. It causes the remaining statements inside the
bracketed clause to be skipped and iteration is terminated. Execution resumes
at the statement following the closing bracket. See also `continue`.
?commands cd
?cd
The `cd` command changes the working directory.
Syntax:
cd '<directory-name>'
The directory name must be enclosed in quotes.
Examples:
cd 'subdir'
cd ".."
It is recommended that Windows users use single-quotes, because backslash [\]
has special significance inside double-quotes and has to be escaped.
For example,
cd "c:\newdata"
fails, but
cd 'c:\newdata'
cd "c:\\newdata"
work as expected.
?commands call
?call
The `call` command is identical to the `load` command with one exception:
the name of the file being loaded may be followed by up to nine parameters.
call "inputfile" <param-1> <param-2> <param-3> ... <param-9>
Previous versions of gnuplot performed macro-like substitution of the special
tokens $0, $1, ... $9 with the literal contents of these parameters.
This mechanism is now deprecated (see `call old-style`).
Gnuplot now provides a set of string variables ARG0, ARG1, ..., ARG9 and an
integer variable ARGC. When a `call` command is executed ARG0 is set to the
name of the input file, ARGC is set to the number of parameters present, and
ARG1 to ARG9 are loaded from the parameters that follow it on the command line.
Any existing contents of the ARG variables are saved and restored across a
`call` command.
Because the parameters are stored in ordinary string variables, they may be
dereferenced by macro expansion (analogous to the old-style deprecated syntax).
However in many cases it is more natural to use them as you would any other
variable.
?call example
?commands call example
Call site
MYFILE = "script1.gp"
FUNC = "sin(x)"
call MYFILE FUNC 1.23 "This is a plot title"
Upon entry to the called script
ARG0 holds "script1.gp"
ARG1 holds the string "sin(x)"
ARG2 holds the string "1.23"
ARG3 holds the string "This is a plot title"
ARGC is 3
The script itself can now execute
plot @ARG1 with lines title ARG3
print ARG2 * 4.56, @ARG2 * 4.56
print "This plot produced by script ", ARG0
Notice that ARG1 must be dereferenced as a macro, but ARG2 may be dereferenced
either as a macro (yielding a numerical constant) or a variable (yielding that
same numerical value after auto-promotion of the string "1.23" to a real).
The same result could be obtained directly from a shell script by invoking
gnuplot with the `-c` command line option:
gnuplot -persist -c "script1.gp" "sin(x)" 1.23 "This is a plot title"
?commands call old-style
?call old-style
This describes the call mechanism used by older versions of gnuplot, now
deprecated.
call "<input-file>" <param-0> <param-1> ... <param-9>
The name of the input file must be enclosed in quotes.
As each line is read from the input file, it is scanned for the following
special character sequences: $0 $1 $2 $3 $4 $5 $6 $7 $8 $9 $#. If found, the
sequence `$`+digit is replaced by the corresponding parameter from the `call`
command line. Quote characters are not copied and string variable substitution
is not performed. The character sequence `$#` is replaced by the number of
passed parameters. `$` followed by any other character is treated as an escape
sequence; use `$$` to get a single `$`.
Example:
If the file 'calltest.gp' contains the line:
print "argc=$# p0=$0 p1=$1 p2=$2 p3=$3 p4=$4 p5=$5 p6=$6 p7=x$7x"
entering the command:
call 'calltest.gp' "abcd" 1.2 + "'quoted'" -- "$2"
will display:
argc=7 p0=abcd p1=1.2 p2=+ p3='quoted' p4=- p5=- p6=$2 p7=xx
NOTES: This use of the `$` character conflicts both with gnuplot's own syntax
for datafile columns and with the use of `$` to indicate environmental
variables in a unix-like shell. The special sequence `$#` was mis-interpreted
as a comment delimiter in gnuplot versions 4.5 through 4.6.3. Quote characters
are ignored during substitution, so string constants are easily corrupted.
?commands clear
?clear
?inset
The `clear` command erases the current screen or output device as specified
by `set terminal` and `set output`. This usually generates a formfeed on
hardcopy devices.
For some terminals `clear` erases only the portion of the plotting surface
defined by `set size`, so for these it can be used in conjunction with `set
multiplot` to create an inset.
Example:
set multiplot
plot sin(x)
set origin 0.5,0.5
set size 0.4,0.4
clear
plot cos(x)
unset multiplot
Please see `set multiplot`, `set size`, and `set origin` for details.
?commands continue
?continue
The `continue` command is only meaningful inside the bracketed iteration clause
of a `do` or `while` statement. It causes the remaining statements inside the
bracketed clause to be skipped. Execution resumes at the start of the next
iteration (if any remain in the loop condition). See also `break`.
?commands do
?do
Syntax:
do for <iteration-spec> {
<commands>
<commands>
}
Execute a sequence of commands multiple times. The commands must be enclosed
in curly brackets, and the opening "{" must be on the same line as the `do`
keyword. This command cannot be used with old-style (un-bracketed) if/else
statements. See `if`. For examples of iteration specifiers, see `iteration`.
Example:
set multiplot layout 2,2
do for [name in "A B C D"] {
filename = name . ".dat"
set title sprintf("Condition %s",name)
plot filename title name
}
unset multiplot
See also `while`, `continue`, `break`.
?commands evaluate
?evaluate
The `evaluate` command executes the commands given as an argument string.
Newline characters are not allowed within the string.
Syntax:
eval <string expression>
This is especially useful for a repetition of similar commands.
Example:
set_label(x, y, text) \
= sprintf("set label '%s' at %f, %f point pt 5", text, x, y)
eval set_label(1., 1., 'one/one')
eval set_label(2., 1., 'two/one')
eval set_label(1., 2., 'one/two')
Please see `substitution macros` for another way to execute commands
from a string.
?commands exit
?exit
exit
exit message "error message text"
exit status <integer error code>
The commands `exit` and `quit`, as well as the END-OF-FILE character (usually
Ctrl-D) terminate input from the current input stream: terminal session, pipe,
or file input (pipe). If input streams are nested (inherited `load` scripts),
then reading will continue in the parent stream. When the top level stream is
closed, the program itself will exit.
The command `exit gnuplot` will immediately and unconditionally cause gnuplot
to exit even if the input stream is multiply nested. In this case any open
output files may not be completed cleanly. Example of use:
bind "ctrl-x" "unset output; exit gnuplot"
The command `exit error "error message"` simulates a program error.
In interactive mode it prints the error message and returns to the command
line, breaking out of all nested loops or calls. In non-interactive mode
the program will exit.
When gnuplot exits to the controlling shell, the return value is not usually
informative. This variant of the command allows you to return a specific value.
exit status <value>
See help for `batch/interactive` for more details.
?commands fit
?fit
?least-squares
?Marquardt
The `fit` command fits a user-supplied real-valued expression to a set of
data points, using the nonlinear least-squares Marquardt-Levenberg
algorithm. There can be up to 12 independent variables, there is always 1
dependent variable, and any number of parameters can be fitted.
Optionally, error estimates can be input for weighting the data points.
The basic use of `fit` is best explained by a simple example:
f(x) = a + b*x + c*x**2
fit f(x) 'measured.dat' using 1:2 via a,b,c
plot 'measured.dat' u 1:2, f(x)
Syntax:
fit {<ranges>} <expression>
'<datafile>' {datafile-modifiers}
{{unitweights} | {y|xy|z}error | errors <var1>{,<var2>,...}}
via '<parameter file>' | <var1>{,<var2>,...}
Ranges may be specified to filter the data used in fitting.
Out-of-range data points are ignored. The syntax is
[{dummy_variable=}{<min>}{:<max>}],
analogous to `plot`; see `plot ranges`.
<expression> can be any valid `gnuplot` expression, although the most common is
a previously user-defined function of the form f(x) or f(x,y). It must be
real-valued.
The names of the independent variables are set by the `set dummy` command,
or in the <ranges> part of the command (see below); by default, the first
two are called x and y.
Furthermore, the expression should depend on one or more variables whose
value is to be determined by the fitting procedure.
<datafile> is treated as in the `plot` command. All the `plot datafile`
modifiers (`using`, `every`,...) except `smooth` are applicable to `fit`.
See `plot datafile`.
The datafile contents can be interpreted flexibly by providing a `using`
qualifier as with plot commands. For example to generate the independent
variable x as the sum of columns 2 and 3, while taking z from column 6 and
requesting equal weights:
fit ... using ($2+$3):6
In the absence of a `using` specification, the fit implicitly assumes
there is only a single independent variable. If the file itself, or the
using specification, contains only a single column of data, the line
number is taken as the independent variable.
If a `using` specification is given, there can be up to 12 independent
variables (and more if specially configured at compile time).
The `unitweights` option, which is the default, causes all data points to be
weighted equally. This can be changed by using the `errors` keyword to read
error estimates of one or more of the variables from the data file. These
error estimates are interpreted as the standard deviation s of the
corresponding variable value and used to compute a weight for the datum as
1/s**2.
In case of error estimates of the independent variables, these weights are
further multiplied by fitting function derivatives according to the
"effective variance method" (Jay Orear, Am. J. Phys., Vol. 50, 1982).
The `errors` keyword is to be followed by a comma-separated list of one or
more variable names for which errors are to be input; the dependent variable
z must always be among them, while independent variables are optional.
For each variable in this list, an additional column will be read from the
file, containing that variable's error estimate. Again, flexible
interpretation is possible by providing the `using` qualifier.
Note that the number of independent variables is thus implicitly given by the
total number of columns in the `using` qualifier, minus 1 (for the dependent
variable), minus the number of variables in the `errors` qualifier.
As an example, if one has 2 independent variables, and errors for the
first independent variable and the dependent variable, one uses
the `errors x,z` qualifier, and a `using` qualifier with 5 columns,
which are interpreted as x:y:z:sx:sz (where x and y are the independent
variables, z the dependent variable, and sx and sz the standard
deviations of x and z).
A few shorthands for the `errors` qualifier are available:
`yerrors` (for fits with 1 column of independent variable), and
`zerrors` (for the general case) are all equivalent to `errors z`,
indicating that there is a single extra column with errors of the
dependent variable.
`xyerrors`, for the case of 1 independent variable, indicates that there
are two extra columns, with errors of both the independent and the
dependent variable. In this case the errors on x and y are treated by
Orear's effective variance method.
Note that `yerror` and `xyerror` are similar in both form and interpretation
to the `yerrorlines` and `xyerrorlines` 2D plot styles.
With the command `set fit v4` the fit command syntax is compatible with
`gnuplot` version 4 and before. Then there must be two more `using`
qualifiers (z and s) than there are independent variables, unless there is
only one variable. `gnuplot` then uses the following formats, depending on
the number of columns given in the `using` specification:
z # 1 independent variable (line number)
x:z # 1 independent variable (1st column)
x:z:s # 1 independent variable (3 columns total)
x:y:z:s # 2 independent variables (4 columns total)
x1:x2:x3:z:s # 3 independent variables (5 columns total)
x1:x2:x3:...:xN:z:s # N independent variables (N+2 columns total)
Please beware that this means that you have to supply z-errors s in a fit with
two or more independent variables. If you want unit weights you need to supply
them explicitly by using e.g. then format x:y:z:(1).
The dummy variable names may be changed when specifying a range as noted above.
The first range corresponds to the first `using` spec, and so on. A range may
also be given for z (the dependent variable), in which case data points for
which f(x,...) is out of the z range will not contribute to the residual being
minimized.
Multiple datasets may be simultaneously fit with functions of one
independent variable by making y a 'pseudo-variable', e.g., the dataline
number, and fitting as two independent variables. See `fit multi-branch`.
The `via` qualifier specifies which parameters are to be optimized, either
directly, or by referencing a parameter file.
Examples:
f(x) = a*x**2 + b*x + c
g(x,y) = a*x**2 + b*y**2 + c*x*y
set fit limit 1e-6
fit f(x) 'measured.dat' via 'start.par'
fit f(x) 'measured.dat' using 3:($7-5) via 'start.par'
fit f(x) './data/trash.dat' using 1:2:3 yerror via a, b, c
fit g(x,y) 'surface.dat' using 1:2:3 via a, b, c
fit a0 + a1*x/(1 + a2*x/(1 + a3*x)) 'measured.dat' via a0,a1,a2,a3
fit a*x + b*y 'surface.dat' using 1:2:3 via a,b
fit [*:*][yaks=*:*] a*x+b*yaks 'surface.dat' u 1:2:3 via a,b
fit [][][t=*:*] a*x + b*y + c*t 'foo.dat' using 1:2:3:4 via a,b,c
set dummy x1, x2, x3, x4, x5
h(x1,x2,x3,x4,s5) = a*x1 + b*x2 + c*x3 + d*x4 + e*x5
fit h(x1,x2,x3,x4,x5) 'foo.dat' using 1:2:3:4:5:6 via a,b,c,d,e
After each iteration step, detailed information about the current state
of the fit is written to the display. The same information about the
initial and final states is written to a log file, "fit.log". This file
is always appended to, so as to not lose any previous fit history; it
should be deleted or renamed as desired. By using the command
`set fit logfile`, the name of the log file can be changed.
If activated by using `set fit errorvariables`, the error for each fitted
parameter will be stored in a variable named like the parameter, but with
"_err" appended. Thus the errors can be used as input for further
computations.
If `set fit prescale` is activated, fit parameters are prescaled by
their initial values. This helps the Marquardt-Levenberg routine
converge more quickly and reliably in cases where parameters differ
in size by several orders of magnitude.
The fit may be interrupted by pressing Ctrl-C (Ctrl-Break in wgnuplot).
After the current iteration completes, you have the option to
(1) stop the fit and accept the current parameter values,
(2) continue the fit,
(3) execute a `gnuplot` command as specified by `set fit script` or the
environment variable `FIT_SCRIPT`. The default is `replot`, so if you
had previously plotted both the data and the fitting function in one graph,
you can display the current state of the fit.
Once `fit` has finished, the `save fit` command may be used to store final
values in a file for subsequent use as a parameter file. See `save fit`
for details.
?commands fit parameters
?fit parameters
?commands fit adjustable_parameters
?fit adjustable_parameters
?fit_parameters
There are two ways that `via` can specify the parameters to be adjusted,
either directly on the command line or indirectly, by referencing a
parameter file. The two use different means to set initial values.
Adjustable parameters can be specified by a comma-separated list of variable
names after the `via` keyword. Any variable that is not already defined
is created with an initial value of 1.0. However, the fit is more likely
to converge rapidly if the variables have been previously declared with more
appropriate starting values.
In a parameter file, each parameter to be varied and a corresponding initial
value are specified, one per line, in the form
varname = value
Comments, marked by '#', and blank lines are permissible. The
special form
varname = value # FIXED
means that the variable is treated as a 'fixed parameter', initialized by the
parameter file, but not adjusted by `fit`. For clarity, it may be useful to
designate variables as fixed parameters so that their values are reported by
`fit`. The keyword `# FIXED` has to appear in exactly this form.
?commands fit beginners_guide
?fit beginners_guide
?fit guide
?fitting
`fit` is used to find a set of parameters that 'best' fits your data to your
user-defined function. The fit is judged on the basis of the sum of the
squared differences or 'residuals' (SSR) between the input data points and
the function values, evaluated at the same places. This quantity is often
called 'chisquare' (i.e., the Greek letter chi, to the power of 2). The
algorithm attempts to minimize SSR, or more precisely, WSSR, as the residuals
are 'weighted' by the input data errors (or 1.0) before being squared;
see `fit error_estimates` for details.
That's why it is called 'least-squares fitting'. Let's look at an example
to see what is meant by 'non-linear', but first we had better go over some
terms. Here it is convenient to use z as the dependent variable for
user-defined functions of either one independent variable, z=f(x), or two
independent variables, z=f(x,y). A parameter is a user-defined variable
that `fit` will adjust, i.e., an unknown quantity in the function
declaration. Linearity/non-linearity refers to the relationship of the
dependent variable, z, to the parameters which `fit` is adjusting, not of
z to the independent variables, x and/or y. (To be technical, the
second {and higher} derivatives of the fitting function with respect to
the parameters are zero for a linear least-squares problem).
For linear least-squares (LLS), the user-defined function will be a sum of
simple functions, not involving any parameters, each multiplied by one
parameter. NLLS handles more complicated functions in which parameters can
be used in a large number of ways. An example that illustrates the
difference between linear and nonlinear least-squares is the Fourier series.
One member may be written as
z=a*sin(c*x) + b*cos(c*x).
If a and b are the unknown parameters and c is constant, then estimating
values of the parameters is a linear least-squares problem. However, if
c is an unknown parameter, the problem is nonlinear.
In the linear case, parameter values can be determined by comparatively
simple linear algebra, in one direct step. However LLS is a special case
which is also solved along with more general NLLS problems by the iterative
procedure that `gnuplot` uses. `fit` attempts to find the minimum by doing
a search. Each step (iteration) calculates WSSR with a new set of parameter
values. The Marquardt-Levenberg algorithm selects the parameter values for
the next iteration. The process continues until a preset criterion is met,
either (1) the fit has "converged" (the relative change in WSSR is less than
a certain limit, see `set fit limit`), or (2) it reaches a preset iteration
count limit (see `set fit maxiter`). The fit may also be interrupted
and subsequently halted from the keyboard (see `fit`). The user variable
FIT_CONVERGED contains 1 if the previous fit command terminated due to
convergence; it contains 0 if the previous fit terminated for any other
reason. FIT_NITER contains the number of iterations that were done during the last fit.
Often the function to be fitted will be based on a model (or theory) that
attempts to describe or predict the behaviour of the data. Then `fit` can
be used to find values for the free parameters of the model, to determine
how well the data fits the model, and to estimate an error range for each
parameter. See `fit error_estimates`.
Alternatively, in curve-fitting, functions are selected independent of
a model (on the basis of experience as to which are likely to describe
the trend of the data with the desired resolution and a minimum number
of parameters*functions.) The `fit` solution then provides an analytic
representation of the curve.
However, if all you really want is a smooth curve through your data points,
the `smooth` option to `plot` may be what you've been looking for rather
than `fit`.
?commands fit error_estimates
?fit error_estimates
?fit errors
In `fit`, the term "error" is used in two different contexts, data error
estimates and parameter error estimates.
Data error estimates are used to calculate the relative weight of each data
point when determining the weighted sum of squared residuals, WSSR or
chisquare. They can affect the parameter estimates, since they determine
how much influence the deviation of each data point from the fitted function
has on the final values. Some of the `fit` output information, including
the parameter error estimates, is more meaningful if accurate data error
estimates have been provided.
The `statistical overview` describes some of the `fit` output and gives some
background for the 'practical guidelines'.
?commands fit error statistical_overview
?fit error statistical_overview
?statistical_overview
The theory of non-linear least-squares (NLLS) is generally described in terms
of a normal distribution of errors, that is, the input data is assumed to be
a sample from a population having a given mean and a Gaussian (normal)
distribution about the mean with a given standard deviation. For a sample of
sufficiently large size, and knowing the population standard deviation, one
can use the statistics of the chisquare distribution to describe a "goodness
of fit" by looking at the variable often called "chisquare". Here, it is
sufficient to say that a reduced chisquare (chisquare/degrees of freedom,
where degrees of freedom is the number of datapoints less the number of
parameters being fitted) of 1.0 is an indication that the weighted sum of
squared deviations between the fitted function and the data points is the
same as that expected for a random sample from a population characterized by
the function with the current value of the parameters and the given standard
deviations.
If the standard deviation for the population is not constant, as in counting
statistics where variance = counts, then each point should be individually
weighted when comparing the observed sum of deviations and the expected sum
of deviations.
At the conclusion `fit` reports 'stdfit', the standard deviation of the fit,
which is the rms of the residuals, and the variance of the residuals, also
called 'reduced chisquare' when the data points are weighted. The number of
degrees of freedom (the number of data points minus the number of fitted
parameters) is used in these estimates because the parameters used in
calculating the residuals of the datapoints were obtained from the same data.
If the data points have weights, `gnuplot` calculates the so-called p-value,
i.e. one minus the cumulative distribution function of the
chisquare-distribution for the number of degrees of freedom and the resulting
chisquare, see `practical_guidelines`.
These values are exported to the variables
FIT_NDF = Number of degrees of freedom
FIT_WSSR = Weighted sum-of-squares residual
FIT_STDFIT = sqrt(WSSR/NDF)
FIT_P = p-value
To estimate confidence levels for the parameters, one can use the minimum
chisquare obtained from the fit and chisquare statistics to determine the
value of chisquare corresponding to the desired confidence level, but
considerably more calculation is required to determine the combinations of
parameters which produce such values.
Rather than determine confidence intervals, `fit` reports parameter error
estimates which are readily obtained from the variance-covariance matrix
after the final iteration. By convention, these estimates are called
"standard errors" or "asymptotic standard errors", since they are calculated
in the same way as the standard errors (standard deviation of each parameter)
of a linear least-squares problem, even though the statistical conditions for
designating the quantity calculated to be a standard deviation are not
generally valid for the NLLS problem. The asymptotic standard errors are
generally over-optimistic and should not be used for determining confidence
levels, but are useful for qualitative purposes.
The final solution also produces a correlation matrix indicating correlation of
parameters in the region of the solution; The main diagonal elements,
autocorrelation, are always 1; if all parameters were independent, the
off-diagonal elements would be nearly 0. Two variables which completely
compensate each other would have an off-diagonal element of unit magnitude,
with a sign depending on whether the relation is proportional or inversely
proportional. The smaller the magnitudes of the off-diagonal elements, the
closer the estimates of the standard deviation of each parameter would be to
the asymptotic standard error.
?commands fit error practical_guidelines
?fit error practical_guidelines
?practical_guidelines
?guidelines
If you have a basis for assigning weights to each data point, doing so lets
you make use of additional knowledge about your measurements, e.g., take into
account that some points may be more reliable than others. That may affect
the final values of the parameters.
Weighting the data provides a basis for interpreting the additional `fit`
output after the last iteration. Even if you weight each point equally,
estimating an average standard deviation rather than using a weight of 1
makes WSSR a dimensionless variable, as chisquare is by definition.
Each fit iteration will display information which can be used to evaluate
the progress of the fit. (An '*' indicates that it did not find a smaller
WSSR and is trying again.) The 'sum of squares of residuals', also called
'chisquare', is the WSSR between the data and your fitted function; `fit`
has minimized that. At this stage, with weighted data, chisquare is expected
to approach the number of degrees of freedom (data points minus parameters).
The WSSR can be used to calculate the reduced chisquare (WSSR/ndf) or stdfit,
the standard deviation of the fit, sqrt(WSSR/ndf). Both of these are
reported for the final WSSR.
If the data are unweighted, stdfit is the rms value of the deviation of the
data from the fitted function, in user units.
If you supplied valid data errors, the number of data points is large enough,
and the model is correct, the reduced chisquare should be about unity. (For
details, look up the 'chi-squared distribution' in your favorite statistics
reference.) If so, there are additional tests, beyond the scope of this
overview, for determining how well the model fits the data.
A reduced chisquare much larger than 1.0 may be due to incorrect data error
estimates, data errors not normally distributed, systematic measurement
errors, 'outliers', or an incorrect model function. A plot of the residuals,
e.g., `plot 'datafile' using 1:($2-f($1))`, may help to show any systematic
trends. Plotting both the data points and the function may help to suggest
another model.
Similarly, a reduced chisquare less than 1.0 indicates WSSR is less than that
expected for a random sample from the function with normally distributed
errors. The data error estimates may be too large, the statistical
assumptions may not be justified, or the model function may be too general,
fitting fluctuations in a particular sample in addition to the underlying
trends. In the latter case, a simpler function may be more appropriate.
The p-value of the fit is one minus the cumulative distribution function of
the chisquare-distribution for the number of degrees of freedom and the
resulting chisquare. This can serve as a measure of the goodness-of-fit.
The range of the p-value is between zero and one. A very small or large
p-value indicates that the model does not describe the data and its errors
well. As described above, this might indicate a problem with the data, its
errors or the model, or a combination thereof. A small p-value might
indicate that the errors have been underestimated and the errors of the
final parameters should thus be scaled. See also `set fit errorscaling`.
You'll have to get used to both `fit` and the kind of problems you apply it
to before you can relate the standard errors to some more practical estimates
of parameter uncertainties or evaluate the significance of the correlation
matrix.
Note that `fit`, in common with most NLLS implementations, minimizes the
weighted sum of squared distances (y-f(x))**2. It does not provide any means
to account for "errors" in the values of x, only in y. Also, any "outliers"
(data points outside the normal distribution of the model) will have an
exaggerated effect on the solution.
?commands fit control
?fit control
Settings of the `fit` command are controlled by `set fit`. The old `gnuplot`
user variables are deprecated as of version 5, see `fit control variables`.
There are a number of environment variables that can be defined to affect
`fit` before starting `gnuplot`, see `fit control environment`.
?commands fit control variables
?fit control variables
The user defined variables described here are deprecated, see `set fit`.
The default epsilon limit (1e-5) may be changed by declaring a value for
FIT_LIMIT
When the sum of squared residuals changes between two iteration steps by
a factor less than this number (epsilon), the fit is considered to have
'converged'.
The maximum number of iterations may be limited by declaring a value for
FIT_MAXITER
A value of 0 (or not defining it at all) means that there is no limit.
If you need even more control about the algorithm, and know the
Marquardt-Levenberg algorithm well, there are some more variables to
influence it. The startup value of `lambda` is normally calculated
automatically from the ML-matrix, but if you want to, you may provide
your own one with
FIT_START_LAMBDA
Specifying FIT_START_LAMBDA as zero or less will re-enable the automatic
selection. The variable
FIT_LAMBDA_FACTOR
gives the factor by which `lambda` is increased or decreased whenever
the chi-squared target function increased or decreased significantly.
Setting FIT_LAMBDA_FACTOR to zero re-enables the default factor of
10.0.
Other variables with the FIT_ prefix may be added to `fit`, so it is safer
not to use that prefix for user-defined variables.
The variables FIT_SKIP and FIT_INDEX were used by earlier releases of
`gnuplot` with a 'fit' patch called `gnufit` and are no longer available.
The datafile `every` modifier provides the functionality of FIT_SKIP.
FIT_INDEX was used for multi-branch fitting, but multi-branch fitting of
one independent variable is now done as a pseudo-3D fit in which the
second independent variable and `using` are used to specify the branch.
See `fit multi-branch`.
?commands fit control environment
?fit control environment
The environment variables must be defined before `gnuplot` is executed; how
to do so depends on your operating system.
FIT_LOG
changes the name (and/or path) of the file to which the fit log will be
written from the default of "fit.log" in the working directory. The default
value can be overwritten using the command `set fit logfile`.
FIT_SCRIPT
specifies a command that may be executed after an user interrupt. The default
is `replot`, but a `plot` or `load` command may be useful to display a plot
customized to highlight the progress of the fit. This setting can also be
changed using `set fit script`.
?commands fit multi-branch
?fit multi-branch
?multi-branch
?branch
In multi-branch fitting, multiple data sets can be simultaneously fit with
functions of one independent variable having common parameters by minimizing
the total WSSR. The function and parameters (branch) for each data set are
selected by using a 'pseudo-variable', e.g., either the dataline number (a
'column' index of -1) or the datafile index (-2), as the second independent
variable.
Example: Given two exponential decays of the form, z=f(x), each describing
a different data set but having a common decay time, estimate the values of
the parameters. If the datafile has the format x:z:s, then
f(x,y) = (y==0) ? a*exp(-x/tau) : b*exp(-x/tau)
fit f(x,y) 'datafile' using 1:-2:2:3 via a, b, tau
For a more complicated example, see the file "hexa.fnc" used by the
"fit.dem" demo.
Appropriate weighting may be required since unit weights may cause one
branch to predominate if there is a difference in the scale of the dependent
variable. Fitting each branch separately, using the multi-branch solution
as initial values, may give an indication as to the relative effect of each
branch on the joint solution.
?commands fit starting_values
?fit starting_values
?starting_values
Nonlinear fitting is not guaranteed to converge to the global optimum (the
solution with the smallest sum of squared residuals, SSR), and can get stuck
at a local minimum. The routine has no way to determine that; it is up to
you to judge whether this has happened.
`fit` may, and often will get "lost" if started far from a solution, where
SSR is large and changing slowly as the parameters are varied, or it may
reach a numerically unstable region (e.g., too large a number causing a
floating point overflow) which results in an "undefined value" message
or `gnuplot` halting.
To improve the chances of finding the global optimum, you should set the
starting values at least roughly in the vicinity of the solution, e.g.,
within an order of magnitude, if possible. The closer your starting values
are to the solution, the less chance of stopping at a false minimum. One way
to find starting values is to plot data and the fitting function on the same
graph and change parameter values and `replot` until reasonable similarity
is reached. The same plot is also useful to check whether the fit found a
false minimum.
Of course finding a nice-looking fit does not prove there is no "better" fit
(in either a statistical sense, characterized by an improved goodness-of-fit
criterion, or a physical sense, with a solution more consistent with the
model.) Depending on the problem, it may be desirable to `fit` with various
sets of starting values, covering a reasonable range for each parameter.
?commands fit tips
?fit tips
?tips
Here are some tips to keep in mind to get the most out of `fit`. They're not
very organized, so you'll have to read them several times until their essence
has sunk in.
The two forms of the `via` argument to `fit` serve two largely distinct
purposes. The `via "file"` form is best used for (possibly unattended) batch
operation, where you supply the starting parameter values in a file.
The `via var1, var2, ...` form is best used interactively, where the command
history mechanism may be used to edit the list of parameters to be fitted or
to supply new startup values for the next try. This is particularly useful
for hard problems, where a direct fit to all parameters at once won't work
without good starting values. To find such, you can iterate several times,
fitting only some of the parameters, until the values are close enough to the
goal that the final fit to all parameters at once will work.
Make sure that there is no mutual dependency among parameters of the function
you are fitting. For example, don't try to fit a*exp(x+b), because
a*exp(x+b)=a*exp(b)*exp(x). Instead, fit either a*exp(x) or exp(x+b).
A technical issue: The larger the ratio of the largest and the
smallest absolute parameter values, the slower the fit will converge.
If the ratio is close to or above the inverse of the machine floating
point precision, it may take next to forever to converge, or refuse
to converge at all. You will either have to adapt your function to avoid
this, e.g., replace 'parameter' by '1e9*parameter' in the function
definition, and divide the starting value by 1e9 or use `set fit prescale`
which does this internally according to the parameter starting values.
If you can write your function as a linear combination of simple functions
weighted by the parameters to be fitted, by all means do so. That helps a
lot, because the problem is no longer nonlinear and should converge with only
a small number of iterations, perhaps just one.
Some prescriptions for analysing data, given in practical experimentation
courses, may have you first fit some functions to your data, perhaps in a
multi-step process of accounting for several aspects of the underlying
theory one by one, and then extract the information you really wanted from
the fitting parameters of those functions. With `fit`, this may often be
done in one step by writing the model function directly in terms of the
desired parameters. Transforming data can also quite often be avoided,
though sometimes at the cost of a more difficult fit problem. If you think
this contradicts the previous paragraph about simplifying the fit function,
you are correct.
A "singular matrix" message indicates that this implementation of the
Marquardt-Levenberg algorithm can't calculate parameter values for the next
iteration. Try different starting values, writing the function in another
form, or a simpler function.
Finally, a nice quote from the manual of another fitting package (fudgit),
that kind of summarizes all these issues: "Nonlinear fitting is an art!"
?commands help
?help
The `help` command displays built-in help. To specify information on a
particular topic use the syntax:
help {<topic>}
If <topic> is not specified, a short message is printed about `gnuplot`.
After help for the requested topic is given, a menu of subtopics is given;
help for a subtopic may be requested by typing its name, extending the help
request. After that subtopic has been printed, the request may be extended
again or you may go back one level to the previous topic. Eventually, the
`gnuplot` command line will return.
If a question mark (?) is given as the topic, the list of topics currently
available is printed on the screen.
?commands history
?history
The `history` command prints or saves previous commands in the history list,
or reexecutes a previous entry in the list. To modify the behavior of this
command, see `set history`.
Input lines with `history` as their first command are not stored in the
command history.
Examples:
history # show the complete history
history 5 # show last 5 entries in the history
history quiet 5 # show last 5 entries without entry numbers
history "hist.gp" # write the complete history to file hist.gp
history "hist.gp" append # append the complete history to file hist.gp
history 10 "hist.gp" # write last 10 commands to file hist.gp
history 10 "|head -5 >>diary.gp" # write 5 history commands using pipe
history ?load # show all history entries starting with "load"
history ?"set c" # like above, several words enclosed in quotes
hi !reread # execute last entry starting with "reread"
hist !"set xr" # like above, several words enclosed in quotes
hist !55 # reexecute the command at history entry 55
?commands if
?if
New syntax:
if (<condition>) { <commands>;
<commands>
<commands>
} else {
<commands>
}
Old syntax:
if (<condition>) <command-line> [; else if (<condition>) ...; else ...]
This version of gnuplot supports block-structured if/else statements. If the
keyword `if` or `else` is immediately followed by an opening "{", then
conditional execution applies to all statements, possibly on multiple input
lines, until a matching "}" terminates the block. If commands may be nested.
The old single-line if/else syntax is still supported, but can not be
mixed with the new block-structured syntax. See `if-old`.
?if if-old
?if-old
Through gnuplot version 4.4, the scope of the if/else commands was limited to
a single input line. Now a multi-line clause may be enclosed in curly brackets.
The old syntax is still honored but cannot be used inside a bracketed clause.
If no opening "{" follows the `if` keyword, the command(s) in <command-line>
will be executed if <condition> is true (non-zero) or skipped if <condition> is
false (zero). Either case will consume commands on the input line until the
end of the line or an occurrence of `else`. Note that use of `;` to allow
multiple commands on the same line will _not_ end the conditionalized commands.
Examples:
pi=3
if (pi!=acos(-1)) print "?Fixing pi!"; pi=acos(-1); print pi
will display:
?Fixing pi!
3.14159265358979
but
if (1==2) print "Never see this"; print "Or this either"
will not display anything.
else:
v=0
v=v+1; if (v%2) print "2" ; else if (v%3) print "3"; else print "fred"
(repeat the last line repeatedly!)
?for
The `plot`, `splot`, `set` and `unset` commands may optionally contain an
iteration for clause. This has the effect of executing the basic command
multiple times, each time re-evaluating any expressions that make use of the
iteration control variable. Iteration of arbitrary command sequences can be
requested using the `do` command.
Two forms of iteration clause are currently supported:
for [intvar = start:end{:increment}]
for [stringvar in "A B C D"]
Examples:
plot for [filename in "A.dat B.dat C.dat"] filename using 1:2 with lines
plot for [basename in "A B C"] basename.".dat" using 1:2 with lines
set for [i = 1:10] style line i lc rgb "blue"
unset for [tag = 100:200] label tag
Nested iteration is supported:
set for [i=1:9] for [j=1:9] label i*10+j sprintf("%d",i*10+j) at i,j
See additional documentation for `iteration`, `do`.
?commands import
?import
The `import` command associates a user-defined function name with a function
exported by an external shared object. This constitutes a plugin mechanism
that extends the set of functions available in gnuplot.
Syntax:
import func(x[,y,z,...]) from "sharedobj[:symbol]"
Examples:
# make the function myfun, exported by "mylib.so" or "mylib.dll"
# available for plotting or numerical calculation in gnuplot
import myfun(x) from "mylib"
import myfun(x) from "mylib:myfun" # same as above
# make the function theirfun, defined in "theirlib.so" or "theirlib.dll"
# available under a different name
import myfun(x,y,z) from "theirlib:theirfun"
The program extends the name given for the shared object by either ".so" or
".dll" depending on the operating system, and searches for it first as a full
path name and then as a path relative to the current directory. The operating
system itself may also search any directories in LD_LIBRARY_PATH or
DYLD_LIBRARY_PATH.
?commands load
?load
The `load` command executes each line of the specified input file as if it
had been typed in interactively. Files created by the `save` command can
later be `load`ed. Any text file containing valid commands can be created
and then executed by the `load` command. Files being `load`ed may themselves
contain `load` or `call` commands. See `comments` for information about
comments in commands. To `load` with arguments, see `call`.
Syntax:
load "<input-file>"
The name of the input file must be enclosed in quotes.
The special filename "-" may be used to `load` commands from standard input.
This allows a `gnuplot` command file to accept some commands from standard
input. Please see help for `batch/interactive` for more details.
On some systems which support a popen function (Unix), the load file can be
read from a pipe by starting the file name with a '<'.
Examples:
load 'work.gnu'
load "func.dat"
load "< loadfile_generator.sh"
The `load` command is performed implicitly on any file names given as
arguments to `gnuplot`. These are loaded in the order specified, and
then `gnuplot` exits.
See `raise`.
?commands pause
?pause
?pause mouse
The `pause` command displays any text associated with the command and then
waits a specified amount of time or until the carriage return is pressed.
`pause` is especially useful in conjunction with `load` files.
Syntax:
pause <time> {"<string>"}
pause mouse {<endcondition>}{, <endcondition>} {"<string>"}
<time> may be any constant or floating-point expression. `pause -1` will wait
until a carriage return is hit, zero (0) won't pause at all, and a positive
number will wait the specified number of seconds.
`pause 0` is synonymous with `print`.
If the current terminal supports `mousing`, then `pause mouse` will terminate
on either a mouse click or on ctrl-C. For all other terminals, or if mousing
is not active, `pause mouse` is equivalent to `pause -1`.
If one or more end conditions are given after `pause mouse`, then any one of
the conditions will terminate the pause. The possible end conditions are
`keypress`, `button1`, `button2`, `button3`, `close`, and `any`.
If the pause terminates on a keypress, then the ascii value of the key pressed
is returned in MOUSE_KEY. The character itself is returned as a one character
string in MOUSE_CHAR. Hotkeys (bind command) are disabled if keypress is one of
the end conditions. Zooming is disabled if button3 is one of the end
conditions.
In all cases the coordinates of the mouse are returned in variables MOUSE_X,
MOUSE_Y, MOUSE_X2, MOUSE_Y2. See `mouse variables`.
Note: Since `pause` communicates with the operating system rather than the
graphics, it may behave differently with different device drivers (depending
upon how text and graphics are mixed).
Examples:
pause -1 # Wait until a carriage return is hit
pause 3 # Wait three seconds
pause -1 "Hit return to continue"
pause 10 "Isn't this pretty? It's a cubic spline."
pause mouse "Click any mouse button on selected data point"
pause mouse keypress "Type a letter from A-F in the active window"
pause mouse button1,keypress
pause mouse any "Any key or button will terminate"
The variant "pause mouse key" will resume after any keypress in the active
plot window. If you want to wait for a particular key to be pressed, you can
use a reread loop such as:
print "I will resume after you hit the Tab key in the plot window"
load "wait_for_tab"
File "wait_for_tab" contains the lines
pause mouse key
if (MOUSE_KEY != 9) reread
?commands plot
?plot
`plot` is the primary command for drawing plots with `gnuplot`. It offers
many different graphical representations for functions and data.
`plot` is used to draw 2D functions and data.
`splot` draws 2D projections of 3D surfaces and data.
Syntax:
plot {<ranges>} <plot-element> {, <plot-element>, <plot-element>}
Each plot element consists of a definition, a function, or a data source
together with optional properties or modifiers:
plot-element:
{<iteration>}
<definition> | {sampling-range} <function> | <data source>
{axes <axes>} {<title-spec>}
{with <style>}
The graphical representation of each plot element is determined by the keyword
`with`, e.g. `with lines` or `with boxplot`. See `plotting styles`.
The data to be plotted is either generated by a function (two functions if in
parametric mode), read from a data file, or read from a named data block that
was defined previously. Multiple datafiles, data blocks, and/or functions may
be plotted in a single plot command separated by commas.
See `data`, `inline data`, `functions`.
A plot-element that contains the definition of a function or variable does not
create any visible output, see third example below.
Examples:
plot sin(x)
plot sin(x), cos(x)
plot f(x) = sin(x*a), a = .2, f(x), a = .4, f(x)
plot "datafile.1" with lines, "datafile.2" with points
plot [t=1:10] [-pi:pi*2] tan(t), \
"data.1" using (tan($2)):($3/$4) smooth csplines \
axes x1y2 notitle with lines 5
plot for [datafile in "spinach.dat broccoli.dat"] datafile
See also `show plot`.
?commands plot axes
?plot axes
?axes
There are four possible sets of axes available; the keyword <axes> is used to
select the axes for which a particular line should be scaled. `x1y1` refers
to the axes on the bottom and left; `x2y2` to those on the top and right;
`x1y2` to those on the bottom and right; and `x2y1` to those on the top and
left. Ranges specified on the `plot` command apply only to the first set of
axes (bottom left).
?binary
?data binary
?datafile binary
?plot data binary
BINARY DATA FILES:
It is necessary to provide the keyword `binary` after the filename.
Adequate details of the file format must be given on the command line or
extracted from the file itself for a supported binary `filetype`.
In particular, there are two structures for binary files, binary matrix
format and binary general format.
The `binary matrix` format contains a two dimensional array of 32 bit IEEE
float values plus an additional column and row of coordinate values. In the
`using` specifier of a plot command, column 1 refers to the matrix row
coordinate, column 2 refers to the matrix column coordinate, and column 3
refers to the value stored in the array at those coordinates.
The `binary general` format contains an arbitrary number of columns for which
information must be specified at the command line. For example, `array`,
`record`, `format` and `using` can indicate the size, format and dimension
of data. There are a variety of useful commands for skipping file headers
and changing endianess. There are a set of commands for positioning and
translating data since often coordinates are not part of the file when uniform
sampling is inherent in the data. Unlike reading from a text or matrix binary
file, general binary does not treat the generated columns as 1, 2 or 3 in the
`using` list. Instead column 1 refers to column 1 of the file, or as specified
in the `format` list.
There are global default settings for the various binary options which may
be set using the same syntax as the options when used as part of the `(s)plot
<filename> binary ...` command. This syntax is `set datafile binary ...`.
The general rule is that common command-line specified parameters override
file-extracted parameters which override default parameters.
`Binary matrix` is the default binary format when no keywords specific to
`binary general` are given, i.e., `array`, `record`, `format`, `filetype`.
General binary data can be entered at the command line via the special file
name '-'. However, this is intended for use through a pipe where programs
can exchange binary data, not for keyboards. There is no "end of record"
character for binary data. Gnuplot continues reading from a pipe until it
has read the number of points declared in the `array` qualifier.
See `binary matrix` or `binary general` for more details.
The `index` keyword is not supported, since the file format allows only one
surface per file. The `every` and `using` filters are supported. `using`
operates as if the data were read in the above triplet form.
Binary File Splot Demo.
?commands plot binary general
?commands splot binary general
?plot binary general
?splot binary general
?datafile binary general
?data binary general
?binary general
The `binary` keyword appearing alone indicates a binary data file that
contains both coordinate information describing a non-uniform grid and
the value of each grid point (see `binary matrix`). Binary data in any other
format requires additional keywords to describe the layout of the data.
Unfortunately the syntax of these required additional keywords is convoluted.
Nevertheless the general binary mode is particularly useful for application
programs sending large amounts of data to gnuplot.
Syntax:
plot '<file_name>' {binary <binary list>} ...
splot '<file_name>' {binary <binary list>} ...
General binary format is activated by keywords in <binary list> pertaining
to information about file structure, i.e., `array`, `record`, `format` or
`filetype`. Otherwise, non-uniform matrix binary format is assumed.
(See `binary matrix` for more details.)
NB: In previous versions of gnuplot there have been some differences between
the interpretation of binary data keywords by `plot` and `splot`. Where the
meanings differ, one or both may change in a future gnuplot version.
Gnuplot knows how to read a few standard binary file types that are fully
self-describing, e.g. PNG images. Type `show datafile binary` at the
command line for a list. Apart from these, you can think of binary data
files as conceptually the same as text data. Each point has columns of
information which are selected via the `using` specification. If no `format`
string is specified, gnuplot will read in a number of binary values equal
to the largest column given in the `<using list>`. For example, `using 1:3`
will result in three columns being read, of which the second will be ignored.
Certain plot types have an associated default using specification.
For example, `with image` has a default of `using 1`, while `with rgbimage`
has a default of `using 1:2:3`.
?binary array
Describes the sampling array dimensions associated with the binary file.
The coordinates will be generated by gnuplot. A number must be specified
for each dimension of the array. For example, `array=(10,20)` means the
underlying sampling structure is two-dimensional with 10 points along the
first (x) dimension and 20 points along the second (y) dimension.
A negative number indicates that data should be read until the end of file.
If there is only one dimension, the parentheses may be omitted.
A colon can be used to separate the dimensions for multiple records.
For example, `array=25:35` indicates there are two one-dimensional records in
the file.
Note: Gnuplot version 4.2 used the syntax array=128x128 rather than
array=(128,128). The older syntax is now deprecated.
?binary record
This keyword serves the same function as `array` and has the same syntax.
However, `record` causes gnuplot to not generate coordinate information.
This is for the case where such information may be included in one of the
columns of the binary data file.
?binary skip
This keyword allows you to skip sections of a binary file. For instance, if the
file contains a 1024 byte header before the start of the data region you would
probably want to use
plot '<file_name>' binary skip=1024 ...
If there are multiple records in the file, you may specify a leading offset for
each. For example, to skip 512 bytes before the 1st record and 256 bytes before
the second and third records
plot '<file_name> binary record=356:356:356 skip=512:256:256 ...
?binary format
The default binary format is a float. For more flexibility, the format can
include details about variable sizes. For example, `format="%uchar%int%float"`
associates an unsigned character with the first using column, an int with the
second column and a float with the third column. If the number of size
specifications is less than the greatest column number, the size is implicitly
taken to be similar to the last given variable size.
Furthermore, similar to the `using` specification, the format can include
discarded columns via the `*` character and have implicit repetition via a
numerical repeat-field. For example, `format="%*2int%3float"` causes gnuplot
to discard two ints before reading three floats. To list variable sizes, type
`show datafile binary datasizes`. There are a group of names that are machine
dependent along with their sizes in bytes for the particular compilation.
There is also a group of names which attempt to be machine independent.
?binary endian
Often the endianess of binary data in the file does not agree with the
endianess used by the platform on which gnuplot is running. Several words can
direct gnuplot how to arrange bytes. For example `endian=little` means treat
the binary file as having byte significance from least to greatest. The options
are
little: least significant to greatest significance
big: greatest significance to least significance
default: assume file endianess is the same as compiler
swap (swab): Interchange the significance. (If things
don't look right, try this.)
Gnuplot can support "middle" ("pdp") endian if it is compiled with that option.
?binary filetype
?filetype
For some standard binary file formats gnuplot can extract all the necessary
information from the file in question. As an example, "format=edf" will read
ESRF Header File format files. For a list of the currently supported file
formats, type `show datafile binary filetypes`.
There is a special file type called `auto` for which gnuplot will check if the
binary file's extension is a quasi-standard extension for a supported format.
Command line keywords may be used to override settings extracted from the file.
The settings from the file override any defaults. See `set datafile binary`.
?binary filetype avs
?filetype avs
?avs
`avs` is one of the automatically recognized binary file types for images.
AVS is an extremely simple format, suitable mostly for streaming between
applications. It consists of 2 longs (xwidth, ywidth) followed by a stream
of pixels, each with four bytes of information alpha/red/green/blue.
?binary filetype edf
?filetype edf
?edf
?filetype ehf
?ehf
`edf` is one of the automatically recognized binary file types for images.
EDF stands for ESRF Data Format, and it supports both edf and ehf formats
(the latter means ESRF Header Format). More information on specifications
can be found at
http://www.edfplus.info/specs
?binary filetype png
?binary filetype gif
?binary filetype jpeg
?filetype png
?filetype gif
?filetype jpeg
If gnuplot was configured to use the libgd library for png/gif/jpeg output,
then it can also be used to read these same image types as binary files.
You can use an explicit command
plot 'file.png' binary filetype=png
Or the file type will be recognized automatically from the extension if you
have previously requested
set datafile binary filetype=auto
?binary keywords
The following keywords apply only when generating coordinates from binary
data files. That is, the control mapping the individual elements of a binary
array, matrix, or image to specific x/y/z positions.
?binary keywords scan
?scan
A great deal of confusion can arise concerning the relationship between how
gnuplot scans a binary file and the dimensions seen on the plot. To lessen
the confusion, conceptually think of gnuplot _always_ scanning the binary file
point/line/plane or fast/medium/slow. Then this keyword is used to tell
gnuplot how to map this scanning convention to the Cartesian convention shown
in plots, i.e., x/y/z. The qualifier for scan is a two or three letter code
representing where point is assigned (first letter), line is assigned (second
letter), and plane is assigned (third letter). For example, `scan=yx` means
the fastest, point-by-point, increment should be mapped along the Cartesian
y dimension and the middle, line-by-line, increment should be mapped along the
x dimension.
When the plotting mode is `plot`, the qualifier code can include the two
letters x and y. For `splot`, it can include the three letters x, y and z.
There is nothing restricting the inherent mapping from point/line/plane to
apply only to Cartesian coordinates. For this reason there are cylindrical
coordinate synonyms for the qualifier codes where t (theta), r and z are
analogous to the x, y and z of Cartesian coordinates.
?binary keywords transpose
?transpose
Shorthand notation for `scan=yx` or `scan=yxz`. I.e. it affects the assignment
of pixels to scan lines during input. To instead transpose an image when it is
displayed try
plot 'imagefile' binary filetype=auto flipx rotate=90deg with rgbimage
?binary keywords dx
?binary keywords dy
?dx
?dy
When gnuplot generates coordinates, it uses the spacing described by these
keywords. For example `dx=10 dy=20` would mean space samples along the
x dimension by 10 and space samples along the y dimension by 20. `dy` cannot
appear if `dx` does not appear. Similarly, `dz` cannot appear if `dy` does not
appear. If the underlying dimensions are greater than the keywords specified,
the spacing of the highest dimension given is extended to the other dimensions.
For example, if an image is being read from a file and only `dx=3.5` is given
gnuplot uses a delta x and delta y of 3.5.
The following keywords also apply only when generating coordinates. However
they may also be used with matrix binary files.
?binary keywords flipx
?flipx
?flipy
?flipz
Sometimes the scanning directions in a binary datafile are not consistent with
that assumed by gnuplot. These keywords can flip the scanning direction along
dimensions x, y, z.
?binary keywords origin
?binary origin
When gnuplot generates coordinates based upon transposition and flip, it
attempts to always position the lower left point in the array at the origin,
i.e., the data lies in the first quadrant of a Cartesian system after transpose
and flip.
To position the array somewhere else on the graph, the `origin` keyword directs
gnuplot to position the lower left point of the array at a point specified by a
tuple. The tuple should be a double for `plot` and a triple for `splot`.
For example, `origin=(100,100):(100,200)` is for two records in the file and
intended for plotting in two dimensions. A second example, `origin=(0,0,3.5)`,
is for plotting in three dimensions.
?binary keywords center
?keywords center
?center
Similar to `origin`, this keyword will position the array such that its center
lies at the point given by the tuple. For example, `center=(0,0)`. Center
does not apply when the size of the array is `Inf`.
?binary keywords rotate
?keywords rotate
?rotate
The transpose and flip commands provide some flexibility in generating and
orienting coordinates. However, for full degrees of freedom, it is possible to
apply a rotational vector described by a rotational angle in two dimensions.
The `rotate` keyword applies to the two-dimensional plane, whether it be `plot`
or `splot`. The rotation is done with respect to the positive angle of the
Cartesian plane.
The angle can be expressed in radians, radians as a multiple of pi, or degrees.
For example, `rotate=1.5708`, `rotate=0.5pi` and `rotate=90deg` are equivalent.
If `origin` is specified, the rotation is done about the lower left sample
point before translation. Otherwise, the rotation is done about the array
`center`.
?binary keywords perpendicular
?perpendicular
For `splot`, the concept of a rotational vector is implemented by a triple
representing the vector to be oriented normal to the two-dimensional x-y plane.
Naturally, the default is (0,0,1). Thus specifying both rotate and
perpendicular together can orient data myriad ways in three-space.
The two-dimensional rotation is done first, followed by the three-dimensional
rotation. That is, if R' is the rotational 2 x 2 matrix described by an angle,
and P is the 3 x 3 matrix projecting (0,0,1) to (xp,yp,zp), let R be
constructed from R' at the upper left sub-matrix, 1 at element 3,3 and zeros
elsewhere. Then the matrix formula for translating data is v' = P R v, where v
is the 3 x 1 vector of data extracted from the data file. In cases where the
data of the file is inherently not three-dimensional, logical rules are used to
place the data in three-space. (E.g., usually setting the z-dimension value to
zero and placing 2D data in the x-y plane.)
?commands plot datafile
?plot datafile
?data-file
?datafile
?data
?file
Discrete data contained in a file can be displayed by specifying the name of
the data file (enclosed in single or double quotes) on the `plot` command line.
Syntax:
plot '<file_name>' {binary <binary list>}
{{nonuniform} matrix}
{index <index list> | index "<name>"}
{every <every list>}
{skip <number-of-lines>}
{using <using list>}
{smooth <option>}
{bins <options>}
{volatile} {noautoscale}
The modifiers `binary`, `index`, `every`, `skip`, `using`, `bins`, and `smooth`
are discussed separately. In brief, `binary` allows data entry from a binary
file, `index` selects which data sets in a multi-data-set file are to be
plotted, `every` specifies which points within a single data set are to be
plotted, `using` determines how the columns within a single record are to be
interpreted, and `smooth` allows for simple interpolation and approximation.
`bins` sorts individual input points into equal-sized intervals along x and
plots a single accumulated value per interval.
`splot` has a similar syntax, but does not support the `smooth` option.
The `noautoscale` keyword means that the points making up this plot will be
ignored when automatically determining axis range limits.
TEXT DATA FILES:
Data files should contain at least one data point per record (`using`
can select one data point from the record). Records beginning with `#`
(and also with `!` on VMS) will be treated as comments and ignored.
Each data point represents an (x,y) pair. For `plot`s with error bars or
error bars with lines (see `errorbars` or `errorlines`),
each data point is (x,y,ydelta), (x,y,ylow,yhigh),
(x,y,xdelta), (x,y,xlow,xhigh), or (x,y,xlow,xhigh,ylow,yhigh).
In all cases, the numbers of each record of a data file must be separated
by white space (one or more blanks or tabs) unless a format specifier is
provided by the `using` option. This white space divides each record into
columns. However, whitespace inside a pair of double quotes is ignored when
counting columns, so the following datafile line has three columns:
1.0 "second column" 3.0
Data may be written in exponential format with the exponent preceded by the
letter e or E. The fortran exponential specifiers d, D, q, and Q may also
be used if the command `set datafile fortran` is in effect.
Only one column (the y value) need be provided. If x is omitted, `gnuplot`
provides integer values starting at 0.
In datafiles, blank records (records with no characters other than blanks and
a newline and/or carriage return) are significant.
Single blank records designate discontinuities in a `plot`; no line will join
points separated by a blank records (if they are plotted with a line style).
Two blank records in a row indicate a break between separate data sets.
See `index`.
If autoscaling has been enabled (`set autoscale`), the axes are automatically
extended to include all datapoints, with a whole number of tic marks if tics
are being drawn. This has two consequences: i) For `splot`, the corner of
the surface may not coincide with the corner of the base. In this case, no
vertical line is drawn. ii) When plotting data with the same x range on a
dual-axis graph, the x coordinates may not coincide if the x2tics are not
being drawn. This is because the x axis has been autoextended to a whole
number of tics, but the x2 axis has not. The following example illustrates
the problem:
reset; plot '-', '-' axes x2y1
1 1
19 19
e
1 1
19 19
e
To avoid this, you can use the `fixmin`/`fixmax` feature of the
`set autoscale` command, which turns off the automatic extension of the
axis range up to the next tic mark.
Label coordinates and text can also be read from a data file (see `labels`).
?commands plot datafile bins
?plot datafile bins
?plot bins
?data-file bins
?datafile bins
?bins
EXPERIMENTAL (implementation details may change in a later version)_
Syntax:
plot 'DATA' using <XCOL> {:<YCOL>} bins{=<NBINS>}
{binrange [<LOW>:<HIGH>]} {binwidth=<width>}
The `bins` option to a `plot` command first assigns the original data to
equal width bins on x and then plots a single value per bin. The default
number of bins is controlled by `set samples`, but this can be changed by
giving an explicit number of bins in the command.
If no binrange is given, the range is taken from the extremes of the x
values found in 'DATA'.
Given the range and the number of bins, bin width is calculated automatically
and points are assigned to bins 0 to NBINS-1
BINWIDTH = (HIGH - LOW) / (NBINS-1)
xmin = LOW - BINWIDTH/2
xmax = HIGH + BINWIDTH/2
first bin holds points with (xmin <= x < xmin + BINWIDTH)
last bin holds points with (xmax-BINWIDTH <= x < xman)
each point is assigned to bin i = floor(NBINS * (x-xmin)/(xmax-xmin))
Alternatively you can provide a fixed bin width, in which case nbins is
calculated as the smallest number of bins that will span the range.
On output bins are plotted or tabulated by midpoint. E.g. if the program
calculates bin width as shown above, the x coordinate output for the first bin
is x=LOW (not x=xmin).
If only a single column is given in the using clause then each data point
contributes a count of 1 to the accumulation of total counts in the bin for
that x coordinate value. If a second column is given then the value in that
column is added to the accumulation for the bin. Thus the following two plot
command are equivalent:
plot 'DATA" using N bins=20
set samples 20
plot 'DATA' using (column(N)):(1)
For related plotting styles see `smooth frequency` and `smooth kdensity`.
?commands plot datafile every
?plot datafile every
?plot every
?data-file every
?datafile every
?every
The `every` keyword allows a periodic sampling of a data set to be plotted.
In the discussion a "point" is a datum defined by a single record in the file;
a "block" of data is a set of consecutive records with blank lines before and
after the block.
Syntax:
plot 'file' every {<point_incr>}
{:{<block_incr>}
{:{<start_point>}
{:{<start_block>}
{:{<end_point>}
{:<end_block>}}}}}
The data points to be plotted are selected according to a loop from
<`start_point`> to <`end_point`> with increment <`point_incr`> and the
blocks according to a loop from <`start_block`> to <`end_block`> with
increment <`block_incr`>.
The first datum in each block is numbered '0', as is the first block in the
file.
Note that records containing unplottable information are counted.
Any of the numbers can be omitted; the increments default to unity, the start
values to the first point or block, and the end values to the last point or
block. ':' at the end of the `every` option is not permitted.
If `every` is not specified, all points in all lines are plotted.
Examples:
every :::3::3 # selects just the fourth block ('0' is first)
every :::::9 # selects the first 10 blocks
every 2:2 # selects every other point in every other block
every ::5::15 # selects points 5 through 15 in each block
See
simple plot demos (simple.dem)
,
Non-parametric splot demos
, and
Parametric splot demos
.
?commands plot datafile example
?plot datafile example
?plot example
?datafile example
?data-file example
?example
This example plots the data in the file "population.dat" and a theoretical
curve:
pop(x) = 103*exp((1965-x)/10)
set xrange [1960:1990]
plot 'population.dat', pop(x)
The file "population.dat" might contain:
# Gnu population in Antarctica since 1965
1965 103
1970 55
1975 34
1980 24
1985 10
Binary examples:
# Selects two float values (second one implicit) with a float value
# discarded between them for an indefinite length of 1D data.
plot '<file_name>' binary format="%float%*float" using 1:2 with lines
# The data file header contains all details necessary for creating
# coordinates from an EDF file.
plot '<file_name>' binary filetype=edf with image
plot '<file_name>.edf' binary filetype=auto with image
# Selects three unsigned characters for components of a raw RGB image
# and flips the y-dimension so that typical image orientation (start
# at top left corner) translates to the Cartesian plane. Pixel
# spacing is given and there are two images in the file. One of them
# is translated via origin.
plot '<file_name>' binary array=(512,1024):(1024,512) format='%uchar' \
dx=2:1 dy=1:2 origin=(0,0):(1024,1024) flipy u 1:2:3 w rgbimage
# Four separate records in which the coordinates are part of the
# data file. The file was created with a endianess different from
# the system on which gnuplot is running.
splot '<file_name>' binary record=30:30:29:26 endian=swap u 1:2:3
# Same input file, but this time we skip the 1st and 3rd records
splot '<file_name>' binary record=30:26 skip=360:348 endian=swap u 1:2:3
See also `binary matrix`.
?commands plot datafile index
?plot datafile index
?plot index
?data-file index
?datafile index
?index
The `index` keyword allows you to select specific data sets in a multi-data-set
file for plotting.
Syntax:
plot 'file' index { <m>{:<n>{:<p>}} | "<name>" }
Data sets are separated by pairs of blank records. `index <m>` selects only
set <m>; `index <m>:<n>` selects sets in the range <m> to <n>; and `index
<m>:<n>:<p>` selects indices <m>, <m>+<p>, <m>+2<p>, etc., but stopping at
<n>. Following C indexing, the index 0 is assigned to the first data set in
the file. Specifying too large an index results in an error message.
If <p> is specified but <n> is left blank then every <p>-th dataset is read
until the end of the file. If `index` is not specified, the entire file is
plotted as a single data set.
Example:
plot 'file' index 4:5
For each point in the file, the index value of the data set it appears in is
available via the pseudo-column `column(-2)`. This leads to an alternative way
of distinguishing individual data sets within a file as shown below. This is
more awkward than the `index` command if all you are doing is selecting one
data set for plotting, but is very useful if you want to assign different
properties to each data set. See `pseudocolumns`, `lc variable`.
Example:
plot 'file' using 1:(column(-2)==4 ? $2 : NaN) # very awkward
plot 'file' using 1:2:(column(-2)) linecolor variable # very useful!
`index '<name>'` selects the data set with name '<name>'. Names are assigned
to data sets in comment lines. The comment character and leading white space
are removed from the comment line. If the resulting line starts with <name>,
the following data set is now named <name> and can be selected.
Example:
plot 'file' index 'Population'
Please note that every comment that starts with <name> will name the following
data set. To avoid problems it may be useful to choose a naming scheme like
'== Population ==' or '[Population]'.
?plot datafile skip
?data-file skip
?datafile skip
?skip
The `skip` keyword tells the program to skip lines at the start of a text
(i.e. not binary) data file. The lines that are skipped do not count toward
the line count used in processing the `every` keyword. Note that `skip N`
skips lines only at the start of the file, whereas `every ::N` skips lines at
the start of every block of data in the file. See also `binary skip` for a
similar option that applies to binary data files.
?commands plot datafile smooth
?plot datafile smooth
?plot smooth
?data-file smooth
?datafile smooth
?smooth
?splines
`gnuplot` includes a few general-purpose routines for interpolation and
approximation of data; these are grouped under the `smooth` option. More
sophisticated data processing may be performed by preprocessing the data
externally or by using `fit` with an appropriate model.
Syntax:
smooth {unique | frequency | fnormal | cumulative | cnormal | bins
| kdensity {bandwidth}
| csplines | acsplines | mcsplines | bezier | sbezier
| unwrap}
The `unique`, `frequency`, `fnormal`, `cumulative` and `cnormal` sort the data
on x and then plot some aspect of the distribution of x values.
The spline and Bezier options determine coefficients describing a continuous
curve between the endpoints of the data. This curve is then plotted in the same
manner as a function, that is, by finding its value at uniform intervals along
the abscissa (see `set samples`) and connecting these points with straight line
segments. If the data set is interrupted by blank lines or undefined values a
separate continuous curve is fit for each uninterrupted subset of the data.
Adjacent separately fit segments may be separated by a gap or discontinuity.
`unwrap` manipulates the data to avoid jumps of more than pi by adding or
subtracting multiples of 2*pi.
If `autoscale` is in effect, axis ranges will be computed for the final curve
rather than for the original data.
If `autoscale` is not in effect, and a spline curve is being generated,
sampling of the spline fit is done across the intersection of the x range
covered by the input data and the fixed abscissa range defined by `set xrange`.
If too few points are available to apply the requested smoothing operation
an error message is produced.
The `smooth` options have no effect on function plots.
?commands plot datafile smooth acsplines
?plot datafile smooth acsplines
?data-file smooth acsplines
?datafile smooth acsplines
?plot smooth acsplines
?plot acsplines
?smooth acsplines
?acsplines
The `acsplines` option approximates the data with a "natural smoothing spline".
After the data are made monotonic in x (see `smooth unique`), a curve is
piecewise constructed from segments of cubic polynomials whose coefficients
are found by fitting to the individual data points weighted by the value,
if any, given in the third column of the using spec. The default is equivalent
to
plot 'data-file' using 1:2:(1.0) smooth acsplines
Qualitatively, the absolute magnitude of the weights determines the number
of segments used to construct the curve. If the weights are large, the
effect of each datum is large and the curve approaches that produced by
connecting consecutive points with natural cubic splines. If the weights are
small, the curve is composed of fewer segments and thus is smoother; the
limiting case is the single segment produced by a weighted linear least
squares fit to all the data. The smoothing weight can be expressed in terms
of errors as a statistical weight for a point divided by a "smoothing factor"
for the curve so that (standard) errors in the file can be used as smoothing
weights.
Example:
sw(x,S)=1/(x*x*S)
plot 'data_file' using 1:2:(sw($3,100)) smooth acsplines
?commands plot datafile smooth bezier
?plot datafile smooth bezier
?plot smooth bezier
?data-file smooth bezier
?datafile smooth bezier
?plot bezier
?smooth bezier
?bezier
The `bezier` option approximates the data with a Bezier curve of degree n
(the number of data points) that connects the endpoints.
?data-file smooth bins
?datafile smooth bins
?smooth bins
`smooth bins` is the same as `bins`.
See `bins`.
For related plotting styles see `smooth frequency` and `smooth kdensity`.
?commands plot datafile smooth csplines
?plot datafile smooth csplines
?plot smooth csplines
?data-file smooth csplines
?datafile smooth csplines
?plot csplines
?smooth csplines
?csplines
The `csplines` option connects consecutive points by natural cubic splines
after rendering the data monotonic (see `smooth unique`).
?commands plot datafile smooth mcsplines
?plot datafile smooth mcsplines
?plot smooth mcsplines
?data-file smooth mcsplines
?datafile smooth mcsplines
?plot mcsplines
?smooth mcsplines
?mcsplines
The `mcsplines` option connects consecutive points by cubic splines constrained
such that the smoothed function preserves the monotonicity and convexity of the
original data points. This reduces the effect of outliers.
FN Fritsch & RE Carlson (1980) "Monotone Piecewise Cubic Interpolation",
SIAM Journal on Numerical Analysis 17: 238–246.
?commands plot datafile smooth sbezier
?plot datafile smooth sbezier
?plot smooth sbezier
?data-file smooth sbezier
?datafile smooth sbezier
?plot sbezier
?smooth sbezier
?sbezier
The `sbezier` option first renders the data monotonic (`unique`) and then
applies the `bezier` algorithm.
?commands plot datafile smooth unique
?plot datafile smooth unique
?plot smooth unique
?data-file smooth unique
?datafile smooth unique
?plot unique
?smooth unique
?unique
The `unique` option makes the data monotonic in x; points with the same
x-value are replaced by a single point having the average y-value. The
resulting points are then connected by straight line segments.
?commands plot datafile smooth unwrap
?plot datafile smooth unwrap
?plot smooth unwrap
?data-file smooth unwrap
?datafile smooth unwrap
?plot unwrap
?smooth unwrap
?unwrap
The `unwrap` option modifies the input data so that any two successive
points will not differ by more than pi; a point whose y value is
outside this range will be incremented or decremented by multiples of
2pi until it falls within pi of the previous point. This operation is
useful for making wrapped phase measurements continuous over time.
?commands plot datafile smooth frequency
?plot datafile smooth frequency
?plot smooth frequency
?data-file smooth frequency
?datafile smooth frequency
?plot frequency
?smooth frequency
?frequency
The `frequency` option makes the data monotonic in x; points with the same
x-value are replaced by a single point having the summed y-values.
To plot a histogram of the number of data values in equal size bins,
set the y-value to 1.0 so that the sum is a count of occurrences in that bin.
This is done implicitly if only a single column is provided.
Example:
binwidth = <something> # set width of x values in each bin
bin(val) = binwidth * floor(val/binwidth)
plot "datafile" using (bin(column(1))):(1.0) smooth frequency
plot "datafile" using (bin(column(1))) smooth frequency # same result
See also
smooth.dem
?commands plot datafile smooth fnormal
?plot datafile smooth fnormal
?plot smooth fnormal
?data-file smooth fnormal
?datafile smooth fnormal
?plot fnormal
?smooth fnormal
?fnormal
The `fnormal` option work just like the `frequency` option, but produces a
normalized histogram. It makes the data monotonic in x and normalises the
y-values so they all sum to 1. Points with the same x-value are replaced by a
single point containing the sumed y-values. To plot a histogram of the number
of data values in equal size bins, set the y-value to 1.0 so that the sum is a
count of occurrences in that bin. This is done implicitly if only a single
column is provided.
See also
smooth.dem
?commands plot datafile smooth cumulative
?plot datafile smooth cumulative
?plot smooth cumulative
?data-file smooth cumulative
?datafile smooth cumulative
?plot cumulative
?smooth cumulative
?cumulative
The `cumulative` option makes the data monotonic in x; points with the same
x-value are replaced by a single point containing the cumulative sum of
y-values of all data points with lower x-values (i.e. to the left of the
current data point). This can be used to obtain a cumulative distribution
function from data.
See also
smooth.dem
?commands plot datafile smooth cnormal
?plot datafile smooth cnormal
?plot smooth cnormal
?data-file smooth cnormal
?datafile smooth cnormal
?plot cnormal
?smooth cnormal
?cnormal
The `cnormal` option makes the data monotonic in x and normalises the
y-values onto the range [0:1]. Points with the same x-value are
replaced by a single point containing the cumulative sum of y-values
of all data points with lower x-values (i.e. to the left of the
current data point) divided by the total sum of all y-values. This can
be used to obtain a normalised cumulative distribution function from
data (useful when comparing sets of samples with differing numbers of
members).
See also
smooth.dem
?commands plot datafile smooth kdensity
?plot datafile smooth kdensity
?plot smooth kdensity
?data-file smooth kdensity
?datafile smooth kdensity
?plot kdensity
?smooth kdensity
?kdensity
The `kdensity` option is a way to plot a kernel density estimate (which is a
smooth histogram) for a random collection of points, using Gaussian kernels.
A Gaussian is placed at the location of each point in the first column and
the sum of all these Gaussians is plotted as a function. The value in the
second column is taken as weight of the Gaussian. To obtain a normalized
histogram, this should be 1/number-of-points. By default gnuplot calculates
and uses the bandwidth which would be optimal for normally distributed data.
default_bandwidth = sigma * (4/3N) ** (0.2)
This will usually be a very conservative, i.e. broad bandwidth.
Alternatively, you can provide an explicit bandwidth.
plot $DATA smooth kdensity bandwidth <value> with boxes
The bandwidth used in the previous plot is stored in variable
GPVAL_KDENSITY_BANDWIDTH.
?special-filenames
?commands plot datafile special-filenames
?plot datafile special-filenames
?plot special-filenames
?datafile special-filenames
?special-filenames ++
?special-filenames +
?+
?++
There are a few filenames that have a special meaning: '', '-', '+' and '++'.
The empty filename '' tells gnuplot to re-use the previous input file in the
same plot command. So to plot two columns from the same input file:
plot 'filename' using 1:2, '' using 1:3
The filename can also be reused over subsequent plot commands, however `save`
then only records the name in a comment.
The special filenames '+' and '++' are a mechanism to allow the full range of
`using` specifiers and plot styles with inline functions. Normally a function
plot can only have a single y (or z) value associated with each sampled point.
The pseudo-file '+' treats the sampled points as column 1, and allows
additional column values to be specified via a `using` specification, just as
for a true input file. By default samples are generated over the full range as
set by `set xrange`, with the sampling controlled via `set samples`.
plot '+' using ($1):(sin($1)):(sin($1)**2) with filledcurves
An independent sampling range can be provided immediately before the '+'. As
in normal function plots, a name can be assigned to the independent variable.
If given for the first plot element, the sampling range specifier has to be
preceeded by the `sample` keyword (see also `plot sampling`).
plot sample [beta=0:2*pi] '+' using (sin(beta)):(cos(beta)) with lines
Additionally, the range specifier of '+' supports giving a sampling increment.
plot $MYDATA, [t=-3:25:1] '+' using (t):(f(t))
The pseudo-file '++' returns 2 columns of data forming a regular grid of [u,v]
coordinates with the number of points along u controlled by `set samples` and
the number of points along v controlled by `set isosamples`. You must set
urange and vrange before plotting '++'. However the x and y ranges can be
autoscaled or can be explicitly set to different values than urange and vrange.
Use of u and v to sample '++' is a CHANGE from version 5.0
Examples:
splot '++' using 1:2:(sin($1)*sin($2)) with pm3d
plot '++' using 1:2:(sin($1)*sin($2)) with image
The special filename `'-'` specifies that the data are inline; i.e., they
follow the command. Only the data follow the command; `plot` options like
filters, titles, and line styles remain on the `plot` command line. This is
similar to << in unix shell script, and $DECK in VMS DCL. The data are
entered as though they are being read from a file, one data point per record.
The letter "e" at the start of the first column terminates data entry.
`'-'` is intended for situations where it is useful to have data and commands
together, e.g. when both are piped to `gnuplot` from another application.
Some of the demos, for example, might use this feature. While
`plot` options such as `index` and `every` are recognized, their use forces
you to enter data that won't be used. For all but the simplest cases it is
probably easier to first define a datablock and then read from it rather than
from `'-'`. See `datablocks`.
If you use `'-'` with `replot`, you may need to enter the data more than once.
See `replot`, `refresh`. Here again it may be better to use a datablock.
A blank filename ('') specifies that the previous filename should be reused.
This can be useful with things like
plot 'a/very/long/filename' using 1:2, '' using 1:3, '' using 1:4
(If you use both `'-'` and `''` on the same `plot` command, you'll need to
have two sets of inline data, as in the example above.)
?commands plot datafile piped-data
?plot datafile piped-data
?plot piped-data
?piped-data
?pipes
On systems with a popen function, the datafile can be piped through a shell
command by starting the file name with a '<'. For example,
pop(x) = 103*exp(-x/10)
plot "< awk '{print $1-1965, $2}' population.dat", pop(x)
would plot the same information as the first population example but with
years since 1965 as the x axis. If you want to execute this example, you
have to delete all comments from the data file above or substitute the
following command for the first part of the command above (the part up to
the comma):
plot "< awk '$0 !~ /^#/ {print $1-1965, $2}' population.dat"
While this approach is most flexible, it is possible to achieve simple
filtering with the `using` keyword.
On systems with an fdopen() function, data can be read from an arbitrary file
descriptor attached to either a file or pipe. To read from file descriptor
`n` use `'<&n'`. This allows you to easily pipe in several data files in a
single call from a POSIX shell:
$ gnuplot -p -e "plot '<&3', '<&4'" 3<data-3 4<data-4
$ ./gnuplot 5< <(myprogram -with -options)
gnuplot> plot '<&5'
?commands plot datafile thru
?plot datafile thru
?plot thru
?data-file thru
?datafile thru
?thru
The `thru` keyword is deprecated.
Old syntax:
plot 'file' thru f(x)
Current syntax:
plot 'file' using 1:(f($2))
?commands plot datafile using
?plot datafile using
?plot using
?data-file using
?datafile using
?using
The most common datafile modifier is `using`. It tells the program which
columns of data in the input file are to be plotted.
Syntax:
plot 'file' using <entry> {:<entry> {:<entry> ...}} {'format'}
If a format is specified, it is used to read in each datafile record using the
C library 'scanf' function. Otherwise the record is interpreted as consisting
of columns (fields) of data separated by whitespace (spaces and/or tabs),
but see `datafile separator`.
Each <entry> may be a simple column number that selects the value from one
field of the input file, a string that matches a column label in the first
line of a data set, an expression enclosed in parentheses, or a special
function not enclosed in parentheses such as xticlabels(2).
If the entry is an expression in parentheses, then the function column(N) may
be used to indicate the value in column N. That is, column(1) refers to the
first item read, column(2) to the second, and so on. The special symbols
$1, $2, ... are shorthand for column(1), column(2) ... The function `valid(N)`
tests whether the value in the Nth column is a valid number.
If each column of data in the input file contains a label in the first row
rather than a data value, this label can be used to identify the column on
input and/or in the plot legend. The column() function can be used to select
an input column by label rather than by column number. For example,
if the data file contains
Height Weight Age
val1 val1 val1
... ... ...
then the following plot commands are all equivalent
plot 'datafile' using 3:1, '' using 3:2
plot 'datafile' using (column("Age")):(column(1)), \
'' using (column("Age")):(column(2))
plot 'datafile' using "Age":"Height", '' using "Age":"Weight"
The full string must match. Comparison is case-sensitive.
To use column labels in the plot legend, use `set key autotitle columnhead`.
In addition to the actual columns 1...N in the input data file, gnuplot
presents data from several "pseudo-columns" that hold bookkeeping information.
E.g. $0 or column(0) returns the sequence number of this data record within a
dataset. Please see `pseudocolumns`.
An empty <entry> will default to its order in the list of entries.
For example, `using ::4` is interpreted as `using 1:2:4`.
If the `using` list has only a single entry, that <entry> will be used for y
and the data point number (pseudo-column $0) is used for x; for example,
"`plot 'file' using 1`" is identical to "`plot 'file' using 0:1`".
If the `using` list has two entries, these will be used for x and y.
See `set style` and `fit` for details about plotting styles that make use of
data from additional columns of input.
'scanf' accepts several numerical specifications but `gnuplot`
requires all inputs to be double-precision floating-point variables,
so "%lf" is essentially the only permissible specifier.
A format string given by the user must contain at least one such
input specifier, and no more than seven of them.
'scanf' expects to see white space---a blank, tab
("\t"), newline ("\n"), or formfeed ("\f")---between numbers; anything else
in the input stream must be explicitly skipped.
Note that the use of "\t", "\n", or "\f" requires use of double-quotes
rather than single-quotes.
?commands plot datafile using examples
?plot datafile using examples
?datafile using examples
?using examples
This creates a plot of the sum of the 2nd and 3rd data against the first:
The format string specifies comma- rather than space-separated columns.
The same result could be achieved by specifying `set datafile separator comma`.
plot 'file' using 1:($2+$3) '%lf,%lf,%lf'
In this example the data are read from the file "MyData" using a more
complicated format:
plot 'MyData' using "%*lf%lf%*20[^\n]%lf"
The meaning of this format is:
%*lf ignore a number
%lf read a double-precision number (x by default)
%*20[^\n] ignore 20 non-newline characters
%lf read a double-precision number (y by default)
One trick is to use the ternary `?:` operator to filter data:
plot 'file' using 1:($3>10 ? $2 : 1/0)
which plots the datum in column two against that in column one provided
the datum in column three exceeds ten. `1/0` is undefined; `gnuplot`
quietly ignores undefined points, so unsuitable points are suppressed.
Or you can use the pre-defined variable NaN to achieve the same result.
In fact, you can use a constant expression for the column number, provided it
doesn't start with an opening parenthesis; constructs like `using
0+(complicated expression)` can be used. The crucial point is that the
expression is evaluated once if it doesn't start with a left parenthesis, or
once for each data point read if it does.
If timeseries data are being used, the time can span multiple columns. The
starting column should be specified. Note that the spaces within the time
must be included when calculating starting columns for other data. E.g., if
the first element on a line is a time with an embedded space, the y value
should be specified as column three.
It should be noted that (a) `plot 'file'`, (b) `plot 'file' using 1:2`, and
(c) `plot 'file' using ($1):($2)` can be subtly different. The exact
behaviour has changed in version 5. See `missing`.
It is often possible to plot a file with lots of lines of garbage at
the top simply by specifying
plot 'file' using 1:2
However, if you want to leave text in your data files, it is safer to put the
comment character (#) in the first column of the text lines.
?pseudocolumns
?commands plot datafile using pseudocolumns
?plot datafile using pseudocolumns
?datafile using pseudocolumns
?using pseudocolumns
Expressions in the `using` clause of a plot statement can refer to additional
bookkeeping values in addition to the actual data values contained in the input
file. These are contained in "pseudocolumns".
column(0) The sequential order of each point within a data set.
The counter starts at 0 and is reset by two sequential blank
records. The shorthand form $0 is available.
column(-1) This counter starts at 0 and is reset by a single blank line.
This corresponds to the data line in array or grid data.
column(-2) The index number of the current data set within a file that
contains multiple data sets. See `index`.
?xticlabels
?using xticlabels
?plot using xticlabels
Axis tick labels can be generated via a string function, usually taking a data
column as an argument. The simplest form uses the data column itself as a
string. That is, xticlabels(N) is shorthand for xticlabels(stringcolumn(N)).
This example uses the contents of column 3 as x-axis tick labels.
plot 'datafile' using <xcol>:<ycol>:xticlabels(3) with <plotstyle>
Axis tick labels may be generated for any of the plot axes: x x2 y y2 z.
The `ticlabels(<labelcol>)` specifiers must come after all of the data
coordinate specifiers in the `using` portion of the command.
For each data point which has a valid set of X,Y[,Z] coordinates,
the string value given to xticlabels() is added to the list of xtic labels
at the same X coordinate as the point it belongs to. `xticlabels()`
may be shortened to `xtic()` and so on.
Example:
splot "data" using 2:4:6:xtic(1):ytic(3):ztic(6)
In this example the x and y axis tic labels are taken from different columns
than the x and y coordinate values. The z axis tics, however, are generated
from the z coordinate of the corresponding point.
Example:
plot "data" using 1:2:xtic( $3 > 10. ? "A" : "B" )
This example shows the use of a string-valued function to generate x-axis
tick labels. Each point in the data file generates a tick mark on x labeled
either "A" or "B" depending on the value in column 3.
?using x2ticlabels
?plot using x2ticlabels
See `plot using xticlabels`.
?using yticlabels
?plot using yticlabels
See `plot using xticlabels`.
?using y2ticlabels
?plot using y2ticlabels
See `plot using xticlabels`.
?using zticlabels
?plot using zticlabels
See `plot using xticlabels`.
?datafile volatile
?data volatile
?plot datafile volatile
?plot volatile
?volatile
The `volatile` keyword in a plot command indicates that the data previously
read from the input stream or file may not be available for re-reading.
This tells the program to use `refresh` rather than `replot` commands whenever
possible. See `refresh`.
?commands plot errorbars
?commands splot errorbars
?plot errorbars
?splot errorbars
Error bars are supported for 2D data file plots by reading one to four
additional columns (or `using` entries); these additional values are used in
different ways by the various errorbar styles.
In the default situation, `gnuplot` expects to see three, four, or six
numbers on each line of the data file---either
(x, y, ydelta),
(x, y, ylow, yhigh),
(x, y, xdelta),
(x, y, xlow, xhigh),
(x, y, xdelta, ydelta), or
(x, y, xlow, xhigh, ylow, yhigh).
The x coordinate must be specified. The order of the numbers must be
exactly as given above, though the `using` qualifier can manipulate the order
and provide values for missing columns. For example,
plot 'file' with errorbars
plot 'file' using 1:2:(sqrt($1)) with xerrorbars
plot 'file' using 1:2:($1-$3):($1+$3):4:5 with xyerrorbars
The last example is for a file containing an unsupported combination of
relative x and absolute y errors. The `using` entry generates absolute x min
and max from the relative error.
The y error bar is a vertical line plotted from (x, ylow) to (x,
yhigh). If ydelta is specified instead of ylow and yhigh, ylow = y -
ydelta and yhigh = y + ydelta are derived. If there are only two
numbers on the record, yhigh and ylow are both set to y. The x error
bar is a horizontal line computed in the same fashion. To get lines
plotted between the data points, `plot` the data file twice, once with
errorbars and once with lines (but remember to use the `notitle`
option on one to avoid two entries in the key). Alternately, use the
errorlines command (see `errorlines`).
The tic marks at the ends of the bar are controlled by `set errorbars`.
If autoscaling is on, the ranges will be adjusted to include the error bars.
See also
errorbar demos.
See `plot using`, `plot with`, and `set style` for more information.
?commands plot errorlines
?commands splot errorlines
?plot errorlines
?splot errorlines
?errorlines
Lines with error bars are supported for 2D data file plots by reading
one to four additional columns (or `using` entries); these additional
values are used in different ways by the various errorlines styles.
In the default situation, `gnuplot` expects to see three, four, or six
numbers on each line of the data file---either
(x, y, ydelta),
(x, y, ylow, yhigh),
(x, y, xdelta),
(x, y, xlow, xhigh),
(x, y, xdelta, ydelta), or
(x, y, xlow, xhigh, ylow, yhigh).
The x coordinate must be specified. The order of the numbers must be
exactly as given above, though the `using` qualifier can manipulate
the order and provide values for missing columns. For example,
plot 'file' with errorlines
plot 'file' using 1:2:(sqrt($1)) with xerrorlines
plot 'file' using 1:2:($1-$3):($1+$3):4:5 with xyerrorlines
The last example is for a file containing an unsupported combination
of relative x and absolute y errors. The `using` entry generates
absolute x min and max from the relative error.
The y error bar is a vertical line plotted from (x, ylow) to (x,
yhigh). If ydelta is specified instead of ylow and yhigh, ylow = y -
ydelta and yhigh = y + ydelta are derived. If there are only two
numbers on the record, yhigh and ylow are both set to y. The x error
bar is a horizontal line computed in the same fashion.
The tic marks at the ends of the bar are controlled by `set errorbars`.
If autoscaling is on, the ranges will be adjusted to include the error bars.
See `plot using`, `plot with`, and `set style` for more information.
?commands plot functions
?plot functions
?functions
Built-in or user-defined functions can be displayed by the `plot` and `splot`
commands in addition to, or instead of, data read from a file. The requested
function is evaluated by sampling at regular intervals spanning the independent
axis range[s]. See `set samples` and `set isosamples`.
Example:
approx(ang) = ang - ang**3 / (3*2)
plot sin(x) title "sin(x)", approx(x) title "approximation"
To set a default plot style for functions, see `set style function`.
For information on built-in functions, see `expressions functions`.
For information on defining your own functions, see `user-defined`.
?commands plot parametric
?commands splot parametric
?plot parametric
?splot parametric
When in parametric mode (`set parametric`) mathematical expressions must be
given in pairs for `plot` and in triplets for `splot`.
Examples:
plot sin(t),t**2
splot cos(u)*cos(v),cos(u)*sin(v),sin(u)
Data files are plotted as before, except any preceding parametric function
must be fully specified before a data file is given as a plot. In other
words, the x parametric function (`sin(t)` above) and the y parametric
function (`t**2` above) must not be interrupted with any modifiers or data
functions; doing so will generate a syntax error stating that the parametric
function is not fully specified.
Other modifiers, such as `with` and `title`, may be specified only after the
parametric function has been completed:
plot sin(t),t**2 title 'Parametric example' with linespoints
See also
Parametric Mode Demos.
?commands plot ranges
?commands splot ranges
?plot ranges
?splot ranges
?ranges
This section describes only the optional axis ranges that may appear as the
very first items in a `plot` command. If present, these ranges override any
range limits established by a previous `set range` statement. For optional
ranges elsewhere in a `plot` command that limit sampling of an individual
plot component see `sampling`.
Syntax:
[{<dummy-var>=}{{<min>}:{<max>}}]
[{{<min>}:{<max>}}]
The first form applies to the independent variable (`xrange` or `trange`, if
in parametric mode). The second form applies to dependent variables.
<dummy-var> optionally establishes a new name for the independent variable.
(The default name may be changed with `set dummy`.)
In non-parametric mode, ranges must be given in the order
plot [<xrange>][<yrange>][<x2range>][<y2range>] ...
In parametric mode, ranges must be given in the order
plot [<trange>][<xrange>][<yrange>][<x2range>][<y2range>] ...
The following `plot` command shows setting `trange` to [-pi:pi], `xrange`
to [-1.3:1.3] and `yrange` to [-1:1] for the duration of the graph:
plot [-pi:pi] [-1.3:1.3] [-1:1] sin(t),t**2
`*` can be used to allow autoscaling of either of min and max.
Use an empty range `[]` as a placeholder if necessary.
Ranges specified on the `plot` or `splot` command line affect only that one
graph; use the `set xrange`, `set yrange`, etc., commands to change the
default ranges for future graphs.
The use of on-the-fly range specifiers in a plot command may not yield
the expected result for linked axes (see `set link`). It is better to use
separate set xrange and set yrange statements instead.
For time data you must provide the range in quotes, using the same format
used to read time from the datafile. See `set timefmt`.
Examples:
This uses the current ranges:
plot cos(x)
This sets the x range only:
plot [-10:30] sin(pi*x)/(pi*x)
This is the same, but uses t as the dummy-variable:
plot [t = -10 :30] sin(pi*t)/(pi*t)
This sets both the x and y ranges:
plot [-pi:pi] [-3:3] tan(x), 1/x
This sets only the y range:
plot [ ] [-2:sin(5)*-8] sin(x)**besj0(x)
This sets xmax and ymin only:
plot [:200] [-pi:] $mydata using 1:2
This sets the x range for a timeseries:
set timefmt "%d/%m/%y %H:%M"
plot ["1/6/93 12:00":"5/6/93 12:00"] 'timedata.dat'
?sampling
?commands plot sampling
?plot sampling
?sampling 1D
?plot sampling 1D
By default, computed functions or data generated for the pseudo-file "+"
are sampled over the entire range of the plot as set by a prior `set xrange`
command, by an explicit global range specifier at the very start of the plot
or splot command, or by autoscaling the xrange to span data seen in all the
elements of this plot. However, individual plot components can be assigned
a more restricted sampling range.
Examples:
This establishes a total range on x running from 0 to 1000 and then plots
data from a file and two functions each spanning a portion of the total range:
plot [0:1000] 'datafile', [0:200] func1(x), [200:500] func2(x)
This is similar except that the total range is established by the contents
of the data file. In this case the sampled functions may or may not be
entirely contained in the plot:
set autoscale x
plot 'datafile', [0:200] func1(x), [200:500] func2(x)
This command is ambiguous. The initial range will be interpreted as applying to
the entire plot, not solely to the sampling of the first function as was
probably the intent:
plot [0:10] f(x), [10:20] g(x), [20:30] h(x)
This command removes the ambiguity of the previous example by inserting the
keyword `sample` so that the range is not applied to the entire plot:
plot sample [0:10] f(x), [10:20] g(x), [20:30] h(x)
This example shows one way of tracing out a helix in a 3D plot
splot [-2:2][-2:2] sample [h=1:10] '+' using (cos(h)):(sin(h)):(h)
?sampling 2D
?plot sampling 2D
Computed functions or data generated for the pseudo-file '++' use samples
generated along the u and v axes. This is a CHANGE from versions prior to
5.2 which sampled along the x and y axes. See `special-filenames ++`.
2D sampling can be used in either `plot` or `splot` commands.
Example of 2D sampling in a 2D `plot` command. These commands generated the
plot shown for plotstyle `with vectors`. See `vectors`.
set urange [ -2.0 : 2.0 ]
set vrange [ -2.0 : 2.0 ]
plot '++' using ($1):($2):($2*0.4):(-$1*0.4) with vectors
Example of 2D sampling in a 3D `splot` command. These commands are similar to
the ones used in `sampling.dem`. Note that the two surfaces are sampled over
u and v ranges smaller than the full x and y ranges of the resulting plot.
set title "3D sampling range distinct from plot x/y range"
set xrange [1:100]
set yrange [1:100]
splot sample [u=30:70][v=0:50] '++' using 1:2:(u*v) lt 3, \
[u=40:80][v=30:60] '++' using (u):(v):(u*sqrt(v)) lt 4
The range specifiers for sampling on u and v can include an explicit sampling
interval to control the number and spacing of samples:
splot sample [u=30:70:1][v=0:50:5] '++' using 1:2:(func($1,$2))
?commands plot for
?commands splot for
?plot for
?splot for
?for loops
If many similar files or functions are to be plotted together, it may be
convenient to do so by iterating over a shared plot command.
Syntax:
plot for [<variable> = <start> : <end> {:<increment>}]
plot for [<variable> in "string of words"]
The scope of an iteration ends at the next comma or the end of the command,
whichever comes first. An exception to this is that definitions are grouped
with the following plot item even if there is an intervening comma.
Note that iteration does not work for plots in parametric mode.
Example:
plot for [j=1:3] sin(j*x)
Example:
plot for [dataset in "apples bananas"] dataset."dat" title dataset
In this example iteration is used both to generate a file name and a
corresponding title.
Example:
file(n) = sprintf("dataset_%d.dat",n)
splot for [i=1:10] file(i) title sprintf("dataset %d",i)
This example defines a string-valued function that generates file names,
and plots ten such files together. The iteration variable ('i' in this
example) is treated as an integer, and may be used more than once.
Example:
set key left
plot for [n=1:4] x**n sprintf("%d",n)
This example plots a family of functions.
Example:
list = "apple banana cabbage daikon eggplant"
item(n) = word(list,n)
plot for [i=1:words(list)] item[i].".dat" title item(i)
list = "new stuff"
replot
This example steps through a list and plots once per item.
Because the items are retrieved dynamically, you can change the list
and then replot.
Example:
list = "apple banana cabbage daikon eggplant"
plot for [i in list] i.".dat" title i
list = "new stuff"
replot
This example does exactly the same thing as the previous example, but uses
the string iterator form of the command rather than an integer iterator.
If an iteration is to continue until all available data is consumed, use the
symbol * instead of an integer <end>. This can be used to process all columns
in a line, all datasets (separated by 2 blank lines) in a file, or all files
matching a template.
Examples:
plot for [i=2:*] 'datafile' using 1:i with histogram
splot for [i=0:*] 'datafile' index i using 1:2:3 with lines
plot for [i=1:*] file=sprintf("File_%03d.dat",i) file using 2 title file
?commands plot title
?commands splot title
?plot title
?splot title
?columnheader
By default each plot is listed in the key by the corresponding function or file
name. You can give an explicit plot title instead using the `title` option.
Syntax:
title <text> | notitle [<ignored text>]
title columnheader | title columnheader(N)
{at {beginning|end}} {{no}enhanced}
where <text> is a quoted string or an expression that evaluates to a string.
The quotes will not be shown in the key.
There is also an option that will interpret the first entry in a column of
input data (i.e. the column header) as a text field, and use it as the key
title. See `datastrings`. This can be made the default by specifying
`set key autotitle columnhead`.
The line title and sample can be omitted from the key by using the keyword
`notitle`. A null title (`title ''`) is equivalent to `notitle`. If only
the sample is wanted, use one or more blanks (`title ' '`). If `notitle`
is followed by a string this string is ignored.
If `key autotitles` is set (which is the default) and neither `title` nor
`notitle` are specified the line title is the function name or the file name as
it appears on the `plot` command. If it is a file name, any datafile modifiers
specified will be included in the default title.
The layout of the key itself (position, title justification, etc.) can be
controlled by `set key`. Please see `set key` for details.
The `at` keyword allows you to place the plot title somewhere outside the
auto-generated key box. The title can be placed immediately before or after the
line in the graph itself by using `at {beginning|end}`. This option may be
useful when plotting `with lines` but makes little sense for most other styles.
To place the plot title at an arbitrary location on the page, use the form
`at <x-position>,<y-position>`. By default the position is interpreted in
screen coordinates; e.g. `at 0.5, 0.5` is always the middle of the screen
regardless of plot axis scales or borders. The format of titles placed in
this way is still affected by key options. See `set key`.
Examples:
This plots y=x with the title 'x':
plot x
This plots x squared with title "x^2" and file "data.1" with title
"measured data":
plot x**2 title "x^2", 'data.1' t "measured data"
Plot multiple columns of data, each of which contains its own title on the
first line of the file. Place the titles after the corresponding lines rather
than in a separate key:
unset key
set offset 0, graph 0.1
plot for [i=1:4] 'data' using i with lines title columnhead at end
Create a single key area for two separate plots:
set key Left reverse
set multiplot layout 2,2
plot sin(x) with points pt 6 title "Left plot is sin(x)" at 0.5, 0.30
plot cos(x) with points pt 7 title "Right plot is cos(x)" at 0.5, 0.27
unset multiplot
?commands plot with
?commands splot with
?commands plot style
?commands splot style
?plot with
?plot style
?splot with
?splot style
?style
?with
Functions and data may be displayed in one of a large number of styles.
The `with` keyword provides the means of selection.
Syntax:
with <style> { {linestyle | ls <line_style>}
| {{linetype | lt <line_type>}
{linewidth | lw <line_width>}
{linecolor | lc <colorspec>}
{pointtype | pt <point_type>}
{pointsize | ps <point_size>}
{fill | fs <fillstyle>} {fillcolor | fc <colorspec>}
{nohidden3d} {nocontours} {nosurface}
{palette}}
}
where <style> is one of
lines dots steps errorbars xerrorbar xyerrorlines
points impulses fsteps errorlines xerrorlines yerrorbars
linespoints labels histeps financebars xyerrorbars yerrorlines
surface vectors parallelaxes
or
boxes boxplot ellipses histograms rgbalpha
boxerrorbars candlesticks filledcurves image rgbimage
boxxyerror circles fillsteps pm3d zerrorfill
or
table
The first group of styles have associated line, point, and text properties.
The second group of styles also have fill properties. See `fillstyle`. Some
styles have further sub-styles. See `plotting styles` for details of each.
The `table` style produces tabular output rather than a plot. See `set table`.
A default style may be chosen by `set style function` and `set style data`.
By default, each function and data file will use a different line type and
point type, up to the maximum number of available types. All terminal
drivers support at least six different point types, and re-use them, in
order, if more are required. To see the complete set of line and point
types available for the current terminal, type `test`.
If you wish to choose the line or point type for a single plot, <line_type>
and <point_type> may be specified. These are positive integer constants (or
expressions) that specify the line type and point type to be used for the
plot. Use `test` to display the types available for your terminal.
You may also scale the line width and point size for a plot by using
<line_width> and <point_size>, which are specified relative to the default
values for each terminal. The pointsize may also be altered
globally---see `set pointsize` for details. But note that both <point_size>
as set here and as set by `set pointsize` multiply the default point
size---their effects are not cumulative. That is,
`set pointsize 2; plot x w p ps 3` will use points three times default size,
not six.
It is also possible to specify `pointsize variable` either as part of a
line style or for an individual plot. In this case one extra column of input
is required, i.e. 3 columns for a 2D plot and 4 columns for a 3D splot. The
size of each individual point is determined by multiplying the global
pointsize by the value read from the data file.
If you have defined specific line type/width and point type/size combinations
with `set style line`, one of these may be selected by setting <line_style> to
the index of the desired style.
If gnuplot was built with `pm3d` support, the special keyword `palette` is
allowed for smooth color change of lines, points and dots in `splot`. The
color is chosen from a smooth palette which was set previously with the
command `set palette`. The color value corresponds to the z-value of the
point coordinates or to the color coordinate if specified by the 4th parameter
in `using`. Both 2D and 3D plots (`plot` and `splot` commands) can use palette
colors as specified by either their fractional value or the corresponding value
mapped to the colorbox range. A palette color value can also be read from an
explicitly specified input column in the `using` specifier.
See `colors`, `set palette`, `linetype`.
The keyword `nohidden3d` applies only to plots made with the `splot` command.
Normally the global option `set hidden3d` applies to all plots in the graph.
You can attach the `nohidden3d` option to any individual plots that you want
to exclude from the hidden3d processing. The individual elements other than
surfaces (i.e. lines, dots, labels, ...) of a plot marked `nohidden3d` will all
be drawn, even if they would normally be obscured by other plot elements.
Similarly, the keyword `nocontours` will turn off contouring for an individual
plot even if the global property `set contour` is active.
Similarly, the keyword `nosurface` will turn off the 3D surface for an
individual plot even if the global property `set surface` is active.
The keywords may be abbreviated as indicated.
Note that the `linewidth`, `pointsize` and `palette` options are not supported
by all terminals.
Examples:
This plots sin(x) with impulses:
plot sin(x) with impulses
This plots x with points, x**2 with the default:
plot x w points, x**2
This plots tan(x) with the default function style, file "data.1" with lines:
plot [ ] [-2:5] tan(x), 'data.1' with l
This plots "leastsq.dat" with impulses:
plot 'leastsq.dat' w i
This plots the data file "population" with boxes:
plot 'population' with boxes
This plots "exper.dat" with errorbars and lines connecting the points
(errorbars require three or four columns):
plot 'exper.dat' w lines, 'exper.dat' notitle w errorbars
Another way to plot "exper.dat" with errorlines (errorbars require three
or four columns):
plot 'exper.dat' w errorlines
This plots sin(x) and cos(x) with linespoints, using the same line type but
different point types:
plot sin(x) with linesp lt 1 pt 3, cos(x) with linesp lt 1 pt 4
This plots file "data" with points of type 3 and twice usual size:
plot 'data' with points pointtype 3 pointsize 2
This plots file "data" with variable pointsize read from column 4
plot 'data' using 1:2:4 with points pt 5 pointsize variable
This plots two data sets with lines differing only by weight:
plot 'd1' t "good" w l lt 2 lw 3, 'd2' t "bad" w l lt 2 lw 1
This plots filled curve of x*x and a color stripe:
plot x*x with filledcurve closed, 40 with filledcurve y=10
This plots x*x and a color box:
plot x*x, (x>=-5 && x<=5 ? 40 : 1/0) with filledcurve y=10 lt 8
This plots a surface with color lines:
splot x*x-y*y with line palette
This plots two color surfaces at different altitudes:
splot x*x-y*y with pm3d, x*x+y*y with pm3d at t
?commands print
?print
The `print` command prints the value of <expression> to the screen. It is
synonymous with `pause 0`. <expression> may be anything that `gnuplot` can
evaluate that produces a number, or it can be a string.
Syntax:
print <expression> {, <expression>, ...}
See `expressions`. The output file can be set with `set print`.
See also `printerr`.
?commands printerr
?printerr
`printerr` is the same as print except that output is always sent to stderr
even if a prior `set print` command remains in effect.
?commands pwd
?pwd
The `pwd` command prints the name of the working directory to the screen.
Note that if you wish to store the current directory into a string variable
or use it in string expressions, then you can use variable GPVAL_PWD, see
`show variables all`.
?commands quit
?quit
The `exit` and `quit` commands and END-OF-FILE character will exit `gnuplot`.
Each of these commands will clear the output device (as does the `clear`
command) before exiting.
?commands raise
?commands lower
?raise
?lower
Syntax:
raise {plot_window_id}
lower {plot_window_id}
The `raise` and `lower` commands function only for a some terminal types and
may depend also on your window manager and display preference settings.
An example of use is shown here
set term wxt 123 # create first plot window
plot $FOO
lower # lower the only plot window that exists so far
set term wxt 456 # create 2nd plot window may occlude the first one
plot $BAZ
raise 123 # raise first plot window
These commands are known to be unreliable.
?commands refresh
?refresh
The `refresh` command is similar to `replot`, with two major differences.
`refresh` reformats and redraws the current plot using the data already read
in. This means that you can use `refresh` for plots with inline data
(pseudo-device '-') and for plots from datafiles whose contents are volatile.
You cannot use the `refresh` command to add new data to an existing plot.
Mousing operations, in particular zoom and unzoom, will use `refresh` rather
than `replot` if appropriate. Example:
plot 'datafile' volatile with lines, '-' with labels
100 200 "Special point"
e
# Various mousing operations go here
set title "Zoomed in view"
set term post
set output 'zoom.ps'
refresh
?commands replot
?replot
The `replot` command without arguments repeats the last `plot` or `splot`
command. This can be useful for viewing a plot with different `set` options,
or when generating the same plot for several devices.
Arguments specified after a `replot` command will be added onto the last
`plot` or `splot` command (with an implied ',' separator) before it is
repeated. `replot` accepts the same arguments as the `plot` and `splot`
commands except that ranges cannot be specified. Thus you can use `replot`
to plot a function against the second axes if the previous command was `plot`
but not if it was `splot`.
N.B.---use of
plot '-' ; ... ; replot
is not recommended, because it will require that you type in the data all
over again. In most cases you can use the `refresh` command instead, which
will redraw the plot using the data previously read in.
Note that in multiplot mode, `replot` can only reproduce the most recent
component plot, not the full set.
See also `command-line-editing` for ways to edit the last `plot` (`splot`)
command.
See also `show plot` to show the whole current plotting command, and the
possibility to copy it into the `history`.
?commands reread
?reread
The `reread` command causes the current `gnuplot` command file, as specified
by a `load` command or on the command line, to be reset to its starting
point before further commands are read from it. This essentially implements
an endless loop of the commands from the beginning of the command file to
the `reread` command. (But this is not necessarily a disaster---`reread` can
be very useful when used in conjunction with `if`.)
The `reread` command has no effect if input from standard input.
Examples:
Suppose the file "looper" contains the commands
a=a+1
plot sin(x*a)
pause -1
if(a<5) reread
and from within `gnuplot` you submit the commands
a=0
load 'looper'
The result will be five plots (separated by the `pause` message).
Suppose the file "data" contains six columns of numbers with a total yrange
from 0 to 10; the first is x and the next are five different functions of x.
Suppose also that the file "plotter" contains the commands
c_p = c_p+1
plot "$0" using 1:c_p with lines linetype c_p
if(c_p < n_p) reread
and from within `gnuplot` you submit the commands
n_p=6
c_p=1
unset key
set yrange [0:10]
set multiplot
call 'plotter' 'data'
unset multiplot
The result is a single graph consisting of five plots. The yrange must be
set explicitly to guarantee that the five separate graphs (drawn on top of
each other in multiplot mode) will have exactly the same axes. The linetype
must be specified; otherwise all the plots would be drawn with the same type.
See animate.dem in demo directory for an animated example.
?commands reset
?reset
?reset errors
?reset bind
?reset session
The `reset` command causes all graph-related options that can be set with the
`set` command to return to their default values. This command can be used to
restore the default settings after executing a loaded command file, or to
return to a defined state after lots of settings have been changed.
The following are _not_ affected by `reset`.
`set term` `set output` `set loadpath` `set fontpath` `set linetype`
`set encoding` `set decimalsign` `set locale` `set psdir` `set fit`
Note that `reset` does not necessarily return settings to the state they
were in at program entry, because the default values may have been altered by
commands in the initialization files gnuplotrc or $HOME/.gnuplot. However,
these commands can be re-executed by using the variant command `reset session`.
`reset session` deletes any user-defined variables and functions, restores
default settings, and then re-executes the system-wide gnuplotrc initialization
file and any private $HOME/.gnuplot preferences file. See `initialization`.
`reset errors` clears only the error state variables GPVAL_ERRNO and
GPVAL_ERRMSG.
`reset bind` restores all hotkey bindings to their default state.
?commands save
?save set
?save
?save fit
Syntax:
save {functions | variables | terminal | set | fit} '<filename>'
If no option is specified, `gnuplot` saves functions, variables, `set`
options and the last `plot` (`splot`) command.
`save`d files are written in text format and may be read by the
`load` command. For `save` with the `set` option or without any
option, the `terminal` choice and the `output` filename are written
out as a comment, to get an output file that works in other
installations of gnuplot, without changes and without risk of
unwillingly overwriting files.
`save terminal` will write out just the `terminal` status, without
the comment marker in front of it. This is mainly useful for
switching the `terminal` setting for a short while, and getting back
to the previously set terminal, afterwards, by loading the saved
`terminal` status. Note that for a single gnuplot session you may
rather use the other method of saving and restoring current terminal
by the commands `set term push` and `set term pop`, see `set term`.
`save fit` saves only the variables used in the most recent `fit` command.
The saved file may be used as a parameter file to initialize future fit
commands using the `via` keyword.
The filename must be enclosed in quotes.
The special filename "-" may be used to `save` commands to standard output.
On systems which support a popen function (Unix), the output of save can be
piped through an external program by starting the file name with a '|'.
This provides a consistent interface to `gnuplot`'s internal settings to
programs which communicate with `gnuplot` through a pipe. Please see
help for `batch/interactive` for more details.
Examples:
save 'work.gnu'
save functions 'func.dat'
save var 'var.dat'
save set 'options.dat'
save term 'myterm.gnu'
save '-'
save '|grep title >t.gp'
?commands set
?commands show
?set
?show
?show all
The `set` command can be used to set _lots_ of options. No screen is
drawn, however, until a `plot`, `splot`, or `replot` command is given.
The `show` command shows their settings; `show all` shows all the settings.
Options changed using `set` can be returned to the default state by giving the
corresponding `unset` command. See also the `reset` command, which returns
all settable parameters to default values.
The `set` and `unset` commands may optionally contain an iteration clause.
See `plot for`.
?commands set angles
?commands show angles
?set angles
?show angles
?angles
?commands set angles degrees
?set angles degrees
?angles degrees
?degrees
By default, `gnuplot` assumes the independent variable in polar graphs is in
units of radians. If `set angles degrees` is specified before `set polar`,
then the default range is [0:360] and the independent variable has units of
degrees. This is particularly useful for plots of data files. The angle
setting also applies to 3D mapping as set via the `set mapping` command.
Syntax:
set angles {degrees | radians}
show angles
The angle specified in `set grid polar` is also read and displayed in the
units specified by `set angles`.
`set angles` also affects the arguments of the machine-defined functions
sin(x), cos(x) and tan(x), and the outputs of asin(x), acos(x), atan(x),
atan2(x), and arg(x). It has no effect on the arguments of hyperbolic
functions or Bessel functions. However, the output arguments of inverse
hyperbolic functions of complex arguments are affected; if these functions
are used, `set angles radians` must be in effect to maintain consistency
between input and output arguments.
x={1.0,0.1}
set angles radians
y=sinh(x)
print y #prints {1.16933, 0.154051}
print asinh(y) #prints {1.0, 0.1}
but
set angles degrees
y=sinh(x)
print y #prints {1.16933, 0.154051}
print asinh(y) #prints {57.29578, 5.729578}
See also
poldat.dem: polar plot using `set angles` demo.
?commands set arrow
?commands unset arrow
?commands show arrow
?set arrow
?unset arrow
?show arrow
?arrow
?noarrow
Arbitrary arrows can be placed on a plot using the `set arrow` command.
Syntax:
set arrow {<tag>} from <position> to <position>
set arrow {<tag>} from <position> rto <position>
set arrow {<tag>} from <position> length <coord> angle <ang>
set arrow <tag> arrowstyle | as <arrow_style>
set arrow <tag> {nohead | head | backhead | heads}
{size <headlength>,<headangle>{,<backangle>}}
{filled | empty | nofilled | noborder}
{front | back}
{linestyle | ls <line_style>}
{linetype | lt <line_type>}
{linewidth | lw <line_width>}
{linecolor | lc <colorspec>}
{dashtype | dt <dashtype>}
unset arrow {<tag>}
show arrow {<tag>}
<tag> is an integer that identifies the arrow. If no tag is given, the
lowest unused tag value is assigned automatically. The tag can be used to
delete or change a specific arrow. To change any attribute of an existing
arrow, use the `set arrow` command with the appropriate tag and specify the
parts of the arrow to be changed.
The position of the first end point of the arrow is always specified by "from".
The other end point can be specified using any of three different mechanisms.
The <position>s are specified by either x,y or x,y,z, and may be preceded by
`first`, `second`, `graph`, `screen`, or `character` to select the coordinate
system. Unspecified coordinates default to 0. See `coordinates` for details.
A coordinate system specifier does not carry over from the first endpoint
description the second.
1) "to <position>" specifies the absolute coordinates of the other end.
2) "rto <position>" specifies an offset to the "from" position. For linear
axes, `graph` and `screen` coordinates, the distance between the start and the
end point corresponds to the given relative coordinate. For logarithmic axes,
the relative given coordinate corresponds to the factor of the coordinate
between start and end point. Thus, a negative relative value or zero are
not allowed for logarithmic axes.
3) "length <coordinate> angle <angle>" specifies the orientation of the arrow
in the plane of the graph. Again any of the coordinate systems can
be used to specify the length. The angle is always in degrees.
Other characteristics of the arrow can either be specified as a pre-defined
arrow style or by providing them in `set arrow` command. For a detailed
explanation of arrow characteristics, see `arrowstyle`.
Examples:
To set an arrow pointing from the origin to (1,2) with user-defined linestyle 5,
use:
set arrow to 1,2 ls 5
To set an arrow from bottom left of plotting area to (-5,5,3), and tag the
arrow number 3, use:
set arrow 3 from graph 0,0 to -5,5,3
To change the preceding arrow to end at 1,1,1, without an arrow head and
double its width, use:
set arrow 3 to 1,1,1 nohead lw 2
To draw a vertical line from the bottom to the top of the graph at x=3, use:
set arrow from 3, graph 0 to 3, graph 1 nohead
To draw a vertical arrow with T-shape ends, use:
set arrow 3 from 0,-5 to 0,5 heads size screen 0.1,90
To draw an arrow relatively to the start point, where the relative distances
are given in graph coordinates, use:
set arrow from 0,-5 rto graph 0.1,0.1
To draw an arrow with relative end point in logarithmic x axis, use:
set logscale x
set arrow from 100,-5 rto 10,10
This draws an arrow from 100,-5 to 1000,5. For the logarithmic x axis, the
relative coordinate 10 means "factor 10" while for the linear y axis, the
relative coordinate 10 means "difference 10".
To delete arrow number 2, use:
unset arrow 2
To delete all arrows, use:
unset arrow
To show all arrows (in tag order), use:
show arrow
arrows demos.
?commands set autoscale
?commands unset autoscale
?commands show autoscale
?set autoscale
?unset autoscale
?show autoscale
?autoscale
?noautoscale
Autoscaling may be set individually on the x, y or z axis or globally on all
axes. The default is to autoscale all axes. If you want to autoscale based on
a subset of the plots in the figure, you can mark the other ones with the flag
`noautoscale`. See `datafile`.
Syntax:
set autoscale {<axes>{|min|max|fixmin|fixmax|fix} | fix | keepfix}
set autoscale noextend
unset autoscale {<axes>}
show autoscale
where <axes> is either `x`, `y`, `z`, `cb`, `x2`, `y2` or `xy`. A keyword with
`min` or `max` appended (this cannot be done with `xy`) tells `gnuplot` to
autoscale just the minimum or maximum of that axis. If no keyword is given,
all axes are autoscaled.
?noextend
By default autoscaling sets the axis range limits to the nearest tic label
position that includes all the plot data. Keywords `fixmin`, `fixmax`, `fix`
or `noextend` tell gnuplot to disable extension of the axis range to the next
tic mark position. In this case the axis range limit exactly matches the
coordinate of the most extreme data point. `set autoscale noextend` is a
synonym for `set autoscale fix`. Range extension for a single axis can be
disabled by appending the `noextend` keyword to the corresponding range
command, e.g.
set yrange [0:*] noextend
`set autoscale keepfix` autoscales all axes while leaving the fix settings
unchanged.
When autoscaling, the axis range is automatically computed and the dependent
axis (y for a `plot` and z for `splot`) is scaled to include the range of the
function or data being plotted.
If autoscaling of the dependent axis (y or z) is not set, the current y or z
range is used.
Autoscaling the independent variables (x for `plot` and x,y for `splot`) is a
request to set the domain to match any data file being plotted. If there are
no data files, autoscaling an independent variable has no effect. In other
words, in the absence of a data file, functions alone do not affect the x
range (or the y range if plotting z = f(x,y)).
Please see `set xrange` for additional information about ranges.
The behavior of autoscaling remains consistent in parametric mode, (see
`set parametric`). However, there are more dependent variables and hence more
control over x, y, and z axis scales. In parametric mode, the independent or
dummy variable is t for `plot`s and u,v for `splot`s. `autoscale` in
parametric mode, then, controls all ranges (t, u, v, x, y, and z) and allows
x, y, and z to be fully autoscaled.
When tics are displayed on second axes but no plot has been specified for
those axes, x2range and y2range are inherited from xrange and yrange. This
is done _before_ applying offsets or autoextending the ranges to a whole
number of tics, which can cause unexpected results. To prevent this you can
explicitly link the secondary axis range to the primary axis range.
See `set link`.
Examples:
This sets autoscaling of the y axis (other axes are not affected):
set autoscale y
This sets autoscaling only for the minimum of the y axis (the maximum of the
y axis and the other axes are not affected):
set autoscale ymin
This disables extension of the x2 axis tics to the next tic mark,
thus keeping the exact range as found in the plotted data and functions:
set autoscale x2fixmin
set autoscale x2fixmax
This sets autoscaling of the x and y axes:
set autoscale xy
This sets autoscaling of the x, y, z, x2 and y2 axes:
set autoscale
This disables autoscaling of the x, y, z, x2 and y2 axes:
unset autoscale
This disables autoscaling of the z axis only:
unset autoscale z
?commands set autoscale polar
?set autoscale polar
When in polar mode (`set polar`), the xrange and the yrange may be left
in autoscale mode. If `set rrange` is used to limit the extent of the polar
axis, then xrange and yrange will adjust to match this automatically.
However, explicit xrange and yrange commands can later be used to make
further adjustments. See `set rrange`.
See also
polar demos.
?commands show bind
?show bind
`show bind` shows the current state of all hotkey bindings. See `bind`.
?commands set bmargin
?set bmargin
?bmargin
The command `set bmargin` sets the size of the bottom margin.
Please see `set margin` for details.
?commands set border
?commands unset border
?commands show border
?set border
?set border polar
?unset border
?show border
?border
?noborder
The `set border` and `unset border` commands control the display of the graph
borders for the `plot` and `splot` commands. Note that the borders do not
necessarily coincide with the axes; with `plot` they often do, but with
`splot` they usually do not.
Syntax:
set border {<integer>}
{front | back | behind}
{linestyle | ls <line_style>}
{linetype | lt <line_type>} {linewidth | lw <line_width>}
{linecolor | lc <colorspec>} {dashtype | dt <dashtype>}
{polar}
unset border
show border
With a `splot` displayed in an arbitrary orientation, like `set view 56,103`,
the four corners of the x-y plane can be referred to as "front", "back",
"left" and "right". A similar set of four corners exist for the top surface,
of course. Thus the border connecting, say, the back and right corners of the
x-y plane is the "bottom right back" border, and the border connecting the top
and bottom front corners is the "front vertical". (This nomenclature is
defined solely to allow the reader to figure out the table that follows.)
The borders are encoded in a 12-bit integer: the four low bits control the
border for `plot` and the sides of the base for `splot`; the next four bits
control the verticals in `splot`; the four high bits control the edges on top
of an `splot`. The border settings is thus the sum of the appropriate
entries from the following table:
Bit plot splot
1 bottom bottom left front
2 left bottom left back
4 top bottom right front
8 right bottom right back
16 no effect left vertical
32 no effect back vertical
64 no effect right vertical
128 no effect front vertical
256 no effect top left back
512 no effect top right back
1024 no effect top left front
2048 no effect top right front
4096 polar no effect
The default setting is 31, which is all four sides for `plot`, and base and
z axis for `splot`.
In 2D plots the border is normally drawn on top of all plots elements
(`front`). If you want the border to be drawn behind the plot elements,
use `set border back`.
In hidden3d plots the lines making up the border are normally subject to the
same hidden3d processing as the plot elements. `set border behind` will
override this default.
Using the optional <linestyle>, <linetype>, <linewidth>, <linecolor>, and
<dashtype> specifiers, the way the border lines are drawn can be influenced
(limited by what the current terminal driver supports).
Besides the border itself, this line style is used for the tics, independent
of whether they are plotted on the border or on the axes (see `set xtics`).
For `plot`, tics may be drawn on edges other than bottom and left by enabling
the second axes -- see `set xtics` for details.
If a `splot` draws only on the base, as is the case with "`unset surface; set
contour base`", then the verticals and the top are not drawn even if they are
specified.
The `set grid` options 'back', 'front' and 'layerdefault' also
control the order in which the border lines are drawn with respect to
the output of the plotted data.
The `polar` keyword enables a circular border for polar plots.
Examples:
Draw default borders:
set border
Draw only the left and bottom (`plot`) or both front and back bottom left
(`splot`) borders:
set border 3
Draw a complete box around a `splot`:
set border 4095
Draw a topless box around a `splot`, omitting the front vertical:
set border 127+256+512 # or set border 1023-128
Draw only the top and right borders for a `plot` and label them as axes:
unset xtics; unset ytics; set x2tics; set y2tics; set border 12
?commands set boxwidth
?commands show boxwidth
?set boxwidth
?show boxwidth
?boxwidth
The `set boxwidth` command is used to set the default width of boxes in the
`boxes`, `boxerrorbars`, `boxplot`, `candlesticks` and `histograms` styles.
Syntax:
set boxwidth {<width>} {absolute|relative}
show boxwidth
By default, adjacent boxes are extended in width until they touch each other.
A different default width may be specified using the `set boxwidth` command.
`Relative` widths are interpreted as being a fraction of this default width.
An explicit value for the boxwidth is interpreted as being a number of units
along the current x axis (`absolute`) unless the modifier `relative` is given.
If the x axis is a log-scale (see `set log`) then the value of boxwidth is
truly "absolute" only at x=1; this physical width is maintained everywhere
along the axis (i.e. the boxes do not become narrower the value of x
increases). If the range spanned by a log scale x axis is far from x=1,
some experimentation may be required to find a useful value of boxwidth.
The default is superseded by explicit width information taken from an extra
data column in styles `boxes` or `boxerrorbars`. In a four-column data set,
the fourth column will be interpreted as the box width unless the width is set
to -2.0, in which case the width will be calculated automatically.
See `style boxes` and `style boxerrorbars` for more details.
To set the box width to automatic use the command
set boxwidth
or, for four-column data,
set boxwidth -2
The same effect can be achieved with the `using` keyword in `plot`:
plot 'file' using 1:2:3:4:(-2)
To set the box width to half of the automatic size use
set boxwidth 0.5 relative
To set the box width to an absolute value of 2 use
set boxwidth 2 absolute
?commands set color
?set color
Gnuplot supports two alternative sets of linetypes. The default set uses a
different color for each linetype, although it also allows you to draw dotted
or dashed lines in that color. The alternative monochrome set uses only
dot/dash pattern or linewidth to distinguish linetypes. The `set color`
command selects the color linetypes. See `set monochrome`, `set linetype`,
and `set colorsequence`.
?commands set colorsequence
?set colorsequence
?colorsequence
Syntax:
set colorsequence {default|classic|podo}
`set colorsequence default` selects a terminal-independent repeating sequence
of eight colors. See `set linetype`, `colors`.
`set colorsequence classic` lets each separate terminal type provide its own
sequence of line colors. The number provided varies from 4 to more than 100,
but most start with red/green/blue/magenta/cyan/yellow.
This was the default behaviour of earlier gnuplot versions.
`set colorsequence podo` selects eight colors drawn from a set recommended by
Wong (2011) [Nature Methods 8:441] as being easily distinguished by color-blind
viewers with either protanopia or deuteranopia.
In each case you can further customize the length of the sequence and the
colors used. See `set linetype`, `colors`.
?commands set clabel
?commands unset clabel
?commands show clabel
?set clabel
?unset clabel
?show clabel
?clabel
This command is obsolete. Use `set cntrlabel` instead.
`unset clabel` is replaced by `set cntrlabel onecolor`.
`set clabel "format"` is replaced by `set cntrlabel format "format"`.
?commands set clip
?commands unset clip
?commands show clip
?set clip
?unset clip
?show clip
?clip
Syntax:
set clip {points|one|two}
unset clip {points|one|two}
show clip
Default state:
unset clip points
set clip one
unset clip two
Data points whose center lies inside the plot boundaries are normally drawn
even if the finite size of the point symbol causes it to extend past a boundary
line. `set clip points` causes such points to be clipped (i.e. not drawn) even
though the point center is inside the boundaries of a 2D plot.
Data points whose center lies outside the plot boundaries are never drawn.
Normally a line segment in a plot is not drawn if either end of the segment
lies outside the plot boundaries (i.e. xrange and yrange).
`set clip one` causes `gnuplot` to draw also the in-range portion of line
segments with one endpoint out of range.
`set clip two` causes `gnuplot` to draw also the in-range portion of line
segments with both endpoints out of range.
Line segments that lie entirely outside the plot boundaries are never drawn.
Notes:
* `set clip` affects only points and lines produced by plot styles `lines`,
`linespoints`, `points`, and `vectors`.
* Clipping of colored quadrangles drawn for `pm3d` maps and surfaces is
controlled `set pm3d clip1in` and `set pm3d clip4in`.
* Object clipping is controlled by the `{clip|noclip}` property of the
individual object.
?commands set cntrlabel
?commands show cntrlabel
?set cntrlabel
?show cntrlabel
?cntrlabel
Syntax:
set cntrlabel {format "format"} {font "font"}
set cntrlabel {start <int>} {interval <int>}
set contrlabel onecolor
`set cntrlabel` controls the labeling of contours, either in the key (default)
or on the plot itself in the case of `splot ... with labels`. In the latter
case labels are placed along each contour line according to the `pointinterval`
or `pointnumber` property of the label descriptor. By default a label is
placed on the 5th line segment making up the contour line and repeated every
20th segment. These defaults are equivalent to
set cntrlabel start 5 interval 20
They can be changed either via the `set cntrlabel` command or by specifying the
interval in the `splot` command itself
set contours; splot $FOO with labels point pointinterval -1
Setting the interval to a negative value means that the label appear only
once per contour line. However if `set samples` or `set isosamples` is large
then many contour lines may be created, each with a single label.
A contour label is placed in the plot key for each linetype used. By default
each contour level is given its own linetype, so a separate label appears for
each. The command `set cntrlabel onecolor` causes all contours to be drawn
using the same linetype, so only one label appears in the plot key.
This command replaces an older command `unset clabel`.
?commands set cntrparam
?commands show cntrparam
?set cntrparam
?show cntrparam
?cntrparam
`set cntrparam` controls the generation of contours and their smoothness for
a contour plot. `show contour` displays current settings of `cntrparam` as
well as `contour`.
Syntax:
set cntrparam { { linear
| cubicspline
| bspline
| points <n>
| order <n>
| levels { auto {<n>} | <n>
| discrete <z1> {,<z2>{,<z3>...}}
| incremental <start>, <incr> {,<end>}
}
}
}
show contour
This command has two functions. First, it sets the values of z for which
contour points are to be determined (by linear interpolation between data
points or function isosamples.) Second, it controls the way contours are
drawn between the points determined to be of equal z. <n> should be an
integral constant expression and <z1>, <z2> ... any constant expressions.
The parameters are:
`linear`, `cubicspline`, `bspline`---Controls type of approximation or
interpolation. If `linear`, then straight line segments connect points of
equal z magnitude. If `cubicspline`, then piecewise-linear contours are
interpolated between the same equal z points to form somewhat smoother
contours, but which may undulate. If `bspline`, a guaranteed-smoother curve
is drawn, which only approximates the position of the points of equal-z.
`points`---Eventually all drawings are done with piecewise-linear strokes.
This number controls the number of line segments used to approximate the
`bspline` or `cubicspline` curve. Number of cubicspline or bspline
segments (strokes) = `points` * number of linear segments.
`order`---Order of the bspline approximation to be used. The bigger this
order is, the smoother the resulting contour. (Of course, higher order
bspline curves will move further away from the original piecewise linear
data.) This option is relevant for `bspline` mode only. Allowed values are
integers in the range from 2 (linear) to 10.
`levels`--- Selection of contour levels, controlled by `auto` (default),
`discrete`, `incremental`, and <n>, number of contour levels.
For `auto`, <n> specifies a nominal number of levels; the actual number will
be adjusted to give simple labels. If the surface is bounded by zmin and zmax,
contours will be generated at integer multiples of dz between zmin and zmax,
where dz is 1, 2, or 5 times some power of ten (like the step between two
tic marks).
For `levels discrete`, contours will be generated at z = <z1>, <z2> ... as
specified; the number of discrete levels sets the number of contour levels.
In `discrete` mode, any `set cntrparam levels <n>` are ignored.
For `incremental`, contours are generated at values of z beginning at <start>
and increasing by <increment>, until the number of contours is reached. <end>
is used to determine the number of contour levels, which will be changed by
any subsequent `set cntrparam levels <n>`. If the z axis is logarithmic,
<increment> will be interpreted as a factor, just like in `set ztics`.
If the command `set cntrparam` is given without any arguments specified, the
defaults are used: linear, 5 points, order 4, 5 auto levels.
Examples:
set cntrparam bspline
set cntrparam points 7
set cntrparam order 10
To select levels automatically, 5 if the level increment criteria are met:
set cntrparam levels auto 5
To specify discrete levels at .1, .37, and .9:
set cntrparam levels discrete .1,1/exp(1),.9
To specify levels from 0 to 4 with increment 1:
set cntrparam levels incremental 0,1,4
To set the number of levels to 10 (changing an incremental end or possibly
the number of auto levels):
set cntrparam levels 10
To set the start and increment while retaining the number of levels:
set cntrparam levels incremental 100,50
See also `set contour` for control of where the contours are drawn, and
`set cntrlabel` for control of the format of the contour labels and linetypes.
See also
contours demo (contours.dem)
and
contours with user defined levels demo (discrete.dem).
?commands set colorbox
?commands show colorbox
?commands unset colorbox
?set colorbox
?show colorbox
?unset colorbox
?colorbox
The color scheme, i.e. the gradient of the smooth color with min_z and
max_z values of `pm3d`'s `palette`, is drawn in a color box unless `unset
colorbox`.
set colorbox
set colorbox {
{ vertical | horizontal } {{no}invert}
{ default | user }
{ origin x, y }
{ size x, y }
{ front | back }
{ noborder | bdefault | border [line style] }
}
show colorbox
unset colorbox
Color box position can be `default` or `user`. If the latter is specified the
values as given with the `origin` and `size` subcommands are used. The box
can be drawn after (`front`) or before (`back`) the graph or the surface.
The orientation of the color gradient can be switched by options `vertical`
and `horizontal`.
`origin x, y` and `size x, y` are used only in combination with the `user`
option. The x and y values are interpreted as screen coordinates by default,
and this is the only legal option for 3D plots. 2D plots, including splot with
`set view map`, allow any coordinate system to be specified. Try for example:
set colorbox horiz user origin .1,.02 size .8,.04
which will draw a horizontal gradient somewhere at the bottom of the graph.
`border` turns the border on (this is the default). `noborder` turns the border
off. If an positive integer argument is given after `border`, it is used as a
line style tag which is used for drawing the border, e.g.:
set style line 2604 linetype -1 linewidth .4
set colorbox border 2604
will use line style `2604`, a thin line with the default border color (-1)
for drawing the border. `bdefault` (which is the default) will use the default
border line style for drawing the border of the color box.
The axis of the color box is called `cb` and it is controlled by means of the
usual axes commands, i.e. `set/unset/show` with `cbrange`, `[m]cbtics`,
`format cb`, `grid [m]cb`, `cblabel`, and perhaps even `cbdata`, `[no]cbdtics`,
`[no]cbmtics`.
`set colorbox` without any parameter switches the position to default.
`unset colorbox` resets the default parameters for the colorbox and switches
the colorbox off.
See also help for `set pm3d`, `set palette`, `x11 pm3d`, and `set style line`.
?colornames
?show colornames
?commands show colornames
?show palette colornames
Gnuplot knows a limited number of color names. You can use these to define
the color range spanned by a pm3d palette, or to assign a terminal-independent
color to a particular linetype or linestyle. To see the list of known color
names, use the command `show colornames`. Example:
set style line 1 linecolor "sea-green"
?commands set contour
?commands unset contour
?commands show contour
?set contour
?unset contour
?show contour
?contour
?contours
?nocontour
`set contour` enables contour drawing for surfaces. This option is available
for `splot` only. It requires grid data, see `grid_data` for more details.
If contours are desired from non-grid data, `set dgrid3d` can be used to
create an appropriate grid.
Syntax:
set contour {base | surface | both}
unset contour
show contour
The three options specify where to draw the contours: `base` draws the
contours on the grid base where the x/ytics are placed, `surface` draws the
contours on the surfaces themselves, and `both` draws the contours on both
the base and the surface. If no option is provided, the default is `base`.
See also `set cntrparam` for the parameters that affect the drawing of
contours, and `set cntrlabel` for control of labeling of the contours.
The surface can be switched off (see `unset surface`), giving a contour-only
graph. Though it is possible to use `set size` to enlarge the plot to fill
the screen, more control over the output format can be obtained by writing
the contour information to a datablock, and rereading it as a 2D datafile plot:
unset surface
set contour
set cntrparam ...
set table $datablock
splot ...
unset table
# contour info now in $datablock
set term <whatever>
plot $datablock
In order to draw contours, the data should be organized as "grid data". In
such a file all the points for a single y-isoline are listed, then all the
points for the next y-isoline, and so on. A single blank line (a line
containing no characters other than blank spaces and a carriage return and/or
a line feed) separates one y-isoline from the next.
See also `splot datafile`.
See also
contours demo (contours.dem)
and
contours with user defined levels demo (discrete.dem).
?commands set dashtype
?commands show dashtype
?set dashtype
?show dashtype
The `set dashtype` command allows you to define a dash pattern that can
then be referred to by its index. This is purely a convenience, as anywhere
that would accept the dashtype by its numerical index would also accept an
explicit dash pattern.
Example:
set dashtype 5 (2,4,2,6) # define or redefine dashtype number 5
plot f1(x) dt 5 # plot using the new dashtype
plot f1(x) dt (2,4,2,6) # exactly the same plot as above
set linetype 5 dt 5 # always use this dash pattern with linetype 5
set dashtype 66 "..-" # define a new dashtype using a string
See also `dashtype`.
?set data style
This form of the command is deprecated. Please see `set style data`.
?set datafile
?show datafile
The `set datafile` command options control interpretation of fields read from
input data files by the `plot`, `splot`, and `fit` commands. Six such
options are currently implemented.
?set datafile fortran
?show datafile fortran
?fortran
The `set datafile fortran` command enables a special check for values in the
input file expressed as Fortran D or Q constants. This extra check slows down
the input process, and should only be selected if you do in fact have datafiles
containing Fortran D or Q constants. The option can be disabled again using
`unset datafile fortran`.
?set datafile nofpe_trap
?fpe_trap
?nofpe_trap
The `set datafile nofpe_trap` command tells gnuplot not to re-initialize a
floating point exception handler before every expression evaluation used while
reading data from an input file. This can significantly speed data input from
very large files at the risk of program termination if a floating-point
exception is generated.
?set datafile missing
?show datafile missing
?set missing
?missing
Syntax:
set datafile missing "<string>"
set datafile missing NaN
show datafile missing
unset datafile
The `set datafile missing` command tells `gnuplot` there is a special string
used in input data files to denote a missing data entry. There is no default
character for `missing`. Gnuplot makes a distinction between missing data and
invalid data (e.g. "NaN", 1/0.). For example invalid data causes a gap in a
line drawn through sequential data points; missing data does not.
Non-numeric characters found in a numeric field will usually be interpreted as
invalid rather than as a missing data point unless they happen to match the
`missing` string.
Conversely `set datafile missing NaN` causes all data or expressions evaluating
to not-a-number (NaN) to be treated as missing data.
Note: The treatment of missing or invalid data values in certain cases has
changed in this version of gnuplot.
The example below shows differences between gnuplot version 4 and version 5.
Example:
set style data linespoints
plot '-' title "(a)"
1 10
2 20
3 ?
4 40
5 50
e
set datafile missing "?"
plot '-' title "(b)"
1 10
2 20
3 ?
4 40
5 50
e
plot '-' using 1:2 title "(c)"
1 10
2 20
3 NaN
4 40
5 50
e
plot '-' using 1:($2) title "(d)"
1 10
2 20
3 NaN
4 40
5 50
e
Plot (a) differs in gnuplot 4 and gnuplot 5 because the third line contains
only one valid number. Version 4 switched to a single-datum-on-a-line
convention that the line number is "x" and the datum is "y", erroneously
placing the point at(2,3).
Both the old and new gnuplot versions handle the same data correctly if the
'?' character is designated as a marker for missing data (b).
Old gnuplot versions handled NaN differently depending of the form of the
`using` clause, as shown in plots (c) and (d). Gnuplot now handles NaN the
same whether the input column was specified as N or ($N). See also the
imageNaN demo.
As of version 5.0.6 this is also true for the missing value flag.
Earlier versions failed to recognize the missing value flag if the plot
command specified `using ($N)` rather than `using N`. Note, however, that
even in current gnuplot using a "missing" value for computation will result
in NaN. I.e. a `missing` string in either columns 1 or 2 will cause
`using ($1+$2)` to evaluate as NaN. If you nevertheless want to treat this
as missing data, use the command `set datafile missing NaN`.
?set datafile separator
?show datafile separator
?datafile separator
?separator
The command `set datafile separator` tells `gnuplot` that data fields in
subsequent input files are separated by a specific character rather than by
whitespace. The most common use is to read in csv (comma-separated value)
files written by spreadsheet or database programs. By default data fields
are separated by whitespace.
Syntax:
set datafile separator {whitespace | tab | comma | "<chars>"}
Examples:
# Input file contains tab-separated fields
set datafile separator "\t"
# Input file contains comma-separated values fields
set datafile separator comma
# Input file contains fields separated by either * or |
set datafile separator "*|"
?set datafile commentschars
?commentschars
The command `set datafile commentschars` specifies what characters can be used
in a data file to begin comment lines. If the first non-blank character on a
line is one of these characters then the rest of the data line is ignored.
Default value of the string is "#!" on VMS and "#" otherwise.
Syntax:
set datafile commentschars {"<string>"}
show datafile commentschars
unset commentschars
Then, the following line in a data file is completely ignored
# 1 2 3 4
but the following
1 # 3 4
will be interpreted as garbage in the 2nd column followed by valid data in
the 3rd and 4th columns.
Example:
set datafile commentschars "#!%"
?set datafile binary
The `set datafile binary` command is used to set the defaults when reading
binary data files. The syntax matches precisely that used for commands
`plot` and `splot`. See `binary matrix` and `binary general` for details
about the keywords that can be present in <binary list>.
Syntax:
set datafile binary <binary list>
show datafile binary
show datafile
unset datafile
Examples:
set datafile binary filetype=auto
set datafile binary array=(512,512) format="%uchar"
?show datafile binary
show datafile binary # list current settings
?commands set decimalsign
?commands show decimalsign
?commands unset decimalsign
?set decimalsign
?show decimalsign
?unset decimalsign
?decimalsign
The `set decimalsign` command selects a decimal sign for numbers printed
into tic labels or `set label` strings.
Syntax:
set decimalsign {<value> | locale {"<locale>"}}
unset decimalsign
show decimalsign
The argument <value> is a string to be used in place of the usual
decimal point. Typical choices include the period, '.', and the comma,
',', but others may be useful, too. If you omit the <value> argument,
the decimal separator is not modified from the usual default, which is
a period. Unsetting decimalsign has the same effect as omitting <value>.
Example:
Correct typesetting in most European countries requires:
set decimalsign ','
Please note: If you set an explicit string, this affects only numbers that
are printed using gnuplot's gprintf() formatting routine, including axis tics.
It does not affect the format expected for input data, and it does not affect
numbers printed with the sprintf() formatting routine. To change the behavior
of both input and output formatting, instead use the form
set decimalsign locale
This instructs the program to use both input and output formats in accordance
with the current setting of the LC_ALL, LC_NUMERIC, or LANG environmental
variables.
set decimalsign locale "foo"
This instructs the program to format all input and output in accordance with
locale "foo", which must be installed. If locale "foo" is not found then an
error message is printed and the decimal sign setting is unchanged.
On linux systems you can get a list of the locales installed on your machine by
typing "locale -a". A typical linux locale string is of the form "sl_SI.UTF-8".
A typical Windows locale string is of the form "Slovenian_Slovenia.1250" or
"slovenian". Please note that interpretation of the locale settings is done by
the C library at runtime. Older C libraries may offer only partial support for
locale settings such as the thousands grouping separator character.
set decimalsign locale; set decimalsign "."
This sets all input and output to use whatever decimal sign is correct for
the current locale, but over-rides this with an explicit '.' in numbers
formatted using gnuplot's internal gprintf() function.
?commands set dgrid3d
?commands unset dgrid3d
?commands show dgrid3d
?set dgrid3d
?unset dgrid3d
?show dgrid3d
?dgrid3d
?nodgrid3d
The `set dgrid3d` command enables, and can set parameters for, non-grid to
grid data mapping. See `splot grid_data` for more details about the grid data
structure.
Syntax:
set dgrid3d {<rows>} {,{<cols>}}
{ splines |
qnorm {<norm>} |
(gauss | cauchy | exp | box | hann)
{kdensity} {<dx>} {,<dy>} }
unset dgrid3d
show dgrid3d
By default `dgrid3d` is disabled. When enabled, 3D data read from a file
are always treated as a scattered data set. A grid with dimensions derived
from a bounding box of the scattered data and size as specified by the
row/col_size parameters is created for plotting and contouring. The grid
is equally spaced in x (rows) and in y (columns); the z values are computed
as weighted averages or spline interpolations of the scattered points' z
values. In other words, a regularly spaced grid is created and the a smooth
approximation to the raw data is evaluated for all grid points. This
approximation is plotted in place of the raw data.
The number of columns defaults to the number of rows, which defaults to 10.
Several algorithms are available to calculate the approximation from the
raw data. Some of these algorithms can take additional parameters.
These interpolations are such the closer the data point is to a grid point,
the more effect it has on that grid point.
The `splines` algorithm calculates an interpolation based on "thin plate
splines". It does not take additional parameters.
The `qnorm` algorithm calculates a weighted average of the input data at
each grid point. Each data point is weighted inversely by its distance from
the grid point raised to the norm power. (Actually, the weights are given
by the inverse of dx^norm + dy^norm, where dx and dy are the components of
the separation of the grid point from each data point. For some norms
that are powers of two, specifically 4, 8, and 16, the computation is
optimized by using the Euclidean distance in the weight calculation,
(dx^2+dy^2)^norm/2. However, any non-negative integer can be used.)
The power of the norm can be specified as a single optional parameter.
This algorithm is the default.
Finally, several smoothing kernels are available to calculate weighted
averages: z = Sum_i w(d_i) * z_i / Sum_i w(d_i), where z_i is the value
of the i-th data point and d_i is the distance between the current grid
point and the location of the i-th data point. All kernels assign higher
weights to data points that are close to the current grid point and lower
weights to data points further away.
The following kernels are available:
gauss : w(d) = exp(-d*d)
cauchy : w(d) = 1/(1 + d*d)
exp : w(d) = exp(-d)
box : w(d) = 1 if d<1
= 0 otherwise
hann : w(d) = 0.5*(1-cos(2*pi*d)) if d<1
w(d) = 0 otherwise
When using one of these five smoothing kernels, up to two additional
numerical parameters can be specified: dx and dy. These are used to
rescale the coordinate differences when calculating the distance:
d_i = sqrt( ((x-x_i)/dx)**2 + ((y-y_i)/dy)**2 ), where x,y are the
coordinates of the current grid point and x_i,y_i are the coordinates
of the i-th data point. The value of dy defaults to the value of dx,
which defaults to 1. The parameters dx and dy make it possible to
control the radius over which data points contribute to a grid point
IN THE UNITS OF THE DATA ITSELF.
The optional keyword `kdensity`, which must come after the name of the
kernel, but before the (optional) scale parameters, modifies the algorithm
so that the values calculated for the grid points are not divided by the
sum of the weights ( z = Sum_i w(d_i) * z_i ). If all z_i are constant,
this effectively plots a bivariate kernel density estimate: a kernel
function (one of the five defined above) is placed at each data point,
the sum of these kernels is evaluated at every grid point, and this smooth
surface is plotted instead of the original data. This is similar in
principle to + what the `smooth kdensity` option does to 1D datasets.
(See kdensity2d.dem for usage demo)
A slightly different syntax is also supported for reasons of backwards
compatibility. If no interpolation algorithm has been explicitly selected,
the `qnorm` algorithm is assumed. Up to three comma-separated, optional
parameters can be specified, which are interpreted as the the number of
rows, the number of columns, and the norm value, respectively.
The `dgrid3d` option is a simple scheme which replaces scattered data
with weighted averages on a regular grid. More sophisticated approaches
to this problem exist and should be used to preprocess the data outside
`gnuplot` if this simple solution is found inadequate.
See also
dgrid3d.dem: dgrid3d demo.
and
scatter.dem: dgrid3d demo.
?commands set dummy
?commands show dummy
?set dummy
?show dummy
?unset dummy
?dummy
The `set dummy` command changes the default dummy variable names.
Syntax:
set dummy {<dummy-var>} {,<dummy-var>}
show dummy
By default, `gnuplot` assumes that the independent, or "dummy", variable for
the `plot` command is "t" if in parametric or polar mode, or "x" otherwise.
Similarly the independent variables for the `splot` command are "u" and "v"
in parametric mode (`splot` cannot be used in polar mode), or "x" and "y"
otherwise.
It may be more convenient to call a dummy variable by a more physically
meaningful or conventional name. For example, when plotting time functions:
set dummy t
plot sin(t), cos(t)
Examples:
set dummy u,v
set dummy ,s
The second example sets the second variable to s. To reset the dummy variable
names to their default values, use
unset dummy
?commands set encoding
?commands show encoding
?set encoding
?show encoding
?encoding
?encodings
?utf8
?sjis
The `set encoding` command selects a character encoding.
Syntax:
set encoding {<value>}
set encoding locale
show encoding
Valid values are
default - tells a terminal to use its default encoding
iso_8859_1 - the most common Western European encoding prior to UTF-8.
Known in the PostScript world as 'ISO-Latin1'.
iso_8859_15 - a variant of iso_8859_1 that includes the Euro symbol
iso_8859_2 - used in Central and Eastern Europe
iso_8859_9 - used in Turkey (also known as Latin5)
koi8r - popular Unix cyrillic encoding
koi8u - Ukrainian Unix cyrillic encoding
cp437 - codepage for MS-DOS
cp850 - codepage for OS/2, Western Europe
cp852 - codepage for OS/2, Central and Eastern Europe
cp950 - MS version of Big5 (emf terminal only)
cp1250 - codepage for MS Windows, Central and Eastern Europe
cp1251 - codepage for 8-bit Russian, Serbian, Bulgarian, Macedonian
cp1252 - codepage for MS Windows, Western Europe
cp1254 - codepage for MS Windows, Turkish (superset of Latin5)
sjis - shift-JIS Japanese encoding
utf8 - variable-length (multibyte) representation of Unicode
entry point for each character
The command `set encoding locale` is different from the other options.
It attempts to determine the current locale from the runtime environment.
On most systems this is controlled by the environmental variables
LC_ALL, LC_CTYPE, or LANG. This mechanism is necessary, for example, to
pass multibyte character encodings such as UTF-8 or EUC_JP to the wxt
and cairopdf terminals. This command does not affect the locale-specific
representation of dates or numbers.
See also `set locale` and `set decimalsign`.
Generally you must set the encoding before setting the terminal type, as it
may affect the choice of appropriate fonts.
?commands set errorbars
?commands show errorbars
?set errorbars
?show errorbars
?errorbars
?commands set bars
?commands show bars
?set bars
?show bars
?bars
The `set errorbars` command controls the tics at the ends of error bars,
and also at the end of the whiskers belonging to a boxplot.
Syntax:
set errorbars {small | large | fullwidth | <size>} {front | back}
{line-properties}
unset errorbars
show errorbars
`small` is a synonym for 0.0 (no crossbar), and `large` for 1.0.
The default is 1.0 if no size is given.
The keyword `fullwidth` is relevant only to boxplots and to histograms with
errorbars. It sets the width of the errorbar ends to be the same as the width
of the associated box. It does not change the width of the box itself.
The `front` and `back` keywords are relevant only to errorbars attached
to filled rectangles (boxes, candlesticks, histograms).
Error bars are by default drawn using the same line properties as the border
of the associated box. You can change this by providing a separate set of
line properties for the error bars.
set errorbars linecolor black linewidth 0.5 dashtype '.'
?commands set fit
?commands show fit
?set fit
?show fit
?set fit quiet
?set fit verbose
?set fit brief
?set fit results
?set fit prescale
?set fit limit
?set fit maxiter
?set fit errorscaling
?set fit errorvariables
?set fit logfile
?set fit script
?set fit v4
?set fit v5
The `set fit` command controls the options for the `fit` command.
Syntax:
set fit {nolog | logfile {"<filename>"|default}}
{{no}quiet|results|brief|verbose}
{{no}errorvariables}
{{no}covariancevariables}
{{no}errorscaling}
{{no}prescale}
{maxiter <value>|default}
{limit <epsilon>|default}
{limit_abs <epsilon_abs>}
{start-lambda <value>|default}
{lambda-factor <value>|default}
{script {"<command>"|default}}
{v4 | v5}
unset fit
show fit
The `logfile` option defines where the `fit` command writes its output. The
<filename> argument must be enclosed in single or double quotes. If no
filename is given or `unset fit` is used the log file is reset to its default
value "fit.log" or the value of the environmental variable `FIT_LOG`. If the
given logfile name ends with a / or \, it is interpreted to be a directory
name, and the actual filename will be "fit.log" in that directory.
By default the information written to the log file is also echoed to the
terminal session. `set fit quiet` turns off the echo, whereas `results`
prints only final results. `brief` gives one line summaries for every
iteration of the fit in addition. `verbose` yields detailed iteration
reports as it was the default before version 5.
If the `errorvariables` option is turned on, the error of each fitted
parameter computed by `fit` will be copied to a user-defined variable
whose name is formed by appending "_err" to the name of the parameter
itself. This is useful mainly to put the parameter and its error onto
a plot of the data and the fitted function, for reference, as in:
set fit errorvariables
fit f(x) 'datafile' using 1:2 via a, b
print "error of a is:", a_err
set label 1 sprintf("a=%6.2f +/- %6.2f", a, a_err)
plot 'datafile' using 1:2, f(x)
If the `errorscaling` option is specified, which is the default, the
calculated parameter errors are scaled with the reduced chi square. This is
equivalent to providing data errors equal to the calculated standard
deviation of the fit (FIT_STDFIT) resulting in a reduced chi square of one.
With the `noerrorscaling` option the estimated errors are the unscaled
standard deviations of the fit parameters.
If no weights are specified for the data, parameter errors are always scaled.
If the `prescale` option is turned on, parameters are prescaled by their
initial values before being passed to the Marquardt-Levenberg
routine. This helps tremendously if there are parameters that differ
in size by many orders of magnitude. Fit parameters with an initial value
of exactly zero are never prescaled.
The maximum number of iterations may be limited with the `maxiter` option.
A value of 0 or `default` means that there is no limit.
The `limit` option can be used to change the default epsilon limit (1e-5) to
detect convergence. When the sum of squared residuals changes by a factor
less than this number (epsilon), the fit is considered to have 'converged'.
The `limit_abs` option imposes an additional absolute limit in the change
of the sum of squared residuals and defaults to zero.
If you need even more control about the algorithm, and know the
Marquardt-Levenberg algorithm well, the following options can be used to
influence it. The startup value of `lambda` is normally calculated
automatically from the ML-matrix, but if you want to, you may provide your
own using the `start_lambda` option. Setting it to `default` will
re-enable the automatic selection. The option `lambda_factor` sets the factor
by which `lambda` is increased or decreased whenever the chi-squared target
function increased or decreased significantly. Setting it to `default`
re-enables the default factor of 10.0.
The `script` option may be used to specify a `gnuplot` command to be executed
when a fit is interrupted---see `fit`. This setting takes precedence over
the default of `replot` and the environment variable `FIT_SCRIPT`.
If the `covariancevariables` option is turned on, the covariances between
final parameters will be saved to user-defined variables. The variable name
for a certain parameter combination is formed by prepending "FIT_COV_" to
the name of the first parameter and combining the two parameter names by
"_". For example given the parameters "a" and "b" the covariance variable is
named "FIT_COV_a_b".
In version 5 the syntax of the fit command changed and it now defaults to
unitweights if no 'error' keyword is given. The `v4` option restores the
default behavior of gnuplot version 4, see also `fit`.
?commands set fontpath
?commands show fontpath
?set fontpath
?show fontpath
?fontpath
The `fontpath` setting defines additional locations for font files
searched when including font files. Currently only the postscript terminal
supports `fontpath`. If a file cannot be found in the current directory,
the directories in `fontpath` are tried. Further documentation concerning
the supported file formats is included in the `terminal postscript` section
of the documentation.
Syntax:
set fontpath {"pathlist1" {"pathlist2"...}}
show fontpath
Path names may be entered as single directory names, or as a list of
path names separated by a platform-specific path separator, eg. colon
(':') on Unix, semicolon (';') on DOS/Windows/OS/2 platforms.
The `show fontpath`, `save` and `save set` commands replace the
platform-specific separator with a space character (' ') for maximum
portability. If a directory name ends with an exclamation mark ('!') also
the subdirectories of this directory are searched for font files.
If the environmental variable GNUPLOT_FONTPATH is set, its contents are
appended to `fontpath`. If it is not set, a system dependent default value
is used. It is set by testing several directories for existence when using
the fontpath the first time. Thus, the first call of `set fontpath`,
`show fontpath`, `save fontpath`, `plot`, or `splot` with embedded font
files takes a little more time. If you want to save this time you may
set the environmental variable GNUPLOT_FONTPATH since probing is switched
off, then. You can find out which is the default fontpath by using
`show fontpath`.
`show fontpath` prints the contents of the user-defined fontpath and the
system fontpath separately. However, the `save` and `save set` commands
save only the user-specified parts of `fontpath`.
For terminal drivers that access fonts by filename via the gd library, the
font search path is controlled by the environmental variable GDFONTPATH.
?commands set format
?commands show format
?set format
?show format
?format
?format cb
The format of the tic-mark labels can be set with the `set format` command
or with the `set tics format` or individual `set {axis}tics format` commands.
Syntax:
set format {<axes>} {"<format-string>"} {numeric|timedate|geographic}
show format
where <axes> is either `x`, `y`, `xy`, `x2`, `y2`, `z`, `cb` or nothing
(which applies the format to all axes). The following two commands are
equivalent:
set format y "%.2f"
set ytics format "%.2f"
The length of the string is restricted to 100 characters. The default format
is "% h", "$%h$" for LaTeX terminals. Other formats such as "%.2f" or "%3.0em"
are often desirable. "set format" with no following string will restore the
default.
If the empty string "" is given, tics will have no labels, although the tic
mark will still be plotted. To eliminate the tic marks, use `unset xtics` or
`set tics scale 0`.
Newline (\n) and enhanced text markup is accepted in the format string.
Use double-quotes rather than single-quotes in this case. See also `syntax`.
Characters not preceded by "%" are printed verbatim. Thus you can include
spaces and labels in your format string, such as "%g m", which will put " m"
after each number. If you want "%" itself, double it: "%g %%".
See also `set xtics` for more information about tic labels, and
`set decimalsign` for how to use non-default decimal separators in numbers
printed this way.
See also
electron demo (electron.dem).
?gprintf
The string function gprintf("format",x) uses gnuplot's own format specifiers,
as do the gnuplot commands `set format`, `set timestamp`, and others. These
format specifiers are not the same as those used by the standard C-language
routine sprintf(). gprintf() accepts only a single variable to be formatted.
Gnuplot also provides an sprintf("format",x1,x2,...) routine if you prefer.
For a list of gnuplot's format options, see `format specifiers`.
?commands set format specifiers
?set format specifiers
?format specifiers
?format_specifiers
The acceptable formats (if not in time/date mode) are:
Format Explanation
%f floating point notation
%e or %E exponential notation; an "e" or "E" before the power
%g or %G the shorter of %e (or %E) and %f
%h or %H like %g with "x10^{%S}" or "*10^{%S}" instead of "e%S"
%x or %X hex
%o or %O octal
%t mantissa to base 10
%l mantissa to base of current logscale
%s mantissa to base of current logscale; scientific power
%T power to base 10
%L power to base of current logscale
%S scientific power
%c character replacement for scientific power
%b mantissa of ISO/IEC 80000 notation (ki, Mi, Gi, Ti, Pi, Ei, Zi, Yi)
%B prefix of ISO/IEC 80000 notation (ki, Mi, Gi, Ti, Pi, Ei, Zi, Yi)
%P multiple of pi
A 'scientific' power is one such that the exponent is a multiple of three.
Character replacement of scientific powers (`"%c"`) has been implemented
for powers in the range -18 to +18. For numbers outside of this range the
format reverts to exponential.
Other acceptable modifiers (which come after the "%" but before the format
specifier) are "-", which left-justifies the number; "+", which forces all
numbers to be explicitly signed; " " (a space), which makes positive numbers
have a space in front of them where negative numbers have "-";
"#", which places a decimal point after
floats that have only zeroes following the decimal point; a positive integer,
which defines the field width; "0" (the digit, not the letter) immediately
preceding the field width, which indicates that leading zeroes are to be used
instead of leading blanks; and a decimal point followed by a non-negative
integer, which defines the precision (the minimum number of digits of an
integer, or the number of digits following the decimal point of a float).
Some systems may not support all of these modifiers but may also support
others; in case of doubt, check the appropriate documentation and
then experiment.
Examples:
set format y "%t"; set ytics (5,10) # "5.0" and "1.0"
set format y "%s"; set ytics (500,1000) # "500" and "1.0"
set format y "%+-12.3f"; set ytics(12345) # "+12345.000 "
set format y "%.2t*10^%+03T"; set ytic(12345)# "1.23*10^+04"
set format y "%s*10^{%S}"; set ytic(12345) # "12.345*10^{3}"
set format y "%s %cg"; set ytic(12345) # "12.345 kg"
set format y "%.0P pi"; set ytic(6.283185) # "2 pi"
set format y "%.0f%%"; set ytic(50) # "50%"
set log y 2; set format y '%l'; set ytics (1,2,3)
#displays "1.0", "1.0" and "1.5" (since 3 is 1.5 * 2^1)
There are some problem cases that arise when numbers like 9.999 are printed
with a format that requires both rounding and a power.
If the data type for the axis is time/date, the format string must contain
valid codes for the 'strftime' function (outside of `gnuplot`, type "man
strftime"). See `set timefmt` for a list of the allowed input format codes.
?commands set format date_specifiers
?commands set format time_specifiers
?set format date_specifiers
?set format time_specifiers
?set date_specifiers
?set time_specifiers
?date_specifiers
?time_specifiers
In time/date mode, the acceptable formats are:
Format Explanation
%a abbreviated name of day of the week
%A full name of day of the week
%b or %h abbreviated name of the month
%B full name of the month
%d day of the month, 01--31
%D shorthand for "%m/%d/%y" (only output)
%F shorthand for "%Y-%m-%d" (only output)
%k hour, 0--23 (one or two digits)
%H hour, 00--23 (always two digits)
%l hour, 1--12 (one or two digits)
%I hour, 01--12 (always two digits)
%j day of the year, 001--366
%m month, 01--12
%M minute, 00--60
%p "am" or "pm"
%r shorthand for "%I:%M:%S %p" (only output)
%R shorthand for "%H:%M" (only output)
%s number of seconds since the start of year 1970
%S second, integer 00--60 on output, (double) on input
%T shorthand for "%H:%M:%S" (only output)
%U week of the year (week starts on Sunday)
%w day of the week, 0--6 (Sunday = 0)
%W week of the year (week starts on Monday)
%y year, 0-68 for 2000-2068, 69-99 for 1969-1999
%Y year, 4-digit
Numerical formats may be preceded by a "0" ("zero") to pad the field with
leading zeroes, and preceded by a positive digit to define the minimum field
width. The %S, and %t formats also accept a precision specifier so that
fractional hours/minutes/seconds can be written.
Format Explanation
%tH +/- hours relative to time=0 (does not wrap at 24)
%tM +/- minutes relative to time=0
%tS +/- seconds associated with previous tH or tM field
?commands set format date_specifiers examples
?commands set format time_specifiers examples
?set format date_specifiers examples
?set format time_specifiers examples
?set date_specifiers examples
?set time_specifiers examples
?date_specifiers examples
?time_specifiers examples
Examples of date format:
Suppose the x value in seconds corresponds a time slightly before midnight
on 25 Dec 1976. The text printed for a tic label at this position would be
set format x # defaults to "12/25/76 \n 23:11"
set format x "%A, %d %b %Y" # "Saturday, 25 Dec 1976"
set format x "%r %D" # "11:11:11 pm 12/25/76"
Examples of time format:
The date format specifiers encode a time in seconds as a clock time on a
particular day. So hours run only from 0-23, minutes from 0-59, and negative
values correspond to dates prior to the epoch (1-Jan-1970). In order to report
a time value in seconds as some number of hours/minutes/seconds relative to a
time 0, use time formats %tH %tM %tS. To report a value of -3672.50 seconds
set format x # default date format "12/31/69 \n 22:58"
set format x "%tH:%tM:%tS" # "-01:01:12"
set format x "%.2tH hours" # "-1.02 hours"
set format x "%tM:%.2tS" # "-61:12.50"
?set function style
This form of the command is deprecated. Please see `set style function`.
?commands show functions
?show functions
The `show functions` command lists all user-defined functions and their
definitions.
Syntax:
show functions
For information about the definition and usage of functions in `gnuplot`,
please see `expressions`.
See also
splines as user defined functions (spline.dem)
and
use of functions and complex variables for airfoils (airfoil.dem).
?commands set grid
?commands unset grid
?commands show grid
?set grid
?unset grid
?show grid
?grid
?nogrid
The `set grid` command allows grid lines to be drawn on the plot.
Syntax:
set grid {{no}{m}xtics} {{no}{m}ytics} {{no}{m}ztics}
{{no}{m}x2tics} {{no}{m}y2tics} {{no}{m}rtics}
{{no}{m}cbtics}
{polar {<angle>}}
{layerdefault | front | back}
{<line-properties-major> {, <line-properties-minor>}}
unset grid
show grid
The grid can be enabled and disabled for the major and/or minor tic
marks on any axis, and the linetype and linewidth can be specified
for major and minor grid lines, also via a predefined linestyle, as
far as the active terminal driver supports this (see `set style line`).
A polar grid can be drawn for 2D plots. This is the default action of
`set grid` if the program is already in polar mode, but can be enabled
explicitly by `set grid polar <angle> rtics` whether or not the program is in
polar mode. Circles are drawn to intersect major and/or minor tics along the
r axis, and radial lines are drawn with a spacing of <angle>. Tic marks
around the perimeter are controlled by `set ttics`, but these do not produce
radial grid lines.
The pertinent tics must be enabled before `set grid` can draw them; `gnuplot`
will quietly ignore instructions to draw grid lines at non-existent tics, but
they will appear if the tics are subsequently enabled.
If no linetype is specified for the minor gridlines, the same linetype as the
major gridlines is used. The default polar angle is 30 degrees.
If `front` is given, the grid is drawn on top of the graphed data. If
`back` is given, the grid is drawn underneath the graphed data. Using
`front` will prevent the grid from being obscured by dense data. The
default setup, `layerdefault`, is equivalent to `back` for 2D plots.
In 3D plots the default is to split up the grid and the graph box into
two layers: one behind, the other in front of the plotted data and
functions. Since `hidden3d` mode does its own sorting, it ignores
all grid drawing order options and passes the grid lines through the
hidden line removal machinery instead. These options actually affect
not only the grid, but also the lines output by `set border` and the
various ticmarks (see `set xtics`).
Z grid lines are drawn on the bottom of the plot. This looks better if a
partial box is drawn around the plot---see `set border`.
?commands set hidden3d
?commands unset hidden3d
?commands show hidden3d
?set hidden3d
?unset hidden3d
?show hidden3d
?hidden3d
?nohidden3d
The `set hidden3d` command enables hidden line removal for surface plotting
(see `splot`). Some optional features of the underlying algorithm can also
be controlled using this command.
Syntax:
set hidden3d {defaults} |
{ {front|back}
{{offset <offset>} | {nooffset}}
{trianglepattern <bitpattern>}
{{undefined <level>} | {noundefined}}
{{no}altdiagonal}
{{no}bentover} }
unset hidden3d
show hidden3d
In contrast to the usual display in gnuplot, hidden line removal actually
treats the given function or data grids as real surfaces that can't be seen
through, so plot elements behind the surface will be hidden by it. For this
to work, the surface needs to have 'grid structure' (see `splot datafile`
about this), and it has to be drawn `with lines` or `with linespoints`.
When `hidden3d` is set, both the hidden portion of the surface and possibly
its contours drawn on the base (see `set contour`) as well as the grid will
be hidden. Each surface has its hidden parts removed with respect to itself
and to other surfaces, if more than one surface is plotted. Contours drawn
on the surface (`set contour surface`) don't work.
As of gnuplot version 4.6, hidden3d also affects 3D plotting styles `points`,
`labels`, `vectors`, and `impulses` even if no surface is present in the graph.
Unobscured portions of each vector are drawn as line segments (no arrowheads).
Individual plots within the graph may be explicitly excluded from this
processing by appending the extra option `nohidden3d` to the `with` specifier.
Hidden3d does not affect solid surfaces drawn using the pm3d mode. To achieve
a similar effect purely for pm3d surfaces, use instead `set pm3d depthorder`.
To mix pm3d surfaces with normal `hidden3d` processing, use the option
`set hidden3d front` to force all elements included in hidden3d processing to
be drawn after any remaining plot elements, including the pm3d surface.
Functions are evaluated at isoline intersections. The algorithm interpolates
linearly between function points or data points when determining the visible
line segments. This means that the appearance of a function may be different
when plotted with `hidden3d` than when plotted with `nohidden3d` because in
the latter case functions are evaluated at each sample. Please see
`set samples` and `set isosamples` for discussion of the difference.
The algorithm used to remove the hidden parts of the surfaces has some
additional features controllable by this command. Specifying `defaults` will
set them all to their default settings, as detailed below. If `defaults` is
not given, only explicitly specified options will be influenced: all others
will keep their previous values, so you can turn on/off hidden line removal
via `set {no}hidden3d`, without modifying the set of options you chose.
The first option, `offset`, influences the linetype used for lines on the
'back' side. Normally, they are drawn in a linetype one index number higher
than the one used for the front, to make the two sides of the surface
distinguishable. You can specify a different linetype offset to add
instead of the default 1, by `offset <offset>`. Option `nooffset` stands for
`offset 0`, making the two sides of the surface use the same linetype.
Next comes the option `trianglepattern <bitpattern>`. <bitpattern> must be
a number between 0 and 7, interpreted as a bit pattern. Each bit determines
the visibility of one edge of the triangles each surface is split up into.
Bit 0 is for the 'horizontal' edges of the grid, Bit 1 for the 'vertical'
ones, and Bit 2 for the diagonals that split each cell of the original grid
into two triangles. The default pattern is 3, making all horizontal and
vertical lines visible, but not the diagonals. You may want to choose 7 to
see those diagonals as well.
The `undefined <level>` option lets you decide what the algorithm is to do
with data points that are undefined (missing data, or undefined function
values), or exceed the given x-, y- or z-ranges. Such points can either be
plotted nevertheless, or taken out of the input data set. All surface
elements touching a point that is taken out will be taken out as well, thus
creating a hole in the surface. If <level> = 3, equivalent to option
`noundefined`, no points will be thrown away at all. This may produce all
kinds of problems elsewhere, so you should avoid this. <level> = 2 will
throw away undefined points, but keep the out-of-range ones. <level> = 1,
the default, will get rid of out-of-range points as well.
By specifying `noaltdiagonal`, you can override the default handling of a
special case can occur if `undefined` is active (i.e. <level> is not 3).
Each cell of the grid-structured input surface will be divided in two
triangles along one of its diagonals. Normally, all these diagonals have
the same orientation relative to the grid. If exactly one of the four cell
corners is excluded by the `undefined` handler, and this is on the usual
diagonal, both triangles will be excluded. However if the default setting
of `altdiagonal` is active, the other diagonal will be chosen for this cell
instead, minimizing the size of the hole in the surface.
The `bentover` option controls what happens to another special case, this
time in conjunction with the `trianglepattern`. For rather crumply surfaces,
it can happen that the two triangles a surface cell is divided into are seen
from opposite sides (i.e. the original quadrangle is 'bent over'), as
illustrated in the following ASCII art:
C----B
original quadrangle: A--B displayed quadrangle: |\ |
("set view 0,0") | /| ("set view 75,75" perhaps) | \ |
|/ | | \ |
C--D | \|
A D
If the diagonal edges of the surface cells aren't generally made visible by
bit 2 of the <bitpattern> there, the edge CB above wouldn't be drawn at all,
normally, making the resulting display hard to understand. Therefore, the
default option of `bentover` will turn it visible in this case. If you don't
want that, you may choose `nobentover` instead.
See also
hidden line removal demo (hidden.dem)
and
complex hidden line demo (singulr.dem).
?commands set historysize
?set historysize
?unset historysize
?historysize
(Deprecated).
`set historysize N` is equivalent to `set history size N`.
`unset historysize` is equivalent to `set history size -1`.
?commands set history
?set history
Syntax:
set history {size <N>} {quiet|numbers} {full|trim} {default}
When leaving gnuplot the value of history size limits the number of lines
saved to the history file. `set history size -1` allows an unlimited number
of lines to be written to the history file.
By default the `history` command prints a line number in front of each command.
`history quiet` suppresses the number for this command only.
`set history quiet` suppresses numbers for all future `history` commands.
The `trim` option reduces the number of duplicate lines in the history list
by removing earlier instances of the current command. This was the default
behavior prior to gnuplot version 5.
Default settings: `set history size 500 numbers trim`.
?commands set isosamples
?commands show isosamples
?set isosamples
?show isosamples
?isosamples
The isoline density (grid) for plotting functions as surfaces may be changed
by the `set isosamples` command.
Syntax:
set isosamples <iso_1> {,<iso_2>}
show isosamples
Each function surface plot will have <iso_1> iso-u lines and <iso_2> iso-v
lines. If you only specify <iso_1>, <iso_2> will be set to the same value
as <iso_1>. By default, sampling is set to 10 isolines per u or v axis.
A higher sampling rate will produce more accurate plots, but will take longer.
These parameters have no effect on data file plotting.
An isoline is a curve parameterized by one of the surface parameters while
the other surface parameter is fixed. Isolines provide a simple means to
display a surface. By fixing the u parameter of surface s(u,v), the iso-u
lines of the form c(v) = s(u0,v) are produced, and by fixing the v parameter,
the iso-v lines of the form c(u) = s(u,v0) are produced.
When a function surface plot is being done without the removal of hidden
lines, `set samples` controls the number of points sampled along each
isoline; see `set samples` and `set hidden3d`. The contour algorithm
assumes that a function sample occurs at each isoline intersection, so
change in `samples` as well as `isosamples` may be desired when changing
the resolution of a function surface/contour.
?commands set jitter
?set jitter
?jitter
Syntax:
set jitter {overlap <yposition>} {spread <factor>} {wrap <limit>}
{swarm|square}
Examples:
set jitter # jitter points within 1 character width
set jitter overlap 1.5 # jitter points within 1.5 character width
set jitter over 1.5 spread 0.5 # same but half the displacement on x
When one or both coordinates of a data set are restricted to discrete values
then many points may lie exactly on top of each other. Jittering introduces an
offset to the coordinates of these superimposed points that spreads them into a
cluster. The threshold value for treating the points as being overlapped may
be specified in character widths or any of the usual coordinate options.
See `coordinates`. Jitter affects only 2D plot styles `with points` and
`with impulses`.
The default jittering operation displaces points only along x.
This produces a distinctive pattern sometimes called a "bee swarm plot".
The optional keyword `square` adjusts the y coordinate of displaced points
in addition to their x coordinate so that the points lie in distinct layers
separated by at least the `overlap` distance.
The maximum displacement (in character units) can be limited using the `wrap`
keyword.
Note that both the overlap criterion and the magnitude of jitter default to
one character unit. Thus the plot appearance will change with the terminal
font size, canvas size, or zoom factor. To avoid this you can specify the
overlap criterion in the y axis coordinate system (the `first` keyword) and
adjust the point size and spread multiplier as appropriate.
See `coordinates`, `pointsize`, `jitter`.
?commands set key
?commands unset key
?commands show key
?set key
?unset key
?show key
?key
?nokey
?legend
The `set key` command enables a key (or legend) containing a title and a
sample (line, point, box) for each plot in the graph. The key may be turned off
by requesting `set key off` or `unset key`. Individual key entries may be
turned off by using the `notitle` keyword in the corresponding plot command.
The text of the titles is controlled by the `set key autotitle` option or by
the `title` keyword of individual `plot` and `splot` commands.
See `plot title` for more information.
Syntax:
set key {on|off} {default}
{{inside | outside | fixed} | {lmargin | rmargin | tmargin | bmargin}
| {at <position>}}
{left | right | center} {top | bottom | center}
{vertical | horizontal} {Left | Right}
{{no}enhanced}
{{no}opaque}
{{no}reverse} {{no}invert}
{samplen <sample_length>} {spacing <line_spacing>}
{width <width_increment>} {height <height_increment>}
{{no}autotitle {columnheader}}
{title {"<text>"} {{no}enhanced} {center | left | right}}
{font "<face>,<size>"} {textcolor <colorspec>}
{{no}box {linestyle <style> | linetype <type> | linewidth <width>}}
{maxcols {<max no. of columns> | auto}}
{maxrows {<max no. of rows> | auto}}
unset key
show key
Elements within the key are stacked according to `vertical` or `horizontal`.
In the case of `vertical`, the key occupies as few columns as possible. That
is, elements are aligned in a column until running out of vertical space at
which point a new column is started. The vertical space may be limited using
'maxrows'. In the case of `horizontal`, the key occupies as few rows as
possible. The horizontal space may be limited using 'maxcols'.
By default the key is placed in the upper right inside corner of the graph.
The keywords `left`, `right`, `top`, `bottom`, `center`, `inside`, `outside`,
`lmargin`, `rmargin`, `tmargin`, `bmargin` (, `above`, `over`, `below` and
`under`) may be used to automatically place the key in other positions of the
graph. Also an `at <position>` may be given to indicate precisely where the
plot should be placed. In this case, the keywords `left`, `right`, `top`,
`bottom` and `center` serve an analogous purpose for alignment.
For more information, see `key placement`.
Justification of the plot titles within the key is controlled by `Left` or
`Right` (default). The text and sample can be reversed (`reverse`) and a
box can be drawn around the key (`box {...}`) in a specified `linetype`
and `linewidth`, or a user-defined `linestyle`.
The text in the key is set in `enhanced` mode by default, this can be changed
with the `{no}enhanced` option, also independently for the key title only and
for each individual plot.
By default the key is built up one plot at a time. That is, the key symbol and
title are drawn at the same time as the corresponding plot. That means newer
plots may sometimes place elements on top of the key. `set key opaque` causes
the key to be generated after all the plots. In this case the key area is
filled with background color and then the key symbols and titles are written.
Therefore the key itself may obscure portions of some plot elements.
The default can be restored by `set key noopaque`.
By default the first plot label is at the top of the key and successive labels
are entered below it. The `invert` option causes the first label to be placed
at the bottom of the key, with successive labels entered above it. This option
is useful to force the vertical ordering of labels in the key to match the
order of box types in a stacked histogram.
The <height_increment> is a number of character heights to be added to or
subtracted from the height of the key box. This is useful mainly when you are
putting a box around the key and want larger borders around the key entries.
An overall title can be put on the key (`title "<text>"`)---see also `syntax`
for the distinction between text in single- or double-quotes. The justification
of the title defaults to center and can be changed by the keywords `right` or
`left`
The defaults for `set key` are `on`, `right`, `top`, `vertical`, `Right`,
`noreverse`, `noinvert`, `samplen 4`, `spacing 1`, `notitle`, and
`nobox`. The default <linetype> is the same as that used for the plot
borders. Entering `set key default` returns the key to its default
configuration.
The key is drawn as a sequence of lines, with one plot described on each
line. On the right-hand side (or the left-hand side, if `reverse` is
selected) of each line is a representation that attempts to mimic the way the
curve is plotted. On the other side of each line is the text description
(the line title), obtained from the `plot` command. The lines are vertically
arranged so that an imaginary straight line divides the left- and right-hand
sides of the key. It is the coordinates of the top of this line that are
specified with the `set key` command. In a `plot`, only the x and y
coordinates are used to specify the line position.
When using the TeX/LaTeX group of terminals or terminals in which formatting
information is embedded in the string, `gnuplot` can only estimate the width
of the string for key positioning. If the key is to be positioned at the
left, it may be convenient to use the combination `set key left Left reverse`.
?set key 3D
?set key splot
?key 3D
?key splot
?set key fixed
?key fixed
Placement of the key for 3D plots (`splot`) by default uses the `fixed` option.
Note that this is a change from earlier gnuplot versions. `fixed` placement is
very similar to `inside` placement with one important difference. The plot
boundaries of a 3D plot change as the view point is rotated or scaled. If the
key is positioned `inside` these boundaries then the key also moves when the
view is changed. `fixed` positioning ignores changes to the view angles or
scaling; i.e. the key remains fixed in one location on the canvas as the plot
is rotated.
For 2D plots the `fixed` option is exactly equivalent to `inside`.
If `splot` is being used to draw contours, by default a separate key entry is
generated for each contour level with a distinct line type.
To modify this see `set cntrlabel`.
?set key examples
?key examples
This places the key at the default location:
set key default
This disables the key:
unset key
This places a key at coordinates 2,3.5,2 in the default (first) coordinate
system:
set key at 2,3.5,2
This places the key below the graph:
set key below
This places the key in the bottom left corner, left-justifies the text,
gives it a title, and draws a box around it in linetype 3:
set key left bottom Left title 'Legend' box 3
?commands set key autotitle
?set key autotitle
?key autotitle
?autotitle
`set key autotitle` causes each plot to be identified in the key by the name
of the data file or function used in the plot command. This is the default.
`set key noautotitle` disables the automatic generation of plot titles.
The command `set key autotitle columnheader` causes the first entry in each
column of input data to be interpreted as a text string and used as a title for
the corresponding plot. If the quantity being plotted is a function of data
from several columns, gnuplot may be confused as to which column to draw the
title from. In this case it is necessary to specify the column explicitly in
the plot command, e.g.
plot "datafile" using (($2+$3)/$4) title columnhead(3) with lines
Note: The effect of `set key autotitle columnheader`, treatment of the first
line in a data file as column headers rather than data applies even if the
key is disabled by `unset key`. It also applies to `stats` and `fit` commands
even though they generate no key.
In all cases an explicit `title` or `notitle` keyword in the plot command
itself will override the default from `set key autotitle`.
?commands set key placement
?set key placement
?key placement
This section describes placement of the primary, auto-generated key.
To construct a secondary key or place plot titles elsewhere, see
`multiple keys`.
To understand positioning, the best concept is to think of a region, i.e.,
inside/outside, or one of the margins. Along with the region, keywords
`left/center/right` (l/c/r) and `top/center/bottom` (t/c/b) control where
within the particular region the key should be placed.
When in `inside` mode, the keywords `left` (l), `right` (r), `top` (t),
`bottom` (b), and `center` (c) push the key out toward the plot boundary as
illustrated:
t/l t/c t/r
c/l c c/r
b/l b/c b/r
When in `outside` mode, automatic placement is similar to the above
illustration, but with respect to the view, rather than the graph boundary.
That is, a border is moved inward to make room for the key outside of
the plotting area, although this may interfere with other labels and may
cause an error on some devices. The particular plot border that is moved
depends upon the position described above and the stacking direction. For
options centered in one of the dimensions, there is no ambiguity about which
border to move. For the corners, when the stack direction is `vertical`, the
left or right border is moved inward appropriately. When the stack direction
is `horizontal`, the top or bottom border is moved inward appropriately.
The margin syntax allows automatic placement of key regardless of stack
direction. When one of the margins `lmargin` (lm), `rmargin` (rm),
`tmargin` (tm), and `bmargin` (bm) is combined with a single, non-conflicting
direction keyword, the following illustrated positions may contain the key:
l/tm c/tm r/tm
t/lm t/rm
c/lm c/rm
b/lm b/rm
l/bm c/bm r/bm
Keywords `above` and `over` are synonymous with `tmargin`. For version
compatibility, `above` or `over` without an additional l/c/r or stack direction
keyword uses `center` and `horizontal`. Keywords `below` and `under` are
synonymous with `bmargin`. For compatibility, `below` or `under` without an
additional l/c/r or stack direction keyword uses `center` and `horizontal`. A
further compatibility issue is that `outside` appearing without an additional
t/b/c or stack direction keyword uses `top`, `right` and `vertical` (i.e., the
same as t/rm above).
The <position> can be a simple x,y,z as in previous versions, but these can
be preceded by one of five keywords (`first`, `second`, `graph`, `screen`,
`character`) which selects the coordinate system in which the position of
the first sample line is specified. See `coordinates` for more details.
The effect of `left`, `right`, `top`, `bottom`, and `center` when <position>
is given is to align the key as though it were text positioned using the
label command, i.e., `left` means left align with key to the right of
<position>, etc.
?commands set key samples
?set key samples
?key samples
By default, each plot on the graph generates a corresponding entry in the key.
This entry contains a plot title and a sample line/point/box of the same color
and fill properties as used in the plot itself. The font and textcolor
properties control the appearance of the individual plot titles that appear in
the key. Setting the textcolor to "variable" causes the text for each key
entry to be the same color as the line or fill color for that plot.
This was the default in some earlier versions of gnuplot.
The length of the sample line can be controlled by `samplen`. The sample
length is computed as the sum of the tic length and <sample_length> times the
character width. `samplen` also affects the positions of point samples in
the key since these are drawn at the midpoint of the sample line, even if
the sample line itself is not drawn.
Key entry lines are single-spaced based on the current font size.
This can be adjusted by `set key spacing <line-spacing>`.
The <width_increment> is a number of character widths to be added to or
subtracted from the length of the string. This is useful only when you are
putting a box around the key and you are using control characters in the text.
`gnuplot` simply counts the number of characters in the string when computing
the box width; this allows you to correct it.
?multiple keys
?set key multiple keys
?key multiple keys
It is possible to construct a legend/key manually rather than having the plot
titles all appear in the auto-generated key. This allows, for example, creating
a single legend for the component panels in a multiplot.
Here is an example:
set multiplot layout 3,2 columnsfirst
set style data boxes
plot $D using 0:6 lt 1 title at 0.75, 0.20
plot $D using 0:12 lt 2 title at 0.75, 0.17
plot $D using 0:13 lt 3 title at 0.75, 0.14
plot $D using 0:14 lt 4 title at 0.75, 0.11
set label 1 at screen 0.75, screen 0.22 "Custom combined key area"
plot $D using 0:($6+$12+$13+$14) with linespoints title "total"
unset multiplot
?commands set label
?commands unset label
?commands show label
?set label
?unset label
?show label
?label
?nolabel
Arbitrary labels can be placed on the plot using the `set label` command.
Syntax:
set label {<tag>} {"<label text>"} {at <position>}
{left | center | right}
{norotate | rotate {by <degrees>}}
{font "<name>{,<size>}"}
{noenhanced}
{front | back}
{textcolor <colorspec>}
{point <pointstyle> | nopoint}
{offset <offset>}
{boxed}
{hypertext}
unset label {<tag>}
show label
The <position> is specified by either x,y or x,y,z, and may be preceded by
`first`, `second`, `polar`, `graph`, `screen`, or `character` to indicate the
coordinate system. See `coordinates` for details.
The tag is an integer that is used to identify the label. If no <tag>
is given, the lowest unused tag value is assigned automatically. The
tag can be used to delete or modify a specific label. To change any
attribute of an existing label, use the `set label` command with the
appropriate tag, and specify the parts of the label to be changed.
The <label text> can be a string constant, a string variable, or a string-
valued expression. See `strings`, `sprintf`, and `gprintf`.
By default, the text is placed flush left against the point x,y,z. To adjust
the way the label is positioned with respect to the point x,y,z, add the
justification parameter, which may be `left`, `right` or `center`,
indicating that the point is to be at the left, right or center of the text.
Labels outside the plotted boundaries are permitted but may interfere with
axis labels or other text.
Some terminals support enclosing the label in a box. See `set style textbox`.
Not all terminals can handle boxes for rotated text.
If `rotate` is given, the label is written vertically. If `rotate by <degrees>`
is given, the baseline of the text will be set to the specified angle.
Some terminals do not support text rotation.
Font and its size can be chosen explicitly by `font "<name>{,<size>}"` if the
terminal supports font settings. Otherwise the default font of the terminal
will be used.
Normally the enhanced text mode string interpretation, if enabled for the
current terminal, is applied to all text strings including label text.
The `noenhanced` property can be used to exempt a specific label from the
enhanced text mode processing. The can be useful if the label contains
underscores, for example. See `enhanced text`.
If `front` is given, the label is written on top of the graphed data. If
`back` is given (the default), the label is written underneath the graphed
data. Using `front` will prevent a label from being obscured by dense data.
`textcolor <colorspec>` changes the color of the label text. <colorspec> can be
a linetype, an rgb color, or a palette mapping. See help for `colorspec` and
`palette`. `textcolor` may be abbreviated `tc`.
`tc default` resets the text color to its default state.
`tc lt <n>` sets the text color to that of line type <n>.
`tc ls <n>` sets the text color to that of line style <n>.
`tc palette z` selects a palette color corresponding to the label z position.
`tc palette cb <val>` selects a color corresponding to <val> on the colorbar.
`tc palette fraction <val>`, with 0<=val<=1, selects a color corresponding to
the mapping [0:1] to grays/colors of the `palette`.
`tc rgb "#RRGGBB"` or `tc rgb "0xRRGGBB"` sets an arbitrary 24-bit RGB color.
`tc rgb 0xRRGGBB` As above; a hexadecimal constant does not require quotes.
If a <pointstyle> is given, using keywords `lt`, `pt` and `ps`, see `style`,
a point with the given style and color of the given line type is plotted at
the label position and the text of the label is displaced slightly.
This option is used by default for placing labels in `mouse` enhanced
terminals. Use `nopoint` to turn off the drawing of a point near
the label (this is the default).
The displacement defaults to 1,1 in `pointsize` units if a <pointstyle> is
given, 0,0 if no <pointstyle> is given. The displacement can be controlled
by the optional `offset <offset>` where <offset> is specified by either x,y
or x,y,z, and may be preceded by `first`, `second`, `graph`, `screen`, or
`character` to select the coordinate system. See `coordinates` for details.
If one (or more) axis is timeseries, the appropriate coordinate should be
given as a quoted time string according to the `timefmt` format string.
See `set xdata` and `set timefmt`.
The options available for `set label` are also available for the `labels` plot
style. See `labels`. In this case the properties `textcolor`, `rotate`, and
`pointsize` may be followed by keyword `variable` rather than by a fixed value.
In this case the corresponding property of individual labels is determined by
additional columns in the `using` specifier.
?label examples
?set label examples
Examples:
To set a label at (1,2) to "y=x", use:
set label "y=x" at 1,2
To set a Sigma of size 24, from the Symbol font set, at the center of
the graph, use:
set label "S" at graph 0.5,0.5 center font "Symbol,24"
To set a label "y=x^2" with the right of the text at (2,3,4), and tag the
label as number 3, use:
set label 3 "y=x^2" at 2,3,4 right
To change the preceding label to center justification, use:
set label 3 center
To delete label number 2, use:
unset label 2
To delete all labels, use:
unset label
To show all labels (in tag order), use:
show label
To set a label on a graph with a timeseries on the x axis, use, for example:
set timefmt "%d/%m/%y,%H:%M"
set label "Harvest" at "25/8/93",1
To display a freshly fitted parameter on the plot with the data and the
fitted function, do this after the `fit`, but before the `plot`:
set label sprintf("a = %3.5g",par_a) at 30,15
bfit = gprintf("b = %s*10^%S",par_b)
set label bfit at 30,20
To display a function definition along with its fitted parameters, use:
f(x)=a+b*x
fit f(x) 'datafile' via a,b
set label GPFUN_f at graph .05,.95
set label sprintf("a = %g", a) at graph .05,.90
set label sprintf("b = %g", b) at graph .05,.85
To set a label displaced a little bit from a small point:
set label 'origin' at 0,0 point lt 1 pt 2 ps 3 offset 1,-1
To set a label whose color matches the z value (in this case 5.5) of some
point on a 3D splot colored using pm3d:
set label 'text' at 0,0,5.5 tc palette z
?hypertext
?label hypertext
?set label hypertext
Some terminals (wxt, qt, svg, canvas, win) allow you to attach hypertext
to specific points on the graph or elsewhere on the canvas. When the mouse
hovers over the anchor point, a pop-up box containing the text is displayed.
Terminals that do not support hypertext will display nothing. You must enable
the `point` attribute of the label in order for the hypertext to be anchored.
Examples:
set label at 0,0 "Plot origin" hypertext point pt 1
plot 'data' using 1:2:0 with labels hypertext point pt 7 \
title 'mouse over point to see its order in data set'
EXPERIMENTAL (implementation details may change):
Text of the form "image{<xsize>,<ysize>}:<filename>{\n<caption text>}" will
trigger display of the image file in a pop-up box. The optional size overrides
a default box size 300x200. The types of image file recognized may vary by
terminal type, but *.png should always work. Any additional text lines
following the image filename are displayed as usual for hypertext.
Example:
set label 7 "image:../figures/Fig7_inset.png\nFigure 7 caption..."
set label 7 at 10,100 hypertext point pt 7
?commands set linetype
?commands show linetype
?set linetype
?show linetype
?linetype
The `set linetype` command allows you to redefine the basic linetypes used
for plots. The command options are identical to those for "set style line".
Unlike line styles, redefinitions by `set linetype` are persistent; they
are not affected by `reset`.
For example, whatever linetypes one and two look like to begin with, if you
redefine them like this:
set linetype 1 lw 2 lc rgb "blue" pointtype 6
set linetype 2 lw 2 lc rgb "forest-green" pointtype 8
everywhere that uses lt 1 will now get a thick blue line. This includes
uses such as the definition of a temporary linestyle derived from the base
linetype 1. Similary lt 2 will now produce a think green line.
This mechanism can be used to define a set of personal preferences for the
sequence of lines used in gnuplot. The recommended way to do this is to add
to the run-time initialization file ~/.gnuplot a sequence of commands like
set linetype 1 lc rgb "dark-violet" lw 2 pt 1
set linetype 2 lc rgb "sea-green" lw 2 pt 7
set linetype 3 lc rgb "cyan" lw 2 pt 6 pi -1
set linetype 4 lc rgb "dark-red" lw 2 pt 5 pi -1
set linetype 5 lc rgb "blue" lw 2 pt 8
set linetype 6 lc rgb "dark-orange" lw 2 pt 3
set linetype 7 lc rgb "black" lw 2 pt 11
set linetype 8 lc rgb "goldenrod" lw 2
set linetype cycle 8
Every time you run gnuplot the line types will be initialized to these values.
You may initialize as many linetypes as you like. If you do not redefine, say,
linetype 3 then it will continue to have the default properties (in this case
blue, pt 3, lw 1, etc). The first few lines of the example script insure that
the commands will be skipped by older versions of gnuplot.
Similar script files can be used to define theme-based color choices, or sets
of colors optimized for a particular plot type or output device.
The command `set linetype cycle 8` tells gnuplot to re-use these definitions
for the color and linewidth of higher-numbered linetypes. That is, linetypes
9-16, 17-24, and so on will use this same sequence of colors and widths.
The point properties (pointtype, pointsize, pointinterval) are not affected by
this command. `unset linetype cycle` disables this feature. If the line
properties of a higher numbered linetype are explicitly defined, this takes
precedence over the recycled low-number linetype properties.
?commands set link
?set link
?link
Syntax:
set link {x2 | y2} {via <expression1> inverse <expression2>}
unset link
The `set link` command establishes a mapping between the x and x2 axes, or the
y and y2 axes. <expression1> maps primary axis coordinates onto the secondary
axis. <expression2> maps secondary axis coordinates onto the primary axis.
Examples:
set link x2
This is the simplest form of the command. It forces the x2 axis to have
identically the same range, scale, and direction as the x axis.
Commands `set xrange`, `set x2range`, `set auto x`, etc will affect both the
x and x2 axes.
set link x2 via x**2 inverse sqrt(x)
plot "sqrt_data" using 1:2 axes x2y1, "linear_data" using 1:2 axes x1y1
This command establishes forward and reverse mapping between the x and x2 axes.
The forward mapping is used to generate x2 tic labels and x2 mouse coordinate
The reverse mapping is used to plot coordinates given in the x2 coordinate
system. Note that the mapping as given is valid only for x non-negative. When
mapping to the y2 axis, both <expression1> and <expression2> must use y as
dummy variable.
?commands set lmargin
?set lmargin
?lmargin
The command `set lmargin` sets the size of the left margin.
Please see `set margin` for details.
?commands set loadpath
?commands show loadpath
?set loadpath
?show loadpath
?loadpath
The `loadpath` setting defines additional locations for data and command
files searched by the `call`, `load`, `plot` and `splot` commands. If a
file cannot be found in the current directory, the directories in
`loadpath` are tried.
Syntax:
set loadpath {"pathlist1" {"pathlist2"...}}
show loadpath
Path names may be entered as single directory names, or as a list of
path names separated by a platform-specific path separator, eg. colon
(':') on Unix, semicolon (';') on DOS/Windows/OS/2 platforms.
The `show loadpath`, `save` and `save set` commands replace the
platform-specific separator with a space character (' ').
If the environment variable GNUPLOT_LIB is set, its contents are appended to
`loadpath`. However, `show loadpath` prints the contents of `set loadpath`
and GNUPLOT_LIB separately. Also, the `save` and `save set` commands ignore
the contents of GNUPLOT_LIB.
?commands set locale
?set locale
?locale
The `locale` setting determines the language with which `{x,y,z}{d,m}tics`
will write the days and months.
Syntax:
set locale {"<locale>"}
<locale> may be any language designation acceptable to your installation.
See your system documentation for the available options. The command
`set locale ""` will try to determine the locale from the LC_TIME, LC_ALL,
or LANG environment variables.
To change the decimal point locale, see `set decimalsign`.
To change the character encoding to the current locale, see `set encoding`.
?commands set logscale
?commands unset logscale
?commands show logscale
?set logscale
?unset logscale
?show logscale
?set log
?logscale
?nologscale
Syntax:
set logscale <axes> {<base>}
unset logscale <axes>
show logscale
where <axes> may be any combinations of `x`, `x2`, `y`, `y2`, `z`, `cb`, and
`r` in any order. <base> is the base of the log scaling (default is base 10).
If no axes are specified, the command affects all axes except `r`.
The command `unset logscale` turns off log scaling for all axes.
Note that the ticmarks generated for logscaled axes are not uniformly spaced.
See `set xtics`.
Examples:
To enable log scaling in both x and z axes:
set logscale xz
To enable scaling log base 2 of the y axis:
set logscale y 2
To enable z and color log axes for a pm3d plot:
set logscale zcb
To disable z axis log scaling:
unset logscale z
?commands set macros
?set macros
In this version of gnuplot macro substitution is always enabled.
Tokens in the command line of the form @<stringvariablename> will be replaced
by the text string contained in <stringvariablename>. See `substitution`.
?commands set mapping
?commands show mapping
?set mapping
?show mapping
?mapping
If data are provided to `splot` in spherical or cylindrical coordinates,
the `set mapping` command should be used to instruct `gnuplot` how to
interpret them.
Syntax:
set mapping {cartesian | spherical | cylindrical}
A cartesian coordinate system is used by default.
For a spherical coordinate system, the data occupy two or three columns
(or `using` entries). The first two are interpreted as the azimuthal
and polar angles theta and phi (or "longitude" and "latitude"), in the
units specified by `set angles`. The radius r is taken from the third
column if there is one, or is set to unity if there is no third column.
The mapping is:
x = r * cos(theta) * cos(phi)
y = r * sin(theta) * cos(phi)
z = r * sin(phi)
Note that this is a "geographic" spherical system, rather than a "polar"
one (that is, phi is measured from the equator, rather than the pole).
For a cylindrical coordinate system, the data again occupy two or three
columns. The first two are interpreted as theta (in the units specified by
`set angles`) and z. The radius is either taken from the third column or set
to unity, as in the spherical case. The mapping is:
x = r * cos(theta)
y = r * sin(theta)
z = z
The effects of `mapping` can be duplicated with the `using` filter on the
`splot` command, but `mapping` may be more convenient if many data files are
to be processed. However even if `mapping` is used, `using` may still be
necessary if the data in the file are not in the required order.
`mapping` has no effect on `plot`.
world.dem: mapping demos.
?commands set margins
?commands show margins
?set margin
?set margins
?show margins
?margins
The `margin` is the distance between the plot border and the outer edge of the
canvas. The size of the margin is chosen automatically, but can be overridden
by the `set margin` commands. `show margin` shows the current settings.
To alter the distance between the inside of the plot border and the data in the
plot itself, see `set offsets`.
Syntax:
set lmargin {{at screen} <margin>}
set rmargin {{at screen} <margin>}
set tmargin {{at screen} <margin>}
set bmargin {{at screen} <margin>}
set margins <left>, <right>, <bottom>, <top>
show margin
The default units of <margin> are character heights or widths, as appropriate.
A positive value defines the absolute size of the margin. A negative value
(or none) causes `gnuplot` to revert to the computed value. For 3D plots,
only the left margin can be set using character units.
The keywords `at screen` indicates that the margin is specified as a fraction
of the full drawing area. This can be used to precisely line up the corners of
individual 2D and 3D graphs in a multiplot. This placement ignores the current
values of `set origin` and `set size`, and is intended as an alternative
method for positioning graphs within a multiplot.
Normally the margins of a plot are automatically calculated based on tics,
tic labels, axis labels, the plot title, the timestamp and the size of the
key if it is outside the borders. If, however, tics are attached to the
axes (`set xtics axis`, for example), neither the tics themselves nor their
labels will be included in either the margin calculation or the calculation
of the positions of other text to be written in the margin. This can lead
to tic labels overwriting other text if the axis is very close to the border.
?commands set micro
?commands show micro
?commands unset micro
?set micro
?show micro
?unset micro
?micro
By default the "%c" format specifier for scientific notation used to generate
axis tick labels uses a lower case u as a prefix to indicate "micro" (10^-6).
The `set micro` command tells gnuplot to use a different typographic
character (unicode U+00B5). The byte sequence used to represent this character
depends on the current encoding. See `format specifiers`, `encoding`.
This command is EXPERIMENTAL. It has known limitations and implementation
details may change.
?commands set minussign
?commands show minussign
?commands unset minussign
?set minussign
?show minussign
?unset minussign
?minussign
Gnuplot uses the C language library routine sprintf() for most formatted input.
However it also has its own formatting routine `gprintf()` that is used to
generate axis tic labels. The C library routine always use a hyphen character
(ascii \055) to indicate a negative number, as in -7. Many people prefer a
different typographic minus sign character (unicode U+2212) for this purpose,
as in −7. The command
set minussign
causes gprintf() to use this minus sign character rather than a hyphen in
numeric output. In a utf-8 locale this is the multibyte sequence corresponding
to unicode U+2212. In a Window codepage 1252 locale this is the 8-bit
character ALT+150 ("en dash"). The `set minussign` command will affect axis
tic labels and any labels that are created by explicitly invoking gprintf.
It has no effect on other strings that contain a hyphen. See `gprintf`.
Note that this command is ignored when you are using any of the LaTeX
terminals, as LaTeX has its own mechanism for handling minus signs.
It also is not necessary when using the postscript terminal because the
postscript prologue output by gnuplot remaps the ascii hyphen code \055 to a
different glyph named `minus`.
This command is EXPERIMENTAL. It has known limitations and implementation
details may change.
Example (assumes utf8 locale):
set minus
A = -5
print "A = ",A # printed string will contain a hyphen
print gprintf("A = %g",A) # printed string will contain character U+2212
set label "V = -5" # label will contain a hyphen
set label sprintf("V = %g",-5) # label will contain a hyphen
set label gprintf("V = %g",-5) # label will contain character U+2212
?commands set monochrome
?set monochrome
?monochrome
Syntax:
set monochrome {linetype N <linetype properties>}
The `set monochrome` command selects an alternative set of linetypes that
differ by dot/dash pattern or line width rather than by color. This command
replaces the monochrome option offered by certain terminal types in earlier
versions of gnuplot. For backward compatibility these terminal types now
implicitly invoke "set monochrome" if their own "mono" option is present.
For example,
set terminal pdf mono
is equivalent to
set terminal pdf
set mono
Selecting monochrome mode does not prevent you from explicitly drawing lines
using RGB or palette colors, but see also `set palette gray`.
Six monochrome linetypes are defined by default. You can change their
properties or add additional monochrome linetypes by using the full form of the
command. Changes made to the monochrome linetypes do not affect the color
linetypes and vice versa. To restore the usual set of color linetypes, use
either `unset monochrome` or `set color`.
?commands set mouse
?commands unset mouse
?set mouse
?unset mouse
?mousing
?mouse
?nomouse
The command `set mouse` enables mouse actions for the current interactive
terminal. It is usually enabled by default in interactive mode, but disabled
by default if commands are being read from a file.
There are two mouse modes. The 2D mode works for `plot` commands and for `splot`
maps (i.e. `set view` with z-rotation 0, 90, 180, 270 or 360 degrees, including
`set view map`). In this mode the mouse position is tracked and you can pan or
zoom using the mouse buttons or arrow keys. Some terminals support toggling
individual plots on/off by clicking on the corresponding key title or on a
separate widget.
For 3D graphs `splot`, the view and scaling of the graph can be changed with
mouse buttons 1 and 2, respectively. A vertical motion of Button 2 with the
shift key held down changes the `xyplane`. If additionally to these
buttons the modifier <ctrl> is held down, the coordinate axes are displayed
but the data are suppressed. This is useful for large data sets.
Mouse button 3 controls the azimuth of the z axis (see `set view azimuth`).
Mousing is not available inside multiplot mode. When multiplot is completed
using `unset multiplot`, then the mouse will be turned on again but acts only
on the most recent plot within the multiplot (like replot does).
Syntax:
set mouse {doubleclick <ms>} {nodoubleclick}
{{no}zoomcoordinates}
{zoomfactors <xmultiplier>, <ymultiplier>}
{noruler | ruler {at x,y}}
{polardistance{deg|tan} | nopolardistance}
{format <string>}
{mouseformat <int>/<string>}
{{no}labels {"labeloptions"}}
{{no}zoomjump} {{no}verbose}
unset mouse
The options `noruler` and `ruler` switch the ruler off and on, the latter
optionally setting the origin at the given coordinates. While the ruler is on,
the distance in user units from the ruler origin to the mouse is displayed
continuously. By default, toggling the ruler has the key binding 'r'.
The option `polardistance` determines if the distance between the mouse cursor
and the ruler is also shown in polar coordinates (distance and angle in
degrees or tangent (slope)). This corresponds to the default key binding '5'.
Choose the option `labels` to define persistent gnuplot labels using Button 2.
The default is `nolabels`, which makes Button 2 draw only a temporary label at
the mouse position. Labels are drawn with the current setting of `mouseformat`.
The `labeloptions` string is passed to the `set label` command. The default is
"point pointstyle 1" which will plot a small plus at the label position.
Temporary labels will disappear at the next `replot` or mouse zoom operation.
Persistent labels can be removed by holding the Ctrl-Key down while clicking
Button 2 on the label's point. The threshold for how close you must be to the
label is also determined by the `pointsize`.
If the option `verbose` is turned on the communication commands are shown
during execution. This option can also be toggled by hitting `6` in the
driver's window. `verbose` is off by default.
Press 'h' in the driver's window for a short summary of the mouse and key
bindings. This will also display user defined bindings or `hotkeys` which
can be defined using the `bind` command, see help for `bind`. Note, that user
defined `hotkeys` may override the default bindings.
See also help for `bind` and `label`.
?set mouse doubleclick
?mouse doubleclick
The doubleclick resolution is given in milliseconds and used for Button 1,
which copies the current mouse position to the `clipboard` on some terminals.
The default value is 300 ms. Setting the value to 0 ms triggers the copy on
a single click.
?set mouse format
?set mouse mouseformat
?mouse format
?mouseformat
The `set mouse format` command specifies a format string for sprintf() which
determines how the mouse cursor [x,y] coordinates are printed to the plot
window and to the clipboard. The default is "% #g".
`set mouse mouseformat` is used for formatting the text on Button1 and Button2
actions -- copying the coordinates to the clipboard and temporarily annotating
the mouse position. An integer argument selects one of the format options in
the table below. A string argument is used as a format for sprintf() in option
6 and should contain two float specifiers.
Example:
`set mouse mouseformat "mouse x,y = %5.2g, %10.3f"`.
Use `set mouse mouseformat ""` to turn this string off again.
The following formats are available:
0 default (same as 1)
1 axis coordinates 1.23, 2.45
2 graph coordinates (from 0 to 1) /0.00, 1.00/
3 x = timefmt y = axis [(as set by `set timefmt`), 2.45]
4 x = date y = axis [31. 12. 1999, 2.45]
5 x = time y = axis [23:59, 2.45]
6 x = date time y = axis [31. 12. 1999 23:59, 2.45]
7 format from `set mouse mouseformat`, e.g. "mouse x,y = 1.23, 2.450"
?set mouse scrolling
?mouse scrolling
?mouse wheel
?scrolling
?mousewheel
X and Y axis scaling in both 2D and 3D graphs can be adjusted using the
mouse wheel. <wheel-up> scrolls up (increases both YMIN and YMAX by ten
percent of the Y range, and increases both Y2MIN and Y2MAX likewise), and
<wheel down> scrolls down. <shift-wheel-up> scrolls left (decreases both
XMIN and XMAX, and both X2MIN and X2MAX), and <shift-wheel-down> scrolls
right. <control-wheel-up> zooms in toward the center of the plot, and
<control-wheel-down> zooms out. <shift-control-wheel-up> zooms in along the
X and X2 axes only, and <shift-control-wheel-down> zooms out along the X and
X2 axes only.
?mouse x11_mouse
?x11_mouse
?x11 mouse
If multiple X11 plot windows have been opened using the `set term x11 <n>`
terminal option, then only the current plot window supports the entire
range of mouse commands and hotkeys. The other windows will, however,
continue to display mouse coordinates at the lower left.
?mouse zoom
?zoom
Zooming is usually accomplished by holding down the left mouse button and
dragging the mouse to delineate a zoom region. Some platforms may require
using a different mouse button. The original plot can be restored by typing
the 'u' hotkey in the plot window. The hotkeys 'p' and 'n' step back and
forth through a history of zoom operations.
The option `zoomcoordinates` determines if the coordinates of the zoom box are
drawn at the edges while zooming. This is on by default.
If the option `zoomjump` is on, the mouse pointer will be automatically
offset a small distance after starting a zoom region with button 3. This can
be useful to avoid a tiny (or even empty) zoom region. `zoomjump` is off by
default.
?commands set mttics
?commands unset mttics
?commands show mttics
?set mttics
?unset mttics
?show mttics
?mttics
?nomttics
Minor tic marks around the perimeter of a polar plot are controlled by
by `set mttics`. Please see `set mxtics`.
?commands set multiplot
?commands unset multiplot
?set multiplot
?unset multiplot
?multiplot
?nomultiplot
?layout
The command `set multiplot` places `gnuplot` in the multiplot mode, in which
several plots are placed next to each other on the same page or screen window.
Syntax:
set multiplot
{ title <page title> {font <fontspec>} {enhanced|noenhanced} }
{ layout <rows>,<cols>
{rowsfirst|columnsfirst} {downwards|upwards}
{scale <xscale>{,<yscale>}} {offset <xoff>{,<yoff>}}
{margins <left>,<right>,<bottom>,<top>}
{spacing <xspacing>{,<yspacing>}}
}
set multiplot {next|previous}
unset multiplot
For some terminals, no plot is displayed until the command `unset multiplot`
is given, which causes the entire page to be drawn and then returns gnuplot
to its normal single-plot mode. For other terminals, each separate `plot`
command produces an updated display.
The `clear` command is used to erase the rectangular area of the page that will
be used for the next plot. This is typically needed to inset a small plot
inside a larger plot.
Any labels or arrows that have been defined will be drawn for each plot
according to the current size and origin (unless their coordinates are
defined in the `screen` system). Just about everything else that can be
`set` is applied to each plot, too. If you want something to appear only
once on the page, for instance a single time stamp, you'll need to put a `set
time`/`unset time` pair around one of the `plot`, `splot` or `replot`
commands within the `set multiplot`/`unset multiplot` block.
The multiplot title is separate from the individual plot titles, if any.
Space is reserved for it at the top of the page, spanning the full width
of the canvas.
The commands `set origin` and `set size` must be used to correctly position
each plot if no layout is specified or if fine tuning is desired. See
`set origin` and `set size` for details of their usage.
Example:
set multiplot
set size 0.4,0.4
set origin 0.1,0.1
plot sin(x)
set size 0.2,0.2
set origin 0.5,0.5
plot cos(x)
unset multiplot
This displays a plot of cos(x) stacked above a plot of sin(x).
`set size` and `set origin` refer to the entire plotting area used for each
plot. Please also see `set term size`. If you want to have the axes
themselves line up, you can guarantee that the margins are the same size with
the `set margin` commands. See `set margin` for their use. Note that the
margin settings are absolute, in character units, so the appearance of the
graph in the remaining space will depend on the screen size of the display
device, e.g., perhaps quite different on a video display and a printer.
With the `layout` option you can generate simple multiplots without having
to give the `set size` and `set origin` commands before each plot: Those
are generated automatically, but can be overridden at any time. With
`layout` the display will be divided by a grid with <rows> rows and
<cols> columns. This grid is filled rows first or columns first depending on
whether the corresponding option is given in the multiplot command. The stack
of plots can grow `downwards` or `upwards`.
Default is `rowsfirst` and `downwards`.
The commands `set multiplot next` and `set multiplot previous` are relevant
only in the context of using the layout option. `next` skips the next position
in the grid, leaving a blank space. `prev` returns to the grid position
immediately preceding the most recently plotted position.
Each plot can be scaled by `scale` and shifted with `offset`; if the y-values
for scale or offset are omitted, the x-value will be used. `unset multiplot`
will turn off the automatic layout and restore the values of `set size` and
`set origin` as they were before `set multiplot layout`.
Example:
set size 1,1
set origin 0,0
set multiplot layout 3,2 columnsfirst scale 1.1,0.9
[ up to 6 plot commands here ]
unset multiplot
The above example will produce 6 plots in 2 columns filled top to bottom,
left to right. Each plot will have a horizontal size of 1.1/2 and a vertical
size of 0.9/3.
Another possibility is to set uniform margins for all plots in the layout with
options `layout margins` and `spacing`, which must be used together. With
`margins` you set the outer margins of the whole multiplot grid.
`spacing` gives the gap size between two adjacent subplots, and can also
be given in `character` or `screen` units. If a single value is given,
it is used for both x and y direction, otherwise two different values
can be selected.
If one value has no unit, the one of the preceding margin setting is used.
Example:
set multiplot layout 2,2 margins 0.1, 0.9, 0.1, 0.9 spacing 0.0
In this case the two left-most subplots will have left boundaries at screen
coordinate 0.1, the two right-most subplots will have right boundaries at
screen coordinate 0.9, and so on. Because the spacing between subplots is
given as 0, their inner boundaries will superimpose.
Example:
set multiplot layout 2,2 margins char 5,1,1,2 spacing screen 0, char 2
This produces a layout in which the boundary of both left subplots is
5 character widths from the left edge of the canvas, the right boundary of the
right subplots is 1 character width from the canvas edge.
The overall bottom margin is one character height and the overall top margin
is 2 character heights. There is no horizontal gap between the two columns of
subplots. The vertical gap between subplots is equal to 2 character heights.
Example:
set multiplot layout 2,2 columnsfirst margins 0.1,0.9,0.1,0.9 spacing 0.1
set ylabel 'ylabel'
plot sin(x)
set xlabel 'xlabel'
plot cos(x)
unset ylabel
unset xlabel
plot sin(2*x)
set xlabel 'xlabel'
plot cos(2*x)
unset multiplot
See also
multiplot demo (multiplt.dem)
?commands set mx2tics
?commands unset mx2tics
?commands show mx2tics
?set mx2tics
?unset mx2tics
?show mx2tics
?mx2tics
?nomx2tics
Minor tic marks along the x2 (top) axis are controlled by `set mx2tics`.
Please see `set mxtics`.
?commands set mxtics
?commands unset mxtics
?commands show mxtics
?set mxtics
?unset mxtics
?show mxtics
?mxtics
?nomxtics
Minor tic marks along the x axis are controlled by `set mxtics`. They can be
turned off with `unset mxtics`. Similar commands control minor tics along
the other axes.
Syntax:
set mxtics {<freq> | default}
unset mxtics
show mxtics
The same syntax applies to `mytics`, `mztics`, `mx2tics`, `my2tics`, `mrtics`,
`mttics` and `mcbtics`.
<freq> is the number of sub-intervals (NOT the number of minor tics) between
major tics (the default for a linear axis is either two or five
depending on the major tics, so there are one or four minor
tics between major tics). Selecting `default` will return the number of minor
ticks to its default value.
If the axis is logarithmic, the number of sub-intervals will be set to a
reasonable number by default (based upon the length of a decade). This will
be overridden if <freq> is given. However the usual minor tics (2, 3, ...,
8, 9 between 1 and 10, for example) are obtained by setting <freq> to 10,
even though there are but nine sub-intervals.
To set minor tics at arbitrary positions, use the ("<label>" <pos> <level>,
...) form of `set {x|x2|y|y2|z}tics` with <label> empty and <level> set to 1.
The `set m{x|x2|y|y2|z}tics` commands work only when there are uniformly
spaced major tics. If all major tics were placed explicitly by
`set {x|x2|y|y2|z}tics`, then minor tic commands are ignored. Implicit
major tics and explicit minor tics can be combined using
`set {x|x2|y|y2|z}tics` and `set {x|x2|y|y2|z}tics add`.
Examples:
set xtics 0, 5, 10
set xtics add (7.5)
set mxtics 5
Major tics at 0,5,7.5,10, minor tics at 1,2,3,4,6,7,8,9
set logscale y
set ytics format ""
set ytics 1e-6, 10, 1
set ytics add ("1" 1, ".1" 0.1, ".01" 0.01, "10^-3" 0.001, \
"10^-4" 0.0001)
set mytics 10
Major tics with special formatting, minor tics at log positions
By default, minor tics are off for linear axes and on for logarithmic axes.
They inherit the settings for `axis|border` and `{no}mirror` specified for
the major tics. Please see `set xtics` for information about these.
?commands set my2tics
?commands unset my2tics
?commands show my2tics
?set my2tics
?unset my2tics
?show my2tics
?my2tics
?nomy2tics
Minor tic marks along the y2 (right-hand) axis are controlled by `set
my2tics`. Please see `set mxtics`.
?commands set mytics
?commands unset mytics
?commands show mytics
?set mytics
?unset mytics
?show mytics
?mytics
?nomytics
Minor tic marks along the y axis are controlled by `set mytics`. Please
see `set mxtics`.
?commands set mztics
?commands unset mztics
?commands show mztics
?set mztics
?unset mztics
?show mztics
?mztics
?nomztics
Minor tic marks along the z axis are controlled by `set mztics`. Please
see `set mxtics`.
?commands set nonlinear
?set nonlinear
?nonlinear
Syntax:
set nonlinear <axis> via f(axis) inverse g(axis)
unset nonlinear <axis>
[new command in version 5.2]
This command is similar to the `set link` command except that only one of the
two linked axes is visible. The hidden axis remains linear. Coordinates along
the visible axis are mapped by applying g(x) to hidden axis coordinates.
f(x) maps the visible axis coordinates back onto the hidden linear axis.
Example:
set xrange [1:1000]
set nonlinear x via log10(x) inverse 10**x
This example establishes a log-scaled x axis. It is an alternative way of
achieving the effect of `set log x`. The hidden axis in this case has range
[0:3], obtained by calculating [log10(xmin):log10(xmax)]. You must provide
both the forward and inverse expressions.
Example:
set xrange [-3:3]
set nonlinear x via norm(x) inverse invnorm(x)
This example establishes a probability-scaled ("probit") x axis, such that
plotting the cumulative normal function Phi(x) produces a straight line plot
against a linear y axis.
Example:
logit(p) = log(p/(1-p))
logistic(a) = 1. / (1. + exp(-a))
set xrange [.001 : .999]
set nonlinear y via logit(y) inverse logistic(y)
plot logit(x)
This example establishes a logit-scaled y axis such that plotting logit(x)
on a linear x axis produces a straight line plot.
Example:
f(x) = (x <= 100) ? x : (x < 500) ? NaN : x-390
g(x) = (x <= 100) ? x : x+390
set xrange [0:1000] noextend
set nonlinear x via f(x) inverse g(x)
set xtics add (100,500)
plot sample [x=1:100] x, [x=500:1000] x
This example creates a "broken axis". X coordinates 0-100 are at the left,
X coordinates 500-1000 are at the right, there is a small gap (10 units)
between them. So long as no data points with (100 < x < 500) are plotted,
this works as expected.
?objects
?commands set object
?commands show object
?set object
?show object
The `set object` command defines a single object which will appear in
subsequent plots. You may define as many objects as you like. Currently the
supported object types are `rectangle`, `circle`, `ellipse`, and `polygon`.
Rectangles inherit a default set of style properties (fill, color, border) from
those set by the command `set style rectangle`, but each object can also be
given individual style properties. Circles, ellipses, and polygons inherit the
fill style from `set style fill`. Objects to be drawn in 2D plots may be
defined in any combination of axis, graph, polar, or screen coordinates.
Object specifications in 3D plots cannot use graph coordinates.
Rectangles and ellipses in 3D plots are limited to screen coordinates.
Syntax:
set object <index>
<object-type> <object-properties>
{front|back|behind} {clip|noclip}
{fc|fillcolor <colorspec>} {fs <fillstyle>}
{default} {lw|linewidth <width>} {dt|dashtype <dashtype>}
unset object <index>
<object-type> is either `rectangle`, `ellipse`, `circle`, or `polygon`.
Each object type has its own set of characteristic properties.
Setting `front` will draw the object in front of all plot elements, but
behind any labels that are also marked `front`. Setting `back` will place the
object behind all plot curves and labels. Setting `behind` will place the
object behind everything including the axes and `back` rectangles, thus
set object rectangle from screen 0,0 to screen 1,1 behind
can be used to provide a colored background for the entire graph or page.
By default, objects are clipped to the graph boundary unless one or more
vertices are given in screen coordinates. Setting `noclip` will disable
clipping to the graph boundary, but will still clip against the screen size.
The fill color of the object is taken from the <colorspec>. `fillcolor`
may be abbreviated `fc`. The fill style is taken from <fillstyle>.
See `colorspec` and `fillstyle`. If the keyword `default` is given,
these properties are inherited from the default settings at the time a plot
is drawn. See `set style rectangle`.
?rectangle
?commands set object rectangle
?commands show object rectangle
?set object rectangle
?show object rectangle
Syntax:
set object <index> rectangle
{from <position> {to|rto} <position> |
center <position> size <w>,<h> |
at <position> size <w>,<h>}
The position of the rectangle may be specified by giving the position of two
diagonal corners (bottom left and top right) or by giving the position of the
center followed by the width and the height. In either case the positions
may be given in axis, graph, or screen coordinates. See `coordinates`.
The options `at` and `center` are synonyms.
Examples:
# Force the entire area enclosed by the axes to have background color cyan
set object 1 rect from graph 0, graph 0 to graph 1, graph 1 back
set object 1 rect fc rgb "cyan" fillstyle solid 1.0
# Position a red square with lower left at 0,0 and upper right at 2,3
set object 2 rect from 0,0 to 2,3 fc lt 1
# Position an empty rectangle (no fill) with a blue border
set object 3 rect from 0,0 to 2,3 fs empty border rgb "blue"
# Return fill and color to the default style but leave vertices unchanged
set object 2 rect default
Rectangle corners specified in screen coordinates may extend beyond the edge of
the current graph. Otherwise the rectangle is clipped to fit in the graph.
?ellipse
?commands set object ellipse
?commands show object ellipse
?set object ellipse
?show object ellipse
Syntax:
set object <index> ellipse {at|center} <position> size <w>,<h>
{angle <orientation>} {units xy|xx|yy}
{<other-object-properties>}
The position of the ellipse is specified by giving the center followed by
the width and the height (actually the major and minor axes). The keywords
`at` and `center` are synonyms. The center position may be given in axis,
graph, or screen coordinates. See `coordinates`. The major and minor axis
lengths must be given in axis coordinates. The orientation of the ellipse
is specified by the angle between the horizontal axis and the major diameter
of the ellipse. If no angle is given, the default ellipse orientation
will be used instead (see `set style ellipse`). The `units` keyword
controls the scaling of the axes of the ellipse. `units xy` means that the
major axis is interpreted in terms of units along the x axis, while the
minor axis in that of the y axis. `units xx` means that both axes of the
ellipses are scaled in the units of the x axis, while `units yy` means
that both axes are in units of the y axis.
The default is `xy` or whatever `set style ellipse units` was set to.
NB: If the x and y axis scales are not equal, (e.g. `units xy` is in
effect) then the major/minor axis ratio will no longer be correct after
rotation.
Note that `set object ellipse size <2r>,<2r>` does not in general produce
the same result as `set object circle <r>`. The circle radius is always
interpreted in terms of units along the x axis, and will always produce a
circle even if the x and y axis scales are different and even if the aspect
ratio of your plot is not 1. If `units` is set to `xy`, then
'set object ellipse' interprets the first <2r> in terms of x axis units
and the second <2r> in terms of y axis units. This will only produce a
circle if the x and y axis scales are identical and the plot aspect ratio
is 1. On the other hand, if `units` is set to `xx` or `yy`, then the
diameters specified in the 'set object' command will be interpreted in the
same units, so the ellipse will have the correct aspect ratio, and it will
maintain its aspect ratio even if the plot is resized.
?circle
?commands set object circle
?commands show object circle
?set object circle
?show object circle
Syntax:
set object <index> circle {at|center} <position> size <radius>
{arc [<begin>:<end>]}
{<other-object-properties>}
The position of the circle is specified by giving the position of the center
center followed by the radius. The keywords `at` and `center` are synonyms.
In 2D plots the position and radius may be given in any coordinate system.
See `coordinates`. Circles in 3D plots cannot use graph coordinates.
In all cases the radius is calculated relative to the horizontal scale of the
axis, graph, or canvas. Any disparity between the horizontal and vertical
scaling will be corrected for so that the result is always a circle.
If you want to draw a circle in plot coordinates (such that it will appear as
an ellipse if the horizontal and vertical scales are different), use
`set object ellipse` instead.
By default a full circle is drawn. The optional qualifier `arc` specifies
a starting angle and ending angle, in degrees, for one arc of the circle.
The arc is always drawn counterclockwise.
See also `set object ellipse`.
?polygon
?commands set object polygon
?commands show object polygon
?set object polygon
?show object polygon
Syntax:
set object <index> polygon
from <position> to <position> ... {to <position>}
or
from <position> rto <position> ... {rto <position>}
The position of the polygon may be specified by giving the position of a
sequence of vertices. These may be given in any coordinate system.
If relative coordinates are used (rto) then the coordinate type must match
that of the previous vertex.
See `coordinates`.
Example:
set object 1 polygon from 0,0 to 1,1 to 2,0
set object 1 fc rgb "cyan" fillstyle solid 1.0 border lt -1
?commands set offsets
?commands unset offsets
?commands show offsets
?set offsets
?unset offsets
?show offsets
?offsets
?nooffsets
Offsets provide a mechanism to put an empty boundary around the data inside
an autoscaled graph. The offsets only affect the x1 and y1 axes, and only in
2D `plot` commands.
Syntax:
set offsets <left>, <right>, <top>, <bottom>
unset offsets
show offsets
Each offset may be a constant or an expression. Each defaults to 0.
By default, the left and right offsets are given in units of the first x axis,
the top and bottom offsets in units of the first y axis. Alternatively, you
may specify the offsets as a fraction of the total axis range by using the
keyword "graph". A positive offset expands the axis range in the specified
direction, e.g., a positive bottom offset makes ymin more negative. Negative
offsets, while permitted, can have unexpected interactions with autoscaling
and clipping. To prevent the auto-scaling from further adjusting your axis
ranges, it is useful to also specify "set auto fix".
Example:
set auto fix
set offsets graph 0.05, 0, 2, 2
plot sin(x)
This graph of sin(x) will have a y range [-3:3] because the function
will be autoscaled to [-1:1] and the vertical offsets are each two.
The x range will be [-11:10] because the default is [-10:10] and it has
been expanded to the left by 0.05 of that total range.
?commands set origin
?commands show origin
?set origin
?show origin
?origin
The `set origin` command is used to specify the origin of a plotting surface
(i.e., the graph and its margins) on the screen. The coordinates are given
in the `screen` coordinate system (see `coordinates` for information about
this system).
Syntax:
set origin <x-origin>,<y-origin>
?commands set output
?commands show output
?set output
?show output
?output
?output file
By default, screens are displayed to the standard output. The `set output`
command redirects the display to the specified file or device.
Syntax:
set output {"<filename>"}
show output
The filename must be enclosed in quotes. If the filename is omitted, any
output file opened by a previous invocation of `set output` will be closed
and new output will be sent to STDOUT. (If you give the command `set output
"STDOUT"`, your output may be sent to a file named "STDOUT"! ["May be", not
"will be", because some terminals, like `x11` or `wxt`, ignore `set output`.])
When both `set terminal` and `set output` are used together, it is safest to
give `set terminal` first, because some terminals set a flag which is needed
in some operating systems. This would be the case, for example, if the
operating system needs a separate open command for binary files.
On platforms that support pipes, it may be useful to pipe terminal output.
For instance,
set output "|lpr -Plaser filename"
set term png; set output "|display png:-"
On MSDOS machines, `set output "PRN"` will direct the output to the default
printer. On VMS, output can be sent directly to any spooled device.
?commands set parametric
?commands unset parametric
?commands show parametric
?set parametric
?unset parametric
?show parametric
?parametric
?noparametric
The `set parametric` command changes the meaning of `plot` (`splot`) from
normal functions to parametric functions. The command `unset parametric`
restores the plotting style to normal, single-valued expression plotting.
Syntax:
set parametric
unset parametric
show parametric
For 2D plotting, a parametric function is determined by a pair of parametric
functions operating on a parameter. An example of a 2D parametric function
would be `plot sin(t),cos(t)`, which draws a circle (if the aspect ratio is
set correctly---see `set size`). `gnuplot` will display an error message if
both functions are not provided for a parametric `plot`.
For 3D plotting, the surface is described as x=f(u,v), y=g(u,v), z=h(u,v).
Therefore a triplet of functions is required. An example of a 3D parametric
function would be `cos(u)*cos(v),cos(u)*sin(v),sin(u)`, which draws a sphere.
`gnuplot` will display an error message if all three functions are not
provided for a parametric `splot`.
The total set of possible plots is a superset of the simple f(x) style plots,
since the two functions can describe the x and y values to be computed
separately. In fact, plots of the type t,f(t) are equivalent to those
produced with f(x) because the x values are computed using the identity
function. Similarly, 3D plots of the type u,v,f(u,v) are equivalent to
f(x,y).
Note that the order the parametric functions are specified is xfunction,
yfunction (and zfunction) and that each operates over the common parametric
domain.
Also, the `set parametric` function implies a new range of values. Whereas
the normal f(x) and f(x,y) style plotting assume an xrange and yrange (and
zrange), the parametric mode additionally specifies a trange, urange, and
vrange. These ranges may be set directly with `set trange`, `set urange`,
and `set vrange`, or by specifying the range on the `plot` or `splot`
commands. Currently the default range for these parametric variables is
[-5:5]. Setting the ranges to something more meaningful is expected.
?commands set paxis
?set paxis
?show paxis
Syntax:
set paxis <axisno> {range <range-options> | tics <tic-options>}
show paxis <axisno> {range | tics}
The `set paxis` command is equivalent to the `set xrange` and `set xtics`
commands except that it acts on one of the axes p1, p2, ... used in parallel
axis plots. See `parallelaxes`, `set xrange`, and `set xtics`.
The normal options to the range and tics commands are accepted although not
all options make sense for parallel axis plots.
?commands show plot
?show plot
The `show plot` command shows the current plotting command as it results
from the last `plot` and/or `splot` and possible subsequent `replot` commands.
In addition, the `show plot add2history` command adds this current plot
command into the `history`. It is useful if you have used `replot` to add
more curves to the current plot and you want to edit the whole command now.
?commands set pm3d
?commands show pm3d
?set pm3d
?show pm3d
?pm3d
pm3d is an `splot` style for drawing palette-mapped 3d and 4d data as
color/gray maps and surfaces. It uses an algorithm that allows plotting
gridded as well as non-gridded data without preprocessing, even when the data
scans do not have the same number of points.
Syntax (the options can be given in any order):
set pm3d {
{ at <position> }
{ interpolate <steps/points in scan, between scans> }
{ scansautomatic | scansforward | scansbackward | depthorder }
{ flush { begin | center | end } }
{ ftriangles | noftriangles }
{ clip1in | clip4in }
{ corners2color
{ mean|geomean|harmean|rms|median|min|max|c1|c2|c3|c4 }
}
{ {no}lighting {primary <fraction>} {specular <fraction>}}
{ hidden3d {<linestyle>} | nohidden3d }
{ implicit | explicit }
{ map }
}
show pm3d
unset pm3d
A pm3d color surface is drawn if the splot command specifies `with pm3d`,
if the data or function `style` is set to pm3d globally, or if the pm3d mode is
`set pm3d implicit`. In the latter two cases, the pm3d surface is draw in
addition to the mesh produced by the style specified in the plot command. E.g.
splot 'fred.dat' with lines, 'lola.dat' with lines
would draw both a mesh of lines and a pm3d surface for each data set.
If the option `explicit` is on (or `implicit` is off) only plots specified
by the `with pm3d` attribute are plotted with a pm3d surface, e.g.:
splot 'fred.dat' with lines, 'lola.dat' with pm3d
would plot 'fred.dat' with lines (only) and 'lola.dat' with a pm3d surface.
On gnuplot start-up, the mode is `explicit`. For historical and compatibility
reasons, the commands `set pm3d;` (i.e. no options) and `set pm3d at X ...`
(i.e. `at` is the first option) change the mode to `implicit`.
The command `set pm3d;` sets other options to their default state.
If you set the default data or function style to `pm3d`, e.g.:
set style data pm3d
then the options `implicit` and `explicit` have no effect.
Note that when plotting several plots, they are plotted in the order given
on the command line. This can be of interest especially for filled surfaces
which can overwrite and therefore hide part of earlier plots.
The pm3d coloring can be drawn at any or all of three different positions,
`top`, `bottom`, or `surface`. See `pm3d position`.
The following command draws three color surfaces at different altitudes:
set border 4095
set pm3d at s
splot 10*x with pm3d at b, x*x-y*y, x*x+y*y with pm3d at t
See also help for `set palette`, `set cbrange`, `set colorbox`,
and definitely the demo file `demo/pm3d.dem`.
?pm3d algorithm
Let us first describe how a map/surface is drawn. The input data come from an
evaluated function or from an `splot data file`. Each surface consists of a
sequence of separate scans (isolines). The pm3d algorithm fills the region
between two neighbouring points in one scan with another two points in the
next scan by a gray (or color) according to z-values (or according to an
additional 'color' column, see help for `using`) of these 4 corners; by default
the 4 corner values are averaged, but this can be changed by the option
`corners2color`. In order to get a reasonable surface, the neighbouring scans
should not cross and the number of points in the neighbouring scans should not
differ too much; of course, the best plot is with scans having same number of
points. There are no other requirements (e.g. the data need not be gridded).
Another advantage is that the pm3d algorithm does not draw anything outside of
the input (measured or calculated) region.
Surface coloring works with the following input data:
1. splot of function or of data file with one or three data columns: The
gray/color scale is obtained by mapping the averaged (or `corners2color`)
z-coordinate of the four corners of the above-specified quadrangle into the
range [min_color_z,max_color_z] of `zrange` or `cbrange` providing a gray value
in the range [0:1]. This value can be used directly as the gray for gray maps.
The normalized gray value can be further mapped into a color---see `set palette`
for the complete description.
2. splot of data file with two or four data columns: The gray/color value is
obtained by using the last-column coordinate instead of the z-value, thus
allowing the color and the z-coordinate be mutually independent. This can be
used for 4d data drawing.
Other notes:
1. The term 'scan' referenced above is used more among physicists than the
term 'iso_curve' referenced in gnuplot documentation and sources. You measure
maps recorded one scan after another scan, that's why.
2. The 'gray' or 'color' scale is a linear mapping of a continuous variable
onto a smoothly varying palette of colors. The mapping is shown in a
rectangle next to the main plot. This documentation refers to this as a
"colorbox", and refers to the indexing variable as lying on the colorbox axis.
See `set colorbox`, `set cbrange`.
?lighting
?pm3d lighting
?pm3d nolighting
?set pm3d lighting
By default the colors assigned to pm3d objects are not dependent on orientation
or viewing angle. This state corresponds to `set pm3d nolighting`.
The command `set pm3d lighting` selects a simple lighting model consisting of a
single fixed source of illumination contributing 50% of the overall lighting.
The strength of this light relative to the ambient illumination can be adjusted
by `set pm3d lighting primary <fraction>`. Inclusion of specular highlighting
can be adjusted by setting a fractional contribution:
set pm3d lighting primary 0.50 specular 0.0 # no highlights
set pm3d lighting primary 0.50 specular 0.6 # strong highlights
?pm3d position
?set pm3d position
Color surface can be drawn at the base or top (then it is a gray/color planar
map) or at z-coordinates of surface points (gray/color surface). This is
defined by the `at` option with a string of up to 6 combinations of `b`, `t`
and `s`. For instance, `at b` plots at bottom only, `at st` plots firstly
surface and then top map, while `at bstbst` will never by seriously used.
Colored quadrangles are plotted one after another. When plotting surfaces
(`at s`), the later quadrangles overlap (overdraw) the previous ones.
(Gnuplot is not virtual reality tool to calculate intersections of filled
polygon meshes.) You may try to switch between `scansforward` and
`scansbackward` to force the first scan of the data to be plotted first or
last. The default is `scansautomatic` where gnuplot makes a guess about scans
order. On the other hand, the `depthorder` option completely reorders the
quadrangles. The rendering is performed after a depth sorting, which allows to
visualize even complicated surfaces; see `pm3d depthorder` for more details.
?pm3d scanorder
?pm3d depthorder
?pm3d flush
?pm3d ftriangles
?set pm3d scanorder
?set pm3d depthorder
?set pm3d flush
?set pm3d ftriangles
?depthorder
By default the quadrangles making up a pm3d solid surface are rendered in the
order they are encountered along the surface grid points. This order may be
controlled by the options `scansautomatic`|`scansforward`|`scansbackward`.
These scan options are not in general compatible with hidden-surface removal.
If two successive scans do not have same number of points, then it has to be
decided whether to start taking points for quadrangles from the beginning of
both scans (`flush begin`), from their ends (`flush end`) or to center them
(`flush center`). Note, that `flush (center|end)` are incompatible with
`scansautomatic`: if you specify `flush center` or `flush end` and
`scansautomatic` is set, it is silently switched to `scansforward`.
If two subsequent scans do not have the same number of points, the option
`ftriangles` specifies whether color triangles are drawn at the scan tail(s)
where there are not enough points in either of the scans. This can be used to
draw a smooth map boundary.
Gnuplot does not do true hidden surface removal for solid surfaces, but often
it is sufficient to render the component quadrangles in order from furthest
to closest. This mode may be selected using the options
set pm3d depthorder hidden3d
The `depthorder` option orders the solid quadrangles; the `hidden3d` option
similarly orders the bounding lines (if drawn). Note that the global option
`set hidden3d` does not affect pm3d surfaces.
?pm3d clipping
?set pm3d clipping
Clipping with respect to x, y coordinates of quadrangles can be done in two
ways. `clip1in`: all 4 points of each quadrangle must be defined and at least
1 point of the quadrangle must lie in the x and y ranges. `clip4in`: all 4
points of each quadrangle must lie in the x and y ranges.
?pm3d color_assignment
`3 columns of data (x,y,z)`:
The coloring setup as well as the color box drawing are determined by
`set palette`. There can be only one palette for the current plot. Drawing
of several surfaces with different palettes can be achieved by `multiplot`
with fixed `origin` and `size`; don't forget to use `set palette maxcolors`
when your terminal is running out of available colors.
There is a single gray/color value associated to each drawn pm3d quadrangle
(it contains a solid color, not a gradient). The value is calculated from
z-coordinates the four corners according to `corners2color <option>`.
`4 columns of data (x,y,z,color)`:
If a fourth column of data is provided, it is normally interpreted as a
separate palette-mapped gray value. The coloring of individual quadrangles
works as above, except that the color value is distinct from the z value.
As a separate coloring option, the fourth data column may provide instead
an RGB color. See `rgbcolor variable`. In this case the plotting command
must be
splot ... using 1:2:3:4 with pm3d lc rgb variable
Another drawing algorithm, which would draw quadrangles around a given node
by taking corners from averaged (x,y)-coordinates of its surrounding 4 nodes
while using node's color, could be implemented in the future. This is already
done for drawing images (2D grids) via `image` and `rgbimage` styles.
Notice that ranges of z-values and color-values for surfaces are adjustable
independently by `set zrange`, `set cbrange`, as well as `set log` for z or
cb. Maps can be adjusted by the cb-axis only; see also `set view map` and
`set colorbox`.
?pm3d corners2color
?set pm3d corners2color
?corners2color
The color of each quadrangle in a pm3d surface is assigned based on the color
values of its four bounding vertices.
The options 'mean' (default), 'geomean', 'harmean, 'rms', and 'median' produce
various kinds of surface color smoothing, while options 'min' and 'max' choose
minimal or maximal value, respectively. This may not be desired for pixel
images or for maps with sharp and intense peaks, in which case the options
'c1', 'c2', 'c3' or 'c4' can be used instead to assign the quadrangle color
based on the z-coordinate of only one corner. Some experimentation may be
needed to determine which corner corresponds to 'c1', as the orientation
depends on the drawing direction. Because the pm3d algorithm does not extend
the colored surface outside the range of the input data points, the 'c<j>'
coloring options will result in pixels along two edges of the grid not
contributing to the color of any quadrangle. For example, applying the pm3d
algorithm to the 4x4 grid of data points in script `demo/pm3d.dem` (please have
a look) produces only (4-1)x(4-1)=9 colored rectangles.
?set pm3d hidden3d
?pm3d hidden3d
?set pm3d border
?pm3d border
The option `set pm3d border {line-properties}` draws bounding lines around each
quadrangle as it is rendered. Normally this is used in conjunction with the
`depthorder` option to approximate hidden line removal.
Note that the global option `set hidden3d` has no effect on pm3d plots.
Default line properties (color, width) optionally follow the keyword `border`.
These defaults can be overridden later in an splot command.
Example of recommended usage:
set pm3d at s depthorder border lw 0.2 lt black
unset hidden3d
unset surf
splot x*x+y*y linecolor rgb "blue" # otherwise it would be black
NB: The deprecated option `set pm3d hidden3d N` is still accepted. It is
equivalent to `set pm3d border ls N`.
?set pm3d interpolate
?pm3d interpolate
The option `interpolate m,n` will interpolate between grid points to generate
a finer mesh. For data files, this smooths the color surface and enhances the
contrast of spikes in the surface. When working with functions, interpolation
makes little sense. It would usually make more sense to increase `samples` and
`isosamples`.
For positive m and n, each quadrangle or triangle is interpolated m-times and
n-times in the respective direction. For negative m and n, the interpolation
frequency is chosen so that there will be at least |m| and |n| points drawn;
you can consider this as a special gridding function.
Note: `interpolate 0,0`, will automatically choose an optimal number of
interpolated surface points.
Note: Currently color interpolation is always linear, even if corners2color
is set to a nonlinear scheme such as the geometric mean.
?set pm3d deprecated_options
?pm3d deprecated_options
?set pm3d map
?pm3d map
?map
There used to be an option {transparent|solid} to this command. Now
you get the same effect from `set grid {front|layerdefault}`, respectively.
The old command `set pm3d map` is equivalent to `set pm3d at b;
set view map scale 1.0; set style data pm3d; set style func pm3d;`
?commands set palette
?commands show palette
?set palette
?show palette
?palette
Palette is a color storage for use by `pm3d`, filled color contours or
polygons, color histograms, color gradient background, and whatever it is
or it will be implemented... Here it stands for a palette of smooth
"continuous" colors or grays, but let's call it just a palette.
Color palettes require terminal entries for filled color polygons and
palettes of smooth colors, are currently available for terminals listed in
help for `set pm3d`. The range of color values are adjustable independently by
`set cbrange` and `set log cb`. The whole color palette is
visualized in the `colorbox`.
Syntax:
set palette
set palette {
{ gray | color }
{ gamma <gamma> }
{ rgbformulae <r>,<g>,<b>
| defined { ( <gray1> <color1> {, <grayN> <colorN>}... ) }
| file '<filename>' {datafile-modifiers}
| functions <R>,<G>,<B>
}
{ cubehelix {start <val>} {cycles <val>} {saturation <val>} }
{ model { RGB | HSV | CMY | YIQ | XYZ } }
{ positive | negative }
{ nops_allcF | ps_allcF }
{ maxcolors <maxcolors> }
}
show palette
show palette palette <n> {{float | int}}
show palette gradient
show palette fit2rgbformulae
show palette rgbformulae
show colornames
`set palette` (i.e. without options) sets up the default values.
Otherwise, the options can be given in any order.
`show palette` shows the current palette properties.
`show palette gradient` displays the gradient defining the palette (if
appropriate). `show palette rgbformulae` prints the available fixed gray -->
color transformation formulae. `show colornames` prints the known color names.
`show palette palette <n>` prints to the screen or to the file given by
`set print` a table of RGB triplets calculated for the current palette settings
and a palette having <n> discrete colors. The default wide table can be
limited to 3 columns of r,g,b float values [0..1] or integer values [0..255]
by options float or int, respectively. This way, the current gnuplot color
palette can be loaded into other imaging applications, for example Octave.
Alternatively, the `test palette` command will plot the R,G,B profiles for the
current palette and leave the profile values in a datablock $PALETTE.
The following options determine the coloring properties.
Figure using this palette can be `gray` or `color`. For instance, in `pm3d`
color surfaces the gray of each small spot is obtained by mapping the averaged
z-coordinate of the 4 corners of surface quadrangles into the range
[min_z,max_z] providing range of grays [0:1]. This value can be used directly
as the gray for gray maps. The color map requires a transformation gray -->
(R,G,B), i.e. a mapping [0:1] --> ([0:1],[0:1],[0:1]).
Basically two different types of mappings can be used: Analytic formulae to
convert gray to color, or discrete mapping tables which are interpolated.
`palette rgbformulae` and `palette functions` use analytic formulae whereas
`palette defined` and `palette file` use interpolated tables. `palette
rgbformulae` reduces the size of postscript output to a minimum.
The command `show palette fit2rgbformulae` finds the best matching `set
palette rgbformulae` for the current `set palette`. Naturally, it makes sense
to use it for non-rgbformulae palettes. This command can be found useful
mainly for external programs using the same rgbformulae definition of palettes
as gnuplot, like zimg (
http://zimg.sourceforge.net
).
`set palette gray` switches to a gray only palette. `set palette rgbformulae`,
`set palette defined`, `set palette file` and `set palette functions` switch
to a color mapping. `set palette color` is an easy way to switch back from the
gray palette to the last color mapping.
Automatic gamma correction via `set palette gamma <gamma>` can be done for
gray maps (`set palette gray`) and for the `cubehelix` color palette schemes.
Gamma = 1 produces a linear ramp of intensity. See `test palette`.
Many terminals support only discrete number of colors (e.g. 256 colors in gif).
After the default gnuplot linetype colors are allocated, the rest of the
available colors are by default reserved for pm3d. Thus a multiplot using
multiple palettes could fail because the first palette has used all the
available color positions. You can mitigate this limitation by using
`set palette maxcolors <N>` with a reasonably small value of N.
This option causes N discrete colors to be selected from a continuous palette
sampled at equally spaced intervals. If you want unequal spacing of N
discrete colors, use `set palette defined` instead of a single continuous
palette.
RGB color space might not be the most useful color space to work in. For that
reason you may change the color space with `model` to one of `RGB`, `HSV`,
`CMY`, `YIQ` and `XYZ`. Using color names for `set palette defined` tables
and a color space other than RGB will result in funny colors. All explanation
have been written for RGB color space, so please note, that `R` can be `H`,
`C`, `Y`, or `X`, depending on the actual color space (`G` and `B`
accordingly).
All values for all color spaces are limited to [0,1].
RGB stands for Red, Green and Blue; CMY stands for Cyan, Magenta and Yellow;
HSV stands for Hue, Saturation, and Value; YIQ is the color model used by
the U.S. Commercial Color Television Broadcasting, it is basically an RGB
recoding with downward compatibility for black and white television;
XYZ are the three primary colors of the color model defined by the 'Commission
Internationale de l'Eclairage' (CIE).
For more information on color models see:
http://en.wikipedia.org/wiki/Color_space
?commands set palette rgbformulae
?set palette rgbformulae
?palette rgbformulae
?rgbformulae
For `rgbformulae` three suitable mapping functions have
to be chosen. This is done via `rgbformulae <r>,<g>,<b>`. The available
mapping functions are listed by `show palette rgbformulae`. Default is
`7,5,15`, some other examples are `3,11,6`, `21,23,3` or `3,23,21`. Negative
numbers, like `3,-11,-6`, mean inverted color (i.e. 1-gray passed into the
formula, see also `positive` and `negative` options below).
Some nice schemes in RGB color space
7,5,15 ... traditional pm3d (black-blue-red-yellow)
3,11,6 ... green-red-violet
23,28,3 ... ocean (green-blue-white); try also all other permutations
21,22,23 ... hot (black-red-yellow-white)
30,31,32 ... color printable on gray (black-blue-violet-yellow-white)
33,13,10 ... rainbow (blue-green-yellow-red)
34,35,36 ... AFM hot (black-red-yellow-white)
A full color palette in HSV color space
3,2,2 ... red-yellow-green-cyan-blue-magenta-red
Please note that even if called `rgbformulae` the formulas might actually
determine the <H>,<S>,<V> or <X>,<Y>,<Z> or ... color components as usual.
Use `positive` and `negative` to invert the figure colors.
Note that it is possible to find a set of the best matching rgbformulae for any
other color scheme by the command
show palette fit2rgbformulae
?commands set palette defined
?set palette defined
?palette defined
Gray-to-rgb mapping can be manually set by use of `palette defined`:
A color gradient is defined and used to give the rgb values. Such a gradient
is a piecewise linear mapping from gray values in [0,1] to the RGB space
[0,1]x[0,1]x[0,1]. You must specify the gray values and the corresponding RGB
values between which linear interpolation will be done.
Syntax:
set palette defined { ( <gray1> <color1> {, <grayN> <colorN>}... ) }
<grayX> are gray values which are mapped to [0,1] and <colorX> are the
corresponding rgb colors. The color can be specified in three different
ways:
<color> := { <r> <g> <b> | '<color-name>' | '#rrggbb' }
Either by three numbers (each in [0,1]) for red, green and blue, separated by
whitespace, or the name of the color in quotes or X style color specifiers
also in quotes. You may freely mix the three types in a gradient definition,
but the named color "red" will be something strange if RGB is not selected
as color space. Use `show colornames` for a list of known color names.
Please note, that even if written as <r>, this might actually be the
<H> component in HSV color space or <X> in CIE-XYZ space, or ...
depending on the selected color model.
The <gray> values have to form an ascending sequence of real numbers; the
sequence will be automatically rescaled to [0,1].
`set palette defined` (without a gradient definition in braces) switches to
RGB color space and uses a preset full-spectrum color gradient.
Use `show palette gradient` to display the gradient.
Examples:
To produce a gray palette (useless but instructive) use:
set palette model RGB
set palette defined ( 0 "black", 1 "white" )
To produce a blue yellow red palette use (all equivalent):
set palette defined ( 0 "blue", 1 "yellow", 2 "red" )
set palette defined ( 0 0 0 1, 1 1 1 0, 2 1 0 0 )
set palette defined ( 0 "#0000ff", 1 "#ffff00", 2 "#ff0000" )
To produce some rainbow-like palette use:
set palette defined ( 0 "blue", 3 "green", 6 "yellow", 10 "red" )
Full color spectrum within HSV color space:
set palette model HSV
set palette defined ( 0 0 1 1, 1 1 1 1 )
set palette defined ( 0 0 1 0, 1 0 1 1, 6 0.8333 1 1, 7 0.8333 0 1)
Approximate the default palette used by MATLAB:
set pal defined (1 '#00008f', 8 '#0000ff', 24 '#00ffff', \
40 '#ffff00', 56 '#ff0000', 64 '#800000')
To produce a palette with only a few, equally-spaced colors:
set palette model RGB maxcolors 4
set palette defined ( 0 "yellow", 1 "red" )
'Traffic light' palette (non-smooth color jumps at gray = 1/3 and 2/3).
set palette model RGB
set palette defined (0 "dark-green", 1 "green", \
1 "yellow", 2 "dark-yellow", \
2 "red", 3 "dark-red" )
?commands set palette functions
?set palette functions
?palette functions
Use `set palette functions <Rexpr>, <Gexpr>, <Bexpr>` to define three formulae
for the R(gray), G(gray) and B(gray) mapping. The three formulae may depend
on the variable `gray` which will take values in [0,1] and should also
produce values in [0,1].
Please note that <Rexpr> might be a formula for the H-value if HSV color
space has been chosen (same for all other formulae and color spaces).
Examples:
To produce a full color palette use:
set palette model HSV functions gray, 1, 1
A nice black to gold palette:
set palette model XYZ functions gray**0.35, gray**0.5, gray**0.8
A gamma-corrected black and white palette
gamma = 2.2
color(gray) = gray**(1./gamma)
set palette model RGB functions color(gray), color(gray), color(gray)
?commands set palette gray
?set palette gray
?set palette grey
?palette gray
`set palette gray` switches to a grayscale palette shading from 0.0 = black
to 1.0 = white. `set palette color` is an easy way to switch back from the
gray palette to the last color mapping.
?commands set palette cubehelix
?set palette cubehelix
?cubehelix
The "cubehelix" option defines a family of palettes in which color (hue) varies
along the standard color wheel while at the same time the net intensity
increases monotonically as the gray value goes from 0 to 1.
D A Green (2011) http://arxiv.org/abs/1108.5083
`start` defines the starting point along the color wheel in radians.
`cycles` defines how many color wheel cycles span the palette range.
Larger values of `saturation` produce more saturated color; saturation > 1
may lead to clipping of the individual RGB components and to intensity
becoming non-monotonic. The palette is also affected by `set palette gamma`.
The default values are
set palette cubehelix start 0.5 cycles -1.5 saturation 1
set palette gamma 1.5
?commands set palette file
?set palette file
?palette file
`set palette file` is basically a `set palette defined (<gradient>)` where
<gradient> is read from a datafile. Either 4 columns (gray,R,G,B) or
just three columns (R,G,B) have to be selected via the `using` data file
modifier. In the three column case, the line number will be used as gray.
The gray range is automatically rescaled to [0,1]. The file is read as a
normal data file, so all datafile modifiers can be used.
Please note, that `R` might actually be e.g. `H` if HSV color space is
selected.
As usual <filename> may be `'-'` which means that the data follow the command
inline and are terminated by a single `e` on a line of its own.
Use `show palette gradient` to display the gradient.
Examples:
Read in a palette of RGB triples each in range [0,255]:
set palette file 'some-palette' using ($1/255):($2/255):($3/255)
Equidistant rainbow (blue-green-yellow-red) palette:
set palette model RGB file "-"
0 0 1
0 1 0
1 1 0
1 0 0
e
Binary palette files are supported as well, see `binary general`. Example:
put 64 triplets of R,G,B doubles into file palette.bin and load it by
set palette file "palette.bin" binary record=64 using 1:2:3
?commands set palette gamma-correction
?set palette gamma-correction
?palette gamma-correction
?gamma-correction
For gray mappings gamma correction can be turned on by `set palette gamma
<gamma>`. <gamma> defaults to 1.5 which is quite suitable for most
terminals.
The gamma correction is applied to the cubehelix color palette family, but not
to other palette coloring schemes. However, you may easily implement gamma
correction for explicit color functions.
Example:
set palette model RGB
set palette functions gray**0.64, gray**0.67, gray**0.70
To use gamma correction with interpolated gradients specify intermediate
gray values with appropriate colors. Instead of
set palette defined ( 0 0 0 0, 1 1 1 1 )
use e.g.
set palette defined ( 0 0 0 0, 0.5 .73 .73 .73, 1 1 1 1 )
or even more intermediate points until the linear interpolation fits the
"gamma corrected" interpolation well enough.
?commands set palette postscript
?set palette postscript
In order to reduce the size of postscript files, the gray value and not all
three calculated r,g,b values are written to the file. Therefore the
analytical formulae are coded directly in the postscript language as a header
just before the pm3d drawing, see /g and /cF definitions. Usually, it makes
sense to write therein definitions of only the 3 formulae used. But for
multiplot or any other reason you may want to manually edit the
transformations directly in the postscript file. This is the default option
`nops_allcF`. Using the option `ps_allcF` writes postscript definitions of
all formulae. This you may find interesting if you want to edit the
postscript file in order to have different palettes for different surfaces
in one graph. Well, you can achieve this functionality by `multiplot` with
fixed `origin` and `size`.
If you are writing a pm3d surface to a postscript file, it may be possible to
reduce the file size by up to 50% by the enclosed awk script
`pm3dCompress.awk`. If the data lies on a rectangular grid, even greater
compression may be possible using the script `pm3dConvertToImage.awk`.
Usage:
awk -f pm3dCompress.awk thefile.ps >smallerfile.ps
awk -f pm3dConvertToImage.awk thefile.ps >smallerfile.ps
?commands set pointintervalbox
?set pointintervalbox
?pointintervalbox
The `pointinterval` and `pointnumber` properties of a line type are used only
in plot style `linespoints`. A negative value of pointinterval or pointnumber,
e.g. -N, means that before the selected set of point symbols are drawn a box
(actually circle) behind each point symbol is blanked out by filling with the
background color. The command `set pointintervalbox` controls the radius of
this blanked-out region. It is a multiplier for the default radius, which is
equal to the point size.
?commands set pointsize
?commands show pointsize
?set pointsize
?show pointsize
?pointsize
The `set pointsize` command scales the size of the points used in plots.
Syntax:
set pointsize <multiplier>
show pointsize
The default is a multiplier of 1.0. Larger pointsizes may be useful to
make points more visible in bitmapped graphics.
The pointsize of a single plot may be changed on the `plot` command.
See `plot with` for details.
Please note that the pointsize setting is not supported by all terminal
types.
?commands set polar
?commands unset polar
?commands show polar
?set polar
?unset polar
?show polar
?polar
?nopolar
The `set polar` command changes the meaning of the plot from rectangular
coordinates to polar coordinates.
Syntax:
set polar
unset polar
show polar
In polar coordinates, the dummy variable (t) represents an angle theta.
The default range of t is [0:2*pi], or [0:360] if degree units have been
selected (see `set angles`).
The command `unset polar` changes the meaning of the plot back to the default
rectangular coordinate system.
The `set polar` command is not supported for `splot`s. See the `set mapping`
command for similar functionality for `splot`s.
While in polar coordinates the meaning of an expression in t is really
r = f(t), where t is an angle of rotation. The trange controls the domain
(the angle) of the function. The r, x and y ranges control the extent of the
graph in the x and y directions. Each of these ranges, as well as the
rrange, may be autoscaled or set explicitly. For details, see `set rrange`
and `set xrange`.
Example:
set polar
plot t*sin(t)
set trange [-2*pi:2*pi]
set rrange [0:3]
plot t*sin(t)
The first `plot` uses the default polar angular domain of 0 to 2*pi. The
radius and the size of the graph are scaled automatically. The second `plot`
expands the domain, and restricts the size of the graph to the area within
3 units of the origin. This has the effect of limiting x and y to [-3:3].
By default polar plots are oriented such that theta=0 is at the far right,
with theta increasing counterclockwise. You can change both the origin and
the sense explicitly. See `set theta`.
You may want to `set size square` to have `gnuplot` try to make the aspect
ratio equal to unity, so that circles look circular. Tic marks around the
perimeter can be specified using `set ttics`.
See also
polar demos (polar.dem)
and
polar data plot (poldat.dem).
?commands set print
?commands show print
?set print
?show print
The `set print` command redirects the output of the `print` command to a file.
Syntax:
set print
set print "-"
set print "<filename>" [append]
set print "|<shell_command>"
set print $datablock [append]
`set print` with no parameters restores output to <STDERR>. The <filename>
"-" means <STDOUT>. The `append` flag causes the file to be opened in append
mode. A <filename> starting with "|" is opened as a pipe to the
<shell_command> on platforms that support piping.
The destination for `print` commands can also be a named data block. Data
block names start with '$', see also `inline data`.
?commands set psdir
?commands show psdir
?set psdir
?show psdir
?psdir
The `set psdir <directory>` command controls the search path used by the
postscript terminal to find prologue.ps and character encoding files.
You can use this mechanism to switch between different sets of
locally-customized prolog files.
The search order is
1) The directory specified by `set psdir`, if any
2) The directory specified by environmental variable GNUPLOT_PS_DIR
3) A built-in header or one from the default system directory
4) Directories set by `set loadpath`
?commands set raxis
?raxis
?set raxis
?unset raxis
The commands `set raxis` and `unset raxis` toggle whether the polar axis
is drawn separately from grid lines and the x axis. If the minimum of the
current rrange is non-zero (and not autoscaled), then a white circle is drawn
at the center of the polar plot to indicate that the plot lines and axes do
not reach 0. The axis line is drawn using the same line type as the plot
border. See `polar`, `rrange`, `rtics`, `rlabel`, `set grid`.
?commands set rgbmax
?set rgbmax
?rgbmax
?unset rgbmax
Syntax:
set rgbmax {1.0 | 255}
unset rgbmax
The red/green/blue color components of an rgbimage plot are by default
interpreted as integers in the range [0:255]. `set rgbmax 1.0` tells the
program that data values used to generate the color components of a plot
with `rgbimage` or `rgbalpha` are floating point values in the range [0:1].
`unset rgbmax` returns to the default integer range [0:255].
Warning: This command is EXPERIMENTAL. Details may change.
In particular, future gnuplot versions may implement rgbmax as a per-file
or per-plot property rather than a global setting.
?commands set rlabel
?rlabel
?set rlabel
?unset rlabel
This command places a label above the r axis. The label will be drawn whether
or not the plot is in polar mode. See `set xlabel` for additional keywords.
?commands set rmargin
?set rmargin
?rmargin
The command `set rmargin` sets the size of the right margin.
Please see `set margin` for details.
?commands set rrange
?commands show rrange
?set rrange
?show rrange
?rrange
The `set rrange` command sets the range of the radial coordinate for a graph
in polar mode. This has the effect of setting both xrange and yrange as well.
The resulting xrange and yrange are both [-(rmax-rmin) : +(rmax-rmin)].
However if you later change the x or y range, for example by zooming, this does
not change rrange, so data points continue to be clipped against rrange.
Unlike other axes, autoscaling the raxis always results in rmin = 0.
The `reverse` autoscaling flag is ignored.
Note: Setting a negative value for rmin may produce unexpected results.
?commands set rtics
?commands show rtics
?set rtics
?show rtics
?rtics
The `set rtics` command places tics along the polar axis. The tics and labels
are drawn to the right of the origin. The `mirror` keyword causes them to be
drawn also to the left of the origin. See `polar`, `set xtics`, and
`set mxtics` for discussion of keywords.
?commands set samples
?commands show samples
?set samples
?show samples
?samples
The default sampling rate of functions, or for interpolating data, may be
changed by the `set samples` command. To change the sampling range for a
particular plot, see `plot sampling`.
Syntax:
set samples <samples_1> {,<samples_2>}
show samples
By default, sampling is set to 100 points. A higher sampling rate will
produce more accurate plots, but will take longer. This parameter has no
effect on data file plotting unless one of the interpolation/approximation
options is used. See `plot smooth` re 2D data and `set cntrparam` and
`set dgrid3d` re 3D data.
When a 2D graph is being done, only the value of <samples_1> is relevant.
When a surface plot is being done without the removal of hidden lines, the
value of samples specifies the number of samples that are to be evaluated for
the isolines. Each iso-v line will have <sample_1> samples and each iso-u
line will have <sample_2> samples. If you only specify <samples_1>,
<samples_2> will be set to the same value as <samples_1>. See also
`set isosamples`.
?commands set size
?commands show size
?set size
?show size
?size
?aspect ratio
?set size square
?set size ratio
?ratio
?square
Syntax:
set size {{no}square | ratio <r> | noratio} {<xscale>,<yscale>}
show size
The <xscale> and <yscale> values are scale factors for the size of the plot,
which includes the graph, labels, and margins.
Important note:
In earlier versions of gnuplot, some terminal types used the values from
`set size` to control also the size of the output canvas; others did not.
Almost all terminals now follow the following convention:
`set term <terminal_type> size <XX>, <YY>` controls the size of the output
file, or `canvas`. Please see individual terminal documentation for allowed
values of the size parameters. By default, the plot will fill this canvas.
`set size <XX>, <YY>` scales the plot itself relative to the size of the
canvas. Scale values less than 1 will cause the plot to not fill the entire
canvas. Scale values larger than 1 will cause only a portion of the plot to
fit on the canvas. Please be aware that setting scale values larger than 1
may cause problems on some terminal types.
`ratio` causes `gnuplot` to try to create a graph with an aspect ratio of <r>
(the ratio of the y-axis length to the x-axis length) within the portion of
the plot specified by <xscale> and <yscale>.
The meaning of a negative value for <r> is different. If <r>=-1, gnuplot
tries to set the scales so that the unit has the same length on both the x
and y axes. This is the 2D equivalent to the 3D command `set view equal xy`.
If <r>=-2, the unit on y has twice the length of the unit on x, and so on.
The success of `gnuplot` in producing the requested aspect ratio depends on
the terminal selected. The graph area will be the largest rectangle of
aspect ratio <r> that will fit into the specified portion of the output
(leaving adequate margins, of course).
`set size square` is a synonym for `set size ratio 1`.
Both `noratio` and `nosquare` return the graph to the default aspect ratio
of the terminal, but do not return <xscale> or <yscale> to their default
values (1.0).
`ratio` and `square` have no effect on 3D plots, but do affect 3D projections
created using `set view map`. See also `set view equal`, which forces
the x and y axes of a 3D onto the same scale.
Examples:
To set the size so that the plot fills the available canvas:
set size 1,1
To make the graph half size and square use:
set size square 0.5,0.5
To make the graph twice as high as wide use:
set size ratio 2
?set style
?show style
?unset style
Default plotting styles are chosen with the `set style data` and
`set style function` commands. See `plot with` for information about how to
override the default plotting style for individual functions and data sets.
See `plotting styles` or `plot with` for a complete list of styles.
Syntax:
set style function <style>
set style data <style>
show style function
show style data
Default styles for specific plotting elements may also be set.
Syntax:
set style arrow <n> <arrowstyle>
set style boxplot <boxplot style options>
set style circle radius <size> {clip|noclip}
set style ellipse size <size> units {xy|xx|yy} {clip|noclip}
set style fill <fillstyle>
set style histogram <histogram style options>
set style line <n> <linestyle>
set style rectangle <object options> <linestyle> <fillstyle>
set style textbox {opaque|transparent} {{no}border} {fillcolor}
?commands set style arrow
?commands unset style arrow
?commands show style arrow
?set style arrow
?unset style arrow
?show style arrow
?arrowstyle
Each terminal has a default set of arrow and point types, which can be seen
by using the command `test`. `set style arrow` defines a set of arrow types
and widths and point types and sizes so that you can refer to them later by
an index instead of repeating all the information at each invocation.
Syntax:
set style arrow <index> default
set style arrow <index> {nohead | head | heads}
{size <length>,<angle>{,<backangle>} {fixed}}
{filled | empty | nofilled | noborder}
{front | back}
{ {linestyle | ls <line_style>}
| {linetype | lt <line_type>}
{linewidth | lw <line_width}
{linecolor | lc <colorspec>}
{dashtype | dt <dashtype>} }
unset style arrow
show style arrow
<index> is an integer that identifies the arrowstyle.
If `default` is given all arrow style parameters are set to their default
values.
If the linestyle <index> already exists, only the given parameters are
changed while all others are preserved. If not, all undefined values are
set to the default values.
Specifying `nohead` produces arrows drawn without a head---a line segment.
This gives you yet another way to draw a line segment on the plot. By
default, arrows have one head. Specifying `heads` draws arrow heads on both
ends of the line.
Head size can be controlled by `size <length>,<angle>` or
`size <length>,<angle>,<backangle>`, where `<length>` defines length of each
branch of the arrow head and `<angle>` the angle (in degrees) they make with
the arrow. `<Length>` is in x-axis units; this can be changed by `first`,
`second`, `graph`, `screen`, or `character` before the <length>; see
`coordinates` for details.
By default the size of the arrow head is reduced for very short arrows.
This can be disabled using the `fixed` keyword after the `size` command.
`<backangle>` is the angle (in degrees) the back branches make with the arrow
(in the same direction as `<angle>`). It is ignored if the style is `nofilled`.
Specifying `filled` produces filled arrow heads with a border line around the
arrow head. Specifying `noborder` produces filled arrow heads with no border.
In this case the tip of the arrow head lies exactly on the endpoint of the
vector and the arrow head is slightly smaller overall. Dashed arrows should
always use `noborder`, since a dashed border is ugly.
Not all terminals support filled arrow heads.
The line style may be selected from a user-defined list of line styles
(see `set style line`) or may be defined here by providing values for
`<line_type>` (an index from the default list of styles) and/or
`<line_width>` (which is a multiplier for the default width).
Note, however, that if a user-defined line style has been selected, its
properties (type and width) cannot be altered merely by issuing another
`set style arrow` command with the appropriate index and `lt` or `lw`.
If `front` is given, the arrows are written on top of the graphed data. If
`back` is given (the default), the arrow is written underneath the graphed
data. Using `front` will prevent a arrow from being obscured by dense data.
Examples:
To draw an arrow without an arrow head and double width, use:
set style arrow 1 nohead lw 2
set arrow arrowstyle 1
See also `set arrow` for further examples.
?commands set style boxplot
?commands unset style boxplot
?commands show style boxplot
?set style boxplot
?unset style boxplot
?show style boxplot
The `set style boxplot` command allows you to change the layout of plots
created using the `boxplot` plot style.
Syntax:
set style boxplot {range <r> | fraction <f>}
{{no}outliers} {pointtype <p>}
{candlesticks | financebars}
{separation <x>}
{labels off | auto | x | x2}
{sorted | unsorted}
The box in the boxplot always spans the range of values from the first
quartile to the third quartile of the data points. The limit of the whiskers
that extend from the box can be controlled in two different ways. By default
the whiskers extend from each end of the box for a range equal to 1.5 times
the interquartile range (i.e. the vertical height of the box proper).
Each whisker is truncated back toward the median so that it terminates at a
y value belonging to some point in the data set. Since there may be no point
whose value is exactly 1.5 times the interquartile distance, the whisker may
be shorter than its nominal range. This default corresponds to
set style boxplot range 1.5
Alternatively, you can specify the fraction of the total number of points
that the whiskers should span. In this case the range is extended
symmetrically from the median value until it encompasses the requested fraction
of the data set. Here again each whisker is constrained to end at a point in
the data set. To span 95% of the points in the set
set style boxplot fraction 0.95
Any points that lie outside the range of the whiskers are considered outliers.
By default these are drawn as individual circles (pointtype 7). The option
`nooutliers` disables this.
By default boxplots are drawn in a style similar to candlesticks, but you have
the option of using instead a style similar to finance bars.
If the using specification for a boxplot contains a fourth column, the values
in that column will be interpreted as the discrete leveles of a factor
variable. In this case more than one boxplots may be drawn, as many as the
number of levels of the factor variable. These boxplots will be drawn next to
each other, the distance between them is 1.0 by default (in x-axis units).
This distance can be changed by the option `separation`.
The `labels` option governs how and where these boxplots (each representing a
part of the dataset) are labeled. By default the value of the factor is put
as a tick label on the horizontal axis -- x or x2, depending on which one is
used for the plot itself. This setting corresponds to option `labels auto`.
The labels can be forced to use either of the x or x2 axes -- options
`labels x` and `labels x2`, respectively --, or they can be turned off
altogether with the option `labels off`.
By default the boxplots corresponding to different levels of the factor
variable are not sorted; they will be drawn in the same order the levels are
encountered in the data file. This behavior corresponds to the `unsorted`
option. If the `sorted` option is active, the levels are first sorted
alphabetically, and the boxplots are drawn in the sorted order.
The `separation`, `labels`, `sorted` and `unsorted` option only have an effect
if a fourth column is given the plot specification.
See `boxplot`, `candlesticks`, `financebars`.
?commands set style data
?commands show style data
?set style data
?show style data
?data style
The `set style data` command changes the default plotting style for data
plots.
Syntax:
set style data <plotting-style>
show style data
See `plotting styles` for the choices.
`show style data` shows the current default data plotting style.
?commands set style fill
?commands show style fill
?set style fill
?show style fill
?fillstyle
The `set style fill` command is used to set the default style of the plot
elements in plots with boxes, histograms, candlesticks and filledcurves.
This default can be superseded by fillstyles attached to individual plots.
See also 'set style rectangle'.
Syntax:
set style fill {empty
| {transparent} solid {<density>}
| {transparent} pattern {<n>}}
{border {lt} {lc <colorspec>} | noborder}
The default fillstyle is `empty`.
The `solid` option causes filling with a solid color, if the terminal
supports that. The <density> parameter specifies the intensity of the
fill color. At a <density> of 0.0, the box is empty, at <density> of 1.0,
the inner area is of the same color as the current linetype.
Some terminal types can vary the density continuously; others implement
only a few levels of partial fill. If no <density> parameter is given,
it defaults to 1.
The `pattern` option causes filling to be done with a fill pattern supplied
by the terminal driver. The kind and number of available fill patterns
depend on the terminal driver. If multiple datasets using filled boxes are
plotted, the pattern cycles through all available pattern types, starting
from pattern <n>, much as the line type cycles for multiple line plots.
The `empty` option causes filled boxes not to be filled. This is the default.
?fillcolor
?fc
Fill color (`fillcolor <colorspec>`) is distinct from fill style. I.e. plot
elements or objects can share a fillstyle while retaining separate colors.
In most places where a fillstyle is accepted you can also specify a fill color.
Fillcolor may be abbreviated `fc`.
Otherwise the fill color is take from the current linetype.
Example:
plot FOO with boxes fillstyle solid 1.0 fillcolor "cyan"
?commands set style fill border
?set style fill border
?fillstyle border
The bare keyword `border` causes the filled object to be surrounded by a
solid line of the current linetype and color. You can change the color of
this line by adding either a linetype or a linecolor.
`noborder` specifies that no bounding line is drawn.
Examples:
# Half-intensity fill, full intensity border in same color
set style fill solid 0.5 border
# Half-transparent fill, solid black border (linetype -1)
set style fill transparent solid 0.5 border -1
# Pattern fill in current color, border using color of linetype 5
plot ... with boxes fillstyle pattern 2 border lt 5
# Fill area in cyan, border in blue
plot ... with boxes fillcolor "cyan" fs solid border linecolor "blue"
Note: The border property of a fill style only affects plots drawn
`with filledcurves` in the default mode (closed curve).
?commands set style fill transparent
?set style fill transparent
?fillstyle transparent
?transparent
Some terminals support the attribute `transparent` for filled areas.
In the case of transparent solid fill areas, the `density` parameter is
interpreted as an alpha value; that is, density 0 is fully transparent,
density 1 is fully opaque. In the case of transparent pattern fill, the
background of the pattern is either fully transparent or fully opaque.
Note that there may be additional limitations on the creation or viewing of
graphs containing transparent fill areas. For example, the png terminal can
only use transparent fill if the "truecolor" option is set. Some pdf viewers
may not correctly display the fill areas even if they are correctly described
in the pdf file. Ghostscript/gv does not correctly display pattern-fill areas
even though actual PostScript printers generally have no problem.
?commands set style function
?commands show style function
?set style function
?show style function
The `set style function` command changes the default plotting style for
function plots (e.g. lines, points, filledcurves). See `plotting styles`.
Syntax:
set style function <plotting-style>
show style function
?commands set style increment
?commands show style increment
?set style increment
?show style increment
`Note`: This command has been deprecated. Instead please use the newer
command `set linetype`, which redefines the linetypes themselves rather
than searching for a suitable temporary line style to substitute.
See `set linetype`
Syntax:
set style increment {default|userstyles}
show style increment
By default, successive plots within the same graph will use successive
linetypes from the default set for the current terminal type.
However, choosing `set style increment user` allows you to step through
the user-defined line styles rather than through the default linetypes.
Example:
set style line 1 lw 2 lc rgb "gold"
set style line 2 lw 2 lc rgb "purple"
set style line 4 lw 1 lc rgb "sea-green"
set style increment user
plot f1(x), f2(x), f3(x), f4(x)
should plot functions f1, f2, f4 in your 3 newly defined line styles.
If a user-defined line style is not found then the corresponding default
linetype is used instead. E.g. in the example above, f3(x) will be plotted
using the default linetype 3.
?commands set style line
?commands unset style line
?commands show style line
?set style line
?unset style line
?show style line
?linestyle
?linewidth
Each terminal has a default set of line and point types, which can be seen
by using the command `test`. `set style line` defines a set of line types
and widths and point types and sizes so that you can refer to them later by
an index instead of repeating all the information at each invocation.
Syntax:
set style line <index> default
set style line <index> {{linetype | lt} <line_type> | <colorspec>}
{{linecolor | lc} <colorspec>}
{{linewidth | lw} <line_width>}
{{pointtype | pt} <point_type>}
{{pointsize | ps} <point_size>}
{{pointinterval | pi} <interval>}
{{pointnumber | pn} <max_symbols>}
{{dashtype | dt} <dashtype>}
{palette}
unset style line
show style line
`default` sets all line style parameters to those of the linetype with
that same index.
If the linestyle <index> already exists, only the given parameters are
changed while all others are preserved. If not, all undefined values are
set to the default values.
Line styles created by this mechanism do not replace the default linetype
styles; both may be used. Line styles are temporary. They are lost whenever
you execute a `reset` command. To redefine the linetype itself,
please see `set linetype`.
The line and point types default to the index value. The exact symbol that is
drawn for that index value may vary from one terminal type to another.
The line width and point size are multipliers for the current terminal's
default width and size (but note that <point_size> here is unaffected by
the multiplier given by the command`set pointsize`).
The `pointinterval` controls the spacing between points in a plot drawn with
style `linespoints`. The default is 0 (every point is drawn). For example,
`set style line N pi 3` defines a linestyle that uses pointtype N, pointsize
and linewidth equal to the current defaults for the terminal, and will draw
every 3rd point in plots using `with linespoints`. A negative value for the
interval is treated the same as a positive value, except that some terminals
will try to interrupt the line where it passes through the point symbol.
The `pointnumber` property is similar to `pointinterval` except that rather
than plotting every Nth point it limits the total number of points to N.
Not all terminals support the `linewidth` and `pointsize` features; if
not supported, the option will be ignored.
Terminal-independent colors may be assigned using either
`linecolor <colorspec>` or `linetype <colorspec>`, abbreviated `lc` or `lt`.
This requires giving a RGB color triple, a known palette color name,
a fractional index into the current palette, or a constant value from the
current mapping of the palette onto cbrange.
See `colors`, `colorspec`, `set palette`, `colornames`, `cbrange`.
`set style line <n> linetype <lt>` will set both a terminal-dependent dot/dash
pattern and color. The commands`set style line <n> linecolor <colorspec>` or
`set style line <n> linetype <colorspec>` will set a new line color while
leaving the existing dot-dash pattern unchanged.
In 3d mode (`splot` command), the special keyword `palette` is allowed as a
shorthand for "linetype palette z". The color value corresponds to the
z-value (elevation) of the splot, and varies smoothly along a line or surface.
Examples:
Suppose that the default lines for indices 1, 2, and 3 are red, green, and
blue, respectively, and the default point shapes for the same indices are a
square, a cross, and a triangle, respectively. Then
set style line 1 lt 2 lw 2 pt 3 ps 0.5
defines a new linestyle that is green and twice the default width and a new
pointstyle that is a half-sized triangle. The commands
set style function lines
plot f(x) lt 3, g(x) ls 1
will create a plot of f(x) using the default blue line and a plot of g(x)
using the user-defined wide green line. Similarly the commands
set style function linespoints
plot p(x) lt 1 pt 3, q(x) ls 1
will create a plot of p(x) using the default triangles connected by a red
line and q(x) using small triangles connected by a green line.
splot sin(sqrt(x*x+y*y))/sqrt(x*x+y*y) w l pal
creates a surface plot using smooth colors according to `palette`. Note,
that this works only on some terminals. See also `set palette`, `set pm3d`.
set style line 10 linetype 1 linecolor rgb "cyan"
will assign linestyle 10 to be a solid cyan line on any terminal that
supports rgb colors.
?commands set style circle
?commands unset style circle
?commands show style circle
?set style circle
?unset style circle
?show style circle
Syntax:
set style circle {radius {graph|screen} <R>}
{{no}wedge}
{clip|noclip}
This command sets the default radius used in plot style "with circles". It
applies to data plots with only 2 columns of data (x,y) and to function plots.
The default is "set style circle radius graph 0.02". `Nowedge` disables
drawing of the two radii that connect the ends of an arc to the center.
The default is `wedge`. This parameter has no effect on full circles. `Clip`
clips the circle at the plot boundaries, `noclip` disables this. Default is
`clip`.
?commands set style rectangle
?commands unset style rectangle
?commands show style rectangle
?set style rectangle
?unset style rectangle
?show style rectangle
Rectangles defined with the `set object` command can have individual styles.
However, if the object is not assigned a private style then it inherits a
default that is taken from the `set style rectangle` command.
Syntax:
set style rectangle {front|back} {lw|linewidth <lw>}
{fillcolor <colorspec>} {fs <fillstyle>}
See `colorspec` and `fillstyle`. `fillcolor` may be abbreviated as `fc`.
Examples:
set style rectangle back fc rgb "white" fs solid 1.0 border lt -1
set style rectangle fc linsestyle 3 fs pattern 2 noborder
The default values correspond to solid fill with the background color and a
black border.
?commands set style ellipse
?commands show style ellipse
?set style ellipse
?unset style ellipse
?show style ellipse
Syntax:
set style ellipse {units xx|xy|yy}
{size {graph|screen} <a>, {{graph|screen} <b>}}
{angle <angle>}
{clip|noclip}
This command governs whether the diameters of ellipses are interpreted in
the same units or not.
Default is `xy`, which means that the major diameter (first axis) of
ellipses will be interpreted in the same units as the x (or x2) axis,
while the minor (second) diameter in those of the y (or y2) axis.
In this mode the ratio of the ellipse axes depends on the scales of the
plot axes and aspect ratio of the plot. When set to `xx` or `yy`,
both axes of all ellipses will be interpreted in the same units.
This means that the ratio of the axes of the plotted ellipses will be
correct even after rotation, but either their vertical or horizontal extent
will not be correct.
This is a global setting that affects all ellipses, both those defined as
objects and those generated with the `plot` command, however, the value of
`units` can also be redefined on a per-plot and per-object basis.
It is also possible to set a default size for ellipses with the `size`
keyword. This default size applies to data plots with only
2 columns of data (x,y) and to function plots. The two values are
interpreted as the major and minor diameters (as opposed to semi-major
and semi-minor axes) of the ellipse.
The default is "set style ellipse size graph 0.05,0.03".
Last, but not least it is possible to set the default orientation with the
`angle` keyword. The orientation, which is defined as the angle between the
major axis of the ellipse and the plot's x axis, must be given in degrees.
`Clip` clips the ellipse at the plot boundaries, `noclip` disables this.
Default is `clip`.
For defining ellipse objects, see `set object ellipse`;
for the 2D plot style, see `ellipses`.
?commands set style textbox
?commands show style textbox
?set style textbox
?unset style textbox
?show style textbox
?textbox
?boxed
Syntax: set style textbox {opaque|transparent}
{{no}border {<bordercolor>}}{linewidth <lw>}
{fillcolor <color>}
{margins <xmargin>,<ymargin>}
This command controls the appearance of labels with the attribute 'boxed'.
Terminal types that do not support boxed text will ignore this style.
Note: The current implementation is experimental; details may change.
Implementation for some terminals (svg, latex) is incomplete.
Most terminals cannot place a box correctly around rotated text.
?commands set surface
?commands unset surface
?commands show surface
?set surface
?unset surface
?show surface
?surface
?nosurface
The `set surface` command is only relevant for 3D plots (`splot`).
Syntax:
set surface {implicit|explicit}
unset surface
show surface
`unset surface` will cause `splot` to not draw points or lines corresponding
to any of the function or data file points. This is mainly useful for drawing
only contour lines rather than the surface they were derived from. Contours
may still be drawn on the surface, depending on the `set contour` option.
To turn off the surface for an individual function or data file while leaving
others active, use the `nosurface` keyword in the `splot` command.
The combination `unset surface; set contour base` is useful for displaying
contours on the grid base. See also `set contour`.
If a 3D data set is recognizable as a mesh (grid) then by default the program
implicitly treats the plot style `with lines` as requesting a gridded surface.
See `grid_data`. The command `set surface explicit` suppresses this expansion,
plotting only the individual lines described by separate blocks of data in the
input file. A gridded surface can still be plotted by explicitly requesting
splot `with surface`.
?commands set table
?set table
?table
When `table` mode is enabled, `plot` and `splot` commands print out a
multicolumn text table of values
X Y {Z} <flag>
rather than creating an actual plot on the current terminal. The flag character
is "i" if the point is in the active range, "o" if it is out-of-range, or "u"
if it is undefined. The data format is determined by the format of the axis
tickmarks (see `set format`). Columns are by default separated by whitespace.
See `with table` for a description of how to write a table to a csv file.
This can be useful if you want to generate contours and then save them for
further use. The same method can be used to save interpolated data
(see `set samples` and `set dgrid3d`).
Syntax:
set table {"outfile" | $datablock} {append}
{separator {space|tab|comma|"<char>"}
plot <whatever>
unset table
Subsequent tabular output is written to "outfile", if specified, otherwise it
is written to stdout or other current value of `set output`. If `outfile`
exists it will be replaced unless the `append` keyword is given.
Alternatively, tabular output can be redirected to a named data block.
Data block names start with '$', see also `inline data`. You must explicitly
`unset table` in order to go back to normal plotting on the current terminal.
See also `plot with table`.
?plot with table
?with table
To avoid any style-dependent processing of the input data being tabulated
(smoothing, errorbar expansion, secondary range checking, etc), or to increase
the number of columns that can be tabulated, use the keyword "table" instead of
a normal plot style. In this case the output does not contain an extra, last,
column of flags `i`, `o`, `u` indicated inrange/outrange/undefined.
The destination for output must first be specified with `set table <where>`.
For example
set table $DATABLOCK1
plot <file> using 1:2:3:4:($5+$6):(func($7)):8:9:10 with table
Because there is no actual plot style in this case the columns do not
correspond to specific axes. Therefore xrange, yrange, etc are ignored.
If a `using` term evaluates to a string, the string is tabulated.
Numerical data is always written with format %g. If you want some other format
use sprintf or gprintf to create a formatted string.
plot <file> using ("File 1"):1:2:3 with table
plot <file> using (sprintf("%4.2f",$1)) : (sprintf("%4.2f",$3)) with table
To create a csv file use
set table "tab.csv" separator comma
plot <foo> using 1:2:3:4 with table
?commands set terminal
?commands show terminal
?set terminal
?set term
?show terminal
?show term
?set terminal push
?set term push
?terminal push
?term push
?push
?set terminal pop
?set term pop
?terminal pop
?term pop
?pop
`gnuplot` supports many different graphics devices. Use `set terminal` to
tell `gnuplot` what kind of output to generate. Use `set output` to redirect
that output to a file or device.
Syntax:
set terminal {<terminal-type> | push | pop}
show terminal
If <terminal-type> is omitted, `gnuplot` will list the available terminal
types. <terminal-type> may be abbreviated.
If both `set terminal` and `set output` are used together, it is safest to
give `set terminal` first, because some terminals set a flag which is needed
in some operating systems.
Some terminals have many additional options.
The options used by a previous invocation `set term <term> <options>` of a
given `<term>` are remembered, thus subsequent `set term <term>` does
not reset them. This helps in printing, for instance, when switching
among different terminals---previous options don't have to be repeated.
The command `set term push` remembers the current terminal including its
settings while `set term pop` restores it. This is equivalent to `save term`
and `load term`, but without accessing the filesystem. Therefore they can be
used to achieve platform independent restoring of the terminal after printing,
for instance. After gnuplot's startup, the default terminal or that from
`startup` file is pushed automatically. Therefore portable scripts can rely
that `set term pop` restores the default terminal on a given platform unless
another terminal has been pushed explicitly.
For more information, see the `complete list of terminals`.
?commands set termoption
?set termoption
?termoption
The `set termoption` command allows you to change the behaviour of the
current terminal without requiring a new `set terminal` command. Only one
option can be changed per command, and only a small number of options can
be changed this way. Currently the only options accepted are
set termoption {no}enhanced
set termoption font "<fontname>{,<fontsize>}"
set termoption fontscale <scale>
set termoption {linewidth <lw>}{lw <lw>}
?commands set theta
?set theta
?unset theta
?theta
Polar coordinate plots are by default oriented such that theta = 0 is on the
right side of the plot, with theta increasing as you proceed counterclockwise
so that theta = 90 degrees is at the top. `set theta` allows you to change
the origin and direction of the polar angular coordinate theta.
set theta {right|top|left|bottom}
set theta {clockwise|cw|counterclockwise|ccw}
`unset theta` restores the default state "set theta right ccw".
?commands set tics
?commands unset tics
?commands show tics
?set tics
?unset tics
?show tics
?tics
The `set tics` command controls the tic marks and labels on all axes at once.
The tics may be turned off with the `unset tics` command, and may be turned on
(the default state) with `set tics`. Fine control of tics on individual axes
is possible using the alternative commands `set xtics`, `set ztics`, etc.
Syntax:
set tics {axis | border} {{no}mirror}
{in | out} {front | back}
{{no}rotate {by <ang>}} {offset <offset> | nooffset}
{left | right | center | autojustify}
{format "formatstring"} {font "name{,<size>}"} {{no}enhanced}
{ textcolor <colorspec> }
set tics scale {default | <major> {,<minor>}}
unset tics
show tics
The options can be applied to a single axis (x, y, z, x2, y2, cb), e.g.
set xtics rotate by -90
unset cbtics
All tic marks are drawn using the same line properties as the plot border
(see `set border`).
Set tics `back` or `front` applies to all axes at once, but only for 2D plots
(not splot). It controls whether the tics are placed behind or in front of
the plot elements, in the case that there is overlap.
`axis` or `border` tells `gnuplot` to put the tics (both the tics themselves
and the accompanying labels) along the axis or the border, respectively. If
the axis is very close to the border, the `axis` option will move the
tic labels to outside the border in case the border is printed (see
`set border`). The relevant margin settings will usually be sized badly by
the automatic layout algorithm in this case.
`mirror` tells `gnuplot` to put unlabeled tics at the same positions on the
opposite border. `nomirror` does what you think it does.
`in` and `out` change the tic marks to be drawn inwards or outwards.
`set tics scale` controls the size of the tic marks. The first value <major>
controls the auto-generated or user-specified major tics (level 0). The
second value controls the auto-generated or user-specified minor tics
(level 1). <major> defaults to 1.0, <minor> defaults to <major>/2.
Additional values control the size of user-specified tics with level 2, 3, ...
Default tic sizes are restored by `set tics scale default`.
`rotate` asks `gnuplot` to rotate the text through 90 degrees, which will be
done if the terminal driver in use supports text rotation. `norotate`
cancels this. `rotate by <ang>` asks for rotation by <ang> degrees, supported
by some terminal types.
The defaults are `border mirror norotate` for tics on the x and y axes, and
`border nomirror norotate` for tics on the x2 and y2 axes. For the z axis,
the default is `nomirror`.
The <offset> is specified by either x,y or x,y,z, and may be preceded by
`first`, `second`, `graph`, `screen`, or `character` to select the
coordinate system. <offset> is the offset of the tics texts from their
default positions, while the default coordinate system is `character`.
See `coordinates` for details. `nooffset` switches off the offset.
By default, tic labels are justified automatically depending on the axis and
rotation angle to produce aesthetically pleasing results. If this is not
desired, justification can be overridden with an explicit `left`, `right` or
`center` keyword. `autojustify` restores the default behavior.
`set tics` with no options restores mirrored, inward-facing tic marks for
the primary axes. All other settings are retained.
See also `set xtics` for more control of major (labeled) tic marks and
`set mxtics` for control of minor tic marks. These commands provide control
of each axis independently.
?commands set ticslevel
?commands show ticslevel
?set ticslevel
?show ticslevel
?ticslevel
Deprecated. See `set xyplane`.
?commands set ticscale
?commands show ticscale
?set ticscale
?show ticscale
?ticscale
The `set ticscale` command is deprecated, use `set tics scale` instead.
?commands set timestamp
?commands unset timestamp
?commands show timestamp
?set timestamp
?unset timestamp
?show timestamp
?timestamp
?notimestamp
The command `set timestamp` places the current time and date in the plot margin.
Syntax:
set timestamp {"<format>"} {top|bottom} {{no}rotate}
{offset <xoff>{,<yoff>}} {font "<fontspec>"}
{textcolor <colorspec>}
unset timestamp
show timestamp
The format string is used to write the date and time. Its default value is
what asctime() uses: "%a %b %d %H:%M:%S %Y" (weekday, month name, day of the
month, hours, minutes, seconds, four-digit year). With `top` or `bottom` you
can place the timestamp along the top left or bottom left margin
(default: bottom). `rotate` writes the timestamp vertically. The constants
<xoff> and <yoff> are offsets that let you adjust the position more finely.
<font> is used to specify the font with which the time is to be written.
The abbreviation `time` may be used in place of `timestamp`.
Example:
set timestamp "%d/%m/%y %H:%M" offset 80,-2 font "Helvetica"
See `set timefmt` for more information about time format strings.
?commands set timefmt
?commands show timefmt
?set timefmt
?show timefmt
?timefmt
This command applies to timeseries where data are composed of dates/times.
It has no meaning unless the command `set *data time` is given also.
Syntax:
set timefmt "<format string>"
show timefmt
The string argument tells `gnuplot` how to read timedata from the datafile.
The valid formats are:
Format Explanation
%d day of the month, 1--31
%m month of the year, 1--12
%y year, 0--99
%Y year, 4-digit
%j day of the year, 1--365
%H hour, 0--24
%M minute, 0--60
%s seconds since the Unix epoch (1970-01-01, 00:00 UTC)
%S second, integer 0--60 on output, (double) on input
%b three-character abbreviation of the name of the month
%B name of the month
Any character is allowed in the string, but must match exactly. \t (tab) is
recognized. Backslash-octals (\nnn) are converted to char. If there is no
separating character between the time/date elements, then %d, %m, %y, %H, %M
and %S read two digits each. If a decimal point immediately follows the field
read by %S, the decimal and any following digits are interpreted as a
fractional second. %Y reads four digits. %j reads three digits.
%b requires three characters, and %B requires as many as it needs.
Spaces are treated slightly differently. A space in the string stands for
zero or more whitespace characters in the file. That is, "%H %M" can be used
to read "1220" and "12 20" as well as "12 20".
Each set of non-blank characters in the timedata counts as one column in the
`using n:n` specification. Thus `11:11 25/12/76 21.0` consists of three
columns. To avoid confusion, `gnuplot` requires that you provide a complete
`using` specification if your file contains timedata.
If the date format includes the day or month in words, the format string must
exclude this text. But it can still be printed with the "%a", "%A", "%b", or
"%B" specifier. `gnuplot` will determine the proper month and weekday from the
numerical values. See `set format` for more details about these and other
options for printing time data.
When reading two-digit years with %y, values 69-99 refer to the 20th century,
while values 00-68 refer to the 21st century. NB: This is in accordance with
the UNIX98 spec, but conventions vary widely and two-digit year values are
inherently ambiguous.
See also `set xdata` and `time/date` for more information.
Example:
set timefmt "%d/%m/%Y\t%H:%M"
tells `gnuplot` to read date and time separated by tab. (But look closely at
your data---what began as a tab may have been converted to spaces somewhere
along the line; the format string must match what is actually in the file.)
See also
time data demo.
?commands set title
?commands show title
?set title
?show title
?title
The `set title` command produces a plot title that is centered at the top of
the plot. `set title` is a special case of `set label`.
Syntax:
set title {"<title-text>"} {offset <offset>} {font "<font>{,<size>}"}
{{textcolor | tc} {<colorspec> | default}} {{no}enhanced}
show title
If <offset> is specified by either x,y or x,y,z the title is moved by the
given offset. It may be preceded by `first`, `second`, `graph`, `screen`,
or `character` to select the coordinate system. See `coordinates` for
details. By default, the `character` coordinate system is used. For
example, "`set title offset 0,-1`" will change only the y offset of the
title, moving the title down by roughly the height of one character. The
size of a character depends on both the font and the terminal.
<font> is used to specify the font with which the title is to be written;
the units of the font <size> depend upon which terminal is used.
`textcolor <colorspec>` changes the color of the text. <colorspec> can be a
linetype, an rgb color, or a palette mapping. See help for `colorspec` and
`palette`.
`noenhanced` requests that the title not be processed by the enhanced text
mode parser, even if enhanced text mode is currently active.
`set title` with no parameters clears the title.
See `syntax` for details about the processing of backslash sequences and
the distinction between single- and double-quotes.
?commands set tmargin
?set tmargin
?tmargin
The command `set tmargin` sets the size of the top margin.
Please see `set margin` for details.
?commands set trange
?commands show trange
?set trange
?show trange
?trange
The `set trange` command sets the parametric range used to compute x and y
values when in parametric or polar modes. Please see `set xrange` for
details.
?commands set ttics
?commands show ttics
?set ttics
?show ttics
?ttics
The `set ttics` command places tics around the perimeter of a polar plot.
This is the border if `set border polar` is enabled, otherwise the outermost
circle of the polar grid drawn at the rightmost ticmark along the r axis.
See `set grid`, `set rtics`. The angular position is always labeled in degrees.
The full perimeter can be labeled regardless of the current trange setting.
The desired range of the tic labels should be given as shown below.
Additional properties of the tic marks can be set. See `xtics`.
set ttics -180, 30, 180
set ttics add ("Theta = 0" 0)
set ttics font ":Italic" rotate
?commands set urange
?commands show urange
?set urange
?show urange
?urange
The `set urange` and `set vrange` commands set the parametric ranges used
to compute x, y, and z values when in `splot` parametric mode.
Please see `set xrange` for details.
?commands show variables
?show variables all
?show variables
The `show variables` command lists the current value of user-defined and
internal variables. Gnuplot internally defines variables whose names begin
with GPVAL_, MOUSE_, FIT_, and TERM_.
Syntax:
show variables # show variables that do not begin with GPVAL_
show variables all # show all variables including those beginning GPVAL_
show variables NAME # show only variables beginning with NAME
?show version
The `show version` command lists the version of gnuplot being run, its last
modification date, the copyright holders, and email addresses for the FAQ,
the gnuplot-info mailing list, and reporting bugs--in short, the information
listed on the screen when the program is invoked interactively.
Syntax:
show version {long}
When the `long` option is given, it also lists the operating system, the
compilation options used when `gnuplot` was installed, the location of the
help file, and (again) the useful email addresses.
?commands set view
?commands show view
?set view
?set view map
?show view
?view
The `set view` command sets the viewing angle for `splot`s. It controls how
the 3D coordinates of the plot are mapped into the 2D screen space. It
provides controls for both rotation and scaling of the plotted data, but
supports orthographic projections only. It supports both 3D projection or
orthogonal 2D projection into a 2D plot-like map.
Syntax:
set view <rot_x>{,{<rot_z>}{,{<scale>}{,<scale_z>}}}
set view map {scale <scale>}
set view {no}equal {xy|xyz}
set view azimuth <angle>
show view
where <rot_x> and <rot_z> control the rotation angles (in degrees) in a
virtual 3D coordinate system aligned with the screen such that initially
(that is, before the rotations are performed) the screen horizontal axis is
x, screen vertical axis is y, and the axis perpendicular to the screen is z.
The first rotation applied is <rot_x> around the x axis. The second rotation
applied is <rot_z> around the new z axis.
Command `set view map` is used to represent the drawing as a map. It is useful
for `contour` plots or 2D heatmaps using pm3d mode rather than `with image`.
In the latter case, take care that you properly use `zrange` and `cbrange` for
input data point filtering and color range scaling, respectively.
<rot_x> is bounded to the [0:180] range with a default of 60 degrees, while
<rot_z> is bounded to the [0:360] range with a default of 30 degrees.
<scale> controls the scaling of the entire `splot`, while <scale_z> scales
the z axis only. Both scales default to 1.0.
Examples:
set view 60, 30, 1, 1
set view ,,0.5
The first sets all the four default values. The second changes only scale,
to 0.5.
?set view azimuth
?view azimuth
?azimuth
set view azimuth <angle-in-degrees>
The setting of azimuth affects the orientation of the z axis in a 3D graph
(splot). At the default azimuth = 0 the z axis of the plot lies in the plane
orthogonal to the screen horizontal. I.e. the projection of the z axis lies
along the screen vertical. Non-zero azimuth rotates the plot about the line
of sight through the origin so that a projection of the z axis is no longer
vertical. When azimuth = 90 the z axis is horizontal rather than vertical.
?set view equal_axes
?set view equal xyz
?set view equal
?view equal_axes
?view equal xyz
?equal_axes
?equal xyz
The command `set view equal xy` forces the unit length of the x and y axes
to be on the same scale, and chooses that scale so that the plot will fit on
the page. The command `set view equal xyz` additionally sets the z axis
scale to match the x and y axes; however there is no guarantee that the
current z axis range will fit within the plot boundary.
By default all three axes are scaled independently to fill the available area.
See also `set xyplane`.
?commands set vrange
?commands show vrange
?set vrange
?show vrange
?vrange
The `set urange` and `set vrange` commands set the parametric ranges used
to compute x, y, and z values when in `splot` parametric mode.
Please see `set xrange` for details.
?commands set x2data
?commands show x2data
?set x2data
?show x2data
?x2data
The `set x2data` command sets data on the x2 (top) axis to timeseries
(dates/times). Please see `set xdata`.
?commands set x2dtics
?commands unset x2dtics
?commands show x2dtics
?set x2dtics
?unset x2dtics
?show x2dtics
?x2dtics
?nox2dtics
The `set x2dtics` command changes tics on the x2 (top) axis to days of the
week. Please see `set xdtics` for details.
?commands set x2label
?commands show x2label
?set x2label
?show x2label
?x2label
The `set x2label` command sets the label for the x2 (top) axis.
Please see `set xlabel`.
?commands set x2mtics
?commands unset x2mtics
?commands show x2mtics
?set x2mtics
?unset x2mtics
?show x2mtics
?x2mtics
?nox2mtics
The `set x2mtics` command changes tics on the x2 (top) axis to months of the
year. Please see `set xmtics` for details.
?commands set x2range
?commands show x2range
?set x2range
?show x2range
?x2range
The `set x2range` command sets the horizontal range that will be displayed on
the x2 (top) axis. See `set xrange` for the full set of command options.
See also `set link`.
?commands set x2tics
?commands unset x2tics
?commands show x2tics
?set x2tics
?unset x2tics
?show x2tics
?x2tics
?nox2tics
The `set x2tics` command controls major (labeled) tics on the x2 (top) axis.
Please see `set xtics` for details.
?commands set x2zeroaxis
?commands unset x2zeroaxis
?commands show x2zeroaxis
?set x2zeroaxis
?unset x2zeroaxis
?show x2zeroaxis
?x2zeroaxis
?nox2zeroaxis
The `set x2zeroaxis` command draws a line at the origin of the x2 (top) axis
(y2 = 0). For details, please see `set zeroaxis`.
?commands set xdata
?commands show xdata
?set xdata
?show xdata
?xdata
This command controls interpretation of data on the x axis.
An analogous command acts on each of the other axes.
Syntax:
set xdata time
show xdata
The same syntax applies to `ydata`, `zdata`, `x2data`, `y2data` and `cbdata`.
The `time` option signals that data represents a time/date in seconds.
The current version of gnuplot stores time to a millisecond precision.
If no option is specified, the data interpretation reverts to normal.
?commands set xdata time
?set xdata time
`set xdata time` indicates that the x coordinate represents a date or time to
millisecond precision. There is an analogous command `set ydata time`.
There are separate format mechanisms for interpretation of time data on input
and output. Input data is read from a file either by using the global
`timefmt` or by using the function timecolumn() as part of the plot command.
These input mechanisms also apply to using time values to set an axis range.
See `set timefmt`, `timecolumn`.
Example:
set xdata time
set timefmt "%d-%b-%Y"
set xrange ["01-Jan-2013" : "31-Dec-2014"]
plot DATA using 1:2
or
plot DATA using (timecolumn(1,"%d-%b-%Y")):2
For output, i.e. tick labels along that axis or coordinates output by mousing,
the function 'strftime' (type "man strftime" on unix to look it up) is used to
convert from the internal time in seconds to a string representation of a date.
`gnuplot` tries to figure out a reasonable format for this. You can customize
the format using either `set format x` or `set xtics format`.
See `time_specifiers` for a special set of time format specifiers.
See also `time/date` for more information.
?commands set xdtics
?commands unset xdtics
?commands show xdtics
?set xdtics
?unset xdtics
?show xdtics
?xdtics
?noxdtics
The `set xdtics` commands converts the x-axis tic marks to days of the week
where 0=Sun and 6=Sat. Overflows are converted modulo 7 to dates. `set
noxdtics` returns the labels to their default values. Similar commands do
the same things for the other axes.
Syntax:
set xdtics
unset xdtics
show xdtics
The same syntax applies to `ydtics`, `zdtics`, `x2dtics`, `y2dtics` and
`cbdtics`.
See also the `set format` command.
?commands set xlabel
?commands show xlabel
?set xlabel
?show xlabel
?xlabel
The `set xlabel` command sets the x axis label. Similar commands set labels
on the other axes.
Syntax:
set xlabel {"<label>"} {offset <offset>} {font "<font>{,<size>}"}
{textcolor <colorspec>} {{no}enhanced}
{rotate by <degrees> | rotate parallel | norotate}
show xlabel
The same syntax applies to `x2label`, `ylabel`, `y2label`, `zlabel` and
`cblabel`.
If <offset> is specified by either x,y or x,y,z the label is moved by the
given offset. It may be preceded by `first`, `second`, `graph`, `screen`,
or `character` to select the coordinate system. See `coordinates` for
details. By default, the `character` coordinate system is used. For
example, "`set xlabel offset -1,0`" will change only the x offset of the
title, moving the label roughly one character width to the left. The size
of a character depends on both the font and the terminal.
<font> is used to specify the font in which the label is written; the units
of the font <size> depend upon which terminal is used.
`noenhanced` requests that the label text not be processed by the enhanced text
mode parser, even if enhanced text mode is currently active.
To clear a label, put no options on the command line, e.g., "`set y2label`".
The default positions of the axis labels are as follows:
xlabel: The x-axis label is centered below the bottom of the plot.
ylabel: The y-axis label is centered to the left of the plot, defaulting to
either horizontal or vertical orientation depending on the terminal type.
zlabel: The z-axis label is centered along the z axis and placed in the space
above the grid level.
cblabel: The color box axis label is centered along the box and placed below
or to the right according to horizontal or vertical color box gradient.
y2label: The y2-axis label is placed to the right of the y2 axis. The
position is terminal-dependent in the same manner as is the y-axis label.
x2label: The x2-axis label is placed above the plot but below the title.
It is also possible to create an x2-axis label by using new-line
characters to make a multi-line plot title, e.g.,
set title "This is the title\n\nThis is the x2label"
Note that double quotes must be used. The same font will be used for both
lines, of course.
The orientation (rotation angle) of the x, x2, y and y2 axis labels in 2D plots
can be changed by specifying `rotate by <degrees>`. The orientation of the x
and y axis labels in 3D plots defaults to horizontal but can be changed to run
parallel to the axis by specifying `rotate parallel`.
If you are not satisfied with the default position of an axis label, use `set
label` instead--that command gives you much more control over where text is
placed.
Please see `syntax` for further information about backslash processing
and the difference between single- and double-quoted strings.
?commands set xmtics
?commands unset xmtics
?commands show xmtics
?set xmtics
?unset xmtics
?show xmtics
?xmtics
?noxmtics
The `set xmtics` command converts the x-axis tic marks to months of the
year where 1=Jan and 12=Dec. Overflows are converted modulo 12 to months.
The tics are returned to their default labels by `unset xmtics`. Similar
commands perform the same duties for the other axes.
Syntax:
set xmtics
unset xmtics
show xmtics
The same syntax applies to `x2mtics`, `ymtics`, `y2mtics`, `zmtics` and
`cbmtics`.
See also the `set format` command.
?commands set xrange
?commands show xrange
?set xrange
?show xrange
?writeback
?restore
?xrange
The `set xrange` command sets the horizontal range that will be displayed.
A similar command exists for each of the other axes, as well as for the
polar radius r and the parametric variables t, u, and v.
Syntax:
set xrange [{{<min>}:{<max>}}] {{no}reverse} {{no}writeback} {{no}extend}
| restore
show xrange
where <min> and <max> terms are constants, expressions or an asterisk to set
autoscaling. If the data are time/date, you must give the range as a quoted
string according to the `set timefmt` format.
If <min> or <max> is omitted the current value will not be changed.
See below for full autoscaling syntax. See also `noextend`.
The same syntax applies to `yrange`, `zrange`, `x2range`, `y2range`, `cbrange`,
`rrange`, `trange`, `urange` and `vrange`.
See `set link` for options that link the ranges of x and x2, or y and y2.
The `reverse` option reverses the direction of an autoscaled axis. For example,
if the data values range from 10 to 100, it will autoscale to the equivalent of
set xrange [100:10]. The `reverse` flag has no effect if the axis is not
autoscaled. NB: This is a change introduced in version 4.7.
Autoscaling: If <min> (the same applies for correspondingly to <max>) is
an asterisk "*" autoscaling is turned on. The range in which autoscaling
is being performed may be limited by a lower bound <lb> or an upper bound
<ub> or both. The syntax is
{ <lb> < } * { < <ub> }
For example,
0 < * < 200
sets <lb> = 0 and <ub> = 200. With such a setting <min> would be autoscaled,
but its final value will be between 0 and 200 (both inclusive despite the
'<' sign). If no lower or upper bound is specified, the '<' to also be
omitted. If <ub> is lower than <lb> the constraints will be turned off
and full autoscaling will happen.
This feature is useful to plot measured data with autoscaling but providing
a limit on the range, to clip outliers, or to guarantee a minimum range
that will be displayed even if the data would not need such a big range.
The `writeback` option essentially saves the range found by `autoscale` in
the buffers that would be filled by `set xrange`. This is useful if you wish
to plot several functions together but have the range determined by only
some of them. The `writeback` operation is performed during the `plot`
execution, so it must be specified before that command. To restore,
the last saved horizontal range use `set xrange restore`. For example,
set xrange [-10:10]
set yrange [] writeback
plot sin(x)
set yrange restore
replot x/2
results in a yrange of [-1:1] as found only from the range of sin(x); the
[-5:5] range of x/2 is ignored. Executing `show yrange` after each command
in the above example should help you understand what is going on.
In 2D, `xrange` and `yrange` determine the extent of the axes, `trange`
determines the range of the parametric variable in parametric mode or the
range of the angle in polar mode. Similarly in parametric 3D, `xrange`,
`yrange`, and `zrange` govern the axes and `urange` and `vrange` govern the
parametric variables.
In polar mode, `rrange` determines the radial range plotted. <rmin> acts as
an additive constant to the radius, whereas <rmax> acts as a clip to the
radius---no point with radius greater than <rmax> will be plotted. `xrange`
and `yrange` are affected---the ranges can be set as if the graph was of
r(t)-rmin, with rmin added to all the labels.
Any range may be partially or totally autoscaled, although it may not make
sense to autoscale a parametric variable unless it is plotted with data.
Ranges may also be specified on the `plot` command line. A range given on
the plot line will be used for that single `plot` command; a range given by
a `set` command will be used for all subsequent plots that do not specify
their own ranges. The same holds true for `splot`.
Examples:
To set the xrange to the default:
set xrange [-10:10]
To set the yrange to increase downwards:
set yrange [10:-10]
To change zmax to 10 without affecting zmin (which may still be autoscaled):
set zrange [:10]
To autoscale xmin while leaving xmax unchanged:
set xrange [*:]
To autoscale xmin but keeping xmin positive:
set xrange [0<*:]
To autoscale x but keep minimum range of 10 to 50 (actual might be larger):
set xrange [*<10:50<*]
Autoscaling but limit maximum xrange to -1000 to 1000, i.e. autoscaling
within [-1000:1000]
set xrange [-1000<*:*<1000]
Make sure xmin is somewhere between -200 and 100:
set xrange [-200<*<100:]
?commands set xtics
?commands unset xtics
?commands show xtics
?set xtics
?unset xtics
?show xtics
?xtics
?noxtics
Fine control of the major (labeled) tics on the x axis is possible with the
`set xtics` command. The tics may be turned off with the `unset xtics`
command, and may be turned on (the default state) with `set xtics`. Similar
commands control the major tics on the y, z, x2 and y2 axes.
Syntax:
set xtics {axis | border} {{no}mirror}
{in | out} {scale {default | <major> {,<minor>}}}
{{no}rotate {by <ang>}} {offset <offset> | nooffset}
{left | right | center | autojustify}
{add}
{ autofreq
| <incr>
| <start>, <incr> {,<end>}
| ({"<label>"} <pos> {<level>} {,{"<label>"}...) }
{format "formatstring"} {font "name{,<size>}"} {{no}enhanced}
{ numeric | timedate | geographic }
{{no}logscale}
{ rangelimited }
{ textcolor <colorspec> }
unset xtics
show xtics
The same syntax applies to `ytics`, `ztics`, `x2tics`, `y2tics` and `cbtics`.
`axis` or `border` tells `gnuplot` to put the tics (both the tics themselves
and the accompanying labels) along the axis or the border, respectively. If
the axis is very close to the border, the `axis` option will move the
tic labels to outside the border. The relevant margin settings will usually
be sized badly by the automatic layout algorithm in this case.
`mirror` tells `gnuplot` to put unlabeled tics at the same positions on the
opposite border. `nomirror` does what you think it does.
`in` and `out` change the tic marks to be drawn inwards or outwards.
With `scale`, the size of the tic marks can be adjusted. If <minor> is not
specified, it is 0.5*<major>. The default size 1.0 for major tics and 0.5
for minor tics is requested by `scale default`.
`rotate` asks `gnuplot` to rotate the text through 90 degrees, which will be
done if the terminal driver in use supports text rotation. `norotate`
cancels this. `rotate by <ang>` asks for rotation by <ang> degrees, supported
by some terminal types.
The defaults are `border mirror norotate` for tics on the x and y axes, and
`border nomirror norotate` for tics on the x2 and y2 axes. For the z axis,
the `{axis | border}` option is not available and the default is
`nomirror`. If you do want to mirror the z-axis tics, you might want to
create a bit more room for them with `set border`.
The <offset> is specified by either x,y or x,y,z, and may be preceded by
`first`, `second`, `graph`, `screen`, or `character` to select the
coordinate system. <offset> is the offset of the tics texts from their
default positions, while the default coordinate system is `character`.
See `coordinates` for details. `nooffset` switches off the offset.
Example:
Move xtics more closely to the plot.
set xtics offset 0,graph 0.05
By default, tic labels are justified automatically depending on the axis and
rotation angle to produce aesthetically pleasing results. If this is not
desired, justification can be overridden with an explicit `left`, `right` or
`center` keyword. `autojustify` restores the default behavior.
`set xtics` with no options restores the default border or axis if xtics are
being displayed; otherwise it has no effect. Any previously specified tic
frequency or position {and labels} are retained.
Tic positions are calculated automatically by default or if the `autofreq`
option is given.
A series of tic positions can be specified by giving either a tic interval
alone, or a start point, interval, and end point (see `xtics series`).
Individual tic positions can be specified individually by providing an
eplicit list of positions, where each position may have an associated
text label. See `xtics list`.
However they are specified, tics will only be plotted when in range.
Format (or omission) of the tic labels is controlled by `set format`, unless
the explicit text of a label is included in the `set xtics ("<label>")` form.
Minor (unlabeled) tics can be added automatically by the `set mxtics`
command, or at explicit positions by the `set xtics ("" <pos> 1, ...)` form.
The appearance of the tics (line style, line width etc.) is determined by the
border line (see `set border`), even if the tics are drawn at the axes.
?set xtics series
?xtics series
Syntax
set xtics <incr>
set xtics <start>, <incr>, <end>
The implicit <start>, <incr>, <end> form specifies that a series of tics will
be plotted on the axis between the values <start> and <end> with an increment
of <incr>. If <end> is not given, it is assumed to be infinity. The
increment may be negative. If neither <start> nor <end> is given, <start> is
assumed to be negative infinity, <end> is assumed to be positive infinity,
and the tics will be drawn at integral multiples of <incr>. If the axis is
logarithmic, the increment will be used as a multiplicative factor.
If you specify to a negative <start> or <incr> after a numerical value
(e.g., `rotate by <angle>` or `offset <offset>`), the parser fails because
it subtracts <start> or <incr> from that value. As a workaround, specify
`0-<start>` resp. `0-<incr>` in that case.
Example:
set xtics border offset 0,0.5 -5,1,5
Fails with 'invalid expression' at the last comma.
set xtics border offset 0,0.5 0-5,1,5
or
set xtics offset 0,0.5 border -5,1,5
Sets tics at the border, tics text with an offset of 0,0.5 characters, and
sets the start, increment, and end to -5, 1, and 5, as requested.
The `set grid` options 'front', 'back' and 'layerdefault' affect the drawing
order of the xtics, too.
Examples:
Make tics at 0, 0.5, 1, 1.5, ..., 9.5, 10.
set xtics 0,.5,10
Make tics at ..., -10, -5, 0, 5, 10, ...
set xtics 5
Make tics at 1, 100, 1e4, 1e6, 1e8.
set logscale x; set xtics 1,100,1e8
?set xtics list
?set xtics add
?xtics list
?xtics add
Syntax
set xtics {add} ("label1" <pos1> <level1>, "label2" <pos2> <level2>, ...)
The explicit ("label" <pos> <level>, ...) form allows arbitrary tic
positions or non-numeric tic labels. In this form, the tics do not
need to be listed in numerical order. Each tic has a
position, optionally with a label.
The label is a string enclosed by quotes or a string-valued expression.
It may contain formatting information for converting the position into its
label, such as "%3f clients", or it may be the empty string "".
See `set format` for more information. If no string is given, the
default label (numerical) is used.
An explicit tic mark has a third parameter, the level.
The default is level 0, a major tic. Level 1 generates a minor tic.
Labels are never printed for minor tics. Major and minor tics may be
auto-generated by the program or specified explicitly by the user.
Tics with level 2 and higher must be explicitly specified by the user, and
take priority over auto-generated tics. The size of tics marks at each
level is controlled by the command `set tics scale`.
Examples:
set xtics ("low" 0, "medium" 50, "high" 100)
set xtics (1,2,4,8,16,32,64,128,256,512,1024)
set ytics ("bottom" 0, "" 10, "top" 20)
set ytics ("bottom" 0, "" 10 1, "top" 20)
In the second example, all tics are labeled. In the third, only the end
tics are labeled. In the fourth, the unlabeled tic is a minor tic.
Normally if explicit tics are given, they are used instead of auto-generated
tics. Conversely if you specify `set xtics auto` or the like it will erase
any previously specified explicit tics. You can mix explicit and auto-
generated tics by using the keyword `add`, which must appear before
the tic style being added.
Example:
set xtics 0,.5,10
set xtics add ("Pi" 3.14159)
This will automatically generate tic marks every 0.5 along x, but will
also add an explicit labeled tic mark at pi.
?set xtics timedata
?xtics timedata tics
?timedata tics
Times and dates are stored internally as a number of seconds.
Input: Non-numeric time and date values are converted to seconds on input using
the format specifier in `timefmt`. Axis positions and range limits also may be
given as quoted dates or times interpreted using `timefmt`.
If the <start>, <incr>, <end> form is used, <incr> must be in seconds.
Use of `timefmt` to interpret input data, range, and tic positions is triggered
by `set xdata time`.
Output: Axis tic labels are generated using a separate format specified either
by `set format` or `set xtics format`. By default the usual numeric format
specifiers are expected (`set xtics numeric`). Other options are geographic
coordinates (`set xtics geographic`), or times or dates (`set xtics time`).
Note: For backward compatibility with earlier gnuplot versions, the command
`set xdata time` will implicitly also do `set xtics time`, and `set xdata`
or `unset xdata` will implicitly reset to `set xtics numeric`. However you
can change this with a later call to `set xtics`.
Examples:
set xdata time # controls interpretation of input data
set timefmt "%d/%m" # format used to read input data
set xtics timedate # controls interpretation of output format
set xtics format "%b %d" # format used for tic labels
set xrange ["01/12":"06/12"]
set xtics "01/12", 172800, "05/12"
set xdata time
set timefmt "%d/%m"
set xtics format "%b %d" time
set xrange ["01/12":"06/12"]
set xtics ("01/12", "" "03/12", "05/12")
Both of these will produce tics "Dec 1", "Dec 3", and "Dec 5", but in the
second example the tic at "Dec 3" will be unlabeled.
?commands set xtics geographic
?set xtics geographic
?geographic
`set xtics geographic` indicates that x-axis values are to be interpreted as
a geographic coordinate measured in degrees. Use `set xtics format` or
`set format x` to specify the appearance of the axis tick labels.
The format specifiers for geographic data are as follows:
%D = integer degrees
%<width.precision>d = floating point degrees
%M = integer minutes
%<width.precision>m = floating point minutes
%S = integer seconds
%<width.precision>s = floating point seconds
%E = label with E/W instead of +/-
%N = label with N/S instead of +/-
For example, the command `set format x "%Ddeg %5.2mmin %E"` will cause
x coordinate -1.51 to be labeled as `" 1deg 30.60min W"`.
If the xtics are left in the default state (`set xtics numeric`) the coordinate
will be reported as a decimal number of degrees, and `format` will be assumed
to contain normal numeric format specifiers rather than the special set above.
To output degrees/minutes/seconds in a context other than axis tics, such as
placing labels on a map, you can use the relative time format specifiers
%tH %tM %tS for strptime. See `time_specifiers`, `strptime`.
?set xtics logscale
?xtics logscale
If the `logscale` attribute is set for a tic series along a log-scaled axis,
the tic interval is interpreted as a multiplicative factor rather than a
constant. For example:
# generate a series of tics at y=20 y=200 y=2000 y=20000
set log y
set ytics 20, 10, 50000 logscale
Note that no tic is placed at y=50000 because it is not in the series 2*10^x.
If the logscale property is disabled, the tic increment will be treated as
an additive constant even for a log-scaled axis. For example:
# generate a series of tics at y=20 y=40 y=60 ... y=200
set log y
set yrange [20:200]
set ytics 20 nologscale
The `logscale` attribute is set automatically by the `set log` command,
so normally you do not need this keyword unless you want to force a
constant tic interval as in the second example above.
?set xtics rangelimited
?xtics rangelimited
?rangelimited
?range-frame
This option limits both the auto-generated axis tic labels and the
corresponding plot border to the range of values actually present in the data
that has been plotted. Note that this is independent of the current range
limits for the plot. For example, suppose that the data in "file.dat" all lies
in the range 2 < y < 4. Then the following commands will create a plot for
which the left-hand plot border (y axis) is drawn for only this portion of the
total y range, and only the axis tics in this region are generated.
I.e., the plot will be scaled to the full range on y, but there will be a gap
between 0 and 2 on the left border and another gap between 4 and 10. This
style is sometimes referred to as a `range-frame` graph.
set border 3
set yrange [0:10]
set ytics nomirror rangelimited
plot "file.dat"
?commands set xyplane
?commands show xyplane
?set xyplane
?show xyplane
?xyplane
The `set xyplane` command adjusts the position at which the xy plane is drawn
in a 3D plot. The synonym "set ticslevel" is accepted for backwards
compatibility.
Syntax:
set xyplane at <zvalue>
set xyplane relative <frac>
set ticslevel <frac> # equivalent to set xyplane relative
show xyplane
The form `set xyplane relative <frac>` places the xy plane below the range in
Z, where the distance from the xy plane to Zmin is given as a fraction of the
total range in z. The default value is 0.5. Negative values are permitted,
but tic labels on the three axes may overlap.
The alternative form `set xyplane at <zvalue>` fixes the placement of the
xy plane at a specific Z value regardless of the current z range. Thus to
force the x, y, and z axes to meet at a common origin one would specify
`set xyplane at 0`.
See also `set view`, and `set zeroaxis`.
?commands set xzeroaxis
?commands unset xzeroaxis
?commands show xzeroaxis
?set xzeroaxis
?unset xzeroaxis
?show xzeroaxis
?xzeroaxis
?noxzeroaxis
The `set xzeroaxis` command draws a line at y = 0. For details,
please see `set zeroaxis`.
?commands set y2data
?commands show y2data
?set y2data
?show y2data
?y2data
The `set y2data` command sets y2 (right-hand) axis data to timeseries
(dates/times). Please see `set xdata`.
?commands set y2dtics
?commands unset y2dtics
?set y2dtics
?unset y2dtics
?show y2dtics
?y2dtics
?noy2dtics
The `set y2dtics` command changes tics on the y2 (right-hand) axis to days of
the week. Please see `set xdtics` for details.
?commands set y2label
?commands show y2label
?set y2label
?show y2label
?y2label
The `set y2label` command sets the label for the y2 (right-hand) axis.
Please see `set xlabel`.
?commands set y2mtics
?commands unset y2mtics
?commands show y2mtics
?set y2mtics
?unset y2mtics
?show y2mtics
?y2mtics
?noy2mtics
The `set y2mtics` command changes tics on the y2 (right-hand) axis to months
of the year. Please see `set xmtics` for details.
?commands set y2range
?commands show y2range
?set y2range
?show y2range
?y2range
The `set y2range` command sets the vertical range that will be displayed on
the y2 (right) axis. See `set xrange` for the full set of command options.
See also `set link`.
?commands set y2tics
?commands unset y2tics
?commands show y2tics
?set y2tics
?unset y2tics
?show y2tics
?y2tics
?noy2tics
The `set y2tics` command controls major (labeled) tics on the y2 (right-hand)
axis. Please see `set xtics` for details.
?commands set y2zeroaxis
?commands unset y2zeroaxis
?commands show y2zeroaxis
?set y2zeroaxis
?unset y2zeroaxis
?show y2zeroaxis
?y2zeroaxis
?noy2zeroaxis
The `set y2zeroaxis` command draws a line at the origin of the y2 (right-hand)
axis (x2 = 0). For details, please see `set zeroaxis`.
?commands set ydata
?commands show ydata
?set ydata
?show ydata
?ydata
The `set ydata` commands sets y-axis data to timeseries (dates/times).
Please see `set xdata`.
?commands set ydtics
?commands unset ydtics
?commands show ydtics
?set ydtics
?unset ydtics
?show ydtics
?ydtics
?noydtics
The `set ydtics` command changes tics on the y axis to days of the week.
Please see `set xdtics` for details.
?commands set ylabel
?commands show ylabel
?set ylabel
?show ylabel
?ylabel
This command sets the label for the y axis. Please see `set xlabel`.
?commands set ymtics
?commands unset ymtics
?commands show ymtics
?set ymtics
?unset ymtics
?show ymtics
?ymtics
?noymtics
The `set ymtics` command changes tics on the y axis to months of the year.
Please see `set xmtics` for details.
?commands set yrange
?commands show yrange
?set yrange
?show yrange
?yrange
The `set yrange` command sets the vertical range that will be displayed on
the y axis. Please see `set xrange` for details.
?commands set ytics
?commands unset ytics
?commands show ytics
?set ytics
?unset ytics
?show ytics
?ytics
?noytics
The `set ytics` command controls major (labeled) tics on the y axis.
Please see `set xtics` for details.
?commands set yzeroaxis
?commands unset yzeroaxis
?commands show yzeroaxis
?set yzeroaxis
?unset yzeroaxis
?show yzeroaxis
?yzeroaxis
?noyzeroaxis
The `set yzeroaxis` command draws a line at x = 0. For details,
please see `set zeroaxis`.
?commands set zdata
?commands show zdata
?set zdata
?show zdata
?zdata
The `set zdata` command sets zaxis data to timeseries (dates/times).
Please see `set xdata`.
?commands set zdtics
?commands unset zdtics
?commands show zdtics
?set zdtics
?unset zdtics
?show zdtics
?zdtics
?nozdtics
The `set zdtics` command changes tics on the z axis to days of the week.
Please see `set xdtics` for details.
?commands set zzeroaxis
?commands unset zzeroaxis
?commands show zzeroaxis
?set zzeroaxis
?unset zzeroaxis
?show zzeroaxis
?zzeroaxis
?nozzeroaxis
The `set zzeroaxis` command draws a line through (x=0,y=0). This has no effect
on 2D plots, including splot with `set view map`. For details, please
see `set zeroaxis` and `set xyplane`.
?commands set cbdata
?commands show cbdata
?set cbdata
?show cbdata
?cbdata
Set color box axis data to timeseries (dates/times). Please see `set xdata`.
?commands set cbdtics
?commands unset cbdtics
?commands show cbdtics
?set cbdtics
?unset cbdtics
?show cbdtics
?cbdtics
?nocbdtics
The `set cbdtics` command changes tics on the color box axis to days of the
week. Please see `set xdtics` for details.
?commands set zero
?commands show zero
?set zero
?show zero
?zero
The `zero` value is the default threshold for values approaching 0.0.
Syntax:
set zero <expression>
show zero
`gnuplot` will not plot a point if its imaginary part is greater in magnitude
than the `zero` threshold. This threshold is also used in various other
parts of `gnuplot` as a (crude) numerical-error threshold. The default
`zero` value is 1e-8. `zero` values larger than 1e-3 (the reciprocal of the
number of pixels in a typical bitmap display) should probably be avoided, but
it is not unreasonable to set `zero` to 0.0.
?commands set zeroaxis
?commands unset zeroaxis
?commands show zeroaxis
?set zeroaxis
?unset zeroaxis
?show zeroaxis
?zeroaxis
The x axis may be drawn by `set xzeroaxis` and removed by `unset xzeroaxis`.
Similar commands behave similarly for the y, x2, y2, and z axes.
`set zeroaxis ...` (no prefix) acts on the x, y, and z axes jointly.
Syntax:
set {x|x2|y|y2|z}zeroaxis { {linestyle | ls <line_style>}
| {linetype | lt <line_type>}
{linewidth | lw <line_width>}
{linecolor | lc <colorspec>}
{dashtype | dt <dashtype>} }
unset {x|x2|y|y2|z}zeroaxis
show {x|y|z}zeroaxis
By default, these options are off. The selected zero axis is drawn
with a line of type <line_type>, width <line_width>, color <colorspec>, and
dash type <dashtype> (if supported by the terminal driver currently in use),
or a user-defined style <line_style> (see `set style line`).
If no linetype is specified, any zero axes selected will be drawn
using the axis linetype (linetype 0).
Examples:
To simply have the y=0 axis drawn visibly:
set xzeroaxis
If you want a thick line in a different color or pattern, instead:
set xzeroaxis linetype 3 linewidth 2.5
?commands set zlabel
?commands show zlabel
?set zlabel
?show zlabel
?zlabel
This command sets the label for the z axis. Please see `set xlabel`.
?commands set zmtics
?commands unset zmtics
?commands show zmtics
?set zmtics
?unset zmtics
?show zmtics
?zmtics
?nozmtics
The `set zmtics` command changes tics on the z axis to months of the year.
Please see `set xmtics` for details.
?commands set zrange
?commands show zrange
?set zrange
?show zrange
?zrange
The `set zrange` command sets the range that will be displayed on the z axis.
The zrange is used only by `splot` and is ignored by `plot`. Please see
`set xrange` for details.
?commands set ztics
?commands unset ztics
?commands show ztics
?set ztics
?unset ztics
?show ztics
?ztics
?noztics
The `set ztics` command controls major (labeled) tics on the z axis.
Please see `set xtics` for details.
?commands set cblabel
?commands show cblabel
?set cblabel
?show cblabel
?cblabel
This command sets the label for the color box axis. Please see `set xlabel`.
?commands set cbmtics
?commands unset cbmtics
?commands show cbmtics
?set cbmtics
?unset cbmtics
?show cbmtics
?cbmtics
?nocbmtics
The `set cbmtics` command changes tics on the color box axis to months of the
year. Please see `set xmtics` for details.
?commands set cbrange
?commands show cbrange
?set cbrange
?show cbrange
?cbrange
The `set cbrange` command sets the range of values which are colored using
the current `palette` by styles `with pm3d`, `with image` and `with palette`.
Values outside of the color range use color of the nearest extreme.
If the cb-axis is autoscaled in `splot`, then the colorbox range is taken from
`zrange`. Points drawn in `splot ... pm3d|palette` can be filtered by using
different `zrange` and `cbrange`.
Please see `set xrange` for details on `set cbrange` syntax. See also
`set palette` and `set colorbox`.
?commands set cbtics
?commands unset cbtics
?commands show cbtics
?set cbtics
?unset cbtics
?show cbtics
?cbtics
?nocbtics
The `set cbtics` command controls major (labeled) tics on the color box axis.
Please see `set xtics` for details.
?commands shell
?shell
The `shell` command spawns an interactive shell. To return to `gnuplot`,
type `logout` if using VMS, `exit` or the END-OF-FILE character if using
Unix, or `exit` if using MS-DOS or OS/2.
The `shell` command ignores anything else on the gnuplot command line.
If instead you want to pass a command string to a shell for immediate
execution, use the `system` function or the shortcut `!`. See `system`.
Examples:
shell
system "print previous_plot.ps"
! print previous_plot.ps
current_time = system("date")
?commands splot
?splot
`splot` is the command for drawing 3D plots (well, actually projections on a 2D
surface, but you knew that). It is the 3D equivalent of the `plot` command.
`splot` provides only a single x, y, and z axis; there is no equivalent to the
x2 and y2 secondary axes provided by `plot`.
See the `plot` command for many options available in both 2D and 3D plots.
Syntax:
splot {<ranges>}
{<iteration>}
<function> | {{<file name> | <datablock name>} {datafile-modifiers}}
{<title-spec>} {with <style>}
{, {definitions{,}} <function> ...}
The `splot` command operates on a data generated by a function, read from
a data file, or stored previously in a named data block. Data file names
are usually provided as a quoted string. The function can be a mathematical
expression, or a triple of mathematical expressions in parametric mode.
By default `splot` draws the xy plane completely below the plotted data.
The offset between the lowest ztic and the xy plane can be changed by `set
xyplane`. The orientation of a `splot` projection is controlled by
`set view`. See `set view` and `set xyplane` for more information.
The syntax for setting ranges on the `splot` command is the same as for `plot`.
In non-parametric mode, ranges must be given in the order
splot [<xrange>][<yrange>][<zrange>] ...
In parametric mode, the order is
splot [<urange>][<vrange>][<xrange>][<yrange>][<zrange>] ...
The `title` option is the same as in `plot`. The operation of `with` is also
the same as in `plot` except that not all 2D plotting styles are available.
The `datafile` options have more differences.
As an alternative to surfaces drawn using parametric or function mode, the
pseudo-file '++' can be used to generate samples on a grid in the xy plane.
See also `show plot`, `set view map`, and `sampling`.
?commands splot datafile
?splot datafile
`Splot`, like `plot`, can display from a file.
Syntax:
splot '<file_name>' {binary <binary list>}
{{nonuniform} matrix}
{index <index list>}
{every <every list>}
{using <using list>}
The special filenames `""` and `"-"` are permitted, as in `plot`.
See `special-filenames`.
In brief, `binary` and `matrix` indicate that the data are in a special
form, `index` selects which data sets in a multi-data-set file are to be
plotted, `every` specifies which datalines (subsets) within a single data
set are to be plotted, and `using` determines how the columns within a single
record are to be interpreted.
The options `index` and `every` behave the same way as with `plot`; `using`
does so also, except that the `using` list must provide three entries
instead of two.
The `plot` option `smooth` is not available for `splot`, but
`cntrparam` and `dgrid3d` provide limited smoothing capabilities.
Data file organization is essentially the same as for `plot`, except that
each point is an (x,y,z) triple. If only a single value is provided, it
will be used for z, the block number will be used for y, and the index
of the data point in the block will be used for x. If two or four values
are provided, `gnuplot` uses the last value for calculating the color in
pm3d plots. Three values are interpreted as an (x,y,z) triple. Additional
values are generally used as errors, which can be used by `fit`.
Single blank records separate blocks of data in a `splot` datafile; `splot`
treats blocks as the equivalent of function y-isolines. No line will join
points separated by a blank record. If all blocks contain the same number of
points, `gnuplot` will draw cross-isolines between points in the blocks,
connecting corresponding points. This is termed "grid data", and is required
for drawing a surface, for contouring (`set contour`) and hidden-line removal
(`set hidden3d`). See also `splot grid_data`.
It is no longer necessary to specify `parametric` mode for three-column
`splot`s.
?commands plot datafile matrix
?commands splot datafile matrix
?plot datafile matrix
?splot datafile matrix
?binary matrix
?matrix
Gnuplot can interpret matrix data input in two different ways.
The first of these assumes a uniform grid of x and y coordinates and assigns
each value in the input matrix to one element M[i,j] of this uniform grid.
The assigned x coordinates are the integers [0:NCOLS-1].
The assigned y coordinates are the integers [0:NROWS-1].
This is the default for text data input, but not for binary input.
See `matrix uniform` for examples and additional keywords.
The second interpretation assumes a non-uniform grid with explicit x and y
coordinates. The first row of input data contains the y coordinates;
the first column of input data contains the x coordinates. For binary input
data, the first element of the first row must contain the number of columns.
This is the default for `binary matrix` input, but requires an additional
keyword `nonuniform` for text input data.
See `matrix nonuniform` for examples.
?commands plot datafile matrix uniform
?commands splot datafile matrix uniform
?datafile matrix uniform
?matrix uniform
?binary matrix uniform
Example commands for plotting uniform matrix data:
splot 'file' matrix using 1:2:3 # text input
splot 'file' binary general using 1:2:3 # binary input
In a uniform grid matrix the z-values are read in a row at a time, i. e.,
z11 z12 z13 z14 ...
z21 z22 z23 z24 ...
z31 z32 z33 z34 ...
and so forth.
For text input, if the first row contains column labels rather than data,
use the additional keyword `columnheaders`. Similarly if the first field
in each row contains a label rather than data, use the additional keyword
`rowheaders`. Here is an example that uses both:
$DATA << EOD
xxx A B C D
aa z11 z12 z13 z14
bb z21 z22 z23 z24
cc z31 z32 z33 z34
EOD
plot $DATA matrix columnheaders rowheaders with image
For text input, a blank line or comment line ends the matrix, and starts a new
surface mesh. You can select among the meshes inside a file by the `index`
option to the `splot` command, as usual.
?commands plot datafile matrix nonuniform
?commands splot datafile matrix nonuniform
?datafile matrix nonuniform
?matrix nonuniform
?binary matrix nonuniform
The first row of input data contains the y coordinates.
The first column of input data contains the x coordinates.
For binary input data, the first field of the first row must contain the
number of columns. (This number is ignored for text input).
Example commands for plotting non-uniform matrix data:
splot 'file' nonuniform matrix using 1:2:3 # text input
splot 'file' binary matrix using 1:2:3 # binary input
Thus the data organization for non-uniform matrix input is
<N+1> <x0> <x1> <x2> ... <xN>
<y0> <z0,0> <z0,1> <z0,2> ... <z0,N>
<y1> <z1,0> <z1,1> <z1,2> ... <z1,N>
: : : : ... :
which is then converted into triplets:
<x0> <y0> <z0,0>
<x0> <y1> <z0,1>
<x0> <y2> <z0,2>
: : :
<x0> <yN> <z0,N>
<x1> <y0> <z1,0>
<x1> <y1> <z1,1>
: : :
These triplets are then converted into `gnuplot` iso-curves and then
`gnuplot` proceeds in the usual manner to do the rest of the plotting.
?commands plot datafile matrix examples
?commands splot datafile matrix examples
?datafile matrix examples
?matrix examples
?binary matrix examples
A collection of matrix and vector manipulation routines (in C) is provided
in `binary.c`. The routine to write binary data is
int fwrite_matrix(file,m,nrl,nrl,ncl,nch,row_title,column_title)
An example of using these routines is provided in the file `bf_test.c`, which
generates binary files for the demo file `demo/binary.dem`.
Usage in `plot`:
plot `a.dat` matrix
plot `a.dat` matrix using 1:3
plot 'a.gpbin' {matrix} binary using 1:3
will plot rows of the matrix, while using 2:3 will plot matrix columns, and
using 1:2 the point coordinates (rather useless). Applying the `every` option
you can specify explicit rows and columns.
Example -- rescale axes of a matrix in a text file:
splot `a.dat` matrix using (1+$1):(1+$2*10):3
Example -- plot the 3rd row of a matrix in a text file:
plot 'a.dat' matrix using 1:3 every 1:999:1:2
(rows are enumerated from 0, thus 2 instead of 3).
Gnuplot can read matrix binary files by use of the option `binary` appearing
without keyword qualifications unique to general binary, i.e., `array`,
`record`, `format`, or `filetype`. Other general binary keywords for
translation should also apply to matrix binary. (See `binary general` for
more details.)
?commands splot datafile example
?splot datafile example
?splot example
A simple example of plotting a 3D data file is
splot 'datafile.dat'
where the file "datafile.dat" might contain:
# The valley of the Gnu.
0 0 10
0 1 10
0 2 10
1 0 10
1 1 5
1 2 10
2 0 10
2 1 1
2 2 10
3 0 10
3 1 0
3 2 10
Note that "datafile.dat" defines a 4 by 3 grid ( 4 rows of 3 points each ).
Rows (blocks) are separated by blank records.
Note also that the x value is held constant within each dataline. If you
instead keep y constant, and plot with hidden-line removal enabled, you will
find that the surface is drawn 'inside-out'.
Actually for grid data it is not necessary to keep the x values constant
within a block, nor is it necessary to keep the same sequence of y
values. `gnuplot` requires only that the number of points be the same for
each block. However since the surface mesh, from which contours are
derived, connects sequentially corresponding points, the effect of an
irregular grid on a surface plot is unpredictable and should be examined
on a case-by-case basis.
?commands splot grid_data
?splot grid_data
?grid_data
The 3D routines are designed for points in a grid format, with one sample,
datapoint, at each mesh intersection; the datapoints may originate from
either evaluating a function, see `set isosamples`, or reading a datafile,
see `splot datafile`. The term "isoline" is applied to the mesh lines for
both functions and data. Note that the mesh need not be rectangular in x
and y, as it may be parameterized in u and v, see `set isosamples`.
However, `gnuplot` does not require that format. In the case of functions,
'samples' need not be equal to 'isosamples', i.e., not every x-isoline
sample need intersect a y-isoline. In the case of data files, if there
are an equal number of scattered data points in each block, then
"isolines" will connect the points in a block, and "cross-isolines"
will connect the corresponding points in each block to generate a
"surface". In either case, contour and hidden3d modes may give different
plots than if the points were in the intended format. Scattered data can be
converted to a {different} grid format with `set dgrid3d`.
The contour code tests for z intensity along a line between a point on a
y-isoline and the corresponding point in the next y-isoline. Thus a `splot`
contour of a surface with samples on the x-isolines that do not coincide with
a y-isoline intersection will ignore such samples. Try:
set xrange [-pi/2:pi/2]; set yrange [-pi/2:pi/2]
set style function lp
set contour
set isosamples 10,10; set samples 10,10;
splot cos(x)*cos(y)
set samples 4,10; replot
set samples 10,4; replot
?commands splot surfaces
?splot surfaces
`splot` can display a surface as a collection of points, or by connecting
those points. As with `plot`, the points may be read from a data file or
result from evaluation of a function at specified intervals, see
`set isosamples`. The surface may be approximated by connecting the points
with straight line segments, see `set surface`, in which case the surface
can be made opaque with `set hidden3d.` The orientation from which the 3d
surface is viewed can be changed with `set view`.
Additionally, for points in a grid format, `splot` can interpolate points
having a common amplitude (see `set contour`) and can then connect those
new points to display contour lines, either directly with straight-line
segments or smoothed lines (see `set cntrparam`). Functions are already
evaluated in a grid format, determined by `set isosamples` and `set samples`,
while file data must either be in a grid format, as described in `data-file`,
or be used to generate a grid (see `set dgrid3d`).
Contour lines may be displayed either on the surface or projected onto the
base. The base projections of the contour lines may be written to a
file, and then read with `plot`, to take advantage of `plot`'s additional
formatting capabilities.
?commands stats
?stats
?statistics
Syntax:
stats {<ranges>} 'filename' {matrix | using N{:M}} {name 'prefix'} {{no}output}
This command prepares a statistical summary of the data in one or two columns
of a file. The using specifier is interpreted in the same way as for plot
commands. See `plot` for details on the `index`, `every`, and `using`
directives. Data points are filtered against both xrange and yrange before
analysis. See `set xrange`. The summary is printed to the screen by default.
Output can be redirected to a file by prior use of the command `set print`,
or suppressed altogether using the `nooutput` option.
In addition to printed output, the program stores the individual statistics
into three sets of variables.
The first set of variables reports how the data is laid out in the file:
STATS_records # total number of in-range data records (N)
STATS_outofrange # number of records filtered out by range limits
STATS_invalid # number of invalid/incomplete/missing records
STATS_blank # number of blank lines in the file
STATS_blocks # number of indexable blocks of data in the file
STATS_columns # number of data columns in the first row of data
The second set reports properties of the in-range data from a single column.
This column is treated as y. If the y axis is autoscaled then no range limits
are applied. Otherwise only values in the range [ymin:ymax] are considered.
If two columns are analysed jointly by a single `stats` command, the suffix
"_x" or "_y" is appended to each variable name.
I.e. STATS_min_x is the minimum value found in the first column, while
STATS_min_y is the minimum value found in the second column.
In this case points are filtered by testing against both xrange and yrange.
STATS_min # minimum value of in-range data points
STATS_max # maximum value of in-range data points
STATS_index_min # index i for which data[i] == STATS_min
STATS_index_max # index i for which data[i] == STATS_max
STATS_lo_quartile # value of the lower (1st) quartile boundary
STATS_median # median value
STATS_up_quartile # value of the upper (3rd) quartile boundary
STATS_mean # mean value of the in-range data points
STATS_ssd # sample standard deviation of the in-range data
= sqrt( Sum[(y-ymean)^2] / (N-1) )
STATS_stddev # population standard deviation of the in-range data
= sqrt( Sum[(y-ymean)^2] / N )
STATS_sum # sum
STATS_sumsq # sum of squares
STATS_skewness # skewness of the in-range data points
STATS_kurtosis # kurtosis of the in-range data points
STATS_adev # mean absolute deviation of the in-range data points
STATS_mean_err # standard error of the mean value
STATS_stddev_err # standard error of the standard deviation
STATS_skewness_err # standard error of the skewness
STATS_kurtosis_err # standard error of the kurtosis
The third set of variables is only relevant to analysis of two data columns.
STATS_correlation # sample correlation coefficient between x and y values
STATS_slope # A corresponding to a linear fit y = Ax + B
STATS_slope_err # uncertainty of A
STATS_intercept # B corresponding to a linear fit y = Ax + B
STATS_intercept_err # uncertainty of B
STATS_sumxy # sum of x*y
STATS_pos_min_y # x coordinate of a point with minimum y value
STATS_pos_max_y # x coordinate of a point with maximum y value
When `matrix` is specified, all matrix entries are included in the analysis.
The matrix dimensions are saved in the variables STATS_size_x and STATS_size_y.
It may be convenient to track the statistics from more than one file or data
column in parallel. The `name` option causes the default prefix "STATS" to be
replaced by a user-specified string. For example, the mean value of column 2
data from two different files could be compared by
stats "file1.dat" using 2 name "A"
stats "file2.dat" using 2 name "B"
if (A_mean < B_mean) {...}
The keyword `columnheader` or function `columnheader(N)` can be used to
generate the prefix from the contents of the first row of a data file:
do for [COL=5:8] { stats 'datafile' using COL name columnheader }
The index reported in STATS_index_xxx corresponds to the value of pseudo-column
0 ($0) in plot commands. I.e. the first point has index 0, the last point
has index N-1.
Data values are sorted to find the median and quartile boundaries.
If the total number of points N is odd, then the median value is taken as the
value of data point (N+1)/2. If N is even, then the median is reported as the
mean value of points N/2 and (N+2)/2. Equivalent treatment is used for the
quartile boundaries.
For an example of using the `stats` command to annotate a subsequent plot, see
stats.dem.
The `stats` command in this version of gnuplot can handle log-scaled data, but
not the presence of time/date fields (`set xdata time` or `set ydata time`).
This restriction may be relaxed in a future version.
?commands system
?system
Syntax:
system "command string"
! command string
output = system("command string")
show variable GPVAL_SYSTEM
`system "command"` executes "command" in a subprocess by invoking the
operating system's default shell. If called as a function, `system("command")`
returns the character stream from the subprocess's stdout as a string.
One trailing newline is stripped from the resulting string if present.
See also `backquotes`.
The exit status of the subprocess is reported in variables GPVAL_SYSTEM_ERRNO
and GPVAL_SYSTEM_ERRMSG. Note that if the command string invokes more than
one programs, the subprocess may return "Success" even if one of the programs
produced an error. E.g. file = system("ls -1 *.plt | tail -1") will return
"Success" even if there are no *.plt files because `tail` succeeds even if `ls`
does not.
The system command can be used to import external functions into gnuplot as
shown below, however this will force creation of a separate subprocess every
time the function is invoked. For functions that will be invoked many times
it would be better to import a directly callable subroutine from a shared
library. See `import` and `plugin.dem`.
f(x) = real(system(sprintf("somecommand %f", x)))
?commands test
?test palette
?test
This command graphically tests or presents terminal and palette capabilities.
Syntax:
test {terminal | palette}
`test` or `test terminal` creates a display of line and point styles and other
useful things supported by the `terminal` you are currently using.
`test palette` plots profiles of R(z),G(z),B(z), where 0<=z<=1. These are the
RGB components of the current color `palette`. It also plots the apparent net
intensity as calculated using NTSC coefficients to map RGB onto a grayscale.
The profile values are also loaded into a datablock named $PALETTE.
?commands toggle
?toggle
Syntax:
toggle {<plotno> | "plottitle" | all}
This command has the same effect as left-clicking on the key entry for a plot
currently displayed by an interactive terminal (qt, wxt, x11). If the plot is
showing, it is toggled off; if it is currently hidden, it is toggled on.
`toggle all` acts on all active plots, equivalent to the hotkey "i".
`toggle "title"` requires an exact match to the plot title. `toggle "ti*"`
acts on the first plot whose title matches the characters before the final '*'.
If the current terminal is not interactive, the toggle command has no effect.
?commands undefine
?undefine
Clear one or more previously defined user variables. This is useful in order
to reset the state of a script containing an initialization test.
A variable name can contain the wildcard character `*` as last character. If the
wildcard character is found, all variables with names that begin with the prefix
preceding the wildcard will be removed. This is useful to remove several variables
sharing a common prefix. Note that the wildcard character is only allowed at the
end of the variable name! Specifying the wildcard character as sole argument to
`undefine` has no effect.
Example:
undefine foo foo1 foo2
if (!exists("foo")) load "initialize.gp"
bar = 1; bar1 = 2; bar2 = 3
undefine bar* # removes all three variables
?commands unset
?unset
Options set using the `set` command may be returned to their default state by
the corresponding `unset` command. The `unset` command may contain an optional
iteration clause. See `plot for`.
Examples:
set xtics mirror rotate by -45 0,10,100
...
unset xtics
# Unset labels numbered between 100 and 200
unset for [i=100:200] label i
?unset linetype
Syntax:
unset linetype N
Remove all characteristics previously associated with a single linetype.
Subsequent use of this linetype will use whatever characteristics and color
that is native to the current terminal type (i.e. the default linetypes
properties available in gnuplot versions prior to 4.6).
?unset monochrome
Switches the active set of linetypes from monochrome to color.
Equivalent to `set color`.
?unset output
Because some terminal types allow multiple plots to be written into a single
output file, the output file is not automatically closed after plotting.
In order to print or otherwise use the file safely, it should first be closed
explicitly by using `unset output` or by using `set output` to close the
previous file and then open a new one.
?unset terminal
The default terminal that is active at the time of program entry depends on the
system platform, gnuplot build options, and the environmental variable GNUTERM.
Whatever this default may be, gnuplot saves it to internal variable GNUTERM.
The `unset terminal` command restores the initial terminal type.
It is equivalent to `set terminal GNUTERM`. However if the string in GNUTERM
contains terminal options in addition to the bare terminal name, you may want
to instead use `set terminal @GNUTERM`.
?commands update
?update
Note: This command is DEPRECATED. Use `save fit` instead.
The `update` command remains in version 5.2 for backwards compatibility but
will be removed in later versions.
Syntax:
update <filename> {<filename>}
This command updates the current values of variables stored in the given
file, which must be formatted as an initial-value file (see `fit`).
If the file does not exist, a new file is created containing all
currently defined user variables. All variables not used in the last fit
are marked as "#FIXED". This is useful for saving the current values of fit
variables for later use or for restarting a converged or stopped fit.
If a second filename is supplied, the updated values are written to this
file, and the original parameter file is left unmodified.
Otherwise, if the file already exists, `gnuplot` first renames it by
appending `.old` and then opens a new file. That is, "`update 'fred'`"
behaves the same as "`!rename fred fred.old; update 'fred.old' 'fred'`".
?while
?commands while
Syntax:
while (<expr>) {
<commands>
}
Execute a block of commands repeatedly so long as <expr> evaluates to
a non-zero value. This command cannot be mixed with old-style (un-bracketed)
if/else statements. See also `do`, `continue`, `break`.
?complete list of terminals
?terminal
?term
Gnuplot supports a large number of output formats. These are selected by
choosing an appropriate terminal type, possibly with additional modifying
options. See `set terminal`.
This document may describe terminal types that are not available to you
because they were not configured or installed on your system. To see a list of
terminals available on a particular gnuplot installation, type 'set terminal'
with no modifiers.
Terminals marked `legacy` are not built by default in recent gnuplot versions
and may not actually work.
?commands set terminal tek410x
?set terminal tek410x
?set term tek410x
?terminal tek410x
?term tek410x
?tek410x
The `tek410x` terminal driver supports the 410x and 420x family of Tektronix
terminals. It has no options.
?commands set terminal tek40xx
?set terminal tek40xx
?set term tek40xx
?terminal tek40xx
?term tek40xx
?tek40
?commands set terminal vttek
?set terminal vttek
?set term vttek
?terminal vttek
?term vttek
?vttek
?commands set terminal xterm
?set terminal xterm
?set term xterm
?terminal xterm
?term xterm
?xterm
This family of terminal drivers supports a variety of VT-like terminals.
`tek40xx` supports Tektronix 4010 and others as well as most TEK emulators.
`vttek` supports VT-like tek40xx terminal emulators.
The following are present only if selected when gnuplot is built:
`kc-tek40xx` supports MS-DOS Kermit Tek4010 terminal emulators in color;
`km-tek40xx` supports them in monochrome. `selanar` supports Selanar graphics.
`bitgraph` supports BBN Bitgraph terminals.
None have any options.
?commands set terminal x11
?set terminal x11
?set term x11
?terminal x11
?term x11
?x11
?X11
Syntax:
set terminal x11 {<n> | window "<string>"}
{title "<string>"}
{{no}enhanced} {font <fontspec>}
{linewidth LW}
{{no}persist} {{no}raise} {{no}ctrlq}
{{no}replotonresize}
{close}
{size XX,YY} {position XX,YY}
set terminal x11 {reset}
Multiple plot windows are supported: `set terminal x11 <n>` directs the
output to plot window number n. If n is not 0, the terminal number will be
appended to the window title (unless a title has been supplied manually)
and the icon will be labeled `Gnuplot <n>`. The active window may be
distinguished by a change in cursor (from default to crosshair).
The `x11` terminal can connect to X windows previously created by an outside
application via the option `window` followed by a string containing the
X ID for the window in hexadecimal format. Gnuplot uses that external X
window as a container since X does not allow for multiple clients selecting
the ButtonPress event. In this way, gnuplot's mouse features work within
the contained plot window.
set term x11 window "220001e"
The x11 terminal supports enhanced text mode (see `enhanced`), subject
to the available fonts. In order for font size commands embedded in text
to have any effect, the default x11 font must be scalable. Thus the first
example below will work as expected, but the second will not.
set term x11 enhanced font "arial,15"
set title '{/=20 Big} Medium {/=5 Small}'
set term x11 enhanced font "terminal-14"
set title '{/=20 Big} Medium {/=5 Small}'
Plot windows remain open even when the `gnuplot` driver is changed to a
different device. A plot window can be closed by pressing the letter q
while that window has input focus, or by choosing `close` from a window
manager menu. All plot windows can be closed by specifying `reset`, which
actually terminates the subprocess which maintains the windows (unless
`-persist` was specified). The `close` command can be used to close
individual plot windows by number. However, after a `reset`, those plot
windows left due to persist cannot be closed with the command `close`.
A `close` without a number closes the current active plot window.
The gnuplot outboard driver, gnuplot_x11, is searched in a default place
chosen when the program is compiled. You can override that by defining
the environment variable GNUPLOT_DRIVER_DIR to point to a different
location.
Plot windows will automatically be closed at the end of the session
unless the `-persist` option was given.
The options `persist` and `raise` are unset by default, which means that
the defaults (persist == no and raise == yes) or the command line options
-persist / -raise or the Xresources are taken. If [no]persist or
[no]raise are specified, they will override command line options and
Xresources. Setting one of these options takes place immediately, so
the behaviour of an already running driver can be modified. If the window
does not get raised, see discussion in `raise`.
The option `replotonresize` (active by default) replots the data when the
plot window is resized. Without this option, the even-aspect-ratio scaling
may result in the plot filling only part of the window after resizing.
With this option, gnuplot does a full replot on each resize event, resulting
in better space utilization. This option is generally desirable, unless the
potentially CPU-intensive replotting during resizing is a concern. Replots
can be manually initiated with hotkey 'e' or the 'replot' command.
The option `title "<title name>"` will supply the title name of the window
for the current plot window or plot window <n> if a number is given.
Where (or if) this title is shown depends on your X window manager.
The size option can be used to set the size of the plot window. The
size option will only apply to newly created windows.
The position option can be used to set the position of the plot window. The
position option will only apply to newly created windows.
The size or aspect ratio of a plot may be changed by resizing the `gnuplot`
window.
Linewidths and pointsizes may be changed from within `gnuplot` with
`set linestyle`.
For terminal type `x11`, `gnuplot` accepts (when initialized) the standard
X Toolkit options and resources such as geometry, font, and name from the
command line arguments or a configuration file. See the X(1) man page
(or its equivalent) for a description of such options.
A number of other `gnuplot` options are available for the `x11` terminal.
These may be specified either as command-line options when `gnuplot` is
invoked or as resources in the configuration file ".Xdefaults". They are
set upon initialization and cannot be altered during a `gnuplot` session.
(except `persist` and `raise`)
?commands set terminal x11 x11_fonts
?set terminal x11 x11_fonts
?set term x11 x11_fonts
?x11 x11_fonts
?x11_fonts
Upon initial startup, the default font is taken from the X11 resources
as set in the system or user .Xdefaults file or on the command line.
Example:
gnuplot*font: lucidasans-bold-12
A new default font may be specified to the x11 driver from inside
gnuplot using
`set term x11 font "<fontspec>"`
The driver first queries the X-server for a font of the exact name given.
If this query fails, then it tries to interpret <fontspec> as
"<font>,<size>,<slant>,<weight>" and to construct a full X11 font name
of the form
-*-<font>-<weight>-<s>-*-*-<size>-*-*-*-*-*-<encoding>
<font> is the base name of the font (e.g. Times or Symbol)
<size> is the point size (defaults to 12 if not specified)
<s> is `i` if <slant>=="italic" `o` if <slant>=="oblique" `r` otherwise
<weight> is `medium` or `bold` if explicitly requested, otherwise `*`
<encoding> is set based on the current character set (see `set encoding`).
So `set term x11 font "arial,15,italic"` will be translated to
-*-arial-*-i-*-*-15-*-*-*-*-*-iso8859-1 (assuming default encoding).
The <size>, <slant>, and <weight> specifications are all optional.
If you do not specify <slant> or <weight> then you will get whatever font
variant the font server offers first.
You may set a default enconding via the corresponding X11 resource. E.g.
gnuplot*encoding: iso8859-15
The driver also recognizes some common PostScript font names and
replaces them with possible X11 or TrueType equivalents.
This same sequence is used to process font requests from `set label`.
If your gnuplot was built with configuration option --enable-x11-mbfonts,
you can specify multi-byte fonts by using the prefix "mbfont:" on the font
name. An additional font may be given, separated by a semicolon.
Since multi-byte font encodings are interpreted according to the locale
setting, you must make sure that the environmental variable LC_CTYPE is set
to some appropriate locale value such as ja_JP.eucJP, ko_KR.EUC, or zh_CN.EUC.
Example:
set term x11 font 'mbfont:kana14;k14'
# 'kana14' and 'k14' are Japanese X11 font aliases, and ';'
# is the separator of font names.
set term x11 font 'mbfont:fixed,16,r,medium'
# <font>,<size>,<slant>,<weight> form is also usable.
set title '(mb strings)' font 'mbfont:*-fixed-medium-r-normal--14-*'
The same syntax applies to the default font in Xresources settings,
for example,
gnuplot*font: \
mbfont:-misc-fixed-medium-r-normal--14-*-*-*-c-*-jisx0208.1983-0
If gnuplot is built with --enable-x11-mbfonts, you can use two special
PostScript font names 'Ryumin-Light-*' and 'GothicBBB-Medium-*' (standard
Japanese PS fonts) without the prefix "mbfont:".
?commands set terminal x11 command-line-options
?set terminal x11 command-line-options
?set term x11 command-line-options
?x11 command-line-options
?command-line-options
In addition to the X Toolkit options, the following options may be specified
on the command line when starting `gnuplot` or as resources in your
".Xdefaults" file (note that `raise` and `persist` can be overridden
later by `set term x11 [no]raise [no]persist)`:
`-mono` forces monochrome rendering on color displays.
`-gray` requests grayscale rendering on grayscale or color displays.
(Grayscale displays receive monochrome rendering by default.)
`-clear` requests that the window be cleared momentarily before a
new plot is displayed.
`-tvtwm` requests that geometry specifications for position of the
window be made relative to the currently displayed portion
of the virtual root.
`-raise` raises plot window after each plot
`-noraise` does not raise plot window after each plot
`-ctrlq ` closes window on ctrl-q rather than q
`-persist` plot windows survive after main gnuplot program exits
The options are shown above in their command-line syntax. When entered as
resources in ".Xdefaults", they require a different syntax.
Example:
gnuplot*gray: on
gnuplot*ctrlq: on
`gnuplot` also provides a command line option (`-pointsize <v>`) and a
resource, `gnuplot*pointsize: <v>`, to control the size of points plotted
with the `points` plotting style. The value `v` is a real number (greater
than 0 and less than or equal to ten) used as a scaling factor for point
sizes. For example, `-pointsize 2` uses points twice the default size, and
`-pointsize 0.5` uses points half the normal size.
The `-ctrlq` switch changes the hot-key that closes a plot window from `q`
to `<ctrl>q`. This is useful is you are using the keystroke-capture feature
`pause mouse keystroke`, since it allows the character `q` to be captured
just as all other alphanumeric characters. The `-ctrlq` switch similarly
replaces the <space> hot-key with <ctrl><space> for the same reason.
?set terminal x11 color_resources
?set term x11 color_resources
?x11 color_resources
NB: THIS SECTION IS LARGELY IRRELEVANT IN GNUPLOT VERSION 5
The X11 terminal honors the following resources (shown here with their
default values) or the greyscale resources. The values may be color names
as listed in the X11 rgb.txt file on your system, hexadecimal RGB color
specifications (see X11 documentation), or a color name followed by a comma
and an `intensity` value from 0 to 1. For example, `blue, 0.5` means a half
intensity blue.
gnuplot*background: white
gnuplot*textColor: black
gnuplot*borderColor: black
gnuplot*axisColor: black
gnuplot*line1Color: red
gnuplot*line2Color: green
gnuplot*line3Color: blue
gnuplot*line4Color: magenta
gnuplot*line5Color: cyan
gnuplot*line6Color: sienna
gnuplot*line7Color: orange
gnuplot*line8Color: coral
The command-line syntax for these is simple only for background,
which maps directly to the usual X11 toolkit option "-bg". All
others can only be set on the command line by use of the generic
"-xrm" resource override option
Examples:
gnuplot -background coral
to change the background color.
gnuplot -xrm 'gnuplot*line1Color:blue'
to override the first linetype color.
?commands set terminal x11 grayscale_resources
?set terminal x11 grayscale_resources
?set term x11 grayscale_resources
?x11 grayscale_resources
?grayscale_resources
When `-gray` is selected, `gnuplot` honors the following resources for
grayscale or color displays (shown here with their default values). Note
that the default background is black.
gnuplot*background: black
gnuplot*textGray: white
gnuplot*borderGray: gray50
gnuplot*axisGray: gray50
gnuplot*line1Gray: gray100
gnuplot*line2Gray: gray60
gnuplot*line3Gray: gray80
gnuplot*line4Gray: gray40
gnuplot*line5Gray: gray90
gnuplot*line6Gray: gray50
gnuplot*line7Gray: gray70
gnuplot*line8Gray: gray30
?set terminal x11 line_resources
?set term x11 line_resources
?x11 line_resources
NB: THIS SECTION IS LARGELY IRRELEVANT IN GNUPLOT VERSION 5
`gnuplot` honors the following resources for setting the width (in pixels) of
plot lines (shown here with their default values.) 0 or 1 means a minimal
width line of 1 pixel width. A value of 2 or 3 may improve the appearance of
some plots.
gnuplot*borderWidth: 1
gnuplot*axisWidth: 0
gnuplot*line1Width: 0
gnuplot*line2Width: 0
gnuplot*line3Width: 0
gnuplot*line4Width: 0
gnuplot*line5Width: 0
gnuplot*line6Width: 0
gnuplot*line7Width: 0
gnuplot*line8Width: 0
`gnuplot` honors the following resources for setting the dash style used for
plotting lines. 0 means a solid line. A two-digit number `jk` (`j` and `k`
are >= 1 and <= 9) means a dashed line with a repeated pattern of `j` pixels
on followed by `k` pixels off. For example, '16' is a dotted line with one
pixel on followed by six pixels off. More elaborate on/off patterns can be
specified with a four-digit value. For example, '4441' is four on, four off,
four on, one off. The default values shown below are for monochrome displays
or monochrome rendering on color or grayscale displays.
Color displays default to dashed:off
gnuplot*dashed: off
gnuplot*borderDashes: 0
gnuplot*axisDashes: 16
gnuplot*line1Dashes: 0
gnuplot*line2Dashes: 42
gnuplot*line3Dashes: 13
gnuplot*line4Dashes: 44
gnuplot*line5Dashes: 15
gnuplot*line6Dashes: 4441
gnuplot*line7Dashes: 42
gnuplot*line8Dashes: 13
?set terminal x11 pm3d_resources
?set term x11 pm3d_resources
?x11 pm3d_resources
?x11 pm3d
NB: THIS SECTION IS LARGELY IRRELEVANT IN GNUPLOT VERSION 5
Choosing the appropriate visual class and number of colors is a crucial
point in X11 applications and a bit awkward, since X11 supports six visual
types in different depths.
By default `gnuplot` uses the default visual of the screen. The number of
colors which can be allocated depends on the visual class chosen. On a
visual class with a depth > 12bit, gnuplot starts with a maximal number
of 0x200 colors. On a visual class with a depth > 8bit (but <= 12 bit)
the maximal number of colors is 0x100, on <= 8bit displays the maximum
number of colors is 240 (16 are left for line colors).
Gnuplot first starts to allocate the maximal number of colors as stated
above. If this fails, the number of colors is reduced by the factor 2
until gnuplot gets all colors which are requested. If dividing `maxcolors`
by 2 repeatedly results in a number which is smaller than `mincolors`
`gnuplot` tries to install a private colormap. In this case the window
manager is responsible for swapping colormaps when the pointer is moved
in and out the x11 driver's window.
The default for `mincolors` is maxcolors / (num_colormaps > 1 ? 2 : 8),
where num_colormaps is the number of colormaps which are currently used
by gnuplot (usually 1, if only one x11 window is open).
Some systems support multiple (different) visual classes together on one
screen. On these systems it might be necessary to force gnuplot to use a
specific visual class, e.g. the default visual might be 8bit PseudoColor
but the screen would also support 24bit TrueColor which would be the
preferred choice.
The information about an Xserver's capabilities can be obtained with the
program `xdpyinfo`. For the visual names below you can choose one of
StaticGray, GrayScale, StaticColor, PseudoColor, TrueColor, DirectColor.
If an Xserver supports a requested visual type at different depths,
`gnuplot` chooses the visual class with the highest depth (deepest).
If the requested visual class matches the default visual and multiple
classes of this type are supported, the default visual is preferred.
Example: on an 8bit PseudoColor visual you can force a private color map
by specifying `gnuplot*maxcolors: 240` and `gnuplot*mincolors: 240`.
gnuplot*maxcolors: <integer>
gnuplot*mincolors: <integer>
gnuplot*visual: <visual name>
?commands set terminal x11 other_resources
?set terminal x11 other_resources
?set term x11 other_resources
?x11 other_resources
By default the contents of the current plot window are exported to the X11
clipboard in response to X events in the window. Setting the resource
'gnuplot*exportselection' to 'off' or 'false' will disable this.
By default text rotation is done using a method that is fast, but can
corrupt nearby colors depending on the background. If this is a problem,
you can set the resource 'gnuplot.fastrotate' to 'off'
gnuplot*exportselection: off
gnuplot*fastrotate: on
gnuplot*ctrlq: off
?commands set terminal xlib
?set terminal xlib
?set term xlib
?terminal xlib
?term xlib
?xlib
The `xlib` terminal driver supports the X11 Windows System. It generates
gnuplot_x11 commands, but sends them to the output file specified by
`set output '<filename>'`. `set term x11` is equivalent to
`set output "|gnuplot_x11 -noevents"; set term xlib`.
`xlib` takes the same set of options as `x11`.
?commands set terminal canvas
?set terminal canvas
?set term canvas
?terminal canvas
?term canvas
The `canvas` terminal creates a set of javascript commands that draw onto the
HTML5 canvas element.
Syntax:
set terminal canvas {size <xsize>, <ysize>} {background <rgb_color>}
{font {<fontname>}{,<fontsize>}} | {fsize <fontsize>}
{{no}enhanced} {linewidth <lw>}
{rounded | butt | square}
{dashlength <dl>}
{standalone {mousing} | name '<funcname>'}
{jsdir 'URL/for/javascripts'}
{title '<some string>'}
where <xsize> and <ysize> set the size of the plot area in pixels.
The default size in standalone mode is 600 by 400 pixels.
The default font size is 10.
NB: Only one font is available, the ascii portion of Hershey simplex Roman
provided in the file canvastext.js. You can replace this with the file
canvasmath.js, which contains also UTF-8 encoded Hershey simplex Greek and
math symbols. For consistency with other terminals, it is also possible to
use `font "name,size"`. Currently the font `name` is ignored, but browser
support for named fonts is likely to arrive eventually.
The default `standalone` mode creates an html page containing javascript
code that renders the plot using the HTML 5 canvas element. The html page
links to two required javascript files 'canvastext.js' and 'gnuplot_common.js'.
An additional file 'gnuplot_dashedlines.js' is needed to support dashed lines.
By default these point to local files, on unix-like systems usually in
directory /usr/local/share/gnuplot/<version>/js. See installation notes for
other platforms. You can change this by using the `jsdir` option to specify
either a different local directory or a general URL. The latter is usually
appropriate if the plot is exported for viewing on remote client machines.
All plots produced by the canvas terminal are mouseable. The additional
keyword `mousing` causes the `standalone` mode to add a mouse-tracking box
underneath the plot. It also adds a link to a javascript file
'gnuplot_mouse.js' and to a stylesheet for the mouse box 'gnuplot_mouse.css'
in the same local or URL directory as 'canvastext.js'.
The `name` option creates a file containing only javascript. Both the
javascript function it contains and the id of the canvas element that it
draws onto are taken from the following string parameter. The commands
set term canvas name 'fishplot'
set output 'fishplot.js'
will create a file containing a javascript function fishplot() that will
draw onto a canvas with id=fishplot. An html page that invokes this
javascript function must also load the canvastext.js function as described
above. A minimal html file to wrap the fishplot created above might be:
<html>
<head>
<script src="canvastext.js"></script>
<script src="gnuplot_common.js"></script>
</head>
<body onload="fishplot();">
<script src="fishplot.js"></script>
<canvas id="fishplot" width=600 height=400>
<div id="err_msg">No support for HTML 5 canvas element</div>
</canvas>
</body>
</html>
The individual plots drawn on this canvas will have names fishplot_plot_1,
fishplot_plot_2, and so on. These can be referenced by external javascript
routines, for example gnuplot.toggle_visibility("fishplot_plot_2").
?commands set terminal cgm
?set terminal cgm
?set term cgm
?terminal cgm
?term cgm
?cgm
The `cgm` terminal generates a Computer Graphics Metafile, Version 1.
This file format is a subset of the ANSI X3.122-1986 standard entitled
"Computer Graphics - Metafile for the Storage and Transfer of Picture
Description Information".
Syntax:
set terminal cgm {color | monochrome} {solid | dashed} {{no}rotate}
{<mode>} {width <plot_width>} {linewidth <line_width>}
{font "<fontname>,<fontsize>"}
{background <rgb_color>}
[deprecated] {<color0> <color1> <color2> ...}
`solid` draws all curves with solid lines, overriding any dashed patterns;
<mode> is `landscape`, `portrait`, or `default`;
<plot_width> is the assumed width of the plot in points;
<line_width> is the line width in points (default 1);
<fontname> is the name of a font (see list of fonts below)
<fontsize> is the size of the font in points (default 12).
The first six options can be in any order. Selecting `default` sets all
options to their default values.
The mechanism of setting line colors in the `set term` command is
deprecated. Instead you should set the background using a separate
keyword and set the line colors using `set linetype`.
The deprecated mechanism accepted colors of the form 'xrrggbb', where x is
the literal character 'x' and 'rrggbb' are the red, green and blue components
in hex. The first color was used for the background, subsequent colors are
assigned to successive line types.
Examples:
set terminal cgm landscape color rotate dashed width 432 \
linewidth 1 'Helvetica Bold' 12 # defaults
set terminal cgm linewidth 2 14 # wider lines & larger font
set terminal cgm portrait "Times Italic" 12
set terminal cgm color solid # no pesky dashes!
?commands set terminal cgm font
?set terminal cgm font
?set term cgm font
?cgm font
The first part of a Computer Graphics Metafile, the metafile description,
includes a font table. In the picture body, a font is designated by an
index into this table. By default, this terminal generates a table with
the following 35 fonts, plus six more with `italic` replaced by
`oblique`, or vice-versa (since at least the Microsoft Office and Corel
Draw CGM import filters treat `italic` and `oblique` as equivalent):
Helvetica
Helvetica Bold
Helvetica Oblique
Helvetica Bold Oblique
Times Roman
Times Bold
Times Italic
Times Bold Italic
Courier
Courier Bold
Courier Oblique
Courier Bold Oblique
Symbol
Hershey/Cartographic_Roman
Hershey/Cartographic_Greek
Hershey/Simplex_Roman
Hershey/Simplex_Greek
Hershey/Simplex_Script
Hershey/Complex_Roman
Hershey/Complex_Greek
Hershey/Complex_Script
Hershey/Complex_Italic
Hershey/Complex_Cyrillic
Hershey/Duplex_Roman
Hershey/Triplex_Roman
Hershey/Triplex_Italic
Hershey/Gothic_German
Hershey/Gothic_English
Hershey/Gothic_Italian
Hershey/Symbol_Set_1
Hershey/Symbol_Set_2
Hershey/Symbol_Math
ZapfDingbats
Script
15
The first thirteen of these fonts are required for WebCGM. The
Microsoft Office CGM import filter implements the 13 standard fonts
listed above, and also 'ZapfDingbats' and 'Script'. However, the
script font may only be accessed under the name '15'. For more on
Microsoft import filter font substitutions, check its help file which
you may find here:
C:\Program Files\Microsoft Office\Office\Cgmimp32.hlp
and/or its configuration file, which you may find here:
C:\Program Files\Common Files\Microsoft Shared\Grphflt\Cgmimp32.cfg
In the `set term` command, you may specify a font name which does not
appear in the default font table. In that case, a new font table is
constructed with the specified font as its first entry. You must ensure
that the spelling, capitalization, and spacing of the name are
appropriate for the application that will read the CGM file. (Gnuplot
and any MIL-D-28003A compliant application ignore case in font names.)
If you need to add several new fonts, use several `set term` commands.
Example:
set terminal cgm 'Old English'
set terminal cgm 'Tengwar'
set terminal cgm 'Arabic'
set output 'myfile.cgm'
plot ...
set output
You cannot introduce a new font in a `set label` command.
?commands set terminal cgm fontsize
?set terminal cgm fontsize
?set term cgm fontsize
?cgm fontsize
Fonts are scaled assuming the page is 6 inches wide. If the `size`
command is used to change the aspect ratio of the page or the CGM file
is converted to a different width, the resulting font sizes will be
scaled up or down accordingly. To change the assumed width, use the
`width` option.
?commands set terminal cgm linewidth
?set terminal cgm linewidth
?set term cgm linewidth
?cgm linewidth
The `linewidth` option sets the width of lines in pt. The default width
is 1 pt. Scaling is affected by the actual width of the page, as
discussed under the `fontsize` and `width` options.
?commands set terminal cgm rotate
?set terminal cgm rotate
?set term cgm rotate
?cgm rotate
The `norotate` option may be used to disable text rotation. For
example, the CGM input filter for Word for Windows 6.0c can accept
rotated text, but the DRAW editor within Word cannot. If you edit a
graph (for example, to label a curve), all rotated text is restored to
horizontal. The Y axis label will then extend beyond the clip boundary.
With `norotate`, the Y axis label starts in a less attractive location,
but the page can be edited without damage. The `rotate` option confirms
the default behavior.
?set terminal cgm solid
?set term cgm solid
?cgm solid
The `solid` option may be used to disable dashed line styles in the
plots. This is useful when color is enabled and the dashing of the
lines detracts from the appearance of the plot. The `dashed` option
confirms the default behavior, which gives a different dash pattern to
each line type.
?commands set terminal cgm size
?set terminal cgm size
?set term cgm size
?cgm size
Default size of a CGM plot is 32599 units wide and 23457 units high for
landscape, or 23457 units wide by 32599 units high for portrait.
?commands set terminal cgm width
?set terminal cgm width
?set term cgm width
?cgm width
All distances in the CGM file are in abstract units. The application
that reads the file determines the size of the final plot. By default,
the width of the final plot is assumed to be 6 inches (15.24 cm). This
distance is used to calculate the correct font size, and may be changed
with the `width` option. The keyword should be followed by the width in
points. (Here, a point is 1/72 inch, as in PostScript. This unit is
known as a "big point" in TeX.) Gnuplot `expressions` can be used to
convert from other units.
Example:
set terminal cgm width 432 # default
set terminal cgm width 6*72 # same as above
set terminal cgm width 10/2.54*72 # 10 cm wide
?commands set terminal cgm nofontlist
?set terminal cgm nofontlist
?set term cgm nofontlist
?cgm nofontlist
?set terminal cgm winword6
?set term cgm winword6
?cgm winword6
The default font table includes the fonts recommended for WebCGM, which
are compatible with the Computer Graphics Metafile input filter for
Microsoft Office and Corel Draw. Another application might use
different fonts and/or different font names, which may not be
documented. The `nofontlist` (synonym `winword6`) option deletes the font
table from the CGM file. In this case, the reading application should
use a default table. Gnuplot will still use its own default font table
to select font indices. Thus, 'Helvetica' will give you an index of 1,
which should get you the first entry in your application's default font
table. 'Helvetica Bold' will give you its second entry, etc.
?commands set terminal dumb
?set terminal dumb
?set term dumb
?terminal dumb
?term dumb
?dumb
The `dumb` terminal driver plots into a text block using ascii characters.
It has an optional size specification and a trailing linefeed flag.
Syntax:
set terminal dumb {size <xchars>,<ychars>} {[no]feed}
{aspect <htic>{,<vtic>}}
{[no]enhanced}
{mono|ansi|ansi256|ansirgb}
where <xchars> and <ychars> set the size of the text block. The default is
79 by 24. The last newline is printed only if `feed` is enabled.
The `aspect` option can be used to control the aspect ratio of the plot by
setting the length of the horizontal and vertical tic marks. Only integer
values are allowed. Default is 2,1 -- corresponding to the aspect ratio of
common screen fonts.
The `ansi`, `ansi256`, and `ansirgb` options will include escape
sequences in the output to handle colors. Note that these might
not be handled by your terminal. Default is `mono`.
To obtain the best color match in `ansi` mode, you should use
`set colorsequence classic`.
Depending on the mode, the `dumb` terminal will emit the
folowing sequences (without the additional whitespace):
ESC [ 0 m reset attributes to defaults
foreground color:
ESC [ 1 m set intense/bold
ESC [ 22 m intense/bold off
ESC [ <fg> m with color code 30 <= <fg> <= 37
ESC [ 39 m reset to default
ESC [ 38; 5; <c> m with palette index 16 <= <c> <= 255
ESC [ 38; 2; <r>; <g>; <b> m with components 0 <= <r,g,b> <= 255
background color:
ESC [ <bg> m with color code 40 <= <bg> <= 47
ESC [ 49 m reset to default
ESC [ 48; 5; <c> m with palette index 16 <= <c> <= 231
ESC [ 48; 2; <r>; <g>; <b> m with components 0 <= <r,g,b> <= 255
See also e.g. the description at
https://en.wikipedia.org/wiki/ANSI_escape_code#Colors
Example:
set term dumb mono size 60,15 aspect 1
set tics nomirror scale 0.5
plot [-5:6.5] sin(x) with impulse ls -1
1 +-------------------------------------------------+
0.8 +|||++ ++||||++ |
0.6 +|||||+ ++|||||||+ sin(x) +----+ |
0.4 +||||||+ ++|||||||||+ |
0.2 +|||||||+ ++|||||||||||+ +|
0 ++++++++++++++++++++++++++++++++++++++++++++++++++|
-0.2 + +|||||||||||+ +|||||||||||+ |
-0.4 + +|||||||||+ +|||||||||+ |
-0.6 + +|||||||+ +|||||||+ |
-0.8 + ++||||+ ++||||+ |
-1 +---+--------+--------+-------+--------+--------+-+
-4 -2 0 2 4 6
?commands set terminal dxf
?set terminal dxf
?set term dxf
?terminal dxf
?term dxf
?dxf
Terminal driver `dxf` for export to AutoCad (Release 10.x).
It has no options. The default size is 120x80 AutoCad units.
`dxf` uses seven colors (white, red, yellow, green, cyan, blue and magenta)
that can be changed only by modifying the source file. If a black-and-white
plotting device is used the colors are mapped to differing line thicknesses.
Note: someone please update to use the 2012 DXF standard!
?commands set terminal emf
?set terminal emf
?set term emf
?terminal emf
?term emf
?emf
The `emf` terminal generates an Enhanced Metafile Format file.
This file format is recognized by many Windows applications.
Syntax:
set terminal emf {color | monochrome}
{enhanced {noproportional}}
{rounded | butt}
{linewidth <LW>} {dashlength <DL>}
{size XX,YY} {background <rgb_color>}
{font "<fontname>{,<fontsize>}"}
{fontscale <scale>}
In `monochrome` mode successive line types cycle through dash patterns.
`linewidth <factor>` multiplies all line widths by this factor.
`dashlength <factor>` is useful for thick lines.
<fontname> is the name of a font; and
`<fontsize>` is the size of the font in points.
The nominal size of the output image defaults to 1024x768 in arbitrary
units. You may specify a different nominal size using the `size` option.
Enhanced text mode tries to approximate proportional character spacing.
If you are using a monospaced font, or don't like the approximation, you
can turn off this correction using the `noproportional` option.
The default settings are `color font "Arial,12" size 1024,768`
Selecting `default` sets all options to their default values.
Examples:
set terminal emf 'Times Roman Italic, 12'
?commands set terminal fig
?set terminal fig
?set term fig
?terminal fig
?term fig
?fig
?xfig
The `fig` terminal device generates output in the Fig graphics language.
Syntax:
set terminal fig {monochrome | color}
{landscape | portrait}
{small | big | size <xsize> <ysize>}
{metric | inches}
{pointsmax <max_points>}
{solid | dashed}
{font "<fontname>{,<fontsize>}"}
{textnormal | {textspecial texthidden textrigid}}
{{thickness|linewidth} <units>}
{depth <layer>}
{version <number>}
`monochrome` and `color` determine whether the picture is black-and-white or
`color`. `small` and `big` produce a 5x3 or 8x5 inch graph in the default
`landscape` mode and 3x5 or 5x8 inches in `portrait` mode.
`size` sets (overrides) the size of the drawing
area to <xsize>*<ysize> in units of inches or centimeters depending on the
`inches` or `metric` setting in effect.
The latter settings is also used as default units for editing with "xfig".
`pointsmax <max_points>` sets the maximum number of points per polyline.
`solid` inhibits automatic usage of `dash`ed lines when solid linestyles are
used up, which otherwise occurs.
`font` sets the text font face to <fontname> and its size to <fontsize>
points. `textnormal` resets the text flags and selects postscript fonts,
`textspecial` sets the text flags for LaTeX specials, `texthidden` sets the
hidden flag and `textrigid` the rigid flag.
`depth` sets the default depth layer for all lines and text. The default
depth is 10 to leave room for adding material with "xfig" on top of the
plot.
`version` sets the format version of the generated fig output. Currently
only versions 3.1 and 3.2 are supported.
`thickness` sets the default line thickness, which is 1 if not specified.
Overriding the thickness can be achieved by adding a multiple of 100 to the
`linetype` value for a `plot` command. In a similar way the `depth`
of plot elements (with respect to the default depth) can be controlled by
adding a multiple of 1000 to <linetype>. The depth is then <layer> +
<linetype>/1000 and the thickness is (<linetype>%1000)/100 or, if that is
zero, the default line thickness. `linewidth` is a synonym for `thickness`.
Additional point-plot symbols are also available with the `fig` driver. The
symbols can be used through `pointtype` values % 100 above 50, with different
fill intensities controlled by <pointtype> % 5 and outlines in black (for
<pointtype> % 10 < 5) or in the current color. Available symbols are
50 - 59: circles
60 - 69: squares
70 - 79: diamonds
80 - 89: upwards triangles
90 - 99: downwards triangles
The size of these symbols is linked to the font size. The depth of symbols
is by default one less than the depth for lines to achieve nice error bars.
If <pointtype> is above 1000, the depth is <layer> + <pointtype>/1000-1. If
<pointtype>%1000 is above 100, the fill color is (<pointtype>%1000)/100-1.
Available fill colors are (from 1 to 9): black, blue, green, cyan, red,
magenta, yellow, white and dark blue (in monochrome mode: black for 1 to 6
and white for 7 to 9).
See `plot with` for details of <linetype> and <pointtype>.
The `big` option is a substitute for the `bfig` terminal in earlier versions,
which is no longer supported.
Examples:
set terminal fig monochrome small pointsmax 1000 # defaults
plot 'file.dat' with points linetype 102 pointtype 759
would produce circles with a blue outline of width 1 and yellow fill color.
plot 'file.dat' using 1:2:3 with err linetype 1 pointtype 554
would produce errorbars with black lines and circles filled red. These
circles are one layer above the lines (at depth 9 by default).
To plot the error bars on top of the circles use
plot 'file.dat' using 1:2:3 with err linetype 1 pointtype 2554
?commands set terminal hpgl
?set terminal hpgl
?set term hpgl
?terminal hpgl
?term hpgl
?hpgl
?commands set terminal pcl5
?set terminal pcl5
?set term pcl5
?terminal pcl5
?term pcl5
?pcl5
The `hpgl` driver produces HPGL output for devices like the HP7475A plotter.
There are two options which can be set: the number of pens and `eject`,
which tells the plotter to eject a page when done. The default is to use 6
pens and not to eject the page when done.
The international character sets ISO-8859-1 and CP850 are recognized via
`set encoding iso_8859_1` or `set encoding cp850` (see `set encoding` for
details).
Syntax:
set terminal hpgl {<number_of_pens>} {eject}
The selection
set terminal hpgl 8 eject
is equivalent to the previous `hp7550` terminal, and the selection
set terminal hpgl 4
is equivalent to the previous `hp7580b` terminal.
The `pcl5` driver supports plotters such as the Hewlett-Packard Designjet
750C, the Hewlett-Packard Laserjet III, and the Hewlett-Packard Laserjet IV.
It actually uses HPGL-2, but there is a name conflict among the terminal
devices. It has several options which must be specified in the order
indicated below:
Syntax:
set terminal pcl5 {mode <mode>} {<plotsize>}
{{color {<number_of_pens>}} | monochrome} {solid | dashed}
{font <font>} {size <fontsize>} {pspoints | nopspoints}
<mode> is `landscape` or `portrait`. <plotsize> is the physical
plotting size of the plot, which is one of the following: `letter` for
standard (8 1/2" X 11") displays, `legal` for (8 1/2" X 14") displays,
`noextended` for (36" X 48") displays (a letter size ratio) or,
`extended` for (36" X 55") displays (almost a legal size ratio).
`color` is for multi-pen (i.e. color) plots, and <number_of_pens> is
the number of pens (i.e. colors) used in color plots. `monochrome` is for
one (e.g. black) pen plots. `solid` draws all lines as solid lines, or
`dashed` will draw lines with different dashed and dotted line patterns.
<font> is `stick`, `univers`, `cg_times`, `zapf_dingbats`, `antique_olive`,
`arial`, `courier`, `garamond_antigua`, `letter_gothic`, `cg_omega`,
`albertus`, `times_new_roman`, `clarendon`, `coronet`, `marigold`,
`truetype_symbols`, or `wingdings`. <fontsize> is the font size in points.
The point type selection can be the standard default set by specifying
`nopspoints`, or the same set of point types found in the postscript terminal
by specifying `pspoints`.
Note that built-in support of some of these options is printer device
dependent. For instance, all the fonts are supposedly supported by the HP
Laserjet IV, but only a few (e.g. univers, stick) may be supported by the HP
Laserjet III and the Designjet 750C. Also, color obviously won't work on the
the laserjets since they are monochrome devices.
Defaults: landscape, noextended, color (6 pens), solid, univers, 12 point,
and nopspoints.
With `pcl5` international characters are handled by the printer; you just put
the appropriate 8-bit character codes into the text strings. You don't need
to bother with `set encoding`.
HPGL graphics can be imported by many software packages.
?commands set terminal png
?set terminal png
?set term png
?terminal png
?term png
?png
Syntax:
set terminal png
{{no}enhanced}
{{no}transparent} {{no}interlace}
{{no}truecolor} {rounded|butt}
{linewidth <lw>} {dashlength <dl>}
{tiny | small | medium | large | giant}
{font "<face> {,<pointsize>}"} {fontscale <scale>}
{size <x>,<y>} {{no}crop}
{background <rgb_color>}
PNG, JPEG and GIF images are created using the external library libgd.
PNG plots may be viewed interactively by piping the output to the
'display' program from the ImageMagick package as follows:
set term png
set output '| display png:-'
You can view the output from successive plot commands interactively by typing
<space> in the display window. To save the current plot to a file,
left click in the display window and choose `save`.
`transparent` instructs the driver to make the background color transparent.
Default is `notransparent`.
`interlace` instructs the driver to generate interlaced PNGs.
Default is `nointerlace`.
The `linewidth` and `dashlength` options are scaling factors that affect all
lines drawn, i.e. they are multiplied by values requested in various drawing
commands.
By default output png images use 256 indexed colors. The `truecolor` option
instead creates TrueColor images with 24 bits of color information per pixel.
Transparent fill styles require the `truecolor` option. See `fillstyle`.
A transparent background is possible in either indexed or TrueColor images.
`butt` instructs the driver to use a line drawing method that does
not overshoot the desired end point of a line. This setting is only
applicable for line widths greater than 1. This setting is most useful when
drawing horizontal or vertical lines. Default is `rounded`.
The details of font selection are complicated.
Two equivalent simple examples are given below:
set term png font arial 11
set term png font "arial,11"
For more information please see the separate section under `fonts`.
The output plot size <x,y> is given in pixels---it defaults to 640x480.
Please see additional information under `canvas` and `set size`.
Blank space at the edges of the finished plot may be trimmed using the `crop`
option, resulting in a smaller final image size. Default is `nocrop`.
?set term png examples
set terminal png medium size 640,480 background '#ffffff'
Use the medium size built-in non-scaleable, non-rotatable font.
Use white (24-bit RGB in hexadecimal) for the non-transparent background.
set terminal png font arial 14 size 800,600
Searches for a scalable font with face name 'arial' and sets the font
size to 14pt. Please see `fonts` for details of how the font search
is done.
set terminal png transparent truecolor enhanced
Use 24 bits of color information per pixel, with a transparent background.
Use the `enhanced text` mode to control the layout of strings to be printed.
?commands set terminal jpeg
?set terminal jpeg
?set term jpeg
?terminal jpeg
?term jpeg
?jpeg
Syntax:
set terminal jpeg
{{no}enhanced}
{{no}interlace}
{linewidth <lw>} {dashlength <dl>} {rounded|butt}
{tiny | small | medium | large | giant}
{font "<face> {,<pointsize>}"} {fontscale <scale>}
{size <x>,<y>} {{no}crop}
{background <rgb_color>}
PNG, JPEG and GIF images are created using the external library libgd.
In most cases, PNG is to be preferred for single plots, and GIF for
animations. Both are loss-less image formats, and produce better image
quality than the lossy JPEG format. This is in particular noticeable
for solid color lines against a solid background, i.e. exactly the sort
of image typically created by gnuplot.
The `interlace` option creates a progressive JPEG image.
Default is `nointerlace`.
The `linewidth` and `dashlength` options are scaling factors that affect all
lines drawn, i.e. they are multiplied by values requested in various drawing
commands.
`butt` instructs the driver to use a line drawing method that does
not overshoot the desired end point of a line. This setting is only
applicable for line widths greater than 1. This setting is most useful when
drawing horizontal or vertical lines. Default is `rounded`.
The details of font selection are complicated.
Two equivalent simple examples are given below:
set term jpeg font arial 11
set term jpeg font "arial,11"
For more information please see the separate section under `fonts`.
The output plot size <x,y> is given in pixels---it defaults to 640x480.
Please see additional information under `canvas` and `set size`.
Blank space at the edges of the finished plot may be trimmed using the `crop`
option, resulting in a smaller final image size. Default is `nocrop`.
?commands set terminal gif
?set terminal gif
?set term gif
?terminal gif
?term gif
?gif
Syntax:
set terminal gif
{{no}enhanced}
{{no}transparent} {rounded|butt}
{linewidth <lw>} {dashlength <dl>}
{tiny | small | medium | large | giant}
{font "<face> {,<pointsize>}"} {fontscale <scale>}
{size <x>,<y>} {{no}crop}
{animate {delay <d>} {loop <n>} {{no}optimize}}
{background <rgb_color>}
PNG, JPEG and GIF images are created using the external library libgd.
GIF plots may be viewed interactively by piping the output to the
'display' program from the ImageMagick package as follows:
set term gif
set output '| display gif:-'
You can view the output from successive plot commands interactively by typing
<space> in the display window. To save the current plot to a file,
left click in the display window and choose `save`.
`transparent` instructs the driver to make the background color transparent.
Default is `notransparent`.
The `linewidth` and `dashlength` options are scaling factors that affect all
lines drawn, i.e. they are multiplied by values requested in various drawing
commands.
`butt` instructs the driver to use a line drawing method that does
not overshoot the desired end point of a line. This setting is only
applicable for line widths greater than 1. This setting is most useful when
drawing horizontal or vertical lines. Default is `rounded`.
The details of font selection are complicated.
Two equivalent simple examples are given below:
set term gif font arial 11
set term gif font "arial,11"
For more information please see the separate section under `fonts`.
The `animate` option is available only if your local gd library supports
the creation of animated gifs. The default delay between display of
successive images may be specified in units of 1/100 second (default 5).
The actual delay may vary depending on the program used as a viewer.
Number of animation loops can be specified, default 0 means infinity.
An animation sequence is terminated by the next `set output` or `set term`
command. The `optimize` option has two effects on the animation.
1) A single color map is used for the entire animation. This requires
that all colors used in any frame of the animation are already
defined in the first frame.
2) If possible, only the portions of a frame that differ from the
previous frame are stored in the animation file. This space saving
may not be possible if the animation uses transparency.
Both of these optimizations are intended to produce a smaller output file,
but the decrease in size is probably only significant for long animations
or very small frame sizes.
The `nooptimize` option turns off both of the effects just described.
Each frame is stored in its entirety along with a private color map.
Note that it is possible to post-process a non-optimized animation
using external utilities, and this post-processing can yield a smaller
file than gnuplot's internal optimization mode.
The default is `nooptimize`.
The output plot size <x,y> is given in pixels---it defaults to 640x480.
Please see additional information under `canvas` and `set size`.
Blank space at the edges of the finished plot may be trimmed using the `crop`
option, resulting in a smaller final image size. Default is `nocrop`.
?set term gif examples
set terminal gif medium size 640,480 background '#ffffff'
Use the medium size built-in non-scaleable, non-rotatable font.
Use white (24 bit RGB in hexadecimal) for the non-transparent background.
set terminal gif font arial 14 enhanced
Searches for a scalable font with face name 'arial' and sets the font
size to 14pt. Please see `fonts` for details of how the font search
is done. Because this is a scalable font, we can use enhanced text mode.
set term gif animate transparent opt delay 10 size 200,200
load "animate2.dem"
Open the gif terminal for creation of an animated gif file. The individual
frames of the animation sequence are created by the script file animate2.dem
from the standard collection of demos.
?commands set terminal sixelgd
?set terminal sixelgd
?set term sixelgd
?terminal sixelgd
?term sixelgd
?sixelgd
Syntax:
set terminal sixelgd
{{no}enhanced}
{{no}transparent} {rounded|butt}
{linewidth <lw>} {dashlength <dl>}
{tiny | small | medium | large | giant}
{font "<face> {,<pointsize>}"} {fontscale <scale>}
{size <x>,<y>} {{no}crop} {animate}
{background <rgb_color>}
The `sixel` output format was originally used by DEC terminals and printers.
This driver produces a sixel output stream by converting a PNG image created
internally using the gd library. The sixel output stream can be viewed in the
terminal as it is created or it can be written to a file so that it can be
replayed later by echoing the file to the terminal.
The `animate` option resets the cursor position to the terminal top left at
the start of every plot so that successive plots overwrite the same area on
the screen rather than having earlier plots scroll off the top. This may be
desirable in order to create an in-place animation.
`transparent` instructs the driver to make the background color transparent.
Default is `notransparent`.
The `linewidth` and `dashlength` options are scaling factors that affect all
lines drawn, i.e. they are multiplied by values requested in various drawing
commands.
By default the sixel output uses 16 indexed colors. The `truecolor` option
instead creates a TrueColor png image that is mapped down onto 256 colors
in the output sixel image. Transparent fill styles require the `truecolor`
option. See `fillstyle`.
A `transparent` background is possible in either indexed or TrueColor images.
`butt` instructs the driver to use a line drawing method that does
not overshoot the desired end point of a line. This setting is only
applicable for line widths greater than 1. This setting is most useful when
drawing horizontal or vertical lines. Default is `rounded`.
The details of font selection are complicated.
For more information please see `fonts`.
The output plot size <x,y> is given in pixels---it defaults to 640x480.
Please see additional information under `canvas` and `set size`.
Blank space at the edges of the finished plot may be trimmed using the `crop`
option, resulting in a smaller final image size. Default is `nocrop`.
The terminal has been sucessfully tested with the xterm, mlterm and mintty
terminals. The later two support the `truecolor` mode using 256 sixel
colors out of box. Distributed copies of xterm may or may not have been
configured to support sixel graphics and 256 colors.
?commands set terminal epslatex
?set terminal epslatex
?set term epslatex
?terminal epslatex
?term epslatex
?epslatex
The `epslatex` driver generates output for further processing by LaTeX.
Syntax:
set terminal epslatex {default}
set terminal epslatex {standalone | input}
{oldstyle | newstyle}
{level1 | leveldefault | level3}
{color | colour | monochrome}
{background <rgbcolor> | nobackground}
{dashlength | dl <DL>}
{linewidth | lw <LW>} {pointscale | ps <PS>}
{rounded | butt}
{clip | noclip}
{palfuncparam <samples>{,<maxdeviation>}}
{size <XX>{unit},<YY>{unit}}
{header <header> | noheader}
{blacktext | colortext | colourtext}
{{font} "fontname{,fontsize}" {<fontsize>}}
{fontscale <scale>}
The epslatex terminal prints a plot as `terminal postscript eps`
but transfers the texts to LaTeX instead of including in the PostScript
code. Thus, many options are the same as in the `postscript terminal`.
The appearance of the epslatex terminal changed between versions 4.0 and 4.2
to reach better consistency with the postscript terminal:
The plot size has been changed from 5 x 3 inches to 5 x 3.5 inches;
the character width is now estimated to be 60% of the font size
while the old epslatex terminal used 50%; now, the larger number of
postscript linetypes and symbols are used. To reach an appearance that is
nearly identical to the old one specify the option `oldstyle`. (In fact
some small differences remain: the symbol sizes are slightly different, the
tics are half as large as in the old terminal which can be changed using
`set tics scale`, and the arrows have all features as in the postscript
terminal.)
If you see the error message
"Can't find PostScript prologue file ... "
Please see and follow the instructions in `postscript prologue`.
The option `color` enables color, while `monochrome` prefers black and white
drawing elements. Further, `monochrome` uses gray `palette` but it does not
change color of objects specified with an explicit `colorspec`.
`dashlength` or `dl` scales the length of dashed-line segments by <DL>,
which is a floating-point number greater than zero.
`linewidth` or `lw` scales all linewidths by <LW>.
By default the generated PostScript code uses language features that were
introduced in PostScript Level 2, notably filters and pattern-fill of
irregular objects such as filledcurves. PostScript Level 2 features are
conditionally protected so that PostScript Level 1 interpreters do not issue
errors but, rather, display a message or a PostScript Level 1 approximation.
The `level1` option substitutes PostScript Level 1 approximations of these
features and uses no PostScript Level 2 code. This may be required by some
old printers and old versions of Adobe Illustrator. The flag `level1` can be
toggled later by editing a single line in the PostScript output file to force
PostScript Level 1 interpretation. In the case of files containing level 2
code, the above features will not appear or will be replaced by a note when
this flag is set or when the interpreting program does not indicate that it
understands level 2 PostScript or higher. The flag `level3` enables PNG
encoding for bitmapped images, which can reduce the output size considerably.
`rounded` sets line caps and line joins to be rounded; `butt` is the
default, butt caps and mitered joins.
`clip` tells PostScript to clip all output to the bounding box;
`noclip` is the default.
`palfuncparam` controls how `set palette functions` are encoded as gradients
in the output. Analytic color component functions (set via
`set palette functions`) are encoded as linear interpolated gradients in the
postscript output: The color component functions are sampled at <samples>
points and all points are removed from this gradient which can be removed
without changing the resulting colors by more than <maxdeviation>. For
almost every useful palette you may safely leave the defaults of
<samples>=2000 and <maxdeviation>=0.003 untouched.
The default size for postscript output is 10 inches x 7 inches. The default
for eps output is 5 x 3.5 inches. The `size` option changes this to
whatever the user requests. By default the X and Y sizes are taken to be in
inches, but other units are possibly (currently only cm). The BoundingBox
of the plot is correctly adjusted to contain the resized image.
Screen coordinates always run from 0.0 to 1.0 along the full length of the
plot edges as specified by the `size` option.
NB: `this is a change from the previously recommended method of using the
set size command prior to setting the terminal type`. The old method left
the BoundingBox unchanged and screen coordinates did not correspond to the
actual limits of the plot.
`blacktext` forces all text to be written in black even in color mode;
The epslatex driver offers a special way of controlling text positioning:
(a) If any text string begins with '{', you also need to include a '}' at the
end of the text, and the whole text will be centered both horizontally
and vertically by LaTeX. (b) If the text string begins with '[', you need
to continue it with: a position specification (up to two out of t,b,l,r,c),
']{', the text itself, and finally, '}'. The text itself may be anything
LaTeX can typeset as an LR-box. \rule{}{}'s may help for best positioning.
See also the documentation for the `pslatex` terminal driver.
To create multiline labels, use \shortstack, for example
set ylabel '[r]{\shortstack{first line \\ second line}}'
The `back` option of `set label` commands is handled slightly different
than in other terminals. Labels using 'back' are printed behind all other
elements of the plot while labels using 'front' are printed above
everything else.
The driver produces two different files, one for the eps part of the figure
and one for the LaTeX part. The name of the LaTeX file is taken from the
`set output` command. The name of the eps file is derived by replacing
the file extension (normally `.tex`) with `.eps` instead. There is no
LaTeX output if no output file is given! Remember to close the
`output file` before next plot unless in `multiplot` mode.
In your LaTeX documents use '\input{filename}' to include the figure.
The `.eps` file is included by the command \includegraphics{...}, so you
must also include \usepackage{graphicx} in the LaTeX preamble. If you
want to use coloured text (option `textcolour`) you also have to include
\usepackage{color} in the LaTeX preamble.
Pdf files can be made from the eps file using 'epstopdf'. If the graphics
package is properly configured, the LaTeX files can also be processed by
pdflatex without changes, using the pdf files instead of the eps files.
The behaviour concerning font selection depends on the header mode.
In all cases, the given font size is used for the calculation of proper
spacing. When not using the `standalone` mode the actual LaTeX font and
font size at the point of inclusion is taken, so use LaTeX commands for
changing fonts. If you use e.g. 12pt as font size for your LaTeX
document, use '"" 12' as options. The font name is ignored. If using
`standalone` the given font and font size are used, see below for a
detailed description.
If text is printed coloured is controlled by the TeX booleans \ifGPcolor
and \ifGPblacktext. Only if \ifGPcolor is true and \ifGPblacktext is
false, text is printed coloured. You may either change them in the
generated TeX file or provide them globally in your TeX file, for example
by using
\newif\ifGPblacktext
\GPblacktexttrue
in the preamble of your document. The local assignment is only done if no
global value is given.
When using the epslatex terminal give the name of the TeX file in the
`set output` command including the file extension (normally ".tex").
The eps filename is generated by replacing the extension by ".eps".
If using the `standalone` mode a complete LaTeX header is added to the
LaTeX file; and "-inc" is added to the filename of the eps file.
The `standalone` mode generates a TeX file that produces
output with the correct size when using dvips, pdfTeX, or VTeX.
The default, `input`, generates a file that has to be included into a
LaTeX document using the \input command.
If a font other than "" or "default" is given it is interpreted as
LaTeX font name. It contains up to three parts, separated by a comma:
'fontname,fontseries,fontshape'. If the default fontshape or fontseries
are requested, they can be omitted. Thus, the real syntax for the fontname
is '[fontname][,fontseries][,fontshape]'. The naming convention for all
parts is given by the LaTeX font scheme. The fontname is 3 to 4 characters
long and is built as follows: One character for the font vendor, two
characters for the name of the font, and optionally one additional
character for special fonts, e.g., 'j' for fonts with old-style numerals
or 'x' for expert fonts. The names of many fonts is described in
http://www.tug.org/fontname/fontname.pdf
For example, 'cmr' stands for Computer Modern Roman, 'ptm' for Times-Roman,
and 'phv' for Helvetica. The font series denotes the thickness of the
glyphs, in most cases 'm' for normal ("medium") and 'bx' or 'b' for bold
fonts. The font shape is 'n' for upright, 'it' for italics, 'sl' for
slanted, or 'sc' for small caps, in general. Some fonts may provide
different font series or shapes.
Examples:
Use Times-Roman boldface (with the same shape as in the surrounding text):
set terminal epslatex 'ptm,bx'
Use Helvetica, boldface, italics:
set terminal epslatex 'phv,bx,it'
Continue to use the surrounding font in slanted shape:
set terminal epslatex ',,sl'
Use small capitals:
set terminal epslatex ',,sc'
By this method, only text fonts are changed. If you also want to change
the math fonts you have to use the "gnuplot.cfg" file or the `header`
option, described below.
In standalone mode, the font size is taken from the given font size in the
`set terminal` command. To be able to use a specified font size, a file
"size<size>.clo" has to reside in the LaTeX search path. By default,
10pt, 11pt, and 12pt are supported. If the package "extsizes" is
installed, 8pt, 9pt, 14pt, 17pt, and 20pt are added.
The `header` option takes a string as argument. This string is written
into the generated LaTeX file. If using the `standalone` mode, it is
written into the preamble, directly before the \begin{document} command.
In the `input` mode, it is placed directly after the \begingroup command
to ensure that all settings are local to the plot.
Examples:
Use T1 fontencoding, change the text and math font to Times-Roman as well
as the sans-serif font to Helvetica:
set terminal epslatex standalone header \
"\\usepackage[T1]{fontenc}\n\\usepackage{mathptmx}\n\\usepackage{helvet}"
Use a boldface font in the plot, not influencing the text outside the plot:
set terminal epslatex input header "\\bfseries"
If the file "gnuplot.cfg" is found by LaTeX it is input in the preamble
the LaTeX document, when using `standalone` mode. It can be used for
further settings, e.g., changing the document font to Times-Roman,
Helvetica, and Courier, including math fonts (handled by "mathptmx.sty"):
\usepackage{mathptmx}
\usepackage[scaled=0.92]{helvet}
\usepackage{courier}
The file "gnuplot.cfg" is loaded before the header information given
by the `header` command. Thus, you can use `header` to overwrite some of
settings performed using "gnuplot.cfg"
?commands set terminal pslatex
?set terminal pslatex
?set term pslatex
?terminal pslatex
?term pslatex
?pslatex
?commands set terminal pstex
?set terminal pstex
?set term pstex
?terminal pstex
?term pstex
?pstex
The `pslatex` driver generates output for further processing by LaTeX,
while the `pstex` driver generates output for further processing by
TeX. `pslatex` uses \specials understandable by dvips and xdvi. Figures
generated by `pstex` can be included in any plain-based format (including
LaTeX).
Syntax:
set terminal [pslatex | pstex] {default}
set terminal [pslatex | pstex]
{rotate | norotate}
{oldstyle | newstyle}
{auxfile | noauxfile}
{level1 | leveldefault | level3}
{color | colour | monochrome}
{background <rgbcolor> | nobackground}
{dashlength | dl <DL>}
{linewidth | lw <LW>} {pointscale | ps <PS>}
{rounded | butt}
{clip | noclip}
{palfuncparam <samples>{,<maxdeviation>}}
{size <XX>{unit},<YY>{unit}}
{<font_size>}
If you see the error message
"Can't find PostScript prologue file ... "
Please see and follow the instructions in `postscript prologue`.
The option `color` enables color, while `monochrome` prefers black and white
drawing elements. Further, `monochrome` uses gray `palette` but it does not
change color of objects specified with an explicit `colorspec`.
`dashlength` or `dl` scales the length of dashed-line segments by <DL>,
which is a floating-point number greater than zero.
`linewidth` or `lw` scales all linewidths by <LW>.
By default the generated PostScript code uses language features that were
introduced in PostScript Level 2, notably filters and pattern-fill of
irregular objects such as filledcurves. PostScript Level 2 features are
conditionally protected so that PostScript Level 1 interpreters do not issue
errors but, rather, display a message or a PostScript Level 1 approximation.
The `level1` option substitutes PostScript Level 1 approximations of these
features and uses no PostScript Level 2 code. This may be required by some
old printers and old versions of Adobe Illustrator. The flag `level1` can be
toggled later by editing a single line in the PostScript output file to force
PostScript Level 1 interpretation. In the case of files containing level 2
code, the above features will not appear or will be replaced by a note when
this flag is set or when the interpreting program does not indicate that it
understands level 2 PostScript or higher. The flag `level3` enables PNG
encoding for bitmapped images, which can reduce the output size considerably.
`rounded` sets line caps and line joins to be rounded; `butt` is the
default, butt caps and mitered joins.
`clip` tells PostScript to clip all output to the bounding box;
`noclip` is the default.
`palfuncparam` controls how `set palette functions` are encoded as gradients
in the output. Analytic color component functions (set via
`set palette functions`) are encoded as linear interpolated gradients in the
postscript output: The color component functions are sampled at <samples>
points and all points are removed from this gradient which can be removed
without changing the resulting colors by more than <maxdeviation>. For
almost every useful palette you may safely leave the defaults of
<samples>=2000 and <maxdeviation>=0.003 untouched.
The default size for postscript output is 10 inches x 7 inches. The default
for eps output is 5 x 3.5 inches. The `size` option changes this to
whatever the user requests. By default the X and Y sizes are taken to be in
inches, but other units are possibly (currently only cm). The BoundingBox
of the plot is correctly adjusted to contain the resized image.
Screen coordinates always run from 0.0 to 1.0 along the full length of the
plot edges as specified by the `size` option.
NB: `this is a change from the previously recommended method of using the
set size command prior to setting the terminal type`. The old method left
the BoundingBox unchanged and screen coordinates did not correspond to the
actual limits of the plot.
if `rotate` is specified, the y-axis label is rotated.
<font_size> is the size (in pts) of the desired font.
If `auxfile` is specified, it directs the driver to put the PostScript
commands into an auxiliary file instead of directly into the LaTeX file.
This is useful if your pictures are large enough that dvips cannot handle
them. The name of the auxiliary PostScript file is derived from the name of
the TeX file given on the `set output` command; it is determined by replacing
the trailing `.tex` (actually just the final extent in the file name) with
`.ps` in the output file name, or, if the TeX file has no extension, `.ps`
is appended. The `.ps` is included into the `.tex` file by a
\special{psfile=...} command. Remember to close the `output file` before
next plot unless in `multiplot` mode.
Gnuplot versions prior to version 4.2 generated plots of the size
5 x 3 inches using the ps(la)tex terminal while the current version generates
5 x 3.5 inches to be consistent with the postscript eps terminal. In
addition, the character width is now estimated to be 60% of the font size
while the old epslatex terminal used 50%. To reach the old format specify
the option `oldstyle`.
The pslatex driver offers a special way of controlling text positioning:
(a) If any text string begins with '{', you also need to include a '}' at the
end of the text, and the whole text will be centered both horizontally
and vertically by LaTeX. (b) If the text string begins with '[', you need
to continue it with: a position specification (up to two out of t,b,l,r),
']{', the text itself, and finally, '}'. The text itself may be anything
LaTeX can typeset as an LR-box. \rule{}{}'s may help for best positioning.
The options not described here are identical to the `Postscript terminal`.
Look there if you want to know what they do.
Examples:
set term pslatex monochrome rotate # set to defaults
To write the PostScript commands into the file "foo.ps":
set term pslatex auxfile
set output "foo.tex"; plot ...; set output
About label positioning:
Use gnuplot defaults (mostly sensible, but sometimes not really best):
set title '\LaTeX\ -- $ \gamma $'
Force centering both horizontally and vertically:
set label '{\LaTeX\ -- $ \gamma $}' at 0,0
Specify own positioning (top here):
set xlabel '[t]{\LaTeX\ -- $ \gamma $}'
The other label -- account for long ticlabels:
set ylabel '[r]{\LaTeX\ -- $ \gamma $\rule{7mm}{0pt}}'
Linewidths and pointsizes may be changed with `set style line`.
?commands set terminal postscript
?set terminal postscript
?set term postscript
?terminal postscript
?term postscript
?postscript
Several options may be set in the `postscript` driver.
Syntax:
set terminal postscript {default}
set terminal postscript {landscape | portrait | eps}
{enhanced | noenhanced}
{defaultplex | simplex | duplex}
{fontfile [add | delete] "<filename>"
| nofontfiles} {{no}adobeglyphnames}
{level1 | leveldefault | level3}
{color | colour | monochrome}
{background <rgbcolor> | nobackground}
{dashlength | dl <DL>}
{linewidth | lw <LW>} {pointscale | ps <PS>}
{rounded | butt}
{clip | noclip}
{palfuncparam <samples>{,<maxdeviation>}}
{size <XX>{unit},<YY>{unit}}
{blacktext | colortext | colourtext}
{{font} "fontname{,fontsize}" {<fontsize>}}
{fontscale <scale>}
If you see the error message
"Can't find PostScript prologue file ... "
Please see and follow the instructions in `postscript prologue`.
`landscape` and `portrait` choose the plot orientation.
`eps` mode generates EPS (Encapsulated PostScript) output, which is just
regular PostScript with some additional lines that allow the file to be
imported into a variety of other applications. (The added lines are
PostScript comment lines, so the file may still be printed by itself.) To
get EPS output, use the `eps` mode and make only one plot per file. In `eps`
mode the whole plot, including the fonts, is reduced to half of the default
size.
`enhanced` enables enhanced text mode features (subscripts,
superscripts and mixed fonts). See `enhanced` for more information.
`blacktext` forces all text to be written in black even in color mode;
Duplexing in PostScript is the ability of the printer to print on both
sides of the same sheet of paper. With `defaultplex`, the default setting
of the printer is used; with `simplex` only one side is printed; `duplex`
prints on both sides (ignored if your printer can't do it).
`"<fontname>"` is the name of a valid PostScript font; and `<fontsize>` is
the size of the font in PostScript points.
In addition to the standard postscript fonts, an oblique version of the
Symbol font, useful for mathematics, is defined. It is called
"Symbol-Oblique".
`default` sets all options to their defaults: `landscape`, `monochrome`,
`dl 1.0`, `lw 1.0`, `defaultplex`, `enhanced`, "Helvetica" and
14pt. Default size of a PostScript plot is 10 inches wide and 7 inches high.
The option `color` enables color, while `monochrome` prefers black and white
drawing elements. Further, `monochrome` uses gray `palette` but it does not
change color of objects specified with an explicit `colorspec`.
`dashlength` or `dl` scales the length of dashed-line segments by <DL>,
which is a floating-point number greater than zero.
`linewidth` or `lw` scales all linewidths by <LW>.
By default the generated PostScript code uses language features that were
introduced in PostScript Level 2, notably filters and pattern-fill of
irregular objects such as filledcurves. PostScript Level 2 features are
conditionally protected so that PostScript Level 1 interpreters do not issue
errors but, rather, display a message or a PostScript Level 1 approximation.
The `level1` option substitutes PostScript Level 1 approximations of these
features and uses no PostScript Level 2 code. This may be required by some
old printers and old versions of Adobe Illustrator. The flag `level1` can be
toggled later by editing a single line in the PostScript output file to force
PostScript Level 1 interpretation. In the case of files containing level 2
code, the above features will not appear or will be replaced by a note when
this flag is set or when the interpreting program does not indicate that it
understands level 2 PostScript or higher. The flag `level3` enables PNG
encoding for bitmapped images, which can reduce the output size considerably.
`rounded` sets line caps and line joins to be rounded; `butt` is the
default, butt caps and mitered joins.
`clip` tells PostScript to clip all output to the bounding box;
`noclip` is the default.
`palfuncparam` controls how `set palette functions` are encoded as gradients
in the output. Analytic color component functions (set via
`set palette functions`) are encoded as linear interpolated gradients in the
postscript output: The color component functions are sampled at <samples>
points and all points are removed from this gradient which can be removed
without changing the resulting colors by more than <maxdeviation>. For
almost every useful palette you may safely leave the defaults of
<samples>=2000 and <maxdeviation>=0.003 untouched.
The default size for postscript output is 10 inches x 7 inches. The default
for eps output is 5 x 3.5 inches. The `size` option changes this to
whatever the user requests. By default the X and Y sizes are taken to be in
inches, but other units are possibly (currently only cm). The BoundingBox
of the plot is correctly adjusted to contain the resized image.
Screen coordinates always run from 0.0 to 1.0 along the full length of the
plot edges as specified by the `size` option.
NB: `this is a change from the previously recommended method of using the
set size command prior to setting the terminal type`. The old method left
the BoundingBox unchanged and screen coordinates did not correspond to the
actual limits of the plot.
Fonts listed by `fontfile` or `fontfile add` encapsulate the font
definitions of the listed font from a postscript Type 1 or TrueType font
file directly into the gnuplot output postscript file. Thus, the enclosed
font can be used in labels, titles, etc. See the section
`postscript fontfile` for more details. With `fontfile delete`, a fontfile
is deleted from the list of embedded files. `nofontfiles` cleans the list
of embedded fonts.
Examples:
set terminal postscript default # old postscript
set terminal postscript enhanced # old enhpost
set terminal postscript landscape 22 # old psbig
set terminal postscript eps 14 # old epsf1
set terminal postscript eps 22 # old epsf2
set size 0.7,1.4; set term post portrait color "Times-Roman" 14
set term post "VAGRoundedBT_Regular" 14 fontfile "bvrr8a.pfa"
Linewidths and pointsizes may be changed with `set style line`.
The `postscript` driver supports about 70 distinct pointtypes, selectable
through the `pointtype` option on `plot` and `set style line`.
Several possibly useful files about `gnuplot`'s PostScript are included
in the /docs/psdoc subdirectory of the `gnuplot` distribution and at the
distribution sites. These are "ps_symbols.gpi" (a `gnuplot` command file
that, when executed, creates the file "ps_symbols.ps" which shows all the
symbols available through the `postscript` terminal), "ps_guide.ps" (a
PostScript file that contains a summary of the enhanced syntax and a page
showing what the octal codes produce with text and symbol fonts),
"ps_file.doc" (a text file that contains a discussion of the organization
of a PostScript file written by `gnuplot`), and "ps_fontfile_doc.tex"
(a LaTeX file which contains a short documentation concerning the
encapsulation of LaTeX fonts with a glyph table of the math fonts).
A PostScript file is editable, so once `gnuplot` has created one, you are
free to modify it to your heart's desire. See the `editing postscript`
section for some hints.
?commands set terminal postscript editing
?set terminal postscript editing
?set term postscript editing
?terminal postscript editing
?term postscript editing
?editing_postscript
?editing postscript
The PostScript language is a very complex language---far too complex to
describe in any detail in this document. Nevertheless there are some things
in a PostScript file written by `gnuplot` that can be changed without risk of
introducing fatal errors into the file.
For example, the PostScript statement "/Color true def" (written into the
file in response to the command `set terminal postscript color`), may be
altered in an obvious way to generate a black-and-white version of a plot.
Similarly line colors, text colors, line weights and symbol sizes can also be
altered in straight-forward ways. Text (titles and labels) can be edited to
correct misspellings or to change fonts. Anything can be repositioned, and
of course anything can be added or deleted, but modifications such as these
may require deeper knowledge of the PostScript language.
The organization of a PostScript file written by `gnuplot` is discussed in
the text file "ps_file.doc" in the docs/ps subdirectory of the gnuplot
source distribution.
?commands set terminal postscript fontfile
?set terminal postscript fontfile
?set term postscript fontfile
?terminal postscript fontfile
?term postscript fontfile
?postscript fontfile
?fontfile
The `fontfile` or `fontfile add` option takes one file name as argument
and encapsulates this file into the postscript output in order to make
this font available for text elements (labels, tic marks, titles, etc.).
The `fontfile delete` option also takes one file name as argument. It
deletes this file name from the list of encapsulated files.
The postscript terminal understands some
font file formats: Type 1 fonts in ASCII file format (extension ".pfa"),
Type 1 fonts in binary file format (extension ".pfb"), and TrueType
fonts (extension ".ttf"). Pfa files are understood directly, pfb and ttf
files are converted on the fly if appropriate conversion tools are
installed (see below). You have to specify the full filename including the
extension. Each `fontfile` option takes exact one font file name. This
option can be used multiple times in order to include more than one font
file.
The font file is searched in the working directory and in all directories
listed in the fontpath which is determined by `set fontpath`.
In addition, the fontpath can be set using the environment variable
GNUPLOT_FONTPATH. If this is not set a system dependent default search
list is used. See `set fontpath` for more details.
For using the encapsulated font file you have to specify the font name
(which normally is not the same as the file name). When embedding a
font file by using the `fontfile` option in interactive mode, the
font name is printed on the screen. E.g.
Font file 'p052004l.pfb' contains the font 'URWPalladioL-Bold'. Location:
/usr/lib/X11/fonts/URW/p052004l.pfb
When using pfa or pfb fonts, you can also find it out by looking into the
font file. There is a line similar to "/FontName /URWPalladioL-Bold def".
The middle string without the slash is the fontname, here
"URWPalladioL-Bold".
For TrueType fonts, this is not so easy since the font name is stored in a
binary format. In addition, they often have spaces in the font names which
is not supported by Type 1 fonts (in which a TrueType is converted on the
fly). The font names are changed in order to eliminate the spaces in the
fontnames. The easiest way to find out which font name is generated for
use with gnuplot, start gnuplot in interactive mode and type in
"set terminal postscript fontfile '<filename.ttf>'".
For converting font files (either ttf or pfb) to pfa format, the conversion
tool has to read the font from a file and write it to standard output. If
the output cannot be written to standard output, on-the-fly conversion is
not possible.
For pfb files "pfbtops" is a tool which can do this. If this program
is installed on your system the on the fly conversion should work.
Just try to encapsulate a pfb file. If the compiled in program call does
not work correctly you can specify how this program is called by
defining the environment variable GNUPLOT_PFBTOPFA e.g. to
"pfbtops %s". The `%s` will be replaced by the font file name and thus
has to exist in the string.
If you don't want to do the conversion on the fly but get a pfa file of
the font you can use the tool "pfb2pfa" which is written in simple c
and should compile with any c compiler.
It is available from many ftp servers, e.g.
ftp://ftp.dante.de/tex-archive/fonts/utilities/ps2mf/
In fact, "pfbtopfa" and "pfb2ps" do the same job. "pfbtopfa" puts
the resulting pfa code into a file, whereas "pfbtops" writes it to
standard output.
TrueType fonts are converted into Type 1 pfa format, e.g.
by using the tool "ttf2pt1" which is available from
http://ttf2pt1.sourceforge.net/
If the builtin conversion does not
work, the conversion command can be changed by the environment variable
GNUPLOT_TTFTOPFA. For usage with ttf2pt1 it may be set to
"ttf2pt1 -a -e -W 0 %s - ". Here again, `%s` stands for the
file name.
For special purposes you also can use a pipe (if available for your
operating system). Therefore you start the file name definition with
the character "<" and append a program call. This program has
to write pfa data to standard output. Thus, a pfa file may be accessed
by `set fontfile "< cat garamond.pfa"`.
For example, including Type 1 font files can be used for including the
postscript output in LaTeX documents. The "european computer modern"
font (which is a variant of the "computer modern" font) is available
in pfb format from any CTAN server, e.g.
ftp://ftp.dante.de/tex-archive/fonts/ps-type1/cm-super/
For example, the file "sfrm1000.pfb" contains the normal upright fonts
with serifs in the design size 10pt (font name "SFRM1000").
The computer modern fonts, which are still necessary for mathematics,
are available from
ftp://ftp.dante.de/tex-archive/fonts/cm/ps-type1/bluesky
With these you can use any character available in TeX. However, the
computer modern fonts have a strange encoding. (This is why you should not
use cmr10.pfb for text, but sfrm1000.pfb instead.)
The usage of TeX fonts is shown in one of the demos.
The file "ps_fontfile_doc.tex" in the /docs/psdoc subdirectory of the
`gnuplot` source distribution contains a table with glyphs of the TeX
mathfonts.
If the font "CMEX10" is embedded (file "cmex10.pfb") gnuplot defines
the additional font "CMEX10-Baseline". It is shifted vertically in order
to fit better to the other glyphs (CMEX10 has its baseline at the top of
the symbols).
?commands set terminal postscript prologue
?set terminal postscript prologue
?terminal postscript prologue
?postscript prologue
?prologue
Each PostScript output file includes a %%Prolog section and possibly some
additional user-defined sections containing, for example, character encodings.
These sections are copied from a set of PostScript prologue files that are
either compiled into the gnuplot executable or stored elsewhere on your
computer. A default directory where these files live is set at the time
gnuplot is built. However, you can override this default either by using the
gnuplot command `set psdir` or by defining an environment variable
GNUPLOT_PS_DIR. See `set psdir`.
?commands set terminal postscript adobeglyphnames
?set terminal postscript adobeglyphnames
?terminal postscript adobeglyphnames
?postscript adobeglyphnames
?adobeglyphnames
This setting is only relevant to PostScript output with UTF-8 encoding.
It controls the names used to describe characters with Unicode entry points
higher than 0x00FF. That is, all characters outside of the Latin1 set.
In general unicode characters do not have a unique name; they have only a
unicode identification code. However, Adobe have a recommended scheme for
assigning names to certain ranges of characters (extended Latin, Greek, etc).
Some fonts use this scheme, others do not. By default, gnuplot will use
the Adobe glyph names. E.g. the lower case Greek letter alpha will be called
/alpha. If you specific `noadobeglyphnames` then instead gnuplot will use
/uni03B1 to describe this character. If you get this setting wrong, the
character may not be found even if it is present in the font.
It is probably always correct to use the default for Adobe fonts, but for
other fonts you may have to try both settings. See also `fontfile`.
?commands set terminal qms
?set terminal qms
?set term qms
?terminal qms
?term qms
?qms
The `qms` terminal driver supports the QMS/QUIC Laser printer, the Talaris
1200 and others. It has no options.
?commands set terminal svg
?set terminal svg
?set term svg
?terminal svg
?term svg
?svg
This terminal produces files in the W3C Scalable Vector Graphics format.
Syntax:
set terminal svg {size <x>,<y> {|fixed|dynamic}}
{mouse} {standalone | jsdir <dirname>}
{name <plotname>}
{font "<fontname>{,<fontsize>}"} {{no}enhanced}
{fontscale <multiplier>}
{rounded|butt|square} {solid|dashed} {linewidth <lw>}
{background <rgb_color>}
where <x> and <y> are the size of the SVG plot to generate,
`dynamic` allows a svg-viewer to resize plot, whereas the default
setting, `fixed`, will request an absolute size.
`linewidth <w>` increases the width of all lines used in the figure
by a factor of <w>.
<font> is the name of the default font to use (default Arial) and
<fontsize> is the font size (in points, default 12). SVG viewing
programs may substitute other fonts when the file is displayed.
The enhanced text mode syntax is shared with other gnuplot terminal types.
See `enhanced` for more details.
The `mouse` option tells gnuplot to add support for mouse tracking and for
toggling individual plots on/off by clicking on the corresponding key entry.
By default this is done by including a link that points to a script in a
local directory, usually /usr/local/share/gnuplot/<version>/js.
You can change this by using the `jsdir` option to specify either a
different local directory or a general URL. The latter is usually
appropriate if you are embedding the svg into a web page.
Alternatively, the `standalone` option embeds the mousing code in the svg
document itself rather than linking to an external resource.
When an SVG file will be used in conjunction with external files,
e.g. if it is referenced by javascript code in a web page or parent document,
then a unique name is required to avoid potential conflicting references
to other SVG plots. Use the `name` option to ensure uniqueness.
?set terminal domterm
?terminal domterm
?set term domterm
?term domterm
?domterm
The `domterm` terminal device runs on the DomTerm terminal emulator
including the domterm and qtdomterm programs.
It supports SVG graphics embedded directly in the terminal output.
See http://domterm.org .
Please read the help for the `svg` terminal.
?commands set terminal tgif
?set terminal tgif
?set term tgif
?terminal tgif
?term tgif
?tgif
Tgif is an X11-based drawing tool---it has nothing to do with GIF.
The `tgif` driver supports a choice of font and font size and multiple
graphs on the page. The proportions of the axes are not changed.
Syntax:
set terminal tgif {portrait | landscape | default} {<[x,y]>}
{monochrome | color}
{{linewidth | lw} <LW>}
{solid | dashed}
{font "<fontname>{,<fontsize>}"}
where <[x,y]> specifies the number of graphs in the x and y directions on the
page, `color` enables color, `linewidth` scales all linewidths by <LW>,
"<fontname>" is the name of a valid PostScript font, and <fontsize>
specifies the size of the PostScript font.
`defaults` sets all options to their defaults: `portrait`, `[1,1]`, `color`,
`linewidth 1.0`, `dashed`, `"Helvetica,18"`.
The `solid` option is usually prefered if lines are colored, as they often
are in the editor. Hardcopy will be black-and-white, so `dashed` should be
chosen for that.
Multiplot is implemented in two different ways.
The first multiplot implementation is the standard gnuplot multiplot feature:
set terminal tgif
set output "file.obj"
set multiplot
set origin x01,y01
set size xs,ys
plot ...
...
set origin x02,y02
plot ...
unset multiplot
See `set multiplot` for further information.
The second version is the [x,y] option for the driver itself. The advantage
of this implementation is that everything is scaled and placed automatically
without the need for setting origins and sizes; the graphs keep their natural
x/y proportions of 3/2 (or whatever is fixed by `set size`).
If both multiplot methods are selected, the standard method is chosen and a
warning message is given.
Examples of single plots (or standard multiplot):
set terminal tgif # defaults
set terminal tgif "Times-Roman,24"
set terminal tgif landscape
set terminal tgif landscape solid
Examples using the built-in multiplot mechanism:
set terminal tgif portrait [2,4] # portrait; 2 plots in the x-
# and 4 in the y-direction
set terminal tgif [1,2] # portrait; 1 plot in the x-
# and 2 in the y-direction
set terminal tgif landscape [3,3] # landscape; 3 plots in both
# directions
?commands set terminal tkcanvas
?set terminal tkcanvas
?set term tkcanvas
?terminal tkcanvas
?term tkcanvas
?tkcanvas
This terminal driver generates Tk canvas widget commands in one of the
following scripting languages: Tcl (default), Perl, Python, Ruby, or REXX.
Syntax:
set terminal tkcanvas {tcl | perl | perltkx | python | ruby | rexx}
{standalone | input}
{interactive}
{rounded | butt}
{nobackground | background <rgb color>}
{{no}rottext}
{size <width>,<height>}
{{no}enhanced}
{externalimages | pixels}
Execute the following sequence of Tcl/Tk commands to display the result:
package require Tk
# the following two lines are only required to support external images
package require img::png
source resize.tcl
source plot.tcl
canvas .c -width 800 -height 600
pack .c
gnuplot .c
Or, for Perl/Tk use a program like this:
use Tk;
my $top = MainWindow->new;
my $c = $top->Canvas(-width => 800, -height => 600)->pack;
my $gnuplot = do "plot.pl";
$gnuplot->($c);
MainLoop;
Or, for Perl/Tkx use a program like this:
use Tkx;
my $top = Tkx::widget->new(".");
my $c = $top->new_tk__canvas(-width => 800, -height => 600);
$c->g_pack;
my $gnuplot = do "plot.pl";
$gnuplot->($c);
Tkx::MainLoop();
Or, for Python/Tkinter use a program like this:
from tkinter import *
from tkinter import font
root = Tk()
c = Canvas(root, width=800, height=600)
c.pack()
exec(open('plot.py').read())
gnuplot(c)
root.mainloop()
Or, for Ruby/Tk use a program like this:
require 'tk'
root = TkRoot.new { title 'Ruby/Tk' }
c = TkCanvas.new(root, 'width'=>800, 'height'=>600) { pack { } }
load('plot.rb')
gnuplot(c)
Tk.mainloop
Or, for Rexx/Tk use a program like this:
/**/
call RxFuncAdd 'TkLoadFuncs', 'rexxtk', 'TkLoadFuncs'
call TkLoadFuncs
cv = TkCanvas('.c', '-width', 800, '-height', 600)
call TkPack cv
call 'plot.rex' cv
do forever
cmd = TkWait()
if cmd = 'AWinClose' then leave
interpret 'call' cmd
end
The code generated by `gnuplot` (in the above examples, this code is
written to "plot.<ext>") contains the following procedures:
gnuplot(canvas)
takes the name of a canvas as its argument.
When called, it clears the canvas, finds the size of the canvas and
draws the plot in it, scaled to fit.
gnuplot_plotarea()
returns a list containing the borders of the plotting area
(xleft, xright, ytop, ybot) in canvas screen coordinates. It works only for 2-dimensional plotting (`plot`).
gnuplot_axisranges()
returns the ranges of the two axes in plot coordinates
(x1min, x1max, y1min, y1max, x2min, x2max, y2min, y2max).
It works only for 2-dimensional plotting (`plot`).
You can create self-contained, minimal scripts using the `standalone`
option. The default is `input` which creates scripts which have to be
source'd (or loaded or called or whatever the adequate term is for the
language selected).
If the `interactive` option is specified, mouse clicking on a line segment
will print the coordinates of its midpoint to stdout.
The user can supersede this behavior by supplying a procedure
user_gnuplot_coordinates which takes the following arguments:
win id x1s y1s x2s y2s x1e y1e x2e y2e x1m y1m x2m y2m,
i.e. the name of the canvas and the id of the line segment followed by the
coordinates of its start and end point in the two possible axis ranges; the
coordinates of the midpoint are only filled for logarithmic axes.
By default the canvas is `transparent`, but an explicit background color
can be set with the `background` option.
`rounded` sets line caps and line joins to be rounded;
`butt` is the default: butt caps and mitered joins.
Text at arbitrary angles can be activated with the `rottext` option,
which requires Tcl/Tk 8.6 or later. The default is `norottext`.
The `size` option tries to optimize the tic and font sizes for the given
canvas size. By default an output size of 800 x 600 pixels is assumed.
`enhanced` selects `enhanced text` processing (default), but is currently
only available for Tcl.
The `pixels` (default) option selects the failsafe pixel-by-pixel image
handler, see also `image pixels`.
The `externalimages` option saves images as external png images, which
are later loaded and scaled by the tkcanvas code. This option is only
available for Tcl and display may be slow in some situations since the
Tk image handler does not provide arbitrary scaling. Scripts need to source
the provided rescale.tcl.
Interactive mode is not yet implemented for Python/Tk and Rexx/Tk.
Interactive mode for Ruby/Tk does not yet support user_gnuplot_coordinates.
?commands set terminal emtex
?set terminal emtex
?set term emtex
?terminal emtex
?term emtex
?emtex
?commands set terminal latex
?set terminal latex
?set term latex
?terminal latex
?term latex
?latex
Syntax:
set terminal {latex | emtex} {default | {courier|roman} {<fontsize>}}
{size <XX>{unit}, <YY>{unit}} {rotate | norotate}
By default the plot will inherit font settings from the embedding document.
You have the option of forcing either Courier (cmtt) or Roman (cmr) fonts
instead. In this case you may also specify a fontsize.
Unless your driver is capable of building fonts at any size (e.g. dvips),
stick to the standard 10, 11 and 12 point sizes.
METAFONT users beware: METAFONT does not like odd sizes.
All drivers for LaTeX offer a special way of controlling text positioning:
If any text string begins with '{', you also need to include a '}' at the
end of the text, and the whole text will be centered both horizontally and
vertically. If the text string begins with '[', you need to follow this with
a position specification (up to two out of t,b,l,r), ']{', the text itself,
and finally '}'. The text itself may be anything LaTeX can typeset as an
LR-box. '\rule{}{}'s may help for best positioning.
Points, among other things, are drawn using the LaTeX commands "\Diamond" and
"\Box". These commands no longer belong to the LaTeX2e core; they are included
in the latexsym package, which is part of the base distribution and thus part
of any LaTeX implementation. Please do not forget to use this package.
Other point types use symbols from the amssymb package.
The default size for the plot is 5 inches by 3 inches. The `size` option
changes this to whatever the user requests. By default the X and Y sizes
are taken to be in inches, but other units are possible (currently only cm).
If 'rotate' is specified, rotated text, especially a rotated y-axis label,
is possible (the packages graphics or graphicx are needed). The 'stacked'
y-axis label mechanism is then deactivated.
Examples:
About label positioning:
Use gnuplot defaults (mostly sensible, but sometimes not really best):
set title '\LaTeX\ -- $ \gamma $'
Force centering both horizontally and vertically:
set label '{\LaTeX\ -- $ \gamma $}' at 0,0
Specify own positioning (top here):
set xlabel '[t]{\LaTeX\ -- $ \gamma $}'
The other label -- account for long ticlabels:
set ylabel '[r]{\LaTeX\ -- $ \gamma $\rule{7mm}{0pt}}'
?commands set terminal eepic
?set terminal eepic
?set term eepic
?terminal eepic
?term eepic
?eepic
The `eepic` terminal driver supports the extended LaTeX picture environment.
It is an alternative to the `latex` driver.
The output of this terminal is intended for use with the "eepic.sty" macro
package for LaTeX. To use it, you need "eepic.sty", "epic.sty" and a
printer driver that supports the "tpic" \specials. If your printer driver
doesn't support those \specials, "eepicemu.sty" will enable you to use some
of them.
dvips and dvipdfm do support the "tpic" \specials.
Syntax:
set terminal eepic {default} {color|dashed} {rotate} {size XX,YY}
{small|tiny|<fontsize>}
Options:
You can give options in any order you wish.
'color' causes gnuplot to produce \color{...} commands so that the graphs are
colored. Using this option, you must include \usepackage{color} in the preamble
of your latex document.
'dashed' will allow dashed line types; without this option, only solid lines
with varying thickness will be used.
'dashed' and 'color' are mutually exclusive; if 'color' is specified, then
'dashed' will be ignored.
'rotate' will enable true rotated text (by 90 degrees). Otherwise, rotated text
will be typeset with letters stacked above each other. If you use this option
you must include \usepackage{graphicx} in the preamble.
'small' will use \scriptsize symbols as point markers (Probably does not work
with TeX, only LaTeX2e). Default is to use the default math size.
'tiny' uses \scriptscriptstyle symbols.
'default' resets all options to their defaults = no color, no dashed lines,
pseudo-rotated (stacked) text, large point symbols.
<fontsize> is a number which specifies the font size inside the picture
environment; the unit is pt (points), i.e., 10 pt equals approx. 3.5 mm.
If fontsize is not specified, then all text inside the picture will be set
in \footnotesize.
Notes:
Remember to escape the # character (or other chars meaningful to (La-)TeX)
by \\ (2 backslashes).
It seems that dashed lines become solid lines when the vertices of a plot
are too close. (I do not know if that is a general problem with the tpic
specials, or if it is caused by a bug in eepic.sty or dvips/dvipdfm.)
The default size of an eepic plot is 5x3 inches. You can change this using
the `size` terminal option.
Points, among other things, are drawn using the LaTeX commands "\Diamond",
"\Box", etc. These commands no longer belong to the LaTeX2e core; they are
included in the latexsym package, which is part of the base distribution and
thus part of any LaTeX implementation. Please do not forget to use this package.
Instead of latexsym, you can also include the amssymb package.
All drivers for LaTeX offer a special way of controlling text positioning:
If any text string begins with '{', you also need to include a '}' at the
end of the text, and the whole text will be centered both horizontally and
vertically. If the text string begins with '[', you need to follow this with
a position specification (up to two out of t,b,l,r), ']{', the text itself,
and finally '}'. The text itself may be anything LaTeX can typeset as an
LR-box. '\rule{}{}'s may help for best positioning.
Examples:
set term eepic
output graphs as eepic macros inside a picture environment;
\input the resulting file in your LaTeX document.
set term eepic color tiny rotate 8
eepic macros with \color macros, \scripscriptsize point markers,
true rotated text, and all text set with 8pt.
About label positioning:
Use gnuplot defaults (mostly sensible, but sometimes not really best):
set title '\LaTeX\ -- $ \gamma $'
Force centering both horizontally and vertically:
set label '{\LaTeX\ -- $ \gamma $}' at 0,0
Specify own positioning (top here):
set xlabel '[t]{\LaTeX\ -- $ \gamma $}'
The other label -- account for long ticlabels:
set ylabel '[r]{\LaTeX\ -- $ \gamma $\rule{7mm}{0pt}}'
?commands set terminal tpic
?set terminal tpic
?set term tpic
?terminal tpic
?term tpic
?tpic
The `tpic` terminal driver supports the LaTeX picture environment with tpic
\specials. It is an alternative to the `latex` and `eepic` terminal drivers.
Options are the point size, line width, and dot-dash interval.
Syntax:
set terminal tpic <pointsize> <linewidth> <interval>
where `pointsize` and `linewidth` are integers in milli-inches and `interval`
is a float in inches. If a non-positive value is specified, the default is
chosen: pointsize = 40, linewidth = 6, interval = 0.1.
All drivers for LaTeX offer a special way of controlling text positioning:
If any text string begins with '{', you also need to include a '}' at the
end of the text, and the whole text will be centered both horizontally
and vertically by LaTeX. --- If the text string begins with '[', you need
to continue it with: a position specification (up to two out of t,b,l,r),
']{', the text itself, and finally, '}'. The text itself may be anything
LaTeX can typeset as an LR-box. \rule{}{}'s may help for best positioning.
Examples:
About label positioning:
Use gnuplot defaults (mostly sensible, but sometimes not really best):
set title '\LaTeX\ -- $ \gamma $'
Force centering both horizontally and vertically:
set label '{\LaTeX\ -- $ \gamma $}' at 0,0
Specify own positioning (top here):
set xlabel '[t]{\LaTeX\ -- $ \gamma $}'
The other label -- account for long ticlabels:
set ylabel '[r]{\LaTeX\ -- $ \gamma $\rule{7mm}{0pt}}'
?commands set terminal pstricks
?set terminal pstricks
?set term pstricks
?terminal pstricks
?term pstricks
?pstricks
The `pstricks` driver is intended for use with the "pstricks.sty" macro
package for LaTeX. It is an alternative to the `eepic` and `latex` drivers.
You need "pstricks.sty", and, of course, a printer that understands
PostScript, or a converter such as Ghostscript.
PSTricks is available via anonymous ftp from the /pub directory at
Princeton.edu. This driver definitely does not come close to using the full
capability of the PSTricks package.
Syntax:
set terminal pstricks {hacktext | nohacktext} {unit | nounit}
The first option invokes an ugly hack that gives nicer numbers; the second
has to do with plot scaling. The defaults are `hacktext` and `nounit`.
?commands set terminal texdraw
?set terminal texdraw
?set term texdraw
?terminal texdraw
?term texdraw
?texdraw
The `texdraw` terminal driver supports the LaTeX texdraw environment. It is
intended for use with "texdraw.sty" and "texdraw.tex" in the texdraw package.
Points, among other things, are drawn using the LaTeX commands "\Diamond" and
"\Box". These commands no longer belong to the LaTeX2e core; they are included
in the latexsym package, which is part of the base distribution and thus part
of any LaTeX implementation. Please do not forget to use this package.
It has no options.
?commands set terminal mf
?set terminal mf
?set term mf
?terminal mf
?term mf
?mf
?metafont
The `mf` terminal driver creates an input file to the METAFONT program. Thus a
figure may be used in the TeX document in the same way as is a character.
To use a picture in a document, the METAFONT program must be run with the
output file from `gnuplot` as input. Thus, the user needs a basic knowledge
of the font creating process and the procedure for including a new font in a
document. However, if the METAFONT program is set up properly at the local
site, an unexperienced user could perform the operation without much trouble.
The text support is based on a METAFONT character set. Currently the
Computer Modern Roman font set is input, but the user is in principal free to
choose whatever fonts he or she needs. The METAFONT source files for the
chosen font must be available. Each character is stored in a separate
picture variable in METAFONT. These variables may be manipulated (rotated,
scaled etc.) when characters are needed. The drawback is the interpretation
time in the METAFONT program. On some machines (i.e. PC) the limited amount
of memory available may also cause problems if too many pictures are stored.
The `mf` terminal has no options.
?commands set terminal mf detailed
?set terminal mf detailed
?set term mf detailed
?mf detailed
?metafont detailed
- Set your terminal to METAFONT:
set terminal mf
- Select an output-file, e.g.:
set output "myfigures.mf"
- Create your pictures. Each picture will generate a separate character. Its
default size will be 5*3 inches. You can change the size by saying `set size
0.5,0.5` or whatever fraction of the default size you want to have.
- Quit `gnuplot`.
- Generate a TFM and GF file by running METAFONT on the output of `gnuplot`.
Since the picture is quite large (5*3 in), you will have to use a version of
METAFONT that has a value of at least 150000 for memmax. On Unix systems
these are conventionally installed under the name bigmf. For the following
assume that the command virmf stands for a big version of METAFONT. For
example:
- Invoke METAFONT:
virmf '&plain'
- Select the output device: At the METAFONT prompt ('*') type:
\mode:=CanonCX; % or whatever printer you use
- Optionally select a magnification:
mag:=1; % or whatever you wish
- Input the `gnuplot`-file:
input myfigures.mf
On a typical Unix machine there will usually be a script called "mf" that
executes virmf '&plain', so you probably can substitute mf for virmf &plain.
This will generate two files: mfput.tfm and mfput.$$$gf (where $$$ indicates
the resolution of your device). The above can be conveniently achieved by
typing everything on the command line, e.g.:
virmf '&plain' '\mode:=CanonCX; mag:=1; input myfigures.mf'
In this case the output files will be named myfigures.tfm and
myfigures.300gf.
- Generate a PK file from the GF file using gftopk:
gftopk myfigures.300gf myfigures.300pk
The name of the output file for gftopk depends on the DVI driver you use.
Ask your local TeX administrator about the naming conventions. Next, either
install the TFM and PK files in the appropriate directories, or set your
environment variables properly. Usually this involves setting TEXFONTS to
include the current directory and doing the same thing for the environment
variable that your DVI driver uses (no standard name here...). This step is
necessary so that TeX will find the font metric file and your DVI driver will
find the PK file.
- To include your pictures in your document you have to tell TeX the font:
\font\gnufigs=myfigures
Each picture you made is stored in a single character. The first picture is
character 0, the second is character 1, and so on... After doing the above
step, you can use the pictures just like any other characters. Therefore, to
place pictures 1 and 2 centered in your document, all you have to do is:
\centerline{\gnufigs\char0}
\centerline{\gnufigs\char1}
in plain TeX. For LaTeX you can, of course, use the picture environment and
place the picture wherever you wish by using the \makebox and \put macros.
This conversion saves you a lot of time once you have generated the font;
TeX handles the pictures as characters and uses minimal time to place them,
and the documents you make change more often than the pictures do. It also
saves a lot of TeX memory. One last advantage of using the METAFONT driver
is that the DVI file really remains device independent, because no \special
commands are used as in the eepic and tpic drivers.
?commands set terminal mpost
?set terminal mp
?set term mp
?terminal mp
?term mp
?mp
?metapost
The `mp` driver produces output intended to be input to the Metapost program.
Running Metapost on the file creates EPS files containing the plots. By
default, Metapost passes all text through TeX. This has the advantage of
allowing essentially any TeX symbols in titles and labels.
Syntax:
set term mp {color | colour | monochrome}
{solid | dashed}
{notex | tex | latex}
{magnification <magsize>}
{psnfss | psnfss-version7 | nopsnfss}
{prologues <value>}
{a4paper}
{amstex}
{"<fontname> {,<fontsize>}"}
The option `color` causes lines to be drawn in color (on a printer or display
that supports it), `monochrome` (or nothing) selects black lines. The option
`solid` draws solid lines, while `dashed` (or nothing) selects lines with
different patterns of dashes. If `solid` is selected but `color` is not,
nearly all lines will be identical. This may occasionally be useful, so it is
allowed.
The option `notex` bypasses TeX entirely, therefore no TeX code can be used in
labels under this option. This is intended for use on old plot files or files
that make frequent use of common characters like `$` and `%` that require
special handling in TeX.
The option `tex` sets the terminal to output its text for TeX to process.
The option `latex` sets the terminal to output its text for processing by
LaTeX. This allows things like \frac for fractions which LaTeX knows about
but TeX does not. Note that you must set the environment variable TEX to the
name of your LaTeX executable (normally latex) if you use this option or use
`mpost --tex=<name of LaTeX executable> ...`. Otherwise metapost will try and
use TeX to process the text and it won't work.
Changing font sizes in TeX has no effect on the size of mathematics, and there
is no foolproof way to make such a change, except by globally setting a
magnification factor. This is the purpose of the `magnification` option. It
must be followed by a scaling factor. All text (NOT the graphs) will be scaled
by this factor. Use this if you have math that you want at some size other
than the default 10pt. Unfortunately, all math will be the same size, but see
the discussion below on editing the MP output. `mag` will also work under
`notex` but there seems no point in using it as the font size option (below)
works as well.
The option `psnfss` uses postscript fonts in combination with LaTeX. Since
this option only makes sense, if LaTeX is being used, the `latex` option is selected
automatically. This option includes the following packages for LaTeX:
inputenc(latin1), fontenc(T1), mathptmx, helvet(scaled=09.2), courier, latexsym
and textcomp.
The option `psnfss-version7` uses also postscript fonts in LaTeX (option `latex`
is also automatically selected), but uses the following packages with LaTeX:
inputenc(latin1), fontenc(T1), times, mathptmx, helvet and courier.
The option `nopsnfss` is the default and uses the standard font (cmr10 if not
otherwise specified).
The option `prologues` takes a value as an additional argument and adds the line
`prologues:=<value>` to the metapost file. If a value of `2` is specified metapost
uses postscript fonts to generate the eps-file, so that the result can be viewed
using e.g. ghostscript. Normally the output of metapost uses TeX fonts and therefore
has to be included in a (La)TeX file before you can look at it.
The option `noprologues` is the default. No additional line specifying the prologue
will be added.
The option `a4paper` adds a `[a4paper]` to the documentclass. Normally letter paper
is used (default). Since this option is only used in case of LaTeX, the `latex` option
is selected automatically.
The option `amstex` automatically selects the `latex` option and includes the following
LaTeX packages: amsfonts, amsmath(intlimits). By default these packages are not
included.
A name in quotes selects the font that will be used when no explicit font is
given in a `set label` or `set title`. A name recognized by TeX (a TFM file
exists) must be used. The default is "cmr10" unless `notex` is selected,
then it is "pcrr8r" (Courier). Even under `notex`, a TFM file is needed by
Metapost. The file `pcrr8r.tfm` is the name given to Courier in LaTeX's psnfss
package. If you change the font from the `notex` default, choose a font that
matches the ASCII encoding at least in the range 32-126. `cmtt10` almost
works, but it has a nonblank character in position 32 (space).
The size can be any number between 5.0 and 99.99. If it is omitted, 10.0 is
used. It is advisable to use `magstep` sizes: 10 times an integer or
half-integer power of 1.2, rounded to two decimals, because those are the most
available sizes of fonts in TeX systems.
All the options are optional. If font information is given, it must be at the
end, with size (if present) last. The size is needed to select a size for the
font, even if the font name includes size information. For example,
`set term mp "cmtt12"` selects cmtt12 shrunk to the default size 10. This
is probably not what you want or you would have used cmtt10.
The following common ascii characters need special treatment in TeX:
$, &, #, %, _; |, <, >; ^, ~, \, {, and }
The five characters $, #, &, _, and % can simply be escaped, e.g., `\$`.
The three characters <, >, and | can be wrapped in math mode, e.g., `$<$`.
The remainder require some TeX work-arounds. Any good book on TeX will give
some guidance.
If you type your labels inside double quotes, backslashes in TeX code need to
be escaped (doubled). Using single quotes will avoid having to do this, but
then you cannot use `\n` for line breaks. As of this writing, version 3.7 of
gnuplot processes titles given in a `plot` command differently than in other
places, and backslashes in TeX commands need to be doubled regardless of the
style of quotes.
Metapost pictures are typically used in TeX documents. Metapost deals with
fonts pretty much the same way TeX does, which is different from most other
document preparation programs. If the picture is included in a LaTeX document
using the graphics package, or in a plainTeX document via epsf.tex, and then
converted to PostScript with dvips (or other dvi-to-ps converter), the text in
the plot will usually be handled correctly. However, the text may not appear
if you send the Metapost output as-is to a PostScript interpreter.
?commands set terminal mp detailed
?set terminal mp detailed
?set term mp detailed
?mp detailed
?metapost detailed
- Set your terminal to Metapost, e.g.:
set terminal mp mono "cmtt12" 12
- Select an output-file, e.g.:
set output "figure.mp"
- Create your pictures. Each plot (or multiplot group) will generate a
separate Metapost beginfig...endfig group. Its default size will be 5 by 3
inches. You can change the size by saying `set size 0.5,0.5` or whatever
fraction of the default size you want to have.
- Quit gnuplot.
- Generate EPS files by running Metapost on the output of gnuplot:
mpost figure.mp OR mp figure.mp
The name of the Metapost program depends on the system, typically `mpost` for
a Unix machine and `mp` on many others. Metapost will generate one EPS file
for each picture.
- To include your pictures in your document you can use the graphics package
in LaTeX or epsf.tex in plainTeX:
\usepackage{graphics} % LaTeX
\input epsf.tex % plainTeX
If you use a driver other than dvips for converting TeX DVI output to PS, you
may need to add the following line in your LaTeX document:
\DeclareGraphicsRule{*}{eps}{*}{}
Each picture you made is in a separate file. The first picture is in, e.g.,
figure.0, the second in figure.1, and so on.... To place the third picture in
your document, for example, all you have to do is:
\includegraphics{figure.2} % LaTeX
\epsfbox{figure.2} % plainTeX
The advantage, if any, of the mp terminal over a postscript terminal is
editable output. Considerable effort went into making this output as clean as
possible. For those knowledgeable in the Metapost language, the default line
types and colors can be changed by editing the arrays `lt[]` and `col[]`.
The choice of solid vs dashed lines, and color vs black lines can be change by
changing the values assigned to the booleans `dashedlines` and `colorlines`.
If the default `tex` option was in effect, global changes to the text of
labels can be achieved by editing the `vebatimtex...etex` block. In
particular, a LaTeX preamble can be added if desired, and then LaTeX's
built-in size changing commands can be used for maximum flexibility. Be sure
to set the appropriate MP configuration variable to force Metapost to run
LaTeX instead of plainTeX.
?commands set terminal context
?set terminal context
?terminal context
?set term context
?term context
?context
ConTeXt is a macro package for TeX, highly integrated with Metapost
(for drawing figures) and intended for creation of high-quality PDF documents.
The terminal outputs Metafun source, which can be edited manually,
but you should be able to configure most things from outside.
For an average user of ConTeXt + gnuplot module it's recommended to refer to
`Using ConTeXt` rather than reading this page
or to read the manual of the gnuplot module for ConTeXt.
The `context` terminal supports the following options:
Syntax:
set term context {default}
{defaultsize | size <scale> | size <xsize>{in|cm}, <ysize>{in|cm}}
{input | standalone}
{timestamp | notimestamp}
{noheader | header "<header>"}
{color | colour | monochrome}
{rounded | mitered | beveled} {round | butt | squared}
{dashed | solid} {dashlength | dl <dl>}
{linewidth | lw <lw>}
{fontscale <fontscale>}
{mppoints | texpoints}
{inlineimages | externalimages}
{defaultfont | font "{<fontname>}{,<fontsize>}"}
In non-standalone (`input`) graphic only parameters `size` to select graphic
size, `fontscale` to scale all the labels for a factor <fontscale>
and font size, make sense, the rest is silently
ignored and should be configured in the .tex file which inputs the graphic.
It's highly recommended to set the proper fontsize if document font differs from
12pt, so that gnuplot will know how much space to reserve for labels.
`default` resets all the options to their default values.
`defaultsize` sets the plot size to 5in,3in.
`size` <scale> sets the plot size to <scale> times <default value>.
If two arguments are given (separated with ','), the first one sets
the horizontal size and the second one the vertical size.
Size may be given without units (in which case it means relative to the default
value), with inches ('in') or centimeters ('cm').
`input` (default) creates a graphic that can be included into another ConTeXt
document.
`standalone` adds some lines, so that the document might be compiled as-is.
You might also want to add `header` in that case.
Use `header` for any additional settings/definitions/macros
that you might want to include in a standalone graphic. `noheader` is the default.
`notimestamp` prevents printing creation time in comments
(if version control is used, one may prefer not to commit new version when only date changes).
`color` to make color plots is the default, but `monochrome` doesn't do anything special yet.
If you have any good ideas how the behaviour should differ to suit the monochrome printers better,
your suggestions are welcome.
`rounded` (default), `mitered` and `beveled` control the shape of line joins.
`round` (default), `butt` and `squared` control the shape of line caps.
See PostScript or PDF Reference Manual for explanation. For wild-behaving functions
and thick lines
it is better to use `rounded` and `round` to prevent sharp corners in line joins.
(Some general support for this should be added to Gnuplot, so that the same options
could be set for each line (style) separately).
`dashed` (default) uses different dash patterns for different line types,
`solid` draws all plots with solid lines.
`dashlength` or `dl` scales the length of the dashed-line segments by <dl>.
`linewidth` or `lw` scales all linewidths by <lw>.
(lw 1 stands for 0.5bp, which is the default line width when drawing with Metapost.)
`fontscale` scales text labels for factor <fontscale> relative to default document font.
`mppoints` uses predefined point shapes, drawn in Metapost.
`texpoints` uses easily configurable set of symbols, defined with ConTeXt
in the following way:
\defineconversion[my own points][+,{\ss x},\mathematics{\circ}]
\setupGNUPLOTterminal[context][points=tex,pointset=my own points]
`inlineimages` writes binary images to a string and only works in ConTeXt MKIV.
`externalimages` writes PNG files to disk and also works with ConTeXt MKII.
Gnuplot needs to have support for PNG images built in for this to work.
With `font` you can set font name and size in standalone graphics.
In non-standalone (`input`) mode only the font size is important
to reserve enough space for text labels.
The command
set term context font "myfont,ss,10"
will result in
\setupbodyfont[myfont,ss,10pt]
If you additionally set `fontscale` to 0.8 for example,
then the resulting font will be 8pt big and
set label ... font "myfont,12"
will come out as 9.6pt.
It is your own responsibility to provide proper typescripts (and header),
otherwise switching the font will have no effect.
For a standard font in ConTeXt MKII (pdfTeX) you could use:
set terminal context standalone header '\usetypescript[iwona][ec]' \
font "iwona,ss,11"
Please take a look into ConTeXt documentation, wiki or mailing list (archives)
for any up-to-date information about font usage.
Examples:
set terminal context size 10cm, 5cm # 10cm, 5cm
set terminal context size 4in, 3in # 4in, 3in
For standalone (whole-page) plots with labels in UTF-8 encoding:
set terminal context standalone header '\enableregime[utf-8]'
You need gnuplot module for ConTeXt
http://ctan.org/pkg/context-gnuplot
and a recent version of ConTeXt.
If you want to call gnuplot on-the-fly, you also need write18 enabled.
In most TeX distributions this can be set with shell_escape=t in texmf.cnf.
See
http://wiki.contextgarden.net/Gnuplot
for details about this terminal and for more exhaustive help & examples.
The easiest way to make plots in ConTeXt documents is
\usemodule[gnuplot]
\starttext
\title{How to draw nice plots with {\sc gnuplot}?}
\startGNUPLOTscript[sin]
set format y "%.1f"
plot sin(x) t '$\sin(x)$'
\stopGNUPLOTscript
\useGNUPLOTgraphic[sin]
\stoptext
This will run gnuplot automatically and include the resulting figure in the document.
?set terminal wxt
?terminal wxt
?set term wxt
?term wxt
?wxt
The `wxt` terminal device generates output in a separate window. The window
is created by the wxWidgets library, where the 'wxt' comes from. The actual
drawing is done via cairo, a 2D graphics library, and pango, a library for
laying out and rendering text.
Syntax:
set term wxt {<n>}
{size <width>,<height>} {position <x>,<y>}
{background <rgb_color>}
{{no}enhanced}
{font <font>} {fontscale <scale>}
{title "title"}
{linewidth <lw>}
{dashlength <dl>}
{{no}persist}
{{no}raise}
{{no}ctrl}
{close}
Multiple plot windows are supported: `set terminal wxt <n>` directs the
output to plot window number n.
The default window title is based on the window number. This title can also
be specified with the keyword "title".
Plot windows remain open even when the `gnuplot` driver is changed to a
different device. A plot window can be closed by pressing the letter 'q'
while that window has input focus, by choosing `close` from a window
manager menu, or with `set term wxt <n> close`.
The size of the plot area is given in pixels, it defaults to 640x384.
In addition to that, the actual size of the window also includes the space
reserved for the toolbar and the status bar.
When you resize a window, the plot is immediately scaled to fit in the
new size of the window. Unlike other interactive terminals, the `wxt`
terminal scales the whole plot, including fonts and linewidths, and keeps
its global aspect ratio constant, leaving an empty space painted in gray.
If you type `replot`, click the `replot` icon in the terminal toolbar or
type a new `plot` command, the new plot will completely fit in the window
and the font size and the linewidths will be reset to their defaults.
The position option can be used to set the position of the plot window.
The position option only applies to the first plot after the `set term`
command.
The active plot window (the one selected by `set term wxt <n>`) is
interactive. Its behaviour is shared with other terminal types. See `mouse`
for details. It also has some extra icons, which are supposed to be
self-explanatory.
This terminal supports an enhanced text mode, which allows font and other
formatting commands (subscripts, superscripts, etc.) to be embedded in labels
and other text strings. The enhanced text mode syntax is shared with other
gnuplot terminal types. See `enhanced` for more details.
<font> is in the format "FontFace,FontSize", i.e. the face and the size
comma-separated in a single string. FontFace is a usual font face name, such
as 'Arial'. If you do not provide FontFace, the wxt terminal will use
'Sans'. FontSize is the font size, in points. If you do not provide it,
the wxt terminal will use a size of 10 points.
For example :
set term wxt font "Arial,12"
set term wxt font "Arial" # to change the font face only
set term wxt font ",12" # to change the font size only
set term wxt font "" # to reset the font name and size
The fonts are retrieved from the usual fonts subsystems. Under Windows,
those fonts are to be found and configured in the entry "Fonts" of the
control panel. Under UNIX, they are handled by "fontconfig".
Pango, the library used to layout the text, is based on utf-8. Thus, the wxt
terminal has to convert from your encoding to utf-8. The default input
encoding is based on your 'locale'. If you want to use another encoding,
make sure gnuplot knows which one you are using. See `encoding` for more
details.
Pango may give unexpected results with fonts that do not respect the unicode
mapping. With the Symbol font, for example, the wxt terminal will use the map
provided by http://www.unicode.org/ to translate character codes to unicode.
Pango will do its best to find a font containing this character, looking for
your Symbol font, or other fonts with a broad unicode coverage, like the
DejaVu fonts. Note that "the Symbol font" is to be understood as the Adobe
Symbol font, distributed with Acrobat Reader as "SY______.PFB".
Alternatively, the OpenSymbol font, distributed with OpenOffice.org as
"opens___.ttf", offers the same characters. Microsoft has distributed a
Symbol font ("symbol.ttf"), but it has a different character set with
several missing or moved mathematic characters. If you experience problems
with your default setup (if the demo enhancedtext.dem is not displayed
properly for example), you probably have to install one of the Adobe or
OpenOffice Symbol fonts, and remove the Microsoft one.
Other non-conform fonts, such as "wingdings" have been observed working.
The rendering of the plot can be altered with a dialog available from the
toolbar. To obtain the best output possible, the rendering involves three
mechanisms : antialiasing, oversampling and hinting.
Antialiasing allows to display non-horizontal and non-vertical lines
smoother.
Oversampling combined with antialiasing provides subpixel accuracy,
so that gnuplot can draw a line from non-integer coordinates. This avoids
wobbling effects on diagonal lines ('plot x' for example).
Hinting avoids the blur on horizontal and vertical lines caused by
oversampling. The terminal will snap these lines to integer coordinates so
that a one-pixel-wide line will actually be drawn on one and only one pixel.
By default, the window is raised to the top of your desktop when a plot is
drawn. This can be controlled with the keyword "raise".
The keyword "persist" will prevent gnuplot from exiting before you
explicitely close all the plot windows.
Finally, by default the key <space> raises the gnuplot console window, and
'q' closes the plot window. The keyword "ctrl" allows you to replace those
bindings by <ctrl>+<space> and <ctrl>+'q', respectively.
These three keywords (raise, persist and ctrl) can also be set and remembered
between sessions through the configuration dialog.
?set terminal epscairo
?terminal epscairo
?set term epscairo
?term epscairo
?epscairo
The `epscairo` terminal device generates encapsulated PostScript (*.eps) using
the cairo and pango support libraries. cairo version >= 1.6 is required.
Please read the help for the `pdfcairo` terminal.
?set terminal cairolatex
?terminal cairolatex
?set term cairolatex
?term cairolatex
?cairolatex
The `cairolatex` terminal device generates encapsulated PostScript (*.eps) or
PDF output using the cairo and pango support libraries and uses LaTeX for
text output using the same routines as the `epslatex` terminal.
Syntax:
set terminal cairolatex
{eps | pdf}
{standalone | input}
{blacktext | colortext | colourtext}
{header <header> | noheader}
{mono|color}
{{no}transparent} {{no}crop} {background <rgbcolor>}
{font <font>} {fontscale <scale>}
{linewidth <lw>} {rounded|butt|square} {dashlength <dl>}
{size <XX>{unit},<YY>{unit}}
The cairolatex terminal prints a plot like `terminal epscairo` or
`terminal pdfcairo` but transfers the texts to LaTeX instead of including
them in the graph. For reference of options not explained here see `pdfcairo`.
`eps` and `pdf` select the type of graphics output. Use `eps` with
latex/dvips and `pdf` for pdflatex.
`blacktext` forces all text to be written in black even in color mode;
The `cairolatex` driver offers a special way of controlling text positioning:
(a) If any text string begins with '{', you also need to include a '}' at the
end of the text, and the whole text will be centered both horizontally
and vertically by LaTeX. (b) If the text string begins with '[', you need
to continue it with: a position specification (up to two out of t,b,l,r,c),
']{', the text itself, and finally, '}'. The text itself may be anything
LaTeX can typeset as an LR-box. \rule{}{}'s may help for best positioning.
See also the documentation for the `pslatex` terminal driver.
To create multiline labels, use \shortstack, for example
set ylabel '[r]{\shortstack{first line \\ second line}}'
The `back` option of `set label` commands is handled slightly different
than in other terminals. Labels using 'back' are printed behind all other
elements of the plot while labels using 'front' are printed above
everything else.
The driver produces two different files, one for the eps or pdf part of the
figure and one for the LaTeX part. The name of the LaTeX file is taken from
the `set output` command. The name of the eps/pdf file is derived by
replacing the file extension (normally '.tex') with '.eps' or '.pdf' instead.
There is no LaTeX output if no output file is given! Remember to close the
`output file` before next plot unless in `multiplot` mode.
In your LaTeX documents use '\input{filename}' to include the figure.
The '.eps' or '.pdf' file is included by the command \includegraphics{...},
so you must also include \usepackage{graphicx} in the LaTeX preamble. If
you want to use coloured text (option `colourtext`) you also have to include
\usepackage{color} in the LaTeX preamble.
The behaviour concerning font selection depends on the header mode.
In all cases, the given font size is used for the calculation of proper
spacing. When not using the `standalone` mode the actual LaTeX font and
font size at the point of inclusion is taken, so use LaTeX commands for
changing fonts. If you use e.g. 12pt as font size for your LaTeX
document, use '", 12"' as options. The font name is ignored. If using
`standalone` the given font and font size are used, see below for a
detailed description.
If text is printed coloured is controlled by the TeX booleans \ifGPcolor
and \ifGPblacktext. Only if \ifGPcolor is true and \ifGPblacktext is
false, text is printed coloured. You may either change them in the
generated TeX file or provide them globally in your TeX file, for example
by using
\newif\ifGPblacktext
\GPblacktexttrue
in the preamble of your document. The local assignment is only done if no
global value is given.
When using the cairolatex terminal give the name of the TeX file in the
`set output` command including the file extension (normally ".tex").
The graph filename is generated by replacing the extension.
If using the `standalone` mode a complete LaTeX header is added to the
LaTeX file; and "-inc" is added to the filename of the gaph file.
The `standalone` mode generates a TeX file that produces
output with the correct size when using dvips, pdfTeX, or VTeX.
The default, `input`, generates a file that has to be included into a
LaTeX document using the \input command.
If a font other than "" or "default" is given it is interpreted as
LaTeX font name. It contains up to three parts, separated by a comma:
'fontname,fontseries,fontshape'. If the default fontshape or fontseries
are requested, they can be omitted. Thus, the real syntax for the fontname
is '{fontname}{,fontseries}{,fontshape}'. The naming convention for all
parts is given by the LaTeX font scheme. The fontname is 3 to 4 characters
long and is built as follows: One character for the font vendor, two
characters for the name of the font, and optionally one additional
character for special fonts, e.g., 'j' for fonts with old-style numerals
or 'x' for expert fonts. The names of many fonts is described in
http://www.tug.org/fontname/fontname.pdf
For example, 'cmr' stands for Computer Modern Roman, 'ptm' for Times-Roman,
and 'phv' for Helvetica. The font series denotes the thickness of the
glyphs, in most cases 'm' for normal ("medium") and 'bx' or 'b' for bold
fonts. The font shape is 'n' for upright, 'it' for italics, 'sl' for
slanted, or 'sc' for small caps, in general. Some fonts may provide
different font series or shapes.
Examples:
Use Times-Roman boldface (with the same shape as in the surrounding text):
set terminal cairolatex font 'ptm,bx'
Use Helvetica, boldface, italics:
set terminal cairolatex font 'phv,bx,it'
Continue to use the surrounding font in slanted shape:
set terminal cairolatex font ',,sl'
Use small capitals:
set terminal cairolatex font ',,sc'
By this method, only text fonts are changed. If you also want to change
the math fonts you have to use the "gnuplot.cfg" file or the `header`
option, described below.
In `standalone` mode, the font size is taken from the given font size in the
`set terminal` command. To be able to use a specified font size, a file
"size<size>.clo" has to reside in the LaTeX search path. By default,
10pt, 11pt, and 12pt are supported. If the package "extsizes" is
installed, 8pt, 9pt, 14pt, 17pt, and 20pt are added.
The `header` option takes a string as argument. This string is written
into the generated LaTeX file. If using the `standalone` mode, it is
written into the preamble, directly before the \begin{document} command.
In the `input` mode, it is placed directly after the \begingroup command
to ensure that all settings are local to the plot.
Examples:
Use T1 fontencoding, change the text and math font to Times-Roman as well
as the sans-serif font to Helvetica:
set terminal cairolatex standalone header \
"\\usepackage[T1]{fontenc}\n\\usepackage{mathptmx}\n\\usepackage{helvet}"
Use a boldface font in the plot, not influencing the text outside the plot:
set terminal cairolatex input header "\\bfseries"
If the file "gnuplot.cfg" is found by LaTeX it is input in the preamble
the LaTeX document, when using `standalone` mode. It can be used for
further settings, e.g., changing the document font to Times-Roman,
Helvetica, and Courier, including math fonts (handled by "mathptmx.sty"):
\usepackage{mathptmx}
\usepackage[scaled=0.92]{helvet}
\usepackage{courier}
The file "gnuplot.cfg" is loaded before the header information given
by the `header` command. Thus, you can use `header` to overwrite some of
settings performed using "gnuplot.cfg"
?set terminal pdfcairo
?terminal pdfcairo
?set term pdfcairo
?term pdfcairo
?pdfcairo
The `pdfcairo` terminal device generates output in pdf. The actual
drawing is done via cairo, a 2D graphics library, and pango, a library for
laying out and rendering text.
Syntax:
set term pdfcairo
{{no}enhanced} {mono|color}
{font <font>} {fontscale <scale>}
{linewidth <lw>} {rounded|butt|square} {dashlength <dl>}
{background <rgbcolor>}
{size <XX>{unit},<YY>{unit}}
This terminal supports an enhanced text mode, which allows font and other
formatting commands (subscripts, superscripts, etc.) to be embedded in labels
and other text strings. The enhanced text mode syntax is shared with other
gnuplot terminal types. See `enhanced` for more details.
The width of all lines in the plot can be modified by the factor <lw>
specified in `linewidth`. The default linewidth is 0.5 points.
(1 "PostScript" point = 1/72 inch = 0.353 mm)
`rounded` sets line caps and line joins to be rounded;
`butt` is the default, butt caps and mitered joins.
The default size for the output is 5 inches x 3 inches. The `size` option
changes this to whatever the user requests. By default the X and Y sizes are
taken to be in inches, but other units are possible (currently only cm).
Screen coordinates always run from 0.0 to 1.0 along the full length of the
plot edges as specified by the `size` option.
<font> is in the format "FontFace,FontSize", i.e. the face and the size
comma-separated in a single string. FontFace is a usual font face name, such
as 'Arial'. If you do not provide FontFace, the pdfcairo terminal will use
'Sans'. FontSize is the font size, in points. If you do not provide it,
the pdfcairo terminal will use a nominal font size of 12 points.
However, the default fontscale parameter for this terminal is 0.5,
so the apparent font size is smaller than this if the pdf output is
viewed at full size.
For example :
set term pdfcairo font "Arial,12"
set term pdfcairo font "Arial" # to change the font face only
set term pdfcairo font ",12" # to change the font size only
set term pdfcairo font "" # to reset the font name and size
The fonts are retrieved from the usual fonts subsystems. Under Windows,
those fonts are to be found and configured in the entry "Fonts" of the
control panel. Under UNIX, they are handled by "fontconfig".
Pango, the library used to layout the text, is based on utf-8. Thus, the pdfcairo
terminal has to convert from your encoding to utf-8. The default input
encoding is based on your 'locale'. If you want to use another encoding,
make sure gnuplot knows which one you are using. See `encoding` for more
details.
Pango may give unexpected results with fonts that do not respect the unicode
mapping. With the Symbol font, for example, the pdfcairo terminal will use the map
provided by http://www.unicode.org/ to translate character codes to unicode.
Note that "the Symbol font" is to be understood as the Adobe
Symbol font, distributed with Acrobat Reader as "SY______.PFB".
Alternatively, the OpenSymbol font, distributed with OpenOffice.org as
"opens___.ttf", offers the same characters. Microsoft has distributed a
Symbol font ("symbol.ttf"), but it has a different character set with
several missing or moved mathematic characters. If you experience problems
with your default setup (if the demo enhancedtext.dem is not displayed
properly for example), you probably have to install one of the Adobe or
OpenOffice Symbol fonts, and remove the Microsoft one.
Other non-conform fonts, such as "wingdings" have been observed working.
The rendering of the plot cannot be altered yet. To obtain the best output
possible, the rendering involves two mechanisms : antialiasing and
oversampling.
Antialiasing allows to display non-horizontal and non-vertical lines
smoother.
Oversampling combined with antialiasing provides subpixel accuracy,
so that gnuplot can draw a line from non-integer coordinates. This avoids
wobbling effects on diagonal lines ('plot x' for example).
?set terminal pngcairo
?terminal pngcairo
?set term pngcairo
?term pngcairo
?pngcairo
The `pngcairo` terminal device generates output in png. The actual
drawing is done via cairo, a 2D graphics library, and pango, a library for
laying out and rendering text.
Syntax:
set term pngcairo
{{no}enhanced} {mono|color}
{{no}transparent} {{no}crop} {background <rgbcolor>
{font <font>} {fontscale <scale>}
{linewidth <lw>} {rounded|butt|square} {dashlength <dl>}
{pointscale <ps>}
{size <XX>{unit},<YY>{unit}}
This terminal supports an enhanced text mode, which allows font and other
formatting commands (subscripts, superscripts, etc.) to be embedded in labels
and other text strings. The enhanced text mode syntax is shared with other
gnuplot terminal types. See `enhanced` for more details.
The width of all lines in the plot can be modified by the factor <lw>.
`rounded` sets line caps and line joins to be rounded;
`butt` is the default, butt caps and mitered joins.
The default size for the output is 640 x 480 pixels. The `size` option
changes this to whatever the user requests. By default the X and Y sizes are
taken to be in pixels, but other units are possible (currently cm and inch).
A size given in centimeters or inches will be converted into pixels assuming
a resolution of 72 dpi. Screen coordinates always run from 0.0 to 1.0 along
the full length of the plot edges as specified by the `size` option.
<font> is in the format "FontFace,FontSize", i.e. the face and the size
comma-separated in a single string. FontFace is a usual font face name, such
as 'Arial'. If you do not provide FontFace, the pngcairo terminal will use
'Sans'. FontSize is the font size, in points. If you do not provide it,
the pngcairo terminal will use a size of 12 points.
For example :
set term pngcairo font "Arial,12"
set term pngcairo font "Arial" # to change the font face only
set term pngcairo font ",12" # to change the font size only
set term pngcairo font "" # to reset the font name and size
The fonts are retrieved from the usual fonts subsystems. Under Windows,
those fonts are to be found and configured in the entry "Fonts" of the
control panel. Under UNIX, they are handled by "fontconfig".
Pango, the library used to layout the text, is based on utf-8. Thus, the pngcairo
terminal has to convert from your encoding to utf-8. The default input
encoding is based on your 'locale'. If you want to use another encoding,
make sure gnuplot knows which one you are using. See `encoding` for more detail.
Pango may give unexpected results with fonts that do not respect the unicode
mapping. With the Symbol font, for example, the pngcairo terminal will use the map
provided by http://www.unicode.org/ to translate character codes to unicode.
Note that "the Symbol font" is to be understood as the Adobe
Symbol font, distributed with Acrobat Reader as "SY______.PFB".
Alternatively, the OpenSymbol font, distributed with OpenOffice.org as
"opens___.ttf", offers the same characters. Microsoft has distributed a
Symbol font ("symbol.ttf"), but it has a different character set with
several missing or moved mathematic characters. If you experience problems
with your default setup (if the demo enhancedtext.dem is not displayed
properly for example), you probably have to install one of the Adobe or
OpenOffice Symbol fonts, and remove the Microsoft one.
Rendering uses oversampling, antialiasing, and font hinting to the extent
supported by the cairo and pango libraries.
?commands set terminal lua
?set terminal lua
?set term lua
?terminal lua
?term lua
?lua
The `lua` generic terminal driver works in conjunction with an
external Lua script to create a target-specific plot file.
Currently the only supported target is TikZ -> pdflatex.
Information about Lua is available at http://www.lua.org .
Syntax:
set terminal lua <target name> | "<file name>"
{<script_args> ...}
{help}
A 'target name' or 'file name' (in quotes) for a script is mandatory.
If a 'target name' for the script is given, the terminal will look for
"gnuplot-<target name>.lua" in the local directory and on failure in
the environmental variable GNUPLOT_LUA_DIR.
All arguments will be provided to the selected script for further
evaluation. E.g. 'set term lua tikz help' will cause the script itself
to print additional help on options and choices for the script.
?set terminal lua tikz
?set term lua tikz
?term lua tikz
The TikZ driver is one output mode of the generic Lua terminal.
Syntax:
set terminal lua tikz
{latex | tex | context}
{color | monochrome}
{nooriginreset | originreset}
{nogparrows | gparrows}
{nogppoints | gppoints}
{picenvironment | nopicenvironment}
{noclip | clip}
{notightboundingbox | tightboundingbox}
{background "<colorpec>"}
{size <x>{unit},<y>{unit}}
{scale <x>,<y>}
{plotsize <x>{unit},<y>{unit}}
{charsize <x>{unit},<y>{unit}}
{font "<fontdesc>"}
{{fontscale | textscale} <scale>}
{dashlength | dl <DL>}
{linewidth | lw <LW>}
{nofulldoc | nostandalone | fulldoc | standalone}
{{preamble | header} "<preamble_string>"}
{tikzplot <ltn>,...}
{notikzarrows | tikzarrows}
{rgbimages | cmykimages}
{noexternalimages|externalimages}
{bitmap | nobitmap}
{providevars <var name>,...}
{createstyle}
{help}
For all options that expect lengths as their arguments they
will default to 'cm' if no unit is specified. For all lengths
the following units may be used: 'cm', 'mm', 'in' or 'inch',
'pt', 'pc', 'bp', 'dd', 'cc'. Blanks between numbers and units
are not allowed.
'monochrome' disables line coloring and switches to grayscaled
fills.
'originreset' moves the origin of the TikZ picture to the lower
left corner of the plot. It may be used to align several plots
within one tikzpicture environment. This is not tested with
multiplots and pm3d plots!
'gparrows' use gnuplot's internal arrow drawing function
instead of the ones provided by TikZ.
'gppoints' use gnuplot's internal plotmark drawing function
instead of the ones provided by TikZ.
'nopicenvironment' omits the declaration of the 'tikzpicture'
environment in order to set it manually. This permits putting
some PGF/TikZ code directly before or after the plot.
'clip' crops the plot at the defined canvas size. Default is
'noclip' by which only a minimum bounding box of the canvas size
is set. Neither a fixed bounding box nor a crop box is set if the
'plotsize' or 'tightboundingbox' option is used.
If 'tightboundingbox' is set the 'clip' option is ignored and the
final bounding box is the natural bounding box calculated by tikz.
'background' sets the background color to the value specified in
the <colorpec> argument. <colorspec> must be a valid color name or
a 3 byte RGB code as a hexadecimal number with a preceding number
sign ('#'). E.g. '#ff0000' specifies pure red. If omitted the
background is transparent.
The 'size' option expects two lenghts <x> and <y> as the canvas
size. The default size of the canvas is 12.5cm x 8.75cm.
The 'scale' option works similar to the 'size' option but expects
scaling factors <x> and <y> instead of lengths.
The 'plotsize' option permits setting the size of the plot area
instead of the canvas size, which is the usual gnuplot behaviour.
Using this option may lead to slightly asymmetric tic lengths.
Like 'originreset' this option may not lead to convenient results
if used with multiplots or pm3d plots. An alternative approach
is to set all margins to zero and to use the 'noclip' option.
The plot area has then the dimensions of the given canvas sizes.
The 'charsize' option expects the average horizontal and vertical
size of the used font. Look at the generated style file for an
example of how to use it from within your TeX document.
'fontscale' or 'textscale' expects a scaling factor as a parameter.
All texts in the plot are scaled by this factor then.
'dashlength' or 'dl' scales the length of dashed-line segments by <DL>,
which is a floating-point number greater than zero. 'linewidth' or
'lw' scales all linewidths by <LW>.
The options 'tex', 'latex' and 'context' choose the TeX output
format. LaTeX is the default. To load the style file put the
according line at the beginning of your document:
\input gnuplot-lua-tikz.tex % (for plain TeX)
\usepackage{gnuplot-lua-tikz} % (for LaTeX)
\usemodule[gnuplot-lua-tikz] % (for ConTeXt)
'createstyle' derives the TeX/LaTeX/ConTeXt styles from the script
and writes them to the appropriate files.
'fulldoc' or 'standalone' produces a full LaTeX document for direct
compilation.
'preamble' or 'header' may be used to put any additional LaTeX code
into the document preamble in standalone mode.
With the 'tikzplot' option the '\path plot' command will be used
instead of only '\path'. The following list of numbers of linetypes
(<ltn>,...) defines the affected plotlines. There exists a plotstyle
for every linetype. The default plotstyle is 'smooth' for every
linetype >= 1.
By using the 'tikzarrows' option the gnuplot arrow styles defined by
the user will be mapped to TikZ arrow styles. This is done by 'misusing'
the angle value of the arrow definition. E.g. an arrow style with the
angle '7' will be mapped to the TikZ style 'gp arrow 7' ignoring all the
other given values. By default the TikZ terminal uses the stealth' arrow
tips for all arrows. To obtain the default gnuplot behaviour please use
the 'gparrows' option.
With 'cmykimages' the CMYK color model will be used for inline image data
instead of the RGB model. All other colors (like line colors etc.) are
not affected by this option, since they are handled e.g. by LaTeX's
xcolor package. This option is ignored if images are externalized.
By using the 'externalimages' option all bitmap images will be written
as external PNG images and included at compile time of the document.
Generating DVI and later postscript files requires to convert the PNGs
into EPS files in a seperate step e.g. by using ImageMagick's `convert`.
Transparent bitmap images are always generated as an external PNGs.
The 'nobitmap' option let images be rendered as filled rectangles instead
of the nativ PS or PDF inline image format. This option is ignored if
images are externalized.
The 'providevars' options makes gnuplot's internal and user variables
available by using the '\gpgetvar{<var name>}' commmand within the TeX
script. Use gnuplot's 'show variables all' command to see the list
of valid variables.
The <fontdesc> string may contain any valid TeX/LaTeX/ConTeXt font commands
like e.g. '\small'. It is passed directly as a node parameter in form of
"font={<fontdesc>}". This can be 'misused' to add further code to a node,
e.g. '\small,yshift=1ex' or ',yshift=1ex' are also valid while the
latter does not change the current font settings. One exception is
the second argument of the list. If it is a number of the form
<number>{unit} it will be interpreted as a fontsize like in other
terminals and will be appended to the first argument. If the unit is
omitted the value is interpreted as 'pt'. As an example the string
'\sffamily,12,fill=red' sets the font to LaTeX's sans serif font at
a size of 12pt and red background color.
The same applies to ConTeXt, e.g. '\switchtobodyfont[iwona],10' changes the
font to Iwona at a size of 10pt.
Plain TeX users have to change the font size explicitly within the first
argument. The second should be set to the same value to get proper scaling
of text boxes.
Strings have to be put in single or double quotes. Double quoted
strings may contain special characters like newlines '\n' etc.
?commands set terminal tikz
?set terminal tikz
?set term tikz
?terminal tikz
?term tikz
?tikz
This driver creates output for use with the TikZ package of graphics macros
in TeX. It is currently implemented via an external lua script, and
`set term tikz` is a short form of the command `set term lua tikz`.
See `term lua` for more information. Use the command `set term tikz help`
to print terminal options.
?bugs
Please e-mail bug reports to the gnuplot-bugs mailing list or
upload the report to the gnuplot web site on SourceForge.
Please give complete information on the version of gnuplot you are using
and, if possible, a test script that demonstrates the bug.
See `seeking-assistance`.
It is not possible to use inline data (e.g. plot '-' ...) inside the curly
brackets of a `do` or `while` loop.
The gamma and bessel functions do not support complex arguments.
Coordinates specified as "time" wrap at 24 hours.
Parametric curves: The 'nohidden3d' option to exempt individual plots from the
global setting 'set hidden3d' does not work for parametric curves.
Iteration inside a `plot` command does not work for parametric curves.
X11 terminal: It is difficult to select UTF-8 fonts.
Only one color palette at a time is active for any given x11 plot window.
This means that multiplots whose constituent plots use different
palettes will not display correctly in x11.
Qt terminal: 3D rotation of polygons and surfaces can be slow;
this is strongly affected by the Qt rendering mode (see Qt documentation).
The `raise` and `lower` functions are unreliable.
?bugs external_libraries
External library GD (used by PNG/JPEG/GIF drivers):
Versions of libgd through 2.0.33 had various bugs in mapping the characters
of Adobe's Symbol font. Also it was possible to trigger a library segfault if
an anti-aliased line crosses an upper corner of the canvas.
External library PDFlib (used by PDF driver):
Gnuplot can be linked against libpdf versions 4, 5, or 6. However, these
versions differ in their handling of piped I/O. Therefore gnuplot scripts
using piped output to PDF may work only for some versions of PDFlib.
External library svgalib (used by linux and vgagl driver):
Requires gnuplot to be suid root (bad!) and has many bugs that are specific
to the video card or graphics driver used in X11.
Internationalization (locale settings):
Gnuplot uses the C runtime library routine setlocale() to control
locale-specific formatting of input and output number, times, and date strings.
The locales available, and the level of support for locale features such as
"thousands' grouping separator", depend on the internationalization support
provided by your individual machine.
|