Stream module containing stream utility methods.
This module provides a set of methods for interacting with
IOStream objects, including asynchronous versions of the
read
and write
methods offered by all stream objects. These
methods should be used in any place where reading from or writing
to a stream might block.
See also:
Adds the specified callback as an event listener for the named event.
Arguments
| name | [String] | Name of the event. |
| callback | [Callback<Object>] | Callback function to invoke when the event is fired. |
Applies the properties to the proxy.
Arguments
| props | [Dictionary] | A dictionary of properties to apply. |
Creates stream from a Buffer
or Blob
object.
Arguments
| params | [CreateStreamArgs] | Parameter object, for specifying the source object and mode. |
Fires a synthesized event to any registered listeners.
Arguments
| name | [String] | Name of the event. |
| event | [Dictionary] | A dictionary of keys and values to add to the Titanium.Event object sent to the listeners. |
Reads data from input stream and passes it to a handler method.
Arguments
| inputStream | [Titanium.IOStream] | Stream to pump from. |
| handler | [Callback<PumpCallbackArgs>] | Handler method that will receive data from inputStream. |
| maxChunkSize | [Number] | Maximum number of bytes to pass to handler in a single call. |
| isAsync | [Boolean] | Specifies if the pump operation should run asynchronously. |
Asynchronously reads data from an IOStream into a buffer.
Arguments
| sourceStream | [Titanium.IOStream] | Stream to read from. |
| buffer | [Titanium.Buffer] | Buffer to read into. |
| offset | [Number] | Offset to start reading stream data from, in bytes. If specified, length must be specified as well. |
| length | [Number] | Number of bytes of data to read from the stream. If specified, offset must be specified as well. |
| resultsCallback | [Callback<ReadCallbackArgs>] | Function to call with the results of the read operation. |
Reads all data from the specified IOStream.
Arguments
| sourceStream | [Titanium.IOStream] | Stream to read from. |
| buffer | [Titanium.Buffer] | Buffer to read into. If specified, resultsCallback must be specified as well. |
| resultsCallback | [Callback<ReadCallbackArgs>] | Function to call with the results of the read operation. If specified, resultsCallback must be specified as well. |
Removes the specified callback as an event listener for the named event.
Arguments
| name | [String] | Name of the event. |
| callback | [Callback<Object>] | Callback function to remove. Must be the same function passed to addEventListener. |
Asynchronously writes data from a buffer to an IOStream.
Arguments
| outputStream | [Titanium.IOStream] | Stream to write to. |
| buffer | [Titanium.Buffer] | Buffer to write from. |
| offset | [Number] | Offset to start writing buffer data from. If specified, length must be specified as well. |
| length | [Number] | Bytes of data to write. If specified, offset must be specified as well. |
| resultsCallback | [Callback<WriteCallbackArgs>] | Function to call with the results of the write operation. |
Writes all data from an input stream to an output stream.
Arguments
| inputStream | [Titanium.IOStream] | Stream to read from. |
| outputStream | [Titanium.IOStream] | Stream to write to. |
| maxChunkSize | [Number] | Maximum number of bytes to copy from inputStream to outputStream in a single operation. |
| resultsCallback | [Callback<WriteStreamCallbackArgs>] | Function to call with the results of the writeStream operation. |


Miami, Drake meet in Gulf Coast Showcase
by EndPlayESTERO, Fla. - Drake (4-1) vs. Miami (3-1)
Gulf Coast Showcase , Hertz Arena, Estero, Florida; Monday, 1:30 p.m. EST
BOTTOM LINE: Drake and Miami will meet in the Gulf Coast Showcase. Miami earned an 80-45 win over Central State on Wednesday, while Drake won 74-58 against Lehigh on Thursday.
LEADING THE WAY: Roman Penn and Liam Robbins have led the Bulldogs. Penn is averaging 11.4 points, four rebounds and 7.4 assists while Robbins is putting up 13 points, five rebounds and three blocks per game. The RedHawks have been led by sophomores Nike Sibande and Dalonte Brown. Sibande has averaged 16.8 points and 5.5 rebounds while Brown has put up 14.5 points and nine rebounds per game.
CREATING OFFENSE: Penn has either made or assisted on 42 percent of all Drake field goals over the last three games. The sophomore guard has 16 field goals and 24 assists in those games.
ASSIST RATIOS: The RedHawks have recently used assists to create baskets more often than the Bulldogs. Miami has an assist on 56 of 89 field goals (62.9 percent) across its past three games while Drake has assists on 50 of 95 field goals (52.6 percent) during its past three games.
DID YOU KNOW: Miami has made 10.5 3-pointers per game this season, which is second-best among MAC teams.
___
For more AP college basketball coverage: https://apnews.com/Collegebasketball and http://twitter.com/AP_Top25
___
This was generated by Automated Insights, http://www.automatedinsights.com/ap, using data from STATS LLC, https://www.stats.com


Pole Goals 2021
What pole trick should you master this year?
Choose Your Level:
Not sure what level you are?
Beginner
I’m new to pole and am still learning or mastering basic spins, tricks, and climbs. I cannot invert.
Intermediate
I've been poling for a while and can sit on the pole, invert, and perform a variety of spins and tricks.
Advanced
I'm a confident and experienced poler who can perform aerial inverts and tricks with two or fewer points of contact.
Extreme
I'm a very confident, expert poler who can perform a variety of aerial tricks and tricks with two or fewer points of contact.
Start working toward your goal now by signing up for a class at our Norwalk, CT studio!
Already mastered this trick?


BrowseService
The following resources are applicable:
- /browseService/artifactAvailable/{g}/{a}/{v}
- /browseService/artifactAvailable/{g}/{a}/{v}/{c}
- /browseService/artifactContentEntries/{g}/{a}/{v}
- /browseService/artifactContentText/{g}/{a}/{v}
- /browseService/artifactDownloadInfos/{g}/{a}/{v}
- /browseService/artifacts/{r}
- /browseService/artifactsByMetadata/{key}/{value}
- /browseService/artifactsByProjectVersionMetadata/{key}/{value}
- /browseService/artifactsByProperty/{key}/{value}
- /browseService/browseGroupId/{groupId}
- /browseService/dependees/{g}/{a}/{v}
- /browseService/importMetadata
- /browseService/metadata/{g}/{a}/{v}/{key}
- /browseService/metadata/{g}/{a}/{v}/{key}/{value}
- /browseService/metadatas/{g}/{a}/{v}
- /browseService/projectVersionMetadata/{g}/{a}
- /browseService/projectVersionMetadata/{g}/{a}/{v}
- /browseService/rootGroups
- /browseService/searchArtifacts/{key}/{text}
- /browseService/searchArtifacts/{text}
- /browseService/treeEntries/{g}/{a}/{v}
- /browseService/userRepositories
- /browseService/versionsList/{g}/{a}
/browseService/artifactAvailable/{g}/{a}/{v}
Mount Point: /restServices/browseService/artifactAvailable/{g}/{a}/{v}
GET
Available Since: 1.4-M3
verify if an artifact is available locally if not download from proxies will be try
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifactAvailable/{g}/{a}/{v}/{c}
Mount Point: /restServices/browseService/artifactAvailable/{g}/{a}/{v}/{c}
GET
Available Since: 1.4-M4
verify if an artifact is available locally if not download from proxies will be try
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| c | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifactContentEntries/{g}/{a}/{v}
Mount Point: /restServices/browseService/artifactContentEntries/{g}/{a}/{v}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| c | (no documentation provided) | query | |
| t | (no documentation provided) | query | |
| p | (no documentation provided) | query | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifactContentText/{g}/{a}/{v}
Mount Point: /restServices/browseService/artifactContentText/{g}/{a}/{v}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
if path is empty content of the file is returned (for pom view)
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| c | (no documentation provided) | query | |
| t | (no documentation provided) | query | |
| p | (no documentation provided) | query | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | artifactContent |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifactDownloadInfos/{g}/{a}/{v}
Mount Point: /restServices/browseService/artifactDownloadInfos/{g}/{a}/{v}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifacts/{r}
Mount Point: /restServices/browseService/artifacts/{r}
GET
Available Since: 1.4-M3
return List of all artifacts from this repository
Parameters
| name | description | type | default |
|---|---|---|---|
| r | (no documentation provided) | path |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifactsByMetadata/{key}/{value}
Mount Point: /restServices/browseService/artifactsByMetadata/{key}/{value}
GET
Available Since: 2.2
Return List of artifacts from this repository with artifact metadata key matching value. If repository is not provided the search runs in all repositories.
Parameters
| name | description | type | default |
|---|---|---|---|
| key | (no documentation provided) | path | |
| value | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifactsByProjectVersionMetadata/{key}/{value}
Mount Point: /restServices/browseService/artifactsByProjectVersionMetadata/{key}/{value}
GET
Available Since: 2.2
Return List of artifacts from this repository with project version level metadata key matching value. If repository is not provided the search runs in all repositories.
Parameters
| name | description | type | default |
|---|---|---|---|
| key | (no documentation provided) | path | |
| value | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/artifactsByProperty/{key}/{value}
Mount Point: /restServices/browseService/artifactsByProperty/{key}/{value}
GET
Available Since: 2.2
Return List of artifacts from this repository with property key matching value. If repository is not provided the search runs in all repositories.
Parameters
| name | description | type | default |
|---|---|---|---|
| key | (no documentation provided) | path | |
| value | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/browseGroupId/{groupId}
Mount Point: /restServices/browseService/browseGroupId/{groupId}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| groupId | groupId to browse | path | |
| repositoryId | optionnal (repository to browse if null all available user repositories are used) | query |
Response Body
| element: | browseResult |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/dependees/{g}/{a}/{v}
Mount Point: /restServices/browseService/dependees/{g}/{a}/{v}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
List of artifacts using the artifact passed in parameter.
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/importMetadata
Mount Point: /restServices/browseService/importMetadata
Available Since: 1.4-M3
POST
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| repository | (no documentation provided) | query |
Request Body
| element: | metadataAddRequest |
| media types: | */* application/xml |
(no documentation provided)
Response Body
| element: | (custom) |
| media types: | */* application/xml |
(no documentation provided)
/browseService/metadata/{g}/{a}/{v}/{key}
Mount Point: /restServices/browseService/metadata/{g}/{a}/{v}/{key}
Available Since: 1.4-M3
DELETE
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| key | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/metadata/{g}/{a}/{v}/{key}/{value}
Mount Point: /restServices/browseService/metadata/{g}/{a}/{v}/{key}/{value}
Available Since: 1.4-M3
PUT
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| key | (no documentation provided) | path | |
| value | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/metadatas/{g}/{a}/{v}
Mount Point: /restServices/browseService/metadatas/{g}/{a}/{v}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/projectVersionMetadata/{g}/{a}
Mount Point: /restServices/browseService/projectVersionMetadata/{g}/{a}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | projectVersionMetadata |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/projectVersionMetadata/{g}/{a}/{v}
Mount Point: /restServices/browseService/projectVersionMetadata/{g}/{a}/{v}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | projectVersionMetadata |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/rootGroups
Mount Point: /restServices/browseService/rootGroups
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| repositoryId | (no documentation provided) | query |
Response Body
| element: | browseResult |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/searchArtifacts/{key}/{text}
Mount Point: /restServices/browseService/searchArtifacts/{key}/{text}
GET
Available Since: 2.2
Search artifacts with the property specified by key matching text. If repository is not provided the search runs in all repositories. If exact is true only the artifacts whose property match exactly are returned.
Parameters
| name | description | type | default |
|---|---|---|---|
| key | (no documentation provided) | path | |
| text | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query | |
| exact | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/searchArtifacts/{text}
Mount Point: /restServices/browseService/searchArtifacts/{text}
GET
Available Since: 2.2
Search artifacts with any property matching text. If repository is not provided the search runs in all repositories. If exact is true only the artifacts whose property match exactly are returned.
Parameters
| name | description | type | default |
|---|---|---|---|
| text | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query | |
| exact | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/treeEntries/{g}/{a}/{v}
Mount Point: /restServices/browseService/treeEntries/{g}/{a}/{v}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
return the dependency Tree for an artifacts the List result has only one entry
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| v | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
(no documentation provided)
/browseService/userRepositories
Mount Point: /restServices/browseService/userRepositories
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Response Body
| element: | (custom) |
| media types: | application/xml application/json |
List of managed repositories current user can read
/browseService/versionsList/{g}/{a}
Mount Point: /restServices/browseService/versionsList/{g}/{a}
Available Since: 1.4-M3
GET
Available Since: 1.4-M3
Parameters
| name | description | type | default |
|---|---|---|---|
| g | (no documentation provided) | path | |
| a | (no documentation provided) | path | |
| repositoryId | (no documentation provided) | query |
Response Body
| element: | versionsList |
| media types: | application/xml application/json |
(no documentation provided)


Go to the source code of this file.
Defines | |
| #define | _OSSL_OPENSSL_MISSING_H_ |
| #define | PEM_read_bio_DSAPublicKey(bp, x, cb, u) |
| #define | PEM_write_bio_DSAPublicKey(bp, x) |
| #define | DSAPrivateKey_dup(dsa) |
| #define | DSAPublicKey_dup(dsa) |
| #define | X509_REVOKED_dup(rev) |
| #define | PKCS7_SIGNER_INFO_dup(si) |
| #define | PKCS7_RECIP_INFO_dup(ri) |
| #define | EVP_DigestInit_ex(ctx, md, engine) EVP_DigestInit((ctx), (md)) |
| #define | EVP_DigestFinal_ex(ctx, buf, len) EVP_DigestFinal((ctx), (buf), (len)) |
| #define | EVP_CipherInit_ex(ctx, type, impl, key, iv, enc) EVP_CipherInit((ctx), (type), (key), (iv), (enc)) |
| #define | EVP_CipherFinal_ex(ctx, outm, outl) EVP_CipherFinal((ctx), (outm), (outl)) |
| #define | EVP_CIPHER_name(e) OBJ_nid2sn(EVP_CIPHER_nid(e)) |
| #define | EVP_MD_name(e) OBJ_nid2sn(EVP_MD_type(e)) |
| #define | HMAC_Init_ex(ctx, key, len, digest, engine) HMAC_Init((ctx), (key), (len), (digest)) |
| #define | PKCS7_is_detached(p7) (PKCS7_type_is_signed(p7) && PKCS7_get_detached(p7)) |
| #define | PKCS7_type_is_encrypted(a) (OBJ_obj2nid((a)->type) == NID_pkcs7_encrypted) |
| #define | OPENSSL_cleanse(p, l) memset((p), 0, (l)) |
Typedefs | |
| typedef char * | d2i_of_void () |
| typedef int | i2d_of_void () |
Functions | |
| void | HMAC_CTX_init (HMAC_CTX *ctx) |
| void | HMAC_CTX_copy (HMAC_CTX *out, HMAC_CTX *in) |
| void | HMAC_CTX_cleanup (HMAC_CTX *ctx) |
| EVP_MD_CTX * | EVP_MD_CTX_create (void) |
| void | EVP_MD_CTX_init (EVP_MD_CTX *ctx) |
| int | EVP_MD_CTX_cleanup (EVP_MD_CTX *ctx) |
| void | EVP_MD_CTX_destroy (EVP_MD_CTX *ctx) |
| int | EVP_CIPHER_CTX_copy (EVP_CIPHER_CTX *out, EVP_CIPHER_CTX *in) |
| void * | X509_STORE_get_ex_data (X509_STORE *str, int idx) |
| int | X509_STORE_set_ex_data (X509_STORE *str, int idx, void *data) |
| int | X509_CRL_set_version (X509_CRL *x, long version) |
| int | X509_CRL_set_issuer_name (X509_CRL *x, X509_NAME *name) |
| int | X509_CRL_sort (X509_CRL *c) |
| int | X509_CRL_add0_revoked (X509_CRL *crl, X509_REVOKED *rev) |
| int | BN_mod_sqr (BIGNUM *r, const BIGNUM *a, const BIGNUM *m, BN_CTX *ctx) |
| int | BN_mod_add (BIGNUM *r, const BIGNUM *a, const BIGNUM *b, const BIGNUM *m, BN_CTX *ctx) |
| int | BN_mod_sub (BIGNUM *r, const BIGNUM *a, const BIGNUM *b, const BIGNUM *m, BN_CTX *ctx) |
| int | BN_rand_range (BIGNUM *r, BIGNUM *range) |
| int | BN_pseudo_rand_range (BIGNUM *r, BIGNUM *range) |
| char * | CONF_get1_default_config_file (void) |
| int | PEM_def_callback (char *buf, int num, int w, void *key) |
| int | ASN1_put_eoc (unsigned char **pp) |
| #define _OSSL_OPENSSL_MISSING_H_ |
Definition at line 12 of file openssl_missing.h.
| #define DSAPrivateKey_dup | ( | dsa | ) |
(DSA *)ASN1_dup((i2d_of_void *)i2d_DSAPrivateKey, \ (d2i_of_void *)d2i_DSAPrivateKey,(char *)(dsa))
Definition at line 42 of file openssl_missing.h.
| #define DSAPublicKey_dup | ( | dsa | ) |
(DSA *)ASN1_dup((i2d_of_void *)i2d_DSAPublicKey, \ (d2i_of_void *)d2i_DSAPublicKey,(char *)(dsa))
Definition at line 47 of file openssl_missing.h.
Referenced by ossl_dsa_to_public_key().
| #define EVP_CIPHER_name | ( | e | ) | OBJ_nid2sn(EVP_CIPHER_nid(e)) |
Definition at line 113 of file openssl_missing.h.
Referenced by ossl_cipher_name().
| #define EVP_CipherFinal_ex | ( | ctx, | |||
| outm, | |||||
| outl | ) | EVP_CipherFinal((ctx), (outm), (outl)) |
Definition at line 109 of file openssl_missing.h.
Referenced by ossl_cipher_final().
| #define EVP_CipherInit_ex | ( | ctx, | |||
| type, | |||||
| impl, | |||||
| key, | |||||
| iv, | |||||
| enc | ) | EVP_CipherInit((ctx), (type), (key), (iv), (enc)) |
Definition at line 106 of file openssl_missing.h.
Referenced by ossl_cipher_init(), ossl_cipher_initialize(), ossl_cipher_new(), ossl_cipher_pkcs5_keyivgen(), ossl_cipher_reset(), ossl_cipher_set_iv(), and ossl_cipher_set_key().
Definition at line 102 of file openssl_missing.h.
Referenced by ossl_digest_finish().
| #define EVP_DigestInit_ex | ( | ctx, | |||
| md, | |||||
| engine | ) | EVP_DigestInit((ctx), (md)) |
Definition at line 99 of file openssl_missing.h.
Referenced by ossl_digest_initialize(), ossl_digest_new(), and ossl_digest_reset().
| #define EVP_MD_name | ( | e | ) | OBJ_nid2sn(EVP_MD_type(e)) |
Definition at line 117 of file openssl_missing.h.
Referenced by ossl_digest_name().
Definition at line 121 of file openssl_missing.h.
| #define OPENSSL_cleanse | ( | p, | |||
| l | ) | memset((p), 0, (l)) |
Definition at line 133 of file openssl_missing.h.
Referenced by ossl_cipher_pkcs5_keyivgen().
| #define PEM_read_bio_DSAPublicKey | ( | bp, | |||
| x, | |||||
| cb, | |||||
| u | ) |
(DSA *)PEM_ASN1_read_bio( \ (d2i_of_void *)d2i_DSAPublicKey,PEM_STRING_DSA_PUBLIC,(bp),(void **)(x),(cb),(u))
Definition at line 30 of file openssl_missing.h.
Referenced by ossl_dsa_initialize().
| #define PEM_write_bio_DSAPublicKey | ( | bp, | |||
| x | ) |
PEM_ASN1_write_bio((i2d_of_void *)i2d_DSAPublicKey,\ PEM_STRING_DSA_PUBLIC,\ (bp),(char *)(x), NULL, NULL, 0, NULL, NULL)
Definition at line 35 of file openssl_missing.h.
| #define PKCS7_is_detached | ( | p7 | ) | (PKCS7_type_is_signed(p7) && PKCS7_get_detached(p7)) |
Definition at line 125 of file openssl_missing.h.
Referenced by ossl_pkcs7_detached_p(), and ossl_pkcs7_s_write_smime().
| #define PKCS7_RECIP_INFO_dup | ( | ri | ) |
(PKCS7_RECIP_INFO *)ASN1_dup((i2d_of_void *)i2d_PKCS7_RECIP_INFO, \ (d2i_of_void *)d2i_PKCS7_RECIP_INFO, (char *)(ri))
Definition at line 62 of file openssl_missing.h.
Referenced by DupPKCS7RecipientPtr(), and ossl_pkcs7ri_new().
| #define PKCS7_SIGNER_INFO_dup | ( | si | ) |
(PKCS7_SIGNER_INFO *)ASN1_dup((i2d_of_void *)i2d_PKCS7_SIGNER_INFO, \ (d2i_of_void *)d2i_PKCS7_SIGNER_INFO, (char *)(si))
Definition at line 57 of file openssl_missing.h.
Referenced by DupPKCS7SignerPtr(), and ossl_pkcs7si_new().
| #define PKCS7_type_is_encrypted | ( | a | ) | (OBJ_obj2nid((a)->type) == NID_pkcs7_encrypted) |
Definition at line 129 of file openssl_missing.h.
Referenced by ossl_pkcs7_get_type().
| #define X509_REVOKED_dup | ( | rev | ) |
(X509_REVOKED *)ASN1_dup((i2d_of_void *)i2d_X509_REVOKED, \ (d2i_of_void *)d2i_X509_REVOKED, (char *)(rev))
Definition at line 52 of file openssl_missing.h.
Referenced by DupX509RevokedPtr(), and ossl_x509revoked_new().
| typedef char* d2i_of_void() |
Definition at line 19 of file openssl_missing.h.
| typedef int i2d_of_void() |
Definition at line 22 of file openssl_missing.h.
| int ASN1_put_eoc | ( | unsigned char ** | pp | ) |
Definition at line 347 of file openssl_missing.c.
Referenced by ossl_asn1cons_to_der().
| int BN_mod_add | ( | BIGNUM * | r, | |
| const BIGNUM * | a, | |||
| const BIGNUM * | b, | |||
| const BIGNUM * | m, | |||
| BN_CTX * | ctx | |||
| ) |
Definition at line 219 of file openssl_missing.c.
References BN_nnmod().
| int BN_mod_sqr | ( | BIGNUM * | r, | |
| const BIGNUM * | a, | |||
| const BIGNUM * | m, | |||
| BN_CTX * | ctx | |||
| ) |
Definition at line 201 of file openssl_missing.c.
| int BN_mod_sub | ( | BIGNUM * | r, | |
| const BIGNUM * | a, | |||
| const BIGNUM * | b, | |||
| const BIGNUM * | m, | |||
| BN_CTX * | ctx | |||
| ) |
Definition at line 228 of file openssl_missing.c.
References BN_nnmod().
| int BN_pseudo_rand_range | ( | BIGNUM * | r, | |
| BIGNUM * | range | |||
| ) |
Definition at line 277 of file openssl_missing.c.
References bn_rand_range().
| int BN_rand_range | ( | BIGNUM * | r, | |
| BIGNUM * | range | |||
| ) |
Definition at line 269 of file openssl_missing.c.
References bn_rand_range().
| char* CONF_get1_default_config_file | ( | void | ) |
Definition at line 286 of file openssl_missing.c.
References getenv(), len, NULL, OPENSSL_CONF, and strlen().
Referenced by Init_ossl_config().
| int EVP_CIPHER_CTX_copy | ( | EVP_CIPHER_CTX * | out, | |
| EVP_CIPHER_CTX * | in | |||
| ) |
Definition at line 121 of file openssl_missing.c.
Referenced by ossl_cipher_copy().
| int EVP_MD_CTX_cleanup | ( | EVP_MD_CTX * | ctx | ) |
Definition at line 67 of file openssl_missing.c.
Referenced by EVP_MD_CTX_destroy(), and HMAC_CTX_cleanup().
| EVP_MD_CTX* EVP_MD_CTX_create | ( | void | ) |
Definition at line 54 of file openssl_missing.c.
References NULL.
Referenced by ossl_digest_alloc().
| void EVP_MD_CTX_destroy | ( | EVP_MD_CTX * | ctx | ) |
Definition at line 78 of file openssl_missing.c.
References EVP_MD_CTX_cleanup().
Referenced by ossl_digest_alloc().
| void EVP_MD_CTX_init | ( | EVP_MD_CTX * | ctx | ) |
Definition at line 87 of file openssl_missing.c.
Referenced by HMAC_CTX_init().
| void HMAC_CTX_cleanup | ( | HMAC_CTX * | ctx | ) |
Definition at line 105 of file openssl_missing.c.
References EVP_MD_CTX_cleanup().
Referenced by hmac_final(), and ossl_hmac_free().
| void HMAC_CTX_copy | ( | HMAC_CTX * | out, | |
| HMAC_CTX * | in | |||
| ) |
Definition at line 26 of file openssl_missing.c.
Referenced by hmac_final(), and ossl_hmac_copy().
| void HMAC_CTX_init | ( | HMAC_CTX * | ctx | ) |
Definition at line 95 of file openssl_missing.c.
References EVP_MD_CTX_init().
Referenced by ossl_hmac_alloc().
| int PEM_def_callback | ( | char * | buf, | |
| int | num, | |||
| int | w, | |||
| void * | key | |||
| ) |
Definition at line 313 of file openssl_missing.c.
References NULL, OSSL_PASS_MIN_LENGTH, and strlen().
Referenced by ossl_pem_passwd_cb().
| int X509_CRL_add0_revoked | ( | X509_CRL * | crl, | |
| X509_REVOKED * | rev | |||
| ) |
Definition at line 186 of file openssl_missing.c.
References inf(), and OSSL_X509_REVOKED_cmp().
Referenced by ossl_x509crl_add_revoked(), and ossl_x509crl_set_revoked().
| int X509_CRL_set_issuer_name | ( | X509_CRL * | x, | |
| X509_NAME * | name | |||
| ) |
Definition at line 152 of file openssl_missing.c.
References NULL.
Referenced by ossl_x509crl_set_issuer().
| int X509_CRL_set_version | ( | X509_CRL * | x, | |
| long | version | |||
| ) |
Definition at line 139 of file openssl_missing.c.
References NULL.
Referenced by ossl_x509crl_set_version().
| int X509_CRL_sort | ( | X509_CRL * | c | ) |
Definition at line 161 of file openssl_missing.c.
Referenced by ossl_x509crl_add_revoked(), and ossl_x509crl_set_revoked().
| void* X509_STORE_get_ex_data | ( | X509_STORE * | str, | |
| int | idx | |||
| ) |
Definition at line 46 of file openssl_missing.c.
Referenced by ossl_verify_cb().
| int X509_STORE_set_ex_data | ( | X509_STORE * | str, | |
| int | idx, | |||
| void * | data | |||
| ) |
Definition at line 39 of file openssl_missing.c.
Referenced by ossl_x509store_set_vfy_cb().


Apple Announces Extended Holiday Return Policy
by iClarifiedApple has announced its Extended Holiday Return Policy for this year. As usual, the company is giving customers a bit more time to return items that were purchased as holiday gifts.
Holiday Return Policy
Items purchased at the Apple Online Store that are received between November 15, 2019 and December 25, 2019, may be returned through January 8, 2020. Please note that all other terms and conditions provided in the Apple Online Store Sales and Refunds Policy are still applicable with respect to such items purchased. All purchases made after December 25, 2019, are subject to the Standard Return Policy.
You can read Apple's full Returns & Refunds Policy at the link below.
Read More


--- layout: doc title: Documentation ---
Proof General inherits support for displaying Unicode (and any other) fonts from the underlying Emacs program. If you are lucky, your system will be able to use or synthesise a font that provides a rich set of mathematical symbols. To store symbols directly in files you need to use a particular coding, for example UTF-8. Newer Emacs versions can handle a multitude of different coding systems and will try to automatically detect an appropriate one; consult the Emacs documentation for more details. Of course, the prover that you are using will need to understand the same encodings and symbol meanings.
Alternatively, you can use the Unicode Tokens mode provided in Proof General to display mathematical symbols in place of sequences of other characters (usually plain ASCII). This can provide better compatibility, portability, and flexibility. Even if you use real Unicode characters as prover input, the Unicode Tokens mode can provide some helpful facilities for input shorthands and giving special layout.
The Maths Menu minor mode (adapted from a menu by Dave Love) simply
adds a menu Maths
to the main menubar for inserting common
mathematical symbols. You can enable or disable it via the menu
Proof-General -> Quick Options -> Minor Modes -> Unicode Maths Menu |
(proof-maths-menu-toggle
). Whether or not the symbols display
well the menus depends on the font used to display the menus (which
depends on the Emacs version, toolkit and platform). Ordinarily, the
symbols inserted into the text will be Unicode characters which will be
saved in the file using the encoding selected by standard Emacs
mechanisms.
The Unicode Tokens minor mode has been written specially for Proof General (with thanks to Stefan Monnier for providing inspiration and a starting point). It supports the display of symbols when the underlying text of the file and buffer actually contains something else, typically, plain ASCII text. It provides backward compatibility with the older X-Symbol mode.
Unicode Tokens can be enabled or disabled using the menu:
Proof-General -> Quick Options -> Display -> Unicode Tokens |
The mode to allows ASCII tokens (i.e., sequences of plain ASCII characters) to be displayed as Unicode character compositions, perhaps with additional text properties. The additional text properties allow the use of tokens to cause font changes (bold, italic), text size changes, and sub-script/super-script.
For example, the ASCII sequences /\
or \<And>
could be
displayed as a conjunction symbol.
The sequence x __ y
might be written to display y
as subscript. This allows a file to be stored in perfectly portable plain ASCII
encoding, but be displayed and edited with real symbols and
appealing layout. Of course, the proof assistant needs to understand
the underlying tokens in each case.
Technically, the mechanism is based on Emacs Font Lock facility, using
the composition
text property to display ASCII character sequence
tokens as something else. This means that the underlying buffer text is
not altered. This is a major advantage over the older X-Symbol (and
the experimental version of Unicode Tokens in PG 3.7.1), which had the
annoying risk of saving your buffer text in a corrupted format. This
can never happen with the new mode.
When the Unicode Tokens mode is enabled, Maths Menu is automatically modified to insert tokenised versions of the Unicode characters (whenever a reverse mapping can be found). This means that you can still use the Maths Menu to conveniently input symbols. You can easily add custom key bindings for particular symbols you need to enter often (see section Adding your own keybindings for examples).
The Unicode Tokens mode also allows short-cut sequences of ordinary characters to quickly type tokens (similarly to the facility provided by X-Symbol). These, along with the token settings themselves, are configured on a per-prover basis.
To edit the strings used to display tokens, or the collection of
short-cuts, you can edit the
file PA-unicode-tokens.el
, or customize the main
variables it contains, for example PA-token-name-alist
and
PA-shortcut-alist
.
E.g., for Isabelle
M-x customize-variable isar-token-name-alist RET |
provides an interface to the tokens, and
M-x customize-variable isar-shortcut-alist |
an interface to the shortcuts.
Where possible, it is better to use the more fine grained way is available to do this, which edits the separate tables which are combine to form the big list of tokens. This is available via the menus, e.g., in Isabelle, use
Tokens -> Customize -> Extended Symbols |
to customize the symbols used for the “extended” (non standard) symbol list.
The Unicode Tokens mode supports both symbol tokens used to display
character sequences in different ways and control tokens used to
control the layout of the text in various ways, such as superscript,
subscript, large, small, bold, italic, etc. (The size and position
layout is managed using Emacs’s display
text property)
As well as displaying token sequences as special symbols, symbol tokens
themselves can define layout options as well; for example you might
define a token \<hugeOplus>
to display a large circled-plus
glyph. If you try the customization mentioned in the section above you
will see the options available when defining symbols.
These options are fixed layout schemes which also make layout tokens
easy to configure for provers. The layout possibilities include the
ones shown in the table below. There are two ways of configuring
control tokens for layout: character controls and region
controls. The character controls apply to the next “character”,
although this is a prover-specific notion and might actually mean the
next word or identifier. An example might be writing BOLDCHAR x
to make a bold x. Similarly the region controls apply to a
delineated region of text, for example, writing BEGINBOLD this is
bold ENDBOLD
could cause the enclosed text this is bold to be
displayed in a bold font.
The control tokens that have been configured populate the Tokens menu, so, for example, you may be able to select a region of text and then use the menu item:
Tokens -> Format Region -> Bold |
to cause the bold region tokens to be inserted around the selected text, which should cause the buffer presentation to show the text in a bold format (hiding the tokens).
Here is the table of layout controls available. What you actually can use will depend on the configuration for the underlying prover.
sub
lower the text (subscript)
sup
raise the text (superscript)
bold
make the text be in the bold weight of the current font
italic
make the text be in the italic variant of the current font
big
make the text be in a bigger size of the current font
small
make the text be in a smaller size of the current font
underline
underline the text
overline
overline the text
script
display the text in a “script” font
frakt
display the text in a “fraktur” font
serif
display the text in a serif font
sans
display the text in a sans serif font
keyword
display the text in the keyword face (font-lock-keyword-face
)
function
display the text in the function name face (font-lock-function-name-face
)
type
display the text in the type name face (font-lock-type-face
)
preprocessor
display the text in the preprocessor face (font-lock-preprocessor-face
)
doc
display the text in the documentation face (font-lock-doc-face
)
builtin
display the text in the builtin face (font-lock-builtin-face
)
Notice that the fonts can be set conveniently by the menu commands
Tokens -> Set Fonts -> Script |
etc. See section Selecting suitable fonts, for more.
The symbols used to select the various font-lock faces (see M-x
list-faces-display
to show them) allow you to define custom colouring
of text for proof assistant input and output, exploiting rich underlying
syntax mechanisms of the prover.
Serif (roman) font face.
Sans serif font face.
Fraktur font face.
Script font face.
If you want to share text between applications (e.g., email some text from an Isabelle theory file which heavily uses symbols), it is useful to convert to and from Unicode with cut-and-paste operations. The default buffer cut and paste functions will copy the underlying text, which contains the tokens (ASCII format). To copy and convert or paste then convert back, use these commands:
Tokens -> Copy as unicode Tokens -> Paste from unicode |
Both of these are necessarily approximate. The buffer presentation may use additional controls (for super/subscript layout or bold fonts, etc), which cannot be converted. Pasting relies on being able to identify a unique token mapped from a single Unicode character; the token table may not include such an entry, or may be ambiguous.
Copy presentation of region between beg and end.
This is an approximation; it makes assumptions about the behaviour
of symbol compositions, and will lose layout information.
Paste text from clipboard, converting Unicode to tokens where possible.
If you are using a mixture of “real” Unicode and tokens like this
you may want to be careful to check the buffer contents: the command
unicode-tokens-highlight-unicode
helps you to manage this.
It
is available on the Tokens menu as
Tokens -> Highlight Real Unicode Chars |
Alternative ways to check are to toggle the display of tokens using
Tokens -> Reveal Symbol Tokens |
(the similar entry for Control Tokens
displays tokens being used
to control layout). Or simply toggle the tokens mode, which will leave
the true Unicode tokens untouched.
Non-nil to highlight Unicode characters.
Two commands (both on the Tokens menu) allow you to see the tokens and shortcuts available:
Tokens -> List Tokens Tokens -> List Shortcuts |
Additionally, you can view the complete Unicode character set available in the default Emacs font, with
Tokens -> List Unicode Characters |
(this uses a list adapted from Norman Walsh’s unichars.el
).
Note that the Unicode Tokens modes displays symbols defined by symbol tokens in a special font.
Show a buffer of all tokens.
Show a buffer of all the shortcuts available.
Insert each Unicode character into a buffer.
Lets you see which characters are available for literal display
in your Emacs font.
The precise set of symbol glyphs that are available to you will depend in complicated ways on your operating system, Emacs version, configuration options used when Emacs was compiled, installed font sets, and (even) command line options used to start Emacs. So it is hard to give comprehensive and accurate advice in this manual. In general, things work much better with Emacs 23 than earlier versions.
To improve flexibility, Unicode Tokens mode allows you to select another font to display symbols from the default font that is used to display text in the buffer. This is the font that is configured by the menu
Tokens -> Set Fonts -> Symbol |
its customization name is unicode-tokens-symbol-font-face
, but
notice that only the font family aspect of the face is used. Similarly,
other fonts can be configured for controling different font families
(script, fraktur, etc).
For symbols, good results are possible by using a proportional font for
displaying symbols that has many symbol glyphs, for example the main font
StixGeneral font from the Stix Fonts project
(http://www.stixfonts.org/). At the time of writing you can
obtain a beta version of these fonts in TTF format from
http://olegueret.googlepages.com/stixfonts-ttf. On recent Linux
distributions and with an Emacs 23 build that uses Xft, simply copy
these ttf
files into the .fonts
directory inside your home
directory to make them available.
Another font I like is DejaVu Sans Mono. It covers all of the standard Isabelle symbols. Some of the symbols are currently not perfect; however this font is an open source effort so users can contribute or suggest improvements. See http://dejavu-fonts.org.
If you are stuck with Emacs 22, you need to use the fontset mechanism which configures sets of fonts to use for display. The default font sets may not include enough symbols (typical symptom: symbols display as empty boxes). To address this, the menu command
Tokens -> Set Fonts -> Make Fontsets |
constructs a number of fontsets at particular point sizes, based on
several widely available fonts. See pg-fontsets.el
for the code.
After running this command, you can select from additional fontsets from
the menus for changing fonts.
For further suggestions, please search (and contribute!) to the Proof General wiki at http://proofgeneral.inf.ed.ac.uk/wiki.
The default font used for symbols. Only :family and :slant attributes are used.
Not documented.
This document was generated on April 14, 2023 using texi2html 1.82.


WNV feeding Nile human Cx. humans West mosquitoes pipiens virus North birds {border-style mosquito Figure px;} #ffffff;} Culex epidemics American infection abundance transmission probability shifts America mammals risk shift using California Med blood hosts intensity number United avian cases data increased summer Colorado robins tarsalis vector Dis Infect New early infections px; zoonotic {font-family Feeding behavior compared factors font-size humans. late meals site Accessed DNA Hyg National Old Trop Virus York competent dispersal dominant double; estimated feedings northeast occur result species strain January Maryland PCR September States, World birds, border-color border-width collab: encephalitis explanation fed fraction greater identified pathogens period results robin slope solid; vector-borne {font-style {font-weight â€" (Â± .), .). AMK, C., Disease Finally, Julian LDK, Park, Shifts St. States amplification appear approximately bold caused courier; decline declined disease effects em; engorged enzootic epidemic high humans, important increase infectious later north-central patterns peak population predicted prevalence primarily product pt;} robins, sites vectors


Given an unsorted integer array, find the smallest missing positive integer.
Example 1:
Input: [1,2,0]
Output: 3
Example 2:
Input: [3,4,-1,1]
Output: 2
Example 3:
Input: [7,8,9,11,12]
Output: 1
Note:
Your algorithm should run in O(n) time and uses constant extra space.
The last requirement is why this problem is marked “hard”. Though the solution feels like cheating: it modifies the array to mark numbers.
So the algorithm still requires O(n) space but O(1) extra space.
The core idea of the solution is, if the length of the array is n, then the smallest missing positive integer must be within [1, n+1].
Consider an edge-case scenario where the array is
[1,2,...,n]
. The smallest missing positive integer is
n+1
.
Now if one of these integers is missing in the array, that integer is the smallest missing positive integer.
If more than one are missing, pick the smallest.
So here we reuse the array and keep trying to put integer
k
into the slot indexed k-1
(via swapping).
/**
* @param {number[]} nums
* @return {number}
*/
var firstMissingPositive = function(nums) {
const n = nums.length
for (let i = 1; i < n; i++) {
while (nums[i] <= n && nums[i] !== nums[nums[i] - 1]) {
const t = nums[i]
nums[i] = nums[t - 1]
nums[t - 1] = t
}
}
for (let i = 0; i < n; i++) {
if (nums[i] !== i + 1) {
return i + 1
}
}
return n + 1
};
Template generated via Leetmark.


Version 3.0 is not backward compatible to previous versions. A conversion script is provided to transform models and libraries of previous versions to the new version. Therefore, conversion should be automatic.
The following changes are present for the whole library:
parameter Modelica.SIunits.Resistance R=1;Physical parameters, such as a resistance, mass, gear ratio, do not have a meaningful default and in nearly all cases, the user of the corresponding component has to provide values for such parameters. If the user forgets this, a tool cannot provide diagnostics, since a default value is present in the library (such as 1 Ohm for the resistance). In most cases the model will simulate but will give wrong results due to wrong parameter values. To improve this situation, all physical parameter declarations in the Modelica Standard Library have been changed, so that the previous default becomes a start value. For example, the above declaration is changed to:
parameter Modelica.SIunits.Resistance R(start=1);This is a backward compatible change and completely equivalent from the perspective of the Modelica language. It is, however, advised that tools will print a warning or optionally an error message, if the start value of a parameter is defined, but no value for the parameter is given via a modification. Furthermore, it is expected, that the input field of a parameter menu is empty, if no default equation is defined, but only a start value. This shows clearly to the modeler that a value has to be provided.
The following new
components have been added to existing libraries (note, the names
in parentheses are the new sublibrary names that are introduced in
version 3.0):
| Blocks.Examples. | |
| InverseModel | Demonstrates the construction of an inverse model. |
| Blocks.Math. | |
| InverseBlockConstraints | Construct inverse model by requiring that two inputs and two outputs are identical (replaces the previously, unbalanced, TwoInputs and TwoOutputs blocks). |
| Electrical.Machines.Utilities | |
| TransformerData | A record that calculates required impedances (parameters) from nominal data of transformers. |
| Mechanics.MultiBody.Examples.Rotational3DEffects | |
| GyroscopicEffects ActuatedDrive MovingActuatedDrive GearConstraint |
New examples to demonstrate the usage of the Rotational library in combination with multi-body components. |
| Mechanics.MultiBody.Sensors | |
| AbsolutePosition AbsoluteVelocity AbsoluteAngles AbsoluteAngularVelocity RelativePosition RelativeVelocity RelativeAngles RelativeAngularVelocity |
New sensors to measure one vector. |
| TransformAbsoluteVector TransformRelativeVector |
Transform absolute and/or relative vector into another frame. |
| Mechanics.Rotational.(Components) | |
| Disc | Right flange is rotated by a fixed angle with respect to left flange |
| IdealRollingWheel | Simple 1-dim. model of an ideal rolling wheel without inertia |
| Mechanics.Translational.Sensors | |
| RelPositionSensor RelSpeedSensor RelAccSensor PowerSensor |
Relative position sensor, i.e., distance between two
flanges Relative speed sensor Relative acceleration sensor Ideal power sensor |
| Mechanics.Translational(.Components) | |
| SupportFriction Brake InitializeFlange |
Model of friction due to support Model of a brake, base on Coulomb friction Initializes a flange with pre-defined position, speed and acceleration . |
| Mechanics.Translational(.Sources) | |
| Force2 LinearSpeedDependentForce QuadraticSpeedDependentForce ConstantForce ConstantSpeed ForceStep |
Force acting on 2 flanges Force linearly dependent on flange speed Force quadratic dependent on flange speed Constant force source Constant speed source Force step |
The following existing
components have been changed in a non-backward compatible way (the
conversion script transforms models and libraries of previous
versions to the new version. Therefore, conversion should be
automatic):
| Blocks.Continuous. | |
| CriticalDamping | New parameter "normalized" to define whether filter is provided in normalized or non-normalized form. Default is "normalized = true". The previous implementation was a non-normalized filter. The conversion script automatically introduces the modifier "normalized=false" for existing models. |
| Blocks.Interfaces. | |
| RealInput RealOutput |
Removed "SignalType", since extending from a replaceable class
and this is not allowed in Modelica 3. The conversion script removes modifiers to SignalType. |
| RealSignal IntegerSignal BooleanSignal |
Moved to library ObsoleteModelica3, since these connectors are
no longer allowed in Modelica 3 (prefixes input and/or output are required). |
| Blocks.Interfaces.Adaptors. | |
| AdaptorReal AdaptorBoolean AdaptorInteger |
Moved to library ObsoleteModelica3, since the models are not
"balanced". These are completely obsolete adaptors between the Real, Boolean, Integer signal connectors of version 1.6 and version ≥ 2.1 of the Modelica Standard Library. |
| Blocks.Math. | |
| ConvertAllUnits | Moved to library ObsoleteModelica3, since extending from a
replaceable class and this is not allowed in Modelica 3. It would be possible to rewrite this model to use a replaceable component. However, the information about the conversion cannot be visualized in the icon in this case. |
| Blocks.Math.UnitConversions. | |
| TwoInputs TwoOutputs |
Moved to library ObsoleteModelica3, since the models are not
"balanced". A new component "InverseBlockConstraints" is provided instead that has the same feature, but is "balanced". |
| Electrical.Analog.Basic. | |
| HeatingResistor | The heatPort has to be connected; otherwise the component
Resistor (without heatPort) has to be used. cardinality() is only used to check whether the heatPort is connected. |
| Electrical.MultiPhase.Examples. | |
| Changed the instance names of components used in the examples to more up-to-date style. | |
| Electrical.Machines. | |
Moved package Machines.Examples.Utilities to
Machines.Utilities |
|
| Removed all nonSIunits; especially in DCMachines parameter NonSIunits.AngularVelocity_rpm rpmNominal was replaced by parameter SIunits.AngularVelocity wNominal |
|
| Changed the following component variable and parameter names to
be more concise: Removed suffix "DamperCage" from all synchronous induction machines since the user can choose whether the damper cage is present or not. RotorAngle ... RotorDisplacementAngle |
|
| Interfaces. | Moved as much code as possible from specific machine models to partials to reduce redundant code. |
| Interfaces.Adapter | Removed to avoid cardinality; instead, the following solution has been implemented: |
| Sensors.RotorDisplacementAngle Interfaces.PartialBasicMachine |
Introduced parameter Boolean useSupport=false "enable /
disable (=fixed stator) support" The rotational support connector is only present with useSupport = true; otherwise the stator is fixed internally. |
| Electrical.Machines.Examples. | |
| Changed the names of the examples to more meaningful
names. Changed the instance names of components used in the examples to more up-to-date style. |
|
| SMEE_Generator | Initialization of smee.phiMechanical with
fixed=true |
| Mechanics.MultiBody. | |
| World | Changed default value of parameter driveTrainMechanics3D from
false to true. 3-dim. effects in Rotor1D, Mounting1D and BevelGear1D are therefore taken into account by default (previously this was only the case, if world.driveTrainMechanics3D was explicitly set). |
| Mechanics.MultiBody.Forces. | |
| FrameForce FrameTorque FrameForceAndTorque |
Models removed, since functionality now available via Force, Torque, ForceAndTorque |
| WorldForce WorldTorque WorldForceAndTorque Force Torque ForceAndTorque |
Connector frame_resolve is optionally enabled via parameter
resolveInFrame . Forces and torques and be resolved in all meaningful frames defined by enumeration resolveInFrame. |
| Mechanics.MultiBody.Frames. | |
| length normalize |
Removed functions, since available also in
Modelica.Math.Vectors The conversion script changes the references correspondingly. |
| Mechanics.MultiBody.Joints. | |
| Prismatic ActuatedPrismatic Revolute ActuatedRevolute Cylindrical Universal Planar Spherical FreeMotion |
Changed initialization, by replacing initial value parameters
with start/fixed attributes. When start/fixed attributes are properly supported in the parameter menu by a Modelica tool, the initialization is considerably simplified for the user and the implementation is much simpler. Replaced parameter "enforceStates" by the more general built-in enumeration stateSelect=StateSelection.xxx. The conversion script automatically transforms from the "old" to the "new" forms. |
| Revolute ActuatedRevolute |
Parameter "planarCutJoint" in the "Advanced" menu of "Revolute"
and of "ActuatedRevolute" removed. A new joint "RevolutePlanarLoopConstraint" introduced that defines the constraints of a revolute joint as cut-joint in a planar loop. This change was needed in order that the revolute joint can be properly used in advanced model checking. ActuatedRevolute joint removed. Flange connectors of Revolute joint can be enabled with parameter useAxisFlange. |
| Prismatic ActuatedPrismatic |
ActuatedPrismatic joint removed. Flange connectors of Prismatic
joint can be enabled with parameter useAxisFlange. |
| Assemblies | Assembly joint implementation slightly changed, so that
annotation "structurallyIncomplete" could be removed (all Assembly joint models are now "balanced"). |
| Mechanics.MultiBody.Joints.Internal | |
| RevoluteWithLengthConstraint PrismaticWithLengthConstraint |
These joints should not be used by a user of the MultiBody library. They are only provided to built-up the MultiBody.Joints.Assemblies.JointXYZ joints. These two joints have been changed in a slightly not backward compatible way, in order that the usage in the Assemblies.JointXYZ joints results in balanced models (no conversion is provided for this change since the user should not have used these joints and the conversion would be too complicated): In releases before version 3.0 of the Modelica Standard Library, it was possible to activate the torque/force projection equation (= cut-torque/-force projected to the rotation/translation axis must be identical to the drive torque/force of flange axis) via parameter axisTorqueBalance. This is no longer possible, since otherwise this model would not be "balanced" (= same number of unknowns as equations). Instead, when using this model in version 3.0 and later versions, the torque/force projection equation must be provided in the Advanced menu of joints Joints.SphericalSpherical and Joints.UniversalSpherical via the new parameter "constraintResidue". |
| Mechanics.MultiBody.Parts. | |
| BodyBox BodyCylinder |
Changed unit of parameter density from g/cm3 to the SI unit
kg/m3 in order to allow stricter unit checking. The conversion script multiplies previous density values with 1000. |
| Body BodyShape BodyBox BodyCylinder PointMass Rotor1D |
Changed initialization, by replacing initial value parameters
with start/fixed attributes. When start/fixed attributes are properly supported in the parameter menu by a Modelica tool, the initialization is considerably simplified for the user and the implementation is much simpler. The conversion script automatically transforms from the "old" to the "new" form of initialization. |
| Mechanics.MultiBody.Sensors. | |
| AbsoluteSensor RelativeSensor CutForceAndTorque |
New design of sensor components: Via Boolean parameters signal connectors for the respective vectors are enabled/disabled. It is not possible to automatically convert models to this new design. Instead, references in existing models are changed to ObsoleteModelice3. This means that these models must be manually adapted. |
| CutForce CutTorque |
Slightly new design. The force and/or torque component can be
resolved in world, frame_a, or frame_resolved. Existing models are automatically converted. |
| Mechanics.Rotational. | |
| Moved components to structured sub-packages (Sources, Components) | |
| Inertia SpringDamper RelativeStates |
Changed initialization, by replacing initial value parameters
with start/fixed attributes. When start/fixed attributes are properly supported in the parameter menu by a Modelica tool, the initialization is considerably simplified for the user and the implementation is much simpler. Parameter "stateSelection" in "Inertia" and "SpringDamper" replaced by the built-in enumeration stateSelect=StateSelection.xxx. Introduced the "stateSelect" enumeration in "RelativeStates". The conversion script automatically transforms from the "old" to the "new" forms. |
| LossyGear GearBox |
Renamed gear ratio parameter "i" to "ratio", in order to have a
consistent naming convention. Existing models are automatically converted. |
| SpringDamper ElastoBacklash Clutch OneWayClutch |
Relative quantities (phi_rel, w_rel) are used as states, if
possible (due to StateSelect.prefer). In most cases, relative states in drive trains are better suited as absolute states. This change might give changes in the selected states of existing models. This might give rise to problems if, e.g., the initialization was not completely defined in a user model, since the default initialization heuristic may give different initial values. |
| Mechanics.Translational. | |
| Moved components to structured sub-packages (Sources, Components) | |
| Adaptions corresponding to Rotational | |
| Stop | Renamed to Components.MassWithStopAndFriction to be more
concise. MassWithStopAndFriction is not available with a support connector, since the reaction force can't be modeled in a meaningful way due to reinit of velocity v. Until a sound implementation of a hard stop is available, the old model may be used. |
| Media. | |
| constant nX constant nXi constant reference_X BaseProperties |
The package constant nX = nS, now always, even for single species media. This also allows to define mixtures with only 1 element. The package constant nXi=if fixedX then 0 else if reducedX or nS==1 then nS - 1 else nS. This required that all BaseProperties for single species media get an additional equation to define the composition X as {1.0} (or reference_X, which is {1.0} for single species). This will also mean that all user defined single species media need to be updated by that equation. |
| SIunits. | |
| CelsiusTemperature | Removed, since no SI unit. The conversion script changes references to SIunits.Conversions.NonSIunits.Temperature_degC |
| ThermodynamicTemperature TemperatureDifference |
Added annotation "absoluteValue=true/false" in order that unit
checking is possible (the unit checker needs to know for a unit that has an offset, whether it is used as absolute or as a relative number) |
| SIunits.Conversions.NonSIunits. | |
| Temperature_degC Temperature_degF Temperature_degRk |
Added annotation "absoluteValue=true" in order that unit
checking is possible (the unit checker needs to know for a unit that has an offset, whether it is used as absolute or as a relative number) |
| StateGraph.Examples. | |
| ControlledTanks | The connectors of the ControlledTanks did not fulfill the new restrictions of Modelica 3. This has been fixed. |
| Utilities | Replacing inflow, outflow by connectors inflow1, inflow2, outflow1, outflow2 with appropriate input/output prefixes in order to fulfill the restrictions of Modelica 3 to arrive at balanced models. No conversion is provided, since too difficult and since the non-backward compatible change is in an example. |
| Thermal.FluidHeatFlow.Sensors. | |
pSensor TSensor dpSensor dTSensor m_flowSensor V_flowSensor H_flowSensor |
renamed to: PressureSensor TemperatureSensor RelPressureSensor RelTemperatureSensor MassFlowSensor VolumeFlowSensor EnthalpyFlowSensor |
| Thermal.FluidHeatFlow.Sources. | |
| Ambient PrescribedAmbient |
available as one combined component Ambient Boolean parameters usePressureInput and useTemperatureInput decide whether pressure and/or temperature are constant or prescribed |
| ConstantVolumeFlow PrescribedVolumeFlow |
available as one combined component VolumeFlow Boolean parameter useVolumeFlowInput decides whether volume flow is constant or prescribed |
| ConstantPressureIncrease PrescribedPressureIncrease |
available as one combined component PressureIncrease Boolean parameter usePressureIncreaseInput decides whether pressure increase is constant or prescribed |
| Thermal.FluidHeatFlow.Examples. | |
| Changed the instance names of components used in the examples to more up-to-date style. | |
| Thermal.HeatTransfer.(Components) | |
| HeatCapacitor | Initialization changed: SteadyStateStart removed. Instead
start/fixed values for T and der_T (initial temperature and its derivative). |
HeatCapacitor ThermalConductor ThermalConvection BodyRadiation TemperatureSensor RelTemperatureSensor HeatFlowSensor FixedTemperature PrescribedTemperature FixedHeatFlow PrescribedHeatFlow |
Moved components to sub-packages: Components.HeatCapacitor Components.ThermalConductor Components.ThermalConvection Components.BodyRadiation Sensors.TemperatureSensor Sensors.RelTemperatureSensor Sensors.HeatFlowSensor Sources.FixedTemperature Sources.PrescribedTemperature Sources.FixedHeatFlow Sources.PrescribedHeatFlow |
| Thermal.FluidHeatFlow.Examples. | |
| Changed the instance names of components used in the examples to more up-to-date style. |
The following existing
components have been improved in a backward compatible way:
| Modelica.* | Parameter declarations, input and output function arguments
without description strings improved by providing meaningful description texts. |
| Modelica.Blocks.Continuous. | |
| TransferFunction | Internal scaling of the controller canonical states introduced in order to enlarge the range of transfer functions where the default relative tolerance of the simulator is sufficient. |
| Butterworth CriticalDamping |
Documentation improved and plots of the filter characteristics added. |
| Electrical.Analog.Basic. | |
| EMF | New parameter "useSupport" to optionally enable a support connector. |
| Icons. | |
| TranslationalSensor RotationalSensor |
Removed drawing from the diagram layer (kept drawing only in
icon layer), in order that this icon can be used in situations where components are dragged in the diagram layer. |
| Math.Vectors. | |
| normalize | Implementation changed, so that the result is awalys
continuous (previously, this was not the case for small vectors: normalize(eps,eps)). |
| Mechanics.MultiBody. | |
| Renamed non-standard keywords defineBranch, defineRoot,
definePotentialRoot, isRooted to the standard names: Connections.branch/.root/.potentialRoot/.isRooted. |
|
| Frames | Added annotation "Inline=true" to all one-line functions (which should be all inlined). |
| Mechanics.MultiBody.Parts. | |
| Mounting1D Rotor1D BevelGear1D |
Changed implementation so that no longer modifiers for
connector variables are used, because this violates the restrictions on "balanced models" of Modelica 3. |
| Mechanics.Rotational. | |
| InitializeFlange | Changed implementation so that counting unknowns and equations is possible without actual values of parameters. |
| Thermal.FluidHeatFlow.Interfaces.Partials. | |
| TwoPort | Introduced parameter Real tapT(final min=0, final
max=1)=1 that defines the temperature of the heatPort between inlet and outlet. |
| StateGraph. | |
| InitialStep InitialStepWithSignal Step StepWithSignal |
Changed implementation so that no longer modifiers for output
variables are used, because this violates the restrictions on "balanced models" of Modelica 3. |
The following critical
errors have been fixed (i.e., errors that can lead
to wrong simulation results):
| Electrical.Analog.Examples. | |
| CauerLowPassSC | Wrong calculation of Capacitor1 both in Rn and Rp corrected (C=clock/R instead of C=clock*R) |
| Mechanics.MultiBody.Parts. | |
| Rotor1D | The 3D reaction torque was not completely correct and gave in some situations a wrong result. This bug should not influence the movement of a multi-body system, but only the constraint torques are sometimes not correct. |
| Mechanics.Rotational. | |
| ElastoBacklash | If the damping torque was too large, the reaction torque could "pull" which is unphysical. The component was newly written by limiting the damping torque in such a case so that "pulling" torques can no longer occur. Furthermore, during initialization the characteristics is made continuous to reduce numerical errors. The relative angle and relative angular velocities are used as states, if possible (StateSelect.prefer), since relative quantities lead usually to better behavior. |
| Position Speed Accelerate Move |
The movement of the flange was wrongly defined as absolute;
this is corrected as relative to connector support. For Accelerate, it was necessary to rename RealInput a to a_ref, as well as the start values phi_start to phi.start and w_start to w.start. The conversion script performs the necessary conversion of existing models automatically. |
| Media.Interfaces. | |
| PartialSimpleIdealGasMedium | Inconsistency in reference temperature corrected. This may give
different results for functions: specificEnthalpy, specificInternalEnergy, specificGibbsEnergy, specificHelmholtzEnergy. |
| Media.Air. | |
| specificEntropy | Small bug in entropy computation of ideal gas mixtures corrected. |
| Media.IdealGases.Common.MixtureGasNasa | |
| specificEntropy | Small bug in entropy computation of ideal gas mixtures corrected. |
The following uncritical
errors have been fixed (i.e., errors that do
not lead to wrong
simulation results, but, e.g., units are wrong or errors in
documentation):
| Blocks.Tables. | |
| CombiTable2D | Documentation improved. |
| Electrica.Digital.Gates | |
| AndGate NandGate OrGate NorGate XorGate XnorGate |
The number of inputs was not correctly propagated to the
included base model. This gave a translation error, if the number of inputs was changed (and not the default used). |
| Electrica.Digital.Sources | |
| Pulse | Model differently implemented, so that warning message about "cannot properly initialize" is gone. |
| Mechanics.Rotational. | |
| BearingFriction Clutch OneWayClutch Brake Gear |
Declaration of table parameter changed from table[:,:] to table[:,2]. |
| Modelica.Mechanics.MultiBody.Examples.Loops.Utilities. | |
| GasForce | Unit of variable "press" corrected (from Pa to bar) |
| StateGraph.Examples. | |
| SimpleFriction | The internal parameter k is defined and calculated with the appropriate unit. |
| Thermal.FluidHeatFlow.Interfaces.Partials. | |
| SimpleFriction | The internal parameter k is defined and calculated with the appropriate unit. |


A module that can be used to implement AMD's define() in Node. This allows you to code to the AMD API and have the module work in node programs without requiring those other programs to use AMD.
1) Update your package.json to indicate amdefine as a dependency:
"dependencies": {
"amdefine": ">=0.1.0"
}
Then run npm install
to get amdefine into your project.
2) At the top of each module that uses define(), place this code:
if (typeof define !== 'function') { var define = require('amdefine')(module) }
Only use these snippets when loading amdefine. If you preserve the basic structure, with the braces, it will be stripped out when using the RequireJS optimizer.
You can add spaces, line breaks and even require amdefine with a local path, but keep the rest of the structure to get the stripping behavior.
As you may know, because if
statements in JavaScript don't have their own scope, the var
declaration in the above snippet is made whether the if
expression is truthy or not. If
RequireJS is loaded then the declaration is superfluous because define
is already already
declared in the same scope in RequireJS. Fortunately JavaScript handles multiple var
declarations of the same variable in the same scope gracefully.
If you want to deliver amdefine.js with your code rather than specifying it as a dependency with npm, then just download the latest release and refer to it using a relative path:
Consider this very experimental.
Instead of pasting the piece of text for the amdefine setup of a define
variable in each module you create or consume, you can use amdefine/intercept
instead. It will automatically insert the above snippet in each .js file loaded
by Node.
Warning: you should only use this if you are creating an application that is consuming AMD style defined()'d modules that are distributed via npm and want to run that code in Node.
For library code where you are not sure if it will be used by others in Node or
in the browser, then explicitly depending on amdefine and placing the code
snippet above is suggested path, instead of using amdefine/intercept
. The
intercept module affects all .js files loaded in the Node app, and it is
inconsiderate to modify global state like that unless you are also controlling
the top level app.
npm has a lot of weaknesses for front-end use (installed layout is not great, should have better support for the `baseUrl + moduleID + '.js' style of loading, single file JS installs), but some people want a JS package manager and are willing to live with those constraints. If that is you, but still want to author in AMD style modules to get dynamic require([]), better direct source usage and powerful loader plugin support in the browser, then this tool can help.
Just require it in your top level app module (for example index.js, server.js):
require('amdefine/intercept');
The module does not return a value, so no need to assign the result to a local variable.
Then just require() code as you normally would with Node's require(). Any .js loaded after the intercept require will have the amdefine check injected in the .js source as it is loaded. It does not modify the source on disk, just prepends some content to the text of the module as it is loaded by Node.
It overrides the Module._extensions['.js']
in Node to automatically prepend
the amdefine snippet above. So, it will affect any .js file loaded by your
app.
It is best if you use the anonymous forms of define() in your module:
define(function (require) {
var dependency = require('dependency');
});
or
define(['dependency'], function (dependency) {
});
Version 1.0.3 of the RequireJS optimizer
will have support for stripping the if (typeof define !== 'function')
check
mentioned above, so you can include this snippet for code that runs in the
browser, but avoid taking the cost of the if() statement once the code is
optimized for deployment.
If you want to support Node 0.4, then add require
as the second parameter to amdefine:
//Only if you want Node 0.4. If using 0.5 or later, use the above snippet.
if (typeof define !== 'function') { var define = require('amdefine')(module, require) }
amdefine creates a define() function that is callable by your code. It will execute and trace dependencies and call the factory function synchronously, to keep the behavior in line with Node's synchronous dependency tracing.
The exception: calling AMD's callback-style require() from inside a factory function. The require callback is called on process.nextTick():
define(function (require) {
require(['a'], function(a) {
//'a' is loaded synchronously, but
//this callback is called on process.nextTick().
});
});
Loader plugins are supported as long as they call their load() callbacks synchronously. So ones that do network requests will not work. However plugins like text can load text files locally.
The plugin API's load.fromText()
is not supported in amdefine, so this means
transpiler plugins like the CoffeeScript loader plugin
will not work. This may be fixable, but it is a bit complex, and I do not have
enough node-fu to figure it out yet. See the source for amdefine.js if you want
to get an idea of the issues involved.
To run the tests, cd to tests and run:
node all.js
node all-intercept.js
New BSD and MIT. Check the LICENSE file for all the details.


Configuring a Development System
Sensus is built on top of the Xamarin framework. The reason for this is two-fold: first, we aim for a mobile sensing system that runs on Android and iOS; second, we do not have a large software development team to reimplement Sensus from scratch on each mobile OS. Xamarin allows us to write the vast majority of our code one time and run it natively on each mobile OS. This includes the user interface. A small amount of functionality must be reimplemented for each OS (e.g., interacting with the hardware sensors), but the overall economy of our approach is substantial. Xamarin is free, and C# (Xamarin's high-level language) is a full-featured language that is similar to Java.
Setup
- After installing Xamarin (targeting the Xamarin Studio Community IDE or Visual Studio), you should open Xamarin/Visual Studio and grab any remaining updates for the environment.
- Fork the official Sensus repository to your personal GitHub account and then clone the Sensus repository from your personal GitHub account to your local machine. This setup will allow you to commit changes back to your GitHub repository and create pull requests from your repository to the official Sensus repository.
- Open the Sensus solution within Xamarin/Visual Studio. The IDE should automatically restore the packages required for the
solution. There are sometimes issues with packages that we have had to address by building our own private versions of the
officially distributed packages (e.g., Nugets). See the
ReferenceFixes
directory for more information and directions for fixing these issues. - You should now be able to build the solution. After building, close Xamarin/Visual Studio and check that no modifications
have been made to your local repository. If any changes have been made, they are probably due to reordering of certain files
(e.g., project references within the .csproj files). Since the order of these files does not matter, you can safely
git checkout .
from the root of your Sensus repository to undo these changes. Lastly, create a symbolic link from
Scripts/git-pre-commit.sh
to.git/hooks/pre-commit
in your local Sensus repository and make the script executable. For example:ln -s [FULL PATH TO SENSUS REPO]/Scripts/git-pre-commit.sh [FULL PATH TO SENSUS REPO]/.git/hooks/pre-commit chmod +x [FULL PATH TO SENSUS REPO]/.git/hooks/pre-commit
You now have a clean, compiling version of Sensus.


This setting allows users to change the default durability mode for running Pipelines. In most cases this is a
trade-off between performance and the ability for running pipelines to resume after unplanned Jenkins outages.
What does this do?
- Previously, running pipelines wrote data constantly, so that they could resume even if Jenkins fails.
This setting gives the user the ability to adjust this write behavior.
- Higher-performance/lower-durability modes write data to disk much less often for running pipelines.
- Writing data less often can massively reduce build times for Pipelines with many steps or complex logic.
For pipelines which spend most of their time waiting for a shell/batch script to run, the difference will be less visible.
- Running pipelines with lower durability settings may lose data if they do not finish and Jenkins is not shut down gracefully:
- A "graceful" shutdown where Jenkins goes through a full shutdown process, such as visiting
http://[jenkins-server]/exit
- A "dirty" shutdown, such as using
kill -9
to terminate the Jenkins process, may prevent incomplete pipelines from persisting data
- Pipelines that cannot persist data may not be able to resume or displayed in Blue Ocean/Stage View/etc.
- Pipelines will generally write log data regardless of durability settings.
- Some modes use an "atomic write" option - this helps ensure that pipeline build files aren't overwritten or left partially written if something fails.
- Atomic writes may place more stress on filesystems, so especially with networked storage it may be faster not to use them.
Note: this only sets a global default. Individual Pipelines and MultiBranch projects may override the global default.


Brittany Bodenheimer
President
We work to educate people in the community (both on and off campus) about current issues, get students involved in the legislative process, and further the goals and ideologies of the Democratic party. Our primary goal is to increase civic engagement through education, volunteer work, and training. We work in conjunction with Kansas Young Democrats, Young Democrats of America, and the Kansas Democratic Party.
President
Vice President
Secretary, Designer


There are four methods added to all controllers for rendering:
- renderPdf(Map args)
- renderGif(Map args)
- renderPng(Map args)
- renderJpeg(Map args)
Each of the methods is equivalent to…«format»RenderingService.render(args + [controller: this], response)
All methods take all of the arguments that their respective service's render()
method take, plus some extras.Extra Render Arguments
All rendering methods take a Map
argument that specifies which template to render and the model to use (in most cases).The following map arguments are common to all rendering methods:
filename
(option) - sets the Content-Disposition
header with attachment; filename="$filename";
(asking the browser to download the file with the given filename)
contentType
(optional) - the Content-Type
header value (see Content Type Defaults below)
Default Content Types
The default content types are…
- application/pdf
- image/gif
- image/png
- image/jpeg
Large Files/Renders
See the section on caching and performance for some other arguments that can help with large renders.


{% extends "base.html" %} {% block head_title %}Home{% endblock %} {% block content %} {% include "tabbar.html" %}
This page will hold a description of what this website does.
For instance: This is a demonstration of the AIR Toolkit.


Welcome to the JAWS Training Lab
Objectives:
There are several primary objectives for this OracleJET web
application:
- Provide an area to practice using JAWS to navigate and interact with a web application.
- Provide examples of inaccessible code and contrast it with the same code
coded to be accessible.
- Provide instructions on how to use JAWS to validate the accessibility of a web page.
Requirements:
It is strongly reccomended that a full-sized keyboard be used while following this training and while performing JAWS accessibility validation. The reason for this is that many JAWS specific functions rely on the numeric pad on a full-sized keyboard.
When you are told to enter numbers, the numbers are those along the top of the alphanumeric portion of the keyboard. When you are told to use the arrow keys, they are the keys located in an inverted "T" shape just right of the main keyboard, and when specific "JAWS" keys are mentioned they are located in the numeric pad as discussed below.
On the numeric pad (numpad) the most important keys for use with JAWS are explained below:
- JAWSKEY or insert key (terms used interchangeably throughout this training)
- This is the long horizontal key on the lower left corner of the numpad.
It is used to modify other keys to perform various JAWS functions.
- PC Cursor Key
- This is the long vertical key in the middle along the right side of the numpad. This key is used to switch JAWS into PC Cursor Mode which is the normal mode where JAWS follows the insertion point rather than the mouse cursor. This key is also used to exit FORMS mode as discussed in lesson 2.
- JAWS Cursor Key
- This is the key in the top right corner of the keypad. It is used to switch JAWS into JAWS mode where the JAWS speech follows the mouse pointer rather than the insertion point. We do not use this mode specifically in this training but the key was included for completeness.
Special Notes:
- From here on, NO MOUSE is allowed!
- Whenever JAWS is being used, the numlock key *MUST* be
turned off so that the JAWS functions can be accessed using
the numpad.
- NOTE 2: Because JAWS reads web pages into a virtual
buffer and works on that buffer, What you see is not always
what you get. Sometimes JAWS is operating on a part of the
page that is not visible, so it is best to rely on JAWS and
to turn off the display altogether.
Now on to lesson #1 and happy browsing!


EZID and N2T at CDL Presentation at UC DLFx, February 27, 2018
Four Unsolved Problems (with Persistent Identifiers) Presentation at PIDapalooza, Palau de Congressos de Girona, Spain, January 23, 2018
Compact Identifiers for Data Citation in Biomedicine and Beyond Presentation at PIDapalooza, Palau de Congressos de Girona, Spain, January 23, 2018
DOI service providers: 4 factors to consider
Software Citation Principles Presentation at DataCite Strategy Meeting (slides), April 3, 2017
Identifiers and Citation: Frequently Asked Questions Presentation at California Data Librarians conference (slides), March 14, 2017
Identifiers and Citation Webinar for CENDI (slides), Feb. 15, 2017


--- layout: post status: publish published: true title: Upgraded to Ubuntu 9.04 author: display_name: Tomas Restrepo login: tomasr email<EMAIL_ADDRESS>url: http://winterdom.com/ author_login: tomasr author_email<EMAIL_ADDRESS>author_url: http://winterdom.com/ wordpress_id: 40 wordpress_url: http://winterdom.com/2009/04/upgradedtoubuntu904 date: '2009-04-23 23:16:14 +0000' date_gmt: '2009-04-23 23:16:14 +0000' categories: - Linux tags: [] comments: - id: 768 author: Pedro author_email<EMAIL_ADDRESS>author_url: '' date: '2009-05-13 20:27:11 +0000' date_gmt: '2009-05-13 20:27:11 +0000' content: Nice desktop. What's the theme you're using? - id: 769 author: Tomas Restrepo author_email<EMAIL_ADDRESS>author_url: http://winterdom.com/ date: '2009-05-14 00:44:03 +0000' date_gmt: '2009-05-14 00:44:03 +0000' content: 'Pedro: I believe it''s New Wave Dark Menus with a few customized things (like the icons). The wallpaper is just something I created with http://www.bgpatterns.com/ if I remember correctly.' ---
Today was the release of Ubuntu 9.04 Jaunty Jackalope, so I immediately started an in-place upgrade of my Dell D820 laptop. Downloading the packages took forever (the servers where obviously getting hammered pretty badly), but finally completed at the end of the afternoon.
After that, actually installing the downloaded packages took about an hour and a half, part of it because I always forget how many prompts an Ubuntu update puts up throughout the process.
After installation and rebooting, I came up to pretty much the same desktop I had before (good). However, I soon ran into troubles: X and Gnome completely locking hard on me. No applications would respond at all (not even a terminal window already opened) so I was forced to drop back to another terminal window and reboot the machine from there.
After this happening three or four times in a row, I realized the lockup would only happen when I tried to change the theme from the Gnome settings panel. As long as I didn’t do that, everything seemed to work just fine.
That’s when it occurred to me to just drop down and remove my ~/.themes
directory. As soon as I did that, I was able to change my gnome appearance settings without X locking up on me.
Not sure what I had in there to cause such troubles, but there you go. I’ll report later then on any new things I find.


/* <CoffeeScript>
functions = require('./functions').functions
utils = require('tztime').utils
histogram = (rows, valueField, noClipping = false) ->
</CoffeeScript> */
/**
* @method histogram
* @member Lumenize
* @param {Object[]} rows
* @param {String} valueField Specifies the field containing the data to calculate the histogram
* @return {Object[]}
*
* Returns an object containing the following:
*
* * buckets - An Array containing {label, count, rows, clippedChartValue}
* * bucketSize - The size of each bucket (except the top one)
* * chartMax - The maximum to use for charting using clipped values
* * clipped - A Boolean indicating if the result is clipped
* * valueMax - The actual maximum value found. Will always be >= chartMax
*
* Given an array of rows like:
*
* {histogram} = require('../')
*
* rows = [
* {age: 7},
* {age: 25},
* {age: 23},
* {age: 27},
* {age: 34},
* {age: 55},
* {age: 42},
* {age: 13},
* {age: 11},
* {age: 23},
* {age: 31},
* {age: 32},
* {age: 29},
* {age: 16},
* {age: 31},
* {age: 22},
* {age: 25},
* ]
*
* histogram will calculate a histogram. There will be sqrt(n) + 1 buckets
*
* {buckets, chartMax} = histogram(rows, 'age')
* for b in buckets
* console.log(b.label, b.count)
* # 0-12 2
* # 12-24 5
* # 24-36 8
* # 36-48 1
* # 48-60 1
*
* console.log(chartMax)
* # 60
*
* This histogram calculator will also attempt to lump outliers into a single bucket at the top.
*
* rows.push({age: 85})
*
* {buckets, chartMax} = histogram(rows, 'age')
*
* lastBucket = buckets[buckets.length - 1]
* console.log(lastBucket.label, lastBucket.count)
* # 48-86* 2
*
* The asterix `*` is there to indicate that this bucket is not the same size as the others and non-linear.
* The histogram calculator will also "clip" the values for these outliers so that you can
* display them in a scatter chart on a linear scale with the last band compressed.
* The `clippedChartValue` will be guaranteed to be below the `chartMax` by interpolating it's position between
* the bounds of the top band where the actual max value is scaled down to the `chartMax`
*
* lastBucket = buckets[buckets.length - 1]
* console.log(lastBucket.rows[1].age, lastBucket.rows[1].clippedChartValue)
* # 85 59.68421052631579
*
*/
/* <CoffeeScript>
chartValues = (row[valueField] for row in rows)
max = functions.max(chartValues)
max = Math.max(max, 1)
if noClipping
upperBound = max
chartValuesMinusOutliers = chartValues
else
q3 = functions.percentileCreator(75)(chartValues)
q1 = functions.percentileCreator(25)(chartValues)
iqr = q3 - q1
upperBound = q3 + 1.5 * iqr # This is the Tukey recommendation http://exploringdata.net/why_1_5.htm
if isNaN(upperBound) or upperBound > max
upperBound = max
chartValuesMinusOutliers = (c for c in chartValues when c <= upperBound)
bucketCount = Math.floor(Math.sqrt(chartValuesMinusOutliers.length))
if bucketCount < 3
bucketCount = 2
bucketSize = Math.floor(upperBound / bucketCount) + 1
upperBound = bucketSize * bucketCount
chartMin = 0
chartMax = upperBound + bucketSize # This will be at the very top of the top bucket
valueMax = Math.floor(functions.max(chartValues)) + 1
valueMax = Math.max(chartMax, valueMax)
# add clippedChartValues to timeInState
# the clippedChartValue is interpolated between upperBound and valueMax to fit within one bucketSize
for row in rows
if row[valueField] >= upperBound
row.clippedChartValue = upperBound + bucketSize * (row[valueField] - upperBound) / (valueMax - upperBound)
else
row.clippedChartValue = row[valueField]
buckets = []
for i in [0..bucketCount]
bucket = {
label: "#{Math.floor(i * bucketSize)}-#{Math.floor((i + 1) * bucketSize)}",
rows: []
count: 0
}
buckets.push(bucket)
clipped = not (valueMax == chartMax)
if clipped
buckets[bucketCount].label = "#{upperBound}-#{valueMax}*"
else
buckets[bucketCount].label = "#{upperBound}-#{valueMax}"
total = 0
for row in rows
if row[valueField] >= upperBound
bucket = buckets[buckets.length - 1]
else
bucket = buckets[Math.floor(row[valueField] / bucketSize)]
bucket.rows.push(row)
bucket.count++
total++
percentile = 0
for b in buckets
percentile += b.count / total
if isNaN(percentile)
b.percentile = 0
else
b.percentile = percentile
buckets[buckets.length - 1].percentile = 1.0
return {buckets, bucketSize, chartMax, clipped, valueMax}
exports.histogram = histogram
</CoffeeScript> */


@(user: models.User)(headContent: Html)
@(user.name, user.surname) match {
case (None, None) =><EMAIL_ADDRESS>case (Some(name), None) => {name}
case (None, Some(surname)) => {surname}
case (name, surname) => {@{name}@{headContent}@surname}
case _ =><EMAIL_ADDRESS>}


Stochastic SIR model
There is also a
simplified version
.
Event rates
Infection: \(\beta \cdot I \cdot \frac{S}{N - 1}\)
\(\quad\implies\quad\)
Recovery: \(\gamma \cdot I\)
\(\quad\implies\quad\)
Parameters
R
0
:
\(\quad\implies\quad\beta\):
Infectious period \(\left(\frac{1}{\gamma}\right)\):
\(\quad\implies\quad\gamma\):
Population size \(\left(N\right)\):
Outbreak
Random events
Extinction
Take-off
Start outbreak
Next event
Run to end


What is an icon?
On a Web page, an icon is often a graphical image that represents the topic or information category of another Web page.
What are sprites?
Sprites are 2D bit maps that draw directly on a representation destination without using transformation, lighting or effects channeling.


{% extends "global/Page.html" %} {% load otree static %} {% block title %} Result {% endblock %} {% block content %}
Round {{ round_to_pay }} has been chosen for payment. The lottery in round {{ round_to_pay }} has {{ chosen_probability }} chance to pay {{ high }} and otherwise to pay {{ low }}. The payout of this lottery has been randomly determined to be {{ outcome }}.
You, as group member {{ id_self }}, proposed that the minimum amount that your group would accept in exchang of the lottery is {{ ce_p }}; group member {{ id_other1 }} proposed {{ ce_p1 }}; group member {{ id_other2 }} proposed {{ ce_p2 }}. Therefore, your group's decision is {{ group_ce }}.
A random number between {{ low }} and {{ high }} has been drawn which is {{ rnd_bdm }}. Hence, your group will receive {{ receive }} and is paid {{ group_payoff }}. Each of you will receive this amount divided by {{ group_size }} so the individual payoff is {{ payoff }}. Your final payoff from this experiment, including your budget, is {{ final_payoff }}.
{% next_button %} {% endblock %}


Miami GP plans get six-month reprieve
Hopes that Miami will be able to host a Formula 1 race in 2021 will stay alive for at least another "three to six months", according to local mayor Carlos Gimenez.
by GMM F1F1 has reached a deal in principle for a race at and near Hard Rock Stadium, but preparations hit an early snag when opposition groups made key blocking moves at the Miami-Dade commission.
Mayor Gimenez used his veto to block the opposition earlier in November.
And this week, an effort to override that veto failed as commissioners only voted 5 to 7.
"This race isn't until May of 2021," Gimenez told CBS Miami.
"Sustaining my veto buys three to six months so that we can at least get the parties that are involved together and we can continue to work toward a solution," he added.
Formula One Management as well as Hard Rock Stadium CEO Tom Garfinkel said in similarly-worded statements that they will now use the extra time to work "very hard to address community concerns in a meaningful way".
body check tags ::


Canvas not supported! =[
Failed to initialize WebGL! Are you sure your browser supports it?
FireFox: supported automatically
Chrome: supported automatically
Safari: Preferences -> Advanced -> Show Develop Menu; then Develop -> Enable WebGL
Opera: supported automatically
Internet Explorer: not supported, probably ever
mobile browsers: hopefully some day...
Amplitude
Wavelength
Direction
Speed
Big waves
Small waves
Show water
Show terrain


Classification propagation enables classifications associated to an entity to be automatically associated with other related entities of the entity. This is very useful in dealing with scenarios where a dataset derives it data from other datasets - like a table loaded with data in a file, a report generated from a table/view, etc. For example, when a table is classified as "PII", tables or views that derive data from this table (via CTAS or ‘create view’ operation) will be automatically classified as "PII".
Consider the following lineage where data from a 'hdfs_path' entity is loaded into a table, which is further made available through views. We will go through various scenarios to understand the classification propagation feature.
When classification ‘PII’ is added to 'hdfs_path' entity, the classification is propagated to all impacted entities in the lineage path, including 'employees' table, views 'us_employees' and 'uk_employees' - as shown below.
Any updates to classifications associated with an entity will be seen in all entities the classification is propagated to as well.
When a classification is deleted from an entity, the classification will be removed from all entities the classification is propagated to as well.
When lineage is added between entities, for example to capture loading of data in a file to a table, the classifications associated with the source entity are propagated to all impacted entities as well.
For example, when a view is created from a table, classifications associated with the table are propagated to the newly created view as well.
Case 1: When an entity is deleted, classifications associated with this entity will be removed from all entities the classifications are propagated to.
For example. when employees table is deleted, classifications associated with this table are removed from 'employees_view' view.
Case 2: When an entity is deleted in the middle of a lineage path, the propagation link is broken and previously propagated classifications will be removed from all derived entities of the deleted entity.
For example. when 'us_employees' table is deleted, classifications propagating through this table (PII) are removed from 'ca_employees' table, since the only path of propagation is broken by entity deletion.
Case 3: When an entity is deleted in the middle of a lineage path and if there exists alternate path for propagation, previously propagated classifications will be retained.
For example. when 'us_employees' table is deleted, classifications propagating (PII) through this table are retained in 'ca_employees' table, since there are two propagation paths available and only one of them is broken by entity deletion.
Apache Atlas provides few options to control whether/where a classification is propagated. This section details available options.
Each association of classification to an entity has a boolean flag that controls whether the classification is propagated or not. When a classification is associated with an entity, this flag is set to ‘true’ i.e. the classification will be propagated to all impacted entities. This flag can be updated to desired value during initial association or later.
Apache Atlas supports a flag at lineage edge to enable/disable propagation of classifications through the edge. By default, the propagation is enabled for lineage edges. When the flag is turned off, no classification will be propagated through this edge; and propagation of currently propagated classifications through the edge will be reevaluated, so that they can be removed from impacted entities. When the flag is turned on, propagation of classifications of the source entity will be reevaluated, so that they can be propagated to all impacted entities.
Apache Atlas supports blocking propagation of specific classifications in at lineage edges. This can be useful, for example, to handle scenarios like: a column classified as PII is masked when creating a view; in such scenario, if corresponding column in the created view might not have PII, hence the propagation of PII classification should be blocked. This can be done by updating the lineage edge to add the PII classification in ‘blocked propagated classifications’ list. Classifications in blocked propagated classifications will not be propagated in the derivative/downstream entities.