uname + uname SUPER-UX ncdump --version + ncdump --version ncdump: ERROR: Illegal option -- - ncdump [-c|-h] [-v ...] [[-b|-f] [c|f]] [-l len] [-n name] [-p n[,n]] [-x] file [-c] Coordinate variable data and header information [-h] Header information only, no data [-v var1[,...]] Data for variable(s) ,... only [-b [c|f]] Brief annotations for C or Fortran indices in data [-f [c|f]] Full annotations for C or Fortran indices in data [-l len] Line length maximum in data section (default 80) [-n name] Name for netCDF (default derived from file name) [-p n[,n]] Display floating-point values with less precision [-x] Output XML (NcML) instead of CDL file Name of netCDF file netcdf library version 3.6.1 of Nov 29 2006 10:10:15 $ ****** Program Information ****** Real Time (sec) : 0.016739 User Time (sec) : 0.000127 Sys Time (sec) : 0.006031 Vector Time (sec) : 0.000000 Inst. Count : 14873 V. Inst. Count : 0 V. Element Count : 0 FLOP Count : 3 MOPS : 117.110236 MFLOPS : 0.023622 A.V. Length : 0.000000 V. Op. Ratio (%) : 0.000000 Memory Size (MB) : 48.000000 MIPS : 117.110236 I-Cache (sec) : 0.000065 O-Cache (sec) : 0.000045 Bank (sec) : 0.000000 Start Time (date) : 2007/05/24 14:26:40 End Time (date) : 2007/05/24 14:26:40 cd /scratchdir/p86caub/XML_SX/xmlf90-1.2g/Examples/dom + cd /scratchdir/p86caub/XML_SX/xmlf90-1.2g/Examples/dom ./text + ./text allocated nodes: 541 number of para elements: 35 Dumping pure text under them... | Permission is granted to copy, distribute and/or modify this document | | under the terms of the GNU Free Documentation License, Version 1.1 or | | any later version published by the Free Software Foundation; with no | | | |, | | or | | | |, each as defined in the license. A copy of | | the license can be found in the file | | included with jEdit. | | | | The SideKick plugin itself is released under the GNU General Public License. | | A copy of the GPL can be found in the jEdit online help. | | | | The SideKick plugin provides a dockable window in which other plugins can | | display buffer structure. | | | | | |>| |>| | displays the current buffer's structure in a | | dockable window. This window is floating by | | default, but it can be docked into the view in the | | pane of the | | dialog box. | | | | The SideKick plugin automatically parses buffers | | when they are loaded or saved, where possible. | | Optionally, buffers can also be parsed on the fly, but this uses a fair bit of | | memory and processor power so it is disabled by default. | | | | | |>| |>| | is a checkbox menu item that toggles on-the-fly | | parsing, for the current buffer only. | | | | The current buffer can be parsed at any other time by clicking the parse | | button in the | | window, or by | | invoking the | | | |>| |>| | command. | | | | Any errors found while parsing the buffer are sent to the | | | | plugin, which means they are highlighted | | in the text area, and shown in the | | | |>| |>| | window. See the | | documentation for the | | plugin for details. | | | | Clicking on a node in the tree will move the caret to its location in the | | buffer; | | conversely, moving the caret in the buffer will select the corresponding | | node. | | | | | |-clicking on a node will select that node in the text | | area. | |-clicking on a node will narrow the text area | | display to that node. | | | | If the structure browser window is docked into the current view, hovering the mouse | | over a node will display its attributes in the status bar. | | | | | |>| |>| | moves the caret to start of the structure | | element (| |). | | | | | |>| |>| | moves the caret to start of the next asset. | | | | | |>| |>| | selects the asset at the caret position. | | | | The SideKick plugin adds a new | | fold handler that | | folds the buffer according to the structure tree. See the jEdit user's guide | | for general details about folding. | | | |>| |>| | hides all text except that of the asset at the | | caret location. This works in any folding mode, not just the | | mode. | | | | A completion popup can be shown at any time | | by invoking the | | | |>| |>| | command. Each plugin that uses SideKick | | implements its own specific completion behavior; see the plugin documentation | | for details. | | | | By itself the SideKick plugin is not very useful; it relies on other plugins to | | provide buffer structure information. This chapter gives a brief overview of | | how it's done. | | | | First you will also need to add a dependency for the SideKick plugin in your plugin's | | property file: | | | | Note that you must replace | | with the | | appropriate number, as dependency properties must have consecutive numbers. | | | | All SideKick plugin classes are in the | | package; | | you will need to add | | statements where appropriate. | | | | Parser instances must be registered in your plugin's | | method using the following method in the | | class: | | | | A corresponding method must be called from your plugin's | | method: | | | | | | is an abstract class. The constructor | | takes one string parameter. This string is used in several properties: | | | | - specifies a human-readable label for the parser, shown in status messages. | | | | - properties of this form are used to associate a parser with an edit mode. | | | | For example, the XML plugin, which provides two | | implementations, defines these properties: | | | | The | | has one abstract method that all | | subclasses must implement: | | | | The latter parameter is an instance of a class provided by the | | | | plugin; consult its documentation for | | details. | | | | The method is called from a thread, so care must be taken to access the | | buffer in a thread-safe manner; the API documentation for the | | | | class describes how this is done. | | | | The constructor of the | | class takes | | one parameter, which is the file name (to be shown at the root of the structure | | tree). | | | | Your implementation of the | | method should add | | structure elements to the | | field of the | | | | instance. This field is an | | instance of Java's | | class, | | and is given a value by the | | constructor. | | | | This part has not been written yet. Use the source, Luke! | | | | requires | | jEdit 4.1pre11.| |Initial release. | | | Normalizing... ==================================================== allocated nodes: 434 number of para elements: 35 Dumping pure text under them... | Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, V ersion 1.1 or any later version published by the Free Software Foundation; with no | |, | | or | |, each as defined in the license. A copy of the license can be found in the file | | included with jEdit. | | The SideKick plugin itself is released under the GNU General Public License. A copy of the GPL can be found in the jEdit onlin e help. | | The SideKick plugin provides a dockable window in which other plugins can display buffer structure. | | | |>| |>| | displays the current buffer's structure in a dockable window. This window is floating by default, but it can be docked into the view in the | | pane of the | | dialog box. | | The SideKick plugin automatically parses buffers when they are loaded or saved, where possible. Optionally, buffers can also b e parsed on the fly, but this uses a fair bit of memory and processor power so it is disabled by default. | | | |>| |>| | is a checkbox menu item that toggles on-the-fly parsing, for the current buffer only. | | The current buffer can be parsed at any other time by clicking the parse button in the | | window, or by invoking the | |>| |>| | command. | | Any errors found while parsing the buffer are sent to the | | plugin, which means they are highlighted in the text area, and shown in the | |>| |>| | window. See the documentation for the | | plugin for details. | | Clicking on a node in the tree will move the caret to its location in the buffer; conversely, moving the caret in the buffer w ill select the corresponding node. | | | |-clicking on a node will select that node in the text area. | |-clicking on a node will narrow the text area display to that node. | | If the structure browser window is docked into the current view, hovering the mouse over a node will display its attributes in t he status bar. | | | |>| |>| | moves the caret to start of the structure element (| |). | | | |>| |>| | moves the caret to start of the next asset. | | | |>| |>| | selects the asset at the caret position. | | The SideKick plugin adds a new | | fold handler that folds the buffer according to the structure tree. See the jEdit user's guide for general details about foldin g. | | | |>| |>| | hides all text except that of the asset at the caret location. This works in any folding mode, not just the | | mode. | | A completion popup can be shown at any time by invoking the | |>| |>| | command. Each plugin that uses SideKick implements its own specific completion behavior; see the plugin documentation for detai ls. | | By itself the SideKick plugin is not very useful; it relies on other plugins to provide buffer structure information. This chapt er gives a brief overview of how it's done. | | First you will also need to add a dependency for the SideKick plugin in your plugin's property file: | | Note that you must replace | | with the appropriate number, as dependency properties must have consecutive numbers. | | All SideKick plugin classes are in the | | package; you will need to add | | statements where appropriate. | | Parser instances must be registered in your plugin's | | method using the following method in the | | class: | | A corresponding method must be called from your plugin's | | method: | | | | is an abstract class. The constructor takes one string parameter. This string is used in several properties: | | - specifies a human-readable label for the parser, shown in status messages. | | - properties of this form are used to associate a parser with an edit mode. | | For example, the XML plugin, which provides two | | implementations, defines these properties: | | The | | has one abstract method that all subclasses must implement: | | The latter parameter is an instance of a class provided by the | | plugin; consult its documentation for details. | | The method is called from a thread, so care must be taken to access the buffer in a thread-safe manner; the API documentation fo r the | | class describes how this is done. | | The constructor of the | | class takes one parameter, which is the file name (to be shown at the root of the structure tree). | | Your implementation of the | | method should add structure elements to the | | field of the | | instance. This field is an instance of Java's | | class, and is given a value by the | | constructor. | | This part has not been written yet. Use the source, Luke! | | requires jEdit 4.1pre11.| |Initial release. | ****** Program Information ****** Real Time (sec) : 0.153547 User Time (sec) : 0.083368 Sys Time (sec) : 0.019501 Vector Time (sec) : 0.006893 Inst. Count : 19957676. V. Inst. Count : 101299. V. Element Count : 1611884. FLOP Count : 22607. MOPS : 257.510558 MFLOPS : 0.271170 VLEN : 15.912141 V. Op. Ratio (%) : 7.508219 Memory Size (MB) : 48.031250 MIPS : 239.391178 I-Cache (sec) : 0.021848 O-Cache (sec) : 0.010598 Bank (sec) : 0.000003 Start Time (date) : 2007/05/24 14:26:40 End Time (date) : 2007/05/24 14:26:41 ###cd /home/p86caub/IPSLIO/bin ###./main.exe ###export DISPLAY=mercure:38.0 ###totalview opa.xx core.26012 ###cd /scratchdir/p86caub/COUPHR3 ###mcs -p lmdz.x ###mcs -p oasis ###mcs -p opa.xx ###cd /scratchdir/p86caub/TESTNEM2 ###mcs -p oasis1 + cd / + rm -rf /tmpdir/nqs.78655.bt3540 /tmp/nqs.78655.Cd3541