Nuclear Template Normalization All of the templates are normalized to 1 and are in in units of 1 photon/keV as the flux in each band is divided by the width in keV For a template flux of 1 photon/cm2 at the earth the number of particles at the Sun is Narrow Line Template: 8.59464e+29 protons gt 30 MeV with a spectral index of 4 and and an alpha/proton ratio of 0.22 Broad Line Template: 6.57083e+030 ... Narrow + Broad Temp: 7.60049e+029 ... For the Pion spectra, normalized to unity above 200 keV the number of protons at the Sun with the corresponding power-law index above 30 MeV: 3.0 1.880e+30 3.5 9.956e+30 4.0 4.897e+31 4.5 2.300e+32 5.0 1.044e+33 Email exchange between Richard Schwartz and Ron Murphy Richard- I multiplied when I should have divided. When the narrow and broad components are combined according to the expected ratio, a unit fluence at Earth would correspond to 7.60e+29 protons >30 MeV; I.e., fewer protons would be required when both components are included in the fit, not more. Ron From: , Ron Date: Friday, August 29, 2014 at 1:27 PM To: "richard.a.schwartz@nasa.gov" Subject: Re: Fitting templates Richard- Deexcitation Lines: When the narrow and broad spectra were originally calculated, they were normalized for 1 accelerated proton >30 MeV. But at the request of the users (i.e., Gerry), they were both renormalized to unit yield. The renormalized narrow spectrum then corresponds to 305.6 protons >30 MeV or, for a unit fluence at Earth, 8.59464e+29 protons >30 MeV. For the assumed accelerated-ion spectral index (s=4) and alpha/proton ratio (0.22) and ambient and accelerated abundances (coronal-coronal), the ratio of the broad component yield to that of the narrow component is expected to be 0.1308. When the narrow and broad components are combined according to the above ratio, a unit fluence at Earth of the combination corresponds to 1.0023e+30 protons >30 MeV. Pion-decay spectra: At the request of that same user, the pion-decay spectra were renormalized to 1 photon >200 keV. A unit fluence >200 keV at Earth then corresponds to the following number of protons >30 MeV for several ion spectral indexes. Since the ion spectrum is assumed unbroken above 1 MeV with the given index, numbers of protons greater than any other energy can be easily calculated. 3.0 1.880e+30 3.5 9.956e+30 4.0 4.897e+31 4.5 2.300e+32 5.0 1.044e+33 Ron From: Richard Schwartz Reply-To: "richard.a.schwartz@nasa.gov" Date: Thursday, August 28, 2014 at 4:01 PM To: "Murphy, Ron" Subject: Re: Fitting templates Here are the .sav files -rwxrwxr-x 1 400 ssw_gen 18944 May 25 1995 /solarsoft/packages/xray/dbase/tungsten_xcom.sav -rwxrwxr-x 1 400 ssw_gen 21880 Sep 11 1996 /solarsoft/packages/xray/dbase/nuclear_template.sav -rwxrwxr-x 1 ktolbert2 oldstaff 22612 Oct 12 2007 /solarsoft/packages/xray/dbase/vern_50e3.sav -rwxrwxr-x 1 ktolbert2 oldstaff 22776 Oct 12 2007 /solarsoft/packages/xray/dbase/nuclear_template1.sav -rwxrwxr-x 1 ktolbert2 oldstaff 22628 Oct 12 2007 /solarsoft/packages/xray/dbase/alpha_dniso_35_60.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22628 Aug 15 2012 /solarsoft/packages/xray/dbase/pi_ap01_s50_b300_nh1e15.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22628 Aug 15 2012 /solarsoft/packages/xray/dbase/pi_ap01_s45_b300_nh1e15.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22628 Aug 15 2012 /solarsoft/packages/xray/dbase/pi_ap01_s40_b300_nh1e15.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22628 Aug 15 2012 /solarsoft/packages/xray/dbase/pi_ap01_s35_b300_nh1e15.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22628 Aug 15 2012 /solarsoft/packages/xray/dbase/pi_ap01_s30_b300_nh1e15.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22628 Aug 15 2012 /solarsoft/packages/xray/dbase/nar_ap022_s400_theta60.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22628 Aug 15 2012 /solarsoft/packages/xray/dbase/brd_ap022_s400_theta60.sav -rw-rw-r-- 1 ktolbert2 ssw_gen 22664 Aug 15 2012 /solarsoft/packages/xray/dbase/brd+nar_ap022_s400_theta60.sav Here's what the user's can access on their side when they are using OSPEX template - Interpolates a template-defined function of energy into user's energy bins a[0] - Normalization in photon /cm2 /sec at Earth over the full energy range of the template Keyword options: brd_nuc, nar_nuc, brd+nar_nuc, pion_s30, pion_s35, pion_s40, pion_s45, pion_s50, nuc1, nuc2, vern, alpha, fline, bline, nline brd_nuc - includes the broad nuclear de-excitation lines produced by nuclei heavier than helium having a differential power-law index of 4.0. Does not include the 511 keV and 2.2 MeV lines. Assume downward isotropic distribution of accelerated particles, a coronal abundance of accelerated particles, coronal ambient abundance(He/H = 0.1), and a heliocentric angle of 60 degrees. nar_nuc - includes the narrow nuclear de-excitation lines produced by proton and alpha particles having a differential power-law index of 4.0. Does not include the 511 keV, 2.2 MeV lines, and the alpha-helium lines. Assume downward isotropic distribution of accelerated particles, a coronal abundance of accelerated particles with alpha/proton = 0.22, coronal ambient abundance (He/H = 0.1), and a heliocentric angle of 60 degrees. brd_nar_nuc - Combined spectrum of brd_nuc and nar_nuc using the broad to narrow ratio found in SMM flares pion_s30 - pion decay produced by accelerated protons with spectral index of 3.0. Assume isotropic distribution of accelerated particles, alpha/proton = .10, magnetic field of 300 gauss, and hydrogen density of 1.e15. pion_s35 - pion decay produced by accelerated protons with spectral index of 3.5. Assume isotropic distribution of accelerated particles, alpha/proton = .10, magnetic field of 300 gauss, and hydrogen density of 1.e15. pion_s40 - pion decay produced by accelerated protons with spectral index of 4.0. Assume isotropic distribution of accelerated particles, alpha/proton = .10, magnetic field of 300 gauss, and hydrogen density of 1.e15. pion_s45 - pion decay produced by accelerated protons with spectral index of 4.5. Assume isotropic distribution of accelerated particles, alpha/proton = .10, magnetic field of 300 gauss, and hydrogen density of 1.e15. pion_s50 - pion decay produced by accelerated protons with spectral index of 5.0. Assume isotropic distribution of accelerated particles, alpha/proton = .10, magnetic field of 300 gauss, and hydrogen density of 1.e15. nuc1 - includes the broad nuclear de-excitation lines produced by proton, alpha, and heavier nuclei, does not include the 511 keV and 2.2 MeV lines. Note: this is out-of-date. Use brd_nuc instead. nuc2 - includes the narrow nuclear de-excitation lines produced by proton, alpha, and heavier nuclei, does not include the 511 keV and 2.2 MeV lines. Note: this is out-of-date. Use nar_nuc instead. vern - includes the calculated shape of the 511 keV annihilation line and its positronium continuum produced in the conditions of a solar atmosphere calculated by Vernazza et al for a temperature of 5000 K. alpha - includes the line feature produced by alpha-alpha collisions for a downward isotropic distribution of accelerated particles with a power spectrum with index 3.5 for a flare at 60 heliocentric angle. Note that nuc1, nuc2, and vern contain this line so it is best not to use both of these specific templates at the same time On 8/28/2014 3:54 PM, Murphy, Ron wrote: > Richard- > > Can you give me a list of the template names (both nuclear lines and > pion-decay) that you want proton numbers for? The list you included in > your email canšt be complete, can it? > > Ron > > On Aug/28/14, 2:38 PM, "Richard Schwartz" > wrote: > >> Hi Ron >> >> I don't have the very basic information requested by Gerard for your >> templates >> All we have are relative fluxes, energy edges, and a few clues from the >> filename about the simulation. >> So I'm not asking much, just what Gerard requested for all the templates >> we have so someone can use them in a scientific way. >> Don't worry about formatting. If I have to I'll put it into a >> spreadsheet and place that in the ospex/dbase directory: >> >> [ ] brd+nar_ap022_s400_theta60.sav 15-Aug-2012 12:43 22K >> [ ] brd_ap022_s400_theta60.sav 15-Aug-2012 12:43 22K >> [ ] nar_ap022_s400_theta60.sav 15-Aug-2012 12:43 22K >> [ ] pi_ap01_s30_b300_nh1e15.sav 15-Aug-2012 12:43 22K >> [ ] pi_ap01_s35_b300_nh1e15.sav 15-Aug-2012 12:43 22K >> [ ] pi_ap01_s40_b300_nh1e15.sav 15-Aug-2012 12:43 22K >> [ ] pi_ap01_s45_b300_nh1e15.sav 15-Aug-2012 12:43 22K >> [ ] pi_ap01_s50_b300_nh1e15.sav 15-Aug-2012 12:43 22K >> >> >> Thanks >> Richard >> On 8/18/2011 10:35 AM, ronald murphy wrote: >>> OK. Give me some info on how to construct readme and I'll do it from >>> now on. >>> >>> Ron >>> >>> >>>> From: "Schwartz, Richard A. (GSFC-671.0)[CATHOLIC UNIV OF AMERICA]" >>>> >>>> Date: Thu, 18 Aug 2011 09:31:38 -0500 >>>> To: ronald murphy >>>> Cc: "gerald.share.ctr@nrl.navy.mil" >>>> Subject: RE: Fitting templates >>>> >>>> readme is a string. yes. It allows you to dump anything in without >>>> concern >>>> about how it will be parsed by code. >>>> It can also be a string array. Or you can call it a header. >>>> >>>> There are some in ssw/packages/xray/dbase >>>> However, most of them are sitting on either Gerry's or your >>>> computer(s). Some >>>> have been passed to me. I'll search out the ones that I have but you >>>> and >>>> Gerry will have to find most of them. I'll send you a more formal >>>> spec later >>>> today. We should make the readme more like a header, so it will be a >>>> string >>>> array wiith names, delimiters, and values. >>>> >>>> Thanks >>>> Richard >>>> >>>> ________________________________________ >>>> From: ronald murphy [murphy@ssd5.nrl.navy.mil] >>>> Sent: Thursday, August 18, 2011 10:18 AM >>>> To: Schwartz, Richard A. (GSFC-671.0)[CATHOLIC UNIV OF AMERICA] >>>> Subject: Re: Fitting templates >>>> >>>> Richard, I will happily remake any save files to your specs. And >>>> certainly >>>> all new files will be done so also. What is the variable "readme"? A >>>> String? >>>> >>>> Ron >>>> >>>> >>>>> From: "Schwartz, Richard A. (GSFC-671.0)[CATHOLIC UNIV OF AMERICA]" >>>>> >>>>> Date: Thu, 18 Aug 2011 09:09:54 -0500 >>>>> To: ronald murphy >>>>> Subject: RE: Fitting templates >>>>> >>>>> What about the other elements in my message? Readme, Units? >>>>> Units can be contained in the readme. >>>>> >>>>> Can you put those elements into the existing templates? Templates >>>>> should be >>>>> understandable outside the Richard, Gerry, and Ron circle. The code >>>>> will >>>>> still >>>>> work on old templates but anything that is in SSW needs to be >>>>> upgraded. >>>>> >>>>> Thanks >>>>> Richard >>>>> ________________________________________ >>>>> From: ronald murphy [murphy@ssd5.nrl.navy.mil] >>>>> Sent: Thursday, August 18, 2011 9:41 AM >>>>> To: Schwartz, Richard A. (GSFC-671.0)[CATHOLIC UNIV OF AMERICA] >>>>> Subject: Re: Fitting templates >>>>> >>>>> Richard- >>>>> >>>>> I always thought that at least wnucl should be in the save file. Let >>>>> me know >>>>> what I can do. >>>>> >>>>> Ron >>>>> >>>>> >>>>>> From: "Schwartz, Richard A. (GSFC-671.0)[CATHOLIC UNIV OF AMERICA]" >>>>>> >>>>>> Date: Thu, 18 Aug 2011 08:39:27 -0500 >>>>>> To: ronald murphy >>>>>> Cc: "gerald.share.ctr@nrl.navy.mil" >>>>>> Subject: RE: Fitting templates >>>>>> >>>>>> Hi Ron >>>>>> >>>>>> After going through the old code with Gerry and then looking at the >>>>>> new code >>>>>> I >>>>>> began to remember the issues. We went through this when I changed >>>>>> f_template >>>>>> last November. We fixed everything at that time. I had trouble >>>>>> explaining >>>>>> why the value of the template factor changed by so little and why it >>>>>> was in >>>>>> a >>>>>> direction Gerry didn't understand. The real issue is whether it is >>>>>> correct >>>>>> at this time. I'll be going through the new version today to >>>>>> validate that. >>>>>> The normalization difference for the template in question was >>>>>> probably >>>>>> driven >>>>>> at the low end and not the high end which would explain our confusion >>>>>> yesterday. What is really needed for the templates is something >>>>>> more than >>>>>> just enucl and fnucl. These need to be understandable by anyone who >>>>>> restores >>>>>> them and not by having to parse through f_template. If we are to >>>>>> use save >>>>>> files as opposed to fits files that have lovely headers with >>>>>> keywords (my >>>>>> preference) then we need for each template sav file >>>>>> >>>>>> enucl : energy centers in keV >>>>>> fnucl : flux in units of photons / cm2 for the Sun observed at the >>>>>> Earth >>>>>> wnucl: bin widths in keV >>>>>> units_enucl: 'keV' for example >>>>>> units_fnucl: as above >>>>>> readme: all of the above and a description of the model. Plus the >>>>>> provenance: >>>>>> who, what, where, how, when >>>>>> This should be done for all existing template .sav files and for any >>>>>> new >>>>>> ones. >>>>>> >>>>>> The main point is that I changed a lot in the new f_template and it >>>>>> wasn't >>>>>> just the integration limits on the total flux. This is the crux of >>>>>> why >>>>>> Gerry's mental scaling between A then and A now is insufficient. >>>>>> >>>>>> Thanks >>>>>> Richard >>>>>> ________________________________________ >>>>>> From: ronald murphy [murphy@ssd5.nrl.navy.mil] >>>>>> Sent: Thursday, August 18, 2011 9:22 AM >>>>>> To: Schwartz, Richard A. (GSFC-671.0)[CATHOLIC UNIV OF AMERICA] >>>>>> Subject: Fitting templates >>>>>> >>>>>> Richard- >>>>>> >>>>>> Gerry tells me there is some issue with the pion-template energy >>>>>> bins not >>>>>> being uniform. They most definitely are not! But neither are the >>>>>> bins of the >>>>>> original nuclear-line templates. If there is anything I can do to >>>>>> help here, >>>>>> please let me know. >>>>>> >>>>>> Ron >>>>>>