the services and rights the Participating Institution provides to a Student in return for the Student’s payment of Tuition to the Institution; Educational Services does not include fees for room and board, travel, health care, books, supplies or equipment.
IT Training is specific to the Information Technology (IT) industry, or to the skills necessary for performing information it jobs
Health psychology is the study of psychological and behavioral processes in health, illness, and healthcare.
Accounting is the process of recording financial transactions pertaining to a business.
Science encompasses the systematic study of the structure and behaviour of the physical and natural world through observation and experiment.
Media are the communication outlets or tools used to store and deliver information or data.
Teacher education TE (TE) or teacher training refers to the policies, procedures, and provision designed to equip (prospective) teachers with the knowledge, attitudes, behaviors,.
anguage school is a school where one studies a foreign language. Classes at a language school are usually geared towards, for example, communicative competence in a foreign language.
Web programming refers to the writing, markup and coding involved in Web development, which includes Web content, Web client and server scripting and network security..
Be student-centered, rather than teacher-centered or course-centered. Use brief, outcomes-based, descriptive phrases that begin with an imperative or active verb.
A webmaster is a person responsible for maintaining one or more websites. ... Webmasters may be generalists with HTML expertise who manage most or all aspects of web operations..
Take A CourseBusiness accounting is the systematic recording, analysing, interpreting and presenting of financial information. ... Accounting helps business owners meet their compliance obligations. It also helps them make smart decisions with their money.
Take A CourseScience encompasses the systematic study of the structure and behaviour of the physical and natural world through observation and experiment, and technology is the application of scientific knowledge for practical purposes.
Take A CourseHealth psychology is a specialty area that focuses on how biology, psychology, behavior, and social factors influence health and illness. Other terms including medical psychology and behavioral medicine are sometimes used interchangeably with the term health psychology.
Take A CourseWe are providing several plans for join the our society. All plans are user-friendly to all.


Write a referee report for a Working Paper (WP) coauthored by a lead financial economist in Asset Pricing/MacroFinance. I recommend to follow the guidelines on how to write a referee report (here) and ( here ).
For examples, look at the program of the 2022 Asset Pricing Conference organized by the NBER.


Bass Effect Audio PortableWireless Speaker
Encore 32 GB Net-tabelet PCClear SuperView
Media pad white UnlockedGSM Tablet
Galaxy Note Pro 4G LTE TabletTitan GRay 7-Inch 16GB
Samsung Note Pro TabletTitan Gray 7-Inch


Matthew McConaughey opens up about his near-fatal encounter with lethal snake
by Lesego MkhizeCape Town - Move over Chuck Norris, there’s a new sheriff in town.
Actor Matthew McConaughey recently got candid about his life-threatening encounter with a brown snake in Australia in the 1980s, E! News reports.
During an interview on the Today Show, the actor, who was an exchange student at the time, revealed how he was almost bitten by the snake considered to be one of the most venomous reptiles.
The Oscar-winner was going into the back garden at a friend’s house when the incident occurred.
"It was a bit dark and just as I opened it [the gate], I saw it went right through my legs and it gave me a bit of a scare," he recalled.
"And then my friend came over and they caught it and they said, 'That's a brown snake, mate. That could have really sucked.'"
Despite his narrow escape, the Dallas Buyers Club star still considers the brown snake to be his favourite animal, Daily Mail reports.
"That's my favourite animal because it didn't bite me."
(Sources: E! News , Today , Daily Mail )
(Photo: Gallo/Getty Images)


--- layout: post title: Whilst I was out to date: 2004-12-13 00:00:00 ---
Whilst I was out to lunch, a ninja must have slipped silently into the FP office and left this web site lying around on my desk: Pongmechanik, an absolutely ludicrous electro-magnetic version of pong.


-
Anyone interested in buying a $2.1 million house in Worcester?
-
I finally had a chance to write up my thoughts and plans regarding the Crashplan pivot.
-
I finally got around to writing a blog post about my new app, Stand Up.
-
Some thoughts on subscription pricing.
-
Just put together my net neutrality comments for the FCC: Net Neutrality
-
I think this is the first bug I’ve reported that Apple unambiguously resolved: Master for iTunes Droplet – Fixed!
-
I modified my Wordpress Child Theme to include website validation for Micro.blog: Child Theme Modifications for Micro.blog
-
Is this thing on?
subscribe via RSS


Privacy Statement
DATA USE
Troopmaster Software only collect and stores information that you, and other users you have authorized to access your site, voluntarily enter into your system. We do not ever use the personal information entered into this system for any reason other than providing support on your account when requested.
While we do not send emails to any members of your unit, we will occasionally send email to existing customers (members who physically purchased the software or are listed as the primary contact for your unit). These emails may include renewal notices (for licenses that will be expiring in the near future) or occasional product announcements as new versions or other items of interest become available. If you do not wish to receive e-mail from us, please let us know by email at<EMAIL_ADDRESS>or use the Unsubscribe link found at the bottom of any email that you receive from us.
Troopmaster Software does not sell, rent or lease its customer lists to any third parties for any reason.
Troopmaster Software will only disclose your personal information, without notice, if required to do so by law or in the good faith belief that such action is necessary to: (a) conform to the edicts of the law or comply with legal process served on Troopmaster Software; (b) protect and defend the rights or property of Troopmaster Software; and, (c) act under exigent circumstances to protect the personal safety of users of Troopmaster Software, or the public.
SECURITY
We take all available precautions to protect your information. When you submit sensitive information via the website, your information is protected both online and offline.
With respect to security: When we transfer and receive private and sensitive information, we encrypt the traffic using 256-bit SSL encryption. We also have appropriate security measures in place in our physical facilities to protect against the loss, misuse or alteration of information that we have collected from you at our site.
Your unit data is stored on our secure server in your unit's own private SQL Server database that only contains information that you or other members of your unit have added to your database. This data may only be accessed by you or other members to whom you have granted access with a valid User ID and Password. This data may only be accessed by our program and our site is configured to prevent any direct access to your data by any other system. The passwords are also encrypted so they can not be read and can only be reset. Your Database is backed up on a daily basis and can be recovered to any of the last 30 days.
Only employees who require access to information to perform a specific job (e.g., billing or customer service) are granted access to personally identifiable information in your database. Your information is stored on a dedicated server in a secure data center in Phoenix, AZ, hosted by Codero.
CHILDREN UNDER THIRTEEN
Our software may be used by customers to collect personally identifiable information from children under the age of thirteen. It is the responsibility of each customer to ensure that parents of children grant permission to collect and use this information. Troopmaster Software recommends that customers that collect information about children under 13 copy parents on all communication to these children. Troopmaster Software collects this information for the following reason(s): to track their progress in scouting and to facilitate communication with their parents about scouting activities.
If you are under the age of thirteen, you must ask your parent or guardian for permission to use this website. If you are a parent and you have questions regarding our data collection practices, please contact us using the information provided at the end of this Statement of Privacy.
COOKIES
Troopmaster Software may use "cookies" to help you personalize your online experience. A cookie is a text file that is placed on your hard disk by a web page server. Cookies cannot be used to run programs or deliver viruses to your computer. Cookies are uniquely assigned to you, and can only be read by a web server in the domain that issued the cookie to you.
CHANGES TO THIS POLICY
Troopmaster Software may occasionally update this Statement of Privacy to reflect company or customer feedback. We encourage you to periodically review this Statement to be informed of how your information is being protected.
PO Box 416
Palmyra, VA 22963
Updated 04/19/18


Collects a set of unique values.
Create an Array of every value stored in this Set.
An Array of unique elements in this Set.


Qpyl.core package¶
This subpackage contains the core functionality of Qpyl.
Modules qdyn, qfep, and qcalc are used for wrapping Q executables, generating inputs and parsing outputs. Modules qparameter and qlibrary are used for generating, converting, and parsing Q parameter files. Reading of Amber and Macromodel formats is also supported. qstructure contains classes for reading and writing structure files. qtopology implements an internal topology builder for mapping the system’s bonding patterns with the parameters. In conjunction with the force-field potential functions implemented in qpotential one can use the topology object for direct evaluation of individual topological components of the system.
Submodules¶
Qpyl.core.qcalc module¶
Module for wrapping Qcalc functionality. Contains classes for running Qcalc (QCalc), generating inputs (QCalcInput), parsing output (QCalcOutput).
-
class
Qpyl.core.qcalc.
QCalc
(qcalc_exec)[source]¶ Bases:
object
Class for running Qcalc.
Parameters: qcalc_exec (string) – Qcalc executable filename
-
class
Qpyl.core.qcalc.
QCalcInput
(top, dcds, fep=None, lambdas=None)[source]¶ Bases:
object
Class for creating qcalc inputs.
Parameters: - top (string) – topology filename
- dcds (list of strings) – trajectory filenames
- fep (string, optional) – FEP file filename
- lambdas (list of floats, optional) – lambda values
-
CALC_ANGLE
= 4¶
-
CALC_DIST
= 3¶
-
CALC_RES_NB
= 8¶
-
CALC_RMSD
= 1¶
-
CALC_RMSF
= 13¶
-
CALC_TORSION
= 5¶
-
add_angle
(atom1, atom2, atom3)[source]¶ Add a angle/angle_energy calculation.
Parameters: - atom1 (int) – index of atom in topology
- atom2 (int) – index of atom in topology
- atom3 (int) – index of atom in topology
-
add_dist
(atom1, atom2)[source]¶ Add a distance/bond_energy calculation.
Parameters: - atom1 (int) – index of atom in topology
- atom2 (int) – index of atom in topology
-
add_residue_nb_mon
(resid_first, resid_last, masks)[source]¶ Add a residue nonbond monitor calculation.
This is used mostly for calculating LRA group contributions.
Parameters: - resid_first (int) – index of first residue
- resid_las (int) – index of last residue
- masks (list of strings) – masks used to describe the Q region (eg. [“res 314”, “1245”, “1246”, ...])
-
add_rmsd
(masks)[source]¶ Add a RMSD calculation.
Parameters: masks (list of strings) – masks used for the calculation (eg. [“res 314”, “1245”, “1246”, ...])
Qpyl.core.qdyn module¶
Module for wrapping Qdyn functionality. Contains classes for generating and parsing Qdyn inputs (QDynInput) and parsing Qdyn output (QDynOutput).
-
class
Qpyl.core.qdyn.
QDynInput
(input_string='', parameters={}, ignore_errors=False)[source]¶ Bases:
object
Used for parsing, modifying and generating QDyn inputs.
Parameters: - input_string (str) – string of a qdyn input file
- parameters (dict) – { “MD”: { “steps”:10000, “stepsize”:1.00, ... }, ... }
- ignore_errors (boolean, optional) – if set, write error messages to logger.warning instead of raising QDynInputError
Examples
>>> try: # load and parse >>> inp = QDynInput( input_file_string ) # or inp=QDynInput( parameters={ "md": ... } ) # update with another input and save the overridden paramaters >>> overridden_parms = inp.update(input_file_2_string) # update with a dictionary >>> new_parameters = { "md": { "steps" : 100000 }, { "temperature" : 50 } } ) >>> inp.update(new_parameters) >>> # check the input >>> inp.check() >>> # get the input string >>> new_inp_str = inp.get_string() >>> except QDynInputError as e: >>> print "Problem with input file:", str(e)
-
check
()[source]¶ Check for missing parameters.
Raises QDynInputError if required parameters are missing. (is not all knowing, please don’t rely to much on it) If ‘ignore_errors’ is set, it logs warnings instead.
-
class
Qpyl.core.qdyn.
QDynOutput
(qdyn_output, time_unit='ps', step_size=None, start_time=0)[source]¶ Bases:
object
Class for parsing Qdyn output and storing the data.
Supports Qdyn versions 5.10 or higher. Typically used indirectly by wrapper QAnalyseDyns.
Parameters: - qdyn_output (string) – Qdyn output filename
- time_unit (string) – fs,ps,ns (optional, default is ps)
- step_size (float) – use in case the output reads 0.000
- start_time (float) – redefine the start time in given units in case of continuation simulation (default is 0)
Examples
# Load a qdyn output >>> qdo = QDynOutput(“qdyn.log”) # list >>> print qdo.data_EQ_Q[0].get_rows([“Time”, “El”]) # print out the Q-Q electrostatic energy >>> print qdo.data_EQ_Q[0].get_rows([“Time”, “El”])
Qpyl.core.qfep module¶
Module for wrapping Qfep functionality. Contains classes for generating Qfep inputs (QFepInput), performing system calls to Qfep (QFep), and parsing Qfep output (QFepOutput).
-
class
Qpyl.core.qfep.
QFep
(qfep_exec)[source]¶ Bases:
object
Class for running Qfep.
Parameters: qfep_exec (string) – Qfep executable path
-
class
Qpyl.core.qfep.
QFepInput
(energy_files, hij, alpha, temperature, gas_const, points_skip, gap_bins, minpts_bin)[source]¶ Bases:
object
Class for creating qfep inputs.
At the moment, supports only: - 2 states - no predefined Hij - single, constant Hij (mu=eta=r0 = 0)
Parameters: - energy_files (list of strings) – list of energy files
- hij (float) – H12_A offdiagonal constant
- alpha (float) – state2 alpha shift
- temperature (float) – temperature in Kelvin
- gas_const (float) – gas_constant in kcal/mol/K
- points_skip (int) – number of energy points to skip in each frame
- gap_bins (int) – number of gap-bins
- minpts_bin (int) – minimum number of points per bin
-
class
Qpyl.core.qfep.
QFepOutput
(qfep_output, _calc_index=0)[source]¶ Bases:
object
Class for parsing and analysing Qfep output.
All data is stored in DataContainer objects in separate _QFepPart0/1/2/3 objects: QFepOutput.part0.data[1].get_rows(columns=[“EQtot”]) QFepOutput.part2.data.get_rows(columns=[“Egap”, “dGg”])
Some special data can be obtained directly: QFepOutput.dGa # activation free energy QFepOutput.dG0 # reaction free energy
Results of exclusion and QCP calculations are stored in dictionaries QFepOutput.exclusions and QanalyseMap.QCP as QFepOutput objects.
Parameters: - qfep_output (string) – qfep output
- _calc_index (int) – used internally for exclusions and QCP
Qpyl.core.qlibrary module¶
This module implements the QLib class for reading and writing Q (and other) library files.
-
class
Qpyl.core.qlibrary.
QLib
(ff_type, ignore_errors=False)[source]¶ Bases:
object
Class for reading and writing Q library files.
Also supports parsing oplsaa_ffld and amber_lib.
Parameters: - ff_type (string) – Either ‘oplsaa’ or ‘amber’
- ignore_errors (boolean) – Optional, default is False. If set to True, some non-vital exceptions are logged instead.
-
check_valid
()[source]¶ Call ‘check_valid’ on each _LibResidue object.
Raises QLibError if something is not cool with the residues. (see _LibResidue for more info)
-
get_string
()[source]¶ Return the whole Q library in string format.
To print specific residues, use self.residue_dict[name].get_str()
-
read_amber_lib
(libfile)[source]¶ Read and parse an Amber library (.lib) file
Add new residues to QLib.residue_dict as _LibResidue objects
Parameters: libfile (string) – name/path of Amber lib file
-
read_ffld
(ffld_file, qstruct)[source]¶ Read and parse a Macromodel FFLD file for oplsaa parameters.
Parameters: - ffld_file (string) – path/name of ffld file
- qstruct (qstructure.QStruct) – object created with the same structure file as the ffld
The second argument is a QStruct object created with the pdb or mol2 file that was used to create the ffld file. It’s needed to map atoms and residue to their names in the structure.
Atom-types have the following format: resisduename.ATOMNAME Eg. asp.CA
-
read_lib
(libfile)[source]¶ Read and parse a Q library (.lib) file
Add new residues to QLib.residue_dict as _LibResidue objects
Parameters: libfile (string) – name/path of Q lib file
Qpyl.core.qparameter module¶
This module implements the QPrm class for reading and writing Q (and other) parameter files.
-
class
Qpyl.core.qparameter.
QPrm
(ff_type, ignore_errors=False)[source]¶ Bases:
object
Class for reading and writing Q parameter files.
Also supports parsing oplsaa_ffld, amber_parm and amber_frcmod files.
Parameters: - ff_type (string) – Either ‘oplsaa’ or ‘amber’
- ignore_errors (boolean) – Optional, default is False. If set to True, some non-vital exceptions are logged instead.
-
get_string
(atom_types=None, bonds=None, angles=None, torsions=None, impropers=None)[source]¶ Return the Q parameter file in string format.
Optional arguments are lists of _PrmAtom, _PrmBond, _PrmAngle, _PrmTorsion and _PrmImproper objects. If unset, all parameters will be printed.
Examples
>>> get_string(atom_types=[_PrmAtom, _PrmAtom], bonds=[_PrmBond, _PrmBond, _PrmBond], angles=[], torsions=[], impropers=[])
-
read_amber_frcmod
(frcmodfile)[source]¶ Read and parse an Amber parameter file (.frcmod).
Parameters: parm_fn (string) – name of parameter file Returns: list of overwritten parameters Return type: overwritten_prms (list) Same parameters with equal values (duplicates) are overwritten, same parameters with different values raise QPrmError, unless QPrm.ignore_errors is set to True.
At the moment, all comments are ignored.
-
read_amber_parm
(parm_fn)[source]¶ Read and parse an Amber parameter file (.parm).
Parameters: parm_fn (string) – name of parameter file Returns: list of overwritten parameters Return type: overwritten_prms (list) Same parameters with equal values (duplicates) are overwritten, same parameters with different values raise QPrmError, unless QPrm.ignore_errors is set to True.
At the moment, all comments are ignored.
-
read_ffld
(ffld_file, qstruct)[source]¶ Read and parse a Macromodel’s FFLD file for oplsaa parameters.
Parameters: - ffld_file (string) – path/name of ffld file
- qstruct (qstructure.QStruct) – object created with the same structure file as the ffld
Returns: list of overwritten parameters
Return type: overwritten_prms (list)
The second argument is a QStruct object created with the pdb or mol2 file that was used to create the ffld file. It’s needed to map atoms and residue to their names in the structure.
Same parameters with equal values (duplicates) are overwritten, same parameters with different values raise QPrmError, unless QPrm.ignore_errors is set to True.
Created atom-types have the following format: resisduename.ATOMNAME Eg. asp.CA, pxn.OP
-
read_prm
(parm_fn)[source]¶ Read and parse a Q parameter file.
Parameters: parm_fn (string) – name of parameter file Returns: list of overwritten parameters Return type: overwritten_prms (list) Same parameters with equal values (duplicates) are overwritten, same parameters with different values raise QPrmError, unless QPrm.ignore_errors is set to True.
Qpyl.core.qpotential module¶
This module implements several force-field potential energy functions, and functions for calculating distances, angles and dihedral angles, as implemented in Q.
-
Qpyl.core.qpotential.
angle_angle
(ac1, ac2, ac3)[source]¶ Calculate the angle (of the angle).
Parameters: ac2, ac3 (ac1,) – atom coordinates Returns: angle in Degrees Return type: theta (float)
-
Qpyl.core.qpotential.
angle_energy
(theta, fc, theta0)[source]¶ Calculate the angle energy using the harmonic potential.
Parameters: - theta (float) – angle between atoms [degrees]
- fc (float) – force constant [kcal/mol]
- theta0 (float) – equilibrium angle [degrees]
Returns: energy of angle [kcal/mol]
Return type: e_angle (float)
-
Qpyl.core.qpotential.
bond_distance
(ac1, ac2)[source]¶ Calculate the bond distance.
Parameters: ac2 (ac1,) – atom coordinates Returns: distance in Angstrom Return type: r (float)
-
Qpyl.core.qpotential.
bond_energy
(r, fc, r0)[source]¶ Calculate the bond energy using the harmonic potential.
Parameters: - r (float) – distance between atoms [angstrom]
- fc (float) – force constant [kcal/mol]
- r0 (float) – equilibrium distance [angstrom]
Returns: energy of bond [kcal/mol]
Return type: e_bond (float)
-
Qpyl.core.qpotential.
improper_angle
(ac1, ac2, ac3, ac4)[source]¶ Calculate the dihedral angle.
Parameters: ac2, ac3, ac4 (ac1,) – atom coordinates Returns: angle in Degrees Return type: theta (float)
-
Qpyl.core.qpotential.
improper_energy_periodic
(phi, fc, multiplicity, phi0)[source]¶ Calculate the improper energy using the periodic potential.
Using the same potential as torsion_energy(), with npaths==1. E = fc/npaths * [1 + cos(multiplicity*phi - phi0)]
Parameters: - phi (float) – dihedral angle [degrees]
- fc (float) – force constant [kcal/mol]
- multiplicity (float) – multiplicity [/]
- phi0 (float) – phase shift [degrees]
Returns: energy of improper [kcal/mol]
Return type: e_improper (float)
-
Qpyl.core.qpotential.
torsion_angle
(ac1, ac2, ac3, ac4)[source]¶ Calculate the dihedral angle.
Parameters: ac2, ac3, ac4 (ac1,) – atom coordinates Returns: angle in Degrees Return type: theta (float)
-
Qpyl.core.qpotential.
torsion_energy
(phi, fc, multiplicity, npaths, phi0)[source]¶ Calculate the torsion energy using the periodic potential.
One torsion term at a time, using this function: E = fc/npaths * [1 + cos(multiplicity*phi - phi0)]
Parameters: - phi (float) – dihedral angle [degrees]
- fc (float) – force constant [kcal/mol]
- multiplicity (float) – multiplicity [/]
- npaths (float) – division factor [/]
- phi0 (float) – phase shift [degrees]
Returns: energy of torsion [kcal/mol]
Return type: e_torsion (float)
Qpyl.core.qstructure module¶
This module contains the QStruct class for handling Q structure files (PDB, mol2). Additionally, it implements methods for finding and replacing atom placeholders (e.g. $1.N$)
-
class
Qpyl.core.qstructure.
PosVector
(x, y, z)¶ Bases:
tuple
-
x
¶ Alias for field number 0
-
y
¶ Alias for field number 1
-
z
¶ Alias for field number 2
-
-
class
Qpyl.core.qstructure.
QStruct
(filename, filetype, ignore_errors=False)[source]¶ Bases:
object
Class for processing the structure (coordinates)
Parameters: - filename (path to the structure file) –
- (type of structure file (filetype) – ‘pdb’ or ‘mol2’)
- ignore_errors (boolean) – Optional, default is False. If set to True, some non-vital exceptions are logged instead.
In contrast to QLib and QPrm, the ‘read’ methods in this class should not be called since the object should contain data from only one structure file.
The structure data is stored in three lists: atoms, residues, molecules which contain _StructAtom, _StructResidue and _StructMolecule objects.
-
convert_placeholders
(inputstring)[source]¶ Convert atom placeholders ($514.C3$) to indexes.
- Placeholders are a combination of the residue id and
- atom name, encapsulated in $$ - $RESID.ATOM_NAME$
- In addition,there are some special values:
- $LAST.ID$ - id of last atom in the system
Parameters: inputstring (string) – string with placeholders (input file contents) Returns: converted string Return type: outputstring (string)
Qpyl.core.qtopology module¶
This module implements an internal topology builder class QTopology. QTopology creates a mapping between the system’s structure (QStruct), bonding patterns/charges (QLib), and the parameters (Qrm), allowing evaluation of individual topological components of the system.
-
class
Qpyl.core.qtopology.
QTopology
(qlib, qprm, qstruct)[source]¶ Bases:
object
Class for storing topology information.
(mashup of library, parameter and structure data) Contains lists of atoms, bonds, angles, torsions and impropers, along with their parameters.
- The constructor takes in three arguments:
- qlib (qlibrary.QLib object) qprm (qparameter.QPrm object) qstruct (qstructure.QStruct object)
Typical usage:
qlib = qlibrary.QLib(“amber”) qprm = qparameter.QPrm(“amber”) qstruct = qstructure.QStruct() qlib.read_lib(”.../qamber14.lib”) qprm.read_prm(”.../qamber14.prm”) qstruct.read_pdb(”.../14u3.pdb”)
- try:
- qtopo = QTopology(qlib, qprm, qstruct)
- except QTopologyError as e:
- print “Failed to make topology: ” + str(e)
- for bond in qtopo.bonds:
- print “%s: fk %.2f, r0 %.2f, r %.2f, E(r) %.2f” %
- (bond, bond.prm.fc, bond.prm.r0, bond.r, bond.energy)


Loading user organisation...
My organisation (as administrator)
Loading subjects...
Subjects of my organisation
0"
[subjects]="organisationSubjects" [canUpdate]="organisation.isActive" >
0)">
No subjects found for my organisation.
Other subjects
0"
[subjects]="otherSubjects" >
0)">
No
others subjects found.


I'm a data scientist, educator, and technology writer. I love learning the latest tools, understanding everything from the math underlying them to their applications in business, and then teaching others about these tools.
I currently work for Metis, a Data Science Training company, teaching their immersive programs in Chicago and doing Data Science training for our corporate clients. As part of this role I speak frequently about Data Science (especially neural nets) at national conferences such as ODSC and local Meetups. I also invest in and have advised Chicago EdTech startups such as LearnMetrics and GetSet.
Prior to working for Metis, I have five years of experience in Data Science, Data Analytics, and Data Science Education at a variety of companies; read more here.


--- layout: archive title: Zulip Chat Archive permalink: /stream/116395-maths/topic/groups.20acting.20on.20sets.html ---
Did we ever get groups acting on sets? [or even monoids acting on sets?]. The reason I ask is that I just tried to define groups acting on abelian groups and I realised I can't use *
because the action is G -> M -> M
. Has a decision been made about notation for groups acting on anything other than themselves?
Yes, these are in mathlib, and you want to use smul
, I think.
\bullet
Apparently it's \bu
now. And I have to import algebra.module
to get the notation :-) It should be some far more primitive thing. Is the fact that the notation is defined in algebra.module evidence that we don't have groups acting on sets yet?
Did we ever get groups acting on sets? [or even monoids acting on sets?]. The reason I ask is that I just tried to define groups acting on abelian groups and I realised I can't use
*
because the action isG -> M -> M
. Has a decision been made about notation for groups acting on anything other than themselves?
is_group_action
also when I did it myself I used \ci
Last updated: Apr 24 2020 at 19:02 UTC


In this site you will view diffrent quotes and depending on whether you liked or did not like it you will vote for it.You can also add your own Quote to the site.
{{quote.id}}.) {{quote.quotes}}
Quote by: {{quote.author}}
Vote:


The Miller-Rabin test is the most often used primality test. It is based on Fermat's Little Theorem. A very clear explanation of the procedure can be found here (in German). Because of the nature of this test, mistakes are possible: The method may produce a result which is supposedly prime, but is in fact composite. Such numbers are called strong pseudoprimes. The opposite case, that the test recognizes a number as composite, which in reality is prime, doesn't happen.
Link: http://en.wikipedia.org/wiki/Miller-Rabin_primality_test


Note that this will shut down TinyPilot, not the machine to which it is attached.
Your OS and browser capture certain key combinations before they reach TinyPilot (e.g., Ctrl + Alt + Del).
Press these buttons to send the corresponding modifier keys on your next keystroke.


GETOPT
Section: (1)Updated: May 31, 1997
Index Return to Main Contents
NAME
getopt - parse command options (enhanced)SYNOPSIS
getopt optstring parametersgetopt [options] [--] optstring parameters
getopt [options] -o|--options optstring [options] [--] parameters
DESCRIPTION
getopt is used to break up (parse) options in command lines for easy parsing by shell procedures, and to check for legal options. It uses the GNU getopt(3) routines to do this.The parameters getopt is called with can be divided into two parts: options which modify the way getopt will parse (options and -o|--options optstring in the SYNOPSIS), and the parameters which are to be parsed (parameters in the SYNOPSIS). The second part will start at the first non-option parameter that is not an option argument, or after the first occurrence of `--'. If no `-o' or `--options' option is found in the first part, the first parameter of the second part is used as the short options string.
If the environment variable GETOPT_COMPATIBLE is set, or if its first parameter is not an option (does not start with a `-', this is the first format in the SYNOPSIS), getopt will generate output that is compatible with that of other versions of getopt(1). It will still do parameter shuffling and recognize optional arguments (see section COMPATIBILITY for more information).
Traditional implementations of getopt(1) are unable to cope with whitespace and other (shell-specific) special characters in arguments and non-option parameters. To solve this problem, this implementation can generate quoted output which must once again be interpreted by the shell (usually by using the eval command). This has the effect of preserving those characters, but you must call getopt in a way that is no longer compatible with other versions (the second or third format in the SYNOPSIS). To determine whether this enhanced version of getopt(1) is installed, a special test option (-T) can be used.
OPTIONS
- -a, --alternative
- Allow long options to start with a single `-'.
- -h, --help
- Output a small usage guide and exit successfully. No other output is generated.
- -l, --longoptions longopts
- The long (multi-character) options to be recognized. More than one option name may be specified at once, by separating the names with commas. This option may be given more than once, the longopts are cumulative. Each long option name in longopts may be followed by one colon to indicate it has a required argument, and by two colons to indicate it has an optional argument.
- -n, --name progname
- The name that will be used by the getopt(3) routines when it reports errors. Note that errors of getopt(1) are still reported as coming from getopt.
- -o, --options shortopts
- The short (one-character) options to be recognized. If this option is not found, the first parameter of getopt that does not start with a `-' (and is not an option argument) is used as the short options string. Each short option character in shortopts may be followed by one colon to indicate it has a required argument, and by two colons to indicate it has an optional argument. The first character of shortopts may be `+' or `-' to influence the way options are parsed and output is generated (see section SCANNING MODES for details).
- -q, --quiet
- Disable error reporting by getopt(3).
- -Q, --quiet-output
- Do not generate normal output. Errors are still reported by getopt(3), unless you also use -q.
- -s, --shell shell
- Set quoting conventions to those of shell. If no -s argument is found, the BASH conventions are used. Valid arguments are currently `sh' `bash', `csh', and `tcsh'.
- -u, --unquoted
- Do not quote the output. Note that whitespace and special (shell-dependent) characters can cause havoc in this mode (like they do with other getopt(1) implementations).
- -T, --test
- Test if your getopt(1) is this enhanced version or an old version. This generates no output, and sets the error status to 4. Other implementations of getopt(1), and this version if the environment variable GETOPT_COMPATIBLE is set, will return `--' and error status 0.
- -V, --version
- Output version information and exit successfully. No other output is generated.
PARSING
This section specifies the format of the second part of the parameters of getopt (the parameters in the SYNOPSIS). The next section (OUTPUT) describes the output that is generated. These parameters were typically the parameters a shell function was called with. Care must be taken that each parameter the shell function was called with corresponds to exactly one parameter in the parameter list of getopt (see the EXAMPLES). All parsing is done by the GNU getopt(3) routines.The parameters are parsed from left to right. Each parameter is classified as a short option, a long option, an argument to an option, or a non-option parameter.
A simple short option is a `-' followed by a short option character. If the option has a required argument, it may be written directly after the option character or as the next parameter (ie. separated by whitespace on the command line). If the option has an optional argument, it must be written directly after the option character if present.
It is possible to specify several short options after one `-', as long as all (except possibly the last) do not have required or optional arguments.
A long option normally begins with `--' followed by the long option name. If the option has a required argument, it may be written directly after the long option name, separated by `=', or as the next argument (ie. separated by whitespace on the command line). If the option has an optional argument, it must be written directly after the long option name, separated by `=', if present (if you add the `=' but nothing behind it, it is interpreted as if no argument was present; this is a slight bug, see the BUGS). Long options may be abbreviated, as long as the abbreviation is not ambiguous.
Each parameter not starting with a `-', and not a required argument of a previous option, is a non-option parameter. Each parameter after a `--' parameter is always interpreted as a non-option parameter. If the environment variable POSIXLY_CORRECT is set, or if the short option string started with a `+', all remaining parameters are interpreted as non-option parameters as soon as the first non-option parameter is found.
OUTPUT
Output is generated for each element described in the previous section. Output is done in the same order as the elements are specified in the input, except for non-option parameters. Output can be done in compatible (unquoted) mode, or in such way that whitespace and other special characters within arguments and non-option parameters are preserved (see QUOTING). When the output is processed in the shell script, it will seem to be composed of distinct elements that can be processed one by one (by using the shift command in most shell languages). This is imperfect in unquoted mode, as elements can be split at unexpected places if they contain whitespace or special characters.If there are problems parsing the parameters, for example because a required argument is not found or an option is not recognized, an error will be reported on stderr, there will be no output for the offending element, and a non-zero error status is returned.
For a short option, a single `-' and the option character are generated as one parameter. If the option has an argument, the next parameter will be the argument. If the option takes an optional argument, but none was found, the next parameter will be generated but be empty in quoting mode, but no second parameter will be generated in unquoted (compatible) mode. Note that many other getopt(1) implementations do not support optional arguments.
If several short options were specified after a single `-', each will be present in the output as a separate parameter.
For a long option, `--' and the full option name are generated as one parameter. This is done regardless whether the option was abbreviated or specified with a single `-' in the input. Arguments are handled as with short options.
Normally, no non-option parameters output is generated until all options and their arguments have been generated. Then `--' is generated as a single parameter, and after it the non-option parameters in the order they were found, each as a separate parameter. Only if the first character of the short options string was a `-', non-option parameter output is generated at the place they are found in the input (this is not supported if the first format of the SYNOPSIS is used; in that case all preceding occurrences of `-' and `+' are ignored).
QUOTING
In compatible mode, whitespace or 'special' characters in arguments or non-option parameters are not handled correctly. As the output is fed to the shell script, the script does not know how it is supposed to break the output into separate parameters. To circumvent this problem, this implementation offers quoting. The idea is that output is generated with quotes around each parameter. When this output is once again fed to the shell (usually by a shell eval command), it is split correctly into separate parameters.Quoting is not enabled if the environment variable GETOPT_COMPATIBLE is set, if the first form of the SYNOPSIS is used, or if the option `-u' is found.
Different shells use different quoting conventions. You can use the `-s' option to select the shell you are using. The following shells are currently supported: `sh', `bash', `csh' and `tcsh'. Actually, only two `flavors' are distinguished: sh-like quoting conventions and csh-like quoting conventions. Chances are that if you use another shell script language, one of these flavors can still be used.
SCANNING MODES
The first character of the short options string may be a `-' or a `+' to indicate a special scanning mode. If the first calling form in the SYNOPSIS is used they are ignored; the environment variable POSIXLY_CORRECT is still examined, though.If the first character is `+', or if the environment variable POSIXLY_CORRECT is set, parsing stops as soon as the first non-option parameter (ie. a parameter that does not start with a `-') is found that is not an option argument. The remaining parameters are all interpreted as non-option parameters.
If the first character is a `-', non-option parameters are outputted at the place where they are found; in normal operation, they are all collected at the end of output after a `--' parameter has been generated. Note that this `--' parameter is still generated, but it will always be the last parameter in this mode.
COMPATIBILITY
This version of getopt(1) is written to be as compatible as possible to other versions. Usually you can just replace them with this version without any modifications, and with some advantages.If the first character of the first parameter of getopt is not a `-', getopt goes into compatibility mode. It will interpret its first parameter as the string of short options, and all other arguments will be parsed. It will still do parameter shuffling (ie. all non-option parameters are outputted at the end), unless the environment variable POSIXLY_CORRECT is set.
The environment variable GETOPT_COMPATIBLE forces getopt into compatibility mode. Setting both this environment variable and POSIXLY_CORRECT offers 100% compatibility for `difficult' programs. Usually, though, neither is needed.
In compatibility mode, leading `-' and `+' characters in the short options string are ignored.
RETURN CODES
getopt returns error code 0 for successful parsing, 1 if getopt(3) returns errors, 2 if it does not understand its own parameters, 3 if an internal error occurs like out-of-memory, and 4 if it is called with -T.EXAMPLES
Example scripts for (ba)sh and (t)csh are provided with the getopt(1) distribution, and are optionally installed in /usr/share/getopt.ENVIRONMENT
- POSIXLY_CORRECT
- This environment variable is examined by the getopt(3) routines. If it is set, parsing stops as soon as a parameter is found that is not an option or an option argument. All remaining parameters are also interpreted as non-option parameters, regardless whether they start with a `-'.
- GETOPT_COMPATIBLE
- Forces getopt to use the first calling format as specified in the SYNOPSIS.
BUGS
getopt(3) can parse long options with optional arguments that are given an empty optional argument (but can not do this for short options). This getopt(1) treats optional arguments that are empty as if they were not present.The syntax if you do not want any short option variables at all is not very intuitive (you have to set them explicitly to the empty string).
AUTHOR
Frodo Looijaard<EMAIL_ADDRESS>ALSO
getopt(3), bash(1), tcsh(1).AVAILABILITY
The getopt command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- PARSING
- OUTPUT
- QUOTING
- SCANNING MODES
- COMPATIBILITY
- RETURN CODES
- EXAMPLES
- ENVIRONMENT
- BUGS
- AUTHOR
- SEE ALSO
- AVAILABILITY
This document was created by man2html, using the manual pages.
Time: 05:29:04 GMT, December 24, 2015


"ErrorBoundary constructor", "ErrorBoundary componentWillMount", "ErrorBoundary render success", "RetryErrorBoundary constructor", "RetryErrorBoundary componentWillMount", "RetryErrorBoundary render", "BrokenRender constructor", "BrokenRender componentWillMount", "BrokenRender render [!]", // In Fiber, failed error boundaries render null before attempting to recover "RetryErrorBoundary componentDidMount", "RetryErrorBoundary componentDidCatch [!]", "ErrorBoundary componentDidMount", // Retry "RetryErrorBoundary render", "BrokenRender constructor", "BrokenRender componentWillMount", "BrokenRender render [!]", // This time, the error propagates to the higher boundary "RetryErrorBoundary componentWillUnmount", "ErrorBoundary componentDidCatch", // Render the error "ErrorBoundary componentWillUpdate", "ErrorBoundary render error", "ErrorBoundary componentDidUpdate"


Signup Here
Join The SV Fitness Team
*WORK IN PROGRESS*
Email address
Password
Confirm Password
Age
18
19
20
21
22
About You


{% extends 'base.html'%} {% import 'bootstrap/wtf.html' as wtf %} {% block styles%} {{ super() }} {% endblock %} {% block content %}
{{ comment.comment }}
Are you sure you want to delete?
No Comments found for this post
Comments for {{ blog.title }}
No Comments found for this post


findmyfluffy.findmyfluffy
Classes
AddCat
AddFoundEntryServlet
AddLostEntryServlet
Cat
DatastoreInfo
FoundCatAdder
LostCatAdder
MatchFound
MatchLost
MemCacheInfo
Serve
SubmitFound
SubmitLost
UploadFound
UploadLost


— Brian Moeskau (@bmoeskau)
Thanks to our venue sponsor:
Thanks to our food sponsor:
Last version check — March 23, 2016:
| 49 | 36 | 45 | 14 14291 |
9.1 |
As of April 27, 2016:
| 49 50 |
36 | 45 46 |
14 14291 |
9.1 |
Released April 13
<link rel='preload'>
Released April 26
A free, open project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs.
That leaves Safari as the lone significant holdout
grunt-cli
now bundled locally by defaultdocument.createElement
instead of innerHTML
They also plan to add an RFC process (also inspired by Ember RFCs)
Open source CI / deployment automation
Attend the virtual launch party on May 4th
Realtime node.js deployments
package.json
becomes a deployable serviceExtends the reach of React Native apps to a new market of 270 million active Windows 10 devices
UWP = Universal Windows Platform
Announced April 13th at the F8 conference
Strange, but true!
Angular 2 core + react-native-renderer
docs-beta.stackexchange.com (currently requires beta access)
Don't just shorten your URL, make it suspicious and frightening
For example:
http://www.5z8.info/hot-older-goats.mov_n2x0pm
_cats-being-dropped-into-the-sea
People love two things: failed Microsoft technologies and obscure Javascript libraries. Naturally, we decided to combine the two.
All things DevOps related
Explore what's new in open source languages, tools, and techniques
It's a 2-day training in .Net, HTML5, JavaScript, EcmaScript, Web API and REST, Sharepoint, and other awesome technologies
/
#


@(implicit isPlay24: Boolean) @main("Documentation", tab = "docs") {
This page explains each component in more details.
There are 4 different field constructors you can use. You only need to declare any of them implicitly on top of your template. Then every input will take it by default.
@@implicitFieldConstructor = @@{ b3.vertical.fieldConstructor }
Or simply:
@@import b3.vertical.fieldConstructor
You have to specify its column widths for the form-group.
form-group
@@implicitFieldConstructor = @@{ b3.horizontal.fieldConstructor("col-md-2", "col-md-10") }
@@implicitFieldConstructor = @@{ b3.inline.fieldConstructor }
Or:
@@import b3.inline.fieldConstructor
This field constructor renders the input helpers directly. It is useful for those cases you need the input without its corresponding form-group. However, although it is used for specific cases, you can also declare it as the default field constructor within a template.
@@import b3.clear.fieldConstructor
args
For every component there is a list of arguments you can add and they will be put within the corresponding input tag as normal HTML. However it will only happen with those arguments without a prefixed slash. The slashed arguments are used to complement the corresponding form-group or to parametrize its behaviour.
For example, the following component has the argument placeholder that will be added to the input text tag. The _label argument set the label for the form-group and the _showConstraints one specifies if the constraints should be shown.
placeholder
_label
_showConstraints
@@b3.text( fooForm("foo"), '_label -> "Constraints", '_showConstraints -> true, 'placeholder -> "A simple text showing its constraints..." )
The previous example outputs the HTML:

 Constraints <input type="text" id="foo" name="foo" value="" class="form-control" placeholder="A simple text showing its constraints..."> Maximum length: 10

The boolean arguments are simply that, booleans. Let's see an example for the disabled attribute. Look all of these different codes:
disabled
<input type="text" name="foo" disabled> <input type="text" name="foo" disabled="true"> <input type="text" name="foo" disabled="false"> <input type="text" name="foo" disabled="blah">
And all of them are equivalents... But don't worry, every false argument will be automatically removed. So you can feel free to do something like:
false
@@b3.text( fooForm("foo"), '_label -> "A maybe disabled text", 'disabled -> maybeTrueFunction(...) )
The b3.form takes a Call object and a list of arguments. It also adds the role="form" attribute by default.
b3.form
Call
role="form"
The are two additional form functions for the horizontal and inline versions that add their corresponding form-horizontal and form-inline classes. But if you want to add custom class attribute you will also have to add them manually.
form-horizontal
form-inline
@@b3.form(routes.Application.handleRequest, 'class -> "form-horizontal another-class") { ... } @@b3.horizontal.form(routes.Application.handleRequest) { ... } // the class form-horizontal is added @@b3.inline.form(routes.Application.handleRequest, 'id -> "form_id") { ... } // the class form-inline is added
FieldConstructor
Every input helper will use the default FieldConstructor (the implicit one), unless you specify another. To do this you can use the formWithFC helper. There is one for each type of form. Here is an example of how to add an inline form within a view with a vertical form as default.
formWithFC
@@import b3.vertical.fieldConstructor @@b3.form(routes.Application.handleRequest) { // vertical form as default @@b3.text( fooForm("foo"), '_label -> "Input Text" ) ... } @@b3.inline.formWithFC(routes.Application.handleRequest) { case (ifc, lang) // an inline form @@b3.text( fooForm("foo"), '_label -> "Input Text" )(ifc, lang) // you have to insert them explicitly ... }
There are 4 different options to insert each type of form. Note that there is also one for a clear FieldConstructor (it simply outputs the input helper without any more). So we have:
@@b3.vertical.formWithFC(routes.Application.handleRequest) { case (vfc, lang) => ... } @@b3.horizontal.formWithFC(routes.Application.handleRequest, "col-md-2", "col-md-10") { case (hfc, lang) => ... } @@b3.inline.formWithFC(routes.Application.handleRequest) { case (ifc, lang) => ... } @@b3.clear.formWithFC(routes.Application.handleRequest) { case (cfc, lang) => ... }
If you would need to specify a different FieldConstructor within a form, you can do:
@@import b3.vertical.fieldConstructor @@horizontalFC = @@{ b3.horizontal.fieldConstructor("col-md-2", "col-md-10") } @@b3.form(routes.Application.handleRequest) { // vertical form as default @@b3.text( fooForm("foo"), '_label -> "Vertical input text" ) @@b3.text( fooForm("bar"), '_label -> "Horizontal input text" )(horizontalFC, implicitly[Lang]) ... }
@@import b3.vertical.fieldConstructor @@b3.form(routes.Application.handleRequest) { // vertical form as default @@b3.text( fooForm("foo"), '_label -> "Vertical input text" ) ... // an inline inner section @@defining(b3.inline.fieldConstructor, implicitly[Lang]) { case (ifc, lang) => @@b3.text( fooForm("bar"), '_label -> "Inline input text" )(ifc, lang) ... } ... }
But remember that horizontal and inline controls need to be inside their corresponding .form-horizontal and .form-inline to be rendered correctly. So you may need to wrap them with a div with these classes.
.form-horizontal
.form-inline
div
To understand them better, let's see before the vertical FieldConstructor:

 @@elements.label(elements.lang) @@elements.input @@elements.errors(elements.lang).filter(_ != null).map { error => @@error } @@if(elements.args.exists(_ == ('_showConstraints, true))) { @@elements.infos(elements.lang).map { info => @@info } } @@elements.args.get('_help).map { help => @@help }

_id
_class
_help
_showLabel
readonly
Both the disabled and readonly attributes for an input prevent the user from modify it. However, the disabled attribute means this input will NOT be sent within the POST request, whereas the readonly one means it will.
Nevertheless, for checkbox, radio and select tags it doesn't happen. To support the readonly attribute for these tags, the corresponding helpers have been adapted to behave as would be expected. To do that, when the readonly attribute appears the helper will:
checkbox
radio
select
<input type="hidden">
checkbox-group
radio-group
select-group
You can see an example in the Readonly Demo.
b3.inputType
It renders a simple input with a specific type attribute and it adds class="form-control" by default.
class="form-control"
@@b3.inputType( "text", fooForm("name"), '_label -> "Name", 'placeholder -> "John Doe" ) @@b3.inputType( "email", fooForm("email"), '_label -> "Email", 'placeholder -> "example@@mail.com" ) @@b3.inputType( "password", fooForm("password"), '_label -> "Password", '_help -> "With at least 8 characters" )
b3.text
It is a short version of b3.inputType for type="text".
type="text"
@@b3.text( fooForm("name"), '_label -> "Name", 'placeholder -> "John Doe" )
b3.password
It is a short version of b3.inputType for type="password".
type="password"
For security reasons, this helper doesn't display the possible value the field could have (for example when the form is reloaded after a validation failure).
@@b3.password( fooForm("password"), '_label -> "Password", '_help -> "With at least 8 characters" )
b3.file
It is a short version of b3.inputType for type="file".
type="file"
@@b3.file( fooForm("file"), '_label -> "File" )
b3.textarea
It renders a textarea and it adds class="form-control" by default.
@@b3.textarea( fooForm("foo"), '_label -> "Textarea", 'row -> 3 )
b3.checkbox
It renders a checkbox. It have always the attribute value set to true. So it only supports boolean bindings. Then, the 'value argument determines its default value (true or false).
'value
The special '_text argument lets you put a text after the checkbox.
'_text
It supports readonly attribute adding an additional disabled one and a <input type="hidden">.
<input type="hidden">
@@b3.checkbox( fooForm("foo"), '_label -> None, '_text -> "Remember me" ) // always checked (even if the form has been filled with a false) @@b3.checkbox( fooForm("foo"), '_label -> None, '_text -> "Remember me", 'checked -> true ) // checked by default (if the form is filled, this value will be taken) @@b3.checkbox( fooForm("foo"), '_label -> None, '_text -> "Remember me", 'value -> true ) // disabled -> it will NOT be sent within the POST request @@b3.checkbox( fooForm("foo"), '_label -> None, '_text -> "Remember me", 'disabled -> true ) // readonly -> it will be sent within the POST request @@b3.checkbox( fooForm("foo"), '_label -> None, '_text -> "Remember me", 'readonly -> true )
Note you can use any value for the _text argument.
_text
@@b3.checkbox( fooForm("foo"), '_label -> None, '_text -> Html("Do you want a beer? ") )
b3.radio
It renders a radio. It supports readonly attribute adding an additional disabled one and a <input type="hidden">.
It has an additional special _inline argument to make it an inline radio (for vertical and horizontal forms).
_inline
@@opts = @@{ Seq("M"->"Male","F"->"Female") } @@b3.radio( fooForm("foo"), options = opts, '_label -> "Radio Group" ) // an inline radio within a vertical or horizontal form @@b3.radio( fooForm("foo"), options = opts, '_label -> "Radio Group", '_inline -> true ) // with value "F" by default (if the form is filled, this value will be taken) @@b3.radio( fooForm("foo"), options = opts, '_label -> "Radio Group", 'value -> "F" ) // disabled -> it will NOT be sent within the POST request @@b3.radio( fooForm("foo"), options = opts, '_label -> "Radio Group", 'disabled -> true ) // readonly -> it will be sent within the POST request @@b3.radio( fooForm("foo"), options = opts, '_label -> "Radio Group", 'readonly -> true )
Note you can use any value for the options argument.
options
@@b3.radio( fooForm("foo"), options = Seq("B" -> Html("Beer "), "C" -> Html("Coffee ")), '_label -> "What do you prefer?" )
b3.select
It renders a select. It supports readonly attribute adding an additional disabled one and a <input type="hidden">.
@@fruits = @@{ Seq("A"->"Apples","P"->"Pears","B"->"Bananas") } @@b3.select( fooForm("foo"), options = fruits, '_label -> "Select" ) // with value "No" by default (if the form is filled, this value will be taken) @@b3.select( fooForm("foo"), options = fruits, '_label -> "Select", 'value -> "No" ) // disabled -> it will NOT be sent within the POST request @@b3.select( fooForm("foo"), options = fruits, '_label -> "Select", 'disabled -> true ) // readonly -> it will be sent within the POST request @@b3.select( fooForm("foo"), options = fruits, '_label -> "Select", 'readonly -> true )
For a multiple select.
multiple select
@@fruits = @@{ Seq("A"->"Apples","P"->"Pears","B"->"Bananas") } @@b3.select( fooForm("foo"), options = fruits, '_label -> "Fruits", 'multiple -> true ) // with value "A" and "B" by default (if the form is filled, this value will be taken) // it is a string with every value separated by commas @@b3.select( fooForm("foo"), options = fruits, '_label -> "Fruits", 'multiple -> true, 'value -> "A,B" ) // disabled -> it will NOT be sent within the POST request @@b3.select( fooForm("foo"), options = fruits, '_label -> "Fruits", 'multiple -> true, 'disabled -> true ) // readonly -> it will be sent within the POST request @@b3.select( fooForm("foo"), options = fruits, '_label -> "Fruits", 'multiple -> true, 'readonly -> true )
b3.hidden
It simply renders a hidden input.
@@b3.hidden("fooName", "fooValue", 'fooAttr -> "fooAttrValue")
Renders to:
<input type="hidden" name="fooName" value="fooValue" fooAttr="fooAttrValue">
Important note: the new HTML5 input types are not fully supported for web browsers. Those not supported by old web browsers, will behave as input type text.
b3.color
It is a short version of b3.inputType for type="color".
type="color"
@@b3.color( fooForm("color"), '_label -> "Color" )
b3.date
It is a short version of b3.inputType for type="date".
type="date"
@@b3.date( fooForm("date"), '_label -> "Date" )
b3.datetime
It is a short version of b3.inputType for type="datetime".
type="datetime"
@@b3.datetime( fooForm("datetime"), '_label -> "Datetime" )
b3.datetimeLocal
It is a short version of b3.inputType for type="datetime-local".
type="datetime-local"
@@b3.datetimeLocal( fooForm("datetimeLocal"), '_label -> "Datetime-Local" )
b3.email
It is a short version of b3.inputType for type="email".
type="email"
@@b3.email( fooForm("email"), '_label -> "Email", 'placeholder -> "example@@mail.com" )
b3.month
It is a short version of b3.inputType for type="month".
type="month"
@@b3.month( fooForm("month"), '_label -> "Month" )
b3.number
It is a short version of b3.inputType for type="number".
type="number"
@@b3.number( fooForm("number"), '_label -> "Number", 'min -> 0, 'max -> 50, 'step -> 5 )
b3.range
It is a short version of b3.inputType for type="range".
type="range"
@@b3.range( fooForm("range"), '_label -> "Range", 'min -> 0, 'max -> 50 )
b3.search
It is a short version of b3.inputType for type="search".
type="search"
@@b3.search( fooForm("search"), '_label -> "Search" )
b3.tel
It is a short version of b3.inputType for type="tel".
type="tel"
@@b3.tel( fooForm("tel"), '_label -> "Telephone" )
b3.time
It is a short version of b3.inputType for type="time".
type="time"
@@b3.time( fooForm("time"), '_label -> "Time" )
b3.url
It is a short version of b3.inputType for type="url".
type="url"
@@b3.url( fooForm("url"), '_label -> "URL" )
b3.week
It is a short version of b3.inputType for type="week".
type="week"
@@b3.week( fooForm("week"), '_label -> "Week" )
b3.static
It renders a static control to place within your form. It takes a HTML as parameter, so you can render whatever you want. Actually, it is like a wrapper for a static HTML. There are two versions: one for vertical forms and another one for horizontal forms. There is no version for inline forms due to you can simply write whatever you want without any particular helper.
HTML
b3.vertical.static
This is a link
@@b3.vertical.static("Static HTML"){  This is a link }
b3.horizontal.static
And for horizontal forms, it takes implicitly the horizontal field constructor.
@@b3.horizontal.static("Static HTML"){  This is a link }
b3.submit
It renders a submit button to place within your form. It takes a HTML as parameter, so you can render whatever you want.
@@b3.submit('class -> "btn btn-default"){  Sign in }
b3.horizontal.submit
There is a version for horizontal forms that takes implicitly the horizontal field constructor.
@@b3.horizontal.submit('class -> "btn btn-default"){ ... }
b3.reset
It renders a reset button to place within your form. It takes a HTML as parameter, so you can render whatever you want.
@@b3.reset('class -> "btn btn-default"){  Reset }
b3.horizontal.reset
@@b3.horizontal.reset('class -> "btn btn-default"){ ... }
b3.actions
It renders whatever you want within a form-group div.
@@b3.actions { <button type="submit" class="btn btn-primary">  Save changes</button>   Cancel }
b3.horizontal.actions
@@b3.horizontal.actions { ... }
b3.inputWrapped
This is the same as b3.inputType but specifying a custom wrapper for the input tag. It is useful for input groups and inputs with validation states and feedback icons.
@@b3.inputWrapped( "email", fooForm("email"), '_label -> "Email", 'placeholder -> "example@@mail.com" ) { input =>
 @@@@ @@input
 <button type="button" class="btn btn-default dropdown-toggle" data-toggle="dropdown">Action </button>

Action

Another action

Something else here

Separated link

 } @@b3.inputWrapped( "password", fooForm("password"), '_label -> "Password", '_class -> "has-success has-feedback" ){ input => @@input  }
It is also very useful for developing your own complex helpers based on this b3.inputWrapped. For example, imagine you use in several places an input-group with glyphicons. Then you could create a new helper as:
input-group
glyphicons
@@(inputType: String, icon: String, field: play.api.data.Field, args: (Symbol,Any)*)(implicit handler: helper.FieldConstructor, lang: play.api.i18n.Lang) @@b3.inputWrapped( inputType, field, b3.Args.withDefault(args, '_label -> None):_* ) { input =>
  @@input
 }
b3.multifield
Sometimes you may need two or more fields within the same line in a horizontal or vertical form (for a set of checkboxes, a date range, ...).
The helper b3.multifield tries to:
To know how it works and how to use it go the the Multifield section.


| future_promise_queue {promises} | R Documentation |
future_promise_queue() future_promise( expr = NULL, envir = parent.frame(), substitute = TRUE, globals = TRUE, packages = NULL, ..., queue = future_promise_queue() )
expr |
An R expression. While the |
envir |
The environment from where global objects should be identified. |
substitute |
If TRUE, argument |
globals |
(optional) a logical, a character vector, or a named list
to control how globals are handled.
For details, see section 'Globals used by future expressions'
in the help for |
packages |
(optional) a character vector specifying packages to be attached in the R environment evaluating the future. |
... |
extra parameters provided to |
queue |
A queue that is used to schedule work to be done using |
When submitting future work, future (by design) will block the main R session until a worker becomes available.
This occurs when there is more submitted future work than there are available future workers.
To counter this situation, we can create a promise to execute work using future (using future_promise()
) and only begin the work if a future worker is available.
Using future_promise()
is recommended when ever a continuous runtime is used, such as with plumber or shiny.
For more details and examples, please see the vignette("future_promise", "promises")
vignette().
Unlike [future::future()],
future_promise()returns a [promise()] object that will eventually resolve the \pkg{future}
expr'.
future_promise_queue
: Default future_promise()
work queue to use. This function returns a WorkQueue that is cached per R session.
future_promise
: Creates a promise()
that will execute the expr
using future::future()
.
# Relative start time start <- Sys.time() # Helper to force two `future` workers with_two_workers <- function(expr) { if (!require("future")) { message("`future` not installed") return() } old_plan <- future::plan(future::multisession(workers = 2)) on.exit({future::plan(old_plan)}, add = TRUE) start <<- Sys.time() force(expr) while(!later::loop_empty()) {Sys.sleep(0.1); later::run_now()} invisible() } # Print a status message. Ex: `"PID: XXX; 2.5s promise done"` print_msg <- function(pid, msg) { message( "PID: ", pid, "; ", round(difftime(Sys.time(), start, units = "secs"), digits = 1), "s " , msg ) } # `"promise done"` will appear after four workers are done and the main R session is not blocked # The important thing to note is the first four times will be roughly the same with_two_workers({ promise_resolve(Sys.getpid()) %...>% print_msg("promise done") for (i in 1:6) future::future({Sys.sleep(1); Sys.getpid()}) %...>% print_msg("future done") }) { #> PID: XXX; 2.5s promise done #> PID: YYY; 2.6s future done #> PID: ZZZ; 2.6s future done #> PID: YYY; 2.6s future done #> PID: ZZZ; 2.6s future done #> PID: YYY; 3.4s future done #> PID: ZZZ; 3.6s future done } # `"promise done"` will almost immediately, before any workers have completed # The first two `"future done"` comments appear earlier the example above with_two_workers({ promise_resolve(Sys.getpid()) %...>% print_msg("promise") for (i in 1:6) future_promise({Sys.sleep(1); Sys.getpid()}) %...>% print_msg("future done") }) { #> PID: XXX; 0.2s promise done #> PID: YYY; 1.3s future done #> PID: ZZZ; 1.4s future done #> PID: YYY; 2.5s future done #> PID: ZZZ; 2.6s future done #> PID: YYY; 3.4s future done #> PID: ZZZ; 3.6s future done }


?II
M
?
?
A
vv
CM
\
A
5
6
7
ƒ
\
9
1
n
dm
Im
copyright
reserved
botanical
Garden
<0>
IMAGED
U.S.
National
Herbarium
Ñ
Examined
for
the
flora
of
St.
John
4c>i
ST.
JOHN
FLORA
The
New
York
Botanical
Garden
No.
1892
OLEA
Jasmimum
multiflorum
(Burm.
f.)
Andr.
ST.
JOHN,
U.S.
Virgin
Islands.
Coral
Bay
Quarter,
Bordeaux
Mountain
Road.
Elev.
00300m.
Sunny
roadside.
Climbing
shrub,
4
to
5
m.
long.
Flowers
white
and
fragrant.
BOTANICAL
GARDE**
NEW
YORK
BOTANICAL
GARDEN
00843176
P.
Acevedo-Rodriguez,
A.
Reilly
August
21,
1987
00843176
Legend -
Level of confidence that token is an accurately-transcribed word
extremely low
very low
low
undetermined
medium
high
very high


How to Run A Daily Scrum That Teams Love Proven techniques to turn your daily scrum into a meeting people love in 2 months.
Liftoff Facilitation Guide Get the guide for how to launch highly successful teams that is used all over the country
Scrum Event Breakdown Know the essential elements for each of the scrum meetings. Great for transformation offices and new Scrum Masters.


Delays on the front- or back-end make it difficult for dependent teams to complete their work efficiently. Be dummy can alleviate those delays in the development process.
Front-end developers can create a mock routes to simulate each endpoint and its corresponding environment in a Be Dummy Model page, before sending the actual request. Developers can view potential responses, without spinning up a back end.
Creating a mock example during the earliest phase of API development fosters clear communication among team members and aligns their expectations. As a result, all teams in the development process can work in parallel; and dependent teams experience fewer delays.


Instagram OS Loader V3.11
Please select the operation system to start:
User ↑ and ↓ to move the highlight to your choice. Press Enter to choose.
Seconds until highlighted choice will be started automatically: 30
Instagram OS V3.11 Checking Hardware ...


The Size object is used to describe the size of something, through its width and height properties.
Example — Create a size that is 10pt wide and 5pt high
var size = new Size(10, 5); console.log(size.width); // 10 console.log(size.height); // 5
Creates a Size object with the given width and height values.
Example — Create a size that is 10pt wide and 5pt high
var size = new Size(10, 5); console.log(size.width); // 10 console.log(size.height); // 5
Creates a Size object using the numbers in the given array as dimensions.
Example — Creating a size of width: 320, height: 240 using an array of numbers:
var array = [320, 240]; var size = new Size(array); console.log(size.width); // 320 console.log(size.height); // 240
Creates a Size object using the properties in the given object.
Example — Creating a size of width: 10, height: 20 using an object literal:
var size = new Size({ width: 10, height: 20 }); console.log(size.width); // 10 console.log(size.height); // 20
Creates a Size object using the coordinates of the given Size object.
Checks whether the width and height of the size are equal to those of the supplied size.
Example
var size = new Size(5, 10); console.log(size == new Size(5, 10)); // true console.log(size == new Size(1, 1)); // false console.log(size != new Size(1, 1)); // true
Returns the addition of the supplied value to the width and height of the size as a new size. The object itself is not modified!
Example
var size = new Size(5, 10); var result = size + 20; console.log(result); // {width: 25, height: 30}
Returns the addition of the width and height of the supplied size to the size as a new size. The object itself is not modified!
Example
var size1 = new Size(5, 10); var size2 = new Size(10, 20); var result = size1 + size2; console.log(result); // {width: 15, height: 30}
Returns the subtraction of the supplied value from the width and height of the size as a new size. The object itself is not modified!
The object itself is not modified!
Example
var size = new Size(10, 20); var result = size - 5; console.log(result); // {width: 5, height: 15}
Returns the subtraction of the width and height of the supplied size from the size as a new size. The object itself is not modified!
Example
var firstSize = new Size(10, 20); var secondSize = new Size(5, 5); var result = firstSize - secondSize; console.log(result); // {width: 5, height: 15}
Returns the multiplication of the supplied value with the width and height of the size as a new size. The object itself is not modified!
Example
var size = new Size(10, 20); var result = size * 2; console.log(result); // {width: 20, height: 40}
Returns the multiplication of the width and height of the supplied size with the size as a new size. The object itself is not modified!
Example
var firstSize = new Size(5, 10); var secondSize = new Size(4, 2); var result = firstSize * secondSize; console.log(result); // {width: 20, height: 20}
Returns the division of the supplied value by the width and height of the size as a new size. The object itself is not modified!
Example
var size = new Size(10, 20); var result = size / 2; console.log(result); // {width: 5, height: 10}
Returns the division of the width and height of the supplied size by the size as a new size. The object itself is not modified!
Example
var firstSize = new Size(8, 10); var secondSize = new Size(2, 5); var result = firstSize / secondSize; console.log(result); // {width: 4, height: 2}
The modulo operator returns the integer remainders of dividing the size by the supplied value as a new size.
Example
var size = new Size(12, 6); console.log(size % 5); // {width: 2, height: 1}
The modulo operator returns the integer remainders of dividing the size by the supplied size as a new size.
Example
var size = new Size(12, 6); console.log(size % new Size(5, 2)); // {width: 2, height: 0}
Checks if this size has both the width and height set to 0.
Checks if the width or the height of the size are NaN.
Copyright © 2011 Jürg Lehni & Jonathan Puckey. All Rights Reserved.


We know that lasers are very accurate instruments and emit a very precise wavelength and hence are in an array of precision applications including bloodless surgery, eye surgery and fingerprint detection. So why do we see random light/dark spots when we shine a laser on anything? Shouldn’t it all be the same color since lasers are deterministic (read: not random)? To answer that question1, we need to delve into optical theory.
Coherent optical systems are simply defined to be deterministic systems. That’s a big definition, so let’s break it into pieces. Coherent systems are where you know the wavelength and phase of every ray. Lasers are very coherent (one wavelength, same phase) while sunlight is not coherent (many wavelength, different phases).
Deterministic is just a way of saying everything about the system is known and there’s no randomness. Sunlight is not deterministic because there are many random processes. Photons are randomly generated and there are many wavelengths. Sunspots are one example of the randomness present in sunlight.
But if lasers are coherent and deterministic, why do we see speckle (read: bright and dark spots) when we see a laser spot? The speckle is random; we can’t predict where every dark spot will be. The randomness of this laser spot and the fact that lasers are deterministic throws a helluva question at us. It turns out what we see the laser on is important, but let’s look at the math and physics behind it.
Coherent optical systems have a very special property. Their impulse response (read: reaction to a standardized input) in the frequency domain is just the pupil function. For those familiar with the parlance and having $f_x$ be a spatial frequency as opposed to a time frequency,
When I saw this derived2, I thought “holy (expletive).” If you just want to only pass high frequency spatial content (read: edges), then all that’s required it to not let light through the center of the lens.
Since this system is linear, we can think of our output as bunch of impulse responses shifted in space and scaled by the corresponding amount. This is the definition of convolution and only works because this is a linear and space invariant system.
To find our impulse response in the space domain, $h\left( x, y\right) $, we have to take the Fourier transform (aka FFT) of our pupil. Since our pupil function is symmetric, the inverse Fourier transform and forward Fourier transform are equivalent.
1 2 3 4 5 6 7 |
|
Through the angular plane wave spectrum, this impulse response can be viewed as a series plane waves coming in at different angles, shown in the figure below.
What angles can a wave be thought of as? The frequency content and angles turn out to be related, since two planes waves of a constant frequency adding together can have a change in frequency depending on what angle they’re at, which makes intuitive sense. Or, our spatial plane wave $U(x,y)$ can be represented by the Fourier transform:
The wall which the laser is shining on is not smooth and perfectly flat. It’s rough, and the distance adds a phase difference between two waves3. Through the Drunkard’s Walk and the angular plane wave spectrum, if we could obtain every angle, the laser spot wouldn’t have any speckle. Our eyes are finite in size, so we can’t obtain every angle or frequency.
Because the wall gives the wave some random phase, we can represent the spot we see by a 2D convolution with a random phase and the impulse response. This convolution is just saying that every spot gives the same response multiplied by some random phase, added together for every point.
1 2 3 4 5 |
|
The laser spot y
shows some speckle! The speckle varies with how large we
make d
(really delta
but that’s long); if we include more frequencies and
more of the impulse response, the dots get smaller. To see this, if you hold a
pinhole up to your eye, the speckles will appear larger.
An intuitive way to think about this involves the impulse response. The impulse response changes on with the distance and so does the phase. Certain areas add up to 0 while others add up to 1. There’s a whole probability density function that goes with that, but that’s goes further into optical and statistical theory.
tl;dr: the roughness of the walls add uncertainty in phase and hence speckle
-
This does rely on assumptions by Goodman. Refer to Eqn. 6-20 for more detail (and thanks Mint!)↩
-
reddit commenter delmar15 pointed out that there’s also phase due to the glass it’s shining through (and many other effects). Statisitcal optics covers that in much more detail.↩


{% extends "base.html" %} {% block title %}Login{% endblock %} {% block content %} Log in {% csrf_token %} {{ form.as_p }} Login Need an account? Talk to an officer! {% endblock %} {# vim: set et ts=2 sw=2 tw=200: #}
Need an account? Talk to an officer!


Welcome to BlazeDS!
The BlazeDS applications are available at the following URLs:
Console Application
Samples Application
Template Application
Spring Samples Application
Spring Template Application


What’s this?
MQTT is a light weight messaging protocol based on a publish-subscribe metaphore. It is widely for example Internet of Things and telecom sectors.
MQTT has features such as guaranteed delivery of messages, which makes it very useful for communicating between Sense and both up- and downstream source/destination systems.
Butler can be configured to forward events from Sense (reload task failures, aborted reload tasks, user session start/stop etc) as MQTT messages.
Butler’s REST API also has an endpoint that makes it possible to send MQTT messages from the Sense load script.
Settings in config file
The settings are of two kinds:
- Defining what MQTT broker/server to connect to
- What MQTT topics should be used when forwarding Qlik Sense events to MQTT.
---
Butler:
...
...
mqttConfig:
enable: false # Should Qlik Sense events be forwarded as MQTT messages?
brokerHost: <FQDN or IP of MQTT server>
brokerPort: 1883
taskFailureSendFull: true
taskAbortedSendFull: true
subscriptionRootTopic: qliksense/# # Topic that Butler will subscribe to
taskStartTopic: qliksense/start_task # Topic for incoming messages used to start Sense tasks. Should be subtopic to subscriptionRootTopic
taskFailureTopic: qliksense/task_failure
taskFailureFullTopic: qliksense/task_failure_full
taskFailureServerStatusTopic: qliksense/butler/task_failure_server
taskAbortedTopic: qliksense/task_aborted
taskAbortedFullTopic: qliksense/task_aborted_full
serviceRunningTopic: qliksense/service_running
serviceStoppedTopic: qliksense/service_stopped
serviceStatusTopic: qliksense/service_status
...
...


Antz A film review by Marty Mapes Copyright 1998 Marty Mapes
*** (out of 4) If you think Disney animated features have been getting stale lately, give ANTZ a try. ANTZ is the first animated feature put out by DreamWorks SKG, (not affiliated with Disney). As such, it has more freedom to target an audience older than 6. It is hipper and funnier than anything Disney has put out for years.
Woody Allen provides the voice of Z, our hero. Z doesn't fit in with the crowd and wants to find a way to express his individuality. Not an easy task when you're an ant.
Z is sulking in the saloon when Princess Bala (Sharon Stone) shows up, slumming with her palace friends. Bala asks Z to dance with her, and he accepts. While the entire bar dances together in lock-step, Z starts to dance to his own drummer, and even convinces Bala to cut loose with him. But it's not long before Bala has to return to the palace.
The dance was enough to energize Z, and he takes the first opportunity he can to trade places with his soldier-ant friend Weaver (Sylvester Stallone). As a soldier, he will get to parade in front of the royal family and see princess Bala again.
The switch goes well until the soldiers are sent out on a suicide mission against the termites. Luckily for Z, his cowardice makes him hide during the massacre (in a battle scene eerily reminiscent of last year's STARSHIP TROOPERS). The lone survivor, Z returns to the colony, where he is hailed as a war hero, and is given entree to the royal court. After being exposed as a worker ant, Z ends up accidentally kidnaping the princess and escaping the colony.
Since he can't return, he starts walking, half hoping the rumors of a far-off "Insectopia" are true. Even if they're not, as long as he and Bala are together, Z will be happy. But General Mandible (Gene Hackman) wants Bala back in the colony and he wants Z destroyed....
ANTZ has two very simple things going for it: the animation and the writing. Both are far enough above average to make this movie very entertaining.
The animation is all computer generated. We've seen that before in Disney's TOY STORY. What we haven't seen before is the uncanny depth rendered on film for this movie. The CG ants look as though they were filmed and not printed.
The ant colony in this film is full of earthy colors and lifelike textures that are much more subdued than the garish, shiny, plastic surfaces of TOY STORY. It's a more subtle, mature use of CG, and it's the next step in CG evolution.
The writing, too, has matured compared to Disney's latest cartoons. When I say the writing is better, I don't mean the story line. If you squint your eyes so the specific details are blurred, you might mistake ANTZ for last year's HERCULES.  Both have a fairly superficial love interest and chummy, amusing sidekicks..
When I say the writing is good, I mean that screenwriters Todd Alcott and Chris and Paul Weitz, working within the genre of the animated feature, have added personality and edge. (Credit also those who cast Woody Allen in the lead role.)
Allen is allowed a one or two minute rant at the film's opening that made me laugh out loud. He rambles on about his usual New York neuroses, only this time he's an ant.  Instead of a bland, vanilla hero, we get one with a little flavor to him.
Allen's lines are inevitably laced with bug-related puns, just as in HERCULES there were mythological puns. But the Antz puns, tailor-made for Woody Allen, work on more than one level. They are funny not so much because they're puns, but because they're things Allen would say if he were an ant (like when he credits his psychologist for putting him in touch with his inner maggot). Allen has a surprisingly large number of these lines, and most of them work.
ANTZ is not an earthshaking movie, but it is fun. The animation, writing, and casting are all above average, and the time (all 82 minutes) flies by. There wasn't a scene that dragged, which is quite an accomplishment.
And hey, if you're a fellow Disney cynic, you can revel in a cartoon unmarred by schmaltzy love ballads, white-bread heroes, and source-mangling storylines!
Check out more current movie reviews at http://www.indra.com/~mmapes/
-- Marty Mapes<EMAIL_ADDRESS>Movie Habit http://net.indra.com/~mmapes
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Durban Heat v Tshwane Spartans washed out
Cape Town - The Durban Heat failed to deliver any heat and instead had rain ruin their Mzansi Super League (MSL) opener against the Tshwane Spartans at Kingsmead on Saturday.
Seasonal wet weather throughout the week building up to the game meant that a damp outfield was already in place when the players arrived.
The toss was initially delayed due to the field not being dry enough, and, when the heavens opened again shortly after 13:00, it left umpires Allahudien Paleker and Adrian Holdstock with little choice but to call off the game.
It was a disappointing outcome, particularly after the spectacular start to MSL 2.0 on Friday when the Cape Town Blitz edged defending champions the Jozi Stars in a high-scoring thriller in Johannesburg.
The Heat and the Spartans take two points each from the game, with the hosts next in action when they are at home to the Paarl Rocks next Friday.
The visitors take on the Nelson Mandela Bay Giants on Wednesday.


A JSON object containing key-value pairs that will set as the baggage for all spans recorded for this request.
An optional boolean that control whether the decision to record a trace should be forced,
suppressed or be left to the application to decide. If true
a sample is forced. If false
no sample
is taken. If left blank, the application decides based on the sampling-probability
configuration
parameter.
A span ID (belonging to an ongoing trace) under which to create the top level span of the traced request. This header must be accompanied by a non-emtpy TRACE_ID header. All spans generated with the application will now have this span ID as an ancestor.
The trace ID under which to record all new spans. If unspecified, a new trace is started and is assigned a randomly generated UUID.
Note that if a new trace is started by foxx-tracer, the subsequent root span's span ID will not be same as the generated trace ID.
Generated using TypeDoc
The HTTP header keys that are used to control tracing behaviour and for setting trace context.


Recent Quality Issues
0;else other_content">
{{ issue.id }} | {{ issue.supplier_id }} | {{ issue.order_id }} |
{{ issue.category_id }} | {{ issue.date_detected | date: 'MMM d, y' }} | {{ issue.date_closed | date: 'MMM d, y' }}
Currently, there are no recent quality issue cases in the database.


Introduction¶
Kappelt gBridge allows you to control (almost) every smart home device with Google Assistant. It provides a bridge between Google Assistant and MQTT.
Tip
Kappelt gBridge is an open source application. However, I provide an inexpensive hosted appliance of gBridge. This is a great way of supporting my work - and you don’t have to care about installation, debugging and maintenance.
Interested? Have a look at https://about.gbridge.kappelt.net.
It acts like a smart home device provider, that is listed in the Google Home app. But there are no real devices by Kappelt gBridge - there are virtual devices defined by you in your user account’s dashboard. When you interact with a virtual device you’ve defined (“Hey Google, turn on the lights in the living room”), gBridge will publish an MQTT message.
This MQTT message can finally be handled by most smart home applications and might be further processed there.
All set? Let’s get started


Topic 2 Decission Trees
2.1 Boosting
2.1.1 Weak Learners
It is often easy to come up with a weak classifier, one that is marginally better than random guessing:
\[Pr(h(X)) \neq(Y) \leq \frac{1}{2} - \epsilon\] A learning algorithm that can consistently generate such classifiers is called a weak learner.
Is it possible to systematically boost the quality of a weak learner?
2.1.2 The blueprint for boosting
Given: data set \((x^{(1)}, y^{(1)}), ..., (x^{(n)}, y^{(n)})\)
Initially give all points equal weight.
Repeat for \(t = 1, 2,...\):
Feed weighted data set to the weak learner, get back a weak classifier \(h_{t}\)
Reweight data to put more emphasis on points \(h_{t}\) gets wrong
Combine all these \(h_{t}\)’s.
2.1.3 AdaBoost
Data set \((x^{(1)}, y^{(1)}), ..., (x^{(n)}, y^{(n)})\) labels \(y^{(i)}\in \{-1, +1\}\)
Initialize \(D_{1}(i) = \frac{1}{n}\) for all \(i = 1, 2,...n\)
- Equal weight
For \(t = 1, 2,..., T\):
Give \(D_{t}\) to weak learner, get back some \(h_t: \mathcal{X} \to [-1, +1]\)
Compute \(h_{t}\)’s margin of correctness:
\[score, r_{t} = \sum_{i = 1}^{n}D_{t}y^{(i)}h_{t}(x^{(i)}) \in [-1, +1] \\ \alpha_{t} = \frac{1}{2}ln \frac{1 + r_{t}}{1 - r_{t}}\]
Note that in the above equation \(h_{t}(x^{(i)})\) is the prediction. When prediction is correct the term \(y^{(i)}h_{t}(x^{(i)})\) becomes \(`+ 1\); when incorrect it becomes \(- 1\).
Update weights: \[D_{t+1}(i)\propto D_{t}(i)e^{-\alpha_{t}y^{(i)}h_{t}(x^{(i)})}\]
when correct: weights on data get reduced
when incorrect: increased weights on data points
- Final classifier: \[H(x) = sign(\sum_{t = 1}^{T}\alpha_{t}h_{t}(x))\]


---
layout: default
title: Best Deal on Snapdeal - Online shopping
description: To avail the best deal on Snapdeal, purchase from the link provided in this page.
keywords: Best deal on Snapdeal, best deal on online shopping.
---
Best Deal on Snapdeal


Toggle navigation
Mycroft Admin
Schemas
Upload schema
View schemas
Jobs
New job
View jobs
Datastores
Register New datastore


--- title: Contribution Template keywords: fastai sidebar: home_sidebar summary: "A brief sentence describing the goal of the article" description: "A brief sentence describing the goal of the article" nb_path: "nbs/01_intro.contribute.ipynb" ---
Notebooks should be named by their sections as well as a topic. Such as how this one is 01_intro
(for introduction section) .contribute
(as it's the contribution guide). Another example would be 02_vision.classification.single_label
In the very first part of your notebook you should denote the fastai
and fastcore
versions, as well as any other library used. I have a cookie-cutter cell below. Simply call state_versions
with a list of your libraries being used and it will display them in Markdown
.
Ensure you have a #hide_input
comment above the function call so the documentation looks clean.
From here you should denote sections with two ##, walking users through your problem or example you are showing:
My problem is x
, below we will try to solve x
using y
. (No need for verbatum, be as creative as you would like to be!)
Ideally if you are walking through an implementation, at the end show an example of how to perform both batch and single input predictions. (see vision.classification.single_label
for an example)
Once you've written your notebook, simply submit your PR to the repo and I will review it!


Jesus went to a place called Gethsemane to pray. "My Father, if it is possible, let this cup pass from me; yet, not as I will, but as you will." (Mt 26:36-46)
The chief priests with the elders and the scribes held a council. They bound Jesus, led him away, and handed him over to Pilate. Pilate, wishing to satisfy the crowd, had Jesus scourged and handed him over to be crucified. (Mk 15:1-16)
They stripped off his clothes and threw a scarlet military cloak about him. Weaving a crown out of thorns, they placed it on his head, and a reed in his right hand. And kneeling before him, they mocked him, saying, "Hail, King of the Jews!" (Mt 27:27-31)
Jesus, weak from being beaten, was unable to carry His cross to Golgotha alone. Simon, a Cyrenian, helped him. (Mk 15:20-22)
When they came to the place called the Skull, they crucified him and the criminals there, one on his right, the other on his left. Jesus said, "Father, forgive them, they know not what they do." (Lk 23:33-46)


{% extends 'layout-quiz.html' %} {% block pageTitle %} Mental Health {% endblock %} {% block beforeContent %} {% endblock %} {% block content %}
Your answers suggest you’re having some of the symptoms of depression. A doctor can tell for sure.
See a GP or call 111 to discuss how you’re feeling. They can get you the support and treatment if you need it.
Your answers suggest you’re having some of the symptoms of anxiety.
Feeling anxious or worried sometimes is normal, but if it’s starting to affect your daily life, it’s best to take action and consider seeing a GP.


DTrace Probes¶ ↑
A list of DTrace probes and their functionality. “Module” and “Function” cannot be defined in user defined probes (known as USDT), so they will not be specified. Probe definitions are in the format of:
provider:module:function:name(arguments)
Since module and function cannot be specified, they will be blank. An example probe definition for Ruby would then be:
ruby:::method-entry(class name, method name, file name, line number)
Where “ruby” is the provider name, module and function names are blank, the probe name is “method-entry”, and the probe takes four arguments:
-
class name
-
method name
-
file name
-
line number
Probes List¶ ↑
Stability¶ ↑
Before we list the specific probes, let's talk about stability. Probe stability is declared in the probes.d file at the bottom on the pragma D attributes lines. Here is a description of each of the stability declarations.
- Provider name stability
-
The provider name of “ruby” has been declared as stable. It is unlikely that we will change the provider name from “ruby” to something else.
- Module and Function stability
-
Since we are not allowed to provide values for the module and function name, the values we have provided (no value) is declared as stable.
- Probe name stability
-
The probe names are likely to change in the future, so they are marked as “Evolving”. Consumers should not depend on these names to be stable.
- Probe argument stability
-
The parameters passed to the probes are likely to change in the future, so they are marked as “Evolving”. Consumers should not depend on these to be stable.
Declared probes¶ ↑
Probes are defined in the probes.d file. Here are the declared probes along with when they are fired and the arguments they take:
- ruby:::method-entry(classname, methodname, filename, lineno);
-
This probe is fired just before a method is entered.
classname name of the class (a string) methodname name of the method about to be executed (a string) filename the file name where the method is _being called_ (a string) lineno the line number where the method is _being called_ (an int)
- ruby:::method-return(classname, methodname, filename, lineno);
-
This probe is fired just after a method has returned. The arguments are the same as “ruby:::method-entry”.
- ruby:::cmethod-entry(classname, methodname, filename, lineno);
-
This probe is fired just before a C method is entered. The arguments are the same as “ruby:::method-entry”.
- ruby:::cmethod-return(classname, methodname, filename, lineno);
-
This probe is fired just before a C method returns. The arguments are the same as “ruby:::method-entry”.
- ruby:::require-entry(requiredfile, filename, lineno);
-
This probe is fired on calls to rb_require_safe (when a file is required).
requiredfile is the name of the file to be required (string). filename is the file that called "require" (string). lineno is the line number where the call to require was made (int).
- ruby:::require-return(requiredfile, filename, lineno);
-
This probe is fired just before rb_require_safe (when a file is required) returns. The arguments are the same as “ruby:::require-entry”. This probe will not fire if there was an exception during file require.
- ruby:::find-require-entry(requiredfile, filename, lineno);
-
This probe is fired right before search_required is called. search_required determines whether the file has already been required by searching loaded features ($“), and if not, figures out which file must be loaded.
requiredfile is the file to be required (string). filename is the file that called "require" (string). lineno is the line number where the call to require was made (int).
- ruby:::find-require-return(requiredfile, filename, lineno);
-
This probe is fired right after search_required returns. See the documentation for “ruby:::find-require-entry” for more details. Arguments for this probe are the same as “ruby:::find-require-entry”.
- ruby:::load-entry(loadedfile, filename, lineno);
-
This probe is fired when calls to “load” are made. The arguments are the same as “ruby:::require-entry”.
- ruby:::load-return(loadedfile, filename, lineno);
-
This probe is fired when “load” returns. The arguments are the same as “ruby:::load-entry”.
- ruby:::raise(classname, filename, lineno);
-
This probe is fired when an exception is raised.
classname is the class name of the raised exception (string) filename the name of the file where the exception was raised (string) lineno the line number in the file where the exception was raised (int)
- ruby:::object-create(classname, filename, lineno);
-
This probe is fired when an object is about to be allocated.
classname the class of the allocated object (string) filename the name of the file where the object is allocated (string) lineno the line number in the file where the object is allocated (int)
- ruby:::array-create(length, filename, lineno);
-
This probe is fired when an Array is about to be allocated.
length the size of the array (long) filename the name of the file where the array is allocated (string) lineno the line number in the file where the array is allocated (int)
- ruby:::hash-create(length, filename, lineno);
-
This probe is fired when a Hash is about to be allocated.
length the size of the hash (long) filename the name of the file where the hash is allocated (string) lineno the line number in the file where the hash is allocated (int)
- ruby:::string-create(length, filename, lineno);
-
This probe is fired when a String is about to be allocated.
length the size of the string (long) filename the name of the file where the string is allocated (string) lineno the line number in the file where the string is allocated (int)
- ruby:::symbol-create(str, filename, lineno);
-
This probe is fired when a Symbol is about to be allocated.
str the contents of the symbol (string) filename the name of the file where the string is allocated (string) lineno the line number in the file where the string is allocated (int)
- ruby:::parse-begin(sourcefile, lineno);
-
Fired just before parsing and compiling a source file.
sourcefile the file being parsed (string) lineno the line number where the source starts (int)
- ruby:::parse-end(sourcefile, lineno);
-
Fired just after parsing and compiling a source file.
sourcefile the file being parsed (string) lineno the line number where the source ended (int)
- ruby:::gc-mark-begin();
-
Fired at the beginning of a mark phase.
- ruby:::gc-mark-end();
-
Fired at the end of a mark phase.
- ruby:::gc-sweep-begin();
-
Fired at the beginning of a sweep phase.
- ruby:::gc-sweep-end();
-
Fired at the end of a sweep phase.
- ruby:::method-cache-clear(class, sourcefile, lineno);
-
Fired when the method cache is cleared.
class is the classname being cleared, or "global" (string) sourcefile the file being parsed (string) lineno the line number where the source ended (int)


The ToDo Application
Add your todo by typing in the text then pressing Return to add it to the list of todos.


This is example of use of the jQuery Heart Beater - a little helper to perform actions in regular interval. See README file for full doc.
In this example the Heart Beater triggers animation of the heart every 2 seconds and is scheduled to perform just 10 beats. While doing beating it is also monitoring the user's focus on the document and when the user becomes inactive it auto-pauses. You can play with the buttons below to experience most of the functionality. All events triggered by the Heart Beater are logged below.


{% endautoescape %}
{% endif %}
{% include "comics/comicvine_link.html" with cvurl=team.cvurl %}
{% include "comics/related_characters.html" with character_list=team.character_set.all %}
{% include "comics/related_issues_by_series.html" %}
{% endblock content %}