ChiantiPy.tools package¶
Submodules¶
ChiantiPy.tools.archival module¶
Functions for reading pre-v8 CHIANTI files
-
ChiantiPy.tools.archival.
elvlcRead
(ions, filename=0, verbose=0, useTh=0)¶ read a chianti energy level file and returns {“lvl”:lvl,”conf”:conf,”term”:term,”spin”:spin,”l”:l,”spd”:spd,”j”:j ,”mult”:mult,”ecm”:ecm,”eryd”:eryd,”ecmth”:ecmth,”erydth”:erydth,”ref”:ref,”pretty”:pretty, ‘ionS’:ions} if a energy value for ecm or eryd is zero(=unknown), the theoretical values (ecmth and erydth) are inserted
-
ChiantiPy.tools.archival.
elvlcWrite
(info, outfile=None, addLvl=0)¶ Write Chianti data to .elvlc file.
Parameters: - info (dict) – Information about the Chianti data to write. Should contain the following keys: ionS, the Chianti style name of the ion such as c_4 conf, an integer denoting the configuration - not too essential term, a string showing the configuration spin, an integer of the spin of the state in LS coupling l, an integer of the angular momentum quantum number spd, an string for the alphabetic symbol of the angular momemtum, S, P, D, etc j, a floating point number, the total angular momentum ecm, the observed energy in inverse cm, if unknown, the value is 0. eryd, the observed energy in Rydbergs, if unknown, the value is 0. ecmth, the calculated energy from the scattering calculation, in inverse cm erydth, the calculated energy from the scattering calculation in Rydbergs ref, the references in the literature to the data in the input info
- outfile (str) – Output filename. ionS+’.elvlc’ (in current directory) if None
- addLvl (int) – Add a constant value to the index of all levels
Notes
For use with files created before elvlc format change in November 2012
See also
ChiantiPy.tools.io.elvlcWrite()
- Write .elvlc file using the new format.
-
ChiantiPy.tools.archival.
wgfaRead
(ions, filename=None, elvlcname=-1, total=False, verbose=False)¶ Read CHIANTI data from a .wgfa file.
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str) – Custom filename, will override that specified by ions
- elvlcname (str) – If specified, the lsj term labels are returned in the pretty1 and pretty2 keys of Wgfa
- total (bool) – Return the level 2 avalue data in Wgfa
- verbose (bool)
Returns: Wgfa – Information read from the .wgfa file. The dictionary structure is {“lvl1”,”lvl2”,”wvl”,”gf”,”avalue”,”ref”,”ionS”,”filename”}
Return type: dict
Notes
This is text-wise not different than the v8 version except that it uses the archival elvlcRead in ~ChiantiPy.tools.archival though this has now been commented out. Can this routine be removed? Should the elvlcRead routine be uncommented?
See also
ChiantiPy.tools.io.wgfaRead()
- Read .wgfa file with the new format.
ChiantiPy.tools.constants module¶
A set of physical constants, in (mostly) cgs unit system. Most are from [11].
References
| [11] | NIST Reference on Constants, Units and Uncertainty (link) |
Notes
Many of these can be replaced by the ~astropy.constants module. Elemental symbols can be removed in favor of the periodictable module. Spectroscopic roman numerals can be removed in favor of roman module. The Gauss-Laguerre weights can be calculated by ~numpy.polynomial.laguerre.laggauss.
ChiantiPy.tools.data module¶
Module for collecting various top-level Chianti data
Descriptions for keywordArgs:
- temperature : temperature (in K)
- eDensity : electron density (in \(\mathrm{cm}^{-3}\))
- hDensity : hydrogen density (in \(\mathrm{cm}^{-3}\))
- pDensity : proton density (in \(\mathrm{cm}^{-3}\))
- radTemperature : radiation temperature of central source (in K)
- rStar : distance of the plasma from the source (in units of the source’s radius)
- distance : distance from the central source
| Parameters: |
|
|---|
ChiantiPy.tools.filters module¶
Line profile filters for creating synthetic spectra.
-
ChiantiPy.tools.filters.
boxcar
(wvl, wvl0, factor=None)¶ Box-car filter
Parameters: - wvl (~numpy.ndarray) – Wavelength array
- wvl0 (~numpy.float64) – Wavelength filter should be centered on.
- factor (~numpy.float64) – Full width of the box-car filter
-
ChiantiPy.tools.filters.
gaussian
(wvl, wvl0, factor=1.0)¶ A gaussian filter
Parameters: - wvl (~numpy.ndarray) – Wavelength array
- wvl0 (~numpy.float64) – Wavelength filter should be centered on.
- factor (~numpy.float64) – Gaussian width
- integrated value is unity
-
ChiantiPy.tools.filters.
gaussianR
(wvl, wvl0, factor=1000.0)¶ A gaussian filter where the gaussian width is given by wvl0/factor.
Parameters: - wvl (~numpy.ndarray) – Wavelength array
- wvl0 (~numpy.float64) – Wavelength filter should be centered on.
- factor (~numpy.float64) – Resolving power
-
ChiantiPy.tools.filters.
lorentz
(wvl, wvl0, factor=1.0)¶ Lorentz profile filter with the exception that all factors are in wavelength units rather than frequency as the lorentz profile is usually defined.
Parameters: - wvl (~numpy.ndarray) – Wavelength array
- wvl0 (~numpy.float64) – Wavelength filter should be centered on.
- factor (~numpy.float64) – Value of the so-called constant gamma
- integrated value is unity
- the FWHM is 2*gamma
- .. math:: – L = frac{1}{pi gamma} frac{ gamma^2}{(lambda - lambda_0)^2 + gamma^2}
-
ChiantiPy.tools.filters.
moffat
(wvl, wvl0, factor=2.5)¶ Moffat profile with parameters suited to Chandra Letg spectra
Parameters: - wvl (~numpy.ndarray) – Wavelength array
- wvl0 (~numpy.float64) – Wavelength the filter is centered on.
- factor (~numpy.float64) – Resolving power (TODO: correct description)
-
ChiantiPy.tools.filters.
voigt
(wvl, wvl0, factor=(0.5, 1.0))¶ pseudo-Voigt filter the sum of a Gaussian and a Lorentzian
Parameters: - wvl (~numpy.ndarray) – Wavelength array
- wvl0 (~numpy.float64) – Wavelength the filter is centered on.
- factor (array-type) – contains the following 2 parameters
- A (~numpy.float64) – relative size of gaussian and lorentz components must be between 0. and 1. but this is not currently checked
- sigma (~numpy.float64) – the gaussian width of the gaussian profile (the standard deviation) also creates the lorentz component with the same fwhm
ChiantiPy.tools.io module¶
Reading and writing functions
-
ChiantiPy.tools.io.
abundanceRead
(abundancename='')¶ Read abundance file abundancename and return the abundance values relative to hydrogen
-
ChiantiPy.tools.io.
autoRead
(ions, filename=None, total=True, verbose=False)¶ Read CHIANTI autoionization rates from a .auto file.
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str) – Custom filename, will override that specified by ions
- elvlcname (str) – If specified, the lsj term labels are returned in the ‘pretty1’ and ‘pretty2’ keys of ‘Wgfa’ dict
- total (bool) – Return the summed level 2 autoionization rates in ‘Auto’
- verbose (bool)
Returns: Auto – Information read from the .wgfa file. The dictionary structure is {“lvl1”, “lvl2”, “avalue”, “pretty1”, “pretty2”, “ref”,”ionS”, “filename”}
Return type: dict
-
ChiantiPy.tools.io.
autoWrite
(info, outfile=None, minBranch=None)¶ Write data to a CHIANTI .wgfa file
Parameters: - info (dict) – Should contain the following: ionS, the Chianti style name of the ion such as c_4 for C IV, lvl1, the lower level, the ground level is 1, lvl2, the upper level, wvl, the wavelength (in Angstroms), avalue, the autoionization rate, pretty1, descriptive text of the lower level (optional), pretty2, descriptive text of the upper level (optiona), ref, reference text, a list of strings
- outfile (str)
- minBranch (~numpy.float64) – The transition must have a branching ratio greater than the specified to be written to the file
-
ChiantiPy.tools.io.
cireclvlRead
(ions, filename=None, filetype='cilvl')¶ Read Chianti cilvl, reclvl, or rrlvl files and return data
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str, optional) – Custom filename, will override that specified by ions
- filetype (str) – {‘cilvl’, ‘reclvl’, ‘rrlvl’} Type of the file to read
-
ChiantiPy.tools.io.
convertName
(name)¶ Convert ion name string to Z and Ion and other interesting info
Parameters: name (str) – a generic name of an ion in the CHIANTI database, such as fe_14 for Fe XIV Notes
A duplicate of the routine in ChiantiPy.tools.util but needed by masterList Info TODO: Put in separate module to avoid multiple copies
-
ChiantiPy.tools.io.
defaultsRead
(verbose=False)¶ Read in configuration from .chiantirc file or set defaults if one is not found.
-
ChiantiPy.tools.io.
diRead
(ions, filename=None)¶ Read chianti direct ionization .params files and return data.
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str, optional) – Custom filename, will override that specified by ions
-
ChiantiPy.tools.io.
drRead
(ions, filename=None)¶ Read CHIANTI dielectronic recombination .drparams files if filename is set, then reads that file
-
ChiantiPy.tools.io.
eaRead
(ions, filename=None)¶ Read a CHIANTI excitation-autoionization file and calculate the EA ionization rate data derived from splupsRead.
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str, optional) – Custom filename, will override that specified by ions
-
ChiantiPy.tools.io.
elvlcRead
(ions, filename=None, getExtended=False, verbose=False, useTh=True)¶ Reads the new format elvlc files.
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str, optional) – Custom filename, will override that specified by ions
- getExtended (bool)
- verbose (bool)
- useTh (bool) – If True, the theoretical values (ecmth and erydth) are inserted when an energy value for ecm or eryd is zero(=unknown)
-
ChiantiPy.tools.io.
elvlcWrite
(info, outfile=None, round=0, addLvl=0, includeRyd=False, includeEv=False)¶ Write Chianti data to .elvlc file.
Parameters: - info (dict) – Information about the Chianti data to write. Should contain the following keys: ionS, the Chianti style name of the ion such as c_4 term, a string showing the configuration spin, an integer of the spin of the state in LS coupling l, an integer of the angular momentum quantum number spd, an string for the alphabetic symbol of the angular momemtum, S, P, D, etc j, a floating point number, the total angular momentum ecm, the observed energy in inverse cm, if unknown, the value is 0. eryd, the observed energy in Rydbergs, if unknown, the value is 0. ecmth, the calculated energy from the scattering calculation, in inverse cm erydth, the calculated energy from the scattering calculation in Rydbergs ref, the references in the literature to the data in the input info
- outfile (str) – Output filename. ionS + ‘.elvlc’ (in current directory) if None
- round (int) – input to ‘np.round’ to round input values to maintain the correct number of significant figures
- addLvl (int) – Add a constant value to the index of all levels
- includeRyd (bool) – If True, write the Rydberg energies in the extended area, delimited by a comma
- includeEv (bool) – If True, write the energies in eV in the extended area, delimited by a comma
Notes
For use with files created after elvlc format change in November 2012
See also
ChiantiPy.tools.archival.elvlcWrite()
- Write .elvlc file using the old format.
-
ChiantiPy.tools.io.
fblvlRead
(ions, filename=None, verbose=False)¶ Read a Chianti energy level file for calculating the free-bound continuum
-
ChiantiPy.tools.io.
gffRead
()¶ Read the free-free gaunt factors of [1].
References
[1] (1, 2) Sutherland, R. S., 1998, MNRAS, 300, 321 Notes
This function reads the file and reverses the values of g2 and u
-
ChiantiPy.tools.io.
grndLevelsRead
()¶ to read the grndLevels.dat file give the number of ground levels to sum over in populate and drPopulate
-
ChiantiPy.tools.io.
ioneqRead
(ioneqName='', minIoneq=1e-20, verbose=False)¶ Reads an ioneq file ionization equilibrium values less then minIoneq are returns as zeros :returns: {‘ioneqname’,’ioneqAll’,’ioneqTemperature’,’ioneqRef’} – Ionization equilibrium values and the reference to the literature :rtype: dict
-
ChiantiPy.tools.io.
ipRead
(verbose=False)¶ Reads the ionization potential file
Returns: ip – Ionization potential (in eV) Return type: array-like
-
ChiantiPy.tools.io.
itohRead
()¶ Read in the free-free gaunt factors of [2].
References
[2] Itoh, N. et al., 2000, ApJS, 128, 125
-
ChiantiPy.tools.io.
klgfbRead
()¶ Read CHIANTI files containing the free-bound gaunt factors for n=1-6 from [13].
Returns: {‘pe’, ‘klgfb’} – Photon energy and the free-bound gaunt factors Return type: dict References
[13] Karzas and Latter, 1961, ApJSS, 6, 167
-
ChiantiPy.tools.io.
masterListInfo
(force=False, verbose=False)¶ Get information about ions in the CHIANTI masterlist.
Returns: masterListInfo – {‘wmin’, ‘wmax’, ‘tmin’, ‘tmax’} Minimum and maximum wavelengths in the wgfa file. Minimum and maximum temperatures for which the ionization balance is nonzero. Return type: dict Notes
This function speeds up multi-ion spectral calculations. The information is stored in a pickled file ‘masterlist_ions.pkl’ If the file is not found, one will be created.
-
ChiantiPy.tools.io.
masterListRead
()¶ Read a CHIANTI masterlist file.
Returns: masterlist – All ions in Chianti database Return type: list
-
ChiantiPy.tools.io.
photoxRead
(ions)¶ Read CHIANTI photoionization .photox files
Returns: {‘lvl1’, ‘lvl2’, ‘energy’, ‘cross’, ‘ref’} – Energy (in Rydbergs) and cross section (in \(\mathrm{cm}^{-2}\)) Return type: dict Notes
The photox files are not in any released version of the CHIANTI database.
-
ChiantiPy.tools.io.
rrLossRead
()¶ to read the Mao 2017 rr loss parameters [12]
References
[12] Mao J., Kaastra J., Badnell N.R., 2017 Astron. Astrophys. 599, A10
-
ChiantiPy.tools.io.
rrRead
(ions, filename=None)¶ Read CHIANTI radiative recombination .rrparams files
Returns: {‘rrtype’,’params’,’ref’} Return type: dict
-
ChiantiPy.tools.io.
scupsRead
(ions, filename=None, verbose=False)¶ Read the new format v8 scups file containing the scaled temperature and upsilons from [8].
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str, optional) – Custom filename, will override that specified by ions
- verbose (bool)
-
ChiantiPy.tools.io.
splomRead
(ions, ea=False, filename=None)¶ Read chianti .splom files
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- ea (bool) – Read .easplom file
- filename (str, optional) – Custom filename, will override that specified by ions
Returns: {‘lvl1’, ‘lvl2’, ‘ttype’, ‘gf’, ‘deryd’, ‘c’, ‘splom’, ‘ref’}
Return type: dict
Notes
Still needed for ionization cross sections
-
ChiantiPy.tools.io.
splupsRead
(ions, filename=None, filetype='splups')¶ Read a CHIANTI .splups file
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str, optional) – Custom filename, will override that specified by ions
- filetype (str, optional) – {psplups,`cisplups`,`splups`} Type of file to read
Returns: {‘lvl1’, ‘lvl2’, ‘ttype’, ‘gf’, ‘de’, ‘cups’, ‘bsplups’, ‘ref’}
Return type: dict
-
ChiantiPy.tools.io.
trRead
(ionS)¶ read the files containing total recombination rates .trparams
-
ChiantiPy.tools.io.
twophotonHRead
()¶ Read the two-photon Einstein A values and distribution function for the H sequence.
Returns: {‘y0’, ‘z0’, ‘avalue’, ‘asum’, ‘psi0’} Return type: dict
-
ChiantiPy.tools.io.
twophotonHeRead
()¶ Read the two-photon Einstein A values and distribution function for the He sequence.
Returns: {‘y0’, ‘avalue’, ‘psi0’} Return type: dict
-
ChiantiPy.tools.io.
vernerRead
()¶ Reads the photoionization cross-section data from [6].
Returns: {‘pqn’,’l’,’eth’,’e0’,’sig0’,’ya’,’p’, yw’} – pqn is the principal quantum number, l is the subshell orbital quantum number, eth (in eV) is the subshell ionization threshold energy; sig0, ya, p, and yw are all fit parameters used in calculating the total photoionization cross-section. Return type: dict References
[6] Verner & Yakovlev, 1995, A&AS, 109, 125
-
ChiantiPy.tools.io.
versionRead
()¶ Read the version number of the CHIANTI database
-
ChiantiPy.tools.io.
wgfaRead
(ions, filename=None, elvlcname=0, total=False, verbose=False)¶ Read CHIANTI data from a .wgfa file.
Parameters: - ions (str) – Ion, e.g. ‘c_5’ for C V
- filename (str) – Custom filename, will override that specified by ions
- elvlcname (str) – If specified, the lsj term labels are returned in the ‘pretty1’ and ‘pretty2’ keys of ‘Wgfa’ dict
- total (bool) – Return the summed level 2 avalue data in ‘Wgfa’
- verbose (bool)
Returns: Wgfa – Information read from the .wgfa file. The dictionary structure is {“lvl1”,”lvl2”,”wvl”,”gf”,”avalue”,”ref”,”ionS”,”filename”}
Return type: dict
See also
ChiantiPy.tools.archival.wgfaRead()
- Read .wgfa file with the old format.
-
ChiantiPy.tools.io.
wgfaWrite
(info, outfile=None, minBranch=1e-05, rightDigits=4, maxLvl1=None)¶ Write data to a CHIANTI .wgfa file
Parameters: - info (dict) – Should contain the following keys: ionS, the Chianti style name of the ion such as c_4 for C IV, lvl1, the lower level, the ground level is 1, lvl2, the upper level, wvl, the wavelength (in Angstroms), gf,the weighted oscillator strength, avalue, the A value, pretty1, descriptive text of the lower level (optional), pretty2, descriptive text of the upper level (optiona), ref, reference text, a list of strings
- outfile (str)
- minBranch (~numpy.float64) – The transition must have a branching ratio greater than the specified minBranchto be written to the file
-
ChiantiPy.tools.io.
zion2name
(z, ion, dielectronic=False)¶ Convert Z and ion to generic name, e.g. 26, 13 -> fe_13
Parameters: - z (int) – the nuclear charge, for example 26 for Fe XIV
- ion (int) – the ion stage, for example, 14 for Fe XIV
Notes
A duplicate of the routine in ChiantiPy.tools.util but needed by masterList Info TODO: Put in separate module to avoid multiple copies
ChiantiPy.tools.mputil module¶
Functions needed for standard Python multiprocessing module mspectrum
-
ChiantiPy.tools.mputil.
doFbQ
(inQ, outQ)¶ Multiprocessing helper for ChiantiPy.core.continuum.freeBound
Parameters: - inQ (~multiprocessing.Queue) – Ion free-bound emission jobs queued up by multiprocessing module
- outQ (~multiprocessing.Queue) – Finished free-bound emission jobs
-
ChiantiPy.tools.mputil.
doFfQ
(inQ, outQ)¶ Multiprocessing helper for ChiantiPy.core.continuum.freeFree
Parameters: - inQ (~multiprocessing.Queue) – Ion free-free emission jobs queued up by multiprocessing module
- outQ (~multiprocessing.Queue) – Finished free-free emission jobs
-
ChiantiPy.tools.mputil.
doIonQ
(inQueue, outQueue)¶ Multiprocessing helper for ChiantiPy.core.ion and ChiantiPy.core.ion.twoPhoton
Parameters: - inQueue (~multiprocessing.Queue) – Jobs queued up by multiprocessing module
- outQueue (~multiprocessing.Queue) – Finished jobs
ChiantiPy.tools.sources module¶
Blackbody temperature calculations
-
class
ChiantiPy.tools.sources.
blackStar
(temperature, radius)¶ Bases:
object
Calculate blackbody radiation
Parameters: - temperature (~numpy.ndarray) – Temperature in Kelvin
- radius (~numpy.ndarray) – Stellar radius in cm
Variables: - Temperature (~numpy.ndarray) – Temperature in Kelvin
- Radius (~numpy.ndarray) – Stellar radius in cm
- Incident (~numpy.ndarray) – Blackbody photon distribution
-
incident
(distance, energy)¶ Calculate photon distribution times the visible cross-sectional area.
Parameters: - distance (~numpy.ndarray) – Distance to the stellar object in cm
- energy (~numpy.ndarray) – Energy range in erg
Notes
This function returns the photon distribution instead of the distribution times the cross-sectional area. Is this correct? Why is the incident photon distribution calculated at all?
-
ChiantiPy.tools.sources.
blackbody
(temperature, variable, hnu=1)¶ Calculate the blackbody photon distribution as a function of energy (hnu = 1) or as a function of wavelength (hnu = 0) in units of \(\mathrm{photons}\,\mathrm{cm}^{-2}\,\mathrm{s}^{-1}\,\mathrm{str}^{-1}\,\mathrm{erg}^{-1}\)
Parameters: - temperature (~numpy.float64) – Temperature at which to calculate the blackbody photon distribution
- variable (~numpy.ndarray) – Either energy (in erg) or wavelength (in angstrom)
- hnu (int) – If 1, calculate distribution as a function of energy. Otherwise, calculate it as a function of wavelength
Returns: {‘photons’, ‘temperature’, ‘energy’} or {‘photons’, ‘temperature’, ‘wvl’}
Return type: dict
ChiantiPy.tools.util module¶
Utility functions
Notes
Some of these functions can be replaced by roman numeral and periodic table lookup libraries. some functions using os.walk can be replaced by os.path
-
ChiantiPy.tools.util.
between
(array, limits)¶ Find the indices of array corresponding to values in the range given by limits
Parameters: - array (‘list` or ~numpy.ndarray`)
- limits (list, tuple or ~numpy.ndarray` of length 2)
-
ChiantiPy.tools.util.
convertName
(name)¶ Convert ion name string (e.g. ‘fe_13’) to atomic number and ion number.
Parameters: name (str) – the CHIANTI style name for an ion, such as fe_14 Returns: {‘Z’, ‘Ion’, ‘Dielectronic’, ‘Element’, ‘higher’, ‘lower’} – higher and lower are the Chianti-style names for the higher and lower ionization stages, respectively. Return type: dict
-
ChiantiPy.tools.util.
descale_bt
(bte, btomega, f, ev1)¶ Apply excitation descaling of [3] to energy and collision strength
Parameters: - bte (array-like) – Scaled energy
- btomega (array-like) – Scaled collision strength
- f (array-like)
- ev1 (array-like)
Returns: [energy,omega] – Descaled energy and collision strength
Return type: list
Notes
Need more details here. Not clear which equations are being used.
See also
scale_bt()
- Apply scaling to excitation energy and cross-section
References
[3] Burgess, A. and Tully, J. A., 1992, A&A, 254, 436
-
ChiantiPy.tools.util.
descale_bti
(bte, btx, f, ev1)¶ Apply ionization descaling of [9] to energy and cross-sections of [7].
Parameters: - bte (array-like) – Scaled energy
- btx (array-like) – Scaled cross-section
- f (float) – Scaling parameter
- ev1 (float) – ionization potential - units determine the output energy units
Returns: [energy,cross] – Descaled energy and cross-section
Return type: list
Notes
This is the scaling used and discussed in the Dere (2007) calculation [7] of cross sections. It was derived from similar scalings provided by reference [2]
See also
scale_bti()
- Descale ionization energy and cross-section
References
[9] Burgess, A. and Tully, J. A., 1992, A&A, 254, 436
-
ChiantiPy.tools.util.
dilute
(radius)¶ Calculate the dilution factor.
Parameters: radius (array-like) – Distance from the center of a star in units of the stellar radius. Notes
If radius is less than 1.0, returns 0.
-
ChiantiPy.tools.util.
el2z
(els)¶ Convert elemental symbol to atomic number
Parameters: els (str) – the abreviated element name Returns: z – the atomic number or nuclear charge of the element Return type: int
-
ChiantiPy.tools.util.
ion2filename
(ions)¶ Convert ion name string to generic directory-file name. convertName has probably made this redundant
Parameters: ions (str) – the CHIANTI style name for an ion, such as fe_14 Returns: fname – the full file name of the ion directory in the CHIANTI database assumes a top directory from the environmental variable XUVTOP Return type: str
-
ChiantiPy.tools.util.
listFiles
(dir)¶ Walks the path and subdirectories to return a list of files.
Parameters: dir (str) – the top directory to search subdirectories are also searched Returns: listname – a list of files in dir and subdirectories Return type: list Notes
This can be replaced by functions in os.path, as if 3.4, pathlib is probably better. It is not clear that this function is used anywhere in ChiantiPy
-
ChiantiPy.tools.util.
listRootNames
(dir)¶ Walks the path and subdirectories to return a list of file root names.
Notes
This can be replaced by functions in os.path, as if 3.4, pathlib is probably better. Only seems to be used by
-
ChiantiPy.tools.util.
qrp
(z, u)¶ Calculate \(Q_R^{\prime}(Z,u)\), where \(u=\epsilon/I\) is the impact electron energy in threshold units, from Eq. 2.12 of [4].
Parameters: - z (int) – Atomic number
- u (array-like) – Impact electron energy in threshold units.
Returns: q – 1s ionization cross-section, \(Q_R^{\prime}(Z,u)\)
Return type: array-like
Notes
Used for calculations of direct ionization cross-sections of the H and He sequences in ChiantiPy.tools.io.twophotonHRead and ChiantiPy.tools.io.twophotonHeRead, respectively.
References
[4] Fontes, C. et al., 1999, PhRvA, 59, 1329
-
ChiantiPy.tools.util.
scale_bt
(evin, omega, f, ev1)¶ Apply excitation scaling of [8] to energy and collision strength.
Parameters: - evin (array-like)
- omega (array-like)
- f (array-like)
- ev1 (array-like)
Returns: [bte,btomega] – Scaled energy and collision strength
Return type: list
Notes
Need more details here. Not clear which equations are being used.
See also
descale_bt()
- Descale excitation energy and cross-section
-
ChiantiPy.tools.util.
scale_bt_rate
(inDict, ip, f=1.7)¶ Apply ionization descaling of [7], a Burgess-Tully type scaling to ionization rates and temperatures. The result of the scaling is to return a scaled temperature between 0 and 1 and a slowly varying scaled rate as a function of scaled temperature. In addition, the scaled rates vary slowly along an iso-electronic sequence.
Parameters: - inDict (dict) – the input dictionary should have the following key pairs: temperature, array-like and rate, array-like
- ip (float) – the ionization potential in eV.
- f (float (optional)) – the scaling parameter, 1.7 generally works well
Notes
btTemperature and btRate keys are added to inDict
-
ChiantiPy.tools.util.
scale_bti
(evin, crossin, f, ev1)¶ Apply ionization scaling of [7],[8]_, to energy and cross-section.
Parameters: - evin (float) – Energy - same units as ev1
- crossin (array-like) – Cross-section
- f (float - the scale factor)
- ev1 (float) – the ionization potential units - the same as evin
Returns: [bte,btx] – Scaled energy and cross-section
Return type: list
Notes
This is the scaling used and discussed in the Dere (2007) calculation [1] of cross sections. It was derived from similar scalings derived in reference [2]
See also
descale_bti()
- Descale ionization energy and cross-section
References
[7] (1, 2, 3, 4) Dere, K. P., 2007, A&A, 466, 771, [8] (1, 2) Burgess, A. and Tully, J. A., 1992, A&A, 254, 436
-
ChiantiPy.tools.util.
scale_classical
(inDict, ip)¶ Apply the classical scaling to the input data
Parameters: inDict (dictionary) –
- the input dictionary should have the following key pairs
energy and cross or temperature and rate
energy (array-like) – energy values of the cross-section
cross (array-like) – a cross-section
temperature (array-like)
rate (array-like)
ip (float) – the ionization potential. Typically in eV.
Returns – the following keys are added to inDict
——-
{‘csEnergy’, ‘csCross’, ‘ip’} or {‘csTemperature’, ‘csRate’, ‘ip’}
-
ChiantiPy.tools.util.
spectroscopic2name
(el, roman)¶ Convert from spectroscopic notation, e.g. Fe XI to ‘fe_11’.
Parameters: - el (str) – Elemental symbol, e.g. Fe for iron
- roman (str) – Roman numeral spectroscopic symbol
-
ChiantiPy.tools.util.
splomDescale
(splom, energy)¶ Calculate the collision strength for excitation-autoionization as a function of energy.
Parameters: - energy (array-like) – In eV
- splom (dict) – Structure returned by ChiantiPy.tools.io.splomRead
Returns: omega – Collision strength
Return type: array-like
-
ChiantiPy.tools.util.
z2element
(z)¶ Convert atomic number z to its elemental symbol.
Parameters: z (int) – The atomic number/nuclear charge Returns: element – the abbreviated element name Return type: str
-
ChiantiPy.tools.util.
zion2dir
(z, ion, dielectronic=False, xuvtop='')¶ Convert atomic number and ion number to CHIANTI database directory.
Parameters: - z (int) – The atomic number/nuclear charge
- ion (int) – the ionization stage, 1 for the neutral, 2 for the first ionization stage, …
- dielectronic (bool, optional)
- xuvtop (str, optional) – Set different CHIANTI database than the default
Returns: fname – the CHIANTI directory where the file for the ion specified by z and ion are found
Return type:
-
ChiantiPy.tools.util.
zion2filename
(z, ion, dielectronic=False, xuvtop='')¶ Convert nuclear charge/atomic number and ion number to CHIANTI database filename.
Parameters: - z (int) – The atomic number/nuclear charge
- ion (int) – the ionization stage, 1 for neutrals, 2 for singly ionized
- dielectronic (bool, optional) – whether the ion is the simple dielectronic model
- xuvtop (str, optional) – the top directory of the CHIANTI database to be used
Returns: fname – CHIANTI database filename
Return type:
-
ChiantiPy.tools.util.
zion2localFilename
(z, ion, dielectronic=False)¶ Convert atomic number and ion number to generic file name with current directory at top.
Parameters: - z (int) – The atomic number/nuclear charge
- ion (int) – the ionization stage, 1 for neutrals, 2 for singly ionized
- dielectronic (bool, optional)
-
ChiantiPy.tools.util.
zion2name
(z, ion, dielectronic=False)¶ Convert atomic number and ion number to generic name, e.g. (26,13) to ‘fe_13’
Parameters: - z (int) – The atomic number/nuclear charge
- ion (int) – the ionization stage, 1 for the neutral, 2 for the first ionization stage, …
- dielectronic (bool, optional)
Returns: thisone – the CHIANTI style ion name, such as ‘fe_13’
Return type:
-
ChiantiPy.tools.util.
zion2spectroscopic
(z, ion, dielectronic=False)¶ Convert atomic number and ion number to spectroscopic notation string
Parameters: - z (int) – The atomic number/nuclear charge
- ion (int) – the ionization stage, 1 for neutrals, 2 for singly ionized
- dielectronic (bool, optional)
Returns: spect – the spectroscopic notation for the ion, such as Fe XIV
Return type: str
Module contents¶
Basic tools and utilities used in ChiantiPy


书馆首页
回到书馆的首页，这里作为游览的起点
内容分类
this is a description for shop123213
兴趣游廊
this is a description for shop21312
书友相会
this is a description for shop12312


| Methods' Details |
getCount
- Returns
- the number of dictionaries in the list.
|
|
getDictionaries
- Returns
- a sequence with an entry for every dictionary
in the list.
- See also
- XDictionary
|
|
getDictionaryByName
| XDictionary |
| getDictionaryByName( |
[in] string |
aDictionaryName ); |
- Description
- searches the list for a dictionary with a given name.
- Returns
- the XDictionary with the specified name. If no such
dictionary exists, NULL will be returned.
- Parameter aDictionaryName
- specifies the name of the dictionary to look for.
- See also
- XDictionary
|
|
addDictionary
- Description
- adds a dictionary to the list.
Additionally, the dictionary-list will add itself to the list of dictionary
event listeners of that dictionary.
- Returns
- true if the dictionary was added successfully,
false otherwise.
- Parameter xDictionary
- the dictionary to be added.
- See also
- XDictionary
|
|
removeDictionary
| boolean |
| removeDictionary( |
[in] XDictionary |
xDictionary ); |
- Description
- removes a single dictionary from the list.
If the dictionary is still active, it will be deactivated
first. The dictionary-list will remove itself from the list of
dictionary event listeners of the dictionary.
- Returns
- true if the dictionary was removed successfully, false
otherwise.
- Parameter xDictionary
- dictionary to be removed from the list of dictionaries.
- See also
- XDictionary
|
|
addDictionaryListEventListener
- Description
- adds an entry to the list of dictionary-list event listeners.
On dictionary-list events, each entry in the listener list will
be notified via a call to
XDictionaryListEventListener::processDictionaryListEvent.
- Returns
- true if the entry was made, false otherwise.
If ::com::sun::star::lang::XEventListener::disposing
was called before, it will always fail.
- Parameter xListener
- the object to be notified of dictionary-list events.
- Parameter bReceiveVerbose
- true if the listener requires more detailed event
notification than usual.
- See also
- XDictionaryListEventListener, com::sun::star::linguistic2::XDictionaryListEvent
|
|
removeDictionaryListEventListener
- Description
- removes an entry from the list of dictionary-list event listeners.
- Returns
- true if the object to be removed was found and removed,
false otherwise.
- Parameter xListener
- the object to be removed from the listener list.
- See also
- XDictionaryListEventListener, com::sun::star::linguistic2::XDictionaryListEvent
|
|
beginCollectEvents
| short |
| beginCollectEvents(); |
- Description
- increases request level for event buffering by one.
The request level for event buffering is an integer
counter that is initially set to 0.
As long as the request level is not 0, events will be buffered
until the next flushing of the buffer.
- Returns
- the current request level for event buffering.
- See also
- com::sun::star::linguistic2::XDictionaryListEvent, XDictionaryListEventListener, XDictionaryList::endCollectEvents, XDictionaryList::flushEvents
|
|
endCollectEvents
| short |
| endCollectEvents(); |
- Description
- flushes the event buffer and decreases the request level for
event buffering by one.
There should be one matching endCollectEvents call for every
beginCollectEvents call. Usually you will group these around
some code where you do not wish to get notfied of every single
event.
- Returns
- the current request level for event buffering.
- See also
- com::sun::star::linguistic2::XDictionaryListEvent, XDictionaryListEventListener, XDictionaryList::beginCollectEvents, XDictionaryList::flushEvents
|
|
| flushEvents
|
createDictionary
- Description
- creates a new dictionary.
- Returns
- an empty dictionary with the given name, language and type.
NULL on failure.
- Parameter aName
- is the name of the dictionary (should be unique).
- Parameter aLocale
- defines the language of the dictionary.
Use an empty aLocale for dictionaries which may contain
entries of all languages.
- Parameter eDicType
- specifies the type of the dictionary.
- Parameter aURL
- is the URL of the location where the dictionary is persistent,
if the XStorable interface is supported.
It may be empty, which means the dictionary will not be persistent.
- See also
- XDictionary, ::com::sun::star::lang::Locale, DictionaryType
|
|
Copyright © 2013, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Flazinc parsing problem</TITLE>

Hi,

I am making a PhD in Ilog. Yet I am trying to make a parser to use solve minizinc model with Ilog product. My frame work is to use the minizinc to flazinc translation and next to parse the flazinc model a write a model in our concept.

Yet I am trying to do the same with Gecode. I use Gecode 2.0.0 and flatzinc-gecode-1.0, but I can’t solve model produce by minizinc to flatzinc. This give an error if its meet a constant (i.e : int I = 3).

What can I do to correct this?

Thanks in advance.

Best regards

Florent Verroust


--- layout: post title: "Waiting to happen" description: "A typical future test maintenance problem." date: 2021-01-11 6:31 UTC tags: [Unit Testing] --- {% include JB/setup %}
{{ page.description }}
In a recent article I showed a unit test and parenthetically mentioned that it might have a future maintenance problem. Here's a more recent version of the same test. Can you tell what the future issue might be?
[Theory] [InlineData("2023-11-24 19:00"<EMAIL_ADDRESS>"Julia Domna", 5)] [InlineData("2024-02-13 18:15"<EMAIL_ADDRESS>"Xenia Ng", 9)] [InlineData("2023-08-23 16:55"<EMAIL_ADDRESS>null, 2)] [InlineData("2022-03-18 17:30"<EMAIL_ADDRESS>"Shanghai Li", 5)] public async Task PostValidReservationWhenDatabaseIsEmpty( string at, string email, string name, int quantity) { var db = new FakeDatabase(); var sut = new ReservationsController( new SystemClock(), new InMemoryRestaurantDatabase(Grandfather.Restaurant), db); var dto = new ReservationDto { Id = "B50DF5B1-F484-4D99-88F9-1915087AF568", At = at, Email = email, Name = name, Quantity = quantity }; await sut.Post(dto); var expected = new Reservation( Guid.Parse(dto.Id), DateTime.Parse(dto.At, CultureInfo.InvariantCulture), new Email(dto.Email), new Name(dto.Name ?? ""), dto.Quantity); Assert.Contains(expected, db.Grandfather); }
To be honest, there's more than one problem with this test, but presently I'm going to focus on one of them.
Since you don't know the details of the implementation, you may not be able to tell what the problem might be. It's not a trick question. On the other hand, you might still be able to guess, just from the clues available in the above code listing.
The code shown here is part of the sample code base that accompanies my book Code That Fits in Your Head.
Here are some clues to consider: I'm writing this article in the beginning of 2021. Consider the dates supplied via the [InlineData]
attributes. Seen from 2021, they're all in the future.
Notice, as well, that the sut
takes a SystemClock
dependency. You don't know the SystemClock
class (it's a proprietary class in this code base), but from the name I'm sure that you can imagine what it represents.
From the perspective of early 2021, all dates are going to be in the future for more than a year. What is going to happen, though, once the test runs after March 18, 2022?
That test case is going to fail.
You can't tell from the above code listing, but the system under test rejects reservations in the past. Once March 18, 2022 has come and gone, the reservation at "2022-03-18 17:30"
is going to be in the past. The sut
will reject the reservation, and the assertion will fail.
You have to be careful with tests that rely on the system clock.
The fundamental problem is that the system clock is non-deterministic. A typical reaction to non-determinism in unit testing is to introduce a Test Double of some sort. Instead of using the system clock, you could use a Stub as a stand-in for the real time.
This is possible here as well. The ReservationsController
class actually depends on an IClock
interface that SystemClock
implements. You could define a test-specific ConstantClock
implementation that would always return a constant date and time. This would actually work, but would rely on an implementation detail.
At the moment, the ReservationsController
only calls Clock.GetCurrentDateTime()
a single time to get the current time. As soon as it has that value, it passes it to a pure function, which implements the business logic:
var now = Clock.GetCurrentDateTime(); if (!restaurant.MaitreD.WillAccept(now, reservations, reservation)) return NoTables500InternalServerError();
A ConstantClock
would work, but only as long as the ReservationsController
only calls Clock.GetCurrentDateTime()
once. If it ever began to call this method multiple times to detect the passing of time, using a constant time value would mostly likely again break the test. This seems brittle, so I don't want to go that way.
Working with the system clock in automated tests is easier if you deal with relative time. Instead of defining the test cases as absolute dates, express them as days into the future. Here's one way to refactor the test:
[Theory] [InlineData(1049, 19, 00<EMAIL_ADDRESS>"Julia Domna", 5)] [InlineData(1130, 18, 15<EMAIL_ADDRESS>"Xenia Ng", 9)] [InlineData( 956, 16, 55<EMAIL_ADDRESS>null, 2)] [InlineData( 433, 17, 30<EMAIL_ADDRESS>"Shanghai Li", 5)] public async Task PostValidReservationWhenDatabaseIsEmpty( int days, int hours, int minutes, string email, string name, int quantity) { var at = DateTime.Now.Date + new TimeSpan(days, hours, minutes, 0); var db = new FakeDatabase(); var sut = new ReservationsController( new SystemClock(), new InMemoryRestaurantDatabase(Grandfather.Restaurant), db); var dto = new ReservationDto { Id = "B50DF5B1-F484-4D99-88F9-1915087AF568", At = at.ToString("O"), Email = email, Name = name, Quantity = quantity }; await sut.Post(dto); var expected = new Reservation( Guid.Parse(dto.Id), DateTime.Parse(dto.At, CultureInfo.InvariantCulture), new Email(dto.Email), new Name(dto.Name ?? ""), dto.Quantity); Assert.Contains(expected, db.Grandfather); }
The absolute dates always were fairly arbitrary, so I just took the current date and converted the dates to a number of days into the future. Now, the first test case will always be a date 1,049 days (not quite three years) into the future, instead of November 24, 2023.
The test is no longer a failure waiting to happen.
Treating test cases that involve time and date as relative to the current time, instead of as absolute values, is usually a good idea if the system under test depends on the system clock.
It's always a good idea to factor as much code as you can as pure functions, like the above WillAccept
method. Pure functions don't depend on the system clock, so here you can safely pass absolute time and date values. Pure functions are intrinsically testable.
Still, as the test pyramid suggests, relying exclusively on unit tests isn't a good idea. The test shown in this article isn't really a unit test, but rather a state-based integration test. It relies on both the system clock and a Fake database. Expressing the test cases for this test as relative time values effectively addresses the problem introduced by the system clock.
There are plenty of other problems with the above test. One thing that bothers me is that the 'fix' made the line count grow. It didn't quite fit into a 80x24 box before, but now it's even worse! I should do something about that, but that's a topic for another article.


About
Who are we ?
We are the new kid on the block founded in year 2019 The reason we exist is to help people who need cleaning service and those who need to provide cleaning service to have a platform to meet. Sometimes you don't have time to clean your place and you need the helping hand and we provide you with that helping hand.
What we do ?
We are the new kid on the block founded in year 2019 The reason we exist is to help people who need cleaning service and those who need to provide cleaning service to have a platform to meet. Sometimes you don't have time to clean your place and you need the helping hand and we provide you with that helping hand.
Services
Who are we ?
We are the new kid on the block founded in year 2019 The reason we exist is to help people who need cleaning service and those who need to provide cleaning service to have a platform to meet. Sometimes you don't have time to clean your place and you need the helping hand and we provide you with that helping hand.
What we do ?
We are the new kid on the block founded in year 2019 The reason we exist is to help people who need cleaning service and those who need to provide cleaning service to have a platform to meet. Sometimes you don't have time to clean your place and you need the helping hand and we provide you with that helping hand.


My Note based on Node.js, Express.js and Client Javascript
Create new file
You can download your file :
DownloadWarning! After downloading file will be deleted immediatly.
If You want to store your files You can sign Up or sign In
×
Forgot Password?
×
All fields are required!


Blade Runner's art director Syd Mead is a huge fan of Tesla's new Cybertruck
by Tyler Sonnemaker- Blade Runner artistic director Syd Mead called the Cybertruck “stylistically breathtaking.”
- Elon Musk had previously said the truck would look like a vehicle from the popular sci-fi movie.
- Mead also told Business Insider that he was “truly flattered” that Musk had taken inspiration from the movie.
- Visit Business Insider’s homepage for more stories.
Syd Mead, the artistic director behind popular sci-fi movie Blade Runner, said in an emailed statement to Business Insider that Tesla’s new Cybertruck “has completely changed the vocabulary of the personal truck market design.”
Mead called the futuristic-looking design “stylistically breathtaking” and said it went beyond his expectations.
When Elon Musk first announced the truck last November, he told Recode’s Kara Swisher that the truck would “look like something out of ‘Blade Runner.'” Mead said in his statement that, “as a long time admirer of Elon Musk, [he] was truly flattered” to hear that the Cybertruck would take a cue from the movie.
Not everyone has had such positive reactions to Tesla’s latest design, and some launch event hiccups didn’t help, but Mead’s words are high praise.
- Read more:
- Everything that happened when Elon Musk unveiled the Cybertruck, including the window-breaking mistake that made him say ‘Oh my f—ing god’
- The 12 coolest features of Tesla’s new $US39,900 Cybertruck pickup
- ‘Looks weird… like, really weird’: Wall Street isn’t sold on Tesla’s new Cybertruck design. Here’s what 7 analysts think about the electric pickup.
- Elon Musk took shots at Ford’s F-150 and other automakers during Tesla’s Cybertruck reveal


--- layout: page weight: 0 title: BCC navigation: show: true ---
Automatically sends a blind carbon copy to an address for every e-mail sent without adding that address to the header. Please note that only one email address may be entered in this field, if you wish to distribute BCCs to multiple addresses you will need to create a distribution group or use forwarding rules.
{% anchor h2 %} Settings {% endanchor %}| Name | Required | Description |
|---|---|---|
| Yes | Sets the entered address to be the BCC recipient. |


|
|||||||||||||||||||||||||||
Amazon - Presented by a guest speaker, Andrew Franklin Amazon have recently unleashed a series of new web services which enable scalable computing, mass storage and an accessible human work force which allow small projects to use facilities previously only available to large companies at a fraction of the cost. Andrew Franklin will give a short presentation looking at some of the services offered by Amazon and will discuss implementation issues with practical examples. Microsoft Office Access 2007
In this session,
Adam
Cogan will cover Microsoft Office Access' 2007 new
and improved
features which can help you:
To find out more, come along and hear what other functions
and benefits Access 2007 has to offer!
|
How to implement online credit card processing
|
||||||||||||||||||||||||||
Featured Service: SSW eXtreme Emails!Key Features & Benefits
SSW eXtreme Emails! enables you to use Microsoft Outlook
as an intelligent bug
Now works with Outlook 2007. |
|||||||||||||||||||||||||||
Merry Christmas from SSW
From all the staff at SSW we
would like to wish you a
very Merry Christmas and a Happy New Year. May you
enjoy a festive season with your families and keep
safe. See you in 2006.
» Monday 25th Dec 2006 | |||||||||||||||||||||||||||
Advertise with SSW
If you would like to advertise your product or
service with SSW or would like to find out more
about different advertising opportunities,
please email your enquiries to
<EMAIL_ADDRESS>or call: +61 2 9953 3000. |
|
| Copyright ?SSW 1990-2006. All Rights Reserved. | Proudly developed by SSW Sydney Web Design | |
|


referenced
by Christina Chortaria at 2022-12-14 22:38:51.merged
by Christina Chortaria at 2022-12-14 22:38:51.closed
by Christina Chortaria at 2022-12-14 22:38:51.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:38:52.closed
by Christina Chortaria at 2022-12-15 13:58:51.referenced
by Christina Chortaria at 2022-12-15 13:59:26.merged
by Christina Chortaria at 2022-12-15 13:59:26.closed
by Christina Chortaria at 2022-12-15 13:59:26.head_ref_deleted
by Christina Chortaria at 2022-12-15 13:59:27.@dependabot rebase
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate
.
mentioned
by Dependabot at 2022-12-14 22:41:05.deployed
by None at 2022-12-14 22:46:47.referenced
by Christina Chortaria at 2022-12-14 22:49:40.merged
by Christina Chortaria at 2022-12-14 22:49:40.closed
by Christina Chortaria at 2022-12-14 22:49:40.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:49:41.Looks like loofah is up-to-date now, so this is no longer needed.
closed
by None at 2022-12-14 22:50:17.head_ref_deleted
by None at 2022-12-14 22:50:19.this PR creates a new directory in data_fixes that includes the subject and agents reports and subject and agents deletions
sent 4 reports for now looking at duplicate records by comparing strings in all name forms against uri's; identifier cleanup; unused agents; and source values to remediate.
referenced
by Christina Chortaria at 2022-12-14 22:52:04.merged
by Christina Chortaria at 2022-12-14 22:52:04.closed
by Christina Chortaria at 2022-12-14 22:52:04.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:52:05.@dependabot rebase
mentioned
by Dependabot at 2022-12-14 22:52:20.head_ref_force_pushed
by None at 2022-12-14 22:52:55.referenced
by Christina Chortaria at 2022-12-14 23:59:22.merged
by Christina Chortaria at 2022-12-14 23:59:22.closed
by Christina Chortaria at 2022-12-14 23:59:22.head_ref_deleted
by Christina Chortaria at 2022-12-14 23:59:23.closed
by Max Kadel at 2022-12-15 14:26:41.deployed
by None at 2022-12-15 14:19:41.referenced
by Max Kadel at 2022-12-15 14:26:39.merged
by Max Kadel at 2022-12-15 14:26:40.closed
by Max Kadel at 2022-12-15 14:26:40.head_ref_deleted
by Max Kadel at 2022-12-15 14:26:41.Will revisit this next week (12/19/22) and follow up with @kayiwa
mentioned
by Francis Kayiwa at 2022-12-15 14:44:41.subscribed
by Francis Kayiwa at 2022-12-15 14:44:41.assigned
by Christina Chortaria at 2022-12-15 14:45:19.This is blocked until further update from @kevinreiss
mentioned
by Kevin Reiss at 2022-12-15 16:17:29.subscribed
by Kevin Reiss at 2022-12-15 16:17:29.At this checkpoint: - Created a buildindex.rb script to create a json-based index from the Getty data. - Created a sub-directory in bin/, called lunrindex. - Implemented a buildidx.js script, which generates a lunr index from the Getty index above. - Implemented two search scripts: search.js, which builds the lunr index on the fly and runs a simple trial search, and quicksearch.js, which used the pre-built index and runs a simple trial search.
When I get back, I'll incorporate these into the website.
assigned
by Cliff Wulfman at 2022-12-15 22:06:16.closed
by Esmé Cowles at 2022-12-15 22:48:09.referenced
by Esmé Cowles at 2022-12-15 22:48:08.merged
by Esmé Cowles at 2022-12-15 22:48:08.closed
by Esmé Cowles at 2022-12-15 22:48:08.head_ref_deleted
by Esmé Cowles at 2022-12-15 22:48:11.I have identified the correct series of Solr Queries for generating this report:
## Items (Views)
curl "http://localhost:8080/solr/statistics/select?indent=on&version=2.2&start=0&rows=1&fl=*&wt=json&explainOther=&hl.fl=&facet=true&start=0&q=owningComm%3A$COMM_ID%20AND%20owningColl%3A$COLL_ID%20AND%20isBot%3Afalse%20AND%20time%3A$QUERY_TIME%20AND%20type%3A2"
## Bitstreams (Downloads)
curl "http://localhost:8080/solr/statistics/select?indent=on&version=2.2&start=0&rows=1&fl=*&wt=json&explainOther=&hl.fl=&facet=true&start=0&q=owningComm%3A$COMM_ID%20AND%20owningColl%3A$COLL_ID%20AND%20isBot%3Afalse%20AND%20time%3A$QUERY_TIME%20AND%20type%3A0"
...where $COMM_ID
is the Community ID, $COLL_ID
is the Collection ID, and $QUERY_TIME
is the Solr datestamp for the time range. The type
parameter may either be 0
for Bitstreams (downloads), or 2
for Items (views).
This is finally in the state where it can be shared:
https://docs.google.com/spreadsheets/d/14FVKxHNQvRsH4ogepNPkYa8lr3eIyS3j4-AkeJSsNW4/edit?usp=sharing
The report has been shared with the requesting users, and I will look to update this issue should any additional tasks be required.
labeled
by None at 2022-12-15 14:38:55.labeled
by None at 2022-12-15 14:38:38.unlabeled
by None at 2022-12-15 14:39:00.labeled
by None at 2022-12-15 14:39:18.assigned
by None at 2022-12-15 14:40:49.referenced
by None at 2022-12-15 14:49:52.head_ref_force_pushed
by None at 2022-12-15 14:58:56.head_ref_force_pushed
by None at 2022-12-15 17:14:11.ready_for_review
by None at 2022-12-15 18:00:17.referenced
by Trey Pendragon at 2022-12-15 21:29:21.merged
by Trey Pendragon at 2022-12-15 21:29:21.closed
by Trey Pendragon at 2022-12-15 21:29:21.head_ref_deleted
by Trey Pendragon at 2022-12-15 21:29:22.referenced
by Max Kadel at 2022-12-15 19:30:19.merged
by Max Kadel at 2022-12-15 19:30:19.closed
by Max Kadel at 2022-12-15 19:30:19.head_ref_deleted
by Max Kadel at 2022-12-15 19:30:23.head_ref_force_pushed
by None at 2022-12-15 19:31:03.head_ref_force_pushed
by None at 2022-12-15 19:31:05.well I tried to 😂 -- I guess it was in the commit as well.
deployed
by None at 2022-12-14 22:15:30.referenced
by None at 2022-12-15 14:14:22.merged
by None at 2022-12-15 14:14:22.closed
by None at 2022-12-15 14:14:23.head_ref_deleted
by None at 2022-12-15 14:14:24.referenced
by Trey Pendragon at 2022-12-14 22:13:57.closed
by None at 2022-12-15 14:14:25.reopened
by None at 2022-12-15 14:15:14.referenced
by Christina Chortaria at 2022-12-14 22:50:46.merged
by Christina Chortaria at 2022-12-14 22:50:46.closed
by Christina Chortaria at 2022-12-14 22:50:46.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:50:48.@dependabot rebase
mentioned
by Dependabot at 2022-12-14 22:51:12.head_ref_force_pushed
by None at 2022-12-14 22:51:41.referenced
by Christina Chortaria at 2022-12-14 22:56:32.merged
by Christina Chortaria at 2022-12-14 22:56:32.closed
by Christina Chortaria at 2022-12-14 22:56:32.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:56:33.labeled
by Max Kadel at 2022-12-15 19:28:55.referenced
by Christina Chortaria at 2022-12-14 22:39:47.merged
by Christina Chortaria at 2022-12-14 22:39:47.closed
by Christina Chortaria at 2022-12-14 22:39:47.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:39:48.closed
by Christina Chortaria at 2022-12-15 13:58:02.labeled
by Christina Chortaria at 2022-12-15 12:44:46.assigned
by Christina Chortaria at 2022-12-15 12:44:46.it's included in https://github.com/pulibrary/orangelight/pull/3294/files#diff-89cade48462044ee1b672dc5f4c3ec250fbd29effcd8932096a23c1283c6731fR323
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
closed
by Christina Chortaria at 2022-12-15 14:32:11.head_ref_deleted
by None at 2022-12-15 14:32:22.OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
closed
by Christina Chortaria at 2022-12-15 14:32:44.head_ref_deleted
by None at 2022-12-15 14:32:54.Coverage remained the same at 94.499% when pulling 09e2f81b813e43eebbe60fc556ea5f6d853082f6 on makeppllive into a68da0c9828f998c6ad029f1e7b9c314601307fc on main.
Marking this issue as blocked for now.
referenced
by Christina Chortaria at 2022-12-15 21:16:44.merged
by Christina Chortaria at 2022-12-15 21:16:45.closed
by Christina Chortaria at 2022-12-15 21:16:45.head_ref_deleted
by Christina Chortaria at 2022-12-15 21:16:46.closed
by Christina Chortaria at 2022-12-15 21:16:46.Coverage remained the same at 94.515% when pulling 98010c06cdca778d5038d3f5bd85617c6cbd896c on rubocop-omit-hash-value-ruby3.1 into aed1ff69c993c985f66e764618787aa50fcb4b67 on main.
head_ref_force_pushed
by Christina Chortaria at 2022-12-16 01:08:28.ready_for_review
by Christina Chortaria at 2022-12-16 01:19:59.Reinstalled asdf from scratch. Not hitting the same problem. Closing.
closed
by Chuck McCallum at 2022-12-15 16:06:52.ready_for_review
by Chuck McCallum at 2022-12-15 14:32:57.renamed
by Chuck McCallum at 2022-12-15 14:33:37.referenced
by Hector Correa at 2022-12-15 18:09:08.merged
by Hector Correa at 2022-12-15 18:09:08.closed
by Hector Correa at 2022-12-15 18:09:08.head_ref_deleted
by Hector Correa at 2022-12-15 18:09:09.ready_for_review
by Chuck McCallum at 2022-12-15 17:59:48.referenced
by Hector Correa at 2022-12-15 18:10:55.merged
by Hector Correa at 2022-12-15 18:10:55.closed
by Hector Correa at 2022-12-15 18:10:55.head_ref_deleted
by Hector Correa at 2022-12-15 18:10:56.I don't like that a search by DOI works (e.g. "10.80021/0hj6-9f47") but a search by the full URL does not (e.g. "https://doi.org/10.80021/0hj6-9f47").
This behavior it's because we don't store the full URL but I think it is confusing to users and we should make it transparent to them. But this is a first pass.
deployed
by None at 2022-12-15 18:25:59.deployed
by None at 2022-12-15 18:27:39.ready_for_review
by Hector Correa at 2022-12-15 18:32:46.referenced
by Bess Sadler at 2022-12-15 19:56:41.merged
by Bess Sadler at 2022-12-15 19:56:41.closed
by Bess Sadler at 2022-12-15 19:56:41.head_ref_deleted
by Bess Sadler at 2022-12-15 19:56:42.Sounds like we have agreement on what the migration messages should look like, and implementation will happen with ticket #720
closed
by Bess Sadler at 2022-12-15 20:53:49.Even simpler if we populate the form in the ERB: See #761
closed
by Chuck McCallum at 2022-12-16 00:27:31.head_ref_deleted
by Chuck McCallum at 2022-12-16 00:27:36.Even simpler if we populate the form in the ERB: See #761
closed
by Chuck McCallum at 2022-12-16 00:27:45.head_ref_deleted
by Chuck McCallum at 2022-12-16 00:27:49.referenced
by Christina Chortaria at 2022-12-14 22:12:52.merged
by Christina Chortaria at 2022-12-14 22:12:52.closed
by Christina Chortaria at 2022-12-14 22:12:52.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:12:53.referenced
by Christina Chortaria at 2022-12-14 22:14:40.merged
by Christina Chortaria at 2022-12-14 22:14:40.closed
by Christina Chortaria at 2022-12-14 22:14:40.head_ref_deleted
by Christina Chortaria at 2022-12-14 22:14:41.review_requested
by Christina Chortaria at 2022-12-14 23:35:09.referenced
by Francis Kayiwa at 2022-12-15 00:28:09.merged
by Francis Kayiwa at 2022-12-15 00:28:09.closed
by Francis Kayiwa at 2022-12-15 00:28:09.head_ref_deleted
by Francis Kayiwa at 2022-12-15 00:28:10.assigned
by Christina Chortaria at 2022-12-15 14:51:36.referenced
by Christina Chortaria at 2022-12-15 15:02:05.merged
by Christina Chortaria at 2022-12-15 15:02:05.closed
by Christina Chortaria at 2022-12-15 15:02:05.head_ref_deleted
by Christina Chortaria at 2022-12-15 15:02:06.review_requested
by Christina Chortaria at 2022-12-15 14:56:41.review_requested
by Christina Chortaria at 2022-12-15 19:41:08.assigned
by Jane Sandberg at 2022-12-15 19:49:36.head_ref_force_pushed
by Francis Kayiwa at 2022-12-15 19:52:30.referenced
by Bess Sadler at 2022-12-15 21:11:48.merged
by Bess Sadler at 2022-12-15 21:11:48.closed
by Bess Sadler at 2022-12-15 21:11:48.head_ref_deleted
by Bess Sadler at 2022-12-15 21:11:48.catalog-staging is on ruby 3.1 :mushroom:
head_ref_force_pushed
by Christina Chortaria at 2022-12-14 22:17:22.review_requested
by Christina Chortaria at 2022-12-14 22:18:10.renamed
by Christina Chortaria at 2022-12-15 15:17:01.referenced
by Christina Chortaria at 2022-12-15 22:03:54.merged
by Christina Chortaria at 2022-12-15 22:03:54.closed
by Christina Chortaria at 2022-12-15 22:03:54.head_ref_deleted
by Christina Chortaria at 2022-12-15 22:03:55.review_requested
by Jane Sandberg at 2022-12-15 16:49:19.referenced
by Jane Sandberg at 2022-12-15 22:19:40.merged
by Jane Sandberg at 2022-12-15 22:19:40.closed
by Jane Sandberg at 2022-12-15 22:19:40.head_ref_deleted
by Jane Sandberg at 2022-12-15 22:19:41.mentioned
by None at 2022-12-15 00:28:16.subscribed
by None at 2022-12-15 00:28:16.assigned
by Jane Sandberg at 2022-12-15 16:31:26.closed
by Jane Sandberg at 2022-12-15 22:19:41.review_requested
by Jane Sandberg at 2022-12-15 22:38:52.mentioned
by None at 2022-12-15 00:11:01.subscribed
by None at 2022-12-15 00:11:01.assigned
by Jane Sandberg at 2022-12-15 22:46:29.review_requested
by Jane Sandberg at 2022-12-16 00:19:04.this was done.
closed
by Christina Chortaria at 2022-12-15 15:26:42.closed
by Christina Chortaria at 2022-12-15 13:57:02.referenced
by Christina Chortaria at 2022-12-15 15:01:50.merged
by Christina Chortaria at 2022-12-15 15:01:50.closed
by Christina Chortaria at 2022-12-15 15:01:50.head_ref_deleted
by Christina Chortaria at 2022-12-15 15:01:51.


Navbar
6
exercises
Modify week details
Add exercise
Exercise name
Modify
Student
Studentnumber
Exercises done
Time
Submit this week's exercises
Student number
Name
Number of made exercises
Exercises
Submit this week's exercises
Student number
Name
Number of made exercises
Exercises


Module std.concurrency
This is a low-level messaging API upon which more structured or restrictive
APIs may be built. The general idea is that every messageable entity is
represented by a common handle type called a Tid
, which allows messages to
be sent to logical threads that are executing in both the current process
and in external processes using the same interface. This is an important
aspect of scalability because it allows the components of a program to be
spread across available resources with few to no changes to the actual
implementation.
A logical thread is an execution context that has its own stack and which runs asynchronously to other logical threads. These may be preemptively scheduled kernel threads, fibers (cooperative user-space threads), or some other concept with similar behavior.
The type of concurrency used when logical threads are created is determined
by the Scheduler
selected at initialization time. The default behavior is
currently to create a new kernel thread per call to spawn
, but other
schedulers are available that multiplex fibers across the main thread or
use some combination of the two approaches.
Synposis
import std.stdio; import std.concurrency; void spawnedFunc(Tid ownerTid) { // Receive a message from the owner thread. receive( (int i) { writeln("Received the number ", i);} ); // Send a message back to the owner thread // indicating success. send(ownerTid, true); } void main() { // Start spawnedFunc in a new thread. auto childTid = spawn(&spawnedFunc, thisTid); // Send the number 42 to this new thread. send(childTid, 42); // Receive the result code. auto wasSuccessful = receiveOnly!(bool); assert(wasSuccessful); writeln("Successfully printed number."); }
Functions
| Name | Description |
|---|---|
initOnce
|
Same as above, but takes a separate mutex instead of sharing one among
all initOnce instances.
|
initOnce
|
Initializes var with the lazy init value in a
thread-safe manner.
|
locate
|
Gets the Tid associated with name .
|
ownerTid
|
Return the Tid of the thread which spawned the caller's thread.
|
prioritySend
|
Places the values as a message on the front of tid 's message queue.
|
receive
|
Receives a message from another thread. |
receiveOnly
|
Receives only messages with arguments of types T .
|
receiveTimeout
|
Tries to receive but will give up if no matches arrive within duration .
|
register
|
Associates name with tid .
|
send
|
Places the values as a message at the back of tid 's message queue.
|
setMaxMailboxSize
|
Sets a maximum mailbox size. |
setMaxMailboxSize
|
Sets a maximum mailbox size. |
spawn
|
Starts fn (args ) in a new logical thread.
|
spawnLinked
|
Starts fn (args ) in a logical thread and will receive a LinkTerminated
message when the operation terminates.
|
thisTid
|
Returns the caller's Tid .
|
unregister
|
Removes the registered name associated with a tid.
|
yield
|
If the caller is a Fiber and is not a Generator , this function will call
scheduler.yield() or Fiber.yield(), as appropriate.
|
yield
|
Yields a value of type T to the caller of the currently executing
generator.
|
Interfaces
| Name | Description |
|---|---|
Scheduler
|
A Scheduler controls how threading is performed by spawn .
|
Classes
| Name | Description |
|---|---|
FiberScheduler
|
An example Scheduler using Fibers.
|
Generator
|
A Generator is a Fiber that periodically returns values of type T to the
caller via yield . This is represented as an InputRange.
|
LinkTerminated
|
Thrown if a linked thread has terminated. |
MailboxFull
|
Thrown on mailbox crowding if the mailbox is configured with
.
|
MessageMismatch
|
Thrown on calls to if a message other than the type
the receiving thread expected is sent.
|
OwnerTerminated
|
Thrown on calls to if the thread that spawned the receiving
thread has terminated and no more messages exist.
|
PriorityMessageException
|
Thrown if a message was sent to a thread via
std.concurrency.prioritySend and the receiver does not have a handler
for a message of this type.
|
ThreadScheduler
|
An example Scheduler using kernel threads.
|
TidMissingException
|
Thrown when a Tid is missing, e.g. when doesn't
find an owner thread.
|
Structs
| Name | Description |
|---|---|
ThreadInfo
|
Encapsulates all implementation-level data needed for scheduling. |
Tid
|
An opaque type used to represent a logical thread. |
Enums
| Name | Description |
|---|---|
OnCrowding
|
These behaviors may be specified when a mailbox is full. |
Global variables
| Name | Type | Description |
|---|---|---|
scheduler
|
Scheduler
|
Sets the Scheduler behavior within the program.
|
Authors
Sean Kelly, Alex Rønne Petersen, Martin Nowak


Morse Click
BY KORLAMARCH~
0
0
Unfortunately, canvas isn't support in your browser :(
How to play: Press anykey on keyboard when there's a "beep" sound to get points and press Enter to pause/unpause.


Le Memaker
❝
Le derp said something.
❞
Herp
,
Derp
Le bullshit:
Le derp said something.

Le Contributors
-
http://github.com/danodic


Last updated: February 10, 2017
Career Buddy: Freddy Crawford
Career Mentor: Joe Cardillo
I use my whole brain when I am creating. Whether it be writing blog posts, writing code, or designing, I am hitting all four quadrants. Even when I am writing creatively I am using the logical and analytical side of my brain because I want the flow and pacing of the writing to make sense to the reader.
Coding also feels like I am using my whole brain. I get to be creative with the design, but there are limits since I want users (other humans) to be able to use my code. This means my design has to be user-friendly and logical. In addition, writing code that others will be able to understand means I have to use the organizational quadrant of my brain.
Graphic design was my introduction to using my whole brain. I found that when I was designing and working with clients, I was completely immersed in the task at hand. Losing track of time is a clue that points to whole-brain activities.
Hi my name is Sam. I seek to improve people’s lives by improving the technology that they use. I build human-centered apps and websites that help individuals be more creative, productive, and happy. I’m learning full stack web development with the CNM STEMulus Deep Dive Coding Bootcamp, which focuses on the LAMP stack. How are you working within the community?
This is the second version of my elevator pitch.
I found my LinkedIn profile at the top, cool! I also found a couple articles I've written for Thought Catalog and my Upwork freelancer page. My blog, TheMinimalistCreative.net was on the first page, and one of my popular Medium articles is on the second. Surprisingly I found an interview I did with ABQ ZineFest in 2015! I think all of these accurately depict my "brand" as a creative person in Albuquerque. Why is my high school cross country record on the second page!? That's kind of crazy. My "Creative Mornings" profile picture is the first image and there is an old blog post and image from 2012 when I was a student employee at PBS. I kind of wish that one would disappear...
Self doubt and imposter syndrome are internal factors that weigh me down sometimes. External factors include lack of time and experience actually programming.
I always help with simple design projects when people ask for help. I think my writing creates value for others, and that's something I love to do. I love giving personal and professional advice to people who ask for it!
I do believe I have potential professionally. In previous jobs, my supervisors have all liked me, but I felt limited by their lack of planning or organization. I often felt like I was taking things more seriously than anyone else, and that my success was limited by a supervisor's lack of support or inability to take responsibility for their mistakes. This makes it sound like I am blaming everyone else for my problems, but I do hope to one day find a supervisor who works as hard as I do and who inspires me to step outside my comfort zone. I want to learn how to be a great leader from a great leader.
I know I'm still very firmly in the honeymoon phase of this bootcamp, but I'm loving it thus far. I realize I am interested in both frontend and backend development. I seek to understand as much as possible about whatever we are learning and I like asking other students for help when I don't understand something. Everyone has their strengths and I appreciate being part of a team. I think the immersive, fast-paced environment fits my personality and learning style.
This week has been more difficult than Week 1, mostly just because the material is more difficult to understand. It's hard to go to bed each night with a jumble of php syntax floating around my brain! I know that if I keep practicing and asking questions during class, it will eventually start to come together. I've found that for me, the first 50 hours of learning and doing something is the most frustrating. After that, it's still not easy, but at least the pieces make sense. In my personal life I've been having to say "no" a lot to friends who ask me to hang out. Even though everyone knows I'm in the bootcamp I don't think they fully understand the intensity! A year ago I would have felt guilty for saying "no," but at this point in my life I no longer feel that way.
This week went by fast. I enjoyed the time we were able to code on our own because I felt myself getting lost in the work. This weekend I'm planning on reviewing my notes from this week and making sure I remember important concepts. All of the lecture was starting to get to me! I enjoyed getting coffee with Karen and Lisa Atkins, they both gave great advice about how to find a company with integrity to work for.
This week I...
I took charge by reading the rules out loud to my teammates. This seemed to steer us in the right direction, but Erin did speak up and say that she prefers to read the rules herself to make sure she understands.  It made me feel good to know that we can bring up issues and concerns early on in the game. When the game got started, I took less of a leadership role. Nat and Erin seemed to already have a strategy in mind, so I let them do their thing. This worked for me, since strategy isn’t my strength! I felt confident and calm during the game which seems like a good sign.
Our team seemed to work really well together through the game! We started by reading all of the documentation together, out loud, making sure we understood the rules. I think we all are aware of others’ thoughts and feelings, which is good, but I do think it can be detrimental if nobody steps up to make decisions when they need to be made. I will keep this in mind as we move through the Capstone projects.
We got assigned our capstone groups this week and I couldn't be more excited. Thus far we have gotten to know one another on a more personal level and gotten some good work done. I'm optimistic about the rest of our time working together. Personally I feel like I'm in a good place in the bootcamp. I've been able to stay on top of the work and get ahead on a couple projects.
This Week I...
Capstone projects are underway and moving along. George and Dylan said that our group is pretty far ahead of the game, but I think we are moving at a steady and comfortable pace. I may not completely understand the PHP syntax, but the overall concepts are coming together the more time I spend playing around with code.
I realize that I can be headstrong while working amongst a team. I don't mind things moving quickly and pieces of the project coming together without my involvement. But sometimes that means other group members feel confused or left out of the process. I am working on being more inclusive and sensitive to other group members learning styles.
Javascript was the most difficult concept for me this week. I know it is something that I will need to spend more time learning in order for the syntax to make sense. That being said, I tried my best with the Javascript Challenge and didn't get too down on myself for not being able to attempt the more difficult assignment tiers.
Meeting with Karen was good. I appreciate her support and listening ear. After meeting with Dan I was left with a couple actionable tasks that I still need to complete, namely contacting a couple employees at various tech companies in Albuquerque. I've never done this before and it is somewhat out of my comfort zone, but I'm sure it won't be too bad.
I totally forgot to write my reflection this week! D:
I was tired this whole week, but my team and I still got a lot accomplished. Our scrum on Monday was frustrating and it sort of set the tone for the week, but I felt supported by my teammates and determined to make the best of things. Overall, I'm really happy to be part of this group.
Next week I plan to message a designer at Meow Wolf to talk about potential internship/career opportunities. I also plan to send my resume to Elisa Valdez since she mentioned having a potential internship opportunity at Lavu.
This experience has been challenging and rewarding. I am glad I took the plunge - 10 weeks flew by! I found the built-in networking component of the bootcamp to be extremely valuable. Demo day felt like a productive way to show off my skill as a developer to a crowd of potential employers. I know I have a lot to learn, but I think I have gained a solid foundation of computer programming and will be able to find employment in the coming months. I am eager to grow as a developer.
Overall I think I worked hard and excelled in the bootcamp. However, in some ways, I wish I had challenged myself even more. I feel like there were days that I should have spent more time self-studying javascript or php. I am hoping that the code-a-thon this weekend gives me more time in the code, since it feels like so long ago that I wrote anything for the back-end of a software product. I will continue practicing, challenging myself, and seeking mentorship after the bootcamp, which will be an asset in my career search.


Welcome to our page, we are going to collect the results to enhance our catalog for you ^.^
Vote for one of following images :


Changelog
In Development
- hic sunt leones.
v2.0.1
Released on May 31, 2019.
- Fix: XML con elementi
ProcessingInstruction
causano errore in lettura (#66) - Aggiunto nuget badge al README (#58)
- Bump FatturaElettronica to 2.0.6 (#57).
v2.0
Released on March 13, 2019.
- Fix: warning NU5125: The 'licenseUrl' element will be deprecated. Closes #23.
- Bump FatturaElettronica to 2.0.
- Bump Microsoft.NET.Test.Sdk to 16.0.1.
- Bump Portable.BouncyCastle to 1.8.5.
- Bump System.Security.Cryptography.Pkcs to 4.5.2.
- Bump Newtonsoft.Json to 12.0.1.
- CI: switch da AppVeyor a Azure Pipelines. Closes #52.
v1.5
Released on February 26, 2019
- New:
WriteHtml(string outPath, string xslPath)
crea HTML della fattura usando un foglio di stile.
v1.4
Released on February 12, 2019
- New:
ReadXmlSigned(Stream stream)
. Closes #39. - Bump FatturaElettronica to 1.1.5
v1.3
Released on January 18, 2019
- New:
ReadXmlSignedBase64()
method. Addresses #30. - New:
ReadXml(Stream stream)
(Daniele Bochicchio). Pull #19. - Fix:
ReadXmlSigned()
does not support Base64-encoded files. Closes #30. - Fix: Improved
ReadXmlSigned()
performance. - Bump FatturaElettronica to 1.1.1.
v1.2
Released on December 30, 2018
- New:
validateSignature
option forReadXMLSigned
method. Closes #21. - Fix:
ReadXmlSigned
doesn't release the input file. Closes #17. - Dump FatturaElettronica to 1.0.2.
v1.1
Released on December 1, 2018
- New:
WriteXmlSigned
method. - Bump MSTest.TestFramework to 1.4.0
- Bump MSTest.TestAdapter to 1.4.0
v1.0.1
Released on November 9, 2018
- Bump Portable.BouncyCastle to 1.8.4.
- Bump MSTest.TestFramework to 1.3.2.
- Bump MSTest.TestAdapter to 1.3.2.
- Bump Microsoft.Net.Test.Sdk to 15.9.0.
v1.0
Released on November 9, 2018
- Bump FatturaElettronica to 1.0.1.
v0.4
Released on October 27, 2018
- New:
FromJson(string json)
extesion method. - Dependency: FatturaElettronica 0.9.
- Dependency: Newtonsoft.Json (new).
v0.3
Released on October 12, 2018
- New:
FatturaElettronicaFileNameGenerator
class. - Fix: Wrong BouncyCastle dependency. Closes #4.
- Fix:
FatturaElettronicaSignatureException
doesn't report the correct error description. - Dependency: FatturaElettronica v0.8.4.
- CI integration on AppVeyor. Closes #2.
v0.2
Released on October 1, 2018
- New:
WriteXML(string filePath)
extension method. - New:
ReadXML(string filePath)
extension method. - Fix: open the signed file in Read mode.
- Enhancement: improve the signature-stripping algorithm. We don't really need a temporary folder.
v0.1.0
Released on September 27, 2018.
- Initial release.


{% extends 'templates/nhs_transaction_layout.html' %} {% import 'includes/form_macros.html' as form_macros %} {% block afterHeader %} {% include "includes/service-headers/low-income.html" %} {% endblock %} {% block content %} Do {{partnerortext}} get any of these benefits? Income support Universal credit Income based job seekers allowance Income related employment & support allowance or No, {{iwe}} do not get any of these {{ form_macros.button({ label: 'Next' }) }} {% endblock %}
or


A Discord bot for playing games with standard playing cards.
Add to DiscordEach server gets a standard 52-card deck of playing cards that anyone can play with. Use $pcb info at any time for a list of commands.
Toggle between a normal art style and a pixel art style for your server's deck of cards.
Play a game of High or Low with others in your server!


## -*- coding: utf-8 -*- <%include file="../header.html" /> <%! from yubichecker.lib import xtea from pylons import config xtea_key = config['xtea_key'] def my_decrypt(text): return xtea.crypt(xtea_key, text.decode('hex')) line=1 %>
If you lost this key, or if you don't want to use it with our system anymore, simply clic on the link bellow.
You can add it again anytime later.


Team Card Builder
Node JS
Al
Manager
ID: 1
Email:
<EMAIL_ADDRESS>Number:<PHONE_NUMBER>
Steve
Engineer
ID: 2
Email:
<EMAIL_ADDRESS>GitHub:
steve
Mike
Intern
ID: 3
Email:
<EMAIL_ADDRESS>School: School of Rock


Provides a replacement and extension of the optim() function to call to several function minimization codes in R in a single statement. These methods handle smooth, possibly box constrained functions of several or many parameters. Note that function 'optimr()' was prepared to simplify the incorporation of minimization codes going forward. Also implements some utility codes and some extra solvers, including safeguarded Newton methods. Many methods previously separate are now included here.
| Version: | 2018-7.10 |
| Imports: | numDeriv |
| Suggests: | knitr, rmarkdown, setRNG, BB, ucminf, minqa, dfoptim, lbfgsb3, lbfgs, subplex |
| Published: | 2018-09-30 |
| Author: | John C Nash [aut, cre], Ravi Varadhan [aut], Gabor Grothendieck [ctb] |
| Maintainer: | John C Nash <nashjc at uottawa.ca> |
| License: | GPL-2 |
| NeedsCompilation: | no |
| Citation: | optimx citation info |
| Materials: | NEWS |
| In views: | Optimization |
| CRAN checks: | optimx results |
| Reference manual: | optimx.pdf |
| Vignettes: |
Using and extending the optimx package Rvmmin15 SNewton |
| Package source: | optimx_2018-7.10.tar.gz |
| Windows binaries: | r-devel: optimx_2018-7.10.zip, r-release: optimx_2018-7.10.zip, r-oldrel: optimx_2018-7.10.zip |
| OS X binaries: | r-release: optimx_2013.8.7.tgz, r-oldrel: optimx_2013.8.7.tgz |
| Old sources: | optimx archive |
| Reverse depends: | embryogrowth, LIHNPSD, macc, midasr, monmlp, NormalGamma, parfm, phenology, sgt |
| Reverse imports: | BioGeoBEARS, calibrar, CatDyn, CensSpatial, CJAMP, Countr, ecd, gear, invGauss, ldhmm, LifeHist, marked, mrds, mvord, PartCensReg, QuantumClone, rankdist, REndo, ROI.plugin.optimx, spfrontier, Synth |
| Reverse suggests: | ACDm, afex, bbmle, dimRed, heemod, languageR, lava, lme4, nlmrt, RandomFields, regsem |
Please use the canonical form https://CRAN.R-project.org/package=optimx to link to this page.


#assign n0_docs="active"> <#assign n1_dll="active"> <#assign n1_extraddl="active">
We use src/main/resources/extra-ddl.xml
to supply extra DDL
for things like views and stored procedures and sometimes indexes -
effectively any DDL that isn't generated via mapping annotations.
The DDL in extra-ddl is then run as part of normal testing (run after dropCreate
)
and as part of DB migrations (as repeatable migrations).
When using extra-ddl.xml
there are a some practices
that are good to follow:
ddl-script
entry.
Instead group ddl into ddl-script
entries for things that will be
dropped and re-created together. If we want to drop and re-create something by itself
it needs to be in it's own ddl-script
entry.
To define DB views which we can then use on an entity bean via @View
we should add ddl-script
elements into extra-ddl.xml to create the views.
Each entry should allow for re-creating the view so generally includes
drop view if exits
and create view
statements.
Each entry becomes a "repeatable" migration and will run whenever the hash of its content changes and run AFTER all the normal "version" migrations.
Note that it would be considered best practice to create a view in it's own
ddl-script
or include dependent views in their own ddl-script
(views that are [dropped] and created together).
drop view if exists product_vw cascade; create view product_vw as ...; -- 2 related/dependent views that drop and create together drop view if exists promotion_minprice_vw cascade; drop view if exists promotion_vw cascade; create view promotion_vw as ...; create view promotion_minprice_vw as ...;
For stored procedures and triggers add a ddl-script
for
the related objects. Note that to support multiple databases we commonly
specify the platforms
attribute.
create or replace function trigger_store_price_log() returns trigger as $$ begin ...; end; $$ LANGUAGE plpgsql; create trigger trg_store_price_log before update on store_price for each row execute procedure trigger_store_price_log();
Note that there is not a restriction on the DDL we can put into extra-ddl.xml
.
We use extra-dll for DDL that isn't modelled and generated by annotations. For example,
we generally don't expect to use extra-ddl for CREATE TABLE
statements as
that DDL is generated from the mapping annotations @Table
etc.
To support multiple database platforms we specify via the platforms
attribute
which database platforms the DDL applies to.
We can use the same script name
with different platforms
to
handle database specific syntax for views, stored procedures etc.
-- h2 specific DDL drop view order_agg_vw; create view order_agg_vw as ...; -- DLL for postgres, mysql and db2 create or replace view order_agg_vw as ...


Black Ties is a student led group focused on the professional advancement of our members through a series of networking events, speaker-series, mentorship, and an annual development conference. We aim to bridge the gap between current students and notable alumni and professionals, so that our members are best prepared when they embark on their professional careers.
LINKS partners female third-year undergraduate students, regardless of their educational background or interests, with women and men of the Rotman MBA program in order to support the undergraduate students in developing the necessary skills that will allow them to successfully transition to their professional life, creating meaningful and productive mentoring relationships.
If you are a third year undergraduate woman who is interested in receiving career development help transitioning into the workforce, please visit our website to learn more about the program and sign up!
Her Campus is the #1 new-media brand for the empowered college woman. Written entirely by the world's top college journalists – with 10,000+ contributors and counting – HerCampus.com features national Style, Beauty, Health, Love, Life, Career, Entertainment, News, DIY, LGBTQ+, High School, and After College content supplemented by local content from 350 campus chapters nationwide and in ten countries.


Accordion
Default
Panel one
Panel one content
Panel two
Button
Button
Panel three
Panel three content
Single expand
Panel one
Panel one content
Panel Two
Panel two content
Panel three
Panel three content
With disabled item
Panel two
Panel one content
Disabled
Disabled content
Panel three
Panel three content
Custom expanded and collapsed icons
Panel one
Panel one content


The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:
| GroupId | ArtifactId | Version | Type | Licenses |
|---|---|---|---|---|
| com.pholser | junit-quickcheck-core | 0.7-SNAPSHOT | jar | The MIT License |
| junit | junit | 4.12 | jar | Eclipse Public License 1.0 |
The following is a list of test dependencies for this project. These dependencies are only required to compile and run unit tests for the application:
| GroupId | ArtifactId | Version | Classifier | Type | Licenses |
|---|---|---|---|---|---|
| ch.qos.logback | logback-classic | 1.1.7 | - | jar | Eclipse Public License - v 1.0-GNU Lesser General Public License |
| com.google.guava | guava | 19.0 | - | jar | The Apache Software License, Version 2.0 |
| com.google.guava | guava-testlib | 19.0 | - | jar | The Apache Software License, Version 2.0 |
| com.pholser | junit-quickcheck-core | 0.7-20160421.164633-5 | tests | test-jar | The MIT License |
| org.hamcrest | hamcrest-core | 1.3 | - | jar | New BSD License |
| org.hamcrest | hamcrest-library | 1.3 | - | jar | New BSD License |
| org.mockito | mockito-all | 1.10.19 | - | jar | The MIT License |
The following is a list of transitive dependencies for this project. Transitive dependencies are the dependencies of the project dependencies.
The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:
| GroupId | ArtifactId | Version | Type | Licenses |
|---|---|---|---|---|
| javassist | javassist | 3.11.0.GA | jar | - |
| ognl | ognl | 3.1.2 | jar | The Apache Software License, Version 2.0 |
| org.antlr | antlr-runtime | 3.1.2 | jar | - |
| org.javaruntype | javaruntype | 1.2 | jar | The Apache Software License, Version 2.0 |
| org.slf4j | slf4j-api | 1.7.21 | jar | MIT License |
| ru.vyarus | generics-resolver | 2.0.1 | jar | The MIT License |
The following is a list of test dependencies for this project. These dependencies are only required to compile and run unit tests for the application:
| GroupId | ArtifactId | Version | Type | Licenses |
|---|---|---|---|---|
| ch.qos.logback | logback-core | 1.1.7 | jar | Eclipse Public License - v 1.0-GNU Lesser General Public License |
| com.google.code.findbugs | jsr305 | 1.3.9 | jar | The Apache Software License, Version 2.0 |
| com.google.errorprone | error_prone_annotations | 2.0.2 | jar | - |
Unknown: Antlr 3 Runtime, Javassist, error-prone annotations
Eclipse Public License 1.0: JUnit
The MIT License: Mockito, generics-resolver, junit-quickcheck-core, junit-quickcheck-generators
MIT License: SLF4J API Module
GNU Lesser General Public License: Logback Classic Module, Logback Core Module
New BSD License: Hamcrest Core, Hamcrest library
The Apache Software License, Version 2.0: FindBugs-jsr305, Guava Testing Library, Guava: Google Core Libraries for Java, OGNL - Object Graph Navigation Library, javaruntype
Eclipse Public License - v 1.0: Logback Classic Module, Logback Core Module
| Filename | Size | Entries | Classes | Packages | Java Version | Debug Information |
|---|---|---|---|---|---|---|
| logback-classic-1.1.7.jar | 304.1 kB | 231 | 175 | 26 | 1.6 | Yes |
| logback-core-1.1.7.jar | 470.8 kB | 418 | 372 | 36 | 1.6 | Yes |
| jsr305-1.3.9.jar | 33 kB | 72 | 35 | 3 | 1.5 | Yes |
| error_prone_annotations-2.0.2.jar | 6.4 kB | 20 | 8 | 2 | 1.7 | No |
| guava-19.0.jar | 2.3 MB | 1746 | 1717 | 17 | 1.6 | Yes |
| guava-testlib-19.0.jar | 754.1 kB | 583 | 562 | 7 | 1.6 | Yes |
| junit-quickcheck-core-0.7-SNAPSHOT.jar | 90.4 kB | 77 | 57 | 8 | 1.8 | Yes |
| junit-quickcheck-core-0.7-SNAPSHOT-tests.jar | 298.7 kB | - | - | - | - | - |
| javassist-3.11.0.GA.jar | 614.2 kB | 366 | 347 | 17 | 1.4 | Yes |
| junit-4.12.jar | 314.9 kB | 323 | 286 | 30 | 1.5 | Yes |
| ognl-3.1.2.jar | 230.3 kB | 141 | 130 | 3 | 1.5 | Yes |
| antlr-runtime-3.1.2.jar | 138.8 kB | 105 | 92 | 4 | 1.4 | Yes |
| hamcrest-core-1.3.jar | 45 kB | 52 | 45 | 3 | 1.5 | Yes |
| hamcrest-library-1.3.jar | 53.1 kB | 46 | 35 | 7 | 1.5 | Yes |
| javaruntype-1.2.jar | 71.2 kB | 51 | 34 | 6 | 1.5 | Yes |
| mockito-all-1.10.19.jar | 1.2 MB | 1215 | 752 | 79 | 1.5 | Yes |
| slf4j-api-1.7.21.jar | 41.1 kB | 46 | 34 | 4 | 1.5 | Yes |
| generics-resolver-2.0.1.jar | 22.4 kB | 24 | 14 | 4 | 1.6 | Yes |
| Total | Size | Entries | Classes | Packages | Java Version | Debug Information |
| 18 | 7 MB | 5516 | 4695 | 256 | 1.8 | 16 |
| compile: 8 | compile: 1.5 MB | compile: 1133 | compile: 994 | compile: 76 | - | compile: 8 |
| test: 10 | test: 5.5 MB | test: 4383 | test: 3701 | test: 180 | - | test: 8 |
| Repo ID | URL | Release | Snapshot |
|---|---|---|---|
| central | https://repo.maven.apache.org/maven2 | Yes | No |
| sonatype-nexus-snapshots | https://oss.sonatype.org/content/repositories/snapshots | No | Yes |
Repository locations for each of the Dependencies.


Join Game
Create Game
Waiting for creater to start game...
Join Game
Create Game
Game Code:
Start Game
Title Deed
Woodward Hall
Rent: $10
With 1 House: $100
With 2 Houses: $150
With 3 Houses: $250
With 4 Houses: $400
With Hotel: $700
Mortgage Value: $50
Houses cost $100 each
Go
French Hall
Community Chest
Judge Hall
Income Tax
Novack
Ripley Hall
Chance
Woodward Hall
Smith Hall
Hanover Police
Gile Hall
ORL
Streeter Hall
Lord Hall
Collis Cafe
South Fayerweather Hall
Community Chest
Fayerweather Hall
North Fayerweather Hall
Free Parking
South Massachusetts Hall
Chance
Massachusetts Hall
North Massachusetts Hall
Courtyard Cafe
Berry Hall
Bildner Hall
FO&M
Rauner Hall
Get Good Sammed
Andres Hall
Zimmerman Hall
Community Chest
Morton Hall
1953 Commons
Chance
Fahey Hall
Luxury Tax
McClane Hall
Game Messages
Players


#cd4;
http://eventimg.auction.co.kr/md/auction/07C0B575AE/goods_c1_list.html
http://eventimg.auction.co.kr/md/auction/07C0B575AE/goods_c2_list.html
http://eventimg.auction.co.kr/md/auction/07C0B575AE/goods_c3_list.html
http://eventimg.auction.co.kr/md/auction/07C0B575AE/goods_c4_list.html
http://eventimg.auction.co.kr/md/auction/07C0B575AE/coupon.html


Parsing Through StdErr and StdOut¶
When using the pipeline with the container and go binary file, all standard out messages and errors are reported in the generated log file. It is important to note, that since the pipeline automatically runs steps concurrently when possible, the order of the log files may show some steps running as dependencies become available and based on the threads available. Also, this standard out is used by SAIGE as well, so anything that does not follow the format below is a results of the software calculations generated by SAIGE, and not the pipeline.
The following shows how messages are formatted in the log output:
Logging Levels¶
There are 4 different levels or types of debugging and error handling. Some are meant to inform, while other are meant to stop the pipeline if an error occurs that cannot be resolved.
Level |
Interpretation |
|---|---|
UPDATE! |
To inform the user of the status of the pipeline. |
CONFIRMED! |
To let user know a check or validation has been passed. |
WARNING! |
There may be a problem but it continues through the pipeline and skips the issue. |
ERROR! |
There is definitely a problem and forces the pipeline to prematurely exit. |
By using the levels and function names, one can grep
through the log file to find specific messages related to functions or error types.
Exit Status Codes¶
Although I am not a huge fan of relying on exit status codes, for those that use Gnu Parallel or other software that records exit status to determine if a job was successful or not, I have coded up a few exit codes so that if an error does occur the number can tell the user which function is responsible for the error. This make troubleshooting and errors easier to identify.
functions |
Exit Status |
|---|---|
func(main) |
return 42 |
func(chunk) |
return 10 |
func(smallerChunk) |
None |
func(processing) |
None |
func(nullModel) |
None |
func(associationAnalysis) |
None |
func(checkInput) |
return 5 |
func(saveResults) |
return 99 |
func(saveQueue) |
None |
func(usePrevChunks) |
return 17 |
func(findElement) |
return 20 |
func(parser) |
return 3 |


2018 Swan Spring Camp
Apr 2 - 20 2018
- Time:
- Week 1: Apr 2 - 6.
- Week 2: Apr 9 - 13.
- Week 3: Apr 16 - 20.
- Dedicated Ping Pong camp for beginner and intermediate level kids
- 6 hour training every day from 9am - 12am and 2pm - 5pm, 5 days a week
- Supervised lunch break hour: 12pm – 2pm
- Free Extended Hour from 5pm to 6:30pm
Price and Discount
-
$390 per Week or $200 per half day week
- Bring your own lunch or add $7 for lunch per day
- Sibling: $20 per week or $10 per half day week if 2 or more siblings sign up
Coaching
- Classes are taught by professional players and coaches:
Gaolin Tang and Yin Liu
Registration
- Download registration form, fill it, and email it back to
<EMAIL_ADDRESS>- You can also come on-site to fill the forms and register.
- Make your check payable to PPC or Ping Pong Community, or Paypal to<EMAIL_ADDRESS>- Camp Inquiry Number:<PHONE_NUMBER>,<PHONE_NUMBER>


--- title: "Brand assets of Bulma" layout: default route: brand breadcrumb: - home - brand --- {% include global/navbar.html id="Brand" %} {% include components/hero.html color="primary" icon="fas fa-medal" title="The Bulma **Brand**" subtitle="Download the official Bulma logo" %}
Icon
{% include components/logos-item.html asset="Bulma Icon" %} {% include components/logos-item.html unsplash="fxvpCFZgTe4" asset="Bulma Icon Black" %} {% include components/logos-item.html unsplash="4TKFpJPnyU8" asset="Bulma Icon White" %}Wordmark
{% include components/logos-item.html asset="Bulma Wordmark" %} {% include components/logos-item.html unsplash="KjWMGF0PYuE" asset="Bulma Wordmark" %} {% include components/logos-item.html unsplash="qsnfSvCdec4" asset="Bulma Wordmark White" %}Logo
{% include components/logos-item.html asset="Bulma Logo" %} {% include components/logos-item.html unsplash="8tA3ZSY9Iic" asset="Bulma Logo Black" %} {% include components/logos-item.html unsplash="RMypptC8-B0" asset="Bulma Logo White" %}Color
Hex
#00D1B2
RGB
rgb(0, 209, 178)
HSL
hsl(171, 100%, 41%)