Jason Larkin's PhD Projects
Origin of the Exceptionally Low Thermal Conductivity of Fullerene Derivative PCBM Films (in progress)
Building on the work and analysis in the projects: Predicting Alloy Vibrational Mode Properties using Lattice Dynamics Calculations, Molecular Dynamics Simulations, and the Virtual Crystal Approximation, and Vibrational Mean Free Paths and Thermal Conductivity Accumulation Functions for Amorphous Materials, we studied the thermal conductivity of fullerene-derivative PCBM thin films. The motivation for this study are the recent measurements by Duda et al. that show PCBM have the lowest thermal conductivity of a fully-dense solid.+ +


Side Resolution
Bore Resolution
Forward Resolution
Up Resolution
Down Resolution
Side Quality
Bore Quality
Forward Quality
Up Quality
Down Quality
Forward Camera Focus
Side AutoExp
Bore AutoExp
Forward AutoExp
Up AutoExp
Down AutoExp
Trim Weight
Last: Unknown
H2O Sampler
Last: Unknown
Gripper
Last: Unknown


| 804 | (A) | that it fleghe in-to þe felde a furlonge and more |
| (C) | ---- no text ---- | |
| 800 | (D) | þat in-to þe feld it flye a furlong and more |
| (E) | ---- no text ---- | |
| (Ex) | ---- no text ---- | |
| 824 | (L) | þat hit flow in to þe feld a forlong or more |
| (P) | ---- no text ---- | |
| 787 | (U) | That in to the felde flewe / a forlong and more |
| (V) | ---- no text ---- |


Download {% endblock %}


Validator output for http://wap.samsungmobile.com/uaprof/SGH-S500.xml
RDF parser error:{E205} rdf:Description is not allowed as an element tag here.
RDF parser warning:{W102} unqualified use of rdf:ID is deprecated.
RDF parser warning:{W102} unqualified use of rdf:resource is deprecated.
RDF parser error:{E201} resource not allowed as attribute here.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "16" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "Yes" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "ARM7" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "Yes" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "ISO-8859-1" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "US-ASCII" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "UTF-8" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "ISO-10646-UCS-2" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "PhoneKeypad" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "SGH-S500" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "2" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "ISO-8859-1" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "US-ASCII" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "UTF-8" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "ISO-10646-UCS-2" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "128x160" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "8x16" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "Yes" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "Yes" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "Yes" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "SAMSUNG" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "Yes" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E205} rdf:Description is not allowed as an element tag here.
RDF parser warning:{W102} unqualified use of rdf:ID is deprecated.
RDF parser warning:{W102} unqualified use of rdf:resource is deprecated.
RDF parser error:{E201} resource not allowed as attribute here.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "No" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "application/vnd.wap.wmlc" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "application/vnd.wap.wbxml" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "application/vnd.wap.wmlscriptc" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "application/vnd.wap.multipart.mixed" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "image/vnd.wap.wbmp" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "image/gif" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "application/vnd.smaf" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "application/vnd.samsung.specific-image" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "application/x-wap-prov.browser-settings" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "US-ASCII" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "ISO-8859-1" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "UTF-8" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "ISO-10646-UCS-2" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "base64" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "MIDP/1.0.3-compatible" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "CLDC/1.0.3-compatible" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "SunJRE/1.3" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E205} rdf:Description is not allowed as an element tag here.
RDF parser warning:{W102} unqualified use of rdf:ID is deprecated.
RDF parser warning:{W102} unqualified use of rdf:resource is deprecated.
RDF parser error:{E201} resource not allowed as attribute here.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "WTLS-2" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "GPRS" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "CSD" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "SMS" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E205} rdf:Description is not allowed as an element tag here.
RDF parser warning:{W102} unqualified use of rdf:ID is deprecated.
RDF parser warning:{W102} unqualified use of rdf:resource is deprecated.
RDF parser error:{E201} resource not allowed as attribute here.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "Openwave" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "<IP_ADDRESS>" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E205} rdf:Description is not allowed as an element tag here.
RDF parser warning:{W102} unqualified use of rdf:ID is deprecated.
RDF parser warning:{W102} unqualified use of rdf:resource is deprecated.
RDF parser error:{E201} resource not allowed as attribute here.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "C" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "1400" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "1.2" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "4096" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "1.2.1" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "1.1" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "1.3" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "Lang" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "Float" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "String" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "URL" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "WMLBrowser" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "Dialogs" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E205} rdf:Description is not allowed as an element tag here.
RDF parser warning:{W102} unqualified use of rdf:ID is deprecated.
RDF parser warning:{W102} unqualified use of rdf:resource is deprecated.
RDF parser error:{E201} resource not allowed as attribute here.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "text/plain" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E204} rdf:li is not allowed as an element tag here.
RDF parser error:{E202} Expecting XML start or end element(s). String data "base64" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
RDF parser error:{E201} Multiple children of property element
RDF parser error:{E202} Expecting XML start or end element(s). String data "4096" not allowed. Maybe there should be an rdf:parseType='Literal' for embedding mixed XML content in RDF. Maybe a striping error.
WARNING: The profile uses a commonly used namespace alias
Aliased namespace is: http://www.wapforum.org/profiles/UAPROF/ccppschema-20020710#
Real namespace is: http://www.wapforum.org/UAPROF/ccppschema-20020710#
Error: http://www.w3.org/1999/02/22-rdf-syntax-ns#subject there is a problem with components
Error: http://www.w3.org/1999/02/22-rdf-syntax-ns#type there is a problem with components
PROFILE IS NOT VALID
Problems with this report?
Original profile
<?xml version="1.0"?>
<!--
*********************************************************************
* SAMSUNG GSM/GPRS Handset UA Prof
*
* Version: 0.4
* Created: 20/11/2003
* Edited: 20/11/2003
* Edited: 20/11/2003
* Edited: 20/11/2003
* Author : INHYE<EMAIL_ADDRESS>* Organization: R&D Group 2 Software Lab. Application team.
*
* Copyright 2003 SAMSUNG
*
* Revision History
* 0.1 Initial Release
* 0.11 Modified Release (</RDF> -> </rdf:RDF>)
*********************************************************************
-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:prf="http://www.wapforum.org/profiles/UAPROF/ccppschema-20020710#" xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<!--*************************************** Hardware Platform Description ***************************************-->
<prf:component>
<rdf:Description ID="HardwarePlatform">
<rdf:type resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#HardwarePlatform"/>
<prf:BitsPerPixel>16</prf:BitsPerPixel>
<prf:ColorCapable>Yes</prf:ColorCapable>
<prf:CPU>ARM7</prf:CPU>
<prf:ImageCapable>Yes</prf:ImageCapable>
<prf:InputCharSet>
<rdf:Bag>
<rdf:li>ISO-8859-1</rdf:li>
<rdf:li>US-ASCII</rdf:li>
<rdf:li>UTF-8</rdf:li>
<rdf:li>ISO-10646-UCS-2</rdf:li>
</rdf:Bag>
</prf:InputCharSet>
<prf:Keyboard>PhoneKeypad</prf:Keyboard>
<prf:Model>SGH-S500</prf:Model>
<prf:NumberOfSoftKeys>2</prf:NumberOfSoftKeys>
<prf:OutputCharSet>
<rdf:Bag>
<rdf:li>ISO-8859-1</rdf:li>
<rdf:li>US-ASCII</rdf:li>
<rdf:li>UTF-8</rdf:li>
<rdf:li>ISO-10646-UCS-2</rdf:li>
</rdf:Bag>
</prf:OutputCharSet>
<prf:ScreenSize>128x160</prf:ScreenSize>
<prf:ScreenSizeChar>8x16</prf:ScreenSizeChar>
<prf:SoundOutputCapable>Yes</prf:SoundOutputCapable>
<prf:StandardFontProportional>Yes</prf:StandardFontProportional>
<prf:TextInputCapable>Yes</prf:TextInputCapable>
<prf:Vendor>SAMSUNG</prf:Vendor>
<prf:VoiceInputCapable>Yes</prf:VoiceInputCapable>
</rdf:Description>
</prf:component>
<!--*************************************** Software Platform Description ***************************************-->
<prf:component>
<rdf:Description ID="SoftwarePlatform">
<rdf:type resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#SoftwarePlatform"/>
<prf:AcceptDownloadableSoftware>No</prf:AcceptDownloadableSoftware>
<prf:CcppAccept>
<rdf:Bag>
<rdf:li>application/vnd.wap.wmlc</rdf:li>
<rdf:li>application/vnd.wap.wbxml</rdf:li>
<rdf:li>application/vnd.wap.wmlscriptc</rdf:li>
<rdf:li>application/vnd.wap.multipart.mixed</rdf:li>
<rdf:li>image/vnd.wap.wbmp</rdf:li>
<rdf:li>image/gif</rdf:li>
<rdf:li>application/vnd.smaf</rdf:li>
<rdf:li>application/vnd.samsung.specific-image</rdf:li>
<rdf:li>application/x-wap-prov.browser-settings</rdf:li>
</rdf:Bag>
</prf:CcppAccept>
<prf:CcppAccept-Charset>
<rdf:Bag>
<rdf:li>US-ASCII</rdf:li>
<rdf:li>ISO-8859-1</rdf:li>
<rdf:li>UTF-8</rdf:li>
<rdf:li>ISO-10646-UCS-2</rdf:li>
</rdf:Bag>
</prf:CcppAccept-Charset>
<prf:CcppAccept-Encoding>
<rdf:Bag>
<rdf:li>base64</rdf:li>
</rdf:Bag>
</prf:CcppAccept-Encoding>
<prf:JavaPlatform>
<rdf:Bag>
<rdf:li>MIDP/1.0.3-compatible</rdf:li>
<rdf:li>CLDC/1.0.3-compatible</rdf:li>
</rdf:Bag>
</prf:JavaPlatform>
<prf:JVMVersion>
<rdf:Bag>
<rdf:li>SunJRE/1.3</rdf:li>
</rdf:Bag>
</prf:JVMVersion>
</rdf:Description>
</prf:component>
<!--*************************************** Network Characteristics Description ***************************************-->
<prf:component>
<rdf:Description ID="NetworkCharacteristics">
<rdf:type resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#NetworkCharacteristics"/>
<prf:SecuritySupport>
<rdf:Bag>
<rdf:li>WTLS-2</rdf:li>
</rdf:Bag>
</prf:SecuritySupport>
<prf:SupportedBearers>
<rdf:Bag>
<rdf:li>GPRS</rdf:li>
<rdf:li>CSD</rdf:li>
<rdf:li>SMS</rdf:li>
</rdf:Bag>
</prf:SupportedBearers>
</rdf:Description>
</prf:component>
<!--*************************************** Browser UA Description ***************************************-->
<prf:component>
<rdf:Description ID="BrowserUA">
<rdf:type resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#BrowserUA"/>
<prf:BrowserName>Openwave</prf:BrowserName>
<prf:BrowserVersion><IP_ADDRESS></prf:BrowserVersion>
</rdf:Description>
</prf:component>
<!--*************************************** WAP Characteristics Description ***************************************-->
<prf:component>
<rdf:Description ID="WapCharacteristics">
<rdf:type resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#WapCharacteristics"/>
<prf:WapDeviceClass>C</prf:WapDeviceClass>
<prf:WapPushMsgSize>1400</prf:WapPushMsgSize>
<prf:WapVersion>1.2</prf:WapVersion>
<prf:WmlDeckSize>4096</prf:WmlDeckSize>
<prf:WmlScriptVersion>
<rdf:Bag>
<rdf:li>1.2.1</rdf:li>
</rdf:Bag>
</prf:WmlScriptVersion>
<prf:WmlVersion>
<rdf:Bag>
<rdf:li>1.1</rdf:li>
<rdf:li>1.3</rdf:li>
</rdf:Bag>
</prf:WmlVersion>
<prf:WmlScriptLibraries>
<rdf:Bag>
<rdf:li>Lang</rdf:li>
<rdf:li>Float</rdf:li>
<rdf:li>String</rdf:li>
<rdf:li>URL</rdf:li>
<rdf:li>WMLBrowser</rdf:li>
<rdf:li>Dialogs</rdf:li>
</rdf:Bag>
</prf:WmlScriptLibraries>
</rdf:Description>
</prf:component>
<!--*************************************** Push Characteristics Description ***************************************-->
<prf:component>
<rdf:Description ID="PushCharacteristics">
<rdf:type resource="http://www.wapforum.org/profiles/UAPROF/ccppschema-20010430#PushCharacteristics"/>
<prf:Push-Accept>
<rdf:Bag>
<rdf:li>text/plain</rdf:li>
</rdf:Bag>
</prf:Push-Accept>
<prf:Push-Accept-Encoding>
<rdf:Bag>
<rdf:li>base64</rdf:li>
</rdf:Bag>
</prf:Push-Accept-Encoding>
<prf:Push-MsgSize>4096</prf:Push-MsgSize>
</rdf:Description>
</prf:component>
<!--********************************************* END of UAProf *********************************************-->
</rdf:RDF>


[page:Object3D] → [page:Light] →
[name]
This light's color gets applied to all the objects in the scene globally.
Example
[example:canvas_camera_orthographic camera / orthographic ]
[example:canvas_interactive_voxelpainter interactive / voxelpainter ]
[example:canvas_materials materials ]
[example:canvas_sandbox sandbox ]
[example:webgl_animation_cloth animation / cloth ]
[example:webgl_animation_skinning_blending animation / skinning / blending ]
var light = new THREE.AmbientLight( 0x404040 ); // soft white light
scene.add( light );
Constructor
[name]( [page:Integer hex] )
[page:Integer hex] — Numeric value of the RGB component of the color.
This creates an Ambientlight with a color.
Properties
[property:Float intensity]
Light's intensity.
In "physically correct" mode, the product of color * intensity is interpreted as luminous irradiance measured in lux at the material surface.
Default — *1.0*.
Methods
[method:AmbientLight clone]()
It returns a clone of Ambientlight.
[method:JSON toJSON]()
Return Ambientlight data in JSON format.
Source
[link:https://github.com/mrdoob/three.js/blob/master/src/[path].js src/[path].js]


*** Your Daily Free Stuff! - http://p.feedblitz.com/r.asp?l=83729917&f=927397&u=34705849&c=4681558
**In This Issue…
-Free 2014 National Poetry Month Poster
-Free Sample of Cantu Shea Butter Coconut Curling Cream
-Free Garnier Triple Nutrition Sample
-Free Sample of Emergen-C
-Reminder: Enter our $100 Amazon Gift Card Giveaway!
-Search Sweet Free Stuff
** Free 2014 National Poetry Month Poster - http://p.feedblitz.com/r.asp?l=84513964&f=927397&u=34705849&c=4681558
The post Free 2014 National Poetry Month Poster appeared first on SweetFreeStuff.com!.
• Email to a friend • Article Search - http://www.feedblitz.com/f/f.fbz?Search=927397;23433268;Free Stuff;Free 2014 National Poetry Month Poster;4681558 • View comments - http://feeds.feedblitz.com/&;/50831549/0/sweetfreestuff&;Free-National-Poetry-Month-Poster/ • Track comments - http://www.feedblitz.com/f/f.fbz?Track=http%3a%2f%2ffeeds.feedblitz.com%2f&;%2f50831549%2f0%2fsweetfreestuff&;Free-National-Poetry-Month-Poster%2ffeed%2f&ref=comment:927397 •
** Free Sample of Cantu Shea Butter Coconut Curling Cream - http://p.feedblitz.com/r.asp?l=84092201&f=927397&u=34705849&c=4681558
Free Sample of Cantu Shea Butter Coconut Curling Cream
The post Free Sample of Cantu Shea Butter Coconut Curling Cream appeared first on SweetFreeStuff.com!.
* Comments
- cant wait to try it! by Carol Dalo
- Please send your special for my daughter Anna! THANK YOU! by Alyona
- I am really needing a great curling cream for my frizzy/curly … by Renee`
- I would love to try this product! by Gloria
- free samples by mail by jana young
• Email to a friend • Article Search - http://www.feedblitz.com/f/f.fbz?Search=927397;23433268;Health and Beauty Freebies;Free Sample of Cantu Shea Butter Coconut Curling Cream;4681558 • View comments - http://feeds.feedblitz.com/&;/50213419/0/sweetfreestuff&;Free-Sample-of-Cantu-Shea-Butter-Coconut-Curling-Cream/ • Track comments - http://www.feedblitz.com/f/f.fbz?Track=http%3a%2f%2ffeeds.feedblitz.com%2f&;%2f50213419%2f0%2fsweetfreestuff&;Free-Sample-of-Cantu-Shea-Butter-Coconut-Curling-Cream%2ffeed%2f&ref=comment:927397 •
** Free Garnier Triple Nutrition Sample - http://p.feedblitz.com/r.asp?l=83792399&f=927397&u=34705849&c=4681558
Click where it says “Get Sample” to sign up for a Free Sample of Garnier Triple Nutrition.
The post Free Garnier Triple Nutrition Sample appeared first on SweetFreeStuff.com!.
* Comments
- would love to try by Gene
- My hair is very dry from coloring. Would love a free sample. … by Linda R Simiele
- My hair feels so dry and I have tried just about everything to … by Autumn Patson
- would love to try this by cath gough
- I woud love a sample by Renee`
- Plus 8 more…
• Email to a friend • Article Search - http://www.feedblitz.com/f/f.fbz?Search=927397;23433268;Health and Beauty Freebies;Free Garnier Triple Nutrition Sample;4681558 • View comments - http://feeds.feedblitz.com/&;/49717584/0/sweetfreestuff&;Free-Garnier-Triple-Nutrition-Sample/ • Track comments - http://www.feedblitz.com/f/f.fbz?Track=http%3a%2f%2ffeeds.feedblitz.com%2f&;%2f49717584%2f0%2fsweetfreestuff&;Free-Garnier-Triple-Nutrition-Sample%2ffeed%2f&ref=comment:927397 •
** Free Sample of Emergen-C - http://p.feedblitz.com/r.asp?l=83792397&f=927397&u=34705849&c=4681558
Sign up to receive free samples of Emergen-C Vitamin Drink Mix.
The post Free Sample of Emergen-C appeared first on SweetFreeStuff.com!.
• Email to a friend • Article Search - http://www.feedblitz.com/f/f.fbz?Search=927397;23433268;Free Food;Free Sample of Emergen-C;4681558 • View comments - http://feeds.feedblitz.com/&;/49722776/0/sweetfreestuff&;Free-Sample-of-EmergenC/ • Track comments - http://www.feedblitz.com/f/f.fbz?Track=http%3a%2f%2ffeeds.feedblitz.com%2f&;%2f49722776%2f0%2fsweetfreestuff&;Free-Sample-of-EmergenC%2ffeed%2f&ref=comment:927397 •
** Reminder: Enter our $100 Amazon Gift Card Giveaway! - http://p.feedblitz.com/r.asp?l=84482265&f=927397&u=34705849&c=4681558
Click below to enter to win a $100 Amazon Gift Card for the holidays from Sweet Free Stuff! Enter the Giveaway Now!!
The post Reminder: Enter our $100 Amazon Gift Card Giveaway! appeared first on SweetFreeStuff.com!.
* Comments
- I WOULD LOVE TO WIN THIS. I WOULD USE IT TO SHOP FOR MY KIDS … by DARLENE EPPS
- Enter the Amazon gift card give away. by Paul McGowan
- It would be nice to win by Darlene Van Meter
- I’m in! Here’s hoping! by Sandra Beeman
- enter????? or exit lol by greg
- Plus 4 more…
• Email to a friend • Article Search - http://www.feedblitz.com/f/f.fbz?Search=927397;23433268;News;Reminder: Enter our $100 Amazon Gift Card Giveaway!;4681558 • View comments - http://feeds.feedblitz.com/&;/50791382/0/sweetfreestuff&;Reminder-Enter-our-Amazon-Gift-Card-Giveaway/ • Track comments - http://www.feedblitz.com/f/f.fbz?Track=http%3a%2f%2ffeeds.feedblitz.com%2f&;%2f50791382%2f0%2fsweetfreestuff&;Reminder-Enter-our-Amazon-Gift-Card-Giveaway%2ffeed%2f&ref=comment:927397 •


Click image to view
This site is dedicated to providing users with the sports information they desire. The content is massive. It provides the user with access to articles, photos, videos, blogs, and much more. Organizing the material in a clear and user-friendly fashion is the visual challenge the site must overcome and I believe they've accomplished that.
Click image to view
Just like CBS Sports, this site provides access to all that's happening in the world of sports. They too have the issue of how to manage the volume of information located on the site. All their info is easily accessible to the user through an abundance of well organized links.
Everything Buckeye! If you're an Ohio State fan, this is the site for you. The site doesn't have near the content volume that the other two sites I've listed has, so it makes for a very easy interaction with the user. It provides a very simple tag at the top for the user to easily view info relating to football, basketball, or recruiting.


Apache Geode uses Apache Log4j 2 as the basis for its logging system.
Geode uses Apache Log4j 2 API and Core libraries as the basis for its logging system. Log4j 2 API is a popular and powerful front-end logging API used by all the Geode classes to generate log statements. Log4j 2 Core is a backend implementation for logging; you can route any of the front-end logging API libraries to log to this backend. Geode uses the Core backend to run two custom Log4j 2 Appenders: AlertAppender and LogWriterAppender.
Geode has been tested with Log4j 2.1.
Note:
For this reason, Geode now always requires the following JARs to be in the classpath: log4j-api-2.1.jar
, log4j-core-2.1.jar
. Both of these JARs are distributed in the $GEMFIRE/lib
directory and included in the appropriate *-dependencies.jar
convenience libraries.
AlertAppender is the component that generates Geode alerts that are then managed by the JMX Management and Monitoring system. See Notification Federation for more details.
LogWriterAppender is the component that is configured by all the log-*
Geode properties such as log-file
, log-file-size-limit
and log-disk-space-limit
.
Both of these appenders are created and controlled programmatically. You configure their behavior with the log-*
Geode properties and the alert level that is configured within the JMX Management & Monitoring system. These appenders do not currently support configuration within a log4j2.xml
config file.
Advanced users may wish to define their own log4j2.xml
. See Advanced Users—Configuring Log4j 2 for Geode for more details.


We bring over 50 years of experience in business strategy, business development, information technology, data analysis and design, data architecture, big data, data warehousing, business intelligence, software development and financial services.
Contact us to learn how you can leverage big data and artificial intelligence in your organization.
We bring over 50 years of experience in the field of business strategy, business development, information technology, data analysis and design, data architecture, big data, data warehousing, business intelligence, software development and financial services.
Technical expertise in data modeling, data analytics and predictive analytics. deep knowledge in data warehouse, data engineering, ETL, reporting and data visualization. developing and maintaining enterprise-wide web based report systems and dashboards for POS, finance, business intelligence and strategy systems.
Experienced in implementing / managing large scale complex projects involving multiple stakeholders, leading and directing multiple project teams. A track record of delivering customer-focused, well-architected, quality projects on time, while adapting to shifting and conflicting demands and priorities. Experience in Data Warehouse / Business Intelligence developments, implementation and operation setup.
Swing by for a cup of coffee.
1607 Ponce de Leon Blvd, Suite 202, Coral Gables, FL 33134


4. Best Practice¶
This section explains to users the best practice in configuring a Simulator XML input file, and implementing the Python wrapper which will interface with the Simulator.
4.1. Configuring and Generating the Python Binaries¶
This option has been added starting from Python 3.8. To export a Simulator that wraps a Python script as an FMU, the user needs to configure files that are needed to create binaries for the targeted Python version.
This can be done by editing the
systemVariables-windows.properties
(Windows) or systemVariables-linux.properties
(Linux)
files. These files are located under parser/makLib
folder.
First, The user is required to provide the path to the following folders:
PYTHON_EXE_DIR
. This is the path to the Python executable directory (e.g.D:\programs\Anaconda3
)CMD_TOOL
. This is the path to the build tools needed to compile the Python/C interface (e.g.C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\msbuild.exe
)
Next, the user is required to run the createlib.py
that is located in parser/makLib
folder by
running the following command:
> python parser/makLib/createlib.py -pv <python-version>
where python-version
is the targeted Python version (e.g. 38
for Python 3.8).
This command will invoke the build tools that will create the Python binaries and copied them in the
appropriate Modelica library folder (parser\libraries\modelica\SimulatorToFMU\Resources\Library
).
The created python binaries will be embedded in the FMU when the FMU will be created (see Creating an FMU).
4.2. Configuring the Simulator XML input file¶
To export a Simulator as an FMU, the user needs to write an XML file which contains the list
of inputs, outputs and parameters of the FMU. The XML snippet below shows how a user has to write such an input file.
A template named SimulatorModeldescritpion.xml
which shows such a file is provided in the parser/utilities
installation folder of SimulatorToFMU.
This template should be adapted to create new XML input file.
The following snippet shows an input file where the user defines 1 input and 1 output variable.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | <?xml version="1.0" encoding="UTF-8"?>
<SimulatorModelDescription
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
fmiVersion="2.0"
modelName="simulator"
description="Input data for a Simulator FMU"
generationTool="SimulatorToFMU">
<ModelVariables>
<ScalarVariable
name="_configurationFileName"
description="parameter"
causality="parameter"
start="C:/Users/Public/server_config.txt"
type="String">
</ScalarVariable>
<ScalarVariable
name="v"
description="Voltage"
causality="input"
type="Real"
unit="V"
start="0.0">
</ScalarVariable>
<ScalarVariable
name="i"
description="Current"
causality="output"
type="Real"
unit="A">
</ScalarVariable>
</ModelVariables>
</SimulatorModelDescription>
|
To create such an input file, the user needs to specify the name of the FMU (Line 5).
This is the modelName
which should be unique.
The user then needs to define the inputs and outputs of the FMUs.
This is done by adding a ScalarVariable
into the list of ModelVariables
.
To parametrize the ScalarVariable
as an input variable, the user needs to
- define the name of the variable (Line 10),
- give a brief description of the variable (Line 11)
- give the causality of the variable (
input
for inputs,output
for outputs) (Line 12)- define the type of variable (Currently only
Real
variables are supported) (Line 13)- give the unit of the variable (Currently only Modelica units are supported) (Line 14)
- give a start value for the input variable (This is optional) (Line 15)
To parametrize the ScalarVariable
as an output variable, the user needs to
- define the name of the variable (Line 18),
- give a brief description of the variable (Line 19)
- give the causality of the variable (
input
for inputs,output
for outputs) (Line 20)- define the type of variable (Currently only
Real
variables are supported) (Line 21)- give the unit of the variable (Currently only Modelica units are supported) (Line 22)
Note
If Modelica units can’t be used (Line 14 and Line 22), then remove the unit field from the input file
when defining new ScalarVariable
.
4.3. Configuring the Python Wrapper Simulator¶
To export a Simulator as an FMU, the user needs to write the Python wrapper which will interface with the Simulator. The wrapper will be embedded in the FMU when the Simulator is exported and used at runtime on the target machine.
The user needs to extend the Python wrapper provided in parser/utilities/simulator_wrapper.py
and implements the function exchange()
.
Line 1 to Line 19 represents a dummy Simulator written in Python.
This simulator implements a doTimeStep()
method that gets some input values and increment the value by one.
Line 22 to Line 84 represents the exchange
function that provides a FMI interface to the Simulator.
The inputs (Line 22) and return arguments (Line 81) of the exchange()
function should not be modified.
The remaining body of the function should be customized so it can invoke the python Simulator when needed.
In this specific case, it is assumed that the Python Simulator has memory.
Line 55 checks if a memory object exists.
Line 57 initializes the Simulator by passing the parameters received through the FMI interface.
Line 60 initializes memory object.
Line 62 stores the initial input values.
Line 64 initializes the output values by calling the “doTimeStep()” of the Simulator.
Line 66 stores the memory object
Line 67 activates the branch which is invoked during time stepping where simulation data are exchanged with the Simulator through the FMI interface.
Line 71 checks if time has changed since the last invocation prior to updating the outputs.
Line 73 invokes the “doTimeStep()” method of the Simulator to update the outputs.
Line 75 to Line 77 save the last simulation time as well as the latest input values and updated output values.
Line 79 checks the validity of the output values.
Line 82 stores the output values that will then be returned on Line 84 along with the memory object.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 | # Dummy Python-driven simulator
class Simulator():
"""
Dummy simulator Python-driven simulator
which increments in its doTimeSteo method the input values by 1.
This class is for illustration purposes only.
"""
def __init__(self, configuration_file, time, input_names,
input_values, output_names, write_results):
self.configuration_file = configuration_file
self.input_values = input_values
def doTimeStep(self, input_values):
"""
This function increments the input variables by 1
"""
return input_values + 1
# Main Python function to be modified to interface with a simulator which has memory.
def exchange(configuration_file, time, input_names,
input_values, output_names, write_results,
memory):
"""
Return a list of output values from the Python-based Simulator.
The order of the output values must match the order of the output names.
:param configuration_file (String): Path to the Simulator model or configuration file
:param time (Float): Simulation time
:param input_names (Strings): Input names
:param input_values (Floats): Input values (same length as input_names)
:param output_names (Strings): Output names
:param write_results (Integers): Store results to file (1 to store, 0 else)
:param memory: Variable that stores the memory of a Python object
"""
#######################################################################
# EDIT AND INCLUDE CUSTOM CODE FOR TARGET SIMULATOR
# Include body of the function used to compute the output values
# based on the inputs received by the simulator function.
# This will need to be adapted so it returns the correct output_values.
# If the list of output names has only one name, then only a scalar
# must be returned.
# The snippet shows how a Python object should be held in the memory
# This is done by getting the object from the exchange function, modifying it,
# and returning it.
########################################################################
# Since master algorithms need to some time call at the same time instant
# an FMU multiple times for event iteration. It is for efficient reasons
# good to catch the simulator input and outputs results, along with the current
# and past simulation times to determine when the Simulator needs to be reinvoked.
if memory == None:
# Initialize the Simulator object
s = Simulator(configuration_file, time, input_names,
input_values, output_names, write_results)
# create the memory object
memory = {'memory':s, 'tLast':time, 'outputs':None}
# get and store the initial inputs
memory['inputsLast'] = input_values
# get and store the initial outputs
memory['outputs'] = s.doTimeStep(input_values)
# store the memory object
memory['s'] = s
else:
# The assumption is that inputs are changed at every invocation of the exchange function
# For efficiency reasons, it is recommended to extend the code to check whether the output values need to be updated.
# Update the outputs of the Simulator if time has advanced
if(abs(time - memory['tLast'])>1e-6):
# Update the outputs
memory['outputs'] = memory['s'].doTimeStep(memory['outputs'])
# Save last time
memory['tLast'] = time
# Save last input values
memory['inputsLast'] = input_values
# Handle errors
if(memory['outputs'] < 0.0):
raise("The memory['outpus'] cannot be null")
# Save the outputs of the Simulator
output_values = memory['outputs']
#########################################################################
return [output_values, memory]
|
The arguments of the exchange
function are in the next table
| Arguments | Description |
|---|---|
configuration_file |
The Path to the Simulator model or configuration file |
time |
The current simulation model time |
input_names |
The list of input names of the FMU |
input_values |
The list of input values of the FMU |
output_names |
The list of output names of the FMU |
output_values |
The list of output values of the FMU |
write_results |
A flag for writing the simulation results to a file located in the working directory of the importing tool. |
memory |
A variable that holds the memory of a Python object This argument is required only if the simulator has variables which have memory. |
If the simulator does not have memory, then the function exchange
will be defined as
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 | # Dummy Python-driven simulator
class Simulator():
"""
Dummy simulator Python-driven simulator
which increments in its doTimeStep method the input values by 1.
This class is for illustration purposes only.
"""
def __init__(self, configuration_file, time, input_names,
input_values, output_names, write_results):
self.configuration_file = configuration_file
self.input_values = input_values
def doTimeStep(self, input_values):
"""
This function increments the input variables by 1
"""
return input_values + 1
# Main Python function to be modified to interface with a simulator which has memory.
def exchange(configuration_file, time, input_names,
input_values, output_names, write_results):
"""
Return a list of output values from the Python-based Simulator.
The order of the output values must match the order of the output names.
:param configuration_file (String): Path to the Simulator model or configuration file
:param time (Float): Simulation time
:param input_names (Strings): Input names
:param input_values (Floats): Input values (same length as input_names)
:param output_names (Strings): Output names
:param write_results (Integers): Store results to file (1 to store, 0 else)
"""
#######################################################################
# EDIT AND INCLUDE CUSTOM CODE FOR TARGET SIMULATOR
# Include body of the function used to compute the output values
# based on the inputs received by the simulator function.
# This will need to be adapted so it returns the correct output_values.
# If the list of output names has only one name, then only a scalar
# must be returned.
########################################################################
# # Initialize the Simulator object
s = Simulator(configuration_file, time, input_names,
input_values, output_names, write_results)
# check if we have input values. If yes, update the outputs.
if not (input_values is None):
output_values=s.doTimeStep(input_values)
else:
# Return default output value
output_values = 1.0
# Save the output of the Simulator
#########################################################################
return output_values
|
Note
- The function
exchange
must return a list of output values which matches the order of the output names. - If the simulator has memory, then the function
exchange
must also return the memory. - The function
exchange
can be used to invoke external programs/scripts which do not ship with the FMU. The external programs/scripts will have to be installed on the target machine where the FMU is run. See Creating an FMU for details on command line options. - Once
simulator_wrapper.py
is implemented, it must be saved under a name of the form"modelname"
+"_wrapper.py"
, and its path used as required argument forSimulatorToFMU.py
.


This appendix describes the XML format for importing data into and exporting data out of Proximity. In addition to handling complete databases, Proximity can import and export individual attributes and containers. Users are solely responsible for ensuring that imported attribute and container data correctly matches the identifiers and data types in the existing database.
The DTD
for the Proximity XML format is located in
$PROX_HOME/resources/prox3db.dtd
.
The examples in this appendix are designed to illustrate the relevant XML syntax and are not intended to represent, in whole or in part, a valid or semantically meaningful database.
The XML data file must start with the following XML declaration:
<?xml version="1.0" encoding="UTF-8"?>
The document type declaration immediately follows the XML declaration. The XML data file must include the following document type declaration:
<!DOCTYPE PROX3DB SYSTEM "prox3db.dtd">
Note that the document type declaration uses a system identifier
for the DTD. Proximity expects to find the
prox3db.dtd
file in the same directory as the XML
data file.


LZ(1) Mtools Users Manual LZ(1) NAME lz - gunzips and shows a listing of a gzip'd tar'd archive SYNOPSIS lz file DESCRIPTION lz provides a listing of a gzip'd tar'd archive, that is a tar(1) archive compressed with the gzip(1) utility. It is not strictly necessary on Debian GNU/Linux, because the GNU tar(1) program provides the same capa‐ bility with the command tar -tzf file but this utility is provided in the mtools package for other platforms and is retained here for completeness. AUTHOR Robert King<EMAIL_ADDRESS>wrote this page for the Debian/GNU mtools package. SEE ALSO mtools(1), gzip(1), tar(1), uz(1). Wed Feb 23 00:00:00 EET 2000 LZ(1)


Choose two contacts by searching and click Merge. Any missing information in the second contact will be filled in from the first. The first contact will then be deleted.


Understandability
We used taxi data from Dresden in order to show alternative tracks that people are using from our project : ExCELL.
You can click on the map to create markers on the map
Then choose if you want an easy or complex or both understanding of the tracks
Change the parameters and click on Find my Way !
You will get some help on your right !
You can only add 5 points
No result sorry...


under construction...
"Serving Regina for 20 years"
Call#<PHONE_NUMBER>
City Cartage Service
55 per hour
55 per hour
Limo and Party Bus Service
55 per hour
125 single drop
80 per hour (3 hours minimum)
125 single drop


Obtaining an identification code
- Preparation of documents
- Legal support in Tax office
Price:
50$
Company registration
- Preparation of constituent documents
- Notary certification of documents
- Company registration in registration authorities
- Company registration in statistical bodies
- Company registration in tax office
- Making seal
Price:
200$
Company registration
- Legal support with paperwork for getting work permit
Price:
185$
- Notarized translation of the passport
Price:
12$
Price:
for one year - 272$;
for three years - 410$
Temporary residence permit in Ukraine (TRP)
- Legal support with paperwork for getting TRP
- Legal support in Migration Service
- Obtaining TRP
Price:
185$
- Notarized translation of the passport
Price:
12$
Registration your address in Kiev


{{ with .Page.Params.second_block_title }}{{ . }}{{ end }}
Your full name *
Your E-Mail *
Your phone number *
Brand name *
Company Revenue (past 12 months) *
Tell us more about your Company
Not sure if you’re ready to sell yet? We’re happy to answer any questions you might have. Reach out to us at<EMAIL_ADDRESS>{{ end }}


|
Cannon Cpp
1.0.0
|
#include "cannon/world/Narrowphase.h"
#include "cannon/utils/TupleDictionary.h"
#include "cannon/equations/ContactEquation.h"
#include "cannon/equations/FrictionEquation.h"
#include "cannon/shapes/Shape.h"
#include "cannon/shapes/Box.h"
#include "cannon/shapes/Plane.h"
#include "cannon/shapes/Sphere.h"
#include "cannon/shapes/Particle.h"
#include "cannon/shapes/Trimesh.h"
#include "cannon/shapes/Heightfield.h"
#include "cannon/shapes/ConvexPolyhedron.h"
#include "cannon/objects/Body.h"
#include "cannon/world/World.h"
#include "cannon/material/Material.h"
#include "cannon/material/ContactMaterial.h"
#include <unordered_map>
Macros | |
| #define | DEFINE_NARROW_PHASE_SOLVER_FUN(func) |
| #define | NARROW_PHASE_SOLVER_FUN(func) onSolve_##func |
Typedefs | |
| using | SolverFunc = bool(*)(Narrowphase *, Shape *, Shape *, Vec3 &, Vec3 &, Quaternion &, Quaternion &, Body *, Body *, Shape *, Shape *, bool) |
Variables | |
| static const std::unordered_map< int, SolverFunc > | __solverMap |
| #define DEFINE_NARROW_PHASE_SOLVER_FUN | ( | func | ) |
| #define NARROW_PHASE_SOLVER_FUN | ( | func | ) | onSolve_##func |
| using SolverFunc = bool (*)(Narrowphase*, Shape*, Shape*, Vec3&, Vec3&, Quaternion&, Quaternion&, Body*, Body*, Shape*, Shape*, bool) |
|
static |


bool pg_put_line ([ resource $connection ], string $data )
pg_put_line() sends a NULL-terminated string to the PostgreSQL backend server. This is needed in conjunction with PostgreSQL's COPY FROM command. COPY is a high-speed data loading interface supported by PostgreSQL. Data is passed in without being parsed, and in a single transaction. An alternative to using raw pg_put_line() commands is to use pg_copy_from(). This is a far simpler interface. Note: The application must explicitly send the two characters "\." on the last line to indicate to the backend that it has finished sending its data, before issuing pg_end_copy(). Warning Use of the pg_put_line() causes most large object operations, including pg_lo_read() and pg_lo_tell(), to subsequently fail. You can use pg_copy_from() and pg_copy_to() instead.
Returns TRUE on success or FALSE on failure.


XAU/USD: Gold retreats from weekly highs, drops to $1465
by Matías Salord- Yellow metal reverses and falls to test yesterday’s low.
- Limited volatility across financial markets as traders await for the FOMC minutes.
Gold weakened from the highest level in almost two weeks slightly below $1480/oz and moved lower. Recently it printed a fresh daily low at $1465, just cents above Tuesday’s low.
The intraday bias points to the downside. Traders await the release of the FOMC minutes from the latest meeting that could trigger some volatility. Price action across financial markets remains calm with the US dollar rising modestly and bond yields steady.
Equity prices in Wall Street are mostly lower showing little changes. The Dow Jones drops 0.25% and the S&P 500 0.08%, affected by concerns on the impact on US/China trade talks of the recent Hong Kong resolution passed by the US Senate. Those concerns initially boosted XAU/USD to the $1480 area but then it reversed.
Technical outlook
In the short-term, gold is still moving with an upside bias, but the momentum is starting to favor the downside. Price needs to recover levels on top of $1472 in order to target again a test of the $1480 area. Above the next strong resistance is seen at $1490.
On the flip side, a consolidation under $1464 would likely increase the bearish pressure ahead of the Asian session. The next support is located at $1455 (Nov 18 low) followed by $1445 (November low).
XAU/USD
| Overview | |
|---|---|
| Today last price | 1469.11 |
| Today Daily Change | -3.38 |
| Today Daily Change % | -0.23 |
| Today daily open | 1472.49 |
| Trends | |
|---|---|
| Daily SMA20 | 1483.7 |
| Daily SMA50 | 1491.93 |
| Daily SMA100 | 1480.71 |
| Daily SMA200 | 1395.85 |
| Levels | |
|---|---|
| Previous Daily High | 1475.43 |
| Previous Daily Low | 1465.08 |
| Previous Weekly High | 1474.6 |
| Previous Weekly Low | 1445.8 |
| Previous Monthly High | 1519.04 |
| Previous Monthly Low | 1455.5 |
| Daily Fibonacci 38.2% | 1471.47 |
| Daily Fibonacci 61.8% | 1469.03 |
| Daily Pivot Point S1 | 1466.57 |
| Daily Pivot Point S2 | 1460.64 |
| Daily Pivot Point S3 | 1456.21 |
| Daily Pivot Point R1 | 1476.92 |
| Daily Pivot Point R2 | 1481.35 |
| Daily Pivot Point R3 | 1487.28 |


The next release of WebPlotDigitizer is around the corner and there is an exciting new addition this time: We will finally have dedicated tools to extract data from bar charts and histograms! I am still doing some final checks before the release, but you can try it out with the beta version that is available here:
http://arohatgi.info/WebPlotDigitizer/beta
Bar Charts vs. Histograms
Most bar charts have a continuous axis along the data, but only a discrete set of labels that correspond to each bar on the other axis. Keeping this in mind, a completely new plot type and an extraction algorithm has been added for bar charts. For the charts where both the axes are continuous (e.g. histograms), you can still use the 2D (X-Y) plot type, but a new algorithm is now available to help with bar charts. I will first describe the extraction process for simple bar charts followed by the process for histograms.
Bar Charts
Just select the "2D Bar Plot" option after loading the image. You will be prompted to select two points on the axis that is along the bars. For horizontal bar charts, pick the two points on the X-axis.
After picking two points on the axis, specify the values at those two points. Select the "Log Scale" option if the data is in log-scale.
You can manually click to specify data, or if you want to do automatic extraction, then do the color selection part just as you would for any other plot type in WebPlotDigitizer. (If you are unfamiliar with WebPlotDigitizer, then please refer to the tutorials section)
The auto-extraction algorithm options are now context sensitive and so you will see only one extraction algorithm called "Bar Extraction". Adjust the two parameters (delta_X or delta_Y and delta_Val) until you see that only one point is detected per bar.
Once you have the data points, you might want to change the labels assigned to each data point (Bar0, Bar1, etc.). Just switch to manual mode and select the "Edit Labels" tool and click on the data point you wish to change the label for. This may get a little repetitive for a large number of data points, so you might want to do this later in your data analysis tool.
Finally, just click "View Data" to view and export data points to a CSV file or Plotly. You can also export data to a JSON file from the File menu.
Histograms
While most bar charts can be digitized using the above method, it might be too tedious to work with bar charts where both axis are continuous and the "labels" for each bar is just a value on an axis. For these charts, you can just select 2D (X-Y) plot type at the start and calibrate the axis as you would for any other 2D X-Y plot in WebPlotDigitizer.
The manual work should work just like it does for any other XY plot, but in the automatic mode, you will now have a new algorithm called "Histograms". This works almost exactly like the algorithm for bar charts above and you can simply adjust the two parameters until you get the desired results like you would in the above case. There are no labels for each data point to edit in this case.
Finally, just click "View Data" to view or export the extracted data.
This is just a first implementation for bar charts and you can expect these features and algorithms to be refined over time. Suggestions for improvements are quite welcome!


--- layout: post permalink: allevol.html Tags: Array NameOfCoupon: Allevol Cash Back Summary: See our Allevol Coupon Code, Allevol Rebate, Allevol Promo Code, Allevol Discount, Allevol Coupon Cash Back Rebate here. MetaKeywords: Allevol Coupon Code, Allevol Rebate, Allevol Promo Code, Allevol Cash Back Rebate, Allevol Discount, Allevol Coupon Image: images/26151.jpg LinkURL: http://www.shareasale.com/r.cfm?b=217148&u=412002&m=26151 affiliate_url_link: http://www.icouponblog.com/jane.php?id=343 thesis_readmore: See the Allevol Coupon thesis_thumb: http://www.icouponblog.com/tn.php?merchantURL=allevol.com Title: Save 4% - Allevol Coupon Code for allevol.com. Allevol Rebate & Discount thesis_description: Our Allevol Discount Coupon Code for allevol.com. We have the best Allevol Rebate anywhere. thesis_keywords: Allevol, Allevol Coupon Code, Allevol Discount, Allevol Rebate product_name: Allevol hop_url: http://www.icouponblog.com/hop.php?id=343 ---
Japanese denim jeans from Allevol are the pair to have. Made from Japanese raw or selvedge denim, these jeans are produced with the finest materials, hand-crafted by denim specialists in trusted traditional Japanese methods. The Allevol Japanese selvedge raw denim fabrics are made by old woven shuttle looms for natural fade, as well as excellent durability. The jeans are made in Okayama, sewn by vintage Union machines for an authentic finish. You will love these Japanese denim jeans, they are a class in themselves, check them out on Allevol right now. You will fall in love with the texture, the color of the Japanese denim. Use our discount coupon to buy a pair today!
Allevol is an independent clothing label which is immersed in the culture of Japanese raw denim products. Allevol also has a variety of t-shirts. Look for comfortable, great quality, attractive t-shirts that have creative designs and written material like ‘Money grows’, ‘You are what you own’ ‘Waste yourself’ These t-shirts are all manufactured and printed in European Communities. Allevol Japanese denim jeans will go great with the Allevol European t-shirt. Check it out online on Allevol.com
Allevol also carries great accessories. You can buy beautiful , suede braided belt for your jeans among other things. Check out Allevol online today and get the vintage jeans or any other Allevol Japanese denim jeans and feel the difference. Allevol has quality, class, culture and good taste written all over it. Use our cash back rebate coupon for the best deals on Allevol Japanese denim jeans, or t-shirts and accessories.


init({
range: [ [-1, 12 ], [ -10, 2.5 ] ]
})
var tr = new Triangle( [ 2, -2], MAIN, [ 1, 1, 1], 3, { "name" : "A", "CAB" : MAIN[ 0 ] , "BCA" : MAIN[ 2 ] } );
tr.draw();
tr.rotate( randRange( 0, 50 ), 2, -1 );
tr.drawLabels();
var trA = new Triangle( [ 5, -5 ], B, [ 1, 1, 1], randRange( 300, 500 )/100, { "name" : "B", "CAB" : B[ 0 ], "ABC" : B[ 1 ] } );
trA.draw();
trA.rotate( randRange( 0, 50 ), 4, -6 );
trA.drawLabels();
var trB = new Triangle( [ 1, -8 ], C, [ 1, 1, 1], randRange( 300, 500 )/100, { "name" : "C", "CAB" : C[ 0 ], "BCA" : C[ 2 ] } );
trB.draw();
trB.rotate( randRange( 0, 50 ), 5, -8 );
trB.drawLabels();
Two triangles are similar if their three angles correspond.
We see that Triangle A
has angles of MAIN[ 0 ]
and MAIN[ 2 ]
. The third angle is therefore 180 - MAIN[ 0 ] - MAIN[ 2 ] = MAIN[ 1 ]
Triangle B
has angles of B[ 0 ]
and B[ 1 ]
. The third angle is therefore 180 - B[ 0 ] - B[ 1 ] = B[ 2 ]
. Therefore triangle
is not similar to triangle
.
Triangle C
has angles of C[ 0 ]
and C[ 2 ]
. The third angle is therefore 180 - C[ 0 ] - B[ 2 ] = C[ 1 ]
. Therefore triangle C
is not similar to triangle A
.


/*
* ====================================================================
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
* ====================================================================
*
* This software consists of voluntary contributions made by many
* individuals on behalf of the Apache Software Foundation. For more
* information on the Apache Software Foundation, please see
* <http://www.apache.org/>.
*
*/ /*...*/ |
||
| 27 | package org.apache.http.impl.client.cache; |
|
|
||
/**
*

* {@link HttpCacheStorage} implementation capable of deallocating resources associated with
* the cache entries.
*

* This cache keeps track of cache entries using
* {@link java.lang.ref.PhantomReference} and maintains a collection of all resources that
* are no longer in use. The cache, however, does not automatically deallocates associated
* resources by invoking {@link Resource#dispose()} method. The consumer MUST periodically
* call {@link #cleanResources()} method to trigger resource deallocation. The cache can be
* permanently shut down using {@link #shutdown()} method. All resources associated with
* the entries used by the cache will be deallocated.
*

*

* This {@link HttpCacheStorage} implementation is intended for use with {@link FileResource}
* and similar.
*

*

* Compatibility note. Prior to version 4.4 this storage implementation used to dispose of
* all resource entries upon {@link #close()}. As of version 4.4 the {@link #close()} method
* disposes only of those resources that have been explicitly removed from the cache with
* {@link #removeEntry(String)} method.
*

*

* The {@link #shutdown()} ()} method can still be used to shut down the storage and dispose of
* all resources currently managed by it.
*

*
* @since 4.1
*/ /*...*/ |
||
| 73 | @ThreadSafe |
|
| 74 | public class ManagedHttpCacheStorage implements HttpCacheStorage, Closeable { |
|
| 76 | private final CacheMap entries; |
|
| 77 | private final ReferenceQueue<HttpCacheEntry> morque; |
|
| 78 | private final Set<ResourceReference> resources; |
|
| 79 | private final AtomicBoolean active; |
|
| 81 | public ManagedHttpCacheStorage(final CacheConfig config) { |
|
| 82 | 1 | super(); |
| 83 | 1 | this.entries = new CacheMap(config.getMaxCacheEntries()); |
| 84 | 1 | this.morque = new ReferenceQueue<HttpCacheEntry>(); |
| 85 | 1 | this.resources = new HashSet<ResourceReference>(); |
| 86 | 1 | this.active = new AtomicBoolean(true); |
| 87 | 1 | } |
| 89 | private void ensureValidState() throws IllegalStateException { |
|
| 90 | 8 | if (!this.active.get()) {
|
| 91 | 0 | throw new IllegalStateException("Cache has been shut down"); |
| 92 | } |
|
| 93 | 8 | } |
| 95 | private void keepResourceReference(final HttpCacheEntry entry) { |
|
| 96 | 1 | final Resource resource = entry.getResource(); |
| 97 | 1 | if (resource != null) {
|
| 98 | // Must deallocate the resource when the entry is no longer in used |
|
| 99 | 1 | final ResourceReference ref = new ResourceReference(entry, this.morque); |
| 100 | 1 | this.resources.add(ref); |
| 101 | } |
|
| 102 | 1 | } |
| 104 | @Override |
|
| 105 | public void putEntry(final String url, final HttpCacheEntry entry) throws IOException { |
|
| 106 | 1 | Args.notNull(url, "URL"); |
| 107 | 1 | Args.notNull(entry, "Cache entry"); |
| 108 | 1 | ensureValidState(); |
| 109 | 1 | synchronized (this) { |
| 110 | 1 | this.entries.put(url, entry); |
| 111 | 1 | keepResourceReference(entry); |
| 112 | 1 | } |
| 113 | 1 | } |
| 115 | @Override |
|
| 116 | public HttpCacheEntry getEntry(final String url) throws IOException { |
|
| 117 | 7 | Args.notNull(url, "URL"); |
| 118 | 7 | ensureValidState(); |
| 119 | 7 | synchronized (this) { |
| 120 | 7 | return this.entries.get(url); |
| 121 | 0 | } |
| 122 | } |
|
| 124 | @Override |
|
| 125 | public void removeEntry(final String url) throws IOException { |
|
| 126 | 0 | Args.notNull(url, "URL"); |
| 127 | 0 | ensureValidState(); |
| 128 | 0 | synchronized (this) { |
| 129 | // Cannot deallocate the associated resources immediately as the |
|
| 130 | // cache entry may still be in use |
|
| 131 | 0 | this.entries.remove(url); |
| 132 | 0 | } |
| 133 | 0 | } |
| 135 | @Override |
|
| 136 | public void updateEntry( |
|
| 137 | final String url, |
|
| 138 | final HttpCacheUpdateCallback callback) throws IOException { |
|
| 139 | 0 | Args.notNull(url, "URL"); |
| 140 | 0 | Args.notNull(callback, "Callback"); |
| 141 | 0 | ensureValidState(); |
| 142 | 0 | synchronized (this) { |
| 143 | 0 | final HttpCacheEntry existing = this.entries.get(url); |
| 144 | 0 | final HttpCacheEntry updated = callback.update(existing); |
| 145 | 0 | this.entries.put(url, updated); |
| 146 | 0 | if (existing != updated) {
|
| 147 | 0 | keepResourceReference(updated); |
| 148 | } |
|
| 149 | 0 | } |
| 150 | 0 | } |
| 152 | public void cleanResources() { |
|
| 153 | 0 | if (this.active.get()) {
|
| 154 | ResourceReference ref; |
|
| 155 | 0 | while ((ref = (ResourceReference) this.morque.poll()) != null) {
|
| 156 | 0 | synchronized (this) { |
| 157 | 0 | this.resources.remove(ref); |
| 158 | 0 | } |
| 159 | 0 | ref.getResource().dispose(); |
| 160 | } |
|
| 161 | } |
|
| 162 | 0 | } |
| 164 | public void shutdown() { |
|
| 165 | 0 | if (this.active.compareAndSet(true, false)) {
|
| 166 | 0 | synchronized (this) { |
| 167 | 0 | this.entries.clear(); |
| 168 | 0 | for (final ResourceReference ref: this.resources) { |
| 169 | 0 | ref.getResource().dispose(); |
| 170 | 0 | } |
| 171 | 0 | this.resources.clear(); |
| 172 | 0 | while (this.morque.poll() != null) {
|
| 173 | } |
|
| 174 | 0 | } |
| 175 | } |
|
| 176 | 0 | } |
| 178 | @Override |
|
| 179 | public void close() { |
|
| 180 | 0 | if (this.active.compareAndSet(true, false)) {
|
| 181 | 0 | synchronized (this) { |
| 182 | ResourceReference ref; |
|
| 183 | 0 | while ((ref = (ResourceReference) this.morque.poll()) != null) {
|
| 184 | 0 | this.resources.remove(ref); |
| 185 | 0 | ref.getResource().dispose(); |
| 186 | } |
|
| 187 | 0 | } |
| 188 | } |
|
| 189 | 0 | } |
| 191 | } |


Alibaba raises up to $17.6 billion in landmark Hong Kong IPO
HONG KONG : Chinese e-commerce giant Alibaba Group raised up to US$12.9 billion (S$17.6 billion) in a landmark listing in Hong Kong.
It is the largest share sale in the city in nine years and a world record for a cross-border secondary share sale.
The deal will be seen as a boost to Hong Kong, following more than five months of anti-government protests and its recent slide into its first recession in a decade.
Alibaba confirmed it had priced the shares at HK$176 (S$30.63) each, a discount of 2.9 per cent to its New York closing price. This means Alibaba will raise at least HK$88 billion - a symbolic total as the number 8 is associated with prosperity and good fortune in Chinese culture.
Alibaba has also chosen the stock code 9988 for its listing, which for Chinese speakers combines two of the luckiest numbers, together symbolising long-lasting prosperity.
The total raised from the deal could eventually reach US$12.9 billion if a so-called "greenshoe" over-allotment option were exercised.
Alibaba shares closed in New York on Tuesday at US$185.25. One of Alibaba's New York-listed American Depositary Shares is worth eight of its Hong Kong shares. - REUTERS


SEX ATTACK SUSPECT
Teenage boy arrested over ‘rape’ of 14-year-old girl in Glasgow
by Connor BoylanA TEENAGE boy has been arrested following the alleged rape of a 14-year-old girl in Glasgow.
Cops launched an investigation into the alleged serious sexual assault on the schoolgirl, which is said to have taken place in the Royston area on Saturday.
And officers have now confirmed a 16-year-old boy has been arrested in connection with the alleged incident.
A Police Scotland spokeswoman said: "Officers are carrying out enquiries after receiving a report of a 14-year-old girl having been seriously sexually assaulted in the Royston area of Glasgow on Saturday, November 16.
"A 16-year-old male youth has been arrested in connection with the incident and enquiries are ongoing."
In an unrelated incident, we told earlier how a brute whose girlfriend took her own life after he injured her has been revealed as the drug dealer who supplied another tragic teen with ecstasy.
Lewis Reid, 22, known as Gucci, sold the Class A substance to friends of Chelsea Bruce, who took ill and died after taking some.
Reid earlier left partner Codey Brown, 18, seriously hurt after accelerating away while she was leaning into his car.
The popular dance student was found dead months later.
A court heard how Reid supplied drugs to a group of youngsters who then took them at a house in the city's Springburn area.
Tragic Chelsea suffered a fit and fell unconscious before being taken by ambulance to Glasgow Royal Infirmary, where she died.


The log2net console application reads data from binary faceLAB/DSS log file(s) and then sends it to a network host using UDP.
To use the supplied version of log2net, run it with the arguments:
- Dir: Source of the logfile(s) to send. The tool will merge the .fll files within the folder into network packets and send them over the network. Note that the folder must contain exactly one set of faceLAB/DSS logfiles (i.e. one timing data file, etc).
- Hostname or IP Address: An optional argument for the host to send to. The default is localhost.
- Port number: An optional argument for the UDP port to send to. The default is 2001, although it can be any port in the range 2000 - 5000
This application is good for testing code that reads from the network, without having to run faceLAB/DSS all the time, since you can run your client, then run log2net and see if the client is reading the data OK.
Example 1:
log2net c:/data/subject23 2044
Merges the data from the logfiles in c:/data/subject23, and send the resulting packets to localhost, port 2044.
Example 2:
log2net c:/data/subject42 simulator.local
Merges the data from the logfiles in c:/data/subject42, and send the resulting packets to simulator.local, port 2001.
This application is mainly useful for testing some of the other applications. Modify the source file examples/log2net/log2net.cpp as you require, remembering that it may change when a new API is released.
The net2log console application reads UDP data from a specified port and saves it to disk.
To use the supplied version of net2log, run it with the arguments:
- Directory: The location to store the logged data. The data is logged into multiple logfiles with one logfile for each faceLAB/DSS output data type. For instance, in the case of faceLAB the network data is logged into 5 separate logfiles. The files created during logging over the network are exactly the same as the files created while logging to disk.
- Port number: An optional argument for the UDP port to receive from. The default is 2001, although it can be any port in the range 2000 - 5000
This application is useful if you want to quickly verify that network data is being received correctly. Be sure to stop logging in faceLAB before stopping the net2log client using Ctrl-C. Note that the logfile is saved in binary form.
Example 1:
Saves any data received from a faceLAB/DSS system on port 2001 to c:/test_data.
Example 2:
net2log c:/test_data 3001
Saves any data received from a faceLAB/DSS system on port 3001 to c:/test_data.
This application is mainly useful for testing some of the other applications. Modify the source file examples/net2log/net2log.cpp as you require, remembering that it may change when a new API is released.
The file logconverter.cpp converts binary logfile data into text format. The tool converts the specified logfile, or a list of the logfiles into a text version in the same folder. Text logfiles are column formatted, allowing them to be easily read into MATLAB or EXCEL.
To use the supplied version of logconverter, run it with the argument:
- Filename(s): The logfile to convert, which must end in .fll
Example 1:
Converts test.fll to test.txt.
Example 2:
logconverter c:/faceLAB/logfiles/head.fll
Converts head.fll to text and saves in the c:/faceLAB/logfiles folder.
Example 3:
logconverter test.fll head.fll eyes.fll
Converts multiple files into the text format in one go.
To minimize the changes you have to make when a new version of the API is released, we donít recommend you change this application. It requires editing several of the core library files. If you do choose to modify this code (for example to only save a subset of the columns), try to make minimal changes and document these changes.
The program receives faceLAB/DSS packets transmitted over a serial port. The serial packet format and protocol is specified in Section 10 of this document.
To use the supplied version of serialreceive, run it with the optional argument:
- Serial port: The port to send to, from COM1 to COM4 (Default is COM2). Note that faceLAB uses COM1 to control analog Sony cameras, so if your faceLAB is equipped with analog Sony cameras, specifying COM1 will not work on the same computer.
Example 1:
Runs serialreceive, receiving packets from COM2
Example 2:
Runs serialreceive, receiving packets from COM1
This project is designed for easy modification. The best place to modify the application is in the function handleEngineOutputData In this function, the data has already been read from the serial port and placed in the appropriate EngineOutputData structure.
The serial2log console application reads serial data from a specified serial port and saves it to disk
To use the supplied version of seria2log, run it with the arguments:
- Directory: The location to store the logged data. The data is logged into multiple logfiles with one logfile for each faceLAB/DSS output data type. For instance, in the case of DSS the serial data is logged into 4 separate logfiles.
- Port number: An optional argument for the serial port to receive from. The default is COM2, although it can be any port in the range COM1 to COM8
This application is useful if you want to quickly verify that serial data is being received correctly. Be sure to stop logging in faceLAB/DSS before stopping the serial2log client using Ctrl-C. Note that the logfile is saved in binary form.
Example 1:
Save any data received from a faceLAB/DSS system on port COM2 to c:/test_data
Example 2:
serial2log c:/test_data COM3
Save any data received from a faceLAB/DSS system on port COM3 to c:/test_data
This application is mainly useful for testing some of the other applications. Modify the source file examples/serial2log/serial2log.cpp as you require, remembering that it may change when a new API is released.
The file udpclient.cpp contains a simple function that listens to a specified port for faceLAB/DSS UDP packets, reading each packet into an EngineOutputData object.
The program is designed to be a starting point for an application that needs to receive faceLAB/DSS data over a UDP network connection.
To use the supplied version of udpclient, run it with the optional argument:
- Port: The UDP port number to listen on. The default is 2001, and it must be between 2000 and 5000.
Example 1:
Runs the udpclient, listening on port 2001.
Example 2:
Runs the udpclient, listening on port 2010.
This project is designed for easy modification. The best place to modify the application is in the function handleEngineOutputData. In this function, the data has already been read from the network and placed in the EngineOutputData class structure. To use the structure, access the appropriate member of output_data. For example, to get the frame number use the notation: output_data.frameNum(). To get the head position, use output_data.headOutputData()->filteredHeadPosition().
Refer to the EngineOutputData header file, or the HTML documentation for detailed information about the EngineOutputData contents.
To use the supplied version of tcpclient, run it with the optional argument:
- Port: The UDP port number to listen on. The default is 2001, and it must be between 2000 and 5000.
Example 1:
Runs the tcpclient, listening on port 2001.
Example 2:
Runs the tcpclient, listening on port 2010.
This project is designed for easy modification. The best place to modify the application is in the function handleEngineOutputData. In this function, the data has already been read from the network and placed in the EngineOutputData class structure. To use the structure, access the appropriate member of output_data. For example, to get the frame number use the notation: output_data.frameNum(). To get the head position, use output_data.headOutputData()->filteredHeadPosition().
Refer to the EngineOutputData header file, or the HTML documentation for detailed information about the EngineOutputData contents.
A simple utility to compress a .eod file.
eodcompressor [options] <source_file> <dest_file>
Options:
-h Displays this usage information
-c <compression_name> Selects compression to use.
Compression Names:
uncompressed
lossy-realtime
lossy-good-quality
lossy-best-quality
lossless-realtime
lossless-good-quality
lossless-best-quality
Example:
eodcompressor -c lossy-realtime src.eod src-lossy-realtime.eod
Compressed the file src.eod
using the compression profile lossy-realtime
to file src-lossy-realtime.eod
.
The example demonstrates how to use the CompressingFileWriter and DecompressingFileReader classes.
This function performs the actual reading and compressing.
Generated on Fri Apr 1 15:36:50 2011 for Seeing Machines CoreData API by
1.5.0


The Toggle component is used to activate or deactivate an element. It uses a visual metaphor to inform the user of the state of the toggle.
Once focused, it can be toggled using the spacebar or the enter key.
<fd-toggle>
Toggle Sizes
Options include 'xs', 's', 'l' and default. If no value is provided, default is used.
Disabled State
Toggle can be in the disabled state, which prevents the user from interacting with it.
Two-Way Binding
It is possible to two-way bind to the checked property of the fd-toggle.
Example Toggle


Add child to stage.
Add Sprites on PIXI Application stage.
Grayscale is given to characters other than the first character.
Character object.
Add pointerdown and pointerup listener.
Append PIXI Application to HTMLElement.
Processing when the pointer is removed. Dragged
Event data of Sprite.
Returns Divide 360 degrees by the number of characters.
number - Addition angle of character Sprite.
Returns Atan2 between Sprite and base base coordinate.
number Atan2
Returns background Sprite object.
Background image path.
PIXI.Sprite Background Sprite object.
Returns PIXI application object.
pixiApp Pixi app that implements the interface
Returns convert angle in radian.
number Radian of angle
spriteObjects Character Sprites.
If event target clicked or touch ,Add pointermove listener.
Event data of Sprite.
Processing while moving the pointer.
Event data of Sprite.
Redraw sprite array
Set backgroundSprite property.
Set characterSprites property.
Character Sprite object.
Radians of object.
Set circle radius and y coordinate depending on the screen mode.
Set scale Sprite. Depending on the screen mode for responsive support.
Character Sprite object.
Set zIndex of Sprite object.
Character Sprite.
zIndex number.
Sort sprite array by left / right swap decision
Method called while moving the pointer. Update properties of Sprite.
Latest radians moving pointer.
Generated using TypeDoc


Types ELI5¶
Erlang is dynamically typed language. It means that any variable, field or function argument can contain any allowed value.
Type Specs¶
There is the type description language, which you can use to describe what YOU think your functions should take and return. These type specs are optional and the compiler will run your program like nothing happened even if a type violation exists. To ensure that your type specs do not contradict each other, there is another tool called Dialyzer.
A type spec is a directive in source ERL file, which looks like
-spec func_name(Arg :: integer(), _, Y :: any()) -> float().
Type specs are not code, they neither run nor prevent your program from compiling.
See also
You can read more about specifying types of your program in Typespec Reference Manual and other existing books, such as Learn You Some Erlang
Dialyzer¶
Dialyzer takes compiled BEAM or ERL source files as input, then tries to guess types (type inference).
How This Works¶
Say you have written a function, f
which takes one argument X
and
returns something.
Dialyzer first does a general assumption that f
is a fun()
, which
takes any value (X :: any()
) and returns whatever (any()
).
This is what Dialyzer guesses initially:
-spec f(X :: any()) -> any().
Any()
is the widest type possible which covers any value.
Then Dialyzer analyzes usage of this function and its code and
tries to reduce argument and return types to more narrow
specific set of types.
For example, if Dialyzer discovers that the only two places
which call your function f
pass an integer or an atom
argument, then X
’s type is reduced to integer()|atom()
(a set of two types). This is what Dialyzer may possibly calculate:
-spec f(X :: integer() | atom()) -> any().
If Dialyzer finds a contradiction, i.e. some types collapse to an empty type
(none()
) or incompatible types are found, Dialyzer reports an error.
These errors may look confusing, but they often (always?) point to an
existing problem in the code.
Typer¶
Typer is another optional tool, found in your OTP distribution. Using same algorithm as Dialyzer, it infers the types for a given module and prints them. You can take them and insert into your program for future use or to better document a large legacy project.


sound.properties
FileThe Java Sound Configuration file,
sound.properties
, can be used to specify default
service providers for javax.sound.sampled.AudioSystem
and javax.sound.midi.MidiSystem
.
The following keys are recognized by AudioSystem
methods:
javax.sound.sampled.Clip
javax.sound.sampled.Port
javax.sound.sampled.SourceDataLine
javax.sound.sampled.TargetDataLine
The following keys are recognized by MidiSystem
methods:
javax.sound.midi.Sequencer
javax.sound.midi.Synthesizer
javax.sound.midi.Transmitter
javax.sound.midi.Receiver
The values should specify the full class name of the service provider and/or the device name.
sound.properties
is located at
$JAVAHOME/jre/lib
.
For more details, see the class descriptions for AudioSystem
and MidiSystem
.
To use MyDeviceProvider
as the default for
SourceDataLine
lines, set the following key:
javax.sound.sampled.SourceDataLine=com.xyz.MyDeviceProvider
To specify the default Synthesizer
by its name
InternalSynth
, set the following key:
javax.sound.midi.Synthesizer=#InternalSynth
To specify the default Receiver
by provider and
name, set the following key:
javax.sound.midi.Receiver=com.sun.media.sound.MidiProvider#SunMIDI1


Kali> mount $TARGET:/vol/share /mnt/nfs
Kali> Mount -t cifs //<server ip>/<share> <local dir> -o username=”guest”,password=””
Some mount flags to be aware of:
noexec
Do not allow direct execution of any binaries on the mounted filesystem. (Until recently it was possible to run binaries anyway using a command like /lib/ld*.so /mnt/binary. This trick fails since Linux 2.4.25 / 2.6.0.)
$ /lib/ld-linux.so.2 ~/id
uid=1001(edd) gid=1001(edd) groups=1001(edd),1002(wheel)
nodev
Do not interpret character or block special devices on the file system.
exec
Permit execution of binaries.
auto
Can be mounted with the -a option.
noauto
Can only be mounted explicitly (i.e., the -a option will not cause the filesystem to be mounted).
suid
Allow set-user-identifier or set-group-identifier bits to take effect.
nosuid
Do not allow set-user-identifier or set-group-identifier bits to take effect. (This seems safe, but is in fact rather unsafe if you have suidperl(1) installed.)
owner
Allow an ordinary (i.e., non-root) user to mount the filesystem if he is the owner of the device. This option implies the options nosuid and nodev (unless overridden by subsequent options, as in the option line owner,dev,suid).
group
Allow an ordinary (i.e., non-root) user to mount the filesystem if one of his groups matches the group of the device. This option implies the options nosuid and nodev (unless overridden by subsequent options, as in the option line group,dev,suid).
user
Allow an ordinary user to mount the filesystem. The name of the mounting user is written to mtab so that he can unmount the filesystem again. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line user,exec,dev,suid).
nouser
Forbid an ordinary (i.e., non-root) user to mount the filesystem. This is the default.
users
Allow every user to mount and unmount the filesystem. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line users,exec,dev,suid).


Longsword of Wounding +2 [66gp]
Warhammer of Justice +1 [41gp]
Hammer of Capability [35gp]
Pendant of Truth [38gp]
Ring of Joy +5 [32gp]
Warhammer of Flame +2 [65gp]
Battleaxe of Glory [23gp]
Plough of Plenty [35gp]
Saw of Capability +1 [35gp]
Amulet of Wounding +2 [35gp]
Pendant of Hope [34gp]
Pendant of Joy [39gp]
Gold remaining: 200


Hot take:
This video of @KomodoPlatform releasing groundbreaking news... https://t.co/FrO5CCBaWh
jorian24-Feb-19 03:20 PM
dude. i literally watched that fyre scam documentary 5 minutes ago
that guy is nuts
nocturnal24-Feb-19 03:35 PM
ive been waiting for months for btc to hit 2.5k to get more heavily into crypto...
so close and yet so far...
LocoMB24-Feb-19 03:40 PM
PTYX24-Feb-19 03:49 PM
Volatility is back
It's not necessarily a bad thing
FishyGuts24-Feb-19 03:58 PM
CHMEX24-Feb-19 04:15 PM
That s4f sounds like a use case for KV on a assetchain
Markus24-Feb-19 04:26 PM
alot of action on binance this sunday, looks like koreans are not up for a run their volume is not the way it use to be
yorklab24-Feb-19 04:32 PM
Just saw the tweet that says new Komodo chins will soon have the ability to be Quantum resistant. I would think the entire Blockchain world would be interested in this. I wonder if this is having any effect on the kmd market.
Markus24-Feb-19 04:32 PM
strong sellers
25.5 wall getting melt
yorklab24-Feb-19 04:33 PM
Yea, it's about to disappear.
and there it goes.
Markus24-Feb-19 04:33 PM
i sold a small portion at 27 to upgrade my kmd stack, looking to buy back around 24 if possible....if not then 25 is fine also
siu - Chainmakers24-Feb-19 04:35 PM
Retest of newly formed supports now. If this holds, then we might be in a good healthy pullback before higher moves up
Markus24-Feb-19 04:38 PM
that 25k order getting poked
yorklab24-Feb-19 04:39 PM
BTC is continuing down which probably has a lot to do with .(edited)
3500 for the most beautiful bear trap.
Failure of tapping high followed by sharp move down shows likelyhood whales are looking for liquidity provided by sellers, further build their position to dump in the 5-6k range.
Markus24-Feb-19 04:40 PM
also very close to 21ma
could use it as support
on daily chart
FishyGuts24-Feb-19 05:02 PM
@yorklab see my “hot take” tweet from above. Watch the vid.
Such Komodo. Many wow. Much ignored.
ToadCrunch24-Feb-19 05:15 PM
ARRR
yorklab24-Feb-19 05:16 PM
Maybe I'm wrong, but if nobody else is doing this, and this really is as big as it seems, I would think Marketing would be telling the world........maybe soon?
jl777c24-Feb-19 05:27 PM
to be fair i only started on this over the weekend, so it came together really quickly
and the initial dilithium CC is more a proof of concept, to make it a fully functional blockchain payment system that is 100% quantum resistant will require a few more days work, and some GUI support too(edited)
if there is some demand for this, I will do it, but I was just helping a student do his homework
passcombo.com 🏴☠🏴24-Feb-19 05:29 PM
JL after yo ufinish write a handbook "DIY: quantum resistance within a weekend"
yorklab24-Feb-19 05:37 PM
Ah, didn't know this was so new. Over a weekend? A few more days? This sounds like something a team of scientists have to create....just amazing. Well jl77c, I suggest you finish your homework.
Markus24-Feb-19 05:48 PM
JL is a genius, one of a kind
2
Hollowman900024-Feb-19 05:58 PM
@FishyGuts@yorklab@jl777c what are you all on about?
FishyGuts24-Feb-19 05:59 PM
JahRules halftime show performance received the ovation that KMD innovations tend to receive... Absolutely none
jl777c24-Feb-19 06:02 PM
just updated the MUSIG chain to support basic dilithium transactions(edited)
it isnt ready for a fully quantum resistant chain as change isnt supported, so just a proof of concept using CC for rapid development. latest research crypto algo in a live blockchain, over the weekend
Markus24-Feb-19 06:22 PM
would been nice if we also had a kmd/usdt pair on binance ^^
also get the background story of the kids homework. Sounds interesting
Hollowman900024-Feb-19 06:43 PM
Definitely need to run that through a grandma translator
-what was the problem
-how this solves it
-10,000 foot view on how it works
-background on how it came about
tolken24-Feb-19 06:45 PM
Nah, I’n about a year, another project like Neo, Eos, or Tron will claim they have the first quantum resistance chains. @yorklab
CHMEX24-Feb-19 06:45 PM
your inverse sha256 algo might be useless soon hollowman(edited)
Hollowman900024-Feb-19 06:45 PM
This is troubling
tolken24-Feb-19 06:47 PM
@CHMEX I believe the proper technical term is “Inverse sha256” don’t mix the two, potentially catastrophic results.
CHMEX24-Feb-19 06:48 PM
corrected
Hollowman900024-Feb-19 06:48 PM
This is double trouble
jl777c24-Feb-19 06:48 PM
there are a variety of quantum resistant algos being submitted to NIST for the post-quantum era
dilithium is one of these new algos
since CC allows to add new consensus rules to komodo chains, i made it so you need to have a valid dilithium signature to be able to spend funds
since komodo architecture allows a custom CC chain to inherit all the rest, in literally a weekend, I created a chain that is able to generate dilithium keypairs, send funds to a pubkey and spend those funds using a privkey
unlike other quantum resistant algos, dilithium appears to allow pubkey reuse
will dilithium be the officially selected algo? maybe, maybe not. if not, i will have to spend another weekend adding a different algo
Alright24-Feb-19 06:52 PM
Can you dumb this down for me? What additional protections would this offer? Would this only be helpful in the event that sha256 is broken?

Hollowman900024-Feb-19 06:56 PM
The theoretical capabilities of a quantum computer are known
Therefore, you create schemes difficult enough to hinder them
nocturnal24-Feb-19 06:56 PM
how many qbits are assumed??
moreover how can you encrypt strongly enough with a classical computer that cant be cracked with a quantum computer(edited)