Then you have to follow these steps:
If not, put them there as individual files containing the wavelenght in \AA and the response. The first time you use a combination of filter and spectrum the program will calculate the AB observed fluxes as a function of redshift and keep them on the directory AB. This usually takes a while, but it is done only once (unless you change your templates and want to recalculate the AB fluxes, then use the NEW_AB option, see below)
You can generate the total filter throughputs and copy them to the subdirectory FILTER using the program gen_trans.py:
The photometry has to be in magnitudes or in "magnitude" fluxes,
i.e. f=10^(-.4m) There are a few conventions to follow:
The program will crash by design if you include negative magnitudes, fluxes or errors in the photometric catalog, except the -99.0 flag, so check it thoroughly before running it through bpz.py
An example can be found in hdfn_z.columns If the photometric catalog name is 'name.cat' the default name for this file will be 'name.columns'. This default can be changed using a command line option (see below)
The first lines of this associated file, or "filter" lines contain
the following columns:
After the 'filter' lines we can include the column number of several columns designating columns in the photometric catalog file, can be included. These columns will also be printed in the output file.
bpz.py my_data.cat [-P my_data.pars] [-PAR1 value -PAR2 value1,value2,value3 ...]
Command line options:
-P my_data.pars This option allows to update the parameter information using the
contents of a file. This file must have the following format:
PAR1 value # comment about parameter 1
PAR2 value1,value2,value3 # comment about parameter 2
Also any of the parameters in bpz.py can be modified in the command
Their default values (assuming that the photometric file is called my_data.cat)
are shown next to the parameter name
The file containing the descriptions of the columns in the input photometry file.
The file containing the photo-z.
The file containing the list of templates. The default is CWWSB.list (The four Coleman, Wu
and Weedman types, plus two Kinney et al. 1996 starbursts)
The default value is the prior derived from the HDFN and the CFRS (Benitez 2000)
Other possible value is 'flat' or 'none'. No prior is used in that case.
Resolution of the redshift grid. The intervals are logarithmic, (1+z)*dz
The data in the photometric catalogs are interpreted as magnitudes by default.
If not, they are treated as fluxes.
If 'yes', recalculates the AB files even if they are already present in the AB directory. It is useful
if the filter shape or spectral templates have been modified but their names are the same as before.
If its value were FILTER_NAME1,FILTER_NAME2 it would
exclude the data corresponding to those filters from the estimation.
This option estimates the average of the ratio between the observed fluxes and
the model fluxes corresponding to the best fit. It is aproximately 1. for the HDF-N spectroscopic
sample, which shows that the CWW+SB templates agree reasonably well with the HDFN
spectroscopic data. It may be useful to detect calibration errors either in the photometry or in the
template set. If spectroscopic redshifts are present in the input catalog, it also prints the comparison
between the observed colors and the expected ones from the templates.
-ZC 1.,2. -FC .2,.4 Adds gaussian 'spikes' to the prior
at the redshifts indicated in ZC. The parameter
FC represents the fraction of the total number of galaxies expected to be in each cluster
If set to 'no', stops bpz from printing to the screen the results of the photo-z estimation.
( it doesn't affect the output from CHECK and PROBS)
This introduces n points of interpolation between the templates in the color space. It is not optimized yet
and considerably slows down the program, but it seems to yield more precise results, specially at low redshift,
even with values as low as INTERP 2.
This number is used to define the redshift confidence limits and also the interval over which
we integrate to find the empirical odds (the interval is such that a gaussian probability distribution
will contain e.g. 95% of the probability)
If its value is different from 'no', it will writes the final bayesian probability and all the individual type
likelihoods to a file named as the parameter value. It may increment the running time by a factor 3 or
more, and generates a huge file, so use with caution. Lots of improvement to do here.
This saves the final redshift probability distribution for each galaxy, which contains all the information about
the photometric redshift.
If this option is 'no', bpz does not estimate new photometric redshifts. It performs the rest of its functions
like plotting, generating AB files, etc. but instead of estimating new photo-z, it reads them from
an already existing OUTPUT file.
If on, bpz will query the user about plot options, etc.
If on, it will produce some useful plots.