Changeset 5035 for trunk/psModules/src/mainpage.dox
- Timestamp:
- Sep 13, 2005, 11:18:21 AM (21 years ago)
- File:
-
- 1 edited
-
trunk/psModules/src/mainpage.dox (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/psModules/src/mainpage.dox
r3651 r5035 11 11 Modules in this release include: 12 12 13 - Astrometry (pmAstrometry) 13 14 - Subtract bias (pmSubtractBias) 14 15 - Correct for non-linearity (pmNonLinear) 15 16 - Flat-field (pmFlatField) 16 - Mask bad pixels (pmMaskBadPixels) 17 - Mask bad pixels (pmMaskBadPixels and pmMaskBadPixelsErrors) 18 - Image Combine (pmImageCombine) 19 - Image Subtract (pmImageSubtract) 17 20 - Combine readouts (pmReadoutCombine) 18 21 - Subtract sky (pmSubtractSky) … … 47 50 https://mhpcc.pan-starrs.org/code/releases 48 51 49 Though MHPCC recommends using the released packaged tar files descibed above,50 both daily development snapshots and direct CVS access is available. The daily51 snapshots are available at52 53 https://mhpcc.pan-starrs.org/code/snapshots54 55 These snapshots represents development code as found in CVS on the day56 specified in the filename. This code set may not be functional, vary in57 testing, etc. Reasonable efforts are made to ensure that the code does58 actually compile, but given the nature of code development, even that is not59 always the case. Use snapshots with great caution.60 61 52 If one has a login account on mhpcc.pan-starrs.org, direct CVS access is 62 53 possible. Example of the commands required for direct CVS retrieval are … … 67 58 where: 68 59 - USERNAME is your login name on the server 69 - RELEASEBRANCH is the desired release branch, e.g. rel 5.60 - RELEASEBRANCH is the desired release branch, e.g. rel7. 70 61 71 62 … … 85 76 <i>Unless otherwise specified, the library is installed with PREFIX of the current directory.</i> 86 77 78 If the code was retrieved from CVS, you will need to substitute 'autogen.sh' for 'configure' in 79 above example. 80 87 81 Other configuration options, such as location of external libraries, are also available. 88 82 To get a list of options, type the following in the top psModule directory. … … 91 85 </pre> 92 86 A likely option needed is '--with-pslib-config', which specifies the location of 93 the configuration script for psLib. By default, iconfigure searches for it using PATH, but that 94 is often not sufficient. 87 the configuration script for psLib. By default, configure searches for it using PATH, but that 88 is not always sufficient. 89 90 @section install How to Install 91 92 To install the library using the prefix given in the configure step, execute in 93 the top build directory: 94 <pre> 95 $ make install 96 </pre> 97 98 99 @section usage Building and Linking your code to the psModule library 100 101 To assist the use of the library with your own code, a configuration tool is part 102 of the psModule library package. This tool, psmodule-config, is installed in the BIN 103 directory, according to the options given to the configure script. 104 105 The required CFLAG options for the compiler stage of code that uses psModule can be 106 obtained via 'psmodule-config --cflags'. This outputs the cc options that supplies 107 include path(s) required to find the psModule headers. 108 109 The required linking options, can be obtained via 'psmodule-config --libs'. This 110 outputs the ld options that supplies the library paths and files required to 111 link to the psModule library. 112 113 Note: psmodule-config usage above refers to the install locations of the library. 95 114 96 115 @section doc How to Create Code Documentation
Note:
See TracChangeset
for help on using the changeset viewer.
