tag:blogger.com,1999:blog-96285022009-07-14T00:36:11.978-05:00XSPECtorKeith's blog on XSPEC, related software and anything else I need to rememberKeith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.comBlogger453125tag:blogger.com,1999:blog-9628502.post-78306262230427633492009-06-12T12:53:00.001-05:002009-06-12T12:55:27.532-05:00XSPEC bug fixes update<table align="center" border="0" cellpadding="0" cellspacing="0" width="680"><tbody><tr align="left" valign="top"><td width="90"><span style="color: red;"><b>12.5.0af</b></span></td> <td>The <b>zredden</b> multiplicative model component is calling the same function as <b>redden</b>, and therefore its <b>redshift</b> parameter has no effect. Our thanks to Brian Refsdal for pointing this out. Report added on May 05, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0ag</b></td> <td>When in <b>setplot wave</b> mode and the user's Xspec.init file entry for WAVE_PLOT_UNITS is set to <b>angstrom</b>, <b>plot efficiency</b> and <b>plot icounts</b> don't display due to a missing plot label error. Our thanks to Maurice Leutenegger for pointing this out. Report added on May 08, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0ah</b></td> <td>Fix to sqrt(2) error in the definition of the thermal broadening used in APEC models. Our thanks to Irina Zhuravleva for pointing this out. Report added on May 21, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><span style="color: red;"><b>12.5.0ai</b></span></td> <td>This adds a new C-callable function to provide access to the <b>version string</b> for users linking the XSPEC models library into their own programs. The function is declared in src/XSUtil/FunctionUtils/xsFortran.h, and has the prototype:<br /><br /> int xs_getVersion(char* buffer, int buffSize);<br /><br /> Report added on May 22, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><span style="color: red;"><b>12.5.0aj</b></span></td> <td>The <b>model</b> command fails to parse expressions that are explicitly of the form: M(M1(A1)+M2(A2)+M3(A3)). Our thanks to Jeremy Sanders for pointing this out. Report added on May 22, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0ak</b></td> <td>When <b>soft limits</b> are in use during fitting, the <b>pegged parameter</b> test should be comparing the actual value against the hard limits, not the adjusted value. Otherwise the parameter may in some cases peg too soon. Report added on June 08, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0al</b></td> <td>The same sqrt(2) fix mentioned in patch 12.5.0ah is needed when thermal broadening is turned on for v2.0 NEI models. Our thanks to Richard Sturm for pointing this out. Report added on June 08, 2009. <br /><a href="http://heasarc.gsfc.nasa.gov/docs/xanadu/xspec/issues/pfiles/neispec.f"></a> </td></tr></tbody></table><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-7830626223042763349?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-26596774524352372892009-06-12T12:43:00.002-05:002009-06-12T12:49:00.783-05:00xselect cleansisFixed a bug spotted by Ed Cackett that the iterate_clean parameter is not recognized. Just needed to add it to the xselect.key file.<br /><br />Note that there are issues turning up using the probabilistic sisclean tool for bright Suzaku sources. There is a tendency for the core of the PSF to be removed. Suggested fixes are either to change the critical probability or turn the iteration off.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-2659677452435237289?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-92122080373761385672009-05-26T17:31:00.001-05:002009-05-26T17:33:21.788-05:00self-irradiated funnelPavel Abolmasov sent in his self-irradiated funnel model (<a href="http://adsabs.harvard.edu/abs/2009PASJ...61..213A">Abolmasov et al. 2009</a>) and I added an entry to the <a href="http://heasarc.gsfc.nasa.gov/docs/xanadu/xspec/newmodels.html">new models web page</a>.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-9212208037376138567?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-24431049441673870062009-05-26T14:11:00.001-05:002009-05-26T14:12:41.838-05:00addascaspecThe perl script addascapec, which is actually useful for other missions in addition to ASCA, had a couple of problems which I've fixed. The default errmeth should have been POISS-0 instead of POISS-1 and this parameter was not being used when summing background spectra.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-2443104944167387006?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-26818500790126643622009-05-23T21:16:00.000-05:002009-05-23T21:17:48.998-05:00Lexicon of handy statistical methodsAndrew Gelman's <a href="http://www.stat.columbia.edu/%7Ecook/movabletype/archives/2009/05/handy_statistic.html">statistical lexicon</a>.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-2681850079012664362?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-51409034560590668922009-05-15T15:11:00.003-05:002009-06-08T12:42:21.875-05:00bug in thermal broadeningIrina Zhuravleva at MPE pointed out that the thermal broadening option in the xspec apec model gives a sigma which is a factor of sqrt(2) too large. Fortunately, I don't think has any science implications since there have been no observations capable of measuring this broadening.<br /><br />update on 6/8/09: Richard Sturm points out there is the same error in the NEI code.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-5140903456059066892?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-44253325987253335982009-05-11T14:24:00.002-05:002009-05-11T14:27:50.738-05:00panda/epanda/bpanda regionsI've added support to cfitsio region filtering for the panda/epanda/bpanda regions produced by ds9. Note that this assumes only one azimuthal region and one annulus although the region specification itself allows multiple for both. Made corresponding changes in extractor though note that the FITS region extension written in this case is not covered by the standard which does not include these shapes.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-4425332598725333598?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-79985388930721804142009-05-07T09:11:00.002-05:002009-05-07T09:16:05.509-05:00Spectral file format standard documentI updated the <a href="http://heasarc.gsfc.nasa.gov/docs/heasarc/ofwg/docs/spectra/ogip_92_007/ogip_92_007.html">PHA file standard document</a> to try to make it clearer. I fixed an error in the type II example which had HDUCLAS3 and HDUCLAS4 inverted.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-7998538893072180414?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-89288754744572557812009-04-14T10:08:00.002-05:002009-04-14T10:10:15.761-05:00XSPEC bug fixes updateHere are the bug fixes from the last month. They can be found in the <a href="http://heasarc.gsfc.nasa.gov/docs/xanadu/xspec/bugs.html">usual place</a>.<br /><br /><table align="center" border="0" cellpadding="0" cellspacing="0" width="680"><tbody><tr align="left" valign="top"><td width="90"><b>12.5.0w</b></td> <td>A <b>new tclout option</b> has been added to make it easier to retrieve the fit parameters' <b>sigma</b> values. The syntax for this option is:<br /><br /> tclout sigma [<>:]n<br /><br /> where n is the parameter number. If it is not a variable parameter or if the fit was unable to calculate its sigma, a value of -1.0 is returned. Report added on Mar 06, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0x</b></td> <td>The model.dat entry for the <b>vequil</b> model is missing the parameter for Ar abundance, causing the vequil parameters which follow it to be misinterpreted in the code. (This bug does not affect the <b>equil</b> model.) Report added on Mar 06, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0y</b></td> <td>The <b>kerrconv</b> convolution model code is still using the xspec11-only LMODDIR environment variable for locating the <b>kerrtable.dat</b> model data file. This should be modified for usage in xspec12, where LMODDIR doesn't exist. Report added on Mar 11, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0z</b></td> <td>This removes an ambiguous reference build error specific to <b>gcc-4.1.1</b> on the <b>Solaris-2.9 platform</b>. Our thanks to Dacheng Lin for pointing this out. Report added on Mar 26, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0aa</b></td> <td>The <b>diskir</b> model goes to infinity when its <b>rirr</b> parameter = 1.0, which is also the default value of rirr's lower limit. Our thanks to Brian Refsdal for pointing this out. Report added on Mar 26, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0ab</b></td> <td>The <b>nsmax</b> model function is only able to find its auxiliary files when it is run directly from XSPEC's model data directory (heasoft-6.x/spectral/modelData). Our thanks to Stephen Doe for pointing this out. Report added on Mar 31, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><span style="color: red;"><b>12.5.0ac</b></span></td> <td>Fixes to a couple of obscure cases of <b>gain parameter</b> usage: If a gain parameter belongs to a response temporarily replaced by a <b>dummy response</b>, or a gain parameter is indirectly removed through the <b>data</b> command erasing its associated spectrum and response, the gain shift may still be applied to a response occupying its former spectrum and source number. This patch also improves the <b>show response</b> output. Report added on Apr 06, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0ad</b></td> <td>The <b>nthcomp</b> model has an uninitialized variable for the case of input energies less than kT_bb/10^4, which may cause a crash to occur. Our thanks to Gulab Dewangan for pointing this out. Report added on Apr 14, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0ae</b></td> <td>For those linking the models library into their own programs, the <b>swind1</b> model crashes when outputing a warning message as it indirectly accesses a variable intended for use only in XSPEC. Our thanks to Stephen Doe for pointing this out. Report added on Apr 14, 2009. </td></tr></tbody></table><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-8928875474457255781?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-63005892892832421132009-04-03T16:00:00.003-05:002009-04-03T16:23:14.228-05:00Notes on using SWIG to import C++ in PythonAs a test case using my heasp library which is being converted from C to C++. Created heasp.i file to define interface. Basically a concatenation of the heasp.h, PHA.h and PHAII.h files with the following at the top. Adding additional classes will just require cat'ing their *.h file to the end and adding the appropriate #include at the top. Note the %include of "std_string.i" which is required to make the string arguments work. Similar %include specifications will be required if other STL classes are arguments for methods.<br /><br />%module heasp<br /><br />%include "std_string.i"<br /><br />%{<br />#include <fstream><br />#include <iostream><br />#include <iomanip><br />#include <cstdlib><br />#include <cmath><br />#include <cstdio><br />#include <sstream><br />#include <string><br />#include <stdexcept><br />#include <ctime><br />#include <valarray><br />#include <vector><br /><br />#include <ccfits/ccfits><br /><br />#include "heasp.h"<br />#include "PHA.h"<br />#include "PHAII.h"<br />%}<br /><br />The interface file is then converted to C++ using<br /><br />swig -python -c++ -classic heasp.i<br /><br />which creates heasp_wrap.cxx and heasp.py. These must then be combined with the *.o files to build a shareable library called _heasp.so (note that the _ prefix and .so suffix are required). Compiling heasp_wrap.cxx will require include files from python. On my mac the relevant flag is<br />-I/Library/Frameworks/Python.framework/Versions/Current/include/python2.5<br />and on the lab Linux network<br />-I/usr1/local/include/python2.5<br /><br />On the mac the command to make the shareable library is<br />ld -bundle -flat_namespace -undefined suppress -o _heasp.so ${OFILES} heasp_wrap.o -L${HEADAS}/lib -lCCfits_2.1 -lcfitsio_3.12<br />and on Linux<br />$(CXX) -shared -o _heasp.so ${OFILES} heasp_wrap.o -L${HEADAS}/lib -lCCfits_2.1 -lcfi<br />tsio_3.13<br /><br />The module is loaded into python by<br />>>> import heasp<br />On the mac this generates an undefined symbol ___eprintf. This may require an update of Xcode to fix. On linux (running python2.5) there are no problems. Example use is<br /><br />>>> import heasp<br />>>> spectrum = heasp.PHA()<br />>>> spectrum.read('file1.pha',1,1)<br />>>> spectrum.disp()<br />>>> spectrum.write('test.pha')<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-6300589289283242113?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-85990937294162018972009-04-02T12:08:00.003-05:002009-04-02T12:09:05.217-05:00chkarfUpdated and much simplified chkarf so it actually lists the correct keywords as mandatory. This tool really should just be a perl script - the current program is overkill.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-8599093729416201897?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-16672312021010293852009-04-01T15:31:00.004-05:002009-04-02T08:32:40.532-05:00using openMP in gccI'm testing out parallelization using openMP on an 8-core Linux box. To build xspec to support openMP options requires the hmakerc to be edited to add -fopenmp to CFLAGS, FFLAGS, and CXXFLAGS and -lgomp to be added to F77LIBS4C (I added it immediately before -lgfortran).<br /><br />First test is in sumape.f to parallelize over the individual elements when interpolating the continuum and pseudo-continuum...<br /><br />C$OMP PARALLEL PRIVATE(ien,limdown,limup,ihigh,energy)<br /><br />C$OMP DO SCHEDULE(DYNAMIC)<br /><br /> DO ielt = 1, nmelt<br /><br />...<br /><br /><br /> ENDDO<br /><br />C$OMP END DO<br /><br />C$OMP END PARALLEL<br /><br />The variables defined as private are to avoid threads overwriting variables being set and used by other threads.<br /><br />Timing tests show that parallelization doesn't win enough in this case. Including the parallel directives slows a newpar down from 0.02 seconds to 0.4 seconds due to the overhead.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-1667231202101029385?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com3tag:blogger.com,1999:blog-9628502.post-63658868207609134072009-03-28T06:34:00.003-05:002009-03-28T06:39:22.782-05:00Computing with GPUsThere is <a href="http://www.gpgpu.org/">web site</a> all about using GPUs for general purpose computing. One particularly useful looking <a href="http://www.clustermonkey.net/content/view/248/33/1/0/">article</a> goes into some of the options and issues of coding for GPUs.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-6365886820760913407?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-17577031460167334032009-03-13T12:31:00.003-05:002009-03-13T12:36:14.893-05:00problem with extractor5.09In the course of Suzaku pipeline testing Lorella spotted a problem I introduced during the attempted speed-up of the fixwmp routine. Pixels with non-zero counts show up even within the part of the region which is supposed to be set to -1.<br /><br />The particular case of Suzaku demonstrated a conceptual issue here. Those pixels showing up within the supposed excluded region are real events. What is happening is that the region is defined in sky coordinates but the WMAP is written in detector coordinates. I calculate a conversion to determine which WMAP pixels are within the image region however it is a time-averaged solution. In the pre-5.09 version the satellite attitude wobble results in some events being incorrectly excluded from the WMAP. It was these events that the 5.09 version actually included however they are potentially confusing to users.<br /><br />The fix is checked in as v5.10.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-1757703146016733403?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-40901369849260479182009-03-02T16:25:00.002-05:002009-03-02T16:28:21.001-05:00xselect and Chandra grating dataJane Turner reported that the current version of xselect fails to read Chandra HETG evt2 data. This is due to a bug in xsel_mdb.f which I think only matters for Chandra grating files.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-4090136984926047918?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-51861427922953713502009-02-25T14:02:00.002-05:002009-02-25T14:06:44.856-05:00XSPEC units for setplot waveIn v12.5 we switched the y-axis units under setplot wave to per Hz instead of per Angstrom. Since this has not been universally popular we have added an initialization option to decide between the two cases. This is available as patch 12.5.0t. That and other recent patches can be obtained from the <a href="http://heasarc.gsfc.nasa.gov/docs/xanadu/xspec/bugs.html">usual place</a> and are summarized below<br /><br /><table align="center" border="0" cellpadding="0" cellspacing="0" width="680"><tbody><tr align="left" valign="top"><td width="90"><b>12.5.0r</b></td> <td>Fix needed for all <b>etable</b> model calculations. Our thanks to Roderick Johnstone for pointing this out. Report added on Feb 12, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0s</b></td> <td>When the both the <b>absori</b> and <b>pexriv</b> models are loaded during the same XSPEC session, whichever model is loaded second will not work properly. Note: this bug originated in version 12.5.0. Report added on Feb 13, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><span style="color: red;"><b>12.5.0t</b></span></td> <td>This adds an option for choosing <b>Y-axis units</b> when plotting in <b>setplot wave</b> mode. The selection is made by the WAVE_PLOT_UNITS entry, which has been added to the <b>new version of the Xspec.init file.</b> The units may now be specified in <b>Hz</b> (the default for version 12.5.0), or <b>angstroms</b> as they were prior to 12.5.0. This applies to plots of data, counts, and all variants of model and ufspec plots. Report added on Feb 19, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><span style="color: red;"><b>12.5.0u</b></span></td> <td>Minor code changes mostly to clean up the messages reported when running XSPEC under the valgrind software tool. Report added on Feb 19, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><span style="color: red;"><b>12.5.0v</b></span></td> <td><b>Multiplicative</b> model components which are created with the <b>mdefine</b> command should not be multiplied by the energy bin widths. Our thanks to Roderick Johnstone for pointing this out. Report added on Feb 19, 2009. </td></tr></tbody></table><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-5186142792295371350?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-13957822972964760482009-02-25T14:00:00.003-05:002009-05-07T09:11:35.259-05:00non-integer COUNTS columnSteve Snowden ran into a silent problem because he made spectrum files with non-integer COUNTS columns. This is in violation of the standard and many ftools will simply silently truncate the float value to the nearest integer. I've added checks in the low-level library routines to write warnings in this case.<br /><br />Update on 5/7/09. It turns out that the RXTE s/w writes PHA files with a real COUNTS column although the values are integers. So, I've improved the checking so that no warnings are given if the values are integers even if the column is defined as real. If the values really are non-integer then a warning is written and the values truncated to integers.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-1395782297296476048?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-31592620755026639492009-02-14T21:50:00.002-05:002009-02-14T21:53:53.168-05:00Gelman on statisticsI'm going to start linking to interesting blog posts by Andrew Gelman because they often have important points to remember. Today he <a href="http://www.stat.columbia.edu/%7Ecook/movabletype/archives/2009/02/dennis-lindleys.html">talks</a> about a couple of reviews of "The Black Swan" and includes the following note on Bayesian inference :<br /><br /><blockquote>From a philosophical point of view, I think the most important point of confusion about Bayesian inference is the idea that it's about computing the probability that a model is true. In all the areas I've ever worked on, the model is never true. But what you <em>can</em> do is find out that certain important aspects of the data are highly unlikely to be captured by the fitted model, which can facilitate a "model shift" moment. This sort of falsification is why I believe Popper's philosophy of science to be a good fit to Bayesian data analysis.</blockquote><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-3159262075502663949?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-20942583391524772072009-02-11T16:08:00.001-05:002009-02-11T16:12:05.960-05:00Recent XSPEC bug fixesThe following are all available from the <a href="http://heasarc.gsfc.nasa.gov/docs/xanadu/xspec/bugs.html">usual place.</a><br /><table align="center" border="0" cellpadding="0" cellspacing="0" width="680"><tbody><tr align="left" valign="top"><td width="90"><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0l</b></td> <td>This slightly modifies the state of <b>newly untied parameters</b>. When a parameter is untied, its <b>frozen/unfrozen</b> setting should retain the setting of the parameter(s) to which it was linked, rather than be restored to its original value. Our thanks to Phil Evans and Delphine Porquet for pointing this out. Report added on Jan 14, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0m</b></td> <td>When <b>steppar</b> is executed, it should not automatically run a fit at the end to place the parameters in their best-fit state. Instead it should restore the parameters to their pre-steppar values, regardless of the fit state. Our thanks to Tim Kallman for pointing this out. Report added on Jan 14, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0n</b></td> <td>Bug fix for a C-to-Fortran boolean conversion error, affecting the default setting for the <b>thermal broadening</b> flag of the <b>bapec and bvapec </b>models. Unless overridden by the APECTHERMAL setting, thermal broadening should be ON by default for <b>bapec and bvapec</b>. This bug has only been observed on <b>Solaris</b> platforms. Report added on Jan 15, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0o</b></td> <td>When a <b>delcomp</b> operation is performed on the unnamed (default) model and <b>no spectra are loaded</b>, the model calculation is not updated. Our thanks to Laura Brenneman for pointing this out. Report added on Jan 21, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0p</b></td> <td>This relaxes the OGIP requirement that spectral data files must contain a <b>RESPFILE</b> keyword, primarily to allow the loading of certain RXTE/PCA files. Our thanks to David Smith for pointing this out. Report added on Jan 30, 2009. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0q</b></td> <td>A new option has been added to the <b>tclout</b> command: <b>tclout gain</b>. See the online <a href="http://heasarc.gsfc.nasa.gov/docs/xanadu/xspec/manual/XStclout.html">tclout manual</a> entry for proper syntax and usage. Prior to this, it was not possible to retrieve the values of gain parameters from tclout. Our thanks to Frank Haberl for pointing this out. Report added on Feb 03, 2009. </td></tr></tbody></table><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-2094258339152477207?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-33453954915885937082009-01-22T18:48:00.002-05:002009-01-22T18:50:09.533-05:00xselect and region filtersI've added clarification to the on-line help for xselect about region filters. It is dangerous to make region filters in Image coordinates - the correct options are WCS or Physical. If the xselect image binning is not 1 then regions in Image coordinates will not be handled correctly.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-3345395491588593708?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-84763663201214955652009-01-22T18:23:00.001-05:002009-01-22T18:24:39.010-05:00Chandra CY11 webspec updatedUpdated webspec with the final ARFs for Chandra Cycle 11.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-8476366320121495565?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-62134343518481075142009-01-16T15:50:00.000-05:002009-01-16T15:51:04.001-05:00Word-cloud of the 171 Astro2010 NOI titles<a href="http://www.wordle.net/gallery/wrdl/444994/Astro2010_NOI" title="Wordle: Astro2010 NOI"><img src="http://www.wordle.net/thumb/wrdl/444994/Astro2010_NOI" alt="Wordle: Astro2010 NOI" style="border: 1px solid rgb(221, 221, 221); padding: 4px;" /></a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-6213434351848107514?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-14537649421958076382009-01-13T10:20:00.000-05:002009-01-13T10:21:46.820-05:00recent xspec patches<table align="center" border="0" cellpadding="0" cellspacing="0" width="680"><tbody><tr align="left" valign="top"><td width="90"><b>12.5.0j</b></td> <td><b>Parameter links</b> both to and from a model which is <b>not associated with any spectra</b> (shown as "Active/Off" in the model display), should not be removed when the model's state gets updated (such as when using the <b>dummyrsp</b> command). Our thanks to Laura Brenneman for pointing this out. Report added on Dec 24, 2008. <br /><br /> </td> </tr> <tr align="left" valign="top"> <td width="90"><b>12.5.0k</b></td> <td>The <b>dummyrsp</b> command may cause a crash when entering a very large number of energy bins. Our thanks to Joel Frioriksson for pointing this out. Report added on Dec 31, 2008. <br /></td></tr></tbody></table><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-1453764942195807638?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-26765871455960397752008-12-16T18:02:00.003-05:002008-12-16T18:03:37.160-05:00webspec for ChandraI've updated webspec to use the Chandra CY11 rmfs and arfs released by the CUC. Note that in mid January they will be releasing new arfs with corrected contamination corrections and effective areas.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-2676587145596039775?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0tag:blogger.com,1999:blog-9628502.post-50581781037889628102008-12-16T11:58:00.000-05:002008-12-16T11:59:21.160-05:00xspec patch for energies extend<b>12.5.0i</b> The <b>energies extend</b> option does not work properly for the case of a data group containing multiple responses whose energy bins differ. Our thanks to Joel Frioriksson for pointing this out. Report added on Dec 15, 2008.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9628502-5058178103788962810?l=xspector.blogspot.com'/></div>Keith Arnaudhttp://www.blogger.com/profile/02055792987509582228noreply@blogger.com0