TSoapServer class.
TSoapServer is a wrapper of the PHP SoapServer class. It associates a SOAP provider class to the SoapServer object. It also manages the URI for the SOAP service and WSDL.
Located in /Web/Services/TSoapService.php (line 277)
TComponent | --TApplicationComponent | --TSoapServer
Creates the SoapServer instance.
Generate a SOAP fault message.
Soap method guessed from the SOAP message received.
Returns the WSDL content of the SOAP server.
If WsdlUri is set, its content will be returned. If not, the Provider class will be investigated and the WSDL will be automatically genearted.
Guess the SOAP method request from the actual SOAP message
Handles the SOAP request.
Inherited From TApplicationComponent
TApplicationComponent::getApplication()
TApplicationComponent::getRequest()
TApplicationComponent::getResponse()
TApplicationComponent::getService()
TApplicationComponent::getSession()
TApplicationComponent::getUser()
TApplicationComponent::publishAsset()
TApplicationComponent::publishFilePath()
Inherited From TComponent
TComponent::addParsedObject()
TComponent::attachEventHandler()
TComponent::canGetProperty()
TComponent::canSetProperty()
TComponent::createdOnTemplate()
TComponent::detachEventHandler()
TComponent::evaluateExpression()
TComponent::evaluateStatements()
TComponent::getEventHandlers()
TComponent::getSubProperty()
TComponent::hasEvent()
TComponent::hasEventHandler()
TComponent::hasProperty()
TComponent::raiseEvent()
TComponent::setSubProperty()
TComponent::__get()
TComponent::__set()
Documentation generated on Fri, 03 Jun 2011 16:25:52 +0200 by phpDocumentor 1.3.0RC4


A simple JavaScript solution for responsive images. But not just images, it can evenload in HTML partials. Interchange uses media queries to dynamically load responsive content that is appropriate for different users' browsers.
# Sample Component
```html
On-page template
```
***
### Basic HTML
You can create an Interchange component with this basic HTML


0.2.0
Class for sorting arrays containing numerical data.
Sort an array of numbers using the Bubble Sort algorithm. Iterating through all items in the array, we compare the current item with the next one in the array. If the current one is greater, the positions are swapped. This is repeated until there is no more swapping necessary.
Array<Number>
:
An array of sorted numbers.
Sort an array of numbers using the Insertion Sort algorithm. Insertion merge is a simple sorting algorithm that builds the final sorted array (or list) one item at a time. The array elements are compared with each other sequentially and then arranged simultaneously in some particular order. The analogy can be understood from the style we arrange a deck of cards.
Array<Number>
:
An array of sorted numbers.
Sort an array of numbers using the Merge Sort algorithm. The MergeSort function repeatedly divides the array into two halves until we reach a stage where we try to perform MergeSort on a subarray of size 1 i.e. p == r. After that, the merge function comes into play and combines the sorted arrays into larger arrays until the whole array is merged.
Array<Number>
:
An array of sorted numbers.
Sort an array of numbers using the Quick Sort algorithm. QuickSort is a Divide and Conquer algorithm. It picks an element as pivot and partitions the given array around the picked pivot. There are many different versions of quickSort that pick pivot in different ways.
Array<Number>
:
An array of sorted numbers.
Class for working with arrays of any types
Chunk one flat array into a series of arrays of a certain size.
(Array)
A an array of values (string, number, etc.).
(Number)
The size of chunks to split the array into.
Array<Array>
:
An array containing arrays of the specified size, containing
the original data from the flat array.
Class for working with arrays containing numbers and numerical data.
Class for working with arrays containing objects with key/value data.
Normalize the values in an object array associated with a specific key between 0 and 1 or a custom range based on the minimums and maximums contained in the object array by that key.
(Array)
A an array containing objects.
(String)
A key which exists in the objects in the array, with associated numerical values.
(Number
= 0
)
(Optional) A custom minimum value to normalize to.
(Number
= 1
)
(Optional) A custom maximum value to normalize to.
Array
:
The modified object array.
Normalize the values in an object array associated with specific keys between 0 and 1 or a custom range based on the minimums and maximums contained in the object array by those keys.
(Array)
A an array containing objects.
(Number
= 0
)
(Optional) A custom minimum value to normalize to.
(Number
= 1
)
(Optional) A custom maximum value to normalize to.
Array
:
The modified object array.
Normalize all the values in an object array associated with keys which have numerical value pairs between 0 and 1 or a custom range based on the minimums and maximums contained in the object array by those keys.
(Array)
A an array containing objects.
(Number
= 0
)
(Optional) A custom minimum value to normalize to.
(Number
= 1
)
(Optional) A custom maximum value to normalize to.
Array
:
The modified object array.
Turn a flat array of objects containing common properties into a nested object hierarchy based on parent/child keys. ex. Folders, File Versions, etc.
(String)
The common property of the objects to establish primary identity.
(String)
The common property of the objects to establish parent -> child relationships.
Array<Object>
:
An array of objects, nested using the .children accessor based on the
parent -> child hierarchy established.
Stack data structure.
Get the count of the number of items in the stack.
number
:
The number of items in the stack.
Remove the top item from the stack.
any
:
Get the item at the top of the stack, without removing it.
any
:
The item at the top of the stack.
Class for creating mock data for algorithm/visualization testing.
Create mock data for a network/graph algorithm.
(any)
The amount of data points to create
{nodes: Array<{size: Number, x: null, y: null}>, links: Array<{source: number, target: number}>}
:
An array
of objects which can be used as nodes and connections in network/graph algorithm testing scenarios.
Class for working with numbers and numerical data.
Normalize a number between 0 and 1 based on a known minimum and maximum value.
Number
:
The random float between the min and max input.
Normalize a number between a custom range (max,min) based on a known minimum and maximum value of the original dataset.
(Number)
The value to normalize.
(Number)
The minimum extent in the original range.
(Number)
The maximum extent in the original range.
(Number)
The minimum extent in the new, custom range.
(Number)
The maximum extent in the new, custom range.
Number
:
Class for working with string data.
Class for working with Cyrillic string data.
Get an array of all the Cyrillic words from a monolithic string.
(any)
The string to break up into individual words.
RegExpMatchArray
:
An array of individual Cyrillic words.
Class for working with Latin string data.
Queue data structure.


RT @PragTob: Still one of my favorite pictures of all time.
@jasonrclark and I pairing at @eurucamp on @shoooesrb code. @rubycorns tattoo…
7/21/2018, 7:53:15 AM
Favs: 0
Retweets: 0
link--- layout: tweet ---
RT @PragTob: Still one of my favorite pictures of all time.
@jasonrclark and I pairing at @eurucamp on @shoooesrb code. @rubycorns tattoo…
7/21/2018, 7:53:15 AM
Favs: 0
Retweets: 0
link


Looks like my site is still under construction. Check back soon!
Check out my Github site here in the meantime.
Looks like my site is still under construction. Check back soon!
Check out my Github site here in the meantime.


Contribute¶
General contribution guidelines¶
Fork the repository on GitHub.
Install Feat on your machine.
Install
pytest
withpip install pytest
then run the tests in the repository withpytest
orpytest/feat/tests/
. Confirm that all tests pass on your system. If some tests fail, try to find out why they are failing. Common issues may be not having downloaded model files or missing dependencies.Create your feature.
Add tests to
feat/tests/
.Run the tests again with
pytest tests/
to make sure everything still passes, including your new feature. If you broke something, edit your feature so that it doesn’t break existing code.Create a pull request to the main repository’s
master
branch!
Model contribution guidelines¶
There are three key steps to adding a model.
Create a folder for the model you are building in the appropriate model type directory. If you are contributing an Action Unit detection model and calling it
mynewmodel
, create a folder infeat/feat/au_detectors/
. If it’s an Emotion detection model, add a folderfeat/feat/emo_detectors/
.Add your model architecture. Your model files could contained in a single (e.g.
feat/emo_detectors/ResMaskNet/resmasknet_test.py
) or they could be separated in to a model file (e.g./au_detectors/JAANet/JAA_model
) and a test file (e.g./au_detectors/JAANet/JAA_test
).Your model should be a class that has the appropriate method that the
Detector
can call it. For example, AU detectors should have the functionmynewmodel.detect_au()
that can be called.Add model to list of models in the
Detector
class infeat/detector.py
.Upload your trained model weights to an accessible locations (e.g. Google Drive).
Add tests to make sure your model is working.
Create a pull request to the main repository’s
master
branch!


MARS ATTACKS! (1996)
Let's not mince words here; Director Tim Burton's big budget sci-fi spoof is, at first glance, a real mess. After an awesome credit sequence, the first half of the movie wobbles along like one of Ed Wood's spaceships, with an all-star cast (including Jack Nicholson in 2 roles, Glenn Close, Michael J. Fox and a multitude of others) seemingly unsure of what exactly is expected of them. (Only Pierce Brosnan, as a perfect distillation of every stiffly handsome eggheaded scientist from the great `50s monster movies, really seems to be in on the joke.) Not that this narrative sloppiness is exactly out of character for this director (Let's face it, based on prior evidence like BATMAN RETURNS and EDWARD SCISSORHANDS, the odds of Tim Burton ever turning out a film with a completely coherent storyline are about as likely as Stanley Kubrick making a movie about kickboxing), but it's still disappointing, considering all the talent involved. But just when you're about to give up hope, suddenly the aliens land, the gags start flying faster and faster, and the movie gets great in a hurry. Whenever the bubble-domed, big-brained Martians are on screen, this movie achieves the kind of surreal, anything goes quality previously found only in the classic Warner Brothers cartoons or the best issues of MAD magazine, as Burton and co. tweak virtually every invasion flick ever made. (One of the best gags - involving the Washington Monument, a malevolent UFO, and a slow moving Boy Scout troop - is lifted directly from the Ray Harryhausen classic EARTH vs THE FLYING SAUCERS.) Not all of the jokes work, but the ones that do make it more than worth your while (the Martians' um - unique method of dealing with a nuclear missile is far and away my favorite movie moment of '96). By the time that Tom Jones and Jim Brown have joined forces to stomp some alien butt, this movie has attained a giggly type of weirdness that's impossible to resist; it left me ack-ing for days.
Copyright 1997: The Critic formerly known as Andrew Wright http://www.seanet.com/~louk/ e-mail<EMAIL_ADDRESS>The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


| 1 | package fr.sii.ogham.sms.builder.cloudhopper; | |
| 2 | ||
| 3 | import java.util.concurrent.Executors; | |
| 4 | import java.util.concurrent.ScheduledExecutorService; | |
| 5 | import java.util.concurrent.ThreadFactory; | |
| 6 | import java.util.concurrent.atomic.AtomicInteger; | |
| 7 | import java.util.function.Supplier; | |
| 8 | ||
| 9 | import com.cloudhopper.smpp.pdu.EnquireLink; | |
| 10 | ||
| 11 | import fr.sii.ogham.core.builder.Builder; | |
| 12 | import fr.sii.ogham.core.builder.configuration.ConfigurationValueBuilder; | |
| 13 | import fr.sii.ogham.core.builder.configuration.ConfigurationValueBuilderHelper; | |
| 14 | import fr.sii.ogham.core.builder.configurer.Configurer; | |
| 15 | import fr.sii.ogham.core.builder.context.BuildContext; | |
| 16 | import fr.sii.ogham.core.fluent.AbstractParent; | |
| 17 | import fr.sii.ogham.sms.sender.impl.cloudhopper.KeepAliveOptions; | |
| 18 | ||
| 19 | /** | |
| 20 | * Builder to configure how keep alive session management should behave. | |
| 21 | * | |
| 22 | *
 | |
| 23 | * Keep alive actively maintains the session opened by sending regularly | |
| 24 | * {@link EnquireLink} messages. | |
| 25 | * | |
| 26 | * This builder let you configure: | |
| 27 | *
 | |
| 28 | *
Enable/disable active keep alive management
 | |
| 29 | *
The time to wait between two {@link EnquireLink} messages
 | |
| 30 | *
The maximum time to wait for a response from the server for | |
| 31 | * {@link EnquireLink} request
 | |
| 32 | *
 | |
| 33 | * | |
| 34 | * @author Aurélien Baudet | |
| 35 | * | |
| 36 | */ | |
| 37 | public class KeepAliveBuilder extends AbstractParent<SessionBuilder> implements Builder<KeepAliveOptions> { | |
| 38 | private static final AtomicInteger enquireLinkThreadCounter = new AtomicInteger(); | |
| 39 | ||
| 40 | private final ConfigurationValueBuilderHelper<KeepAliveBuilder, Boolean> enableValueBuilder; | |
| 41 | private final ConfigurationValueBuilderHelper<KeepAliveBuilder, Long> enquireLinkIntervalValueBuilder; | |
| 42 | private final ConfigurationValueBuilderHelper<KeepAliveBuilder, Long> enquireLinkTimeoutValueBuilder; | |
| 43 | private final ConfigurationValueBuilderHelper<KeepAliveBuilder, Boolean> connectAtStartupValueBuilder; | |
| 44 | private final ConfigurationValueBuilderHelper<KeepAliveBuilder, Integer> maxConsecutiveTimeoutsValueBuilder; | |
| 45 | private Supplier<ScheduledExecutorService> executorFactory; | |
| 46 | ||
| 47 | public KeepAliveBuilder(SessionBuilder parent, BuildContext buildContext) { | |
| 48 | super(parent); | |
| 49 | this.enableValueBuilder = buildContext.newConfigurationValueBuilder(this, Boolean.class); | |
| 50 | this.enquireLinkIntervalValueBuilder = buildContext.newConfigurationValueBuilder(this, Long.class); | |
| 51 | this.enquireLinkTimeoutValueBuilder = buildContext.newConfigurationValueBuilder(this, Long.class); | |
| 52 | this.connectAtStartupValueBuilder = buildContext.newConfigurationValueBuilder(this, Boolean.class); | |
| 53 | this.maxConsecutiveTimeoutsValueBuilder = buildContext.newConfigurationValueBuilder(this, Integer.class); | |
| 54 | } | |
| 55 | ||
| 56 | /** | |
| 57 | * Enable or disable sending of {@link EnquireLink} messages to keep the | |
| 58 | * session alive. | |
| 59 | * | |
| 60 | *
 | |
| 61 | * The value set using this method takes precedence over any property and | |
| 62 | * default value configured using {@link #enable()}. | |
| 63 | * | |
| 64 | *
 | |
| 65 | * .enable(true) | |
| 66 | * .enable() | |
| 67 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 68 | * .defaultValue(false) | |
| 69 | *
 | |
| 70 | * | |
| 71 | *
 | |
| 72 | * .enable(true) | |
| 73 | * .enable() | |
| 74 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 75 | * .defaultValue(false) | |
| 76 | *
 | |
| 77 | * | |
| 78 | * In both cases, {@code enable(true)} is used. | |
| 79 | * | |
| 80 | *
 | |
| 81 | * If this method is called several times, only the last value is used. | |
| 82 | * | |
| 83 | *
 | |
| 84 | * If {@code null} value is set, it is like not setting a value at all. The | |
| 85 | * property/default value configuration is applied. | |
| 86 | * | |
| 87 | * @param enable | |
| 88 | * true to enable sending requests to keep the session alive | |
| 89 | * @return this instance for fluent chaining | |
| 90 | */ | |
| 91 | public KeepAliveBuilder enable(Boolean enable) { | |
| 92 |
1
1. enable : removed call to fr/sii/ogham/core/builder/configuration/ConfigurationValueBuilderHelper::setValue → NO_COVERAGE |
enableValueBuilder.setValue(enable); |
| 93 |
1
1. enable : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::enable → NO_COVERAGE |
return this; |
| 94 | } | |
| 95 | ||
| 96 | /** | |
| 97 | * Enable or disable sending of {@link EnquireLink} messages to keep the | |
| 98 | * session alive. | |
| 99 | * | |
| 100 | *
 | |
| 101 | * This method is mainly used by {@link Configurer}s to register some | |
| 102 | * property keys and/or a default value. The aim is to let developer be able | |
| 103 | * to externalize its configuration (using system properties, configuration | |
| 104 | * file or anything else). If the developer doesn't configure any value for | |
| 105 | * the registered properties, the default value is used (if set). | |
| 106 | * | |
| 107 | *
 | |
| 108 | * .enable() | |
| 109 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 110 | * .defaultValue(false) | |
| 111 | *
 | |
| 112 | * | |
| 113 | *
 | |
| 114 | * Non-null value set using {@link #enable(Boolean)} takes precedence over | |
| 115 | * property values and default value. | |
| 116 | * | |
| 117 | *
 | |
| 118 | * .enable(true) | |
| 119 | * .enable() | |
| 120 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 121 | * .defaultValue(false) | |
| 122 | *
 | |
| 123 | * | |
| 124 | * The value {@code true} is used regardless of the value of the properties | |
| 125 | * and default value. | |
| 126 | * | |
| 127 | *
 | |
| 128 | * See {@link ConfigurationValueBuilder} for more information. | |
| 129 | * | |
| 130 | * | |
| 131 | * @return the builder to configure property keys/default value | |
| 132 | */ | |
| 133 | public ConfigurationValueBuilder<KeepAliveBuilder, Boolean> enable() { | |
| 134 |
1
1. enable : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::enable → RUN_ERROR |
return enableValueBuilder; |
| 135 | } | |
| 136 | ||
| 137 | /** | |
| 138 | * The fixed delay (in milliseconds) between two {@link EnquireLink} | |
| 139 | * messages. | |
| 140 | * | |
| 141 | *
 | |
| 142 | * The value set using this method takes precedence over any property and | |
| 143 | * default value configured using {@link #interval()}. | |
| 144 | * | |
| 145 | *
 | |
| 146 | * .interval(60000L) | |
| 147 | * .interval() | |
| 148 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 149 | * .defaultValue(30000L) | |
| 150 | *
 | |
| 151 | * | |
| 152 | *
 | |
| 153 | * .interval(60000L) | |
| 154 | * .interval() | |
| 155 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 156 | * .defaultValue(30000L) | |
| 157 | *
 | |
| 158 | * | |
| 159 | * In both cases, {@code interval(60000L)} is used. | |
| 160 | * | |
| 161 | *
 | |
| 162 | * If this method is called several times, only the last value is used. | |
| 163 | * | |
| 164 | *
 | |
| 165 | * If {@code null} value is set, it is like not setting a value at all. The | |
| 166 | * property/default value configuration is applied. | |
| 167 | * | |
| 168 | * @param delay | |
| 169 | * the amount of time to wait between two {@link EnquireLink} | |
| 170 | * messages | |
| 171 | * @return this instance for fluent chaining | |
| 172 | */ | |
| 173 | public KeepAliveBuilder interval(Long delay) { | |
| 174 |
1
1. interval : removed call to fr/sii/ogham/core/builder/configuration/ConfigurationValueBuilderHelper::setValue → NO_COVERAGE |
enquireLinkIntervalValueBuilder.setValue(delay); |
| 175 |
1
1. interval : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::interval → NO_COVERAGE |
return this; |
| 176 | } | |
| 177 | ||
| 178 | /** | |
| 179 | * The fixed delay (in milliseconds) between two {@link EnquireLink} | |
| 180 | * messages. | |
| 181 | * | |
| 182 | *
 | |
| 183 | * This method is mainly used by {@link Configurer}s to register some | |
| 184 | * property keys and/or a default value. The aim is to let developer be able | |
| 185 | * to externalize its configuration (using system properties, configuration | |
| 186 | * file or anything else). If the developer doesn't configure any value for | |
| 187 | * the registered properties, the default value is used (if set). | |
| 188 | * | |
| 189 | *
 | |
| 190 | * .interval() | |
| 191 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 192 | * .defaultValue(30000L) | |
| 193 | *
 | |
| 194 | * | |
| 195 | *
 | |
| 196 | * Non-null value set using {@link #interval(Long)} takes precedence over | |
| 197 | * property values and default value. | |
| 198 | * | |
| 199 | *
 | |
| 200 | * .interval(60000L) | |
| 201 | * .interval() | |
| 202 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 203 | * .defaultValue(30000L) | |
| 204 | *
 | |
| 205 | * | |
| 206 | * The value {@code 60000L} is used regardless of the value of the | |
| 207 | * properties and default value. | |
| 208 | * | |
| 209 | *
 | |
| 210 | * See {@link ConfigurationValueBuilder} for more information. | |
| 211 | * | |
| 212 | * | |
| 213 | * @return the builder to configure property keys/default value | |
| 214 | */ | |
| 215 | public ConfigurationValueBuilder<KeepAliveBuilder, Long> interval() { | |
| 216 |
1
1. interval : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::interval → RUN_ERROR |
return enquireLinkIntervalValueBuilder; |
| 217 | } | |
| 218 | ||
| 219 | /** | |
| 220 | * The maximum amount of time (in milliseconds) to wait for receiving a | |
| 221 | * response from the server to an {@link EnquireLink} request. | |
| 222 | * | |
| 223 | *
 | |
| 224 | * The value set using this method takes precedence over any property and | |
| 225 | * default value configured using {@link #responseTimeout()}. | |
| 226 | * | |
| 227 | *
 | |
| 228 | * .responseTimeout(5000L) | |
| 229 | * .responseTimeout() | |
| 230 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 231 | * .defaultValue(10000L) | |
| 232 | *
 | |
| 233 | * | |
| 234 | *
 | |
| 235 | * .responseTimeout(5000L) | |
| 236 | * .responseTimeout() | |
| 237 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 238 | * .defaultValue(10000L) | |
| 239 | *
 | |
| 240 | * | |
| 241 | * In both cases, {@code responseTimeout(5000L)} is used. | |
| 242 | * | |
| 243 | *
 | |
| 244 | * If this method is called several times, only the last value is used. | |
| 245 | * | |
| 246 | *
 | |
| 247 | * If {@code null} value is set, it is like not setting a value at all. The | |
| 248 | * property/default value configuration is applied. | |
| 249 | * | |
| 250 | * @param timeout | |
| 251 | * the maximum amount of time to wait for the response | |
| 252 | * @return this instance for fluent chaining | |
| 253 | */ | |
| 254 | public KeepAliveBuilder responseTimeout(Long timeout) { | |
| 255 |
1
1. responseTimeout : removed call to fr/sii/ogham/core/builder/configuration/ConfigurationValueBuilderHelper::setValue → NO_COVERAGE |
enquireLinkTimeoutValueBuilder.setValue(timeout); |
| 256 |
1
1. responseTimeout : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::responseTimeout → NO_COVERAGE |
return this; |
| 257 | } | |
| 258 | ||
| 259 | /** | |
| 260 | * The maximum amount of time (in milliseconds) to wait for receiving a | |
| 261 | * response from the server to an {@link EnquireLink} request. | |
| 262 | * | |
| 263 | *
 | |
| 264 | * This method is mainly used by {@link Configurer}s to register some | |
| 265 | * property keys and/or a default value. The aim is to let developer be able | |
| 266 | * to externalize its configuration (using system properties, configuration | |
| 267 | * file or anything else). If the developer doesn't configure any value for | |
| 268 | * the registered properties, the default value is used (if set). | |
| 269 | * | |
| 270 | *
 | |
| 271 | * .responseTimeout() | |
| 272 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 273 | * .defaultValue(10000L) | |
| 274 | *
 | |
| 275 | * | |
| 276 | *
 | |
| 277 | * Non-null value set using {@link #responseTimeout(Long)} takes precedence | |
| 278 | * over property values and default value. | |
| 279 | * | |
| 280 | *
 | |
| 281 | * .responseTimeout(5000L) | |
| 282 | * .responseTimeout() | |
| 283 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 284 | * .defaultValue(10000L) | |
| 285 | *
 | |
| 286 | * | |
| 287 | * The value {@code 5000L} is used regardless of the value of the properties | |
| 288 | * and default value. | |
| 289 | * | |
| 290 | *
 | |
| 291 | * See {@link ConfigurationValueBuilder} for more information. | |
| 292 | * | |
| 293 | * | |
| 294 | * @return the builder to configure property keys/default value | |
| 295 | */ | |
| 296 | public ConfigurationValueBuilder<KeepAliveBuilder, Long> responseTimeout() { | |
| 297 |
1
1. responseTimeout : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::responseTimeout → RUN_ERROR |
return enquireLinkTimeoutValueBuilder; |
| 298 | } | |
| 299 | ||
| 300 | /** | |
| 301 | * Connect to the server directly when the client is ready (if true). | |
| 302 | * Otherwise, the connection is done when the first message is sent. | |
| 303 | * | |
| 304 | * This may be useful to avoid a latency for the first message. | |
| 305 | * | |
| 306 | * If connection fails at startup, then a new attempt is done when first | |
| 307 | * message is sent. | |
| 308 | * | |
| 309 | *
 | |
| 310 | * The value set using this method takes precedence over any property and | |
| 311 | * default value configured using {@link #connectAtStartup()}. | |
| 312 | * | |
| 313 | *
 | |
| 314 | * .connectAtStartup(true) | |
| 315 | * .connectAtStartup() | |
| 316 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 317 | * .defaultValue(false) | |
| 318 | *
 | |
| 319 | * | |
| 320 | *
 | |
| 321 | * .connectAtStartup(true) | |
| 322 | * .connectAtStartup() | |
| 323 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 324 | * .defaultValue(false) | |
| 325 | *
 | |
| 326 | * | |
| 327 | * In both cases, {@code connectAtStartup(true)} is used. | |
| 328 | * | |
| 329 | *
 | |
| 330 | * If this method is called several times, only the last value is used. | |
| 331 | * | |
| 332 | *
 | |
| 333 | * If {@code null} value is set, it is like not setting a value at all. The | |
| 334 | * property/default value configuration is applied. | |
| 335 | * | |
| 336 | * @param connectAtStartup | |
| 337 | * try to connect when client is ready | |
| 338 | * @return this instance for fluent chaining | |
| 339 | */ | |
| 340 | public KeepAliveBuilder connectAtStartup(Boolean connectAtStartup) { | |
| 341 |
1
1. connectAtStartup : removed call to fr/sii/ogham/core/builder/configuration/ConfigurationValueBuilderHelper::setValue → NO_COVERAGE |
connectAtStartupValueBuilder.setValue(connectAtStartup); |
| 342 |
1
1. connectAtStartup : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::connectAtStartup → NO_COVERAGE |
return this; |
| 343 | } | |
| 344 | ||
| 345 | /** | |
| 346 | * Connect to the server directly when the client is ready (if true). | |
| 347 | * Otherwise, the connection is done when the first message is sent. | |
| 348 | * | |
| 349 | * This may be useful to avoid a latency for the first message. | |
| 350 | * | |
| 351 | * If connection fails at startup, then a new attempt is done when first | |
| 352 | * message is sent. | |
| 353 | * | |
| 354 | *
 | |
| 355 | * This method is mainly used by {@link Configurer}s to register some | |
| 356 | * property keys and/or a default value. The aim is to let developer be able | |
| 357 | * to externalize its configuration (using system properties, configuration | |
| 358 | * file or anything else). If the developer doesn't configure any value for | |
| 359 | * the registered properties, the default value is used (if set). | |
| 360 | * | |
| 361 | *
 | |
| 362 | * .connectAtStartup() | |
| 363 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 364 | * .defaultValue(false) | |
| 365 | *
 | |
| 366 | * | |
| 367 | *
 | |
| 368 | * Non-null value set using {@link #connectAtStartup(Boolean)} takes | |
| 369 | * precedence over property values and default value. | |
| 370 | * | |
| 371 | *
 | |
| 372 | * .connectAtStartup(true) | |
| 373 | * .connectAtStartup() | |
| 374 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 375 | * .defaultValue(false) | |
| 376 | *
 | |
| 377 | * | |
| 378 | * The value {@code true} is used regardless of the value of the properties | |
| 379 | * and default value. | |
| 380 | * | |
| 381 | *
 | |
| 382 | * See {@link ConfigurationValueBuilder} for more information. | |
| 383 | * | |
| 384 | * | |
| 385 | * @return the builder to configure property keys/default value | |
| 386 | */ | |
| 387 | public ConfigurationValueBuilder<KeepAliveBuilder, Boolean> connectAtStartup() { | |
| 388 |
1
1. connectAtStartup : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::connectAtStartup → RUN_ERROR |
return connectAtStartupValueBuilder; |
| 389 | } | |
| 390 | ||
| 391 | /** | |
| 392 | * Provides a factory that creates an {@link ScheduledExecutorService}. The | |
| 393 | * created executor is then used to schedule the task that sends | |
| 394 | * {@link EnquireLink} requests. | |
| 395 | * | |
| 396 | * The factory should use one of: | |
| 397 | *
 | |
| 398 | *
{@link Executors#newSingleThreadScheduledExecutor()}
 | |
| 399 | *
{@link Executors#newSingleThreadScheduledExecutor(java.util.concurrent.ThreadFactory)}
 | |
| 400 | *
{@link Executors#newScheduledThreadPool(int)}
 | |
| 401 | *
{@link Executors#newScheduledThreadPool(int, java.util.concurrent.ThreadFactory)}
 | |
| 402 | *
 | |
| 403 | * | |
| 404 | *
 | |
| 405 | * If this method is called several times, only the last value is used. | |
| 406 | * | |
| 407 | * @param executorFactory | |
| 408 | * the factory that creates an executor to use | |
| 409 | * @return this instance for fluent chaining | |
| 410 | */ | |
| 411 | public KeepAliveBuilder executor(Supplier<ScheduledExecutorService> executorFactory) { | |
| 412 | this.executorFactory = executorFactory; | |
| 413 |
1
1. executor : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::executor → NO_COVERAGE |
return this; |
| 414 | } | |
| 415 | ||
| 416 | /** | |
| 417 | * Provides an {@link ScheduledExecutorService}. The executor is then used | |
| 418 | * to schedule the task that sends {@link EnquireLink} requests. | |
| 419 | * | |
| 420 | *
 | |
| 421 | * This method is a shortcut to {@code executor(() -> executor)}. | |
| 422 | * | |
| 423 | *
 | |
| 424 | * If this method is called several times, only the last value is used. | |
| 425 | * | |
| 426 | * @param executor | |
| 427 | * the executor to use | |
| 428 | * @return this instance for fluent chaining | |
| 429 | */ | |
| 430 | public KeepAliveBuilder executor(ScheduledExecutorService executor) { | |
| 431 |
2
1. executor : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::executor → NO_COVERAGE 2. lambda$executor$0 : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::lambda$executor$0 → NO_COVERAGE |
return executor(() -> executor); |
| 432 | } | |
| 433 | ||
| 434 | /** | |
| 435 | * The maximum number of consecutive timeouts to {@link EnquireLink} | |
| 436 | * requests to consider that a new session is required. | |
| 437 | * | |
| 438 | *
 | |
| 439 | * The value set using this method takes precedence over any property and | |
| 440 | * default value configured using {@link #maxConsecutiveTimeouts()}. | |
| 441 | * | |
| 442 | *
 | |
| 443 | * .maxConsecutiveTimeouts(5) | |
| 444 | * .maxConsecutiveTimeouts() | |
| 445 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 446 | * .defaultValue(3) | |
| 447 | *
 | |
| 448 | * | |
| 449 | *
 | |
| 450 | * .maxConsecutiveTimeouts(5) | |
| 451 | * .maxConsecutiveTimeouts() | |
| 452 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 453 | * .defaultValue(3) | |
| 454 | *
 | |
| 455 | * | |
| 456 | * In both cases, {@code maxConsecutiveTimeouts(5)} is used. | |
| 457 | * | |
| 458 | *
 | |
| 459 | * If this method is called several times, only the last value is used. | |
| 460 | * | |
| 461 | *
 | |
| 462 | * If {@code null} value is set, it is like not setting a value at all. The | |
| 463 | * property/default value configuration is applied. | |
| 464 | * | |
| 465 | * @param max | |
| 466 | * the maximum consecutive timeouts | |
| 467 | * @return this instance for fluent chaining | |
| 468 | */ | |
| 469 | public KeepAliveBuilder maxConsecutiveTimeouts(Integer max) { | |
| 470 |
1
1. maxConsecutiveTimeouts : removed call to fr/sii/ogham/core/builder/configuration/ConfigurationValueBuilderHelper::setValue → NO_COVERAGE |
maxConsecutiveTimeoutsValueBuilder.setValue(max); |
| 471 |
1
1. maxConsecutiveTimeouts : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::maxConsecutiveTimeouts → NO_COVERAGE |
return this; |
| 472 | } | |
| 473 | ||
| 474 | /** | |
| 475 | * The maximum number of consecutive timeouts to {@link EnquireLink} | |
| 476 | * requests to consider that a new session is required. | |
| 477 | * | |
| 478 | *
 | |
| 479 | * This method is mainly used by {@link Configurer}s to register some | |
| 480 | * property keys and/or a default value. The aim is to let developer be able | |
| 481 | * to externalize its configuration (using system properties, configuration | |
| 482 | * file or anything else). If the developer doesn't configure any value for | |
| 483 | * the registered properties, the default value is used (if set). | |
| 484 | * | |
| 485 | *
 | |
| 486 | * .maxConsecutiveTimeouts() | |
| 487 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 488 | * .defaultValue(3) | |
| 489 | *
 | |
| 490 | * | |
| 491 | *
 | |
| 492 | * Non-null value set using {@link #maxConsecutiveTimeouts(Integer)} takes | |
| 493 | * precedence over property values and default value. | |
| 494 | * | |
| 495 | *
 | |
| 496 | * .maxConsecutiveTimeouts(5) | |
| 497 | * .maxConsecutiveTimeouts() | |
| 498 | * .properties("${custom.property.high-priority}", "${custom.property.low-priority}") | |
| 499 | * .defaultValue(3) | |
| 500 | *
 | |
| 501 | * | |
| 502 | * The value {@code 5} is used regardless of the value of the properties and | |
| 503 | * default value. | |
| 504 | * | |
| 505 | *
 | |
| 506 | * See {@link ConfigurationValueBuilder} for more information. | |
| 507 | * | |
| 508 | * | |
| 509 | * @return the builder to configure property keys/default value | |
| 510 | */ | |
| 511 | public ConfigurationValueBuilder<KeepAliveBuilder, Integer> maxConsecutiveTimeouts() { | |
| 512 |
1
1. maxConsecutiveTimeouts : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::maxConsecutiveTimeouts → RUN_ERROR |
return maxConsecutiveTimeoutsValueBuilder; |
| 513 | } | |
| 514 | ||
| 515 | @Override | |
| 516 | public KeepAliveOptions build() { | |
| 517 | KeepAliveOptions keepAliveOptions = new KeepAliveOptions(); | |
| 518 |
1
1. build : removed call to fr/sii/ogham/sms/sender/impl/cloudhopper/KeepAliveOptions::setEnable → RUN_ERROR |
keepAliveOptions.setEnable(enableValueBuilder.getValue()); |
| 519 |
1
1. build : removed call to fr/sii/ogham/sms/sender/impl/cloudhopper/KeepAliveOptions::setEnquireLinkInterval → RUN_ERROR |
keepAliveOptions.setEnquireLinkInterval(enquireLinkIntervalValueBuilder.getValue()); |
| 520 |
1
1. build : removed call to fr/sii/ogham/sms/sender/impl/cloudhopper/KeepAliveOptions::setEnquireLinkTimeout → RUN_ERROR |
keepAliveOptions.setEnquireLinkTimeout(enquireLinkTimeoutValueBuilder.getValue()); |
| 521 |
1
1. build : removed call to fr/sii/ogham/sms/sender/impl/cloudhopper/KeepAliveOptions::setConnectAtStartup → RUN_ERROR |
keepAliveOptions.setConnectAtStartup(connectAtStartupValueBuilder.getValue()); |
| 522 |
2
1. build : negated conditional → RUN_ERROR 2. build : removed call to fr/sii/ogham/sms/sender/impl/cloudhopper/KeepAliveOptions::setExecutor → RUN_ERROR |
keepAliveOptions.setExecutor(executorFactory != null ? executorFactory : defaultEnquireLinkTimerFactory()); |
| 523 |
1
1. build : removed call to fr/sii/ogham/sms/sender/impl/cloudhopper/KeepAliveOptions::setMaxConsecutiveTimeouts → RUN_ERROR |
keepAliveOptions.setMaxConsecutiveTimeouts(maxConsecutiveTimeoutsValueBuilder.getValue()); |
| 524 |
1
1. build : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::build → RUN_ERROR |
return keepAliveOptions; |
| 525 | } | |
| 526 | ||
| 527 | /** | |
| 528 | * Default factory that provides a {@link ScheduledExecutorService} | |
| 529 | * executor. As only one thread is needed (only one task) to regularly send | |
| 530 | * {@link EnquireLink}s, it uses | |
| 531 | * {@link Executors#newSingleThreadScheduledExecutor(ThreadFactory)}. | |
| 532 | * | |
| 533 | *
 | |
| 534 | * The thread is named {@code EnquireLink-<generated number>}. | |
| 535 | * | |
| 536 | * @return the factory | |
| 537 | */ | |
| 538 | public static Supplier<ScheduledExecutorService> defaultEnquireLinkTimerFactory() { | |
| 539 |
2
1. lambda$defaultEnquireLinkTimerFactory$1 : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::lambda$defaultEnquireLinkTimerFactory$1 → NO_COVERAGE 2. defaultEnquireLinkTimerFactory : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::defaultEnquireLinkTimerFactory → RUN_ERROR |
return () -> Executors.newSingleThreadScheduledExecutor(KeepAliveBuilder::newThread); |
| 540 | } | |
| 541 | ||
| 542 | private static Thread newThread(Runnable runnable) { | |
| 543 | Thread thread = new Thread(runnable); | |
| 544 |
1
1. newThread : removed call to java/lang/Thread::setName → NO_COVERAGE |
thread.setName("EnquireLink-" + enquireLinkThreadCounter.incrementAndGet()); |
| 545 |
1
1. newThread : replaced return value with null for fr/sii/ogham/sms/builder/cloudhopper/KeepAliveBuilder::newThread → NO_COVERAGE |
return thread; |
| 546 | } | |
| 547 | } | |
Mutations | ||
| 92 |
1.1 |
|
| 93 |
1.1 |
|
| 134 |
1.1 |
|
| 174 |
1.1 |
|
| 175 |
1.1 |
|
| 216 |
1.1 |
|
| 255 |
1.1 |
|
| 256 |
1.1 |
|
| 297 |
1.1 |
|
| 341 |
1.1 |
|
| 342 |
1.1 |
|
| 388 |
1.1 |
|
| 413 |
1.1 |
|
| 431 |
1.1 2.2 |
|
| 470 |
1.1 |
|
| 471 |
1.1 |
|
| 512 |
1.1 |
|
| 518 |
1.1 |
|
| 519 |
1.1 |
|
| 520 |
1.1 |
|
| 521 |
1.1 |
|
| 522 |
1.1 2.2 |
|
| 523 |
1.1 |
|
| 524 |
1.1 |
|
| 539 |
1.1 2.2 |
|
| 544 |
1.1 |
|
| 545 |
1.1 |


USD/CAD consolidates in a range, around mid-1.3200s
by Haresh Menghani- USD/CAD seemed struggling to build on Friday’s intraday upsurge.
- A subdued USD price action kept a lid on any strong follow-through.
- Weaker oil prices undermined the loonie and helped limit the downside.
The USD/CAD pair extended its sideways consolidative price action through the early European session on Monday and remained confined in a narrow trading band, around mid-1.3200s.
A combination of diverging forces failed to assist the pair in building the previous session's strong intraday upsurge of nearly 100 pips, triggered by stellar US NFP report and dismal Canadian employment details.
Focus on trade developments, FOMC
The US dollar failed to capitalize on the post-NFP positive move and remained on the defensive amid persistent uncertainty over a potential US-China trade deal ahead of the December 15 news tariffs deadline.
On the other hand, the Canadian dollar was being weighed down by a modest pullback in crude oil prices, which eroded a part of Friday’s upsurge to 12-week tops on the back of bigger output cuts by OPEC and its allies.
It is worth reporting that Saudi Arabia has agreed to provide 400,000 bpd of additional cuts, beyond what was agreed during Friday’s meeting, if OPEC+ averaged its part of 1.7 million bpd through the first quarter of 2020.
The pair now seems to have entered a bullish consolidation phase as market participants now seemed reluctant to place any aggressive bets, rather preferred to wait on the sidelines ahead of the latest FOMC policy update.
The Fed is scheduled to announce its decision on Wednesday, which coupled with a duo of important US macro releases – consumer inflation figures and monthly retail sales data – will provide a fresh directional impetus to the major.
In the meantime, the pair seems more likely to continue with its subdued trading action, though the incoming trade-related headlines might continue to influence the USD price dynamics and produce some short-term trading opportunities.
Technical levels to watch
USD/CAD
| Overview | |
|---|---|
| Today last price | 1.3253 |
| Today Daily Change | -0.0006 |
| Today Daily Change % | -0.05 |
| Today daily open | 1.3259 |
| Trends | |
|---|---|
| Daily SMA20 | 1.326 |
| Daily SMA50 | 1.3217 |
| Daily SMA100 | 1.323 |
| Daily SMA200 | 1.328 |
| Levels | |
|---|---|
| Previous Daily High | 1.3272 |
| Previous Daily Low | 1.317 |
| Previous Weekly High | 1.3322 |
| Previous Weekly Low | 1.3158 |
| Previous Monthly High | 1.3328 |
| Previous Monthly Low | 1.3114 |
| Daily Fibonacci 38.2% | 1.3233 |
| Daily Fibonacci 61.8% | 1.3209 |
| Daily Pivot Point S1 | 1.3196 |
| Daily Pivot Point S2 | 1.3133 |
| Daily Pivot Point S3 | 1.3095 |
| Daily Pivot Point R1 | 1.3297 |
| Daily Pivot Point R2 | 1.3335 |
| Daily Pivot Point R3 | 1.3398 |


Raffa
Women
Men
Sale
Accessories
3 items
NEW
ARRIVALS
ADD TO CART
LONG TRICOLOUR JERSEY
$
170.00
(12 reviews)
ADD TO CART
BREVET INSULATED VEST
$
210.00
(339 reviews)
ADD TO CART
RCC PRO TEAM BIB SHORTS II
$
295.00
(104 reviews)
SIGNUP
TODAY!


--- title: Creating an expository graph for a talk author: Jeff Leek date: '2017-10-02' slug: creating-an-expository-graph-for-a-talk categories: [] tags: [] ---
I’m co-teaching a data science class at Johns Hopkins with John Muschelli. I gave the lectures on EDA and he just gave a lecture on how to create an “expository graph”. When we teach the class an exploratory graph is the kind of graph you make for yourself just to try to understand a data set. An expository graph is one where you are trying to communicate information to someone else.
When you are making an exploratory graph it is usually simple, with no axes, legends, fancy colors, or other effort to make it pretty, understandable and clear. John has a great blog post on how to build up a figure that is expository.
Recently I gave a talk at McGill University and needed to create a plot for the talk. I figured one more example is always better for everything, so I thought I’d go through my process here.
I wanted to show the p-value distribution from the tidy-pvals package. So first I loaded the data:
library(tidypvals)
library(ggridges)
## Loading required package: ggplot2
library(dplyr)
##
## Attaching package: 'dplyr'
## The following objects are masked from 'package:stats':
##
## filter, lag
## The following objects are masked from 'package:base':
##
## intersect, setdiff, setequal, union
library(ggplot2)
library(forcats)
data(allp)
I knew I wanted to use the ggridges package so I read the docs and started with the easiest version:
allp %>%
ggplot(aes(x = pvalue, y = field)) +
geom_density_ridges()
## Picking joint bandwidth of 0.00413
Right away I saw there were some problems here. First of all, clearly a p-value greater than one shouldn’t be in there, so that was a mistake. I also don’t like that you can’t really see the values because most of the action is near zero.
So let’s fix the x-axis a bit. I spent a few minutes fiddling and decided I just wanted to see the values between 0 and 0.25.
allp %>%
ggplot(aes(x = pvalue, y = field)) +
geom_density_ridges() +
xlim(c(0,0.25))
## Picking joint bandwidth of 0.00401
## Warning: Removed 359521 rows containing non-finite values
## (stat_density_ridges).
Ok that’s better, but I don’t really like the grey background so let’s pick a different background color
allp %>%
ggplot(aes(x = pvalue, y = field)) +
geom_density_ridges() +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## Picking joint bandwidth of 0.00401
## Warning: Removed 359521 rows containing non-finite values
## (stat_density_ridges).
That’s a bit prettier, but we see that field is sometimes NA so we need to remove those values.
allp %>%
filter(!is.na(field)) %>%
ggplot(aes(x = pvalue, y = field)) +
geom_density_ridges() +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## Picking joint bandwidth of 0.00404
## Warning: Removed 349629 rows containing non-finite values
## (stat_density_ridges).
And actually the density plots are a little weird for p-values, lets see if we can turn them into something a little more like a histogram, which I think fits this data type better. To do that we have to change the parameters in geom_density_ridges
.
allp %>%
filter(!is.na(field)) %>%
ggplot(aes(x = pvalue, y = field)) +
geom_density_ridges(stat = "binline") +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## `stat_binline()` using `bins = 30`. Pick better value with `binwidth`.
## Warning: Removed 349629 rows containing non-finite values (stat_binline).
Ok but I think it would look better if it was a little bit higher resolution, let’s up the number of bins
allp %>%
filter(!is.na(field)) %>%
ggplot(aes(x = pvalue, y = field)) +
geom_density_ridges(stat = "binline",bins=50) +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## Warning: Removed 349629 rows containing non-finite values (stat_binline).
Ok but as people have pointed out the spike at 0.05 is due to censoring (p-values reported like \(P < 0.05\)). So let’s break it down by operator.
allp %>%
filter(!is.na(field)) %>%
ggplot(aes(x = pvalue, y = field,fill=operator)) +
geom_density_ridges(stat = "binline",bins=50) +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## Warning: Removed 349629 rows containing non-finite values (stat_binline).
Ok there aren’t that many greater than p-values and it makes the plot messy so let’s drop those
allp %>%
filter(!is.na(field)) %>%
filter(operator != "greaterthan") %>%
ggplot(aes(x = pvalue, y = field,fill=operator)) +
geom_density_ridges(stat = "binline",bins=50) +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## Warning: Removed 332965 rows containing non-finite values (stat_binline).
The histograms overlap a bit so let’s alpha blend the colors.
allp %>%
filter(!is.na(field)) %>%
filter(operator != "greaterthan") %>%
ggplot(aes(x = pvalue, y = field,fill=operator)) +
geom_density_ridges(stat = "binline",
bins=50,alpha=0.25) +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## Warning: Removed 332965 rows containing non-finite values (stat_binline).
There is some funkiness in how the histogram bins are computed so I went to the internet and figured out I needed to set the boundary at 0 and make the bins be closed on the right.
allp %>%
filter(!is.na(field)) %>%
filter(operator != "greaterthan") %>%
ggplot(aes(x = pvalue, y = field,fill=operator)) +
geom_density_ridges(stat = "binline",
bins=50,alpha=0.25,
boundary=0,closed="right") +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE)
## Warning: Removed 332965 rows containing non-finite values (stat_binline).
Now we make sure that there isn’t wasted space on the y-axis by using the expand argument.
allp %>%
filter(!is.na(field)) %>%
filter(operator != "greaterthan") %>%
ggplot(aes(x = pvalue, y = field,fill=operator)) +
geom_density_ridges(stat = "binline",
bins=50,alpha=0.25,
boundary=0,closed="right") +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE) +
scale_y_discrete(expand=c(0,0))
## Warning: Removed 332965 rows containing non-finite values (stat_binline).
Remove the baseline from the plot for true ggridges coolness
allp %>%
filter(!is.na(field)) %>%
filter(operator != "greaterthan") %>%
ggplot(aes(x = pvalue, y = field,fill=operator)) +
geom_density_ridges(stat = "binline",
bins=50,alpha=0.25,
boundary=0,closed="right",
draw_baseline=FALSE) +
xlim(c(0,0.25)) +
theme_ridges(grid = FALSE) +
scale_y_discrete(expand=c(0,0))
## Warning: Removed 332965 rows containing non-finite values (stat_binline).
That’s definitely not a perfect plot, but it worked for my talk and was at least able to communicate a couple of the key points (about variation by field, variation by operator, and spikes at critical values).
If I was going beyond the talk I’d probably reduce the number of fields displayed or really increase the size of the plot. I’d probably make the bin width even smaller and I’d add a title. I’d also probably clean up the “greaterthan” and “lessthan” to be “Greater than” and “Less than”.
Regardless, I’m always surprised how much work it takes to go from an exploratory plot I’m just looking at myself to one I’d show to other people.


A Complete Free (forever)* Solution for School, Online Education, HCM, CRM, Supply Chain, GL, Book Keeping, Assets Tracking, Visitor and many more applications.
Elish ERP is a complete Mobile/desktop App to manage Students, Employee, Payroll, Customer, Leads, Sales/Orders and Help Desk/Service Calls. Elish ERP also contain moduled for eHealth LAB management and Education/Student and Learning Management modules.
* free community version
"Why Elish ERP?"
Live Assets & Employee Location Tracking
GPS/Picture Employee & Visitor Attendance
Payroll
Complete CRM
Live Inventory Management
No Language Barrier
This app is available in 10
A complete ERP App to manage customer details, documents, Billing, finance transactions management system.
A complete ERP App connecting Customers, Service Providers through modern advance communications channels.
A complete knowledge base which covers lots of field and topic and provide a cursory reading to whom who are looking for.
We provide a wide platform to search Service povider anywhere in india as per category and with location and provide a medium to communicate with them regarding any problem.
Ask freely with Personal Service advisers through ElishConsulting.com either online or offline.
A complete knowledge base which covers lots of field and topic and provide a cursory reading to whom who are looking for something new.
We provide a wide platform to search CRM Service Providers anywhere in india as per category and with location and provide a medium to communicate with them regarding any problem.
Ask freely with CRM advisers through ELISH Consulting either online or offline.


So easy to use, even your dog could do it.
We take care of all the dog breeds.
Your pets are in great hands with a loving sitter.
Simple and affordable price plans for you and your dog.
$10 for 6 hours
$15 for 10 hours
$17 for 12 hours
$12 for 6 hours
$17 for 10 hours
$20 for 12 hours
$14 for 6 hours
$19 for 10 hours
$23 for 12 hours


The proxy server politely waited for a response from the upstream server. The upstream server was caught sleeping on the job.
If you feel offended or think that this shouldn't be an error, ">shoot us a love letter and let us know you saw this.


This plugin allows you to use PureCM as a SCM.
Plugin Information |
|---|
No information for the plugin 'purecm' is available. It may have been removed from distribution. |
Configuring the PureCM Plugin
You first need to install the purecm client on the Jenkins server. You then need to install the PureCM plugin within Jenkins.
Configuring the PureCM Server Settings
The Jenkins plugin uses the PureCM command line tool - pcm. After installing the PureCM Client this should put on the path. By default, Jenkins will use the command 'pcm' so you do not need to update the PureCM Server Settings.
If you have multiple versions of PureCM installed or have modified the location of PureCM then you need to tell Jenkins which pcm to use. To do this go to 'Manage Jenkins | Configure System'. Under the PureCM heading there is a field for 'Commadn line executable' where you can enter the path to the pcm executable.
Configuring a Job to Use PureCM
In the Job Configuration screen there is a section for Source Code Management. If PureCM is correctly configured then it will appear as one of the options. Select PureCM to reveal the following options:
Repository
This should include the name of the Repository containing the stream.
Stream
This will be the full path of the stream being used for this job. For example this might be 'Project 1\Version 1\Version 1'.
This is the stream path rather than version path. To get the stream path for a version open the PureCM GUI, open the properties for the version and go to the streams page.
Clean Copy
If this is selected then every build will delete the old workspace and create a new workspace. In almost all circumstances this will not be necessary and updating the existing workspace will suffice. Obviously this will have big performance implications if the workspace is large.


Rajasthan urban local body polls peaceful, 72% turnout
Stray incidents of violence reported from Bharatpur, Banswara, Bhiwadi, Beawar
by Special CorrespondentNearly 72% voters exercised their franchise in the elections to 49 municipal bodies in Rajasthan on Saturday, with a maximum of 91.67% turnout in Nasirabad municipality of Ajmer district.
Polling took place peacefully, barring stray incidents of violence which left a few persons injured.
An inebriated person damaged an EVM in Churu, after which the apparatus was replaced.
The voter turnout touched 80% at some places in 24 districts where the polling was held. A total of 7,944 candidates were in the fray for election of 2,100 ward councillors. Over 33 lakh voters were eligible for exercising their franchise, for which 3,479 polling booths were set up across the State.
The results will be declared after counting of votes on November 19, while the election for chairpersons and deputy chairpersons of the urban local bodies will be held on November 26 and 27, respectively.
Chief Electoral Officer Shyam Singh Rajpurohit said the supervisors were given the responsibility to look after the law and order at their allotted centres. However, the Congress and the BJP workers clashed with each other in Bharatpur, Banswara, Bhiwadi and Beawar.
Four injured
Four persons were injured in the fight with lathi and stones between two rival groups of party workers in Bharatpur. Tension prevailed in Jhunjhunu after allegations of bogus voting, while the police dispersed two groups hurling stones at each other in Sikar.
Energy Minister B.D. Kalla cast his vote in Bikaner, while Tourism Minister Vishvendra Singh exercised his franchise in Bharatpur and Minister of State for Technical Education Subhash Garg in Bharatpur. The Leader of the Opposition in the State Assembly, Gulab Chand Kataria, cast his vote in Udaipur.
(With inputs from PTI)


BOSNA! A film review by Gareth Rees Copyright 1994 Gareth Rees
Director: Bernard-Henri Levy, Alain Ferrari Camera: Pierre Boffety Editors: Frederic Lossignol, Yann Kassile Music: Denis Barbier Duration: 117 minutes Bosnia/France 1994
It's hard to approach the good and bad in this film without being caught up a discussion of the message of BOSNA!, for this is a film that explicitly sets out to convert its audience to its side, to make people aware of the war and to try to influence them to pressure their governments to intervene. It's a film that's very aware of itself, of the process of its making and of the influence it might have: for example, Mitterand's visit to Bosnia is portrayed as an outcome of information given to the French President by the director, Bernard-Henri Levy.
The film is full of very disturbing images: a mother and child fleeing from snipers in Sarajevo; bodies littering a street after a shell has landed on a bread queue, many of them with legs or faces blown off; starving prisoners staring at the camera through the barbed wire of a concentration camp. It's impossible not to be moved by the suffering of these people, and difficult not to feel anger at the inaction of the diplomats who do little but talk while people are fighting for their lives and homes. The film makes much of comparisons between Western indifference to Bosnia today and Western indifference to Czechoslovakia and the Spanish Republic in the 1930s. There is, suggests Levy, the same denial, the same explanations that it's all much too complex to get involved in. In 1945 people saw pictures of the concentration camps in Poland and said "never again", but now that the camps are back it seems that we would rather deny them, or suggest that there's fault on both sides, then determine to stop the atrocities.
If there is anything I don't like about BOSNA!, it is the incessant wordiness of the voice-over. Perhaps Levy was so anxious to persuade that he didn't dare to let the audience come to their own conclusions. At times sounding like a Biblical prophet, at times hectoring us, at times reflecting on how the war affects our image of ourselves as Europeans, the narration never lets the eloquent pictures speak for themselves, pictures that have more than enough power to move and to persuade on their own.
*
Cambridge Arts Cinema hosted the British premiere of BOSNA!, a powerful and disturbing film about the war in Bosnia-Herzegovina and about the reluctance of governments in Western Europe to acknowledge what was going on and their refusal to offer real assistance to Bosnia. Director Bernard-Henri Levy gave a short talk before the film. He said that the BOSNA!, filmed in Sarajevo between September 1993 and January 1994, and in other parts of Bosnia in March and April of this year, was neither a dispassionate documentary nor an artistic film; but was the answer to the question "What can I do to help these people, to make their heroic struggle known?" He wanted the film to be as militant and passionate as possible without being inaccurate in its presentation of the facts.
A question and answer session followed the film, chaired by Leonard Doyle of "The Independent." The questioners mostly expressed positive opinions of the films and asked Levy about the relationship between his film and a wider historical context. The film made much of the comparisons between the West s failure to intervene in Bosnia and its failure to take a stand over Czechoslovakia and Spain in the 1930s, but what about the many conflicts within and between other ex-communist states, such as Armenia and Azerbaijan? Levy said that his own memory and family history was concerned with World War Two, and so that was where he turned more naturally. He also wanted to try to convince people in England that they should come to the aid of Bosnia as they had come to the aid of France. He suggested that the West wasn't doing enough to help the post-communist states towards democracy, and that we risked the creation of monsters from the volatile mixture of fascism, nationalism and communism in these countries.
One questioner suggested that the reluctance of the West to become involved was out of a fear of Islamic fundamentalism in what the media portray as a predominately Muslim state. Levy agreed, and said that this was an inaccurate view of Bosnia. Sarajevo had been a "second Jerusalem," a city in which sizable communities of Jews, Christians and Muslims lived and worshiped in peace. Levy described a meeting with Bosian President Izetbegovic at the world premiere of BOSNA! in early June. Izetbegovic said that he had always refused a fundamentalist Islamic state, but if the West were to stand back and lets the country be partitioned along ethnic lines, then Bosnia may have to become one.
One questioner disagreed. He said that the conflict in Bosnia was much more complex than the film suggested, and that it was a mistake not to examine the origins of the present conflict in World War Two, in which the Serbians resisted fascism while Muslims were recruited into the German army. Levy responded passionately. He said that being right in 1945 didn't make the Serbians right now; even if their grandparents had fought Hitler, that didn t excuse concentration camps and ethnic cleansing.
Bernard-Henri Levy made a very positive impression on me; he seemed full of respect for the Bosnians he had met and spoken with and filmed, and full of energy and passion to tell their story to the world.
.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Communicating with your instrument¶
Note
If you have been using PyVISA before version 1.5, you might want to read Migrating from PyVISA < 1.5.
An example¶
Let’s go in medias res and have a look at a simple example:
>>> import pyvisa
>>> rm = pyvisa.ResourceManager()
>>> rm.list_resources()
('ASRL1::INSTR', 'ASRL2::INSTR', 'GPIB0::14::INSTR')
>>> my_instrument = rm.open_resource('GPIB0::14::INSTR')
>>> print(my_instrument.query('*IDN?'))
This example already shows the two main design goals of PyVISA: preferring simplicity over generality, and doing it the object-oriented way.
After importing pyvisa
, we create a ResourceManager
object. If called
without arguments, PyVISA will prefer the default backend (NI) which tries to
find the VISA shared library for you. If it fails it will fall back to
pyvisa-py if installed. You can check what backend is used and the location of
the shared library used, if relevant, simply by:
>>> print(rm)
<ResourceManager('/path/to/visa.so')>
Note
In some cases, PyVISA is not able to find the library for you resulting in
an OSError
. To fix it, find the library path yourself and pass it to
the ResourceManager constructor. You can also specify it in a configuration
file as discussed in Configuring the backend.
Once that you have a ResourceManager
, you can list the available resources
using the list_resources
method. The output is a tuple listing the
VISA resource names. You can use a dedicated regular expression syntax
to filter the instruments discovered by this method. The syntax is described in
details in list_resources()
. The default value is ‘?*::INSTR’ which means that
by default only instrument whose resource name ends with ‘::INSTR’ are listed
(in particular USB RAW resources and TCPIP SOCKET resources are not listed).
In this case, there is a GPIB instrument with instrument number 14, so you ask
the ResourceManager
to open “‘GPIB0::14::INSTR’” and assign the returned
object to the my_instrument.
Notice open_resource
has given you an instance of GPIBInstrument
class
(a subclass of the more generic Resource
).
>>> print(my_instrument)
<GPIBInstrument('GPIB::14')>
There many Resource
subclasses representing the different types of
resources, but you do not have to worry as the ResourceManager
will provide
you with the appropriate class. You can check the methods and attributes of
each class in the Resource classes
Then, you query the device with the following message: '\*IDN?'
.
Which is the standard GPIB message for “what are you?” or – in some cases –
“what’s on your display at the moment?”. query
is a short form for a
write
operation to send a message, followed by a read
.
So:
>>> my_instrument.query("*IDN?")
is the same as:
>>> my_instrument.write('*IDN?')
>>> print(my_instrument.read())
Note
You can access all the opened resources by calling
rm.list_opened_resources()
. This will return a list of Resource
,
however note that this list is not dynamically updated.
Getting the instrument configuration right¶
For most instruments, you actually need to properly configure the instrument
so that it understands the message sent by the computer (in particular how to
identifies the end of the commands) and so that computer knows when the
instrument is done talking. If you don’t you are likely to see a VisaIOError
reporting a timeout.
For message based instruments (which covers most of the use cases), this
usually consists in properly setting the read_termination
and
write_termination
attribute of the resource. Resources have more attributes
described in Resources, but for now we will focus on those two.
The first place to look for the values you should set for your instrument is the manual. The information you are looking is usually located close to the beginning of the IO operation section of the manual. If you cannot find the value, you can try to iterate through a couple of standard values but this is not recommended approach.
Once you have that information you can try to configure your instrument and start communicating as follows:
>>> my_instrument.read_termination = '\n'
>>> my_instrument.write_termination = '\n'
>>> my_instrument.query('*IDN?')
Here we use ‘n’ known as ‘line feed’. This is a common value, another one is ‘r’ i.e. ‘carriage return’, and in some cases the null byte ‘0’ is used.
In in an ideal world, this will work and you will be able to get an answer from your instrument. If it does not, it means the settings are likely wrong (the documentation does not always shine by its clarity). In the following we will discuss common debugging tricks, if nothing works feel free to post on the PyVISA issue tracker. If you do be sure to describe in detail your setup and what you already attempted.
Note
The particular case of reading back large chunk of data either in ASCII or binary format is not discussed below but in Reading and Writing values.
Making sure the instrument understand the command¶
When using query, we are testing both writing to and reading from the instrument. The first thing to do is to try to identify if the issue occurs during the write or the read operation.
If your instrument has a front panel, you can check for errors (some instrument will display a transient message right after the read). If an error occurs, it may mean your command string contains a mistake or the instrument is using a different set of command (some instrument supports both a legacy set of commands and SCPI commands). If you see no error it means that either the instrument did not detect the end of your message or you just cannot read it. The next step is to determine in what situation we are.
To do so, you can look for a command that would produce a visible/measurable
change on the instrument and send it. In the absence of errors, if the expected
change did not occur it means the instrument did not understand that the
command was complete. This points out to an issue with the write_termination
.
At this stage, you can go back to the manual (some instruments allow to switch
between the recognized values), or try standards values (such as ‘n’,
‘r’, combination of those two, ‘0’).
Assuming you were able to confirm that the instrument understood the command
you sent, it means the reading part is the issue, which is easier to
troubleshoot. You can try different standard values for the read_termination
,
but if nothing works you can use the read_bytes()
method. This method will read
at most the number of bytes specified. So you can try reading one byte at a
time till you encounter a time out. When that happens most likely the last
character you read is the termination character. Here is a quick example:
my_instrument.write('*IDN?')
while True:
print(my_instrument.read_bytes(1))
If read_bytes()
times out on the first read, it actually means that the
instrument did not answer. If the instrument is old it may be because your are
too fast for it, so you can try waiting a bit before reading (using
time.sleep from Python standard library). Otherwise, you either use a command
that does not cause any answer or actually your write does not work (go back
up a couple of paragraph).
The above focused on using only PyVISA, if you are running Windows, or MacOS you are likely to have access to third party tools that can help. Some tips to use them are given in the next section.
Note
Some instruments do not react well to a communication error, and you may have to restart it to get it to work again.
Using third-party softwares¶
The implementation of VISA from National Instruments and Keysight both come with tools (NIMax, Keysight Connection Expert) that can be used to figure out what is wrong with your communication setup.
In both cases, you can open an interactive communication session to your instrument and tune the settings using a GUI (which can make things easier). The basic procedure is the one described above, if you can make it work in one of those tools you should be able, in most cases, to get it to work in PyVISA. However if it does not work using those tools, it won’t work in PyVISA.
Hopefully those simple tips will allow you to get through. In some cases, it may not be the case and you are always welcome to ask for help (but realize that the maintainers are unlikely to have access to the instrument you are having trouble with).


Eric Akis: Spicy chicken dish awakens senses
by Eric AkisLast week, my wife and I both had colds. Luckily, when we’re sick, we crave similar styles of food. Among our favourites are Asian-style dishes with a robust taste and aroma guaranteed to awaken the senses, even when dulled by a cold.
One of our long-time favourites is a Szechuan-style chicken dish we first tried decades ago at Chung King restaurant, on Spadina Avenue in Toronto.
The golden bits of chicken served on an oval platter were coated with sweet, tangy and sticky orange sauce. That aromatic sauce contained garlic, ginger, slightly bitter-tasting pieces of dried orange zest and, most noticeably, numerous whole, small dried red chilies.
As with bay leaves added to soup, those fiery hot chilies were not to be eaten unless you really wanted to feel the burn. They were there to infuse their spicy taste into the chicken and sauce, creating a dish that certainly does awaken the senses.
We started making that style of dish at home after we found a recipe for it in Canadian author Cynthia Wine’s book Hot and Spicy Cooking, published in 1984.
Last week, as my wife and I sniffled, we reminisced about how much we enjoyed that recipe and realized we had not prepared it for a while.
So I took up the challenge and made an adapted version of Wine’s recipe that incorporated aspects of Chinese recipes I found for the dish.
When served with rice and a steamed green vegetable, such as baby bok choy, it yielded three servings. That meant there was enough for dinner for both of us and some leftovers for one — me! — to enjoy the next day for lunch.
Szechuan-style Chicken with Orange and Chilies
Tender bits of chicken are cooked until golden and set in a sweet and sour orange sauce infused with the spicy flavour of whole dried red chilies. The whole chilies are only added for flavour — do not eat them unless you really want to feel the burn!

With a vegetable peeler, thinly peel off the zest from one of the oranges. Cut that zest into 3/4-inch squares and place in a single layer on the baking sheet.
Put zest in the oven for two hours, or until dry and crisp. Remove zest from the oven and set aside until needed.
Cut the orange you removed the zest from, and the other orange, in half. Thoroughly squeeze the juice out each half orange into a bowl.
Pour juice into a measuring cup until you have 3/4 cup. If you don’t, top it up with a bit of water.
Add the 4 tsp soy sauce, sugar, rice vinegar and 1 tsp Chinese Shaoxing wine (or dry sherry) to the juice. Cover and refrigerate mixture until needed.
To ready chicken, place it in a bowl and toss with the egg white, 1 tsp soy sauce, 1 tsp Shaoxing rice cooking wine (or dry sherry) and 1 tsp of the cornstarch. Cover chicken, refrigerate and marinate one or two hours.
When chicken has marinated, heat the oil in a very large non-stick skillet (mine was 12 inches wide) set over medium-high heat. Add the chicken and stir-fry until just cooked through and golden, about four minutes. Remove pan from the heat, lift chicken out of it and set on a plate.
Mix the remaining 2 tsp cornstarch into the orange-juice mixture until dissolved. Set skillet back over medium-high heat. When hot, add the garlic, ginger and whole chili peppers and stir-fry 30 seconds.
Add the orange-juice mixture and dried orange zest to the skillet and bring sauce to a boil. Reduce heat to medium-low and simmer sauce one minute, or until it lightly thickens.
Return chicken to the skillet and heat in the sauce one to two minutes. If you find the sauce has overly reduced, add a bit of chicken broth to thin it. Toss in the sliced green onions and serve.
Eric Akis is the author of eight cookbooks, including seven in his Everyone Can Cook series. His columns appear in the Life section Wednesday and Sunday.


This program is written for 32-Bit Microsoft Windows.
The source code
is provided in Delphi 5.0.
OPERATION OF 'TempSense'
This utility uses the TMEX API to read and view temperatures
from
DS1920/DS1820 devices. This is a multi-threaded program in that
an external thread is created to perform 1-Wire communication
during
program startup. This frees the main GUI thread to perform
updates
on Windows/mouse events and keeps the app from "freezing" during
calls to "Sleep". It requires the 32-Bit Windows TMEX
drivers
to be present.
This example program contains only one window. It displays the
information on DS1920/DS18S20 temperature devices such as the
1-Wire
address and the value of the temperature read by the
device. To switch
adapters or ports, please change the default port adapter
through the
'Default 1-Wire Net' program located in the folder in which the
1-Wire Drivers
were installed.
Ibtmexpw.pas - Pascal
source file for the TMEX calls.
Readme.html -
This file.
TempSense.dpr
- Delphi project file.
TempSense.exe -
Executable.
TempSenseUnit.dfm - Main Form (Window)
of the project.
TempSenseUnit.pas - Main pascal source
file for Main Form.


| Package | com.sibirjak.angara.core |
| Class | public class LoaderItemEvent |
| Inheritance | LoaderItemEvent flash.events.Event |
| Subclasses | ResourceLoaderEvent, SequenceEvent, SequenceManagerEvent |
| Property | Defined by | ||
|---|---|---|---|
| affectedLoaderItem : ILoaderItem
[read-only]
Returns the affected child loader item, which has been added or removed.
| LoaderItemEvent | ||
| loaderItem : ILoaderItem
[read-only]
Returns the event dispatching loader item.
| LoaderItemEvent | ||
| priority : uint [read-only]
Returns the priority the item is added with to the LoaderManager.
| LoaderItemEvent |
| Property | Defined by | ||
|---|---|---|---|
| _affectedLoaderItem : ILoaderItem
Reference to a child oader item, which has been added or removed.
| LoaderItemEvent | ||
| _loaderItem : ILoaderItem
Reference to the event dispatching loader item.
| LoaderItemEvent | ||
| _priority : uint
Loader item priority.
| LoaderItemEvent |
| Method | Defined by | ||
|---|---|---|---|
|
LoaderItemEvent(type:String, loaderItem:ILoaderItem, affectedLoaderItem:ILoaderItem = null, priority:uint = 0)
Creates a new LoaderItemEvent.
| LoaderItemEvent |
| Constant | Defined by | ||
|---|---|---|---|
| ADD : String = "item_added" [static]
An item has been added to the loader manager queue (Schedule)
or to a sequence.
| LoaderItemEvent | ||
| CLEAR : String = "item_clear" [static]
Item container has been cleared.
| LoaderItemEvent | ||
| COMPLETE : String = "item_complete" [static]
Item is complete.
| LoaderItemEvent | ||
| FAILURE : String = "item_failure" [static]
Loading resource has been failed.
| LoaderItemEvent | ||
| PAUSE : String = "item_pause" [static]
Item has been paused.
| LoaderItemEvent | ||
| PROGRESS : String = "item_progress" [static]
Progress of an item has changed.
| LoaderItemEvent | ||
| REMOVE : String = "item_removed" [static]
An item has been removed from the to the loader manager queue (Schedule)
or from the connection pool.
| LoaderItemEvent | ||
| RESUME : String = "item_resume" [static]
Item has been resumed.
| LoaderItemEvent | ||
| STOP : String = "item_stop" [static]
Item has been stopped.
| LoaderItemEvent |
| _affectedLoaderItem | property |
protected var _affectedLoaderItem:ILoaderItem
Reference to a child oader item, which has been added or removed.
| affectedLoaderItem | property |
affectedLoaderItem:ILoaderItem
[read-only]Returns the affected child loader item, which has been added or removed.
Implementation public function get affectedLoaderItem():ILoaderItem
| _loaderItem | property |
protected var _loaderItem:ILoaderItem
Reference to the event dispatching loader item.
| loaderItem | property |
loaderItem:ILoaderItem
[read-only]Returns the event dispatching loader item.
Implementation public function get loaderItem():ILoaderItem
| _priority | property |
protected var _priority:uint
Loader item priority.
Item priority when added to the LoaderManager.
| priority | property |
priority:uint
[read-only]Returns the priority the item is added with to the LoaderManager.
This property is only set in the ADD event of the LoaderManager.
Implementation public function get priority():uint
| LoaderItemEvent | () | constructor |
public function LoaderItemEvent(type:String, loaderItem:ILoaderItem, affectedLoaderItem:ILoaderItem = null, priority:uint = 0)
Creates a new LoaderItemEvent.
Parameterstype:String — Type of the event.
|
|
loaderItem:ILoaderItem — Reference to the affected loader item.
|
|
affectedLoaderItem:ILoaderItem (default = null ) — The affected (added or removed) child loader item.
|
|
priority:uint (default = 0 )
|
| ADD | constant |
public static const ADD:String = "item_added"
An item has been added to the loader manager queue (Schedule) or to a sequence.
The loader manager will start listening to events of the scheduled item (Schedule) or continue loading (Sequence and SequenceManager)
Dispatched by Schedule, Sequence and SequenceManager.
| CLEAR | constant |
public static const CLEAR:String = "item_clear"
Item container has been cleared.
Dispatched by LoaderManager, Sequence and SequenceManager.
| COMPLETE | constant |
public static const COMPLETE:String = "item_complete"
Item is complete.
Dispatched by all loader items.
| FAILURE | constant |
public static const FAILURE:String = "item_failure"
Loading resource has been failed.
Dispatched only by resource loaders.
| PAUSE | constant |
public static const PAUSE:String = "item_pause"
Item has been paused.
Dispatched by all loader items.
| PROGRESS | constant |
public static const PROGRESS:String = "item_progress"
Progress of an item has changed.
Dispatched by all loader items.
| REMOVE | constant |
public static const REMOVE:String = "item_removed"
An item has been removed from the to the loader manager queue (Schedule) or from the connection pool.
The loader manager will stop listening to events of the scheduled item after the Schedule dispatchs this event.
The loader manager will find the next items to load after the ConnectionPool dispatchs this event.
Dispatched by Schedule and ConnectionPool.
| RESUME | constant |
public static const RESUME:String = "item_resume"
Item has been resumed.
Dispatched by all loader items.
| STOP | constant |
public static const STOP:String = "item_stop"
Item has been stopped.
Dispatched by all loader items.


Cisco-IOS-XR-tty-vty-cfg API API Reference
API generated from<EMAIL_ADDRESS>API Endpoint
http://{Controller-IP}:{Controller-Port}/restconf/config/network-topology:network-topology/topology/topology-netconf/node/inetri/yang-ext:mount/
URL '/' code: %2F
Schemes: http
Version: 1.0.0
Leaf Color Code:
Key  Mandatory  OptionalPaths
VTY - Update
Update operation of resource: vty
vtybody object
Successful operation
Internal Error
Response Content-Types: application/json
VTY - Create
Create operation of resource: vty
vtybody object
Successful operation
Internal Error
Response Content-Types: application/json
VTY - Delete
Delete operation of resource: vty
Successful operation
Internal Error
Response Content-Types: application/json
VTY - Retrieve
Retrieve operation of resource: vty
Successful operation
Internal Error
VTY-POOLS - Update
Update operation of resource: vty-pools
vty-poolsbody object
Successful operation
Internal Error
Response Content-Types: application/json
VTY-POOLS - Create
Create operation of resource: vty-pools
vty-poolsbody object
Successful operation
Internal Error
Response Content-Types: application/json
VTY-POOLS - Delete
Delete operation of resource: vty-pools
Successful operation
Internal Error
Response Content-Types: application/json
VTY-POOLS - Retrieve
Retrieve operation of resource: vty-pools
Successful operation
Internal Error
VTY-POOL - Update
Update operation of resource: vty-pool
vty-poolbody object
ID of pool-name
Request Content-Types: application/json
Request Example
{
"last-vty": "integer",
"none": "string",
"first-vty": "integer",
"line-template": "string",
"pool-name": "string"
}
Successful operation
Internal Error
Response Content-Types: application/json
VTY-POOL - Create
Create operation of resource: vty-pool
vty-poolbody object
ID of pool-name
Request Content-Types: application/json
Request Example
{
"last-vty": "integer",
"none": "string",
"first-vty": "integer",
"line-template": "string",
"pool-name": "string"
}
Successful operation
Internal Error
Response Content-Types: application/json
VTY-POOL - Delete
Delete operation of resource: vty-pool
ID of pool-name
Successful operation
Internal Error
Response Content-Types: application/json
VTY-POOL - Retrieve
Retrieve operation of resource: vty-pool
ID of pool-name
Successful operation
Internal Error
Response Content-Types: application/json
Response Example (200 OK)
{
"last-vty": "integer",
"none": "string",
"first-vty": "integer",
"line-template": "string",
"pool-name": "string"
}
Schema Definitions
vty_schema:
VTY Pools configuration
- vty-pools: object
-
List of VTY Pools
-
- vty-pool: object[]
-
VTY Pool
-
object - last-vty: integer
-
Last VTY number,For default configure between 0-99,For user-defined configure between 5-99 ,For fault-manager configure between 100-199
- none: string
-
Empty Option
- first-vty: integer
-
First VTY number,For default VTY use 0,For user-defined use 5,For fault-manager use 100
- line-template: string
-
Name of line template
- pool-name: string
-
For configuring range for default pool use 'default',For configuring range for fault-manager pool use 'fm',For configuring range for any user defined pool use any other string
Example
{
"vty-pools": {
"vty-pool": [
{
"last-vty": "integer",
"none": "string",
"first-vty": "integer",
"line-template": "string",
"pool-name": "string"
}
]
}
}
vty-pools_schema:
List of VTY Pools
- vty-pool: object[]
-
VTY Pool
-
object - last-vty: integer
-
Last VTY number,For default configure between 0-99,For user-defined configure between 5-99 ,For fault-manager configure between 100-199
- none: string
-
Empty Option
- first-vty: integer
-
First VTY number,For default VTY use 0,For user-defined use 5,For fault-manager use 100
- line-template: string
-
Name of line template
- pool-name: string
-
For configuring range for default pool use 'default',For configuring range for fault-manager pool use 'fm',For configuring range for any user defined pool use any other string
Example
{
"vty-pool": [
{
"last-vty": "integer",
"none": "string",
"first-vty": "integer",
"line-template": "string",
"pool-name": "string"
}
]
}
vty-pool_schema:
- last-vty: integer
-
Last VTY number,For default configure between 0-99,For user-defined configure between 5-99 ,For fault-manager configure between 100-199
- none: string
-
Empty Option
- first-vty: integer
-
First VTY number,For default VTY use 0,For user-defined use 5,For fault-manager use 100
- line-template: string
-
Name of line template
- pool-name: string
-
For configuring range for default pool use 'default',For configuring range for fault-manager pool use 'fm',For configuring range for any user defined pool use any other string
Example
{
"last-vty": "integer",
"none": "string",
"first-vty": "integer",
"line-template": "string",
"pool-name": "string"
}


this work intends to demonstrate the role of aesthetics in source code in understanding a program. this demonstration will resolve the contradiction that, on one side, understanding is multi-faceted and, on the other side, there are language-independent and domain-independent practices which facilitate understanding.
the significance of the study is the possibility to adopt close-reading practices to a body of texts which has so far remained largely unexplored. it is using both cross-disciplinary frameworks to further qualify a somewhat new and unique kind of text.
this study contributes to a finer understanding of programming as a a practice in-between engineering and literature; it creates this middle-ground not at the higher level of general concepts, but at the practical level of reading and writing. this practical approach ties the notions of understanding that we explore within a broader socio-economical context, and as such requalifies both engineering and literature as, respectively, sociotechnics and socioaesthetics.
there has been no significant study of the aesthetics of source code from a cross-disciplinary perspective. either you have cross-disciplinary (software studies, etc.) and they do not (or very little) (or through the poetics, not the aesthetics) address source code directly, or you have computer science and they only address it in terms of their own particular practice, sometimes reaching out to “literary” or “beautiful”, but without extensive theoretical backing. this thesis proposes to have both enter in a dialogue. a final component of the problem at hand is that there is little intertextual analyses of source code from a literary perspective, so far contained to text-by-text readings rather than more holistic approaches.
the methodology is inductive, and qualitative. by gathering and reading primary sources, i establish the practice-based aesthetic standards to which practitioners submit their work. i propose an inductive approach first because there is no “criticism” in programming, but rather “peer-reviewing”, which means that anyone who writes, reads, and therefore what the writers and the readers say is equally important. second because the cross-disciplinary approach of analyzing those texts inherently forbids the blanket use of one theory mapped onto possibily different practices. rather, establishing a set of practices and then invoking theoretical frameworks to further qualify these practices avoids the trap of overfitting.
(1) i am assuming that aesthetics (including the lack thereof) is an essential part of source code. since it is not possible to separate both, every text becomes a valid means of examination since it would display some dimension of aesthetic properties. of course, some texts might be more useful than others. (2) i am assuming that writing practices are influenced by additional writing published in the field, from the art of computer programming to blog posts and best-practices lists (kinda theory of communicative action).
in terms of limitations, the clear distinction between closed-source and open-source will inherently limit the scope of our body of text. (2) there is also my limited understanding of certain languages and certain hardware. (3) the social component of the study also implies that i might not have access to specific language communities (i.e. hacking and educating in non-english or non-french languages), but that would be mitigated by the fact that most resources are based on english
with this work we propose to demonstrate the thesis that aesthetics play a role in understanding code; the previous research has left many questions unanswered, and the data gathered is still insufficient.


| Installing an application |
With App Installer, you can install applications stored in your internal storage or microSD card.
During the installation, an Install blocked message may be displayed. Read the message carefully. If you want to continue with the installation, follow the onscreen instructions to allow the installation of third-party applications.


Tesla unveils its brand new Cybertruck and it looks absolutely insane
by Yoni HeislerAfter years of anticipation, Tesla today finally unveiled its all-electric pickup truck, a vehicle the company has dubbed the Cybertruck. We can get into the specs in a bit, but for starters, we have to address the obvious: Tesla’s Cybertruck looks like nothing we’ve ever seen before.
I’m not sure if that’s a good or a bad thing, but you have to give Tesla props for completely re-imagining what a pickup truck is supposed to look like. The final design essentially looks like a military vehicle out of some futuristic movie. Tesla CEO Elon Musk certainly wasn’t lying when he said the vehicle would resemble a “really futuristic cyberpunk ‘Blade Runner’ pickup truck.”
Four more photos, for good measure, can be viewed below.
Here’s a shot of the interior. Note the steering wheel design.
The look is even wilder from the back.
As far as specs are concerned, the truck will be available in three configurations. The entry-level model will boast 250 miles of range, a mid-tier model will boast 300 miles of range, and the premium model will be able to travel an impressive 500 miles on a single charge. The entry-level model has a 0-60 MPH time of 6.5 seconds and can tow upwards of 7,500 pounds. The mid-tier model has a 0-60 time of 4.5 seconds and can tow upwards of 10,000 pounds. And lastly, the top of the line Cybertruck has a 0-60 time of 2.9 seconds and can tow in excess of 14,000 pounds.
With respect to price, the three aforementioned Cybertruck models are respectively priced at $39,900, $49,900, and $69,900.
During Thursday night’s presentation, Musk said that the Cybertruck is incredibly resilient and can withstand strikes from a hammer and even a gunshot. Meanwhile, a live demonstration of the Cybertruck’s armored glass didn’t go as planned when a window was broken on stage.
“Cybertruck is built with an exterior shell made for ultimate durability and passenger protection,” Tesla boasts on its website. “Starting with a nearly impenetrable exoskeleton, every component is designed for superior strength and endurance, from Ultra-Hard 30X Cold-Rolled stainless-steel structural skin to Tesla armor glass.”
Additional specs are as follows:
- Payload: Up to 3,500 lbs
- Vault length: 6.5 feet
- Storage capacity: 100 cubic feet of exterior, lockable storage including the vault, frunk, and sail pillars.
- Suspension: 4” in either direction
- Touchscreen size: 17”
- Body: Ultra-Hard 30X Cold-Rolled stainless steel. If there was something better, we’d use it.
- Seating capacity: Up to six adults
- Charging: Can be charged at home, at Destination Charging locations, and with our network of more than 14,000 Superchargers, including on our newest V3 technology, which is helpful for long hauls and towing.
So when can you expect to see this wild design on the road? Per Musk, Tesla is anticipating a production start date sometime in 2021. Pre-orders, meanwhile, are already open over here.
As a final point of interest, Musk noted that the Cybertruck design was inspired by the famed Lotus Esprit which appeared in the James Bond movie The Spy Who Loved Me.


species models biodiversity climate SDMs change dispersal climatic distribution RCPs future Fig. metrics range sensitivity {border-style GCMs influence deviance different px;} #ffffff;} data explained loss projections uncertainty variation (Supplementary current model modelling suitable relative used using choice considering suitability effects global projected (Fig. areas uncertainties (e.g. GCM Supplementary conditions multiple nested results scenarios sources species’ total Ecol. RCP SDMs, area conservation px; single turnover variability {font-family Biodiversity Change However, calculated changes circulation dispersal’ font-size function maps metric projection quality resolution run variance ./j.-...x Clim. IPBES Nature RCPs, SDM analyses concentration considered currently double; effect ensemble grid highest pathways representative scale scenario selected species, species. temporal α-diversity km ANOVA CHELSA GCMs, Here, Interestingly, Species TSS W.T. amphibian, analyses, bird border-color border-width choices difference importance important limited mammal mean originating percentage pixel report represented result selecting solid; space sub-region time true use {font-style {font-weight ‘no (). (GCMs) (SDMs), (i.e. (see Assessment Biol. Commons Creative Data Figs. Glob. Models RCPs. SDMs. Thuiller algorithms approaches available birds, bold community complex conditions, converted courier; differ distributions diversity em; emission ensembles final followed high impact included information input means metrics. modelled particularly partitioning project provide pt;} represent represents respectively. results. scenarios. spatial threshold thresholds variables words,


About Me
I'm a backend developer based in Noida, India.
I'm experienced in providing End-to-End Software Delivery using Agile Methodologies.
I'm self-motivated, flexible, and always keen on learning new things in life.
I'm also a self-professed cook.
Tech Skills
- ASP.NET 4.5
- MVC 4
- ADO.NET
- C# 6.0
- MS SQL
- SSIS
- SSRS (Basics)
- HTML5
- JavaScript
- jQuery
Professional Experience
-
April 2016 - PresentTata Consultancy Services (TCS)
At TCS, I'm responsible for working in a collaborative environment, requirement gathering and analysis, end-to-end development, and deployment for the clients.
I'm working in the Healthcare domain (IT and Services industry) for TCS's US Clients, where we work on these tools and technologies:
C#, .NET Framework, ADO.NET, ASP.NET, Windows Communication Foundation (WCF), MVC 5, SSIS, Microsoft SQL Server 2008R2, Microsoft VS Studio, TFS and VSTS.


“Benjamin Rackstrow, a most enterprising showman in Georgian London, staged ‘The Chair of Beatification’, which involved irradiating a willing member of the public with the kind of flaming amazement that Ariel conjured on the shipwreck: ‘a Glass Crown being placed on the Head of the Person who sits in the Chair, immediately becomes filled with Aetherial Fire; and likewise a Glass Sceptre, wherein is to be seen one continued stream of Electrical Fire, of a beautiful Purple Colour’.”
Marina Warner, Phantasmagoria : Spirit Visions, Metaphors, And Media Into The Twenty-First Century (2006)


Module "pl.config"
reads configuration files into a Lua table.
Understands INI files, classic Unix config files, and simple delimited columns of values.
# test.config # Read timeout in seconds read.timeout=10 # Write timeout in seconds write.timeout=5 #acceptable ports ports = 1002,1003,1004 -- readconfig.lua require 'pl' local t = config.read 'test.config' print(pretty.write(t)) ### output ##### { ports = { 1002, 1003, 1004 }, write_timeout = 5, read_timeout = 10 }See the Guide for further discussion
Functions
| config.lines (file) | like io.lines(), but allows for lines to be continued with '\'. |
| config.read (file, cnfg) | read a configuration file into a table |
Functions
- config.lines (file)
-
like io.lines(), but allows for lines to be continued with '\'.
Parameters:
- file: a file-like object (anything where read() returns the next line) or a filename. Defaults to stardard input.
Return value:
an iterator over the lines - config.read (file, cnfg)
-
read a configuration file into a table
Parameters:
- file: either a file-like object or a string, which must be a filename
- cnfg: a configuration table
Return value:
nil,error_msg in case of an error, otherwise a table containing items


When i was small boy my father told me
never recommend a church or a woman
to anyone. And i have found it wise never to
recommend a restaurant
ether. Something
always goes wrong with the cheese souffle.
There is Something profoundly satisfying
sharing a meal, eating together,
breaking bread together is one of
oldest and one of the fundermentally unifying human experience
There is Something profoundly satisfying
sharing a meal, eating together,
breaking bread together is one of
oldest and one of the fundermentally unifying human experience
There is Something profoundly satisfying
sharing a meal, eating together,
breaking bread together is one of
oldest and one of the fundermentally unifying people adventure