Before Change
The output feature of shape :math:`(N, D_{out})` where :math:`D_{out}`
is the output feature size.
graph = graph.local_var()
graph.ndata["h"] = self.fc(feat).view(-1, self._n_kernels, self._out_feats)
E = graph.number_of_edges()
// compute gaussian weight
gaussian = -0.5 * ((pseudo.view(E, 1, self._dim) -
After Change
The output feature of shape :math:`(N, D_{out})` where :math:`D_{out}`
is the output feature size.
with graph.local_scope():
feat_src, feat_dst = expand_as_pair(feat)
graph.srcdata["h"] = self.fc(feat_src).view(-1, self._n_kernels, self._out_feats)
E = graph.number_of_edges()
// compute gaussian weight
gaussian = -0.5 * ((pseudo.view(E, 1, self._dim) -
self.mu.view(1, self._n_kernels, self._dim)) ** 2)
gaussian = gaussian * (self.inv_sigma.view(1, self._n_kernels, self._dim) ** 2)
gaussian = th.exp(gaussian.sum(dim=-1, keepdim=True)) // (E, K, 1)
graph.edata["w"] = gaussian
graph.update_all(fn.u_mul_e("h", "w", "m"), self._reducer("m", "h"))
rst = graph.dstdata["h"].sum(1)
// residual connection
if self.res_fc is not None:
rst = rst + self.res_fc(feat_dst)
// bias
if self.bias is not None:
rst = rst + self.bias
return rst


impl-args.Rd
Define implementation parameters
define_impl(proto_ipm, kernel_impl_list) make_impl_args_list(kernel_names, int_rule, dom_start, dom_end, ...)
| proto_ipm | The name of object you wish to append the new kernel to. |
|---|---|
| kernel_impl_list | A named list. Names correspond to kernel names. Each
kernel should have 3 slots defined - the |
| kernel_names | A character vector with the names of the kernels that parameters are being defined for. |
| int_rule | The integration rule to be used for the kernel. The default is "midpoint". "trapezoid" and "g-l" (Gauss-Legendre) will be implemented as well. If "g-l", additional arguments need to be supplied (Work on this later!!). |
| dom_start | The name of the state variable for the kernel at time t. |
| dom_end | The name of the state variable for the kernel at time t+1.
This is usually the same as |
| ... | Additional arguments required for |
A proto_ipm
with the implementation details stored.
define_impl
is meant to help distinguish the process of
generating the kernels' mathematical form from their implementation details.
It takes a proto_ipm
object and returns a modified one containing the
implementation information.
make_impl_args_list
helps generate that
information in the correct format. It is usually easiest to call make_impl_args_list
before calling init_ipm
and then substituting that variable into
the call to define_impl
. Alternatively, one can do something like
define_impl(kernel_impl_list = make_impl_arg_list(...))
within the course
of the model definitition pipeline.


Stephanie Major
Home
Product Management
Projects
About
Blog
Git and Github
CSS: Margins, Borders, Padding
Ruby: Arrays and Hashes
Ruby: Enumerable Methods
Ruby vs JavaScript
NoSQL Databases
Code Programming - Moving On
Learning Agile
The Role of a Product Manager


|
ComInterface
|
TCP/IP Socket communication interface. It can be used as a server or a client. More...
#include <comsocket.hpp>
Public Member Functions | |
| ComSocket (const std::string &address="<IP_ADDRESS>", unsigned int port=3444, unsigned int timeout=1000) | |
| TCP/IP socket interface constructor. More... | |
| virtual | ~ComSocket () |
| Virtual destructor for the socket interface. It is necessary for polymorphism. | |
| virtual bool | Open () |
| Open the interface. More... | |
| virtual bool | Close () |
| Close the interface. More... | |
| virtual bool | Opened () |
| Check if the interface is currently opened. More... | |
| virtual int | ReadSome (void *buffer_in, size_t len) |
| Non blocking read. It tries to read the available bytes for the interface. More... | |
| virtual int | WriteSome (const void *buffer_out, size_t len) |
| Non blocking write. It tries to write the the data passed to it. More... | |
| virtual int | Read (void *buffer_in, size_t len) |
| Blocking read. It waits until the indicated number of bytes are received or the timeout expires. More... | |
| virtual int | Write (const void *buffer_out, size_t len) |
| Blocking write. It waits until the indicated number of bytes are transmitted or the timeout expires. More... | |
| virtual void | Abort () |
| Abort the current operation on the interface. | |
| virtual bool | SetWriteTimeout (unsigned int write_timeout) |
| Set the timeout time of the Write operations. More... | |
| virtual unsigned int | GetWriteTimeout () |
| Get the timeout time of the Write operations. More... | |
| virtual bool | SetReadTimeout (unsigned int read_timeout) |
| Set the timeout time of the Read operations. More... | |
| virtual unsigned int | GetReadTimeout () |
| Get the timeout time of the Read operations. More... | |
| bool | SetOpenTimeout (unsigned int open_timeout) |
| Set the timeout time of the Open operations. More... | |
| unsigned int | GetOpenTimeout () |
| Get the timeout time of the Open operations. More... | |
| bool | SetAddress (const std::string &address) |
| Set the IP address of the device to connect. More... | |
| std::string | GetAddress () |
| Get the IP address of the device to connect. More... | |
| bool | SetPort (unsigned int port) |
| Set the TCP port of the service to connect. More... | |
| unsigned int | GetPort () |
| Get the TCP port of the service to connect. More... | |
| Public Member Functions inherited from ComInterface | |
| virtual | ~ComInterface () |
| Virtual destructor for the interface. It is necessary for polymorphism. | |
| std::string | GetVersion () |
| Get the version of the library. More... | |
TCP/IP Socket communication interface. It can be used as a server or a client.
| ComSocket::ComSocket | ( | const std::string & | address = "<IP_ADDRESS>" , |
| unsigned int | port = 3444 , |
||
| unsigned int | timeout = 1000 |
||
| ) |
TCP/IP socket interface constructor.
| address | IP address of the device to connect. Example: "<IP_ADDRESS>". If set to "", the use mode is server. Else, client mode. |
| port | TCP port of the service to connect. |
| timeout | Timeout in milliseconds for Open, Read and Write. |
|
virtual |
| std::string ComSocket::GetAddress | ( | ) |
Get the IP address of the device to connect.
| unsigned int ComSocket::GetOpenTimeout | ( | ) |
Get the timeout time of the Open operations.
| unsigned int ComSocket::GetPort | ( | ) |
Get the TCP port of the service to connect.
| port | TCP port of the service to connect. |
|
virtual |
|
virtual |
|
virtual |
|
virtual |
Check if the interface is currently opened.
Implements ComInterface.
|
virtual |
Blocking read. It waits until the indicated number of bytes are received or the timeout expires.
| buffer_in | Buffer that will contain the received data. |
| len | Number of bytes to read. |
Implements ComInterface.
|
virtual |
Non blocking read. It tries to read the available bytes for the interface.
| buffer_in | Buffer that will contain the received data. |
| len | Number of bytes to read. |
Implements ComInterface.
| bool ComSocket::SetAddress | ( | const std::string & | address | ) |
Set the IP address of the device to connect.
| address | IP address of the device to connect. Example: "<IP_ADDRESS>". If set to "", the use mode is server. Else, client mode. |
| bool ComSocket::SetOpenTimeout | ( | unsigned int | open_timeout | ) |
Set the timeout time of the Open operations.
| open_timeout | Time in milliseconds. |
| bool ComSocket::SetPort | ( | unsigned int | port | ) |
Set the TCP port of the service to connect.
| port | TCP port of the service to connect. |
|
virtual |
Set the timeout time of the Read operations.
| read_timeout | Time in milliseconds. |
Implements ComInterface.
|
virtual |
Set the timeout time of the Write operations.
| write_timeout | Time in milliseconds. |
Implements ComInterface.
|
virtual |
Blocking write. It waits until the indicated number of bytes are transmitted or the timeout expires.
| buffer_out | Buffer that contains the data to be transmitted. |
| len | Number of bytes to write. |
Implements ComInterface.
|
virtual |
Non blocking write. It tries to write the the data passed to it.
| buffer_out | Buffer that contains the data to be transmitted. |
| len | Number of bytes to write. |
Implements ComInterface.


Click on the browser window or press the tab key to start the app.
Use mouse or arrow keys to control theremin.


@(page: model.Page, idRequest: services.IdentityRequest, idUrlBuilder: services.IdentityUrlBuilder)(implicit request: RequestHeader, context: model.ApplicationContext) @import views.html.fragments.registrationFooter
Follow the link in the email to reset your password.
Reset password links are valid for 30 minutes.


{% extends 'base/main.html' %} {% block content %}
We’ve emailed you instructions for setting your password, if an account exists with the email you entered. You should receive them shortly.
If you don’t receive an email, please make sure you’ve entered the address you registered with, and check your spam folder.
{% endblock content %}


Default Title
Create your own meals, plan your days, and monitor your nutrition.
Ingredients
Meals
Day Planner


<script src="RGraph.common.core.js"></script> <script src="RGraph.common.dynamic.js"></script> <script src="RGraph.common.tooltips.js"></script> <script src="RGraph.hbar.js"></script>Put this where you want the chart to show up:
<canvas id="cvs" width="350" height="176"> [No canvas support] </canvas>This is the code that generates the chart - it should be placed AFTER the canvas tag(s):


$35.99
Bring your meow friend to the mountain in this bright and light backpack! Waterproof material makes it perfect for all weather, and the holes on every face ensures that there’s always enough fresh air.
Blackberry
Crazy Berry
Fire Orange
Strawberry
Tiny
Small
Medium
Large
$35.99
$19.99
$19.99
$21.99
$23.99
$23.99


# `markdown-renderer`
A web-component to render markdown to html.
## Props
| name | type | default | required |
|---|---|---|---|
| children | Text Node | `✖` | yes
# Usage
Add `markdown-renderer` to your index.html.
```html
```
Use `markdown-renderer` in your project:
```html
# Wassap Mang?
_I woke up in a new Bugatti._
[Here](https://google.com) is a link.
```


Overview
A blocking queue is a queue that blocks when you try to dequeue from a empty queue, or if you try to enqueue items into a full queue.
Details
BlockingQueue doesn’t accept null values. Otherwise throw NullPointerException.
BlockingQueue implementations are thread-safe. All queuing methods are atomic in nature and use internal locks or other forms of concurrency control.
BlockingQueue interface is part of java collections framework and it’s primarily used for implementing producer consumer problem.
Two important methods:
put(E e): This method is used to insert elements to the queue, if the queue is full it waits for the space to be available.
E take(): This method retrieves and remove the element from the head of the queue, if queue is empty it waits for the element to be available.
Usage
BlockingQueue is typically used to have one thread produce objects, with another thread consumes (producer consumer problem). Refer to [Design] Producer Consumer Problem.
Example 1
This example shows how changing the speed of consuming and producing results in different sequence of outputs, using a BlockingQueue. The size of the BlockingQueue is initialized at 5.
public class Main {
// original post from:
// http://www.journaldev.com/1034/java-blockingqueue-example-implementing-producer-consumer-problem
private static final Setting testFullQueue = new Setting(3, 10, 0);
private static final Setting testEmptyQueue = new Setting(10, 3, 100);
public static void main(String[] args) {
// Creating BlockingQueue of size 5
BlockingQueue<Message> queue = new ArrayBlockingQueue<>(5);
Setting variableSetting = testFullQueue;
Producer producer = new Producer(queue, variableSetting.produceSpeed);
Consumer consumer = new Consumer(queue, variableSetting.consumeSpeed,
variableSetting.consumerDelay);
// starting producer to produce messages in queue
new Thread(producer).start();
// starting consumer to consume messages from queue
new Thread(consumer).start();
System.out.println("Producer and Consumer has been started");
}
static class Setting {
int produceSpeed;
int consumeSpeed;
int consumerDelay;
public Setting(int a, int b, int c) {
this.produceSpeed = a;
this.consumeSpeed = b;
this.consumerDelay = c;
}
}
}
Producer
public class Producer implements Runnable {
private BlockingQueue<Message> queue;
int produceSpeed;
public Producer(BlockingQueue<Message> q, int a) {
this.queue = q;
this.produceSpeed = a;
}
@Override
public void run() {
// produce messages
for (int i = 0; i < 13; i++) {
Message msg = new Message("" + i);
try {
Thread.sleep(produceSpeed);
queue.put(msg);
System.out.println("Produced " + msg.getMsg() + " ("
+ queue.size() + " items)");
} catch (InterruptedException e) {
e.printStackTrace();
}
}
// adding exit message
Message msg = new Message("exit");
try {
queue.put(msg);
} catch (InterruptedException e) {
e.printStackTrace();
}
}
}
Consumer
public class Consumer implements Runnable {
private BlockingQueue<Message> queue;
int consumeSpeed;
int consumerDelay;
public Consumer(BlockingQueue<Message> q, int a, int b) {
this.queue = q;
this.consumeSpeed = a;
this.consumerDelay = b;
}
@Override
public void run() {
try {
// initial delay: used to wait for producer to
// fill up the queue
Thread.sleep(consumerDelay);
Message msg;
// consuming messages until exit message is received
while ((msg = queue.take()).getMsg() != "exit") {
System.out.println(" " + msg.getMsg() + " Consumed"+ " ("
+ queue.size() + " items)");
Thread.sleep(consumeSpeed);
}
} catch (InterruptedException e) {
e.printStackTrace();
}
System.out.println("Consumer finished working. Exit. ");
}
}
Message Class
public class Message {
private String msg;
public Message(String str){
this.msg=str;
}
public String getMsg() {
return msg;
}
}
Output (testFullQueue):
Producer and Consumer has been started
Produced 0 (0 items)
0 Consumed (0 items)
Produced 1 (1 items)
Produced 2 (2 items)
1 Consumed (1 items)
Produced 3 (2 items)
Produced 4 (3 items)
Produced 5 (4 items)
2 Consumed (3 items)
Produced 6 (4 items)
Produced 7 (5 items)
3 Consumed (5 items)
Produced 8 (5 items)
4 Consumed (4 items)
Produced 9 (5 items)
5 Consumed (4 items)
Produced 10 (5 items)
6 Consumed (4 items)
Produced 11 (5 items)
7 Consumed (4 items)
Produced 12 (5 items)
8 Consumed (4 items)
9 Consumed (4 items)
10 Consumed (3 items)
11 Consumed (2 items)
12 Consumed (1 items)
Consumer finished working. Exit.
Output (testEmptyQueue):
Producer and Consumer has been started
Produced 0 (1 items)
Produced 1 (2 items)
Produced 2 (3 items)
Produced 3 (4 items)
Produced 4 (5 items)
Produced 5 (5 items)
0 Consumed (5 items)
1 Consumed (4 items)
2 Consumed (3 items)
Produced 6 (4 items)
3 Consumed (3 items)
4 Consumed (2 items)
Produced 7 (3 items)
5 Consumed (2 items)
6 Consumed (1 items)
7 Consumed (0 items)
Produced 8 (1 items)
8 Consumed (0 items)
Produced 9 (1 items)
9 Consumed (0 items)
Produced 10 (1 items)
10 Consumed (0 items)
Produced 11 (0 items)
11 Consumed (0 items)
Produced 12 (1 items)
12 Consumed (0 items)
Consumer finished working. Exit.


headers = resp.info()
// This capitalization was copied from the stdlib too
if "content-length" in headers:
size = int(headers["Content-Length"])
update_to(blocknum, bs, size)
while True:
with \
tqdm(unit="B", unit_scale=True, miniters=1, desc=path.name) as t, \
path.open("wb") as f, \
urlopen(Request(url, headers={"User-agent": "scanpy-user"})) as resp:
t.total = int(resp.info().get("content-length", 0))


Menlo Innovations
Senior Consultant
2021-Present
- Mentored a client team in iterative architecture as they successfully rebuilt an experimental system using Agile methodologies
- Simultaneously served as the anchor developer on several budget constrained projects. Worked closely with client stakeholders to find effective solutions to time sensitive customer needs.
Consultant
2016-2021
- Paired directly with client developers to teach process and skills while also successfully replacing a 40 year old legacy system which managed scheduling for a small inter-modal logistics company
- Worked increasingly in a leadership and mentorship capacity across numerous successful projects in a wide range of industries
- Scoped, estimated and wrote proposals during the pre-sales phase of projects
Associate Developer
2014-2016
- Writing test-driven software for numerous clients in a highly collaborative team
- Working directly with other roles (QA, High-tech Anthropologists, Project Managers, and Client Stake-holders) to understand requirements, diagnose problems, and prioritize tasks.
Direct Incorporation
Website Developer
May 2014-Oct 2014
- Maintained several LAMP-stack applications
- Administered several Linux servers providing email, web, and DNS services to several thousand clients
Ray Ontko & Co.
Intern
Summers, 2008 - 2010
- Created software which largely automated the formatting step for a profitable e-publishing project.


Here is the dataset I've got by crawling del.icio.us. Details follow.
First, I set up a script which reads del.icio.us' news feeds. The script run for about 1.5 months, gathering approx 1.3M tags. The problem with del.icio.us' news feeds is that they only contain data about the first time a user tags a document, so the majority of data is lost.
The second step was to take every single document in the downloaded data and simply download all its tags, along with the users who tagged it and the timestamps of the tagging event. This process took about a week using ten different machines.
| 1280686 | documents |
| 21408652 | total tags (16.7 tags per document on average) |
| 1205958 | unique tags |
| 491702 | users |
| 7034524 | tagging events |
A chart showing the distribution of number of tags per document:
The 30 most frequent tags:
| Frequency | Tag |
|---|---|
| 277414 | design |
| 195461 | blog |
| 147274 | tools |
| 135187 | inspiration |
| 129119 | imported |
| 124871 | tutorial |
| 124798 | programming |
| 122118 | art |
| 119211 | webdesign |
| 114229 | reference |
| 113939 | education |
| 113082 | software |
| 103713 | video |
| 94744 | web |
| 94365 | music |
| 92504 | photography |
| 83826 | development |
| 79686 | howto |
| 79615 | resources |
| 75723 | linux |
| 74114 | javascript |
| 69075 | free |
| 67085 | recipes |
| 66254 | via:packrati.us |
| 66108 | shopping |
| 63386 | business |
| 62953 | food |
| 62458 | research |
| 62145 | science |
| 60547 | technology |
A chart showing the raw frequency of tags. For readability the chart is cut, showing only frequencies >>2000.
<tags t="1229008773" u="gregloby" href="005cb474bfc10f41036b543f042ae791"> <t>jquery</t> <t>webdesign</t> <t>navigation</t> </tags>Every tags tag represent a tagging event: "a user has tagged a document with zero or more tags"*. The attributes of tags are:
| del.icio.us dataset (XML format, Bzipped) | 182.3 MB |
| del.icio.us dataset corpus (for Distributional Semantics, see below, Bzipped) | 53.2 MB |
Word Space Models were built from the del.icio.us dataset. The idea is treating the tags associated to a document as a document itself, made by just the (randomly ordered) list of tags. In this way a corpus of "documents" is created which can tehn be used for exploring aspects of the del.icio.us folksonomy using methods from NLP such as Distributional Semantics.
So far two models were build, namely a LSA model (100 dimensions) and a Random Indexing model (4000 dimensions). Both models were made with the Semantic Space package.
If you intend to use this data for research, please cite the following article:
Valerio Basile, Silvio Peroni, Fabio Tamburini, Fabio Vitali (2015)
Topical tags vs non-topical tags: Towards a bipartite classification?
Journal of Information Science.
@article{basile_topical_2015, title = {Topical tags vs non-topical tags: {Towards} a bipartite classification?}, volume = {41}, url = {http://dx.doi.org/10.1177/0165551515585283}, doi = {10.1177/0165551515585283}, number = {4}, journal = {J. Information Science}, author = {Basile, Valerio and Peroni, Silvio and Tamburini, Fabio and Vitali, Fabio}, year = {2015}, pages = {486--505}, file = {55a4f9eb08ae81aec91327f8.pdf:files/253/55a4f9eb08ae81aec91327f8.pdf:application/pdf} }


3D Object's Pokédex
with Pokémons' Demo and Trackball Controls
Made with
three.js
by
Rúben André Barreiro


README
ConnectionException
DarkSky
Alert
DataBlock
DataPoint
Flags
Forecast
Languages
Units
struct
DarkSky::DataBlock
DarkSky::DataBlock
Struct
Value
Object
Included Modules
JSON::Serializable
Defined in:
data_block.cr
Constructors
.new
(pull : JSON::PullParser)
Instance Method Summary
#data
: Array(DataPoint)?
#icon
: String?
#summary
: String?
Constructor Detail
def self.
new
(pull : JSON::PullParser)
#
[
View source
]
Instance Method Detail
def
data
: Array(
DataPoint
)?
#
[
View source
]
def
icon
: String?
#
[
View source
]
def
summary
: String?
#
[
View source
]


Advanced Visualization: Working with Annotations
This short protocol reviews how to add an manipulate annotations in Cytoscape.
Annotations in Cytoscape
Cytoscape has three separate drawing surfaces on which the network and annotations are drawn:
- Network canvas: where nodes and edges are drawn.
- Background canvas: the drawing surface behind nodes and edges.
- Foreground canvas: the drawing surface in front of nodes and edges.
Annotations are drawn either on the foreground or background canvases, and are exported as objects. They are high quality graphically, allowing for export of images. Annotation types:
- Shapes, Text, Bounded Text, Images and Arrows
- Groups, to group annotations together
Annotation Panel
The Annotation Panel is available in the Control Panel. In the below example, a label and corresponding arrow has been added to indicate that one of the nodes is mutated, and a rounded rectangle shape has been added to indicate a group, and a title has been added.
- To start, navigate to the Network Search at the top of the Network Panel, and select NDEx in the drop-down.
- Type in galFiltered and click the search icon. In the results, select the galFiltered.sif - STE12 subnetwork network and click the green arrow to open in Cytoscape.
Adding a Label Annotation
- To add a label annotation, click the Text button at the top of the Annotation panel.
- Click anywhere on the canvas to place the label, and in the Appearance interface, enter the desired label and select font and color.
- To adjust the location of the annotation, first click the Toggle Annotation Selection . The annotation can now be moved by click and drag.
Adding an Arrow Annotation
- To add an arrow annotation, click the Arrow button at the top of the Annotation panel.
- Instead of clicking on the canvas, first click the annotation you want the arrow to point from, in this case the label added previously.
- Next, click on the node or annotation you want to point the arrow to.
- In the Appearance tab of the Annotations Panel, select line color and arrow style and color. In this case, we will add a red line with a red t-bar end.
Adding a Shape Annotation
- To add a shape annotation, click the Shape button at the top of the Annotation panel.
- Click anywhere on the canvas to place the shape, and in the Appearance interface, select the desired shape, color etc.
- The new shape will automatically be selected, and you can now size it to your liking and then click on the canvas to set the size.
- By default the shape will be drawn on the foreground canvas, obstructing any nodes behind it. To move it to the background canvas, select the shape in the Layers tab in the Annotation panel and click the Push Annotations to Background Layer arrow just below the list.
Editing Annotations
When the Toggle Annotation Selection button is enabled, annotations can be selected and edited.
- Click on an annotation to bring activate the Appearance panel.
- To delete one or more annotations, select them in the Annotations Panel and click the delete button at the top. Alternatively, select them in the network and click Delete on the keyboard.
- As was described previously, annotations can also be moved between the background and foreground layer in the Layers tab in the Annotations Panel.
Rotating Annotations
Annotations can also be rotated:
- Select the shape annotation we added earlier.
- In the Appearance panel, drag the Rotation Angle to about -20. This will rotate the object 20 degrees counter-clockwise.
For more information on using annotations in network visualization, see the Ten Simple Rules protocol.


Home
TOP 10
Add Review
About
Contact Us
Admin
Profile
Logout
Welcome to
The Good Food Site
Login / Register
Forgot your password? click
here


| | |
- __builtin__.object
-
- Orbit
-
- MeanJ2
class MeanJ2(Orbit) |
| |
Implements propagation to evolve elements with mean J2 perturbations |
| |
- Method resolution order:
- MeanJ2
- Orbit
- __builtin__.object
Methods defined here:
- getAop(self, t_dt=None)
- Computes the AoP value of the object (in radians) at the given point
in time, as propagated by the orbit-averaged mean precession computed
in the *getAopRate* method.
- getAopRate(self)
- Computes and returns the rate at which the argument of perigee
processes, in radians per second, as a result of the non-spherical
Earth's J2 harmonic.
- getQpqw2eci(self, t_dt=None)
- Returns a time-varying tranformation matrix that converts vectors
from the PQW (co-orbital) frame to the earth-centered inertial (ECI)
frame (w.r.t. the J2000 epochal orientation). This includes the RAAN
precession and AoP procession rates induced by the J2 harmonic.
- getRaan(self, t_dt=None)
- Computes the RAAN value of the object (in radians) at the given point
in time, as propagated by the orbit-averaged mean precession computed
in the *getRaanRate* method.
- getRaanRate(self)
- Computes and returns the rate at which the right-ascension of the
ascending node precesses, in radians per second, as a result of the
non-spherical Earth's J2 harmonic.
- getReci(self, t_dt=None)
- Computes and returns the position of the object, in meters, as
evaluted in the earth-centered inertial (ECI) frame. This includes
the RAAN precession and ApP procession rates induced by J2 harmonic.
Class methods defined here:
- fromConstAop(cls, T_s) from __builtin__.type
- Determines an eccentric sun-synch orbit from the given period
- fromMolniya(cls, lon_rad) from __builtin__.type
- Returns a Molniya-style orbit designed to peak at the given longitude
(in radians). Inclined to match RAAN recession to solar orientation.
- fromSunSync(cls, T_s) from __builtin__.type
- Returns a new MeanJ2 orbit object scaled to a specific inclination
and altitude to achieve the given period, but with fixed RAAN
(inclined such that the orbital plane orientation w.r.t. the sun
remains constant).
- fromTundra(cls, lon_rad) from __builtin__.type
- According to some definitions, tundra orbits do not necessarily match
inclination to eliminate RAAN recession. QZSS, for example, targets
apogee dwell at a specific latitude. While technically not requiring
a J2 model, it is implemented here to support cases where the
inclination (at 63.4 degrees) is choosen to ensure a fixed track.
Methods inherited from Orbit:
- __init__(self, a_m=None, e=None, i_rad=None, O_rad=None, w_rad=None, M_rad=None, tEpoch_dt=None)
- Initializes a restricted two-body propagation model for a spherical
earth. Defaults to a circular GEO orbit with all angles set to 0.
(Epoch is set to the UTC time when the object is created.)
- __str__(self)
- Converts an Orbit object into a string representation (invoked by the
*str* and *print* functions) that references the shape (altitude at
perigee and apogee) and object location in memory.
- getAngMom(self)
- Returns the scalar angular momentum of the orbit, in m/s^2.
- getApogee(self)
- Returns the 3-component position vector of the object at apogee, in
meters and evaluated within the earth-centered inertial (ECI) frame.
- getAscNode(self)
- Returns the 3-component position vector of the object at the
ascending node, in meters and evaluated within the earth-centered
inertial (ECI) frame.
- getDescNode(self)
- Returns the 3-component position vector of the object at the
descending node, in meters and evaluated within the earth-centered
inertial (ECI) frame.
- getPerigee(self)
- Returns the 3-component position vector of the object at perigee, in
meters and evaluated within the earth-centered inertial (ECI) frame.
- getPeriod(self)
- Returns the period of the current orbit, in seconds.
- getRlla(self, t_dt=None)
- Computes and returns the position at the given datetime, in latitude,
longitude, and altitude (radians, radians, and meters, respectively).
- getRpqw(self, t_dt=None)
- Returns the 3-component position vector of the object at the given
datetime, as evaluted in the PQW (co-planar) frame.
- getShape(self)
- Returns a two-element tuple containing the altitude of the object at
perigee and apogee, in meters above spherical sea level.
- getShapeVel(self)
- Returns a two-element tuple containing the scalar velocity of the
object at perigee and apogee, in meters per second.
- getTaaRad(self)
- Returns the true-anomaly averaged radius (geometric mean of radius at
perigee and apogee), in meters.
- getTrue(self, t_dt=None)
- Returns the true anomaly of the object when propagated to a given
datetime.
- propagate(self, tEpoch_dt=None, T_s=None, nSamples=1000)
- Computes inertial position over the course of one orbit, beginning
with the given datetime (or, if not provided, the element epoch).
This defaults to 1,000 samples within that time range.
- setShape(self, hPer_m, hApo_m)
- Sets the a_m (semi-major axis) and e (eccentricity) values of an
orbit based on the given altitude (meters above spherical sea level)
at perigee and apogee.
- track(self, tEpoch_dt=None, T_s=None, nSamples=1000)
- Computes lat/lon/alt position over the course of one orbit, beginning
with the given datetime (or, if not provided, the element epoch).
This defaults to 1,000 samples within that time range.
Class methods inherited from Orbit:
- fromHTht(cls, h1_m, tht1_rad, h2_m, tht2_rad) from __builtin__.type
- Constructs an Orbit object based on the given altitude (meters above
spherical sea level) and true anomaly values (in radians).
- fromRV(cls, rEci_m, vEci_mps) from __builtin__.type
- Constructs an Orbit object from the given position (meters) and
velocity (meters-per-second) state vectors, as evaluated in the
earth-centered inertial (ECI) frame.
- fromTle(cls, line1, line2) from __builtin__.type
- Constructs an Orbit object from the given two strings, as formatted
by the TLE (two-line element) specification (one string per line).
Data descriptors inherited from Orbit:
- __dict__
- dictionary for instance variables (if defined)
- __weakref__
- list of weak references to the object (if defined)
|
class Orbit(__builtin__.object) |
| |
Restricted two-body propagation model |
| |
Methods defined here:
- __init__(self, a_m=None, e=None, i_rad=None, O_rad=None, w_rad=None, M_rad=None, tEpoch_dt=None)
- Initializes a restricted two-body propagation model for a spherical
earth. Defaults to a circular GEO orbit with all angles set to 0.
(Epoch is set to the UTC time when the object is created.)
- __str__(self)
- Converts an Orbit object into a string representation (invoked by the
*str* and *print* functions) that references the shape (altitude at
perigee and apogee) and object location in memory.
- getAngMom(self)
- Returns the scalar angular momentum of the orbit, in m/s^2.
- getApogee(self)
- Returns the 3-component position vector of the object at apogee, in
meters and evaluated within the earth-centered inertial (ECI) frame.
- getAscNode(self)
- Returns the 3-component position vector of the object at the
ascending node, in meters and evaluated within the earth-centered
inertial (ECI) frame.
- getDescNode(self)
- Returns the 3-component position vector of the object at the
descending node, in meters and evaluated within the earth-centered
inertial (ECI) frame.
- getPerigee(self)
- Returns the 3-component position vector of the object at perigee, in
meters and evaluated within the earth-centered inertial (ECI) frame.
- getPeriod(self)
- Returns the period of the current orbit, in seconds.
- getQpqw2eci(self)
- Returns the frame transformation matrix from the PQW (co-planar)
frame to the earth-centered inertial (ECI) frame, w.r.t. J2000.
- getReci(self, t_dt=None)
- Returns the position of the object at the given point in time, as
evaluated within the earth-centered inertial (ECI) frame, in meters.
- getRlla(self, t_dt=None)
- Computes and returns the position at the given datetime, in latitude,
longitude, and altitude (radians, radians, and meters, respectively).
- getRpqw(self, t_dt=None)
- Returns the 3-component position vector of the object at the given
datetime, as evaluted in the PQW (co-planar) frame.
- getShape(self)
- Returns a two-element tuple containing the altitude of the object at
perigee and apogee, in meters above spherical sea level.
- getShapeVel(self)
- Returns a two-element tuple containing the scalar velocity of the
object at perigee and apogee, in meters per second.
- getTaaRad(self)
- Returns the true-anomaly averaged radius (geometric mean of radius at
perigee and apogee), in meters.
- getTrue(self, t_dt=None)
- Returns the true anomaly of the object when propagated to a given
datetime.
- propagate(self, tEpoch_dt=None, T_s=None, nSamples=1000)
- Computes inertial position over the course of one orbit, beginning
with the given datetime (or, if not provided, the element epoch).
This defaults to 1,000 samples within that time range.
- setShape(self, hPer_m, hApo_m)
- Sets the a_m (semi-major axis) and e (eccentricity) values of an
orbit based on the given altitude (meters above spherical sea level)
at perigee and apogee.
- track(self, tEpoch_dt=None, T_s=None, nSamples=1000)
- Computes lat/lon/alt position over the course of one orbit, beginning
with the given datetime (or, if not provided, the element epoch).
This defaults to 1,000 samples within that time range.
Class methods defined here:
- fromHTht(cls, h1_m, tht1_rad, h2_m, tht2_rad) from __builtin__.type
- Constructs an Orbit object based on the given altitude (meters above
spherical sea level) and true anomaly values (in radians).
- fromRV(cls, rEci_m, vEci_mps) from __builtin__.type
- Constructs an Orbit object from the given position (meters) and
velocity (meters-per-second) state vectors, as evaluated in the
earth-centered inertial (ECI) frame.
- fromTle(cls, line1, line2) from __builtin__.type
- Constructs an Orbit object from the given two strings, as formatted
by the TLE (two-line element) specification (one string per line).
Data descriptors defined here:
- __dict__
- dictionary for instance variables (if defined)
- __weakref__
- list of weak references to the object (if defined)
| |


{{site.user_description}}
Javascript | React & Redux | ExpressJS | NodeJS | Python | Flask | PostgreSQL
Experience with modern front end frameworks including React Hooks, React Native, and Redux, as well as extensive work in styling and state management
Built APIs using both Flask and Express, with strong knowledge in server-side routing, maintanence, and authentication
Practiced source control workflow and well-versed in PostgreSQL (along with its requsite ORMs) and deployment using Docker


Rest.li 2.0 introduces a new backwards incompatible URI format, as well as removes several APIs that have been marked as deprecated for quite some time. You can find details about these changes on our user guide as well as our protocol documentation. This page documents the steps needed to upgrade from a 1.x release to a 2.x release.
Having issues with any of the steps listed below? Please create an issue and someone from the Rest.li team will help you.
Take these steps to make your source code compatible with Rest.li 2.x:
-Xlint:deprecation
flag when using javac
.com.linkedin.restli.client.BatchRequest#getIdObjects
. If you look at the Javadoc for this method we have instructions on what to use instead.For the most part the protocol changes are taken care off under the hood by Rest.li. As an application developer, you don’t have to worry about the Rest.li 2.0 protocol changes.
However, if you are hard coding URLs, HTTP request/response bodies, or HTTP request/response headers in your code you will have to update these to the Rest.li 2.0 protocol format. Details of the protocol can be found on this page.
The basic rules for upgrading and deploying your clients and servers is as follows:
If you have a complicated Rest.li call graph involving multiple Rest.li services, start the upgrade and deployment process at the leaf nodes of the graph (i.e. the Rest.li services that don’t call other Rest.li services) and work your way backwards.


Here’s all the known subjects in the messaging service.
Topic name | Meaning | To… | Data schema |
|---|---|---|---|
| The queue has changed in the Arena service. | N/A | { "event": string, "gameType": IGameType, "queue": int } |
| A change occured in a game instance. | N/A | { "event": string, "gameType": IGameType, "gameId": int } |
| Someone joined the queue. | All subscribers | { IQueueInstance } |
| Someone leaved the queue. | All subscribers | { IQueueInstance } |
| A game was created | The players in the game instance | { "gameId": int, "gameType": IGameType } |
| An action was updated | All subscribers | { IGameAction } |
| A card changed in a game instance | All subscribers | { "changes": { [key]: [change value] }, "gameCard": IGameCard } |
| A message was posted in a room | The senders in the room | { IPublicMessage } |
| The account was updated | The user of the account | { IWizard } |
| Someone killed Nantusuelta | All subscribers | { "user": int } |
| Someone killed the Mossy Source | All subscribers | { "user": int } |
| Someone killed the Monarch | All subscribers | { "user": int } |


SFPSDWriter Class Reference
| Inherits from | NSObject |
| Declared in | SFPSDWriter.h SFPSDWriter.m |
Tasks
Other Methods
-
flattenedContext
Context used to hold the flattened image for the PSD preview
property -
layers
The PSDLayer objects with layer data, names, etc… Note that when you call createPSDData, this array is slowly emptied – the PSDWriter removes the individual layers from memory as it builds the PSD file.
property -
documentSize
The size of the PSD you’re exporting.
property -
documentResolution
The pixel per inch property of the resulting document. It is a SFPSDResolution because the document can have different vertical and horizontal resolutions
property -
documentResolutionUnit
The unit of the document resolution.
property -
colorProfile
The embedded color profile of the document.
property -
hasTransparentLayers
The number of channels in each layer. Defaults to 4, unless layers are not transparent. This is the global
property -
flattenedData
Optional. The RGBA data for a flattened “preview” of the PSD.
property -
– initWithDocumentSize:
Initializes a new PSDWriter for creating a PSD document with the specified size.
-
– initWithDocumentSize:andResolution:andResolutionUnit:
Initializes a new PSDWriter for creating a PSD document with the specified size and resolution value.
-
– initWithDocumentSize:andResolution:andResolutionUnit:andHasTransparentLayers:andLayers:
Designed initializer.
-
– addLayerWithCGImage:andName:
Adds a new layer to the PSD image with a name. The opacity of the layer will be 1 and no offset will be applied.
-
– addLayerWithCGImage:andName:andOpacity:andOffset:
Adds a new layer to the PSD image with the provided properties.
-
– openGroupLayerWithName:
Opens a new PSD group.
-
– openGroupLayerWithName:andOpacity:andIsOpened:
Opens a new PSD group.
-
– closeCurrentGroupLayer
Closes the corresponding opened PSD group without returning errors. The function will simply return nil if there is no opened group to close.
-
– closeCurrentGroupLayerWithError:
Closes the corresponding opened PSD group.
-
– numberOfChannels
The number of channels of the PSD document. If it has transparencies – 4, else 3.
-
– visibleLayers
An array with only visible layers inside the document bounds.
-
– createPSDData
Deprecated function. Use createPSDDataWithError: instead
-
– createPSDDataWithError:
Generates an NSData object representing a PSD image with the width and height specified by documentSize and the contents specified by the layers array. Note that this function can be (and really should be) called on a separate thread.
Other Methods
-
– init
-
– initWithDocumentSize:andHasTransparentLayers:andLayers:
-
– dealloc
-
– resetFlattenedContext
-
– addLayerToFlattenedContext:error:
-
– preprocess
-
– writeFileHeaderSectionOn:
-
– writeColorModeDataSectionOn:
-
– writeImageResourceSectionOn:
-
– writeLayerAndMaskInformationSectionOn:
-
– writeImageDataSectionOn:
Properties
colorProfile
The embedded color profile of the document.
@property (nonatomic, assign) SFPSDColorProfile colorProfile
Discussion
The embedded color profile of the document.
Declared In
SFPSDWriter.h
documentResolution
The pixel per inch property of the resulting document. It is a SFPSDResolution because the document can have different vertical and horizontal resolutions
@property (nonatomic, assign) SFPSDResolution documentResolution
Discussion
The pixel per inch property of the resulting document. It is a SFPSDResolution because the document can have different vertical and horizontal resolutions
Declared In
SFPSDWriter.h
documentResolutionUnit
The unit of the document resolution.
@property (nonatomic, assign) SFPSDResolutionUnit documentResolutionUnit
Discussion
The unit of the document resolution.
Declared In
SFPSDWriter.h
documentSize
The size of the PSD you’re exporting.
@property (nonatomic, assign) CGSize documentSize
Discussion
The size of the PSD you’re exporting.
Declared In
SFPSDWriter.h
flattenedContext
Context used to hold the flattened image for the PSD preview
@property (nonatomic, assign) CGContextRef flattenedContext
Discussion
Context used to hold the flattened image for the PSD preview
Declared In
SFPSDWriter.h
flattenedData
Optional. The RGBA data for a flattened “preview” of the PSD.
@property (nonatomic, strong) NSData *flattenedData
Discussion
Optional. The RGBA data for a flattened “preview” of the PSD.
Declared In
SFPSDWriter.h
hasTransparentLayers
The number of channels in each layer. Defaults to 4, unless layers are not transparent. This is the global
@property (nonatomic, assign) BOOL hasTransparentLayers
Discussion
The number of channels in each layer. Defaults to 4, unless layers are not transparent. This is the global
Declared In
SFPSDWriter.h
layers
The PSDLayer objects with layer data, names, etc… Note that when you call createPSDData, this array is slowly emptied – the PSDWriter removes the individual layers from memory as it builds the PSD file.
@property (nonatomic, strong) NSMutableArray *layers
Discussion
The PSDLayer objects with layer data, names, etc… Note that when you call createPSDData, this array is slowly emptied – the PSDWriter removes the individual layers from memory as it builds the PSD file.
Declared In
SFPSDWriter.h
Instance Methods
addLayerToFlattenedContext:error:
- (BOOL)addLayerToFlattenedContext:(SFPSDLayer *)layer error:(NSError *__autoreleasing *)error
addLayerWithCGImage:andName:
Adds a new layer to the PSD image with a name. The opacity of the layer will be 1 and no offset will be applied.
- (SFPSDLayer *)addLayerWithCGImage:(CGImageRef)image andName:(NSString *)name
Parameters
- image
The image to be added. Does not need to be the same size as the document. If the image is larger than the document it will be cropped in the final result.
- name
The name you’d like to give the layer.
Return Value
The newly created layer in order to customize it after the creation.
Discussion
Adds a new layer to the PSD image with a name. The opacity of the layer will be 1 and no offset will be applied.
Declared In
SFPSDWriter.h
addLayerWithCGImage:andName:andOpacity:andOffset:
Adds a new layer to the PSD image with the provided properties.
- (SFPSDLayer *)addLayerWithCGImage:(CGImageRef)image andName:(NSString *)name andOpacity:(float)opacity andOffset:(CGPoint)offset
Parameters
- image
The image to be added. Does not need to be the same size as the document. If the image is larger than the document it will be cropped.
- name
The name you’d like to give the layer.
- opacity
The opacity of the layer, from [0-1]
- offset
The offset of the layer within the document. Use this to position layers within the PSD.
Return Value
The newly created layer in order to customize it after the creation.
Discussion
Adds a new layer to the PSD image with the provided properties.
If you are using NSImages and not CGImages, use the following code to convert to CGImageRefs:
NSImage* yourImage; CGImageSourceRef source = CGImageSourceCreateWithData((CFDataRef)[yourImage TIFFRepresentation], NULL); CGImageRef imageRef = CGImageSourceCreateImageAtIndex(source, 0, NULL);
If you prefer, you can setup PSDLayers by yourself and put them in the PSDWriter.layers array, but this method automatically creates the flattenedData, an image that is a flattened preview of the layered PSD. If you populate the layer objects yourself, you need to provide the flattened image data yourself.
Note: Having layers partially off the edge of the canvas is not currently supported.
Declared In
SFPSDWriter.h
closeCurrentGroupLayer
Closes the corresponding opened PSD group without returning errors. The function will simply return nil if there is no opened group to close.
- (SFPSDGroupClosingLayer *)closeCurrentGroupLayer
Discussion
Closes the corresponding opened PSD group without returning errors. The function will simply return nil if there is no opened group to close.
Declared In
SFPSDWriter.h
closeCurrentGroupLayerWithError:
Closes the corresponding opened PSD group.
- (SFPSDGroupClosingLayer *)closeCurrentGroupLayerWithError:(NSError *__autoreleasing *)error
Return Value
The newly created group layer in order to customize it after the creation.
Discussion
Closes the corresponding opened PSD group.
The layer will have the name and other data of the SFPSDGroupOpeningLayer that it is closing
Declared In
SFPSDWriter.h
createPSDData
Deprecated function. Use createPSDDataWithError: instead
- (NSData *)createPSDData
Discussion
Deprecated function. Use createPSDDataWithError: instead
Declared In
SFPSDWriter.h
createPSDDataWithError:
Generates an NSData object representing a PSD image with the width and height specified by documentSize and the contents specified by the layers array. Note that this function can be (and really should be) called on a separate thread.
- (NSData *)createPSDDataWithError:(NSError *__autoreleasing *)error
Return Value
PSD data. This data has to be written on a file.
Discussion
Generates an NSData object representing a PSD image with the width and height specified by documentSize and the contents specified by the layers array. Note that this function can be (and really should be) called on a separate thread.
Declared In
SFPSDWriter.h
initWithDocumentSize:
Initializes a new PSDWriter for creating a PSD document with the specified size.
- (id)initWithDocumentSize:(CGSize)documentSize
Parameters
- size
The document size.
Discussion
Initializes a new PSDWriter for creating a PSD document with the specified size.
Declared In
SFPSDWriter.h
initWithDocumentSize:andHasTransparentLayers:andLayers:
- (id)initWithDocumentSize:(CGSize)documentSize andHasTransparentLayers:(BOOL)hasTransparentLayers andLayers:(NSArray *)layers
initWithDocumentSize:andResolution:andResolutionUnit:
Initializes a new PSDWriter for creating a PSD document with the specified size and resolution value.
- (id)initWithDocumentSize:(CGSize)documentSize andResolution:(float)resolution andResolutionUnit:(SFPSDResolutionUnit)resolutionUnit
Parameters
- documentSize
The document size.
- resolution
The resolution value of the document.
Discussion
Initializes a new PSDWriter for creating a PSD document with the specified size and resolution value.
Declared In
SFPSDWriter.h
initWithDocumentSize:andResolution:andResolutionUnit:andHasTransparentLayers:andLayers:
Designed initializer.
- (id)initWithDocumentSize:(CGSize)documentSize andResolution:(float)resolution andResolutionUnit:(SFPSDResolutionUnit)resolutionUnit andHasTransparentLayers:(BOOL)hasTransparentLayers andLayers:(NSArray *)layers
Parameters
- documentSize
document size.
- resolution
The resolution value of the document.
- resolutionUnit
The unit of the document resolution.
- hasTransparentLayers
tells if the layer has the alpha channel.
- layers
Initial layers.
Discussion
Designed initializer.
Declared In
SFPSDWriter.h
numberOfChannels
The number of channels of the PSD document. If it has transparencies – 4, else 3.
- (int)numberOfChannels
Discussion
The number of channels of the PSD document. If it has transparencies – 4, else 3.
Declared In
SFPSDWriter.h
openGroupLayerWithName:
Opens a new PSD group.
- (SFPSDGroupOpeningLayer *)openGroupLayerWithName:(NSString *)name
Parameters
- name
The name of the group
Return Value
The newly created Group in order to customize it after the creation.
Discussion
Opens a new PSD group.
The group will contain all the layers and groups added to the PSDWriter’s instance before the corresponding closeCurrentGroupLayer is called
Declared In
SFPSDWriter.h
openGroupLayerWithName:andOpacity:andIsOpened:
Opens a new PSD group.
- (SFPSDGroupOpeningLayer *)openGroupLayerWithName:(NSString *)name andOpacity:(float)opacity andIsOpened:(BOOL)isOpened
Parameters
- name
The name of the group
- opacity
The opacity of the group
- isOpened
If the group should be opened inside the PSD
Return Value
The newly created Group in order to customize it after the creation.
Discussion
Opens a new PSD group.
The group will contain all the layers and groups added to the PSDWriter’s instance before the corresponding closeCurrentGroupLayer is called
Declared In
SFPSDWriter.h


HttpBodyHandler class
HttpBodyHandler is a helper class for processing and collecting
HTTP message data in an easy-to-use HttpBody object. The content
body is parsed, depending on the Content-Type
header field. When
the full body is read and parsed the body content is made
available. The class can be used to process both server requests
and client responses.
The following content types are recognized:
text/ *
application/json
application/x-www-form-urlencoded
multipart/form-data
For content type text/\*
the body is decoded into a string. The
'charset' parameter of the content type specifies the encoding
used for decoding. If no 'charset' is present the default encoding
of ISO-8859-1 is used.
For content type application/json
the body is decoded into a
string which is then parsed as JSON. The resulting body is a
Map. The 'charset' parameter of the content type specifies the
encoding used for decoding. If no 'charset' is present the default
encoding of UTF-8 is used.
For content type application/x-www-form-urlencoded
the body is a
query string which is then split according to the rules for
splitting a query string. The resulting body is a Map<String,
String>
. If the same name is present several times in the query
string, then the last value seen for this name will be in the
resulting map. The encoding US-ASCII is always used for decoding
the body.
For content type multipart/form-data
the body is parsed into
it's different fields. The resulting body is a Map<String,
dynamic>
, where the value is a String for normal fields and a
HttpBodyFileUpload instance for file upload fields. If the same
name is present several times, then the last value seen for this
name will be in the resulting map.
When using content type multipart/form-data
the encoding of
fields with String values is determined by the browser sending
the HTTP request with the form data. The encoding is specified
either by the attribute accept-charset
on the HTML form, or by
the content type of the web page containing the form. If the HTML
form has an accept-charset
attribute the browser will use the
encoding specified there. If the HTML form has no accept-charset
attribute the browser determines the encoding from the content
type of the web page containing the form. Using a content type of
text/html; charset=utf-8
for the page and setting
accept-charset
on the HTML form to utf-8
is recommended as the
default for HttpBodyHandler is UTF-8. It is important to get
these encoding values right, as the actual multipart/form-data
HTTP request sent by the browser does not contain any
information on the encoding. If something else than UTF-8 is used
defaultEncoding
needs to be set in the HttpBodyHandler
constructor and calls to processRequest and processResponse.
For all other content types the body will be treated as
uninterpreted binary data. The resulting body will be of type
List<int>
.
To use with the HttpServer for request messages, HttpBodyHandler can be used as either a StreamTransformer or as a per-request handler (see processRequest).
HttpServer server = ...
server.transform(new HttpBodyHandler())
.listen((HttpRequestBody body) {
...
});
To use with the HttpClient for response messages, HttpBodyHandler can be used as a per-request handler (see processResponse).
HttpClient client = ...
client.get(...)
.then((HttpClientRequest response) => response.close())
.then(HttpBodyHandler.processResponse)
.then((HttpClientResponseBody body) {
...
});
Implements
StreamTransformer<HttpRequest, HttpRequestBody>
Static Methods
Future<HttpRequestBody> processRequest(HttpRequest request, {Encoding defaultEncoding: UTF8}) #
Process and parse an incoming HttpRequest. The returned HttpRequestBody
contains a response
field for accessing the HttpResponse.
See HttpBodyHandler constructor for more info on defaultEncoding.
Future<HttpClientResponseBody> processResponse(HttpClientResponse response, {Encoding defaultEncoding: UTF8}) #
Process and parse an incoming HttpClientResponse.
See HttpBodyHandler constructor for more info on defaultEncoding.
Constructors
new HttpBodyHandler({Encoding defaultEncoding: UTF8}) #
Create a new HttpBodyHandler to be used with a Stream<HttpRequest>, e.g. a HttpServer.
If the page is served using different encoding than UTF-8, set
defaultEncoding accordingly. This is required for parsing
multipart/form-data
content correctly. See the class comment
for more information on multipart/form-data
.


Old Growth at Mount Hood National Forest
Mature forests 80-120 years of age
Old-Growth Forests 120+ years of age
March 2017 -
OWL Prototype
- Data Source:
Oregon Wild


Documentation builders#
This module is the starting point for building documentation, and is
responsible to figure out what to build and with which options. The actual
documentation build for each individual document is then done in a subprocess
call to Sphinx, see builder_helper()
. Note that
The builders are configured with
build_options.py
;The Sphinx subprocesses are configured in
conf.py
.
DocBuilder
is the base class of all Builders. It has builder helpers
html()
, latex()
, pdf()
, inventory()
, etc, which are
invoked depending on the output type. Each type corresponds with the Sphinx
builder format, except that pdf
is Sphinx latex builder plus compiling
latex to pdf. Note that Sphinx inventory builder is not native to Sphinx
but provided by Sage. See sage_docbuild/ext/inventory_builder.py
. The
Sphinx inventory builder is a dummy builder with no actual output but produces
doctree files in local/share/doctree
and inventory.inv
inventory files
in local/share/inventory
.
The reference manual is built in two passes, first by ReferenceBuilder
with inventory
output type and secondly with``html`` output type. The
ReferenceBuilder
itself uses ReferenceTopBuilder
and
ReferenceSubBuilder
to build subcomponents of the reference manual.
The ReferenceSubBuilder
examines the modules included in the
subcomponent by comparing the modification times of the module files with the
times saved in local/share/doctree/reference.pickle
from the previous
build. Then new rst files are generated for new and updated modules. See
get_new_and_updated_modules()
.
After github issue #31948, when Sage is built, ReferenceBuilder
is not used
and its responsibility is now taken by the Makefile
in $SAGE_ROOT/src/doc
.
- class sage_docbuild.builders.AllBuilder#
Bases:
object
A class used to build all of the documentation.
- get_all_documents()#
Return a list of all of the documents.
A document is a directory within one of the language subdirectories of SAGE_DOC_SRC specified by the global LANGUAGES variable.
EXAMPLES:
sage: from sage_docbuild.builders import AllBuilder sage: documents = AllBuilder().get_all_documents() sage: 'en/tutorial' in documents # optional - sage_spkg True sage: documents[0] == 'en/reference' True
- class sage_docbuild.builders.DocBuilder(name, lang='en')#
Bases:
object
INPUT:
name
- the name of a subdirectory in SAGE_DOC_SRC, such as ‘tutorial’ or ‘bordeaux_2008’lang
- (default “en”) the language of the document.
- changes(*args, **kwds)#
- clean(*args)#
- html(*args, **kwds)#
- htmlhelp(*args, **kwds)#
- inventory(*args, **kwds)#
- json(*args, **kwds)#
- latex(*args, **kwds)#
- linkcheck(*args, **kwds)#
- pdf()#
Build the PDF files for this document.
This is done by first (re)-building the LaTeX output, going into that LaTeX directory, and running ‘make all-pdf’ there.
EXAMPLES:
sage: from sage_docbuild.builders import DocBuilder sage: b = DocBuilder('tutorial') sage: b.pdf() #not tested
- pickle(*args, **kwds)#
- web(*args, **kwds)#
- class sage_docbuild.builders.ReferenceBuilder(name, lang='en')#
Bases:
AllBuilder
This class builds the reference manual. It uses DocBuilder to build the top-level page and ReferenceSubBuilder for each sub-component.
- get_all_documents(refdir)#
Return a list of all reference manual components to build.
We add a component name if it’s a subdirectory of the manual’s directory and contains a file named ‘index.rst’.
We return the largest component (most subdirectory entries) first since they will take the longest to build.
EXAMPLES:
sage: from sage_docbuild.builders import ReferenceBuilder sage: b = ReferenceBuilder('reference') sage: refdir = os.path.join(os.environ['SAGE_DOC_SRC'], 'en', b.name) # optional - sage_spkg sage: sorted(b.get_all_documents(refdir)) # optional - sage_spkg ['reference/algebras', 'reference/arithgroup', ..., 'reference/valuations']
- class sage_docbuild.builders.ReferenceSubBuilder(*args, **kwds)#
Bases:
DocBuilder
This class builds sub-components of the reference manual. It is responsible for making sure that the auto generated reST files for the Sage library are up to date.
When building any output, we must first go through and check to see if we need to update any of the autogenerated reST files. There are two cases where this would happen:
A new module gets added to one of the toctrees.
The actual module gets updated and possibly contains a new title.
- auto_rest_filename(module_name)#
Return the name of the file associated to a given module
EXAMPLES:
sage: from sage_docbuild.builders import ReferenceSubBuilder sage: ReferenceSubBuilder("reference").auto_rest_filename("sage.combinat.partition") '.../en/reference/sage/combinat/partition.rst'
- cache_filename()#
Return the filename where the pickle of the reference cache is stored.
- clean_auto()#
Remove all autogenerated reST files.
- get_all_included_modules()#
Return an iterator for all modules which are included in the reference manual.
- get_all_rst_files(exclude_sage=True)#
Return an iterator for all rst files which are not autogenerated.
- get_cache()#
Retrieve the reference cache which contains the options previously used by the reference builder.
If it doesn’t exist, then we just return an empty dictionary. If it is corrupted, return an empty dictionary.
- get_modified_modules()#
Return an iterator for all the modules that have been modified since the documentation was last built.
- get_module_docstring_title(module_name)#
Return the title of the module from its docstring.
- get_modules(filename)#
Given a filename for a reST file, return an iterator for all of the autogenerated reST files that it includes.
- get_new_and_updated_modules()#
Return an iterator for all new and updated modules that appear in the toctrees, and remove obsolete old modules.
- get_sphinx_environment()#
Return the Sphinx environment for this project.
- get_unincluded_modules()#
Return an iterator for all the modules in the Sage library which are not included in the reference manual.
- print_included_modules()#
Print all of the modules that are included in the Sage reference manual.
- print_modified_modules()#
Print a list of all the modules that have been modified since the documentation was last built.
- print_new_and_updated_modules()#
Print all the modules that appear in the toctrees that are newly included or updated.
- print_unincluded_modules()#
Print all of the modules which are not included in the Sage reference manual.
- save_cache()#
Pickle the current reference cache for later retrieval.
- update_mtimes()#
Update the modification times for reST files in the Sphinx environment for this project.
- write_auto_rest_file(module_name)#
Write the autogenerated reST file for module_name.
- class sage_docbuild.builders.ReferenceTopBuilder(*args, **kwds)#
Bases:
DocBuilder
This class builds the top-level page of the reference manual.
- pdf()#
Build top-level document.
- class sage_docbuild.builders.SingleFileBuilder(path)#
Bases:
DocBuilder
This is the class used to build the documentation for a single user-specified file. If the file is called ‘foo.py’, then the documentation is built in
DIR/foo/
if the user passes the command line option “-o DIR”, or inDOT_SAGE/docbuild/foo/
otherwise.
- class sage_docbuild.builders.WebsiteBuilder(name, lang='en')#
Bases:
DocBuilder
- clean()#
When we clean the output for the website index, we need to remove all of the HTML that were placed in the parent directory.
In addition, remove the index file installed into the root doc directory.
- html()#
After we have finished building the website index page, we copy everything one directory up.
In addition, an index file is installed into the root doc directory.
- sage_docbuild.builders.build_many(target, args, processes=None)#
Thin wrapper around \(sage_docbuild.utils.build_many\) which uses the docbuild settings
NUM_THREADS
andABORT_ON_ERROR
.
- sage_docbuild.builders.build_other_doc(args)#
- sage_docbuild.builders.build_ref_doc(args)#
- sage_docbuild.builders.builder_helper(type)#
Return a function which builds the documentation for output type
type
.
- sage_docbuild.builders.get_builder(name)#
Return an appropriate Builder object for the document
name
.DocBuilder and its subclasses do all the real work in building the documentation.
- sage_docbuild.builders.get_documents()#
Return a list of document names the Sage documentation builder will accept as command-line arguments.


Experience
{{ job.company }}
{{ job.position }} • {{ job.duration }}
{{ job.summary }}
Education
{{ education.uni }}
{{ education.degree }} • {{ education.year }}
-
{% for award in education.awards %}
- {{ award.award }} {% endfor %}
Skills
{{ skill.skill }}
{{ skill.description }}
Recognition
{{ recognition.award }}
{{ recognition.organization }} • {{ recognition.year }}
{{ recognition.summary }}
Certifications
Outside Interests
-
{% for interest in site.data.interests %}
- {{ interest.description }} {% endfor %}
Associations
{% if association.url %}{{ association.organization }}{% else %}{{ association.organization }}{% endif %}
{{ association.role }} • {{ association.year }}
{{ association.summary }}
Additional Links
-
{% for link in site.data.links %}
- {{ link.description }} {% endfor %}


Ptolemy II includes a number of utilities for constructing user interfaces for models. Some of these are represented by actors, while others are utilities for constructing applets or applications.


{% extends "base.html" %} {% load widget_tweaks comments scribbler_tags %} {% block title %}Submit Data{% endblock title %} {% block body_id %}resource-detail{% endblock body_id %} {% block body_class %}catalog{% endblock body_class %} {% block extra-meta %} {% endblock %} {% block content %}
We realize that we haven't listed every North Carolina-based government data set in the Open N.C. catalog. If you have a specific data set that you've found and would like to share, let us know by completing and submitting the form below. We'll review the information and determine whether the data set should be included in Open N.C.. The data must be specific to North Carolina, available online, and contain information in columns and rows. Our goal is to catalog government datasets that adhere as closely as possible to the 8 Principles of Open Government Data. A full list of review criteria is available on the FAQ page.
This form is for recommending specific data sets, applications, or APIs. If you'd like to nominate a general area where you think data should be more easily available, visit the Request Data page.
If the data is not already online, there are several ways you can help put it online. Remember, though, that the more disconnected data becomes from its original source the less it adheres to the 8 Principles of Open Government Data. Data sets that aren't as close to the source as possible and for which the acquisition and publication processes aren't transparent will not be included in the catalog.
{% endscribble %}Ideally, the data you want to share is already public on a government website. If it is, please post here the URL that points directly to the dataset.
{% endscribble %}


UNESCO's World Heritage List can be seen as a celebration of both the greatness of nature and the
greatness of culture. The list
acknowledges humankind's
capacity to feel awed by the beauty and
power of the "wonders" of nature; similarly, it acknowledges humankind's ability to create its
own
great structures by recombining elements of the natural world in unique
ways.
The UNESCO World Heritage List was established to preserve the great structures of all the
diverse
cultures of the world. From this point of view, such structures are not treasures of particular
nations only, but are the heritage of all humankind. Thus, the concept of the cultural and
natural
wonders as "world heritage" was born. In 1972, the UNESCO World Heritage List was
established,
since, in the words of the General Assembly Resolution,
At this writing, over 1121 properties are on UNESCO's list: 869 cultural, 213 natural, and 39 mixed
properties. The cultural sites include the Great Wall of China, the historic district of Quebec in
Canada, the Pyramids of Egypt, Mont-Saint Michel and its bay in France, Monticello and the
University of Virginia in Charlottesville in the United States.
According to Article 1 of the World Heritage Convention, cultural heritage properties must fall into one of these categories:
According to Article 2 of the World Heritage Convention, natural heritage properties must fall into one of these categories:
(Source)
Such examples are the Great Barrier Reef of Australia, the Galapagos Islands of Ecuador, Mount Nimba
Strict Nature Reserve of Guinea and Cote d'Ivoire, the Caves of Aggtelek and Slovak Karst in Hungary
and Slovakia, and the Grand Canyon in the United States. World Heritage sites receive international
assistance so that they may be maintained and preserved for all humankind.


[viewBag] title = "1Bet" url = "/partners/1bet" layout = "partner" is_hidden = 1 navigation_hidden = 1 previevImg = "/1bet.jpg" previevText = "1Bet are now a leading online sportsbook. They are very similar to IBC (Maxbet) in their look and feel and also settle bets at a partial amount of 80%." ==
1Bet are now a leading online sportsbook. They are very similar to IBC (Maxbet) in their look and feel and also settle bets at a partial amount of 80%.
They have a wide variety of betting opportunities across a range of sports – specialising in Asian Handicaps. Like many other Asian Sportsbooks they welcome arbitrage business, do note the 1×2 prices are not as competitive. You can find better elsewhere.
1Bet are owned by Bellona N.V. with offices located in Curacao. Gaming activity is operated and regulated under license no. 8048/JAZ issued by the Gaming Commission of Curacao.
We have noticed that 1Bet offer very competitive odds, have early lines available across their football product and a good in-play offering with settlement at 80%. BOLO BET have not been informed of any voided bets.


Agent waited at the rest stop near Stuttgart for subject to arrive. Agent had Big Mac with fries*. Big Mac called “Der Big Mac”.
Subject arrived at 06:30 in an Iveco PowerDrive 420 E9. Also had Big Mac.
Subject left at 07:10 following the E41. Agent followed at a discreet distance. Agent ran out of gas near Dorfmark, and lost visual on subject.
Leased a new car at ALD AutoLeasing D**, but it was too late to catch up with subject. Agent drove to Bad Fallingbostel to try the state-recognised Kneipp spa***.
Subject’s truck was stopped by other agents near Meckelfeld. Truck was found to contain apples, bananas and oranges. Subject allowed agents to keep a crate of bananas. No suspicious contents discovered.
* See expense report #AD-5854.
** See expense report #AD-5915.
*** I’ll pay for it myself, okay?


Undergraduate Research Assistant
Universidad de los Andes
August 2019 - Present
- Developing a deep learning network to perform lung segmentation in CT scans of patients with SDRA.
Summer Intern
Seguros Bolivar
June 2019 - August 2019
- Developed a short research project on the correlation of the risk of the different insurance products with the help of a mentor.
Undergraduate Research Fellow
Purdue University
May 2018 - August 2018
-
Participated in an extensive joint research program along with Purdue University Summer Undergraduate Research Fellowship
(SURF) and the Network for Computational Nanotechnology (NCN).
-
Conducted research under a faculty member on machine learning for the continuous representation of discrete chemical data.
-
Final deliverables included presenting research at a poster symposium, delivering an oral presentation,
writing a technical paper and publishing a simulation tool on nanoHUB.
Undergraduate Teaching Assistant
Universidad de los Andes
February 2016 - July 2019
- Tutored and graded the exams, projects and workshops of over 200 undergraduates and a few graduate students in diverse
Computer Science and Mathematics courses.
- Courses and technologies: Algorithmic and Object Oriented Programming I and II (Honors), Computational Infrastructure
(Java), Security and Privacy of IIoT and IoT Systems (BLE, Wireshark), Database Systems (Java, SQL), Design and Analysis
of Algorithms (Java, Python), Communications Infrastructure. Linear Algebra, Mathematical Thinking, Probability (Honors).


Psalm 12
For the chief musician; set to the Sheminith. A psalm of David.
1 Help, Yahweh, for the godly have disappeared;
the faithful have vanished.
2 Everyone says empty words to his neighbor;
everyone speaks with flattering lips and a double heart.
3 Yahweh, cut off all flattering lips,
every tongue declaring great things.
4 These are those who have said, "With our tongues will we prevail.
When our lips speak, who can be master over us?"
5 "Because of violence against the poor, because of the groans of the needy,
I will arise," says Yahweh.
"I will provide the safety for which they long."
6 The words of Yahweh are pure words,
like silver purified in a furnace on the earth,
refined seven times.
7 You are Yahweh! You keep them.
You preserve the godly people from this wicked generation and forever.
8 The wicked walk on every side
when evil is exalted among the sons of men.


Notes: - Click on a node to see the belief-base at that point. - Hover over a node for context information. - Colour code: Traversed / Viable Path Non-Viable path Failed Action


Often when designing games, we need to design a pull algorithm, or a way to give the player a random game object from a pool of random objects. It's hard to visualize how these random distributions look in practice and so difficult to design them well.
This is our first simulation and it’s pretty simple. Just click the interact! button to give the player a game piece. Different players require different amounts of engagement. If a player receives too little stimulation, they will leave.
This is a really abstract representation of how getting stuff in games works. Nevertheless, you can imagine that if this were Pokemon Go, every time you pressed the interact button, the player got a new Pokemon.
This is an obvious and gross simplification of the player's experience. However, if we look at it as purely the experience on the single axis of the pull system, and a heavy simplification of that as well, we can still derive value from these simulations. It is also worth remembering that a new feature could do well in this simulation, but still be bad for your game due to something that this article doesn’t cover, such as negatively impacting the decision making in the game or increasing complexity to the point of impenetrability. Video games are complex and need to be looked at with multiple lenses.
A common game development pattern is to use a system to drive the player’s engagement instead of hand-crafting it in the manner of the above simulations. It’s often time consuming and expensive to hand-craft a full drop pattern. So, with this simulation, we’re going to go over a basic system to do that for us.
There are three sliders to play with in this simulation:
|
|
Pull Rate 0Novelty Requirement 1 |
Observations:
We're now going to add some detail to the previous simulation to make it skew closer to a real pull system.
The impetus for this piece came from watching Pokemon Go release the second generation of Pokemon into the wild, so we’re going to use that game as the primary example for the rest of the piece. In particular, we’re going to look at the way players randomly encounter new Pokemon to catch, and consider that a pull system.
We’re going to start with the most abstract representation, where we’ll just assume that all of the pieces are of equal value and we’ll assume 100 of them.
|
|
Pull Rate 0Novelty Requirement 1Number of Pieces 100Value of New Piece 2Value of Duplicate Piece 0Average Number of Pulls: Average Number of Unique Pieces: Average Time for Player: |
Observations:
Possible Improvements:
Let’s get a little deeper into what a real pull system looks like. Taking Pokemon Go itself, different Pokemon are differently valuable due to the following axes:
We're not going to simulate all of that, just something a little closer to it than the simulation above. Note, that at this level of abstraction, this data can represent a lot of games, not just Pokemon Go. To do this, I:
|
|
Pull Rate 0Novelty Requirement 1Average Number of Pulls: Average Number of Unique Pieces: Average Time For Player: |
Observations:
Pokemon Go, when introducing the second generation, just added more pieces to their existing pulls. Releasing like that when your players have already performed a large number of pulls results in a graph that looks something like the below one.
|
|
Pull Rate 0Novelty Requirement 1Number of Old Pieces 100Number of New Pieces 100Starting Number of Pulls 0Value of New Piece 2Value of Duplicate Piece 0Average Number of Pulls: Average Number of Unique Pieces: Average Time For Player: |
Observations:
We've only worked with simple, highly random pull algorithms thus far. In this section, we'll take a look at some other kinds.
What does this graph look like in the trivial case of just going through every element one by one?
|
|
Pull Rate 0Novelty Requirement 1Number of Pieces 100Value of New Piece 2Value of Duplicate Piece 0Average Number of Pulls: Average Number of Unique Pieces: Average Time For Player: |
Note that it feels very different for players to get random pulls and to get deterministic pulls. One reason for this is that being able to calculate the effort required for something changes the way players value that thing. These simulations have no way to model that though. They can only show you what players get.
Observations:
A common approach to smooth out the variance of a pull system is to place a ceiling on the number of low-value pulls. That results in graphs that look like this:
|
|
Pull Rate 0Novelty Requirement 1Number of Pieces 100Value of New Piece 2Value of Duplicate Piece 0Bad Pull Cap 0Average Number of Pulls: Average Number of Unique Pieces: Average Time For Player: |
Observations:
On a personal note, I dislike it when games do this without communicating the skew to the player because I feel it reinforces the gambler’s fallacy. I also feel that making the cap more explicit is a better experience for the player as the player doesn’t feel like bad pulls help them get to good pulls when it is implicit.
Another option is to divide your pool of pulls across a lot of smaller pools and then let the player move between them. This is essentially what Pokemon Red did and also what a game like Heroes Charge does as well. This changes the flow to be much wavier, and so the graph looks more like this:
|
|
Pull Rate 0Novelty Requirement 1Number of Old Pieces 100Number of New Pieces 100Starting Number of Pulls 0Value of New Piece 2Value of Duplicate Piece 0Average Number of Pulls: Average Number of Unique Pieces: Average Time For Player: |
Of course, there are a lot of ways to implement a division like this and the amount of effort required is dependent on the kind of separation that you want to make.
Observations:
This is, of course, a very incomplete taxonomy. Hopefully though, it lets you think about how players interact with the pull systems that you have made and the potential problems and benefits of these solutions.
You can look through the source code here - https://github.com/nikwin/pullArticle
If you have any feedback on this or if you want to see more things like this, you can reach me on Twitter at @murthynikhil. If you make any new simulations like this, please do tell me. I’d love to see more explanations like this.


Make Every Single Kind Gesture Count!
The severe damage to the economy that this novel Coronavirus has proven that people in economic contrains are the ones suferring the most.Don Beto, a seventy nine years old man, sells his candies for living, in a small village in El Salvador in Central America. Due to COVID-19 quarantine he has not been able to sale his candies and did not have any food on his table.


| Overview | Namespace | Class | Index | Help |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value x in the term acosh(x). |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value to be rounded. |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value x in the term asinh(x). |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value x in the term atanh(x). |
| rtl_String * * | pResult, |
| sal_Int32 * | pResultCapacity, |
| sal_Int32 | nResultOffset, |
| double | fValue, |
| rtl_math_StringFormat | eFormat, |
| sal_Int32 | nDecPlaces, |
| sal_Char | cDecSeparator, |
| const sal_Int32 * | pGroups, |
| sal_Char | cGroupSeparator, |
| sal_Bool | bEraseTrailingDecZeros ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| pResult | Returns the resulting byte string. Must itself not be null, and must point to either null or a valid string. |
| pResultCapacity | If null, pResult is considered to point to immutable strings, and a new string will be allocated in pResult. If non-null, it points to the current capacity of pResult, which is considered to point to a string buffer (pResult must not itself be null in this case, and must point to a string that has room for the given capacity). The string representation of the given double value is inserted into pResult at position nResultOffset. If pResult's current capacity is too small, a new string buffer will be allocated in pResult as necessary, and pResultCapacity will contain the new capacity on return. |
| nResultOffset | If pResult is used as a string buffer (i.e., pResultCapacity is non-null), nResultOffset specifies the insertion offset within the buffer. Ignored otherwise. |
| fValue | The value to convert. |
| eFormat | The format to use, one of rtl_math_StringFormat. |
| nDecPlaces | The number of decimals to be generated. Effectively fValue is rounded at this position, specifying nDecPlaces <= 0 accordingly rounds the value before the decimal point and fills with zeros. If eFormat == rtl_math_StringFormat_Automatic and nDecPlaces == rtl_math_DecimalPlaces_Max, the highest number of significant decimals possible is generated. If eFormat == rtl_math_StringFormat_G, nDecPlaces specifies the number of significant digits instead. If nDecPlaces == rtl_math_DecimalPlaces_DefaultSignificance, the default number (currently 6 as implemented by most libraries) of significant digits is generated. According to the ANSI C90 standard the E style will be used only if the exponent resulting from the conversion is less than -4 or greater than or equal to the precision. However, as opposed to the ANSI standard, trailing zeros are not necessarily removed from the fractional portion of the result unless bEraseTrailingDecZeros == true was specified. |
| cDecSeparator | The decimal separator. |
| pGroups | Either null (no grouping is used), or a null-terminated list of group lengths. Each group length must be strictly positive. If the number of digits in a conversion exceeds the specified range, the last (highest) group length is repeated as needed. Values are applied from right to left, for a grouping of 1,00,00,000 you'd have to specify pGroups={3,2,0}. |
| cGroupSeparator | The group separator. Ignored if pGroups is null. |
| bEraseTrailingDecZeros | Trailing zeros in decimal places are erased. |
| rtl_uString * * | pResult, |
| sal_Int32 * | pResultCapacity, |
| sal_Int32 | nResultOffset, |
| double | fValue, |
| rtl_math_StringFormat | eFormat, |
| sal_Int32 | nDecPlaces, |
| sal_Unicode | cDecSeparator, |
| const sal_Int32 * | pGroups, |
| sal_Unicode | cGroupSeparator, |
| sal_Bool | bEraseTrailingDecZeros ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| pResult | Returns the resulting Unicode string. Must itself not be null, and must point to either null or a valid string. |
| pResultCapacity | If null, pResult is considered to point to immutable strings, and a new string will be allocated in pResult. If non-null, it points to the current capacity of pResult, which is considered to point to a string buffer (pResult must not itself be null in this case, and must point to a string that has room for the given capacity). The string representation of the given double value is inserted into pResult at position nResultOffset. If pResult's current capacity is too small, a new string buffer will be allocated in pResult as necessary, and pResultCapacity will contain the new capacity on return. |
| nResultOffset | If pResult is used as a string buffer (i.e., pResultCapacity is non-null), nResultOffset specifies the insertion offset within the buffer. Ignored otherwise. |
| fValue | The value to convert. |
| eFormat | The format to use, one of rtl_math_StringFormat. |
| nDecPlaces | The number of decimals to be generated. Effectively fValue is rounded at this position, specifying nDecPlaces <= 0 accordingly rounds the value before the decimal point and fills with zeros. If eFormat == rtl_math_StringFormat_Automatic and nDecPlaces == rtl_math_DecimalPlaces_Max, the highest number of significant decimals possible is generated. If eFormat == rtl_math_StringFormat_G, nDecPlaces specifies the number of significant digits instead. If nDecPlaces == rtl_math_DecimalPlaces_DefaultSignificance, the default number (currently 6 as implemented by most libraries) of significant digits is generated. According to the ANSI C90 standard the E style will be used only if the exponent resulting from the conversion is less than -4 or greater than or equal to the precision. However, as opposed to the ANSI standard, trailing zeros are not necessarily removed from the fractional portion of the result unless bEraseTrailingDecZeros == true was specified. |
| cDecSeparator | The decimal separator. |
| pGroups | Either null (no grouping is used), or a null-terminated list of group lengths. Each group length must be strictly positive. If the number of digits in a conversion exceeds the specified range, the last (highest) group length is repeated as needed. Values are applied from right to left, for a grouping of 1,00,00,000 you'd have to specify pGroups={3,2,0}. |
| cGroupSeparator | The group separator. Ignored if pGroups is null. |
| bEraseTrailingDecZeros | Trailing zeros in decimal places are erased. |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value x in the term erf(x). |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value x in the term erfc(x). |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value x in the term e^x-1. |
| double | fValue ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value x in the term log(1+x). |
| double | fValue, |
| int | nExp ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | The value to be raised. |
| nExp | The exponent. |
| double | fValue, |
| int | nDecPlaces, |
| rtl_math_RoundingMode | eMode ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| fValue | Specifies the value to be rounded. |
| nDecPlaces | Specifies the decimal place where rounding occurs. Must be in the range -20 to +20, inclusive. Negative if rounding occurs before the decimal point. |
| eMode | Specifies the rounding mode. |
| const sal_Char * | pBegin, |
| const sal_Char * | pEnd, |
| sal_Char | cDecSeparator, |
| sal_Char | cGroupSeparator, |
| rtl_math_ConversionStatus * | pStatus, |
| const sal_Char * * | pParsedEnd ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| pBegin | Points to the start of the byte string to convert. Must not be null. |
| pEnd | Points one past the end of the byte string to convert. The condition pEnd >= pBegin must hold. |
| cDecSeparator | The decimal separator. |
| cGroupSeparator | The group (aka thousands) separator. |
| pStatus | If non-null, returns the status of the conversion. |
| pParsedEnd | If non-null, returns one past the position of the last character parsed away. Thus if [pBegin..pEnd) only contains the numerical string to be parsed, *pParsedEnd == pEnd on return. If no numerical (sub-)string is found, *pParsedEnd == pBegin on return, even if there was leading whitespace. |
| const sal_Unicode * | pBegin, |
| const sal_Unicode * | pEnd, |
| sal_Unicode | cDecSeparator, |
| sal_Unicode | cGroupSeparator, |
| rtl_math_ConversionStatus * | pStatus, |
| const sal_Unicode * * | pParsedEnd ); |
| virtual | abstract | const | volatile | template | static | inline | C-linkage |
| NO | NO | NO | NO | NO | NO | NO | YES |
| pBegin | Points to the start of the Unicode string to convert. Must not be null. |
| pEnd | Points one past the end of the Unicode string to convert. The condition pEnd >= pBegin must hold. |
| cDecSeparator | The decimal separator. |
| cGroupSeparator | The group (aka thousands) separator. |
| pStatus | If non-null, returns the status of the conversion. |
| pParsedEnd | If non-null, returns one past the position of the last character parsed away. Thus if [pBegin..pEnd) only contains the numerical string to be parsed, *pParsedEnd == pEnd on return. If no numerical (sub-)string is found, *pParsedEnd == pBegin on return, even if there was leading whitespace. |
Copyright © 2012, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


The base directory for screenshot storage. When null or empty will default to the environment current working directory.
A function that produces a filename for a given screenshot request.
An identifier for the reference run. Internally this value is used as a relative path, so values that contain path separators are handled as expected.
Defaults to 0000.auto if no directory is found matching the pattern \d+\.auto
, otherwise will equal the latest detected directory of that format.
An identifier for the current run. Internally this value is used as a relative path, so values that contain path separators are handled as expected.
Defaults to 0001.auto when no reference directory exists, otherwise 0002.auto, 0003.auto etc.
note: this value when unset will autoincrement every time the screenshot module is loaded - usually once per test run.
Generated using TypeDoc
Setup options for screencheck. Allows optional configuration of base directory, run id, reference run id, and filename generator function.


Input comma seperated numbers, and/or dash seperated ranges of numbers.
Note: Universes are numbered from 1, and address 1 = DIP switch 000000001
Created by: nick.niemeir@gmail.com


' Source: https://plantuml.com/sequence-diagram
@startuml
participant Participant as Foo
actor Actor as Foo1
boundary Boundary as Foo2
control Control as Foo3
entity Entity as Foo4
database Database as Foo5
collections Collections as Foo6
queue Queue as Foo7
Foo -> Foo1 : To actor
Foo -> Foo2 : To boundary
Foo -> Foo3 : To control
Foo -> Foo4 : To entity
Foo -> Foo5 : To database
Foo -> Foo6 : To collections
Foo -> Foo7 : To queue
@enduml


Contents
Short Descriptions
|
compresses image files to produce a JPEG/JFIF file on the standard output. Currently supported input file formats are: PPM (PBMPLUS color format), PGM (PBMPLUS gray-scale format), BMP, and Targa. |
|
|
decompresses image files from JPEG/JFIF format to either PPM (PBMPLUS color format), PGM (PBMPLUS gray-scale format), BMP, or Targa format. |
|
|
is used for lossless transformation of JPEG files. |
|
|
displays text comments from within a JPEG file. |
|
|
is used to benchmark the performance of libjpeg-turbo. |
|
|
inserts text comments into a JPEG file. |
|
|
contains functions used for reading and writing JPEG images. |


Simon Says
Start Game
Score: 0
Level: 1
Follow the pattern of light and sound, difficulty increases with each level!


The Akan Name Generator !!!!
Hello there! This is a web application that takes your birthday details and then outputs your Akan name depending on your gender. Akan names originate from the Akan people of Ghana who have a unique naming system that is based on the day of the week that one was born and their gender. Read more about the Akan people here
If you would like to know your Akan name, please enter your birthday details and gender below and click submit.


crossfilter-hydrology
This page is based on
filtering.html
from the list of simple dc-js examples.
selected:
reset
range:
reset
selected:
reset