IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changeset 1372


Ignore:
Timestamp:
Aug 3, 2004, 10:42:30 AM (22 years ago)
Author:
desonia
Message:

* empty log message *

Location:
trunk/psLib
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • trunk/psLib/psLib.kdevses

    r1368 r1372  
    33<KDevPrjSession>
    44 <DocsAndViews NumberOfDocuments="2" >
    5   <Doc0 NumberOfViews="1" URL="file:/home/desonia/psLib/src/dataManip/psStats.c" >
    6    <View0 line="1442" Type="???" >
    7     <AdditionalSettings Top="2" Width="1104" Attach="1" Height="787" Left="2" MinMaxMode="0" />
     5  <Doc0 NumberOfViews="1" URL="file:/home/desonia/psLib/src/mainpage.dox" >
     6   <View0 line="46" Type="???" >
     7    <AdditionalSettings Top="1" Width="1305" Attach="1" Height="750" Left="1" MinMaxMode="0" />
    88   </View0>
    99  </Doc0>
    10   <Doc1 NumberOfViews="1" URL="file:/home/desonia/psLib/src/dataManip/psStats.h" >
    11    <View0 line="0" Type="???" >
    12     <AdditionalSettings Top="2" Width="1104" Attach="1" Height="787" Left="2" MinMaxMode="0" />
     10  <Doc1 NumberOfViews="1" URL="file:/home/desonia/psLib/src/pslib.h" >
     11   <View0 line="12" Type="???" >
     12    <AdditionalSettings Top="1" Width="782" Attach="1" Height="583" Left="1" MinMaxMode="0" />
    1313   </View0>
    1414  </Doc1>

  • trunk/psLib/src/Makefile.Globals

    r1137 r1372  
    55##  Assumptions:    Variable "prefix" already defined
    66##
    7 ##  $Revision: 1.12 $  $Name: not supported by cvs2svn $
    8 ##  $Date: 2004-06-30 01:09:12 $
     7##  $Revision: 1.13 $  $Name: not supported by cvs2svn $
     8##  $Date: 2004-08-03 20:42:30 $
    99##
    1010##  Copyright 2004 Maui High Performance Computing Center, University of Hawaii
    … …  
    2929
    3030ifndef testbindir
    31     export testbindir = $(prefix)/bin/test
     31    export testbindir = $(prefix)/testbin
    3232endif
    3333

  • trunk/psLib/src/mainpage.dox

    r1269 r1372  
    1 /** @mainpage psLib Image Processing Library
    2 
     1/** @mainpage psLib Image Processing Library - Release 2
    32
    43@section intro Introduction
    54
    6 This library contains the Pan-STARRS Image Processing Pipeline (IPP) toolkit,
    7 psLib. The intended use is to provide a library of basic software functions which
     5This library contains the Pan-STARRS Image Processing Pipeline (IPP) common library,
     6psLib. The intended use is to provide a set of basic software functions in which
    87can be used throughout the Pan-STARRS project to simplify programming tasks. Among
    9 the benefits are: reuse of code, simplification of testing, streamlining of code,
    10 and isolation of functionality that may be subject to change.     
     8the benefits are:
     9 - reuse of code,
     10 - simplification of testing,
     11 - streamlining of code, and
     12 - isolation of functionality that may be subject to change.     
    1113
    1214The capabilities provided by psLib are grouped into the following areas which are
    1315also reflected in the file system directory structure:
    1416 - System Utilities
     17 - Data Collections
    1518 - Image Operations
    16  - Data Collections
    1719 - Data Manipulation
    1820 - Astronomy
    … …  
    2123data types of the earlier entries.
    2224
    23 The installed code for psLib consists of header files and binary libraries in the form of static
    24 (libpslib.a) and shared (libpslib.so or libpslib.dylib for OX/X.) Assuming these components
    25 have been built and installed in the standard library path, psLib may be used within a program by
    26 including the line #include <pslib.h> and linking with -lpslib.
    27 
     25The installed code for psLib consists of header files and binary libraries in
     26the form of static (libpslib.a) and shared (libpslib.so or libpslib.dylib,
     27depending on operating system.) Assuming these components have been built and
     28installed in the standard library path, psLib may be used within a program by
     29including the line #include <pslib.h> and linking using the '-lpslib' option
     30while linking.
    2831
    2932
    3033@section extinstall Required 3rd Party Libraries
    3134
    32 Before building psLib from source, several 3rd party software libraries must be installed.
    33 These include:
    34  - GNU Scientific Library (GSL), Available at http://www.gnu.org/software/gsl
    35  - Fastest Fourier Transform in the West (FFTW), Available at http://www.fftw.org
    36  - C Flexible Image Transport System Input output (CFITSIO), Available at http://heasarc.gsfc.nasa.gov/docs/software/fitsio
     35Before building psLib from source, several 3rd party software libraries must
     36be installed.  These include:
     37 - GNU Scientific Library (GSL)
     38     - Compatibility tested with version is 1.4
     39     - Available at http://www.gnu.org/software/gsl
     40 - Fastest Fourier Transform in the West (FFTW), version 3
     41     - Compatibility tested with version is 3.0.1
     42     - Available at http://www.fftw.org
     43 - C Flexible Image Transport System Input output (CFITSIO), version 2.480 or later
     44     - Available at http://heasarc.gsfc.nasa.gov/docs/software/fitsio
     45     - Compatibility tested with version is 2.490
     46     - Versions earlier than 2.480 will not work as new functionality introduced in 2.480 is exercised
     47 - Doxygen Documentation System
     48     - Available at http://www.doxygen.org
     49     - Compatibility tested with version 1.3.6
    3750
    38 If you use a Darwin (Mac OS X) system, a dlfcn compatability library needs to be
    39 installed on the system. This can be obtained from the Fink project on SourceForge
    40 (the dlcompat package at http://www.sf.net/projects/fink). The Darwin 7.0 (OS X 10.3)
    41 'devtools' package seems to also include dlfcn support, so explicit installation of a
    42 dlfcn compatibility layer may not be required for this version of Darwin.
    43 
     51We recommend using the particular versions listed as compatibility tested, as
     52that is the only versions of the external libraries tested to work well with psLib. 
     53Though it is quite possible that later versions of the libraries listed will also
     54work as well, care must be taken when upgrading these libraries to verify that its
     55functionality is compatible with the tested version.
    4456
    4557@section install How to Build from Source
    4658
    4759The psLib code should to be downloaded from either the tar file posted on:
    48 https://gforge.mhpcc.hawaii.edu/projects/panstarrs/ or directly from the CVS server
    49 with the following command:
     60
     61https://mhpcc.pan-starrs.org/cgi-bin/viewcvs.cgi/releases/rel2
     62
     63or directly from the CVS server with the following command:
    5064<pre>
    51 $ cvs -d:ext:username@gforge.mhpcc.hawaii.edu:data/panstarrs/cvsroot co -P psLib
     65$ cvs -d:ext:username@mhpcc.pan-starrs.org:/data/panstarrs/cvsroot co -r rel2_0 psLib
    5266</pre>
    5367
    5468   
    55 The source should build from the Makefile in the psLib/src directory.  The
     69The source should build using the Makefile in the psLib/src directory.  The
    5670recommended steps are:
    5771<pre>
     72$ cd psLib/src
    5873$ make
    5974$ make install
    … …  
    6277
    6378
    64 @section run How to Run Tests
     79@section run How to Build and Run Tests
    6580
    66 Since psLib is a library, there is no executable, per se. However, to test the installation, users
    67 may execute the FullUnitTest script:
     81Since psLib is a library, there is no executable, per se. However, to test the
     82installation, users may execute the the unit test suite.  To build the unit test
     83suite, do the following:
    6884<pre>
    6985$ cd psLib/test
    7086$ make
    7187$ make install
    72 $ FullUnitTest
     88$ make installtests
    7389</pre>
    74 <i>This builds and executes test files for each of the psLib functional areas.</i>
     90<i>This builds and installs the unit test files to the psLib/testbin directory.</i>
    7591
     92To run the unit test suite, do the following:
     93<pre>
     94$ cd psLib/testbin
     95$ ./FullUnitTest
     96</pre>
     97or to run a particular test
     98<pre>
     99$ ./runTest testfilename
     100</pre>
    76101
    77 @section doc How to Create Documentation
     102@section doc How to Create Code Documentation
    78103
    79 Both HTML and man page documentation may also be generated:
     104Both HTML and man page documentation may also be generated from the inline
     105documentation in the code using the following commands:
    80106<pre>
    81107$ cd psLib/src
    … …  
    84110<i>This places documentation in psLib/docs.</i>
    85111
     112Also, a prebuilt set of documentation can be found at:
     113
     114https://mhpcc.pan-starrs.org/docs/
     115
    86116*/

  • trunk/psLib/test/Makefile

    r1308 r1372  
    33##  Makefile:   test
    44##
    5 ##  $Revision: 1.7 $  $Name: not supported by cvs2svn $
    6 ##  $Date: 2004-07-28 02:50:32 $
     5##  $Revision: 1.8 $  $Name: not supported by cvs2svn $
     6##  $Date: 2004-08-03 20:42:30 $
    77##
    88##  Copyright 2004 Maui High Performance Computing Center, University of Hawaii
    … …  
    6262        $(MAKE) --directory=dataManip install
    6363        $(MAKE) --directory=sysUtils install
     64        $(MAKE) --directory=astronomy install
    6465
    6566# Define PHONY target "distclean" which will cleanup the distribution

  • trunk/psLib/test/sysUtils/verified/tst_psMemory.stderr

    r1365 r1372  
    1717 <DATE> <TIME> |<HOST>|I|  TPOutOfMemory|Upon requesting more memory than is available, psalloc shall call the psMemExhaustedCallback.
    1818 <DATE> <TIME> |<HOST>|I|TPOutOfMemoryEx|Custom MemExhaustedCallback was invoked.
    19  <DATE> <TIME> |<HOST>|A|      p_psAlloc|Failed to allocate 4294966295 bytes at tst_psMemory.c:206
     19 <DATE> <TIME> |<HOST>|A|      p_psAlloc|Failed to allocate 4294966295 bytes at tst_psMemory.c:228
    2020
    2121---> TESTPOINT PASSED (psMemory{outOfMemory} | tst_psMemory.c)
    … …  
    2828
    2929 <DATE> <TIME> |<HOST>|I|TPReallocOutOfM|Upon requesting more memory than is available, psRealloc shall call the psMemExhaustedCallback.
    30  <DATE> <TIME> |<HOST>|A|    p_psRealloc|Failed to reallocate -1001 bytes at tst_psMemory.c:171
     30 <DATE> <TIME> |<HOST>|A|    p_psRealloc|Failed to reallocate -1001 bytes at tst_psMemory.c:193
    3131
    3232---> TESTPOINT PASSED (psMemory{reallocOutOfMemory} | tst_psMemory.c)
    … …  
    7070 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|following psMemCheckLeaks call should produce one instance.
    7171                   file:line ID
    72          tst_psMemory.c:356  1
     72         tst_psMemory.c:378  1
    7373 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|Testing psMemCheckLeaks again with a different leak location
    7474 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|following psMemCheckLeaks call should produce one error.
    7575                   file:line ID
    76          tst_psMemory.c:386  11
     76         tst_psMemory.c:408  11
    7777 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|Testing psMemCheckLeaks again with multiple leak locations.
    7878 <DATE> <TIME> |<HOST>|I|   TPcheckLeaks|following psMemCheckLeaks call should produce two errors.
    7979                   file:line ID
    80          tst_psMemory.c:414  16
    81          tst_psMemory.c:414  14
     80         tst_psMemory.c:436  16
     81         tst_psMemory.c:436  14
    8282
    8383---> TESTPOINT PASSED (psMemory{checkLeaks} | tst_psMemory.c)
    … …  
    115115 <DATE> <TIME> |<HOST>|I| TPmultipleFree|Next should be an error about multiple freeing.
    116116 <DATE> <TIME> |<HOST>|E|  checkMemBlock|Memory Corruption: memory block 1 was freed but still used.
    117  <DATE> <TIME> |<HOST>|E|memProblemCallb|Block 1 allocated at tst_psMemory.c:526 freed more than once at tst_psMemory.c:531
    118  <DATE> <TIME> |<HOST>|A|memProblemCallb|Detected a problem in the memory system at tst_psMemory.c:531
     117 <DATE> <TIME> |<HOST>|E|memProblemCallb|Block 1 allocated at tst_psMemory.c:548 freed more than once at tst_psMemory.c:553
     118 <DATE> <TIME> |<HOST>|A|memProblemCallb|Detected a problem in the memory system at tst_psMemory.c:553
    119119
    120120---> TESTPOINT PASSED (psMemory{multipleFree} | tst_psMemory.c)
Note: See TracChangeset for help on using the changeset viewer.