MBUsdlKeys
enum MBUsdlKeys {}
Possible keys that can be used for obtaining USDL result elements.
-
Mandatory on all driver’s licenses. All barcodes which are using 3-track magnetic stripe encoding used in the interest of smoothing a transition from legacy documents shall be designated as
Magnetic
. All barcodes which are using compact encoding compliant with ISO/IEC 18013-2 shall be designated asCompact
. All barcodes (majority) compliant with Mandatory PDF417 Bar Code of the American Association of Motor Vehicle Administrators (AAMVA) Card Design Standard from AAMVA DL/ID-2000 standard to DL/ID-2013 shall be designated asAAMVA
.Declaration
Objective-C
DocumentType
-
Mandatory on all driver’s licenses.
AAMVA Version Number: This is a decimal value between 0 and 99 that specifies the version level of the PDF417 bar code format. Version
0
and00
is reserved for bar codes printed to the specification of the American Association of Motor Vehicle Administrators (AAMVA) prior to the adoption of the AAMVA DL/ID-2000 standard. All bar codes compliant with the AAMVA DL/ID-2000 standard are designated Version01.
All barcodes compliant with AAMVA Card Design Specification version 1.0, dated 09-2003 shall be designated Version02.
All barcodes compliant with AAMVA Card Design Specification version 2.0, dated 03-2005 shall be designated Version03.
All barcodes compliant with AAMVA Card Design Standard version 1.0, dated 07-2009 shall be designated Version04.
All barcodes compliant with AAMVA Card Design Standard version 1.0, dated 07-2010 shall be designated Version05.
All barcodes compliant with AAMVA Card Design Standard version 1.0, dated 07- 2011 shall be designated Version06
. All barcodes compliant with AAMVA Card Design Standard version 1.0, dated 06-2012 shall be designated Version07
. All barcodes compliant with this current AAMVA standard shall be designated08
. Should a need arise requiring major revision to the format, this field provides the means to accommodate additional revision.If document type is not
AAMVA
, this field defines version number of the given document type’s standard.Declaration
Objective-C
StandardVersionNumber
-
Mandatory on all AAMVA, Magnetic and Compact barcodes.
Family name of the cardholder. (Family name is sometimes also called
last name
orsurname.
) Collect full name for record, print as many characters as possible on portrait side of DL/ID.Declaration
Objective-C
CustomerFamilyName
-
Mandatory on all AAMVA, Magnetic and Compact barcodes.
First name of the cardholder.
Declaration
Objective-C
CustomerFirstName
-
Mandatory on all AAMVA, Magnetic and Compact barcodes.
Full name of the individual holding the Driver License or ID.
The Name field contains up to four portions, separated with the
,
delimiter: Last Name (required) , (required) First Name (required) , (required if other name portions follow, otherwise optional) Middle Name(s) (optional) , (required if other name portions follow, otherwise optional) Suffix (optional) , (optional)If indvidual has more than one middle name they are separated with space.
Declaration
Objective-C
CustomerFullName
-
Mandatory on all AAMVA, Magentic and Compact barcodes.
Date on which the cardholder was born. (MMDDCCYY format)
Declaration
Objective-C
DateOfBirth
-
Mandatory on all AAMVA, Magentic barcodes. Optional on Compact barcodes.
Gender of the cardholder. 1 = male, 2 = female.
Declaration
Objective-C
Sex
-
Mandatory on AAMVA 02, 03, 04, 05, 06, 07, 08 barcodes. Optional on AAMVA 01, Magnetic and Compact barcodes.
Color of cardholder’s eyes. (ANSI D-20 codes)
Code Description BLK Black BLU Blue BRO Brown GRY Gray GRN Green HAZ Hazel MAR Maroon PNK Pink DIC Dichromatic UNK Unknown
Declaration
Objective-C
EyeColor
-
Mandatory on all AAMVA and Magnetic barcodes.
On compact barcodes, use kFullAddress.
Street portion of the cardholder address. The place where the registered driver of a vehicle (individual or corporation) may be contacted such as a house number, street address etc.
Declaration
Objective-C
AddressStreet
-
Mandatory on all AAMVA and Magnetic barcodes.
On compact barcodes, use kFullAddress.
City portion of the cardholder address.
Declaration
Objective-C
AddressCity
-
Mandatory on all AAMVA and Magnetic barcodes.
On compact barcodes, use kFullAddress.
State portion of the cardholder address.
Declaration
Objective-C
AddressJurisdictionCode
-
Mandatory on all AAMVA and Magnetic barcodes.
On compact barcodes, use kFullAddress.
Postal code portion of the cardholder address in the U.S. and Canada. If the trailing portion of the postal code in the U.S. is not known, zeros can be used to fill the trailing set of numbers up to nine (9) digits.
Declaration
Objective-C
AddressPostalCode
-
Mandatory on all AAMVA and Magnetic barcodes. Optional on Compact barcodes.
Full address of the individual holding the Driver License or ID.
The full address field contains up to four portions, separated with the
,
delimiter: Street Address (required) , (required if other address portions follow, otherwise optional) City (optional) , (required if other address portions follow, otherwise optional) Jurisdiction Code (optional) , (required if other address portions follow, otherwise optional) ZIP - Postal Code (optional)Declaration
Objective-C
FullAddress
-
Mandatory on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes. Optional on AAMVA 01 and Magnetic barcodes.
Height of cardholder, either in Inches or in Centimeters.
Inches (in): number of inches followed by
in
example: 6'1’‘ =73 in
Centimeters (cm): number of centimeters followed by
cm
example: 181 centimeters =181 cm
Declaration
Objective-C
Height
-
Mandatory on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes. Optional on AAMVA 01 and Magnetic barcodes.
Height of cardholder in Inches. Example: 5'9’‘ =
69
.Declaration
Objective-C
HeightIn
-
Mandatory on AAMVA 02, 03, 04, 05, 06, 07, 08 Compact barcodes. Optional on AAMVA 01 and Magnetic barcodes.
Height of cardholder in Centimeters. Example: 180 Centimeters =
180
.Declaration
Objective-C
HeightCm
-
Mandatory on AAMVA 04, 05, 06, 07, 08. Optional on AAMVA 01, 02, 03, Magnetic and Compcat barcodes.
Middle name(s) of the cardholder. In the case of multiple middle names they shall be separated by space “ ”.
Declaration
Objective-C
CustomerMiddleName
-
Optional on all AAMVA, Magnetic and Compact barcodes.
Bald, black, blonde, brown, gray, red/auburn, sandy, white, unknown. If the issuing jurisdiction wishes to abbreviate colors, the three-character codes provided in ANSI D20 must be used.
Code Description BAL Bald BLK Black BLN Blond BRO Brown GRY Grey RED Red/Auburn SDY Sandy WHI White UNK Unknown
Declaration
Objective-C
HairColor
-
Mandatory on AAMVA 02 barcodes. Optional on AAMVA 01, 03, 04, 05, 06, 07, 08, Magnetic and Compact barcodes.
Name Suffix (If jurisdiction participates in systems requiring name suffix (PDPS, CDLIS, etc.), the suffix must be collected and displayed on the DL/ID and in the MRT).
- JR (Junior)
- SR (Senior)
- 1ST or I (First)
- 2ND or II (Second)
- 3RD or III (Third)
- 4TH or IV (Fourth)
- 5TH or V (Fifth)
- 6TH or VI (Sixth)
- 7TH or VII (Seventh)
- 8TH or VIII (Eighth)
- 9TH or IX (Ninth)
Declaration
Objective-C
NameSuffix
-
Optional on all AAMVA and Compact barcodes.
Other name by which cardholder is known. ALTERNATIVE NAME(S) of the individual holding the Driver License or ID.
The Name field contains up to four portions, separated with the
,
delimiter: AKA Last Name (required) , (required) AKA First Name (required) , (required if other name portions follow, otherwise optional) AKA Middle Name(s) (optional) , (required if other name portions follow, otherwise optional) AKA Suffix (optional) , (optional)If indvidual has more than one AKA middle name they are separated with space.
Declaration
Objective-C
AKAFullName
-
Optional on all AAMVA and Compact barcodes.
Other family name by which cardholder is known.
Declaration
Objective-C
AKAFamilyName
-
Optional on all AAMVA and Compact barcodes.
Other given name by which cardholder is known
Declaration
Objective-C
AKAGivenName
-
Optional on all AAMVA and Compact barcodes.
Other suffix by which cardholder is known.
The Suffix Code Portion, if submitted, can contain only the Suffix Codes shown in the following table (e.g., Andrew Johnson, III = JOHNSON@ANDREW@@3RD):
Suffix Meaning or Synonym JR Junior SR Senior or Esquire 1ST First 2ND Second 3RD Third 4TH Fourth 5TH Fifth 6TH Sixth 7TH Seventh 8TH Eighth 9TH Ninth
Declaration
Objective-C
AKASuffixName
-
Mandatory on AAMVA 02 barcodes. Optional on AAMVA 01, 03, 04, 05, 06, 07, 08, Magnetic and Compact barcodes.
Indicates the approximate weight range of the cardholder: 0 = up to 31 kg (up to 70 lbs) 1 = 32 – 45 kg (71 – 100 lbs) 2 = 46 - 59 kg (101 – 130 lbs) 3 = 60 - 70 kg (131 – 160 lbs) 4 = 71 - 86 kg (161 – 190 lbs) 5 = 87 - 100 kg (191 – 220 lbs) 6 = 101 - 113 kg (221 – 250 lbs) 7 = 114 - 127 kg (251 – 280 lbs) 8 = 128 – 145 kg (281 – 320 lbs) 9 = 146+ kg (321+ lbs)
Declaration
Objective-C
WeightRange
-
Mandatory on AAMVA 02 barcodes. Optional on AAMVA 01, 03, 04, 05, 06, 07, 08, Magnetic and Compact barcodes.
Cardholder weight in pounds Example: 185 lb =
185
Declaration
Objective-C
WeightPounds
-
Mandatory on AAMVA 02 barcodes. Optional on AAMVA 01, 03, 04, 05, 06, 07, 08, Magnetic and Compact barcodes.
Cardholder weight in kilograms Example: 84 kg =
084
Declaration
Objective-C
WeightKilograms
-
Mandatory on all AAMVA and Compact barcodes
The number assigned or calculated by the issuing authority.
Declaration
Objective-C
CustomerIdNumber
-
Mandatory on AAMVA 04, 05, 06, 07, 08 barcodes. Optional on Compact barcodes.
A code that indicates whether a field has been truncated (T), has not been truncated (N), or – unknown whether truncated (U).
Declaration
Objective-C
FamilyNameTruncation
-
Mandatory on AAMVA 04, 05, 06, 07, 08 barcodes. Optional on Compact barcodes.
A code that indicates whether a field has been truncated (T), has not been truncated (N), or – unknown whether truncated (U).
Declaration
Objective-C
FirstNameTruncation
-
Mandatory on AAMVA 04, 05, 06, 07, 08
A code that indicates whether a field has been truncated (T), has not been truncated (N), or – unknown whether truncated (U).
Declaration
Objective-C
MiddleNameTruncation
-
Optional on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes
Country and municipality and/or state/province
Declaration
Objective-C
PlaceOfBirth
-
Optional on all AAMVA barcodes
On Compact barcodes, use kFullAddress
Second line of street portion of the cardholder address.
Declaration
Objective-C
AddressStreet2
-
Optional on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes
Codes for race or ethnicity of the cardholder, as defined in ANSI D20.
Race: Code Description AI Alaskan or American Indian (Having Origins in Any of The Original Peoples of North America, and Maintaining Cultural Identification Through Tribal Affiliation of Community Recognition) AP Asian or Pacific Islander (Having Origins in Any of the Original Peoples of the Far East, Southeast Asia, or Pacific Islands. This Includes China, India, Japan, Korea, the Philippines Islands, and Samoa) BK Black (Having Origins in Any of the Black Racial Groups of Africa) W White (Having Origins in Any of The Original Peoples of Europe, North Africa, or the Middle East)
Ethnicity: Code Description H Hispanic Origin (A Person of Mexican, Puerto Rican, Cuban, Central or South American or Other Spanish Culture or Origin, Regardless of Race) O Not of Hispanic Origin (Any Person Other Than Hispanic) U Unknown
Declaration
Objective-C
RaceEthnicity
-
Optional on AAMVA 01
PREFIX to Driver Name. Freeform as defined by issuing jurisdiction.
Declaration
Objective-C
NamePrefix
-
Mandatory on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes.
Country in which DL/ID is issued. U.S. = USA, Canada = CAN.
Declaration
Objective-C
CountryIdentification
-
Optional on AAMVA version 01.
Driver Residence Street Address 1.
Declaration
Objective-C
ResidenceStreetAddress
-
Optional on AAMVA version 01.
Driver Residence Street Address 2.
Declaration
Objective-C
ResidenceStreetAddress2
-
Optional on AAMVA version 01.
Driver Residence City
Declaration
Objective-C
ResidenceCity
-
Optional on AAMVA version 01.
Driver Residence Jurisdiction Code.
Declaration
Objective-C
ResidenceJurisdictionCode
-
Optional on AAMVA 01 barcodes.
Driver Residence Postal Code.
Declaration
Objective-C
ResidencePostalCode
-
Optional on AAMVA 01 barcodes.
Full residence address of the individual holding the Driver License or ID.
The full address field contains up to four portions, separated with the
,
delimiter: Residence Street Address (required) , (required if other address portions follow, otherwise optional) Residence City (optional) , (required if other address portions follow, otherwise optional) Residence Jurisdiction Code (optional) , (required if other address portions follow, otherwise optional) Residence ZIP - Residence Postal Code (optional)Declaration
Objective-C
ResidenceFullAddress
-
Optional on AAMVA 05, 06, 07, 08
Date on which the cardholder turns 18 years old. (MMDDCCYY format)
Declaration
Objective-C
Under18
-
Optional on AAMVA 05, 06, 07, 08
Date on which the cardholder turns 19 years old. (MMDDCCYY format)
Declaration
Objective-C
Under19
-
Optional on AAMVA 05, 06, 07, 08
Date on which the cardholder turns 21 years old. (MMDDCCYY format)
Declaration
Objective-C
Under21
-
Optional on AAMVA version 01.
The number assigned to an individual by the Social Security Administration.
Declaration
Objective-C
SocialSecurityNumber
-
Optional on AAMVA version 01.
Driver
AKA
Social Security Number. FORMAT SAME AS DRIVER SOC SEC NUM. ALTERNATIVE NUMBERS(S) used as SS NUM.Declaration
Objective-C
AKASocialSecurityNumber
-
Optional on AAMVA 01
ALTERNATIVE MIDDLE NAME(s) or INITIALS of the individual holding the Driver License or ID. Hyphenated names acceptable, spaces between names acceptable, but no other use of special symbols
Declaration
Objective-C
AKAMiddleName
-
Optional on AAMVA 01
ALTERNATIVE PREFIX to Driver Name. Freeform as defined by issuing jurisdiction.
Declaration
Objective-C
AKAPrefixName
-
Optional on AAMVA 01, 06, 07, 08
Field that indicates that the cardholder is an organ donor =
1
.Declaration
Objective-C
OrganDonor
-
Optional on AAMVA 07, 08
Field that indicates that the cardholder is a veteran =
1
Declaration
Objective-C
Veteran
-
Optional on AAMVA 01. (MMDDCCYY format)
ALTERNATIVE DATES(S) given as date of birth.
Declaration
Objective-C
AKADateOfBirth
-
Mandatory on all AAMVA, Magnetic and Compact barcodes.
This number uniquely identifies the issuing jurisdiction and can be obtained by contacting the ISO Issuing Authority (AAMVA)
Declaration
Objective-C
IssuerIdentificationNumber
-
Mandatory on all AAMVA, Magnetic and Compact barcodes.
If document is non expiring than
Non expiring
is written in this field.Date on which the driving and identification privileges granted by the document are no longer valid. (MMDDCCYY format)
Declaration
Objective-C
DocumentExpirationDate
-
Mandatory on all AAMVA and Compact barcodes. Optional on Magnetic barcodes.
Jurisdiction Version Number: This is a decimal value between 0 and 99 that specifies the jurisdiction version level of the PDF417 bar code format. Notwithstanding iterations of this standard, jurisdictions implement incremental changes to their bar codes, including new jurisdiction-specific data, compression algorithms for digitized images, digital signatures, or new truncation conventions used for names and addresses. Each change to the bar code format within each AAMVA version (above) must be noted, beginning with Jurisdiction Version 00.
Declaration
Objective-C
JurisdictionVersionNumber
-
Mandatory on all AAMVA and Magnetic barcodes.
Jurisdiction-specific vehicle class / group code, designating the type of vehicle the cardholder has privilege to drive.
Declaration
Objective-C
JurisdictionVehicleClass
-
Mandatory on all AAMVA barcodes. Optional on Magnetic barcodes.
Jurisdiction-specific codes that represent restrictions to driving privileges (such as airbrakes, automatic transmission, daylight only, etc.).
Declaration
Objective-C
JurisdictionRestrictionCodes
-
Mandatory on all AAMVA barcodes. Optional on Magnetic barcodes.
Jurisdiction-specific codes that represent additional privileges granted to the cardholder beyond the vehicle class (such as transportation of passengers, hazardous materials, operation of motorcycles, etc.).
Declaration
Objective-C
JurisdictionEndorsementCodes
-
Mandatory on all AAMVA and Compact barcodes.
Date on which the document was issued. (MMDDCCYY format)
Declaration
Objective-C
DocumentIssueDate
-
Mandatory on AAMVA versions 02 and 03.
Federally established codes for vehicle categories, endorsements, and restrictions that are generally applicable to commercial motor vehicles. If the vehicle is not a commercial vehicle,
NONE
is to be entered.Declaration
Objective-C
FederalCommercialVehicleCodes
-
Optional on all AAMVA barcodes. Mandatory on Compact barcodes.
Jurisdictions may define a subfile to contain jurisdiction-specific information. These subfiles are designated with the first character of “Z” and the second character is the first letter of the jurisdiction’s name. For example,
ZC
would be the designator for a California or Colorado jurisdiction-defined subfile,ZQ
would be the designator for a Quebec jurisdiction-defined subfile. In the case of a jurisdiction-defined subfile that has a first letter that could be more than one jurisdiction (e.g. California, Colorado, Connecticut) then other data, like the IIN or address, must be examined to determine the jurisdiction.Declaration
Objective-C
IssuingJurisdiction
-
Optional on all AAMVA barcodes. Mandatory on Compact barcodes.
Standard vehicle classification code(s) for cardholder. This data element is a placeholder for future efforts to standardize vehicle classifications.
Declaration
Objective-C
StandardVehicleClassification
-
Optional on all AAMVA and Magnetic barcodes.
Name of issuing jurisdiction, for example: Alabama, Alaska …
Declaration
Objective-C
IssuingJurisdictionName
-
Optional on all AAMVA barcodes.
Standard endorsement code(s) for cardholder. See codes in D20. This data element is a placeholder for future efforts to standardize endorsement codes.
Code Description H Hazardous Material - This endorsement is required for the operation of any vehicle transporting hazardous materials requiring placarding, as defined by U.S. Department of Transportation regulations. L Motorcycles – Including Mopeds/Motorized Bicycles. N Tank - This endorsement is required for the operation of any vehicle transporting, as its primary cargo, any liquid or gaseous material within a tank attached to the vehicle. O Other Jurisdiction Specific Endorsement(s) - This code indicates one or more additional jurisdiction assigned endorsements. P Passenger - This endorsement is required for the operation of any vehicle used for transportation of sixteen or more occupants, including the driver. S School Bus - This endorsement is required for the operation of a school bus. School bus means a CMV used to transport pre-primary, primary, or secondary school students from home to school, from school to home, or to and from school sponsored events. School bus does not include a bus used as common carrier (49 CRF 383.5). T Doubles/Triples - This endorsement is required for the operation of any vehicle that would be referred to as a double or triple. X Combined Tank/HAZ-MAT - This endorsement may be issued to any driver who qualifies for both the N and H endorsements.
Declaration
Objective-C
StandardEndorsementCode
-
Optional on all AAMVA barcodes
Standard restriction code(s) for cardholder. See codes in D20. This data element is a placeholder for future efforts to standardize restriction codes.
Code Description B Corrective Lenses C Mechanical Devices (Special Brakes, Hand Controls, or Other Adaptive Devices) D Prosthetic Aid E Automatic Transmission F Outside Mirror G Limit to Daylight Only H Limit to Employment I Limited Other J Other K CDL Intrastate Only L Vehicles without air brakes M Except Class A bus N Except Class A and Class B bus O Except Tractor-Trailer V Medical Variance Documentation Required W Farm Waiver
Declaration
Objective-C
StandardRestrictionCode
-
Optional on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes
Text that explains the jurisdiction-specific code(s) for classifications of vehicles cardholder is authorized to drive.
Declaration
Objective-C
JurisdictionVehicleClassificationDescription
-
Optional on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes
Text that explains the jurisdiction-specific code(s) that indicates additional driving privileges granted to the cardholder beyond the vehicle class.
Declaration
Objective-C
JurisdictionEndorsmentCodeDescription
-
Optional on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes
Text describing the jurisdiction-specific restriction code(s) that curtail driving privileges.
Declaration
Objective-C
JurisdictionRestrictionCodeDescription
-
Optional on AAMVA 02, 03, 04, 05, 06, 07, 08
A string of letters and/or numbers that is affixed to the raw materials (card stock, laminate, etc.) used in producing driver licenses and ID cards. (DHS recommended field)
Declaration
Objective-C
InventoryControlNumber
-
Optional on AAMVA 04, 05, 06, 07, 08 and Compact barcodes
DHS required field that indicates date of the most recent version change or modification to the visible format of the DL/ID (MMDDCCYY format)
Declaration
Objective-C
CardRevisionDate
-
Mandatory on AAMVA 02, 03, 04, 05, 06, 07, 08 and Magnetic barcodes. Optional and Compact barcodes
Number must uniquely identify a particular document issued to that customer from others that may have been issued in the past. This number may serve multiple purposes of document discrimination, audit information number, and/or inventory control.
Declaration
Objective-C
DocumentDiscriminator
-
Optional on AAMVA 04, 05, 06, 07, 08 and Compact barcodes
DHS required field that indicates that the cardholder has temporary lawful status =
1
.Declaration
Objective-C
LimitedDurationDocument
-
Optional on AAMVA 02, 03, 04, 05, 06, 07, 08 and Compact barcodes
A string of letters and/or numbers that identifies when, where, and by whom a driver license/ID card was made. If audit information is not used on the card or the MRT, it must be included in the driver record.
Declaration
Objective-C
AuditInformation
-
Optional on AAMVA 04, 05, 06, 07, 08 and Compact barcodes
DHS required field that indicates compliance:
M
= materially compliant,F
= fully compliant, and,N
= non-compliant.Declaration
Objective-C
ComplianceType
-
Optional on AAMVA version 01.
Issue Timestamp. A string used by some jurisdictions to validate the document against their data base.
Declaration
Objective-C
IssueTimestamp
-
Optional on AAMVA version 01.
Driver Permit Expiration Date. MMDDCCYY format. Date permit expires.
Declaration
Objective-C
PermitExpirationDate
-
Optional on AAMVA version 01.
Type of permit.
Declaration
Objective-C
PermitIdentifier
-
Optional on AAMVA version 01.
Driver Permit Issue Date. MMDDCCYY format. Date permit was issued.
Declaration
Objective-C
PermitIssueDate
-
Optional on AAMVA version 01.
Number of duplicate cards issued for a license or ID if any.
Declaration
Objective-C
NumberOfDuplicates
-
Optional on AAMVA 04, 05, 06, 07, 08 and Compact barcodes
Date on which the hazardous material endorsement granted by the document is no longer valid. (MMDDCCYY format)
Declaration
Objective-C
HAZMATExpirationDate
-
Optional on AAMVA version 01.
Medical Indicator/Codes. STATE SPECIFIC. Freeform, Standard
TBD
Declaration
Objective-C
MedicalIndicator
-
Optional on AAMVA version 01.
Non-Resident Indicator.
Y
. Used by some jurisdictions to indicate holder of the document is a non-resident.Declaration
Objective-C
NonResident
-
Optional on AAMVA version 01.
A number or alphanumeric string used by some jurisdictions to identify a
customer
across multiple data bases.Declaration
Objective-C
UniqueCustomerId
-
Optional on compact barcodes.
Document discriminator.
Declaration
Objective-C
DataDiscriminator
-
Optional on Magnetic barcodes.
Month on which the driving and identification privileges granted by the document are no longer valid. (MMYY format)
Declaration
Objective-C
DocumentExpirationMonth
-
Optional on Magnetic barcodes.
Field that indicates that the driving and identification privileges granted by the document are nonexpiring =
1
.Declaration
Objective-C
DocumentNonexpiring
-
Optional on Magnetic barcodes.
Security version beeing used.
Declaration
Objective-C
SecurityVersion


Ocean's Eight
Ocean's Eight is a movie starring Sandra Bullock, Cate Blanchett, and Anne Hathaway. Debbie Ocean gathers an all-female crew to attempt an impossible heist at New York City's yearly Met Gala.


Source code for hypertools.tools.reduce
#!/usr/bin/env python
##PACKAGES##
import warnings
import numpy as np
from ppca import PPCA
from sklearn.decomposition import PCA as PCA
from ..tools.df2mat import df2mat
from ..tools.normalize import normalize as normalizer
from .._shared.helpers import *
##MAIN FUNCTION##
[docs]def reduce(x, ndims=3, method='PCA', normalize=False, internal=False):
"""
Reduces dimensionality of an array, or list of arrays
Parameters
----------
x : Numpy array or list of arrays
Dimensionality reduction using PCA is performed on this array. If
there are nans present in the data, the function will try to use
PPCA to interpolate the missing values.
ndims : int
Number of dimensions to reduce
method : str
Reduction model to use. Currently, only 'PCA' (PCA/PPCA) is
implemented. In next release this kwarg will support all scikit-learn
reduction models.
normalize : str or False
Normalizes the data before reducing. If set to 'across', the columns
of the input data will be z-scored across lists (default). That is,
the z-scores will be computed with repect to column n across all arrays
passed in the list. If set to 'within', the columns will be z-scored
within each list that is passed. If set to 'row', each row of the
input data will be z-scored. If set to False, the input data will be
returned with no z-scoring.
Returns
----------
x_reduced : Numpy array or list of arrays
The reduced data with ndims dimensionality is returned. If the input
is a list, a list is returned.
"""
##SUB FUNCTIONS##
def reducePCA(x, ndim):
# if there are any nans in any of the lists, use ppca
if np.isnan(np.vstack(x)).any():
warnings.warn('Missing data: Inexact solution computed with PPCA (see https://github.com/allentran/pca-magic for details)')
# ppca if missing data
m = PPCA(np.vstack(x))
m.fit(d=ndim)
x_pca = m.transform()
# if the whole row is missing, return nans
all_missing = [idx for idx,a in enumerate(np.vstack(x)) if all([type(b)==np.nan for b in a])]
if len(all_missing)>0:
for i in all_missing:
x_pca[i,:]=np.nan
# get the original lists back
if len(x)>1:
x_split = np.cumsum([i.shape[0] for i in x][:-1])
return list(np.split(x_pca,x_split,axis=0))
else:
return [x_pca]
else:
m=PCA(n_components=ndim, whiten=True)
m.fit(np.vstack(x))
if len(x)>1:
return [m.transform(i) for i in x]
else:
return [m.transform(x[0])]
x = format_data(x)
assert all([i.shape[1]>ndims for i in x]), "In order to reduce the data, ndims must be less than the number of dimensions"
if normalize:
x = normalizer(x, normalize=normalize)
if method=='PCA':
x_reduced = reducePCA(x,ndims)
if internal or len(x_reduced)>1:
return x_reduced
else:
return x_reduced[0]


filter
active
active
Playtime
( excluded
)
If you were a video gaming zombie who plays 24/7 without sleeping or eating then:
- Your total amount of consecutive current playtime would be .
- Your remaining amount of consecutive main playtime would be ().
- Your remaining amount of consecutive extras playtime would be ().
- Your remaining amount of consecutive completionist playtime would be ().
Not a zombie? Check out the Steam Survival Calculator ™
Slice
filter
active
active
Playtime by Genre
No Data
Playtime by Metacritic score
No Data
Playtime by Release Date
No Data
Playtime by Type
No Data
Filter
Advanced
| Game | ||||||
|---|---|---|---|---|---|---|
| (nongame/endless?) | > | Missing (click to update) (wrong game?) Updating... Update submitted for approval Update failed (click to retry) | ||||
| - | - | - | - | - | - |


Use Register for registration.
Use CreateGroup for group creating.
Fill target uuid for private conversation and group id for group conversation.


Class: Sketchup::Materials
| Relationships | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Entity
|
|
|
Instance Chain:
self,
Enumerable,
Entity
|
|
| Inherits: |
Sketchup::Entity
|
Overview
A collection of Materials
objects. Each model contains a Materials
collection that can be accessed via Model
.materials.
Instance Attribute Summary
-
#current ⇒ Sketchup::Material
rw
The current method is used to get the current material, i.e.
-
#current=(material) ⇒ Sketchup::Material
rw
The current= method is used to set the current material.
Entity
- Inherited
Instance Method Summary
-
#[](index) ⇒ Sketchup::Material?
The #[] method is used to retrieve a material by index or name.
-
#add(name) ⇒ Sketchup::Material
Add a new
Material
. -
#add_observer(observer) ⇒ Boolean
The add_observer method is used to add an observer to the materials collection.
-
#[](index) ⇒ Sketchup::Material?
The #[] method is used to retrieve a material by index or name.
- #count ⇒ Integer
-
#each {|material| ... } ⇒ nil
The #each method is used to iterate through all of the materials.
-
#length ⇒ Integer
The number of materials in the collection.
-
#load(filename) ⇒ Sketchup::Material
The #load method is used to load a material from file into the model.
-
#purge_unused ⇒ Sketchup::Materials
The purge_unused method is used to remove unused materials.
-
#remove(material) ⇒ Boolean
Remove a given material.
-
#remove_observer(observer) ⇒ Boolean
The remove_observer method is used to remove an observer from the materials collection.
-
#size ⇒ Integer
The number of materials in the collection.
-
#unique_name(name) ⇒ String
The #unique_name method is used to retrieve a unique name from the materials collection that is based on the provided one.
Entity
- Inherited
| #add_observer | The add_observer method is used to add an observer to the current object. |
| #attribute_dictionaries | The attribute_dictionaries method is used to retrieve the |
| #attribute_dictionary | The attribute_dictionary method is used to retrieve an attribute dictionary with a given name that is attached to an |
| #delete_attribute | The |
| #entityID | The entityID method is used to retrieve a unique ID assigned to an entity. |
| #get_attribute | The |
| #inspect | The to_s method is used to retrieve the string representation of the entity. |
| #model | The model method is used to retrieve the model for the entity. |
| #parent | The parent method is used to retrieve the parent of the entity. |
| #persistent_id | The |
| #remove_observer | The remove_observer method is used to remove an observer from the current object. |
| #set_attribute | The set attribute is used to set the value of an attribute in an attribute dictionary with the given name. |
| #to_s | The to_s method is used to retrieve the string representation of the entity. |
| #typename | The typename method retrieves the type of the entity, which will be a string such as “Face”, “Edge”, or “Group”. |
Instance Attribute Details
#current ⇒ Sketchup::Material (rw)
The current method is used to get the current material, i.e. the material that the user has selected in the Materials
dialog.
#current=(material) ⇒ Sketchup::Material (rw)
The current= method is used to set the current material.
Instance Method Details
#[](index) ⇒ Sketchup::Material?
#[](name) ⇒ Sketchup::Material?
The #[]
method is used to retrieve a material by index or name.
The #at method is an alias of #[]
#add(name) ⇒ Sketchup::Material
Add a new Material
. When called with no arguments, this will generate a new unique name for the new Material
. If a name is given, it will check to see if there is already a material with that name. If there is already a material with the given name, then a new unique name is generated using the given name as a base.
#add_observer(observer) ⇒ Boolean
The add_observer method is used to add an observer to the materials collection.
#[](index) ⇒ Sketchup::Material?
#[](name) ⇒ Sketchup::Material?
#count ⇒ Integer
Since SketchUp 2014 the count method is inherited from Ruby’s Enumerable
mix-in module. Prior to that the #count
method is an alias for #length.
#each {|material| ... } ⇒ nil
Don’t remove content from this collection while iterating over it with #each
. This would change the size of the collection and cause elements to be skipped as the indices change. Instead copy the current collection to an array using to_a
and then use each
on the array, when removing content.
The #each
method is used to iterate through all of the materials.
#length ⇒ Integer
#load(filename) ⇒ Sketchup::Material
The #load
method is used to load a material from file into the model.
If a matching material exist in the model it will be returned instead.
#purge_unused ⇒ Materials
The purge_unused method is used to remove unused materials.
#remove(material) ⇒ Boolean
Remove a given material.
NOTE: On SketchUp versions prior to 2014 there is a bug in this method that could potentially lead to file corruption. If you call Materials
.remove on a material that is painted onto any entity in the active model (e.g. faces, edges, groups, …), then calling this method will not successfully unpaint the entity and remove the material from the model. You must first unpaint all of the entities that respond to .material and .back_material before calling Materials
.remove.
#remove_observer(observer) ⇒ Boolean
The remove_observer method is used to remove an observer from the materials collection.
#size ⇒ Integer
#unique_name(name) ⇒ String
The #unique_name
method is used to retrieve a unique name from the materials collection that is based on the provided one. If provided name is unique it will be returned, otherwise any trailing indices will be replaced by a new index.


This page will send HTTP requests to demonstate additional features of Raw routing.
They will show the user of multiple handlers, redirecting, sending errors and custom path parameters.
View the code
Send an HTTP GET request with multiple handlers:
Send an HTTP GET request to a redirecting handler:
Send an HTTP GET request to a handler that parses the URL path as a parameter:
Send an HTTP GET request to a handler that returns an error:


--- layout: post title: Java file upload categories: [] tags: serviceapi java java-client status: publish type: post published: true meta: {} ---
The ServiceStack client we use to connect to the ServiceAPI from Java builds a set of classes to simply creating and requesting objects but it has no facility to upload an electronic document. Given the diversity of HTTP libraries in the Java world this probably makes sense.
This sample demonstrates uploading a file using the Apache HttpClient.


Classes - huh! what are they good for!!.. Absolutely everything!..
Classes, in programming are used in the object-oriented programming style.
They are a construct that group's the actions that a class can perform along with the data (attributes or properties that tell us something about the class) that the actions are performed on. This is called 'encapsulation'. This encapsulation, means we don't have methods and attributes for the same object spread all over the place in your code. This makes for easier maintenance and eliminates duplication of code amongst other things.
If we consider we a house as a class, then each house is an 'instance' of the class of houses. When a house is built, it shares many common traits and behaviours and physical attributes, not necessarily each one identical to another house but often very similar. Let's take this analogy further then, physical attributes relate to the attributes and properties of a class, so front door, back door, kitchen tap, exterior colour, flooring, number of toilets, stove, includes a bath, includes a shower etc. Attributes are what defines it's state or appearance to the outside world. The house's behaviours, might be 'turn on kitchen tap', 'open front door', 'close back door', 'turn on shower', 'vacuum carpet', 'mop floor' etc. So our behaviours are 'actions' we can perform. These 'actions' relate to the 'methods' of a class
When you want to use a class, you first of all need to create an 'instance' of the class. The class serves as a template for the instance of the class. In our example this would be building our house based on it's plans or blue-print.
The great thing about classes is that they enable you to create a template for the object you want to model and from then on make copies from that template. This is called 'inheritance'. This eliminates or reduces much duplication of code as when you want to change an attribute or method for all instances of a class, you just need to make the change in the class, and when instances are created they all inherit that change. No need to make the change in each instance manually.
Why aren't classes just used everywhere then ?. The use of classes may require a bit more planning up front, on the drawing up of plans, confirming what the features of the house will be ensuring the placement of utilities make the building of the house as simple as possible, and taking into account what might be needed in future if the house is to be extended or mofified in some way. If we compare this to the effort and planning that might go into building a garden shed or some such smaller structure, this may be seen as more effort than is required to achieve the desired result, the difference may be seen when modifications or extension is required for the garden shed. These most often will just be banged together, which may not produce the most efficient shed from the gardeners perspective.
As the extensions and changes to the house scale that's when the extra work up front will come into it's own by enabling complex extensions and changes to the building structure to be more easily implemented, maintained and further scaled up.
Let's look further now at creating my house class.
class house
'define some attributes for the house class'
attr_reader :front-door, :back-door, :kitchen-tap, :stove
:stove{element_1 => off,
element_2 => off,
element_3 => off,
element_4 => off,
oven => off}
def initialize
#define the intial states of the attributes
@front-door = 'closed'
@back-door = 'closed'
@kitchen-tap = 'closed'
@stove{element_1 => off,
element_2 => off,
element_3 => off,
element_4 => off,
oven => off}
end
def open_front_door
some code to open the front-door
@front-door = 'open'
end
def close_front_door
some code to close the front-door
@front-door = 'closed'
end
def turn_on_kitchen_tap
some code to turn on the kitchen-tap
@kitchen-tap = 'running'
end
def turn_off_kitchen_tap
some code to turn off the kitched-tap
@kitchen-tap = 'closed'
end
def turn_on_stove_element (which_element)
some code to turn on the (which_element)
@stove[which_element] = 'on'
end
def turn_off_stove_element (which_element)
some code to turn off the @stove[which_element]
@stove[which_element] = 'off'
end
end
Now that we have a class that we can base an instance of a house from the next thing we need to do is to create the instance,
my_house = house.new
We can now interact with our new instance,
Let's check to see if the front door is open
print my_house.front-door would display 'closed' at this point.
Now lets open the front door.
my_house.open_front_door
Let's check the state of the front door again
print my_house.front-door would display 'open' now.
Using this house class, I can now create lots of different house's that are similar, but each one can be independantly controlled and each with their own set of attributes that can only be updated or changed by the methods in the instance.
The instance variables/attributes can only be updated by the methods of the instance, which were inherited from the house class. The encapsulation of the attributes and the methods that work upon these attributes mean anything to do with the houses door's stove, taps etc, can only be made by making a call to the methods of the instance. This means that no other class can be created that can make changes to the atributes of the house class without the house class knowing about it and more importantly being in control of that change.
I am working on creating a working example of my 'house' class, virtual as it may be..Watch this space...


--- layout: base title: Explore the data use-site-title: true css: - "/css/explore.css" - "/css/skeleton.css" - "/css/leaflet.css" - "/css/introjs.min.css" js: - "/js/jquery-1.11.2.min.js" - "/js/d3.min.js" - "/js/d3-scale-chromatic.v1.min.js" - "/js/leaflet.js" - "/js/lodash.js" - "/js/intro.min.js" - "/js/explore/utils.js" - "/js/explore/age.js" - "/js/explore/bmi.js" - "/js/explore/region.js" - "/js/explore/textual.js" - "/js/explore/app.js" - "/js/explore/nutrients.js" ---
Welcome on this personal nutrition datavizualisation!
It is a demo built for a personal nutrition project where participants collect data on their food consumption.
The proof-of-concept interactive visualization allows participants to compare their nutrient intakes across food classes with the rest of the population.
Have fun! ;-)


 Enter your email in the form below and we'll send you instructions for creating a new one. {% endblocktrans %}
{% crispy form %} {% endblock %} {# This is used by django.contrib.auth #}


«
1
2
3
»
Child Case Profile
First Responder ID#
How many children?:
Age:
Disabilities:
Difficulty:
Submit


The following are instructions required to compile an application that uses the FreeType 2 library.
Locate the FreeType 2 include
directory.
You have to add it to your compilation include path.
In Unix-like environments you can use the
pkg-config
program to retrieve the
appropriate compilation flags; say.
pkg-config --cflags freetype2
to get the compilation flags.
This program can also be used to check the version of the library that is installed on your system, as well as the required librarian and linker flags.
Another solution is the freetype-config
script. However, its use is deprecated since it can't
be used reliably for cross compilation.
Include the file named ft2build.h
.
It contains various macro declarations that are later
used to #include
the appropriate public
FreeType 2 header files.
Include the main FreeType 2 API header file.
You should do that using the
macro FT_FREETYPE_H
, like in the
following example.
#include <ft2build.h> #include FT_FREETYPE_H
FT_FREETYPE_H
is a special macro defined
in file ftheader.h
. It contains some
installation-specific macros to name other public
header files of the FreeType 2 API.
You can read this section of the FreeType 2 API Reference for a complete listing of the header macros.
The use of macros in #include
statements is
ANSI-compliant. It is used for several reasons.
FT_MULTIPLE_MASTERS_H
or FT_SFNT_NAMES_H
are a lot more readable
and explanatory than the real file names
ftmm.h
and ftsnames.h
.To initialize the FreeType library, create a variable of
type FT_Library
named, for example, library
, and call the
function FT_Init_FreeType
.
#include <ft2build.h> #include FT_FREETYPE_H FT_Library library; ... error = FT_Init_FreeType( &library ); if ( error ) { ... an error occurred during library initialization ... }
This function is in charge of
library
to it,
andlibrary
object is able to handle TrueType, Type 1,
CID-keyed & OpenType/CFF fonts gracefully.As you can see, the function returns an error code, like
most other functions of the FreeType API. An error code
of 0 (also known
as FT_Err_Ok
) always means that the
operation was successful; otherwise, the value describes
the error, and library
is set to NULL.
A list of all FreeType error codes can be found in
file fterrdef.h
.
Create a new face
object by
calling FT_New_Face
.
A face describes a given typeface and style. For
example, ‘Times New Roman Regular’ and
‘Times New Roman Italic’ correspond to two
different faces.
FT_Library library; /* handle to library */ FT_Face face; /* handle to face object */ error = FT_Init_FreeType( &library ); if ( error ) { ... } error = FT_New_Face( library, "/usr/share/fonts/truetype/arial.ttf", 0, &face ); if ( error == FT_Err_Unknown_File_Format ) { ... the font file could be opened and read, but it appears ... that its font format is unsupported } else if ( error ) { ... another error code means that the font file could not ... be opened or read, or that it is broken... }
As you can certainly imagine, FT_New_Face
opens a font file, then tries to extract one face from it.
Its parameters are as follows.
Certain font formats allow several font faces to be embedded in a single file.
This index tells which face you want to load. An error is returned if its value is too large.
Index 0 always works, though.
A pointer to the handle that is set to describe the new face object.
It is set to NULL in case of error.
To know how many faces a given font file contains, set
face_index
to -1
, then
check the value of face->num_faces
, which
indicates how many faces are embedded in the font
file.
In the case where you have already loaded the font file
into memory, you can similarly create a new face object
for it by
calling FT_New_Memory_Face
.
FT_Library library; /* handle to library */ FT_Face face; /* handle to face object */ error = FT_Init_FreeType( &library ); if ( error ) { ... } error = FT_New_Memory_Face( library, buffer, /* first byte in memory */ size, /* size in bytes */ 0, /* face_index */ &face ); if ( error ) { ... }
As you can see, FT_New_Memory_Face
takes a
pointer to the font file buffer and its size in bytes
instead of a file pathname. Other than that, it has
exactly the same semantics as
FT_New_Face
.
Note that you must not deallocate the font file buffer
before calling
FT_Done_Face
.
There are cases where using a file pathname or preloading the file into memory is not sufficient. With FreeType 2, it is possible to provide your own implementation of I/O routines.
This is done through
the FT_Open_Face
function, which can be used to open a new font face with a
custom input stream, select a specific driver for opening,
or even pass extra parameters to the font driver when
creating the object. We advise you to look up
the FreeType 2
reference manual in order to learn how to use it.
A face object models all information that
globally describes the face. Usually, this data can be
accessed directly by dereferencing a handle, like
in face−>num_glyphs
.
The complete list of available fields is in
the FT_FaceRec
structure description. However, we describe here a few of
them in more detail.
FT_FACE_FLAG_SCALABLE
indicates that the
face's font format is scalable and that glyph images can
be rendered for all character pixel sizes. For more
information on face flags, please read
the FreeType 2
API Reference.A pointer to an array
of FT_Bitmap_Size
elements. Each FT_Bitmap_Size
indicates
the horizontal and vertical character pixel
sizes for each of the strikes that are present in
the face.
Note that, generally speaking, these are not the cell size of the bitmap strikes.
FreeType 2 uses size objects to model all information related to a given character size for a given face. For example, a size object holds the value of certain metrics like the ascender or text height, expressed in 1/64th of a pixel, for a character size of 12 points (however, those values are rounded to integers, i.e., multiples of 64).
When the FT_New_Face
function is called (or
one of its siblings), it automatically creates a
new size object for the returned face. This size object
is directly accessible as
face−>size
.
NOTE: A single face object can deal with one or more size objects at a time; however, this is something that few programmers really need to do. We have thus decided to make this feature available through additional functions.
When a new face object is created, all elements are set
to 0 during initialization. To populate the
structure with sensible values, you should
call FT_Set_Char_Size
.
Here is an example, setting the character size to 16pt for
a 300×300dpi device:
error = FT_Set_Char_Size( face, /* handle to face object */ 0, /* char_width in 1/64th of points */ 16*64, /* char_height in 1/64th of points */ 300, /* horizontal device resolution */ 300 ); /* vertical device resolution */
Some notes.
This function computes the (possibly fractional) character pixel size that corresponds to the character width and height and device resolutions. A common acronym for the pixel size is ppem (pixel per em).
If you want to specify the (integer) pixel sizes
yourself, you can call
FT_Set_Pixel_Sizes
.
error = FT_Set_Pixel_Sizes( face, /* handle to face object */ 0, /* pixel_width */ 16 ); /* pixel_height */
This example sets the character pixel sizes to 16×16 pixels. As previously, a value of 0 for one of the dimensions means ‘same as the other’.
Note that both functions return an error code. Usually,
an error occurs with a fixed-size font format (like FNT or
PCF) when trying to set the pixel size to a value that is
not listed in the face->fixed_sizes
array.
Be aware that fractional ppem values are not always supported. For example, the native bytecode engine for hinting TrueType fonts (TTFs) only supports integer ppem values, and FreeType rounds fractional ppem values accordingly.
Normally, an application wants to load a glyph image based on its character code, which is a unique value that defines the character for a given encoding. For example, code 65 (0x41) represents character ‘A’ in ASCII encoding.
A face object contains one or more tables, called charmaps, to convert character codes to glyph indices. For example, most older TrueType fonts contain two charmaps: One is used to convert Unicode character codes to glyph indices, the other one is used to convert Apple Roman encoding to glyph indices. Such fonts can then be used either on Windows (which uses Unicode) and old MacOS versions (which use Apple Roman). Note also that a given charmap might not map to all the glyphs present in the font.
By default, when a new face object is created, FreeType tries to select a Unicode charmap. It emulates a Unicode charmap if the font doesn't contain such a charmap, based on glyph names. Note that it is possible that the emulation misses glyphs if glyph names are non-standard. For some fonts like symbol fonts, no Unicode emulation is possible at all.
Later on we will describe how to look for specific
charmaps in a face. For now, we assume that the face
contains at least a Unicode charmap that was selected
during a call to FT_New_Face
. To convert a
Unicode character code to a font glyph index, we use
FT_Get_Char_Index
.
glyph_index = FT_Get_Char_Index( face, charcode );
This code line looks up the glyph index corresponding to
the given charcode
in the charmap that is
currently selected for the face. You should use the
UTF-32 representation form of Unicode; for example, if you
want to load character U+1F028, use value 0x1F028 as the
value for charcode
.
If no charmap was selected, the function returns the charcode.
Note that this is one of the rare FreeType functions that do not return an error code. However, when a given character code has no glyph image in the face, value 0 is returned. By convention, it always corresponds to a special glyph image called the missing glyph, which is commonly displayed as a box or a space.
Once you have a glyph index, you can load the corresponding glyph image. The latter can be stored in various formats within the font file. For fixed-size formats like FNT or PCF, each image is a bitmap. Scalable formats like TrueType or CFF use vectorial shapes (outlines) to describe each glyph. Some formats may have even more exotic ways of representing glyphs (e.g., MetaFont – but this format is not supported). Fortunately, FreeType 2 is flexible enough to support any kind of glyph format through a simple API.
The glyph image is always stored in a special object called a
glyph slot. As its name suggests, a glyph slot
is a container that is able to hold one glyph image at a
time, be it a bitmap, an outline, or something else. Each
face object has a single glyph slot object that can be
accessed as face->glyph
. Its fields are
explained by
the FT_GlyphSlotRec
structure documentation.
Loading a glyph image into the slot is performed by
calling FT_Load_Glyph
.
error = FT_Load_Glyph( face, /* handle to face object */ glyph_index, /* glyph index */ load_flags ); /* load flags, see below */
The load_flags
value is a set of bit flags
to indicate some special operations. The default value
FT_LOAD_DEFAULT
is 0.
This function tries to load the corresponding glyph image from the face.
FT_LOAD_NO_BITMAP
flag.The
field face−>glyph−>format
describes the format used for storing the glyph image in
the slot. If it is
not FT_GLYPH_FORMAT_BITMAP
, one can
immediately convert it to a bitmap
through FT_Render_Glyph
.
error = FT_Render_Glyph( face->glyph, /* glyph slot */ render_mode ); /* render mode */
The parameter render_mode
is a set of bit
flags to specify how to render the glyph image.
FT_RENDER_MODE_NORMAL
, the default, renders
an anti-aliased coverage bitmap with 256 gray levels (also
called a pixmap), as this is the default. You
can alternatively use FT_RENDER_MODE_MONO
if
you want to generate a 1-bit monochrome bitmap. More
values are available for
the FT_Render_Mode
enumeration value.
Once you have a bitmapped glyph image, you can access it
directly through glyph->bitmap
(a simple
descriptor for bitmaps or pixmaps), and position it
through glyph->bitmap_left
and
glyph->bitmap_top
. For optimal rendering
on a screen the bitmap should be used as an alpha channel
in linear blending with gamma correction.
Note that bitmap_left
is the horizontal
distance from the current pen position to the leftmost
border of the glyph bitmap, while bitmap_top
is the vertical distance from the pen position (on the
baseline) to the topmost border of the glyph
bitmap. It is positive to indicate an upwards
distance.
As said before, when a new face object is created, it
looks for a Unicode charmap and select it. The currently
selected charmap can be accessed
via face->charmap
. This field is NULL if
no charmap is selected, which typically happens when you
create a new FT_Face
object from a font file
that doesn't contain a Unicode charmap (which is rather
infrequent today).
There are two ways to select a different charmap with
FreeType. It's easiest if the encoding you need already
has a corresponding enumeration defined
in FT_FREETYPE_H
, for
example FT_ENCODING_BIG5
. In this case, you
can call
FT_Select_Charmap
.
error = FT_Select_Charmap( face, /* target face object */ FT_ENCODING_BIG5 ); /* encoding */
Another way is to manually parse the list of charmaps for
the face; this is accessible through the
fields num_charmaps
and
charmaps
(notice the ‘s’) of the
face object. As you could expect, the first is the number
of charmaps in the face, while the second is a table
of pointers to the charmaps embedded in the face.
Each charmap has a few visible fields to describe it more
precisely. The most important ones are
charmap->platform_id
and charmap->encoding_id
, defining a pair
of values that describe the charmap in a rather generic
way: Each value pair corresponds to a given encoding. For
example, the pair (3,1) corresponds to Unicode. The list
is defined in the OpenType specification; you can also use
the file FT_TRUETYPE_IDS_H
, which defines
several helpful constants to deal with them. Note that we
use the OpenType enumeration values for non-OpenType fonts
also (by defining additional constants where
necessary).
To select a specific encoding, you need to find a corresponding value pair in the specification, then look for it in the charmaps list.
FT_CharMap found = 0;
FT_CharMap charmap;
int n;
for ( n = 0; n < face->num_charmaps; n++ )
{
charmap = face->charmaps[n];
if ( charmap->platform_id == my_platform_id &&
charmap->encoding_id == my_encoding_id )
{
found = charmap;
break;
}
}
if ( !found ) { ... }
/* now, select the charmap for the face object */
error = FT_Set_Charmap( face, found );
if ( error ) { ... }
Once a charmap has been selected, either through
FT_Select_Charmap
or FT_Set_Charmap
,
it is used by all subsequent calls
to FT_Get_Char_Index
.
It is possible to specify an affine transformation with
FT_Set_Transform
,
to be applied to glyph images when they are loaded. Of
course, this only works for scalable (vectorial) font
formats.
error = FT_Set_Transform( face, /* target face object */ &matrix, /* pointer to 2x2 matrix */ &delta ); /* pointer to 2d vector */
This function sets the current transformation for a given
face object. Its second parameter is a pointer to an
FT_Matrix
structure that describes a 2×2 affine matrix. The
third parameter is a pointer to
an FT_Vector
structure, describing a two-dimensional vector that
translates the glyph image after the 2×2
transformation.
Note that the matrix pointer can be set to NULL, in which case the identity transformation is used. Coefficients of the matrix are otherwise in 16.16 fixed-point units.
The vector pointer can also be set to NULL (in which case a delta of (0,0) is used). The vector coordinates are expressed in 1/64th of a pixel (also known as 26.6 fixed-point numbers).
The transformation is applied to every
glyph that is loaded through FT_Load_Glyph
and is completely independent of any hinting
process. This means that you won't get the same
results if you load a glyph at the size of 24 pixels,
or a glyph at the size of 12 pixels scaled by 2
through a transformation, because the hints are computed
differently (except if you have disabled hints).
If you ever need to use a non-orthogonal transformation
with optimal hints, you first have to decompose your
transformation into a scaling part and a rotation/shearing
part. Use the scaling part to compute a new character
pixel size, then the other one to call
FT_Set_Transform
. This is explained in more
detail in part II of this tutorial.
Rotation usually disables hinting.
Loading a glyph bitmap with a non-identity transformation works; the transformation is ignored in this case.
We now present a simple example to render a string of 8-bit Latin-1 text, assuming a face that contains a Unicode charmap.
The idea is to create a loop that loads one glyph image on each iteration, converts it to a pixmap, draws it on the target surface, then increments the current pen position.
The following code performs our simple text rendering with the functions previously described.
FT_GlyphSlot slot = face->glyph; /* a small shortcut */ int pen_x, pen_y, n; ... initialize library ... ... create face object ... ... set character size ... pen_x = 300; pen_y = 200; for ( n = 0; n < num_chars; n++ ) { FT_UInt glyph_index; /* retrieve glyph index from character code */ glyph_index = FT_Get_Char_Index( face, text[n] ); /* load glyph image into the slot (erase previous one) */ error = FT_Load_Glyph( face, glyph_index, FT_LOAD_DEFAULT ); if ( error ) continue; /* ignore errors */ /* convert to an anti-aliased bitmap */ error = FT_Render_Glyph( face->glyph, FT_RENDER_MODE_NORMAL ); if ( error ) continue; /* now, draw to our target surface */ my_draw_bitmap( &slot->bitmap, pen_x + slot->bitmap_left, pen_y - slot->bitmap_top ); /* increment pen position */ pen_x += slot->advance.x >> 6; pen_y += slot->advance.y >> 6; /* not useful for now */ }
This code needs a few explanations.
slot
that points
to the face object's glyph slot. (The
type FT_GlyphSlot
is a pointer). That is a convenience to avoid using
face->glyph->XXX
every time.slot->advance
, which correspond to the
glyph's advance width (also known as
its escapement). The advance vector is
expressed in 1/64th of pixels, and is truncated to
integer pixels on each iteration.my_draw_bitmap
is not part
of FreeType but must be provided by the application to
draw the bitmap to the target surface. In this example,
it takes a pointer to
an FT_Bitmap
descriptor and the position of its top-left corner as
arguments. For ideal rendering on a screen this
function should perform linear blending with gamma
correction, using the bitmap as an alpha channel.slot->bitmap_top
is
positive for an upwards vertical distance.
Assuming that the coordinates taken
by my_draw_bitmap
use the opposite
convention (increasing Y corresponds to downwards
scanlines), we subtract it from pen_y
,
instead of adding to it.The following code is a refined version of the example above. It uses features and functions of FreeType that have not yet been introduced, and which are explained below.
FT_GlyphSlot slot = face->glyph; /* a small shortcut */ FT_UInt glyph_index; int pen_x, pen_y, n; ... initialize library ... ... create face object ... ... set character size ... pen_x = 300; pen_y = 200; for ( n = 0; n < num_chars; n++ ) { /* load glyph image into the slot (erase previous one) */ error = FT_Load_Char( face, text[n], FT_LOAD_RENDER ); if ( error ) continue; /* ignore errors */ /* now, draw to our target surface */ my_draw_bitmap( &slot->bitmap, pen_x + slot->bitmap_left, pen_y - slot->bitmap_top ); /* increment pen position */ pen_x += slot->advance.x >> 6; }
We have reduced the size of our code, but it does exactly the same thing.
FT_Load_Char
instead of FT_Load_Glyph
. As you probably
imagine, it is equivalent to
calling FT_Get_Char_Index
, then
FT_Load_Glyph
.We do not use FT_LOAD_DEFAULT
for the
loading mode, but the bit
flag FT_LOAD_RENDER
. It indicates that
the glyph image must be immediately converted to an
anti-aliased bitmap. This is of course a shortcut
that avoids calling FT_Render_Glyph
explicitly but is strictly equivalent.
Note that you can also specify that you want a
monochrome bitmap instead by using the
additional FT_LOAD_MONOCHROME
load
flag.
Let us try to render transformed text now (for example
through a rotation). We can do this
using FT_Set_Transform
.
FT_GlyphSlot slot; FT_Matrix matrix; /* transformation matrix */ FT_UInt glyph_index; FT_Vector pen; /* untransformed origin */ int n; ... initialize library ... ... create face object ... ... set character size ... slot = face->glyph; /* a small shortcut */ /* set up matrix */ matrix.xx = (FT_Fixed)( cos( angle ) * 0x10000L ); matrix.xy = (FT_Fixed)(-sin( angle ) * 0x10000L ); matrix.yx = (FT_Fixed)( sin( angle ) * 0x10000L ); matrix.yy = (FT_Fixed)( cos( angle ) * 0x10000L ); /* the pen position in 26.6 cartesian space coordinates */ /* start at (300,200) */ pen.x = 300 * 64; pen.y = ( my_target_height - 200 ) * 64; for ( n = 0; n < num_chars; n++ ) { /* set transformation */ FT_Set_Transform( face, &matrix, &pen ); /* load glyph image into the slot (erase previous one) */ error = FT_Load_Char( face, text[n], FT_LOAD_RENDER ); if ( error ) continue; /* ignore errors */ /* now, draw to our target surface (convert position) */ my_draw_bitmap( &slot->bitmap, slot->bitmap_left, my_target_height - slot->bitmap_top ); /* increment pen position */ pen.x += slot->advance.x; pen.y += slot->advance.y; }
Some remarks.
FT_Vector
to
store the pen position, with coordinates expressed as
1/64th of pixels, hence a multiplication. The position
is expressed in cartesian space.bitmap_left
and bitmap_top
correspond to the bitmap
origin in target space pixels. We thus don't
add pen.x
or pen.y
to their
values when calling my_draw_bitmap
.A complete source code example can be found here.
It is important to note that, while this example is a bit more complex than the previous one, it is strictly equivalent for the case where the transformation is the identity. Hence it can be used as a replacement (but a more powerful one).
The still present few shortcomings will be explained, and solved, in the next part of this tutorial.
Last update: 13-Feb-2018


{% from "wiki/includes/document_macros.html" import revision_diff with context %} {{ revision_diff(revision_from, revision_to, show_picker=True) }}


import awesome from Life; def myLife(): print ("Coding is awesome!") print ("I evolve around it") myLife()


---
layout: post
title: Lacto Calamine Classic
tags:
- Lacto Calamine
status: publish
type: post
published: true
meta:
_edit_last: '2'
_aioseop_description: Lacto Calamine - Classic
_aioseop_keywords: Lacto Calamine - Classic review, Lacto Calamine , Lacto Calamine
review
_aioseop_title: Lacto Calamine - Classic
_graphene_slider_img: global
_graphene_slider_imgurl: ''
_graphene_show_addthis: global
_yoast_wpseo_linkdex: '85'
_yoast_wpseo_focuskw: lacto calamine classic
_yoast_wpseo_title: Lacto Calamine Classic - Miss Enchanted
_yoast_wpseo_metadesc: Lacto Calamine Classic review and swatches.
_yoast_wpseo_meta-robots-noindex: '0'
_yoast_wpseo_meta-robots-nofollow: '0'
_yoast_wpseo_meta-robots-adv: none
_yoast_wpseo_sitemap-include: ! '-'
_yoast_wpseo_sitemap-prio: ! '-'
_yoast_wpseo_canonical: ''
_yoast_wpseo_redirect: ''
_thumbnail_id: '383'
---
Lacto Calamine Classic
This is a life saver, I have been using Lacto Calamine Classic for last 10 years :). I don't remember who introduced me to this great product, but I do remember using it during summers back in my home town. Initially my hostel mates thought it was kinda foundation because of its pink color :D he he
Price: Rs. 95 for 120ml
Product boasts of: Discover Skinsurance with Lacto calamine - The goodness of Clay & Glycerin gives your skin:
- Nourishment,
- Acne and Oil control
- Dead skin removal
- Protection.
Apply daily for clear, beautiful skin
Product contains: Aqua, Light Kaolin, Castor Oil, Glycerin, Zinc Oxide, Zinc Carbonate, Emulsifiers, Preservatives, Perfumes and Permited colours
Instruction: Shake well before use and for external purpose only.
What I Love about the product:
- All the contents are safe and beneficial for the skin health.
- Consistency is correct and gives coverage to skin.
- Gets absorbed into skin and gives a shine free look.
- Pricing is so correct :)
- Handy packing and can be carried in hand bag
- It does remove dead skin slowly
- It gives that soothing effect to the complete face.
What I dont like :
- No Sun, protection, so need to put on a sheer SPF powder OR cream on top :(
I absolutely adore the product, it keeps my sensitive and oily skin oil free and healthy.
Whats your take on Lacto Calamine Classic have you tried the Aloe vera version yet ?


{% extends 'portal/base.html' %} {% load static %} {% load bootstrap %} {% block title %} UniBind Enrichment Analysis {% endblock %} {% block content_header %} UniBind Enrichment Analysis {% endblock %} {% block breadcrumb %}
Note: All the input file(s) should be genomic regions as BED file in hg38 version of the human genome.
{% if message %} {% endif %}The UniBind_enrichment tool predicts which sets of TFBSs from the UniBind database are enriched in a set of given genomic regions. Enrichment computations are performed using the LOLA tool. For more information about the underlying enrichment computations, read the LOLA documentation. The underlying database of TFBS sets from UniBind in provided in the RDS file data/20190423_UniBind_LOLA.RDS (provided here), which has been precomputed using LOLA. The tool allows for three types of computations:
To compute which sets of TFBSs from UniBind are enriched in a set S of genomic regions compared to a background B of genomic regions, you can use the oneSetBg subcommand as follows.
bash bin/UniBind_enrich.sh oneSetBg <LOLA db> <S bed> <B bed> <output dir>
This will compute the enrichment of TFBS sets from UniBind (using
data/20190423_UniBind_LOLA.RDS) in the genomic regions from S (provided as
a BED file) when compared to the genomic regions in B (provided as a BED
file). All result files will be provided in the <output dir>
directory.
To compute which sets of TFBSs from UniBind are enriched in a set S1 of genomic regions compared to another set S2 of genomic regions, you can use the twoSets subcommand as follows.
bash bin/UniBind_enrich.sh twoSets <LOLA db> <S1 bed> <S2 bed> <output dir>
This will compute the enrichment of TFBS sets from UniBind (using
data/20190423_UniBind_LOLA.RDS) in the genomic regions from S1 (provided as
a BED file) when compared to the genomic regions in S2 (provided as a BED
file). All result files will be provided in the <output dir>
directory.
When no background is provided, one can compute which sets of TFBSs from UniBind are enriched in a set S of genomic regions using the oneSetNoBg subcommand as follows. In this case, the enrichment will be computed against a default background corresponding to the genomic regions of all TFBSs stored in UniBind. WARNING We encourage users to provide an adequate background set of genomic regions whenever possible using the oneSetBg subcommand.
bash bin/UniBind_enrich.sh oneSetNoBg <LOLA db> <LOLA universe> <S bed> <output dir>
This will compute the enrichment of TFBS sets from UniBind (using
data/20190423_UniBind_LOLA.RDS and data/20190423_UniBind_LOLAuniverse.RDS)
in the genomic regions from S (provided as a BED file). All result files will
be provided in the <output dir>
directory.
The output directory will contain the allEnrichments.tsv file provide the
enrichment score for each TFBS set from UniBind along with their metadata
information. Similar files (following the template col_
A visual representation of the enrichment analysis is provided in the output directory in the plot file allEnrichments_swarm.pdf. It corresponds to a swarm plot using the log10(p-value) of the enrichment for each TFBS set on the y-axis. The data sets for the top 10 TFs showing a log10(p-value)<2 are highlighted with dedicated colors (one color per TF). Data sets with log10(p-value)>2 are provided with a color for N.S. (non-significant).
As an example of application, we provide data derived from the publication DNA methylation at enhancers identifies distinct breast cancer lineages, Fleischer, Tekpli, et al, Nature Communications, 2017. The genomic regions of interest correspond to 200bp-long regions around CpGs from cluster 2A described in the publication. These regions around CpGs of interest are shown to be associated with FOXA1, GATA, and ESR1 binding. We applied the following command to compute TFBS enrichment using all the CpG probes from the Illumina Infinium HumanMethylation450 microarray:
bash bin/UniBind_enrich.sh oneSetBg data/20190423_UniBind_LOLAdb.RDS data/example_Fleischer_et_al/clusterA_200bp_hg38.bed data/example_Fleischer_et_al/450k_probes_hg38_200bp.bed ub_enrichment
We observe a clear enrichment for TFBSs associated with the expected TFs. The corresponding swarm plot is:


Wrap Up Scores Week 12
AMARILLO, Texas (KFDA) - The Wrap Up continues this week with the latest scores and highlights from this week’s games.
You can view this week’s scores below:
Don’t forget to tune in to The Wrap Up on 10too at 11:05 p.m. every Friday night.


Nick
My Profile
My Calendar
My Inbox
3
My Tasks
7
Lock Screen
Log Out
Store
Store
Seller Account
Store View
Developer
Follow
Message
Overview
Store Account Details
Products
Store Analytics
Visitors
Sales
Refunds
Orders
Reports & Analytics
Help
37
Projects
51
Tasks
61
Uploads
About Marcus Doe
Lorem ipsum dolor sit amet diam nonummy nibh dolore.
www.keenthemes.com
@keenthemes
keenthemes
Profile Account
Store Details
Business & Bank Details
Documents
Seller Name
Seller Email Address
City Pincode Number
State
City
Contact Number
Display Name
Store Description
Pick up Address
Contact Number
Pick up Address
Pincode Number
State
City
Save
Cancel
Business Details
Business Name
Main Selling Category
PAN Number
TIN Number
TAN Number
Edit
Cancel
Bank Details
Bank Name
Account Holder Name
Account Number
IFSC Code
State
City
Branch
Save
Cancel
Upload Other Files
1 file selected.
Other Actions


"x" "1" "CHUNG,KT, MURDOCK,CA, ZHOU,Y, STEVENS,SE, LI,YS, WEI,CI, FERNANDO,SYAND CHOU,MW, EFFECTS OF THE NITRO GROUP ON THE MUTAGENICITY AND TOXICITY OF SOMEBENZAMINES, ENVIRON. MOL. MUTAGEN. 27(1):67-74, 1996"


| Package | flare.util |
| Class | public class Strings |
format
method provides a powerful mechanism for formatting
and templating strings.
| Property | Defined by | ||
|---|---|---|---|
| AD : String = "AD" [static] String indicating "AD" time.
| Strings | ||
| AM1 : String = "A" [static] Abbreviated string indicating "AM" time.
| Strings | ||
| AM2 : String = "AM" [static] Full string indicating "AM" time.
| Strings | ||
| BC : String = "BC" [static] String indicating "BC" time.
| Strings | ||
| DAY_ABBREVS : Array [static] Array of abbreviated names for days of the week.
| Strings | ||
| DAY_NAMES : Array [static] Array of full names for days of the week.
| Strings | ||
| DECIMAL_SEPARATOR : String = "." [static] Separator for decimal (fractional) values.
| Strings | ||
| MONTH_ABBREVS : Array [static] Array of abbreviated names for months of the year.
| Strings | ||
| MONTH_NAMES : Array [static] Array of full names for months of the year.
| Strings | ||
| NaN : String = "NaN" [static] String representing Not-a-Number (NaN).
| Strings | ||
| NEGATIVE_INFINITY : String = "-Inf" [static] String representing negative infinity.
| Strings | ||
| PM1 : String = "P" [static] Abbreviated string indicating "PM" time.
| Strings | ||
| PM2 : String = "PM" [static] Full string indicating "PM" time.
| Strings | ||
| POSITIVE_INFINITY : String = "+Inf" [static] String representing positive infinity.
| Strings | ||
| THOUSAND_SEPARATOR : String = "," [static] Separator for thousands values.
| Strings |
| Method | Defined by | ||
|---|---|---|---|
|
Strings()
Constructor, throws an error if called, as this is an abstract class.
| Strings | ||
|
align(s:String, align:int):String
[static]
Aligns a string by inserting padding space characters as needed.
| Strings | ||
|
format(fmt:String, ... args):String
[static]
Outputs a formatted string using a set of input arguments and string
formatting directives.
| Strings | ||
|
pad(x:Number, digits:int):String
[static]
Pads a number with a specified number of "0" digits on
the left-hand-side of the number.
| Strings | ||
|
padString(s:String, n:int):String
[static]
Pads a string with zeroes up to given length.
| Strings | ||
|
repeat(s:String, reps:int):String
[static]
Creates a new string by repeating an input string.
| Strings |
| Constant | Defined by | ||
|---|---|---|---|
| DEFAULT_NUMBER : String = "0.########" [static] Default formatting string for numbers.
| Strings |
| AD | property |
public static var AD:String = "AD"
String indicating "AD" time.
| AM1 | property |
public static var AM1:String = "A"
Abbreviated string indicating "AM" time.
| AM2 | property |
public static var AM2:String = "AM"
Full string indicating "AM" time.
| BC | property |
public static var BC:String = "BC"
String indicating "BC" time.
| DAY_ABBREVS | property |
public static var DAY_ABBREVS:Array
Array of abbreviated names for days of the week.
| DAY_NAMES | property |
public static var DAY_NAMES:Array
Array of full names for days of the week.
| DECIMAL_SEPARATOR | property |
public static var DECIMAL_SEPARATOR:String = "."
Separator for decimal (fractional) values.
| MONTH_ABBREVS | property |
public static var MONTH_ABBREVS:Array
Array of abbreviated names for months of the year.
| MONTH_NAMES | property |
public static var MONTH_NAMES:Array
Array of full names for months of the year.
| NaN | property |
public static var NaN:String = "NaN"
String representing Not-a-Number (NaN).
| NEGATIVE_INFINITY | property |
public static var NEGATIVE_INFINITY:String = "-Inf"
String representing negative infinity.
| PM1 | property |
public static var PM1:String = "P"
Abbreviated string indicating "PM" time.
| PM2 | property |
public static var PM2:String = "PM"
Full string indicating "PM" time.
| POSITIVE_INFINITY | property |
public static var POSITIVE_INFINITY:String = "+Inf"
String representing positive infinity.
| THOUSAND_SEPARATOR | property |
public static var THOUSAND_SEPARATOR:String = ","
Separator for thousands values.
| Strings | () | constructor |
public function Strings()
Constructor, throws an error if called, as this is an abstract class.
| align | () | method |
public static function align(s:String, align:int):String
Aligns a string by inserting padding space characters as needed.
Parameterss:String — the string to align
|
|
align:int — an integer indicating both the desired length of
the string (the absolute value of the input) and the alignment
style (negative for left alignment, positive for right alignment)
|
String — the aligned string, padded or truncated as necessary
|
| format | () | method |
public static function format(fmt:String, ... args):String
Outputs a formatted string using a set of input arguments and string formatting directives. This method uses the String formatting conventions of the .NET framework, providing a very flexible system for mapping input values into various string representations. For examples and reference documentation for string formatting options, see this example page or Microsoft's documentation.
Parametersfmt:String — a formatting string. Format strings include markup
indicating where input arguments should be placed in the string,
along with optional formatting directives. For example,
{1}, {0} writes out the second value argument, a
comma, and then the first value argument.
|
|
... args — value arguments to be placed within the formatting
string.
|
String — the formatted string.
|
| pad | () | method |
public static function pad(x:Number, digits:int):String
Pads a number with a specified number of "0" digits on the left-hand-side of the number.
Parametersx:Number — an input number
|
|
digits:int — the number of "0" digits to pad by
|
String — a padded string representation of the input number
|
| padString | () | method |
public static function padString(s:String, n:int):String
Pads a string with zeroes up to given length.
Parameterss:String — the string to pad
|
|
n:int — the target length of the padded string
|
String — the padded string. If the input string is already equal or
longer than n characters it is returned unaltered. Otherwise, it
is left-padded with zeroes up to form an n-character string.
|
| repeat | () | method |
public static function repeat(s:String, reps:int):String
Creates a new string by repeating an input string.
Parameterss:String — the string to repeat
|
|
reps:int — the number of times to repeat the string
|
String — a new String containing the repeated input
|
| DEFAULT_NUMBER | constant |
public static const DEFAULT_NUMBER:String = "0.########"
Default formatting string for numbers.


Welcome to Akan Birthday Calculator. Most people do know when their birthdays are, but some might not know what day of the week they were born. Luckily for us, there is a way to calculate the day of the week from a specific date.
The Akans name Calculator takes a user's birthday and calculates the day of the week they were born and then depending on their gender outputs their Akan Name. Akan names are derived from Ghanian culture. Frequently in Ghana, children are given their first name as a 'day name' which corresponds to the day in the week they were born.


Our Approach to Privacy
Our goal is to maintain your trust and confidence when handling personal information about you.
Security of Personal Information
The security of personal information about you is our priority. We protect this information by maintaining physical, electronic and procedural safeguards that meet applicable law. We train our employees in the proper handling of personal information. When we use other companies to provide services for us, we require them to protect the confidentiality of personal information they receive.
Unfortunately, however, while we strive to protect your personal information, not everything is under our control and no data transmission over the internet can be guaranteed to be 100% secure. You must keep your password and other website registration information you hold secret. You should also control access to your SMS/email communications at all times.
Online Privacy and Cookies Policy
This Online Privacy and Cookies Policy describes how we may collect, use and share information you provide when you visit this website and receive our SMS/email communications. If you are a cardholder, it is supplemental to any information that has been provided to you in connection with the card, which will explain in more detail which Citi entities control and are responsible for the handling of your information.
1. What Information Do We Collect?
2. How Do We Use the Information We Collect?
3. Can You Control Your Information That’s Collected and Used Online?
1. What Information Do We Collect?
When you visit our site, we automatically collect the IP address of the device you use to connect to the Internet. In addition, we gather information such as what browser and which version of it you're using, the type of operating system you have and your internet service provider. If you access this website via your mobile device, we may also collect information about your mobile provider and your mobile device. This information allows us to recognize when your device accesses our website and helps us provide an online experience that matches your device.
We may use cookies or other tracking technologies to do this. In some cases, we may not be able to provide the services unless the cookie or other technology is installed.
In addition to the information described above , we may also gather or process personal information that you provide to us such as your user name, password, address, global location, card number, security code, postcode, email or telephone PIN. In the course of using this website, you may provide us with other personal information to the extent you wish to do so or that we may request from you to allow us to provide you with further information. For example, where offered in your country, you may choose to provide us with your mobile number or email address in order to receive alerts relating to your reserved balance. Registration on ClientZone website is required in order to use your card. Registration on the One Platform website is not obligatory and you can still use your card without such registration (although you may not be able to receive all the services offered by us).
Cookies
When you browse our site, Citi uses cookies to collect information and store your online preferences.
 Cookies are useful because they allow a website to recognize a user’s device. Some of these cookies will be encrypted.
Most of the cookies used on the website are essential in order to enable you to access the website securely. This website uses temporary “session” cookies which are only active on your device for the duration of your usage of our website. These cookies may allow, for example, your device’s web browser to remember which pages on our website you have visited.
If you decide to tick the 'Remember my preferences' box when logging in to our website, cookies may be placed on your device which remain on your device after you have finished using our website. These cookies may remain on your device until such time as you decide to delete them via your browser settings in accordance with Section 4 of this Online Privacy and Cookies Policy. The details stored on these cookies may include your user name, language or the region you are in. A cookie will also be set to record whether you have acknowledged our notice regarding the use of cookies, so that the notice won’t be displayed to you again unnecessarily.
It’s important to note that most of the cookies we use do not capture any information that can personally identify you and they cannot track your browsing activity on any other websites. Most of the cookies we use on the website are essential in order to enable you to access the website securely.
You can find more information about cookies, including how to see what cookies have been set and how to manage and delete them, by looking at Section 4 of this Online Privacy and Cookies Policy, or by visiting the all about cookies website.
2. How Do We Use the Information We Collect?
Citi uses the information we collect about and from you to manage our business and to offer a high quality, personalized online experience on our site.
The information we collect allows us to:
· Verify your identity when you access the services on this website;
· Communicate with you (including via email or SMS where such contact details have been provided);
· Investigate any complaints about the use of this website;
· Maintain security and confidentiality of data on this website; and
· Provide services via this website.
We may also use the information we collect to administer and manage our business and meet legal, regulatory and compliance requirements (such as anti money laundering, regulatory reporting requirements and record maintenance). This may include disclosing your information to regulators, government authorities and other official bodies to the extent permitted under applicable data protection laws.
We may disclose your personal information to other companies within the Citigroup Inc. group of companies and to its or their service providers and agents for the above purposes. This will be done confidentially and only to the extent permitted under applicable data protection laws. In some countries, you may have the right to request a list of those entities that may have access to your personal information. For this information, please email<EMAIL_ADDRESS>Your personal information may be transferred to the recipients identified above for the above purposes which, given the international nature of our business, may be located in countries other than your own such as the US and India, including countries which may not have laws protecting the use of your personal information which are as strong as the laws in your country. However, the security of your personal information is our priority and we maintain adequate safeguards (including the use of appropriate contracts) to protect it.
If we sell all or part of our business, or make a sale or transfer of assets, or are otherwise involved in a merger or business transfer, we may transfer your personal information to a third party as part of that transaction (and will seek your consent where required by applicable law).
We will not rent, sell or otherwise provide your personal information to third parties for their marketing purposes or use your personal information for any other purpose as described herein without your prior consent.
3. Can You Control Your Information That’s Collected and Used Online?
You have the ability to control how your information is collected and used online.
Alerts
If you wish to amend your choice of email or SMS alerts or stop receiving them at any time, you will need to amend your contact details through the website or contact Customer Services.
Cookies
You can also control whether to accept cookies or not or remove existing cookies. If you decide to not accept cookies or remove existing cookies, some features and services on our site may not work properly.
If you would prefer, you can:
Please refer to the help and support area on your internet browser for instructions on how to locate the file or directory that stores cookies.
Privacy Requests and Questions
To request a copy of the information we hold on you or if you have any other requests or questions about privacy or your rights (which may include, subject to applicable law, the right to correct, suppress and sometimes object to or delete certain information), please contact us at<EMAIL_ADDRESS>We may charge you a reasonable administration fee for providing you with a copy of such information, as permitted under applicable law. You can also access and/or change your personal information by logging onto the website
Please note that any personal information you provide to Citi will be retained by us in accordance with applicable law.
Notice of changes
From time to time, we may change this Online Privacy and Cookies Policy. The effective date of this policy, as stated below, indicates the last time this policy was revised or materially changed. Checking the effective date below allows you to determine whether there have been changes since the last time you reviewed the policy. We will notify you if the changes are material and if required by applicable law, we will obtain your consent.
Effective Date
This policy was last modified on 2 September 2013.
This website is managed by Citibank, N.A.
© Copyright 2013 Citibank, N.A. All Rights Reserved.


A reminder that all voting for the student government election this year will be held in person. This page is for informational purposes only.
Students will have complete access to all the candidate profiles on the website, and should familiarize themselves with the candidates before election week. On the first day of election week (April 12th), the campaign videos will be released on the website for teachers to show to their classes, as well as for students to view themselves. Candidates will also be campaigning throughout the school and engaging with the student body.
We will be using the ranked-choice voting system for the 2021 election. Students will be asked to rank the top 5 candidates for each candidate. Please watch the video for more information about ranked-choice voting. See a sample ballot here.
Important! If you are unable to attend class on Friday morning, an early-voting session will be available the day before (Thursday, April 15th) after school in Room 116. Please bring a copy of your schedule and student ID.


## Mako can find this base file because it's in the settings.py -> MAKO_TEMPLATES_DIRS list <%inherit file="base.htm" /> <%block name="content">
Jacob and Julie Meyer started Meyer Photography in 1990 after they graduated in graphics design and photography respectively.
Meyer Photography has been a sucessfull local shop ever since inception, but with the new trends in digital photography the Meyer's new they had move with the market.
In 2013, My Stuff was born, and since that day we have worked tirelessly to bring you the best that the digital photography world has to offer.
My Stuff is just the beginning. The Meyer's have other great plans that are going to change the world of digital photography.
%block>


List 89
I was inspired by Huyen Chip to make this list. My list of things I wanna do before I leave this life.
- ~ Be kind
- ~ Challenge the Status Quo
- ~ Act Like an Entrepreneur
- ~ Have an “It can be done, it can be improved” Attitude
- Get married with the one i love
- Be a good father
- Visit America
- Visit North Pole
- Visit South Pole
- Visit Everest Base Camp
- Start my own company (I had two)
- Start a non profit organization
- Drive a boat/ship with a license
- Have a trip to Son Doong cave
- Read 500 books


I'm a very driven person, draming of one day sailing around the world, map the ocean floor, and uncover the secrets of deep sea life. I'm in pursuit of jobs that can help make my dreams happen.
-
Cal State Monterey Bay
2011-2015
B.S. Marine Sciences, Psychology Minor -
Cuesta College, San Luis Obispo
2008-2011
General Education


Posted on
by
Contact Project Owner
Project Description:
Target Industry:
Location
Tags
{{item}}
Comments:
{{comment.message}}
by {{comment.author}} on
Add Comments:
Add Comment


{% extends 'portal/base.html' %} {% load static %} {% block title %} About {% endblock %} {% block content_header %} About JASPAR {% endblock %} {% block breadcrumb %}
JASPAR is a collection of transcription factor DNA-binding preferences, modeled as matrices. These can be converted into Position Weight Matrices (PWMs or PSSMs), used for scanning genomic sequences.
JASPAR is the only database with this scope where the data can be used with no restrictions (open-source). For a comprehensive review of models and how they can be used, please see the following reviews


Namespace google::cloud::mocks (2.9.0)
Contains helpers for testing the Google Cloud C++ Client Libraries.
The symbols defined in this namespace are part of google-cloud-cpp
's public API. Application developers may use them when mocking the client libraries in their own tests.
Functions
CurrentOptions()
Retrieve options used in a client call.
This would be used to verify configuration options from within a MockConnection. It provides a way for applications to test the difference between client.Foo(request, options)
and client.Foo(request)
.
TEST(Foo, CallOptions) {
auto mock = std::make_shared<MockConnection>();
EXPECT_CALL(*mock, Foo).WillOnce([] {
auto const& options = google::cloud::mocks::CurrentOptions();
EXPECT_THAT(options, ...);
});
auto client = Client(mock);
MyFunctionThatCallsFoo(client);
}
| Returns | |
|---|---|
| Type | Description |
Options const & |
MakeStreamRange(std::vector< T >, Status)
Construct a StreamRange
<T>
for use in tests.
auto sr = MakeStreamRange<T>({t1, t2});
for (StatusOr<T> const& t : sr) {
// Yields t1 -> t2
}
sr = MakeStreamRange<T>({t1, t2}, BadStatus());
for (StatusOr<T> const& t : sr) {
// Yields t1 -> t2 -> BadStatus()
}
| Parameters | |
|---|---|
| Name | Description |
values |
The successfully returned |
final_status |
|
typename T |
|
| Returns | |
|---|---|
| Type | Description |
StreamRange< T > |


Pricing is the name of the game in US Federal Government Contracting. Are your prices too high putting you out of contention for a prized RFP? Are your prices too low and going to be a liability to company profitability and sustainability? We help companies with creating indirect rates, reviewing pricing proposals, DCAA audits and ensuring your accounting system is compliant with government standards. Our pricing services are available a la carte by the hour and are billed in 15 minute increments. Additional fees for expedited or short turn-around times.
A Defense Contract Audit Agency Audit is an important part of winning a large US Federal Government Defense Contract. With defense spending being the highest spending category of government spending, any company that could possibly provide a service to a defense agency should be looking into the requirements. Most people associate the defense agencies with guns and rockets. This is a ill-informed view of these agencies. The defense agencies buy almost everything from companies like yours because they need a whole lot more than just guns and rockets to run a vast agency/bureaucracy and take care of troops. For certain sized contracts, a DCAA Audit becomes a requirment. We can look through your books to make sure everything is up to date with the government standards of DCAA Audits.