Uses of Package
com.google.zxing
Package
Description
-
ClassDescriptionEnumerates barcode formats known to this package.This class hierarchy provides a set of methods to convert luminance data to 1 bit data.This class is the core bitmap class used by ZXing to represent 1 bit data.Thrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.These are a set of hints that you may pass to Writers to specify their behavior.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.The purpose of this class hierarchy is to abstract different bitmap implementations across platforms into a standard interface for requesting greyscale luminance values.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.The general exception class throw when something goes wrong during decoding of a barcode.Encapsulates the result of decoding a barcode within an image.Represents some type of metadata about the result of the decoding that the decoder wishes to communicate back to the caller.Encapsulates a point of interest in an image containing a barcode.The base class for all objects which encode/generate a barcode image.A base class which covers the range of exceptions which may occur when encoding a barcode using the Writer framework.
-
ClassDescriptionEnumerates barcode formats known to this package.This class is the core bitmap class used by ZXing to represent 1 bit data.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.These are a set of hints that you may pass to Writers to specify their behavior.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.Encapsulates a point of interest in an image containing a barcode.The base class for all objects which encode/generate a barcode image.
-
ClassDescriptionThrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.
-
-
ClassDescriptionThe purpose of this class hierarchy is to abstract different bitmap implementations across platforms into a standard interface for requesting greyscale luminance values.
-
-
ClassDescriptionThis class hierarchy provides a set of methods to convert luminance data to 1 bit data.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.The purpose of this class hierarchy is to abstract different bitmap implementations across platforms into a standard interface for requesting greyscale luminance values.Thrown when a barcode was not found in the image.Encapsulates a point of interest in an image containing a barcode.
-
ClassDescriptionThrown when a barcode was not found in the image.Encapsulates a point of interest in an image containing a barcode.
-
ClassDescriptionEnumerates barcode formats known to this package.This class is the core bitmap class used by ZXing to represent 1 bit data.Thrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.These are a set of hints that you may pass to Writers to specify their behavior.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.The base class for all objects which encode/generate a barcode image.
-
ClassDescriptionThrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.
-
-
-
ClassDescriptionThis class is the core bitmap class used by ZXing to represent 1 bit data.Thrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.
-
ClassDescriptionThrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.
-
ClassDescriptionThis class is the core bitmap class used by ZXing to represent 1 bit data.Thrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.
-
ClassDescriptionThis class is the core bitmap class used by ZXing to represent 1 bit data.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.
-
ClassDescriptionEncapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was not found in the image.Callback which is invoked when a possible result point (significant point in the barcode image such as a corner) is found.
-
ClassDescriptionEnumerates barcode formats known to this package.This class is the core bitmap class used by ZXing to represent 1 bit data.Thrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.These are a set of hints that you may pass to Writers to specify their behavior.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.The base class for all objects which encode/generate a barcode image.
-
ClassDescriptionEncapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.Encapsulates a point of interest in an image containing a barcode.
-
ClassDescriptionEncapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.
-
ClassDescriptionThrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.
-
ClassDescriptionEnumerates barcode formats known to this package.This class is the core bitmap class used by ZXing to represent 1 bit data.Thrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.These are a set of hints that you may pass to Writers to specify their behavior.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.The base class for all objects which encode/generate a barcode image.A base class which covers the range of exceptions which may occur when encoding a barcode using the Writer framework.
-
ClassDescriptionThrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Encapsulates a point of interest in an image containing a barcode.
-
ClassDescriptionThrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.
-
ClassDescriptionThis class is the core bitmap class used by ZXing to represent 1 bit data.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was not found in the image.
-
ClassDescriptionA base class which covers the range of exceptions which may occur when encoding a barcode using the Writer framework.
-
ClassDescriptionEnumerates barcode formats known to this package.This class is the core bitmap class used by ZXing to represent 1 bit data.Thrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.These are a set of hints that you may pass to Writers to specify their behavior.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Implementations of this interface can decode an image of a barcode in some format into the String it encodes.Encapsulates the result of decoding a barcode within an image.The base class for all objects which encode/generate a barcode image.A base class which covers the range of exceptions which may occur when encoding a barcode using the Writer framework.
-
ClassDescriptionThrown when a barcode was successfully detected and decoded, but was not returned because its checksum feature failed.Encapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Encapsulates a point of interest in an image containing a barcode.
-
ClassDescriptionEncapsulates a type of hint that a caller may pass to a barcode reader to help it more quickly or accurately decode it.Thrown when a barcode was successfully detected, but some aspect of the content did not conform to the barcode's format rules.Thrown when a barcode was not found in the image.Encapsulates a point of interest in an image containing a barcode.Callback which is invoked when a possible result point (significant point in the barcode image such as a corner) is found.
-
ClassDescriptionThese are a set of hints that you may pass to Writers to specify their behavior.A base class which covers the range of exceptions which may occur when encoding a barcode using the Writer framework.


The Huracán EVO represents the natural evolution of the most successful V10 in Lamborghini history. It is the result of fine-tuning and consolidation which involves the already existing features and performance of Huracán, combined with the development of new solutions in terms of efficiency and design. But overall this vehicle stands out for its ability to anticipate the moves and satisfy the desires of the driver, in harmony with the Lamborghini DNA.
The Huracán EVO was developed to amplify your daily routine by anticipating the needs of the driver, making your day-to-day experience behind the wheel unique and totally personal. A state-of-the-art control system and innovative touchscreen easily manage the car’s functions and entertainment system. This, combined with dazzling aerodynamic design, elevate the performance and driving emotions to unprecedented levels.


Please provide the following information to run the identityTranslator of ROSE:
Step 1/2. Input source code (max size allowed: 20,000 characters, roughly 500 lines)
/*a test C++ program. You can replace this content with yours, within 20,000 character limit (about 500 lines) . */ template
class X { public: X(); ~X(); void foo(); X operator+(); }; X
::~X() { } X
::X() { } void X
::foo() { } X
X
::operator+( ) { X
x; return x; }
Step 2/2: Select suffix of the source code
.c
.cpp (including c++11)
.f
.f90


This is a template
This is a template and you can change this however you want.
Copy & Paste this link for a rickroll:


Feature: Entering time
Note: personas are listed here
Employee user story:
As an employee, Andrea,
I want to record my time
so I am easily able to document my time in an organized way
Scenarios:
A employee enters six hours on a project with copious notes
Given I have worked 6 hours on project A on Monday with a lot of notes,
when I enter in that time,
then the system indicates it has persisted the new information.
A employee has already entered 24 hours for the day, they cannot enter more time on a new entry
given the employee has already entered 24 hours of time entries before,
when they enter in a new time entry for one hour,
then the system disallows it.
001 - recordTime - An employee should be able to enter time for a specified date
Given the employee worked 8 hours yesterday,
when the employee enters their time,
then time is saved.
002 - recordTime - An employee should be able to edit the number of hours worked from a previous time entry
Given Andrea has a previous time entry with 24 hours,
when she changes the entry to only 8 hours,
then it is reflected in the database.


Here you have the option to select either the Kubernetes Cluster or the GPU. To navigate this form, you first make your selection, then click on the buttons to the left to travel through the form.
If you want to stop filling out the Cluster Form or vice versa, just go back to the selection tab and select the other option. It will clear your old form and allow you to navigate your desired form.
After making sure to fill out all of the input fields, you will be able to then submit the form at the review page, which shows what you have inputted.
Here are some quick explanations as to what certain parts of the forms refer to:
Region and Zone: Selected from the gcloud regions list
Machine Type: Type of Server (n1-standard-2 for cheap alternative/ otherwise go for n1-highmem-4)
Authorization File: Service account authorization (i.e. auth.json)
Number of Nodes: Default number of nodes
Number of Nodes (Class): The number of nodes when class is in session


InfoCommand
The info command returns different information and statistics about the server in an format that's simple to parse by computers and easy to red by huamns.
Bulk reply, specifically in the following format:
edis_version:0.07
connected_clients:1
connected_slaves:0
used_memory:3187
changes_since_last_save:0
last_save_time:1237655729
total_connections_received:1
total_commands_processed:1
uptime_in_seconds:25
uptime_in_days:0
All the fields are in the form
field:value
-
used_memory
is returned in bytes, and is the total number of bytes allocated by the program using malloc
. -
uptime_in_days
is redundant since the uptime in seconds contains already the full uptime information, this field is only mainly present for humans. -
changes_since_last_save
does not refer to the number of key changes, but to the number of operations that produced some kind of change in the dataset.


--- title: Grain Size Project layout: grainsize ---
Sequence information of new TaCKX2-A1, TaCKX2-B1 and TaCKX2-D1 mutations in the T2 progeny plants from event #4-6. The mutation types include deletions (dashed line), insertions (lower-case letters in black) and substitutions (blue letters). PAM sequences are in green. Black dots mean nucleotides not shown.


poetry
Manage Python packages and dependencies.
More information: home page
- Create a new Poetry project in the directory with a specific name:
poetry new project_name
- Install a dependency and its subdependencies:
poetry add dependency
- Install a development dependency and its subdependencies:
poetry add --group dev dependency
- Interactively initialize the current directory as a new Poetry project:
poetry init
- Get the latest version of all dependencies and update `poetry.lock`:
poetry update
- Execute a command inside the project's virtual environment:
poetry run command
- Bump the minor version of the project in `pyproject.toml`:
poetry version minor


Next: Examples of MAXIMIZE and MINIMIZE clauses, Previous: Examples of APPEND and NCONC clauses, Up: Value Accumulation Clauses
(loop for i in '(a b nil c nil d e) count i) ⇒ 5


Github
This is the main entrance of pygithub3
-
class pygithub3.Github(**config)
You can preconfigure all services globally with a config dict. See
Service
Example:
gh = Github(user='kennethreitz', token='ABC...', repo='requests')
-
gists
Gists service
-
remaining_requests
Limit of Github API v3
-
repos
Repos service
-
users
Users service


File containing the definition of methods for the operation of an H-Bridge in bipolar operation mode. File containing the definition of methods for the operation of an H-Bridge in bipolar operation mode. More...
#include <MKL25Z4.h>
#include "fsl_sim_hal.h"
#include "fsl_tpm_hal.h"
Go to the source code of this file.
Classes | |
| struct | driver_instance_t |
| driver_instance_t Struct containing specific data for a motor driver instance. More... | |
Functions | |
| void | driver_initDriver (driver_instance_t driverInstance) |
| Initializes the driver with the load in idle (50% duty cycle). More... | |
| void | driver_appendDriver (driver_instance_t driverInstance) |
| Add another driver instance to an already active driver session with the load in idle (50% duty cycle). More... | |
| void | driver_disableDriver (driver_instance_t driverInstance) |
| Disables the driver by clearing the enable pin. More... | |
| void | driver_enableDriver (driver_instance_t driverInstance) |
| Enables the driver by setting the enable pin. More... | |
| void | driver_setChannelADutyCycle (driver_instance_t driverInstance, int uiDutyCyclePercent) |
| Sets duty cycle for Channel A only. More... | |
| void | driver_setChannelBDutyCycle (driver_instance_t driverInstance, int uiDutyCyclePercent) |
| Sets duty cycle for Channel B only. More... | |
| void | driver_setHBridgeDutyCycle (driver_instance_t driverInstance, int uiDutyCyclePercent) |
| Sets duty cycle for H-Bridge operation. Both ChA and ChB. More... | |
| void | driver_setDriver (driver_instance_t driverInstance, int input) |
| Sets the driver from -100 to 100, the former being full reverse, and the latter, full steam ahead. More... | |
| void | driver_setDriver2 (driver_instance_t driverInstance, int input, float factor) |
| setDriver but takes another argument to multiply duty cycle More... | |
File containing the definition of methods for the operation of an H-Bridge in bipolar operation mode. File containing the definition of methods for the operation of an H-Bridge in bipolar operation mode.
| void driver_appendDriver | ( | driver_instance_t | driverInstance | ) |
Add another driver instance to an already active driver session with the load in idle (50% duty cycle).
| driverInstance | driver_instance_t struct. |
| void driver_disableDriver | ( | driver_instance_t | driverInstance | ) |
Disables the driver by clearing the enable pin.
| driverInstance | driver_instance_t struct. |
| void driver_enableDriver | ( | driver_instance_t | driverInstance | ) |
Enables the driver by setting the enable pin.
| driverInstance | driver_instance_t struct. |
| void driver_initDriver | ( | driver_instance_t | driverInstance | ) |
Initializes the driver with the load in idle (50% duty cycle).
| driverInstance | driver_instance_t struct. |
| void driver_setChannelADutyCycle | ( | driver_instance_t | driverInstance, |
| int | uiDutyCyclePercent | ||
| ) |
Sets duty cycle for Channel A only.
| driverInstance | driver_instance_t struct. |
| uiDutyCyclePercent | Duty cycle in percentage. |
| void driver_setChannelBDutyCycle | ( | driver_instance_t | driverInstance, |
| int | uiDutyCyclePercent | ||
| ) |
Sets duty cycle for Channel B only.
| driverInstance | driver_instance_t struct. |
| uiDutyCyclePercent | Duty cycle in percentage. |
| void driver_setDriver | ( | driver_instance_t | driverInstance, |
| int | input | ||
| ) |
Sets the driver from -100 to 100, the former being full reverse, and the latter, full steam ahead.
| driverInstance | driver_instance_t struct. |
| input | -100 to 100. |
| void driver_setDriver2 | ( | driver_instance_t | driverInstance, |
| int | input, | ||
| float | factor | ||
| ) |
setDriver but takes another argument to multiply duty cycle
| driverInstance | driver_instance_t struct. |
| input | -100 to 100. |
| factor | to multiply input. |
| void driver_setHBridgeDutyCycle | ( | driver_instance_t | driverInstance, |
| int | uiDutyCyclePercent | ||
| ) |
Sets duty cycle for H-Bridge operation. Both ChA and ChB.
| driverInstance | driver_instance_t struct. |
| uiDutyCyclePercent | Duty cycle in percentage (0% is full reverse, 100% is full ahead). |


back to index
The idea of connecting the finite and infinite is met explicitly when learning limits in calculus; or via alternate branches of mathematics. Typical of most Western education systems this will be viewed through a topic-specific lens instead of philosophically.
Leo Tolstoy presents it in a beautiful form through his A Confession and Other Religious Writings, which I discovered via BrainPickings.org.
The more time you spend with with the concept of connecting the finite and infinite the more you will find it positions itself in thought provoking niches:
- In views of life and religion as commented on by Tolstoy (I would add an individual's contribution to human knowledge, or culture, is analogous in some sense to his presentation of religion).
- Evaluations of possible solutions to quantum gravity and other budding physical theories.
- The foundations of mathematics and computation.
When these (possible) connections are found it is worth pausing to give complete thought.


{% extends '_base.html' %} {% load humanize %} {% block content %} Telemetry This is what we can infer from signals, plus a raw list below. {{ active_users_last_day|intword|intcomma }} Active users in the last 24 hours {{ active_users_last_week|intword|intcomma }} Active users in the last 7 days {{ active_users_last_month|intword|intcomma }} Active users in the last 30 days {{ active_users_last_month_long_term|intword|intcomma }} Long Term Users in the last 30 days {{ active_monthly_users.as_html }} {% for chart_list in charts %} {% for chart in chart_list.items %} {{ chart.0 }} {{ chart.1.as_html }} {% endfor %} {% endfor %} Raw Signals The last 10 signals Received At User Type Parameters {% for obj in object_list %} {{ obj.received_at }} {{ obj.user.short_name }} {{ obj.type }} {{ obj.parameters }} {% empty %} No Signals for this App yet. {% endfor %} {% endblock %}
This is what we can infer from signals, plus a raw list below.
The last 10 signals


This project is maintained by BIB-R
BIB-RCAT is a dataset of MARC21 records accompanied by the FRBR version to evaluate a FRBRization solution.
BIB-R includes two datasets (T42 and BIB-RCAT) dedicated to the evaluation of the FRBRization process. The goal of the first dataset T42 is to identify the weak and strong points of a tool by testing all possible issues that libraries may face during FRBRization. The second dataset BIB-RCAT is extracted from catalogs of three different cultural institutions and can be used for comparing or experimenting with the data quality and size of data that typically is found in real world catalogs. The expected FRBR results (gold standard) are included in these datasets to enable evaluation. The MARC catalogs are provided in MARC/XML format while the FRBR collections are available in RDF/XML (Generated by the Jena API).
T42 has been built for benchmarking FRBRization solutions which deal with MARC (UNIMARC & MARC21) records. The dataset is composed by 42 different tests where each relates a specific FRBR pattern representation and can include specific issues.
BIB-RCAT is a dataset of MARC21 records accompanied by the FRBR version to evaluate a FRBRization solution.
The MARC files are provided in MARC/XML format and can be handled by MARC-based libraries or tools (e.g., MARC4J). The FRBR files use the RDF/XML format. They can be loaded and managed by API such as Jena to manipulate data as triples.
The FRBR collections use an adhoc vocabulary which is specific to our project. However, each concept comes from reference FRBR vocabularies such as FRBRer and RDA. A RDF mapping file is provided where each concept from our vocabulary is mapped to reference concepts. Example:
```xml
These datasets are released under a Creative Commons Attribution-NonCommercial licence (CC BY-NC 2.0).


Everything you need to create a basic custom controller class is detailed in the previous sections.
GenControlClass
, however, has a number of messages and structures that will be used by some subclasses, though this will be relatively rare. This section details these messages and structures.
MSG_GEN_CONTROL_GENERATE_UI, MSG_GEN_CONTROL_DESTROY_UI, MSG_GEN_CONTROL_GENERATE_TOOLBOX_UI, MSG_GEN_CONTROL_DESTROY_TOOLBOX_UI, MSG_GEN_CONTROL_UPDATE_UI, MSG_GEN_CONTROL_ENABLE_DISABLE, MSG_GEN_CONTROL_ADD_APP_UI, MSG_GEN_CONTROL_ADD_APP_TOOLBOX_UI, MSG_GEN_CONTROL_REBUILD_NORMAL_UI, MSG_GEN_CONTROL_REBUILD_TOOLBOX_UI
GenControlClass
has several messages that add, remove, and manipulate the controller UI gadgetry. Keep in mind also that, as a subclass of
GenInteractionClass
and thereby of
GenClass
, the GenControl also can use any of the generic UI messages for object tree manipulation. These messages are detailed in the following list.
void MSG_GEN_CONTROL_GENERATE_UI();
This message generates the UI gadgetry for the controller.
Source: Unrestricted--sent by self as part of specific UI build.
Destination: Any GenControl object
Interception: If subclassed to add functionality, the subclass must call the superclass at the beginning of the handler.
Warnings: If you intercept this message, you should also intercept
MSG_GEN_CONTROL_DESTROY_UI
, below.
void MSG_GEN_CONTROL_DESTROY_UI();
This message destroys the UI gadgetry for the controller.
Source: Unrestricted--sent by self when being taken off the screen.
Destination: Any GenControl object
Interception: Any subclass that intercepts
MSG_GEN_CONTROL_GENERATE_UI
must intercept this. The subclass must call the superclass at the end of the handler.
void MSG_GEN_CONTROL_GENERATE_TOOLBOX_UI( optr parent);
This message generates the UI gadgetry for the controller's tool box.
Source: Sent by tool box object via the active list as part of its specific UI build mechanism.
Destination: The GenControl object that owns the tool box.
Parameters:
parent
The optr of GenInteraction that will be the parent of the controller's tools.
Return: Nothing.
Interception: A subclass may intercept this to add UI gadgetry to the toolbox when the toolbox is built. The subclass must call the superclass at the beginning of the handler.
Warnings: Any controller that subclasses this message must also subclass
MSG_GEN_CONTROL_DESTROY_TOOLBOX_UI
as well.
void MSG_GEN_CONTROL_DESTROY_TOOLBOX_UI();
This message destroys all toolbox UI associated with the controller.
Source: Sent by the tool box being destroyed as part of its specific UI destruction mechanism.
Destination: The GenControl object that owns the tool box.
Interception: Any controller class that subclasses the message
MSG_GEN_CONTROL_GENERATE_TOOLBOX_UI
must also subclass this message. The subclass must call its superclass at the end of its handler.
void MSG_GEN_CONTROL_UPDATE_UI(@stack MemHandle toolBlock, MemHandle childBlock, WordFlags toolboxFeatures, WordFlags features, MemHandle data, word changeID, ManufacturerID manufID);
This message updates all
UI
components for the recipient controller.
Source: Sent by
GenControlClass
in its default handler for MSG_META_NOTIFY_WITH_DATA_BLOCK.
Destination: The GenControl object being updated.
Parameters:
toolBlock
Handle of the object resource block containing the controller's tool UI gadgetry.
childBlock
TEMP_GEN_CONTROL_INSTANCE
vardata field.
toolboxFeatures
TEMP_GEN_CONTROL_INSTANCE
vardata field. If the toolbox UI is not interactible, then this field will be zero.
features
TEMP_GEN_CONTROL_INSTANCE
vardata field. If the UI is not interactible, then this field will be zero.
data
changeID
manufID
Interception: Controllers should intercept this message in order to properly update their UI gadgetry. There is no default handler for this message.
Structures: The
TEMP_GEN_CONTROL_INSTANCE
vardata field is of type
TempGenControlInstance
, which has the following structure:
typedef struct { GenControlInteractableFlags TGCI_interactableFlags; MemHandle TGCI_childBlock; MemHandle TGCI_toolBlock; optr TGCI_toolParent; WordFlags TGCI_features; WordFlags TGCI_toolboxFeatures; GCNListType TGCI_activeNotificationList; GenControlInteractableFlags TGCI_upToDate; } TempGenControlInstance;
TGCI_interactableFlags
TGCI_childBlock
TGCI_toolBlock
TGCI_toolParent
MSG_GEN_CONTROL_GENERATE_TOOLBOX_UI
, if any (tools will be added to this object).
TGCI_features
TGCI_toolboxFeatures
TGCI_activeNotificationList
TGCI_upToDate
GenControlInteractableFlags
at the time of the last notification; that is, which portions of the controller's UI were up to date. This is used by the specific UI for drawing optimizations.
The flags for the
GenControlInteractableFlags
record are listed below:
void MSG_GEN_CONTROL_ENABLE_DISABLE( Message msg; VisUpdateMode updateMode);
This message enables or disables the controller object as well as its default and tool box UI gadgetry.
Source: Sent by
GenControlClass
to the controller object when it receives
MSG_META_NOTIFY_WITH_DATA_BLOCK
.
Destination: Sent by controller to itself.
Parameters:
msg
Either
MSG_GEN_SET_ENABLED
or
MSG_GEN_SET_NOT_ENABLED
as appropriate.
updateMode
VisUpdateMode
indicating when the visual update should occur.Interception: Unlikely--typically should not be intercepted.
void MSG_GEN_CONTROL_ADD_APP_UI( optr appUI);
This message adds the passed UI object to the controller's generic tree as if it had been originally defined in the default child block. By default, the new object is added as the last child of the controller.
Source: Unrestricted--generated as part of the default functionality of
MSG_GEN_CONTROL_GENERATE_UI
if the controller has
ATTR_GEN_CONTROL_APP_UI
set.
Destination: Any GenControl object.
Parameters:
appUI
The optr of the object to be added.
Interception: Should be intercepted by controllers that wish to add the new object somewhere other than as the last child.
void MSG_GEN_CONTROL_ADD_APP_TOOLBOX_UI( optr appUI);
This message adds the passed UI object to the controller's tool UI gadgetry as if it had been defined as a tool in the tool resource block. By default, the new object is added as the last child of the controller.
Source: Unrestricted--generated as part of the default functionality of
MSG_GEN_CONTROL_GENERATE_TOOLBOX_UI
if the controller has
ATTR_GEN_CONTROL_APP_TOOLBOX_UI
set.
Destination: Any GenControl object.
Parameters:
appUI
The optr of the object to be added.
Interception: Should be intercepted by controllers that wish to add the new object somewhere other than as the last child.
void MSG_GEN_CONTROL_REBUILD_NORMAL_UI();
This message forces the normal UI of the controller to be rebuilt; each component will be visually destroyed and rebuilt.
Source: Unrestricted.
Destination: Any GenControl object.
Interception: Should not be intercepted.
void MSG_GEN_CONTROL_REBUILD_TOOLBOX_UI();
This message forces the toolbox UI of the controller to be rebuilt; each component will be visually destroyed and rebuilt.
Source: Unrestricted.
Destination: Any GenControl object.
Interception: Should not be intercepted.
MSG_GEN_CONTROL_SCAN_FEATURE_HINTS, MSG_GEN_CONTROL_ADD_FEATURE, MSG_GEN_CONTROL_REMOVE_FEATURE, MSG_GEN_CONTROL_ADD_TOOLBOX_FEATURE, MSG_GEN_CONTROL_REMOVE_TOOLBOX_FEATURE, MSG_GEN_CONTROL_GET_NORMAL_FEATURES, MSG_GEN_CONTROL_GET_TOOLBOX_FEATURES
Besides being able to set and clear features of a given controller, both the controller class and outside agents can dynamically alter the features of a given controller object.
GenControlClass
has several messages that you can use for this purpose; these messages are detailed below.
void MSG_GEN_CONTROL_SCAN_FEATURE_HINTS( GenControlUIType type, GenControlScanInfo *info);
This message scans the feature hints set for the controller object to set the required and prohibited features.
Source: Unrestricted--Sent by
GenControlClass
to itself in numerous circumstances.
Destination: The GenControl object to be scanned.
Parameters:
type
An indicator whether the normal or tool box UI hints are to be scanned. This should be GCUIT_NORMAL for the normal hints, GCUIT_TOOLBOX for the tool box hints.
info
GenControlScanInfo
structure to be filled in by the handler. This structure is shown below.Return: No value is returned directly.
info
GenControlScanInfo
structure filled in by the method.Interception: Should not be intercepted.
Structures:
The
GenControlScanInfo
structure has the following fields:
typedef struct { WordFlags GCSI_userAdded; WordFlags GCSI_userRemoved; WordFlags GCSI_appRequired; WordFlags GCSI_appProhibited; } GenControlScanInfo;
GCSI_userAdded
MSG_GEN_CONTROL_ADD_FEATURE
.
GCSI_userRemoved
GCSI_appRequired
ATTR_GEN_CONTROL_REQUIRE_TOOLBOX_UI
or
ATTR_GEN_CONTROL_REQUIRE_UI
.
GCSI_appProhibited
ATTR_GEN_CONTROL_PROHIBIT_TOOLBOX_UI
or
ATTR_GEN_CONTROL_PROHIBIT_UI
.void MSG_GEN_CONTROL_ADD_FEATURE( WordFlags featureToAdd);
This message adds a feature to those currently supported by the controller. This is used for the default settings only, not for tool box UI. The controller is destroyed and then rebuilt with the new feature, causing it to be marked for saving to the state file in the new configuration.
Source: Unrestricted.
Destination: Any GenControl object.
Parameters:
featureToAdd
A feature record with the flag of the feature to be added set.
Interception: Should not be intercepted.
void MSG_GEN_CONTROL_REMOVE_FEATURE WordFlags featureToRemove);
This message removes a feature from those currently supported by the controller. It does not affect the active tools. The controller will be marked for saving to the state file in the new configuration; it is destroyed and rebuilt with feature removed.
Source: Unrestricted.
Destination: Any GenControl object.
Parameters:
featureToRemove
A feature record with the flag of the feature to be removed set.
Interception: Should not be intercepted.
void MSG_GEN_CONTROL_ADD_TOOLBOX_FEATURE( WordFlags featureToAdd);
This message adds a tool to those currently supported by the controller. This is used for the tool box settings only, not for the default UI features. The controller is destroyed and then rebuilt with the new tool, causing it to be marked for saving to the state file in the new configuration.
Source: Unrestricted.
Destination: Any GenControl object.
Parameters:
featureToAdd
A feature record with the flag of the to be added set.
Interception: Should not be intercepted.
void MSG_GEN_CONTROL_REMOVE_TOOLBOX_FEATURE( WordFlags featureToRemove);
This message removes a tool from those currently supported by the controller. It does not affect the default active feature list. The controller will be marked for saving to the state file in the new configuration; it is destroyed and rebuilt with the tool removed.
Source: Unrestricted.
Destination: Any GenControl object.
Parameters:
featureToRemove
A feature record with the flag of the tool to be removed set.
Interception: Should not be intercepted.
void MSG_GEN_CONTROL_GET_NORMAL_FEATURES( GenControlGetFeaturesReturn *return);
This message returns a structure indicating which of the default features of the controller are currently active, which are required, and which are prohibited.
Source: Unrestricted--typically GenToolControl.
Destination: Any GenControl object.
Parameters:
return
A pointer to an empty structure to be returned.
Return: The
return
parameter, upon return, points to a filled
GenControlGetFeaturesReturn
structure.
Structures:
The
GenControlGetFeaturesReturn
structure is shown below:
typedef struct { WordFlags GCSR_features; WordFlags GCSR_required; WordFlags GCSR_prohibited; WordFlags GCSR_supported; } GenControlGetFeaturesReturn;
GCSR_features
GCSR_required
GCSR_prohibited
GCSR_supported
void MSG_GEN_CONTROL_GET_TOOLBOX_FEATURES( GenControlGetFeaturesReturn *return);
This message returns a structure indicating which of the controller's tools are currently active, which are required, and which are prohibited.
Source: Unrestricted--typically GenToolControl.
Destination: Any GenControl object.
Parameters:
return
A pointer to an empty structure to be returned.
Return: The
return
parameter, upon return, points to a filled
GenControlGetFeaturesReturn
structure.
Structures: The
GenControlGetFeaturesReturn
structure is shown in
MSG_GEN_CONTROL_GET_NORMAL_FEATURES
, above.
MSG_GEN_CONTROL_ADD_TO_GCN_LISTS, MSG_GEN_CONTROL_REMOVE_FROM_GCN_LISTS
Because
GenControlClass
uses GCN lists, it has two messages that add itself to and remove itself from the lists. You can intercept or send these if you need to; applications generally will not, however. These two messages are detailed below.
void MSG_GEN_CONTROL_ADD_TO_GCN_LISTS();
This message adds the controller object to the GCN lists specified by its return value of
MSG_GEN_CONTROL_GET_INFO
. It will force a status update to ensure that the controller updates itself.
Source: Generated internally on startup and at other times.
Destination: Sent to self.
Interception: Generally not intercepted. Subclasses should use this only to see when the controller is being added to its lists; it should call the superclass to do the actual addition.
void MSG_GEN_CONTROL_REMOVE_FROM_GCN_LISTS();
This message removes the controller from all its GCN lists.
Source: Generated internally on shutdown and at other times.
Destination: Sent to self.
Interception: Generally not intercepted. Subclasses should use this only to see when the controller is being removed from its lists; it should call the superclass to do the actual removal.
MSG_GEN_CONTROL_NOTIFY_INTERACTABLE, MSG_GEN_CONTROL_NOTIFY_NOT_INTERACTABLE, MSG_GEN_CONTROL_UNBUILD_NORMAL_UI_IF_POSSIBLE
Because controllers are generic objects which may or may not be interactable,
GenControlClass
has two messages to handle the interactable state. It has an additional message to close the normal UI tools, if possible. These three messages are detailed below.
void MSG_GEN_CONTROL_NOTIFY_INTERACTABLE( GenControlInteractableFlags flags);
This message instructs the controller to take any actions necessary before being put on the screen and made interactable. It causes the controller to add itself to its GCN lists (if it wasn't already) and take any final steps to get ready to go on the screen.
Source: Generated Internally--do not generate externally.
Destination: Sent to self.
Parameters:
flags
A single record of flags indicating which portions of the controller will be made interactable.
Interception: May be intercepted to circumvent default behavior.
void MSG_GEN_CONTROL_NOTIFY_NOT_INTERACTABLE( GenControlInteractableFlags flags);
This message indicates that the UI has determined that the controller can no longer be seen or interacted with by the user. The default behavior of the controller is to remove itself from its GCN lists for optimization.
Source: Generated Internally--do not generate externally.
Destination: Sent to self.
Parameters:
flags
A single record of flags indicating which portions of the controller are no longer interactable.
Interception: May be intercepted to circumvent default behavior.
void MSG_GEN_CONTROL_UNBUILD_NORMAL_UI_IF_POSSIBLE();
This internal message requests that the normal default controller UI gadgetry be removed and destroyed if they are not in use. This is an optimization intended to save swap space and perhaps memory space; it causes the objects to be loaded back in again when needed, however. Thus, the optimization is only suited to machines with limited swap space (it originated due to these conditions on palmtop machines).
Source: Generated internally. Do not generate externally.
Destination: Sent to self.
Interception: May be intercepted to avoid the optimization. May also need to be intercepted if a subclass creates its own UI gadgetry by intercepting
MSG_GEN_CONTROL_GENERATE_UI
.


Visualizing Conservation Interventions and Outcomes
Order:
-----
Reset Intervention Order
Reset Outcome Order
Reset All Order


{% extends 'main/base.html' %} {% load staticfiles %} {% load crispy_forms_tags %} {% block head_title %} NeuroPower | {{block.super}} {% endblock %} {% block navbar %} {% include 'main/navbar.html' %} {%include 'design/designnavbar.html' %} {% endblock %} {% block content %}
This toolbox helps researchers with the planning of experimental designs for fMRI experiments. In short: depending on the exact time and order of stimulus presentations, a study can achieve higher statistical power or efficiency for estimating the brain signal. As such, depending on the design criteria, you'll have more power with fewer subjects or with shorter experiments. For more details about the methods, please see the methods section, or take a look at the step-by-step tutorial on this page. Do you want to know how to run an optimisation on your computer without the GUI, go to the package information page.
You're looking at the first version of the design efficiency toolbox. We need input ! Any feedback is welcome: visual, aesthetical, user friendliness, bugs,... If you were redirected to a 404 or 500 page, we probably got a very detailed report of what went wrong, but feel free to give more details.
We want to make this toolbox as useful as possible. If you're currently planning a study and your design requires specific options that are not in here, let us know ! We might include it. If you have other ideas on how to extend or improve this toolbox, just fill out the form below.
Here are some ideas on our plate:
Depending on the feedback, we will make a list of potential new features and bugs and prioritise accordingly !


Wufoo
Kitchen Sink
This is my form. Please fill it out. It's awesome!
Simple Text Field
Number
Paragraph Field
Checkboxes
First Choice
Second Choice
Third Choice
Select a Choice
First Choice
Second Choice
Third Choice
Select a Choice
First Choice
Second Choice
Third Choice
Section Break
A description of the section goes here.
Name
First
Last
Attach a File
Address
Street Address
Address Line 2
City
State / Province / Region
Postal / Zip Code
United States
United Kingdom
Australia
Canada
France
New Zealand
India
Brazil
----
Afghanistan
Åland Islands
Albania
Algeria
American Samoa
Andorra
Angola
Anguilla
Antarctica
Antigua and Barbuda
Argentina
Armenia
Aruba
Austria
Azerbaijan
Bahamas
Bahrain
Bangladesh
Barbados
Belarus
Belgium
Belize
Benin
Bhutan
Bolivia
Bosnia and Herzegovina
Botswana
British Indian Ocean Territory
Brunei Darussalam
Bulgaria
Burkina Faso
Burundi
Cambodia
Cameroon
Cape Verde
Central African Republic
Chad
Chile
China
Colombia
Comoros
Democratic Republic of the Congo
Republic of the Congo
Cook Islands
Costa Rica
Côte d'Ivoire
Croatia
Cuba
Cyprus
Czech Republic
Denmark
Djibouti
Dominica
Dominican Republic
East Timor
Ecuador
Egypt
El Salvador
Equatorial Guinea
Eritrea
Estonia
Ethiopia
Faroe Islands
Fiji
Finland
Gabon
Gambia
Georgia
Germany
Ghana
Greece
Grenada
Guatemala
Guinea
Guinea-Bissau
Guyana
Haiti
Honduras
Hong Kong
Hungary
Iceland
Indonesia
Iran
Iraq
Ireland
Israel
Italy
Jamaica
Japan
Jordan
Kazakhstan
Kenya
Kiribati
North Korea
South Korea
Kuwait
Kyrgyzstan
Laos
Latvia
Lebanon
Lesotho
Liberia
Libya
Liechtenstein
Lithuania
Luxembourg
Macedonia
Madagascar
Malawi
Malaysia
Maldives
Mali
Malta
Marshall Islands
Mauritania
Mauritius
Mexico
Micronesia
Moldova
Monaco
Mongolia
Montenegro
Morocco
Mozambique
Myanmar
Namibia
Nauru
Nepal
Netherlands
Netherlands Antilles
Nicaragua
Niger
Nigeria
Norway
Oman
Pakistan
Palau
Panama
Papua New Guinea
Paraguay
Peru
Philippines
Poland
Portugal
Puerto Rico
Qatar
Romania
Russia
Rwanda
Saint Kitts and Nevis
Saint Lucia
Saint Vincent and the Grenadines
Samoa
San Marino
Sao Tome and Principe
Saudi Arabia
Senegal
Serbia and Montenegro
Seychelles
Sierra Leone
Singapore
Slovakia
Slovenia
Solomon Islands
Somalia
South Africa
Spain
Sri Lanka
Sudan
Suriname
Swaziland
Sweden
Switzerland
Syria
Taiwan
Tajikistan
Tanzania
Thailand
Togo
Tonga
Trinidad and Tobago
Tunisia
Turkey
Turkmenistan
Tuvalu
Uganda
Ukraine
United Arab Emirates
United States Minor Outlying Islands
Uruguay
Uzbekistan
Vanuatu
Vatican City
Venezuela
Vietnam
Virgin Islands, British
Virgin Islands, U.S.
Yemen
Zambia
Zimbabwe
Country
Date
MM
/
DD
/
YYYY
Email
Time
HH
:
MM
:
SS
AM
PM
AM/PM
Phone Number
###
-
###
-
####
Web Site
Price
$
Dollars
.
Cents
Evaluate the following statements.
Strongly Disagree
Disagree
Agree
Strongly Agree
Statement One
1
2
3
4
Statement Two
1
2
3
4
Statement Three
1
2
3
4


Class: Aws::OpsWorks::Types::AutoScalingThresholds
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
::Aws::Structure ,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb |
Overview
Describes a load-based auto scaling upscaling or downscaling threshold configuration, which specifies when AWS OpsWorks Stacks starts or stops load-based instances.
Constant Summary
Instance Attribute Summary
-
#alarms ⇒ Array<String>
rw
Custom Cloudwatch auto scaling alarms, to be used as thresholds.
-
#cpu_threshold ⇒ Float
rw
The CPU utilization threshold, as a percent of the available CPU.
-
#ignore_metrics_time ⇒ Integer
rw
The amount of time (in minutes) after a scaling event occurs that AWS OpsWorks Stacks should ignore metrics and suppress additional scaling events.
-
#instance_count ⇒ Integer
rw
The number of instances to add or remove when the load exceeds a threshold.
-
#load_threshold ⇒ Float
rw
The load threshold.
-
#memory_threshold ⇒ Float
rw
The memory utilization threshold, as a percent of the available memory.
-
#thresholds_wait_time ⇒ Integer
rw
The amount of time, in minutes, that the load must exceed a threshold before more instances are added or removed.
Instance Method Summary
::Aws::Structure
- Included
| #to_hash | Alias for Structure#to_h. |
Instance Attribute Details
#alarms ⇒ Array
<String
> (rw)
Custom Cloudwatch auto scaling alarms, to be used as thresholds. This parameter takes a list of up to five alarm names, which are case sensitive and must be in the same region as the stack.
cloudwatch:DescribeAlarms
. You can either have AWS OpsWorks Stacks
update the role for you when you first use this feature or you can
edit the role manually. For more information, see Allowing AWS
::Aws::OpsWorks
Stacks to Act on Your Behalf.
# File 'gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb', line 263
class AutoScalingThresholds < Struct.new( :instance_count, :thresholds_wait_time, :ignore_metrics_time, :cpu_threshold, :memory_threshold, :load_threshold, :alarms) SENSITIVE = [] include Aws::Structure end
#cpu_threshold ⇒ Float
(rw)
The CPU utilization threshold, as a percent of the available CPU. A value of -1 disables the threshold.
# File 'gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb', line 263
class AutoScalingThresholds < Struct.new( :instance_count, :thresholds_wait_time, :ignore_metrics_time, :cpu_threshold, :memory_threshold, :load_threshold, :alarms) SENSITIVE = [] include Aws::Structure end
#ignore_metrics_time ⇒ Integer
(rw)
The amount of time (in minutes) after a scaling event occurs that
AWS OpsWorks Stacks should ignore metrics and suppress additional
scaling events. For example, AWS OpsWorks Stacks adds new instances
following an upscaling event but the instances won't start reducing
the load until they have been booted and configured. There is no
point in raising additional scaling events during that operation,
which typically takes several minutes. IgnoreMetricsTime
allows
you to direct AWS OpsWorks Stacks to suppress scaling events long
enough to get the new instances online.
# File 'gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb', line 263
class AutoScalingThresholds < Struct.new( :instance_count, :thresholds_wait_time, :ignore_metrics_time, :cpu_threshold, :memory_threshold, :load_threshold, :alarms) SENSITIVE = [] include Aws::Structure end
#instance_count ⇒ Integer
(rw)
The number of instances to add or remove when the load exceeds a threshold.
# File 'gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb', line 263
class AutoScalingThresholds < Struct.new( :instance_count, :thresholds_wait_time, :ignore_metrics_time, :cpu_threshold, :memory_threshold, :load_threshold, :alarms) SENSITIVE = [] include Aws::Structure end
#load_threshold ⇒ Float
(rw)
The load threshold. A value of -1 disables the threshold. For more information about how load is computed, see Load (computing).
# File 'gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb', line 263
class AutoScalingThresholds < Struct.new( :instance_count, :thresholds_wait_time, :ignore_metrics_time, :cpu_threshold, :memory_threshold, :load_threshold, :alarms) SENSITIVE = [] include Aws::Structure end
#memory_threshold ⇒ Float
(rw)
The memory utilization threshold, as a percent of the available memory. A value of -1 disables the threshold.
# File 'gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb', line 263
class AutoScalingThresholds < Struct.new( :instance_count, :thresholds_wait_time, :ignore_metrics_time, :cpu_threshold, :memory_threshold, :load_threshold, :alarms) SENSITIVE = [] include Aws::Structure end
#thresholds_wait_time ⇒ Integer
(rw)
The amount of time, in minutes, that the load must exceed a threshold before more instances are added or removed.
# File 'gems/aws-sdk-opsworks/lib/aws-sdk-opsworks/types.rb', line 263
class AutoScalingThresholds < Struct.new( :instance_count, :thresholds_wait_time, :ignore_metrics_time, :cpu_threshold, :memory_threshold, :load_threshold, :alarms) SENSITIVE = [] include Aws::Structure end


The homeworks will be posted here. There will be three homeworks and a tournament will happened at the final week. The homeworks will be classic comprehension programming assignments. The tournament will require you solving a two player game (like tic-tac-toe). We will play the game in class to determine the winner. All reasonable players (i.e., no crashing) will get equal credits.
Late Submission Policy: You are highly encouraged to submit homeworks on time. If you submit late you will loose 1 point for each day passed after the deadline (where 1 point = 1/20 of the total homework points).
- HW1, due 06/11, 15h: .html, .lhs download
- Tournament, due 17/11: .html
- HW2, due 02/12, 15h: .html, .lhs download


We Can Code Week 5: Multiplayer Games and Networking
wolfram74.github.io/wcc_index.html
Real time (continuous) vs turn based (discrete)
Local vs Networked
Same Machine Discrete
Same Machine Continuous
Local area
Client-Server
Peer-to-Peer
Synchronizing State
Size of complete state?
Transaction based updates
Deterministic Mechanics
Complicated Design question with lots of room for exploration


WARNING: Mushroom hunting is very dangerous. We take no responsibility for any misidentification, misshandling or ingestion of toxic substances.


Two
NOUN (plural)
, both alike in dignity,
In fair
PLACE
, where we lay our scene,
From ancient
NOUN
break to new mutiny,
Where civil blood makes civil hands unclean.
From forth the fatal loins of these two foes
A pair of star-cross`d
NOUN (plural)
take their life;
Whole misadventured piteous overthrows
Do with their
NOUN
bury their parents` strife.
The fearful passage of their
ADJECTIVE
love,
And the continuance of their parents` rage,
Which, but their children`s end, nought could
VERB
,
Is now the
NUMBER
hours` traffic of our stage;
The which if you with
ADJECTIVE
BODY PART
attend,
What here shall
VERB
, our toil shall strive to mend.


This is a recreation of Tetris. Use The Left & Right Arrows to move left and right. You can press the Down Arrow to "Soft Drop". The Up Arrow and Q will rotate right. CTRL and E will rotate left. (Not Simultaneously for rotation) You can press Space for a "Hard Drop". Press Shift to swap HOLD. Fill up 100 Lines to win.


pyamgx Reference¶
-
exception
pyamgx.
AMGXError
¶ Exception class for errors returned from calls to AMGX routines.
-
class
pyamgx.
Config
¶ Config: Class for creating and handling AMGX Config objects.
-
create
(options)¶ Create the underlying AMGX Config object from a configuration string.
Parameters: options (str or bytes_like) – AMGX configuration string. Returns: self Return type: Config
-
create_from_dict
(param_file)¶ Create the underlying AMGX Config object from a dictionary.
Parameters: params (dict) – Dictionary with configuration options.
-
create_from_file
(param_file)¶ Create the underlying AMGX Config object from a configuration file.
Parameters: param_file (str or bytes_like) – Path to configuration file.
-
destroy
()¶ Destroy the underlying AMGX Config object.
-
-
class
pyamgx.
Matrix
¶ Matrix : Class for creating and handling AMGX Matrix objects.
Examples
Uploading the matrix
[[1, 2], [3, 4]]
using the upload method:>>> import pyamgx, numpy as np >>> pyamgx.initialize() >>> cfg = pyamgx.Config().create("") >>> rsrc = pyamgx.Resources().create_simple(cfg) >>> M = pyamgx.Matrix().create(rsrc) >>> M.upload( ... row_ptrs=np.array([0, 2, 4], dtype=np.int32), ... col_indices=np.array([0, 1, 0, 1], dtype=np.int32), ... data=np.array([1., 2., 3., 4.], dtype=np.float64)) >>> M.destroy() >>> rsrc.destroy() >>> cfg.destroy() >>> pyamgx.finalize()
-
create
(Resources rsrc, mode='dDDI')¶ Create the underlying AMGX Matrix object.
Parameters: Returns: self
Return type:
-
destroy
()¶ Destroy the underlying AMGX Matrix object.
-
get_size
()¶ Get the matrix size (in block units), and the block dimensions.
Returns: - n (int) – The matrix size (number of rows/columns) in block units.
- block_dims (tuple) – A tuple (bx, by) representing the size of the blocks in the x- and y- dimensions.
-
replace_coefficients
(data)¶ Replace matrix coefficients without changing the nonzero structure.
Parameters: data (array_like) – Array of matrix data.
-
upload
(row_ptrs, col_indices, data, block_dims=[1, 1])¶ Copy data from arrays describing the sparse matrix to the Matrix object.
Parameters: - row_ptrs (array_like) – Array of row pointers. For a description of the arrays row_ptrs, col_indices and data, see here.
- col_indices (array_like) – Array of column indices.
- data (array_like) – Array of matrix data.
- block_dims (tuple_like, optional) – Dimensions of block in x- and y- directions. Currently only square blocks are supported, so block_dims[0] should be equal to block_dims[1].
Returns: self
Return type:
-
upload_CSR
(csr)¶ Copy data from a
scipy.sparse.csr_matrix
to the Matrix object.Parameters: csr (scipy.sparse.csr_matrix) – Returns: self Return type: Matrix
-
-
class
pyamgx.
Resources
¶ Resources: Class for creating and freeing AMGX Resources objects.
-
create_simple
(cfg)¶ Create the underlying AMGX Resources object in a single-threaded application.
Parameters: cfg (Config) – Returns: self Return type: Resources
-
destroy
()¶ Destroy the underlying AMGX Resources object.
-
-
class
pyamgx.
Solver
¶ Solver: Class for creating and handling AMGX Solver objects.
-
create
(Resources rsrc, Config cfg, mode='dDDI')¶ Create the underlying AMGX Solver object
Parameters:
-
destroy
()¶ Destroy the underlying AMGX Solver object.
-
get_residual
(iteration, block_idx)¶ Get the value of the residual for a given iteration from the last solve phase.
Parameters: Returns: res – Value of residual at specified iteration.
Return type:
-
iterations_number
¶ The number of iterations that were executed during the last solve phase.
-
setup
(A)¶ Invoke the set up phase.
Parameters: A (Matrix) – The Matrix representing the coefficient matrix of the equation to be solved.
-
solve
(Vector rhs, Vector sol)¶ Invoke the solve phase.
Parameters: - b (Vector) – The Vector representing the right-hand side of the equation to be solved.
- x (Vector) – The Vector representing the solution vector of the equation to be solved. If zero_initial_guess is unspecified, the values in x are used as the initial guess for iterative algorithms.
- zero_initial_guess (bool, optional) – If True, use an initial guess of zero for the solution, regardless of the values in x.
-
status
¶ The status from the last solve phase.
-
-
class
pyamgx.
Vector
¶ Vector: Class for creating and handling AMGX Vector objects.
Examples
Creating a vector, uploading values from a numpy array, and downloading values back to a numpy array:
>>> import pyamgx, numpy as np >>> pyamgx.initialize() >>> cfg = pyamgx.Config().create("") >>> rsrc = pyamgx.Resources().create_simple(cfg) >>> v = pyamgx.Vector().create(rsrc) >>> v.upload(np.array([1., 2., 3.,], dtype=np.float64)) >>> v.download() array([ 1., 1., 1.]) >>> v.destroy() >>> rsrc.destroy() >>> cfg.destroy() >>> pyamgx.finalize()
-
create
(Resources rsrc, mode='dDDI')¶ Create the underlying AMGX Vector object.
Parameters: Returns: self
Return type:
-
destroy
()¶ Destroy the underlying AMGX Vector object.
-
download
(data)¶ Copy data from the Vector to an array.
Parameters: data (array, ndim=1) – Array to copy data to.
-
download_raw
(ptr)¶ Copy data from the Vector to an array, given a raw pointer to the array.
Parameters: ptr (pointer) – An integer (or long integer, if required) that points to the array containing data
-
get_size
()¶ Get the size of the vector (in block units), and the block size.
Returns: - n (int) – The size of the vector in block units.
- block_dim (int) – The block size.
-
set_zero
(n=None, block_dim=None)¶ Allocate storage if needed and set all the values in the vector to zero.
Parameters: - n (int, optional) – Number of entries in the vector, in block units. If not provided or None, then the values must have been previously initialized using e.g., v.upload().
- block_dim (int, optional) –
Number of values per block. If not provided or None, then the values must have been previously
initialized using e.g., v.upload().
-
upload
(data, block_dim=1)¶ Copy data to the Vector from an array.
Parameters: - data (array_like, ndim=1) – Array to copy data from.
- block_dim (int, optional) – Number of values per block.
Returns: self
Return type:
-
upload_raw
(ptr, n, block_dim=1)¶ Copy data to the Vector from an array, given a raw pointer to the array.
Parameters:
-
-
pyamgx.
check_error
(err_code)¶ Raise AMGXError for non-zero values of err_code.
Parameters: err_code (RC) – Error code returned from call to an AMGX routine.
-
pyamgx.
finalize
()¶ Finalize AMGX.
-
pyamgx.
get_api_version
()¶ Return the API version of AMGX as a string.
Returns: version – String continaing major and minor API version information. Return type: str
-
pyamgx.
get_error_string
(err_code)¶ Return a human-readable error string corresponding to an error code.
Parameters: err_code (RC) – Error code returned from call to an AMGX routine. Returns: err_str – Human-readable error string. Return type: str
-
pyamgx.
initialize
()¶ Initialize AMGX.
-
pyamgx.
install_signal_handler
()¶ Cause AMGX to install its default signal handlers.
-
pyamgx.
pin_memory
()¶ Notify the operating system that the underlying buffer of data is to be pinned to reside in physical memory.
Parameters: data (numpy.ndarray, double) – The array containing data to be pinned.
-
pyamgx.
read_system
()¶ Read linear system from a MatrixMarket file.
Parameters:
-
pyamgx.
register_print_callback
(f)¶ Register a user-provided callback function for handling text output from calls to AMGX functions. The callback function should accept a single argument (a string containing the text output).
Parameters: f (function) – Python function that accepts a string as input Examples
>>> import pyamgx >>> import time >>> import pyamgx >>> pyamgx.initialize() >>> pyamgx.register_print_callback(lambda msg: print('{}: {}'.format(time.asctime(), msg))) >>> cfg = pyamgx.Config().create("") Fri Aug 10 07:23:25 2018: Cannot read file as JSON object, trying as AMGX config >>> cfg.destroy() >>> pyamgx.finalize()
-
pyamgx.
reset_signal_handler
()¶ Cause AMGX to restore previous signal handlers.
-
pyamgx.
unpin_memory
()¶ Notify the operating system that the underlying buffer of data is to be unpinned
Parameters: data (numpy.ndarray, double) – The array containing data to be unpinned.


Hello MR..
I'm Ayoub Kandah from Jordan, I graduated with a bachelor's degree in risk management and insurance
from the Hashemite university. I worked in insurance company in motor claim.
I have a tendency in programming and design, so I learned programming in the Unity Engine (C#).
learned design in many programs such as
- Photoshop
- After Effects
- 3d max
My favorite programs and web applications :


Configuration Handling¶
New in version 0.3.
Applications need some kind of configuration. There are different settings you might want to change depending on the application environment like toggling the debug mode, setting the secret key, and other such environment-specific things.
The way Flask is designed usually requires the configuration to be available when the application starts up. You can hardcode the configuration in the code, which for many small applications is not actually that bad, but there are better ways.
Independent of how you load your config, there is a config object
available which holds the loaded configuration values:
The config
attribute of the Flask
object. This is the place where Flask itself puts certain configuration
values and also where extensions can put their configuration values. But
this is also where you can have your own configuration.
Configuration Basics¶
The config
is actually a subclass of a dictionary and
can be modified just like any dictionary:
app = Flask(__name__)
app.config['DEBUG'] = True
Certain configuration values are also forwarded to the
Flask
object so you can read and write them from there:
app.debug = True
To update multiple keys at once you can use the dict.update()
method:
app.config.update(
DEBUG=True,
SECRET_KEY='...'
)
Builtin Configuration Values¶
The following configuration values are used internally by Flask:
DEBUG |
enable/disable debug mode |
TESTING |
enable/disable testing mode |
PROPAGATE_EXCEPTIONS |
explicitly enable or disable the propagation of exceptions. If not set or explicitly set to None this is implicitly true if either TESTING or DEBUG is true. |
PRESERVE_CONTEXT_ON_EXCEPTION |
By default if the application is in debug mode the request context is not popped on exceptions to enable debuggers to introspect the data. This can be disabled by this key. You can also use this setting to force-enable it for non debug execution which might be useful to debug production applications (but also very risky). |
SECRET_KEY |
the secret key |
SESSION_COOKIE_NAME |
the name of the session cookie |
SESSION_COOKIE_DOMAIN |
the domain for the session cookie. If
this is not set, the cookie will be
valid for all subdomains of
SERVER_NAME . |
SESSION_COOKIE_PATH |
the path for the session cookie. If
this is not set the cookie will be valid
for all of APPLICATION_ROOT or if
that is not set for '/' . |
SESSION_COOKIE_HTTPONLY |
controls if the cookie should be set with the httponly flag. Defaults to True. |
SESSION_COOKIE_SECURE |
controls if the cookie should be set with the secure flag. Defaults to False. |
PERMANENT_SESSION_LIFETIME |
the lifetime of a permanent session as
datetime.timedelta object.
Starting with Flask 0.8 this can also be
an integer representing seconds. |
USE_X_SENDFILE |
enable/disable x-sendfile |
LOGGER_NAME |
the name of the logger |
SERVER_NAME |
the name and port number of the server.
Required for subdomain support (e.g.:
'myapp.dev:5000' ) Note that
localhost does not support subdomains so
setting this to “localhost” does not
help. Setting a SERVER_NAME also
by default enables URL generation
without a request context but with an
application context. |
APPLICATION_ROOT |
If the application does not occupy
a whole domain or subdomain this can
be set to the path where the application
is configured to live. This is for
session cookie as path value. If
domains are used, this should be
None . |
MAX_CONTENT_LENGTH |
If set to a value in bytes, Flask will reject incoming requests with a content length greater than this by returning a 413 status code. |
SEND_FILE_MAX_AGE_DEFAULT : |
Default cache control max age to use with
send_static_file() (the
default static file handler) and
send_file() , in
seconds. Override this value on a per-file
basis using the
get_send_file_max_age()
hook on Flask or
Blueprint ,
respectively. Defaults to 43200 (12 hours). |
TRAP_HTTP_EXCEPTIONS |
If this is set to True Flask will
not execute the error handlers of HTTP
exceptions but instead treat the
exception like any other and bubble it
through the exception stack. This is
helpful for hairy debugging situations
where you have to find out where an HTTP
exception is coming from. |
TRAP_BAD_REQUEST_ERRORS |
Werkzeug’s internal data structures that
deal with request specific data will
raise special key errors that are also
bad request exceptions. Likewise many
operations can implicitly fail with a
BadRequest exception for consistency.
Since it’s nice for debugging to know
why exactly it failed this flag can be
used to debug those situations. If this
config is set to True you will get
a regular traceback instead. |
PREFERRED_URL_SCHEME |
The URL scheme that should be used for
URL generation if no URL scheme is
available. This defaults to http . |
JSON_AS_ASCII |
By default Flask serialize object to
ascii-encoded JSON. If this is set to
False Flask will not encode to ASCII
and output strings as-is and return
unicode strings. jsonfiy will
automatically encode it in utf-8
then for transport for instance. |
JSON_SORT_KEYS |
By default Flask will serialize JSON objects in a way that the keys are ordered. This is done in order to ensure that independent of the hash seed of the dictionary the return value will be consistent to not trash external HTTP caches. You can override the default behavior by changing this variable. This is not recommended but might give you a performance improvement on the cost of cachability. |
JSONIFY_PRETTYPRINT_REGULAR |
If this is set to True (the default)
jsonify responses will be pretty printed
if they are not requested by an
XMLHttpRequest object (controlled by
the X-Requested-With header) |
More on SERVER_NAME
The SERVER_NAME
key is used for the subdomain support. Because
Flask cannot guess the subdomain part without the knowledge of the
actual server name, this is required if you want to work with
subdomains. This is also used for the session cookie.
Please keep in mind that not only Flask has the problem of not knowing
what subdomains are, your web browser does as well. Most modern web
browsers will not allow cross-subdomain cookies to be set on a
server name without dots in it. So if your server name is
'localhost'
you will not be able to set a cookie for
'localhost'
and every subdomain of it. Please chose a different
server name in that case, like 'myapplication.local'
and add
this name + the subdomains you want to use into your host config
or setup a local bind.
New in version 0.4: LOGGER_NAME
New in version 0.5: SERVER_NAME
New in version 0.6: MAX_CONTENT_LENGTH
New in version 0.7: PROPAGATE_EXCEPTIONS
, PRESERVE_CONTEXT_ON_EXCEPTION
New in version 0.8: TRAP_BAD_REQUEST_ERRORS
, TRAP_HTTP_EXCEPTIONS
,
APPLICATION_ROOT
, SESSION_COOKIE_DOMAIN
,
SESSION_COOKIE_PATH
, SESSION_COOKIE_HTTPONLY
,
SESSION_COOKIE_SECURE
New in version 0.9: PREFERRED_URL_SCHEME
New in version 0.10: JSON_AS_ASCII
, JSON_SORT_KEYS
, JSONIFY_PRETTYPRINT_REGULAR
Configuring from Files¶
Configuration becomes more useful if you can store it in a separate file, ideally located outside the actual application package. This makes packaging and distributing your application possible via various package handling tools (Deploying with Distribute) and finally modifying the configuration file afterwards.
So a common pattern is this:
app = Flask(__name__)
app.config.from_object('yourapplication.default_settings')
app.config.from_envvar('YOURAPPLICATION_SETTINGS')
This first loads the configuration from the
yourapplication.default_settings module and then overrides the values
with the contents of the file the YOURAPPLICATION_SETTINGS
environment variable points to. This environment variable can be set on
Linux or OS X with the export command in the shell before starting the
server:
$ export YOURAPPLICATION_SETTINGS=/path/to/settings.cfg
$ python run-app.py
* Running on http://<IP_ADDRESS>:5000/
* Restarting with reloader...
On Windows systems use the set builtin instead:
>set YOURAPPLICATION_SETTINGS=\path\to\settings.cfg
The configuration files themselves are actual Python files. Only values in uppercase are actually stored in the config object later on. So make sure to use uppercase letters for your config keys.
Here is an example of a configuration file:
# Example configuration
DEBUG = False
SECRET_KEY = '?\xbf,\xb4\x8d\xa3"<\x9c\xb0@\x0f5\xab,w\xee\x8d$0\x13\x8b83'
Make sure to load the configuration very early on, so that extensions have
the ability to access the configuration when starting up. There are other
methods on the config object as well to load from individual files. For a
complete reference, read the Config
object’s
documentation.
Configuration Best Practices¶
The downside with the approach mentioned earlier is that it makes testing a little harder. There is no single 100% solution for this problem in general, but there are a couple of things you can keep in mind to improve that experience:
- create your application in a function and register blueprints on it. That way you can create multiple instances of your application with different configurations attached which makes unittesting a lot easier. You can use this to pass in configuration as needed.
- Do not write code that needs the configuration at import time. If you limit yourself to request-only accesses to the configuration you can reconfigure the object later on as needed.
Development / Production¶
Most applications need more than one configuration. There should be at least separate configurations for the production server and the one used during development. The easiest way to handle this is to use a default configuration that is always loaded and part of the version control, and a separate configuration that overrides the values as necessary as mentioned in the example above:
app = Flask(__name__)
app.config.from_object('yourapplication.default_settings')
app.config.from_envvar('YOURAPPLICATION_SETTINGS')
Then you just have to add a separate config.py file and export
YOURAPPLICATION_SETTINGS=/path/to/config.py
and you are done. However
there are alternative ways as well. For example you could use imports or
subclassing.
What is very popular in the Django world is to make the import explicit in
the config file by adding an from yourapplication.default_settings
import *
to the top of the file and then overriding the changes by hand.
You could also inspect an environment variable like
YOURAPPLICATION_MODE
and set that to production, development etc
and import different hardcoded files based on that.
An interesting pattern is also to use classes and inheritance for configuration:
class Config(object):
DEBUG = False
TESTING = False
DATABASE_URI = 'sqlite://:memory:'
class ProductionConfig(Config):
DATABASE_URI = 'mysql://user@localhost/foo'
class DevelopmentConfig(Config):
DEBUG = True
class TestingConfig(Config):
TESTING = True
To enable such a config you just have to call into
from_object()
:
app.config.from_object('configmodule.ProductionConfig')
There are many different ways and it’s up to you how you want to manage your configuration files. However here a list of good recommendations:
- keep a default configuration in version control. Either populate the config with this default configuration or import it in your own configuration files before overriding values.
- use an environment variable to switch between the configurations. This can be done from outside the Python interpreter and makes development and deployment much easier because you can quickly and easily switch between different configs without having to touch the code at all. If you are working often on different projects you can even create your own script for sourcing that activates a virtualenv and exports the development configuration for you.
- Use a tool like fabric in production to push code and configurations separately to the production server(s). For some details about how to do that, head over to the Deploying with Fabric pattern.
Instance Folders¶
New in version 0.8.
Flask 0.8 introduces instance folders. Flask for a long time made it
possible to refer to paths relative to the application’s folder directly
(via Flask.root_path
). This was also how many developers loaded
configurations stored next to the application. Unfortunately however this
only works well if applications are not packages in which case the root
path refers to the contents of the package.
With Flask 0.8 a new attribute was introduced:
Flask.instance_path
. It refers to a new concept called the
“instance folder”. The instance folder is designed to not be under
version control and be deployment specific. It’s the perfect place to
drop things that either change at runtime or configuration files.
You can either explicitly provide the path of the instance folder when creating the Flask application or you can let Flask autodetect the instance folder. For explicit configuration use the instance_path parameter:
app = Flask(__name__, instance_path='/path/to/instance/folder')
Please keep in mind that this path must be absolute when provided.
If the instance_path parameter is not provided the following default locations are used:
Uninstalled module:
/myapp.py /instance
Uninstalled package:
/myapp /__init__.py /instance
Installed module or package:
$PREFIX/lib/python2.X/site-packages/myapp $PREFIX/var/myapp-instance
$PREFIX
is the prefix of your Python installation. This can be/usr
or the path to your virtualenv. You can print the value ofsys.prefix
to see what the prefix is set to.
Since the config object provided loading of configuration files from relative filenames we made it possible to change the loading via filenames to be relative to the instance path if wanted. The behavior of relative paths in config files can be flipped between “relative to the application root” (the default) to “relative to instance folder” via the instance_relative_config switch to the application constructor:
app = Flask(__name__, instance_relative_config=True)
Here is a full example of how to configure Flask to preload the config from a module and then override the config from a file in the config folder if it exists:
app = Flask(__name__, instance_relative_config=True)
app.config.from_object('yourapplication.default_settings')
app.config.from_pyfile('application.cfg', silent=True)
The path to the instance folder can be found via the
Flask.instance_path
. Flask also provides a shortcut to open a
file from the instance folder with Flask.open_instance_resource()
.
Example usage for both:
filename = os.path.join(app.instance_path, 'application.cfg')
with open(filename) as f:
config = f.read()
# or via open_instance_resource:
with app.open_instance_resource('application.cfg') as f:
config = f.read()


This is a text with a to another page.
This is a text with a to another page in a new window.
This is a text with a .
This is a text with an the link.
This is a text with .


Claim for HPCDS
2. Submissions
All submissions must be made in a timely manner and as such no claims should be submitted after 6 months from the date the client received help at court.
If the HPCDS fee has already been claimed before the legal help matter is opened then you should notify<EMAIL_ADDRESS>of the need to amend the report. The Provider Assurance team will retrospectively tick the ‘Legal Help’ field in the relevant report, make a note in the ‘notes’ field and recoup the fee paid. You should report the Legal Help claim in the usual way.
Please note that HPCDS cases which go on to receive Legal Help will still be counted as HPCDS acts of assistance for the purposes of your allocation and performance.
Payments are triggered by our receipt of fully completed monthly reporting spreadsheet (HPCDS Contract Report Form v1.4) on or before their respective due date. Payment will be delayed if reports are not received on time. Guidance is available at Annex 4 which offers help with how to complete the monthly reporting spreadsheet.
Submit online
You can submit your claim online. The online service will:
- reminder and confirmation notifications
- check the data for errors
- tell you how much and when to expect your payment
- display historical claims
Submit via email
You can submit via email. This is a more basic service and you should expect longer payment periods.
Send your contract report form to hpcdsreports@legalaid.gsi.gov.uk


Warning:
jsMath
requires JavaScript to process the mathematics on this page.
If your browser supports JavaScript, be sure it is enabled.
jsMath Image Mode Test Page
this is math formula
\left(\, \sum_{k=1}^n a_k b_k \right)^2 \le \left(\, \sum_{k=1}^n a_k^2 \right) \left(\, \sum_{k=1}^n b_k^2 \right)
... and the string after it
this is math formula
\left(\, \sum_{k=1}^n a_k b_k \right)^2 \le \left(\, \sum_{k=1}^n a_k^2 \right) \left(\, \sum_{k=1}^n b_k^2 \right)
... and the string after it


Your e-mail address for [[SITENAME]] has been changed
E-mail changed mail
Dear [[USERNAME]]
Your e-mail address for your account at [[SITENAME]] has been changed from [[OLDEMAIL]] to [[NEWEMAIL]]. You will receive a verification mail at your new address.


| Current | Average | |
|---|---|---|
| Connections | - | - |
| Requests | - | - |
| Req / Conn | - | - |
| Bandwidth | - | - |
| Current | Average | |
|---|---|---|
| Hit Ratio | - | - |
| Hits | - | - |
| Misses | - | - |
| Cache Size | - | - |
| Current | Average | |
|---|---|---|
| Connections | - | - |
| Fetch & Pass | - | - |
| Fails | - | - |
| Reuse | - | - |
| Current | Average | |
|---|---|---|
| Workers Created | - | - |
| SHM writes | - | - |
| ESI Errors/Warnings | - | - |
| Accept Failures | - | - |


@(params: Map[String, Any]) @uk.gov.hmrc.hmrcemailrenderer.templates.helpers.html.template_main(params, "Your HMRC agent services link to view client records") {
Dear @{params("name")}
This email contains a link to a new service for agents where you can view the income and tax records of your clients.
Click on this unique link to access this service. Do not give it to anyone else.
From the HMRC Digital team
}


Web Build
Last Updated May 14th, 2021
Download Versions:
Update Log
May 14th, 2021
- Uploaded final version of the game! That inludes...
- Added Options Menu (Toggleable Controls + Volume Sliders)
- Added Credits Screen (with New Music Track!)
- Added More Enemy Models (Generic Enemy Statue + Bondrewg)
- Reworked Pop-Up Menus
- Reworked Audio Balancing
April 17th, 2021
- Added a start menu (with unique music!)
- Added a new gameplay song (that is fully charted)
- Added screenshake effect
- Includes more voxel models
- Reworked background visual elements
- Reworked weapon selection (once every level)
March 16th, 2021
- Contains five brand new levels (that are decorated!)
- Contains new enemy: "Bondrewg"
- Includes tutorial pop-ups explaining core gameplay
- Includes additional visual effects (note hexagon, attack pop-up, death explosion, etc.)
- Reworked note sprites
- Reworked shaders (tile + enemies)
February 22nd, 2021
- Contains three full levels with different obstacles, terrains, and goals
- Contains new enemy: "Gnath"
- Includes two weapons (Bow + Axe)
- Includes floating damage numbers
- Various enhancements to the rhythm gameplay
- Gameplay song has been charted (Notes are in sync with music)
January 25th, 2021:
- Contains hub world with two NPCs
- Contains two test levels and one full level
- Includes four weapons
- Contains one song with notes
{% include about-card.html %}
{% include navigation-menu.html %}


Day Planner
current date
Current events
Upcoming events
Future events
9am
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
10am
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
11am
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
12noon
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
1pm
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
2pm
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
3pm
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
4pm
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save
5pm
Select:
Chore
Meeting
Check
Errand
Web
Interview
Call
Schedule
Miscelaneous
Save


StealJS is a collection of command line and JavaScript client utilities
that make building, packaging, and sharing
JavaScript applications easy. Lets see what it can do:
Loads JS, CSS, Less, CoffeeScript, and client-side templates.
Parallel loading.
Works with scripts that don't use steal.
steal('widgets/tabs.js',
'./style.css',
function(Tabs){
new Tabs("#item");
});
JS/CSS concatenation and minification (steal.build)
steal.build combines and minfies an application (or application's) resources
into a small number of minified packages for faster downloading. Features:
Minifies JS, Less, CoffeeScript, and client-side templates.
StealJS is a collection of command line and JavaScript client utilities that make building, packaging, and sharing JavaScript applications easy. Lets see what it can do:
Dependency management (steal)
steal loads modules into your app. Features:
JS/CSS concatenation and minification (steal.build)
steal.build combines and minfies an application (or application's) resources into a small number of minified packages for faster downloading. Features:
Logging (steal.dev)
steal.dev logs messages cross browser. Messages are removed in production builds.
Code generators (steal.generate)
steal.generate makes building code generators extremely easy. Features:
Code cleaner (steal.clean)
steal.clean cleans your code and checks it against JSLint.
Searchable ajax apps (steal.html)
steal.html makes Google-crawlable html from your ajax app.


Connect
Select
Action
Another action
Something else here
Compose
blogger-mdn
About
Copyright (c) 2020 Prahlad Yeri. blogger-mdn is
Free Software
v1.0


There exist numerous methods to authenticate a user to a system, but using only passwords continues to be the dominating choice [1, 2]. Under these circumstances, ideally, a user would have strong, unique passwords for each account that he or she has. However, this is an unrealistic expectation for the average human being. Thus largely, the general population uses a handful of weak passwords for all of their user accounts.[3, 4, 5, 6]
At an attempt to alleviate this problem, password managers were introduced. A password manager is a program that stores and organizes all of a user's passwords. Access to a user's passwords in the password manager typically requires knowledge of a "master password." This pushes the burden of remembering strong, unique passwords from the human user to a software application.
Fairly often, the topic will come up whether to use a password manager or not. It is argued back and forth. In my opinion, password managers are one of the best things since sliced bread. There's no better feeling than using a random 50 character password or using openssl rand -base64 5
output as an answer to a security question (I use 5 bytes because if I want to get anything done with a support line over the phone, it's more realistic to spell out a 7 character string than 50 character string).
I've noticed, though, that many tech savvy people are reluctant to adopt such a technology. I know plenty of security professionals that use either the same password for all accounts or use a handful of passwords in a tiered fashion (one password for important accounts, another for less sensitive accounts, another for the ones they care about even less, and so on). The average non-technical person, in my experience, is quick to adopt password managers once they discover such apps, but it's frustrating to me how information security professionals are so stubborn to do the same.
The biggest excuse I hear is probably "I don't want all my eggs in one basket," though there are others [7]. At first, this tradeoff makes it unclear whether using a password manager is any safer than the traditional method of memorization. To tackle this problem, we really need to change the way we think about password managers. They shouldn't be thought of as "password vaults," but "password strengtheners." Here, I will describe the proper way to utilize password managers such that they are in theory no less safe than using pure memorization.
Assume user Alice is currently using a 2-tier password scheme with the passwords \(P_1\) for important accounts (email, bank) and \(P_2\) for the rest of her accounts. In this scenario, we will require Alice to come up with a separate master password. The strength of the master password does not actually matter as our proof does not rely on it.
To login to her bank account, Alice should take the password entry in the password manager for her bank account, and incorporate it with her password \(P_1\). "Incorporate" entails somehow merging the two -- most likely prepending or appending the entry to \(P_1\). The idea is the password entry in her password manager adds to the strength and complexity of her original password \(P_1\). A similar method should also be adopted for accounts with password \(P_2\).
Notice how other than retrieving the password from the password manger, the way Alice uses her passwords does not need to change. As we have seen she still "uses" password \(P_1\) for important accounts and can use \(P_2\) for less sensitive accounts. The password manager passwords merely strengthened her original passwords.
Now, let's revisit the "eggs in one basket" problem again. There are two scenarios:
- Alice's password vault is somehow compromised (e.g. LastPass vendor compromise [8] or Tavis Ormandy ;) [9]). In this case, the strength of her passwords falls back to the original strength of \(P_1\) for important accounts and \(P_2\) for the rest of her accounts.
- Alice's computer is compromised, e.g. infected with malware. In this case, we can assume the password vault would also be compromised since it just takes unlocking it once for malware to log the master password. At this point, the security of her accounts, password-wise, is in the same state as it was in situation 1. We can thus conclude, again, that the strength of her passwords falls back to \(P_1\) or \(P_2\) (that, and both \(P_1\) and \(P_2\) are logged by the malware once she attempts to logging into accounts).
In both situations, the use of a password manager isn't any less safe than traditional memorization alone in theory. The proposed method does not solely rely on the password manager for the security of Alice's account; its function is to strengthen her existing passwords.
The caveat here is, as you probably guessed, the phrase "in theory." In reality, it's a little more nuanced than the above scenarios and their assumptions. The password manager technically does open up attack surface. As an example, when I open 1Password on macOS, it opens up a few ports. Port 49506 is the port used for local LAN syncing of passwords between devices (which can be disabled in the app).
$ sudo lsof -iTCP -sTCP:LISTEN -P -n | awk '{print $1, $3, $5, $9, $10}' | column -t
COMMAND USER TYPE NAME
...
2BUA8C4S2 kedy IPv4 *:49506 (LISTEN)
2BUA8C4S2 kedy IPv6 *:49506 (LISTEN)
2BUA8C4S2 kedy IPv4 <IP_ADDRESS>:6258 (LISTEN)
2BUA8C4S2 kedy IPv6 [::1]:6258 (LISTEN)
2BUA8C4S2 kedy IPv4 <IP_ADDRESS>:6263 (LISTEN)
2BUA8C4S2 kedy IPv6 [::1]:6263 (LISTEN)
<IP_ADDRESS>
increases the attack surface. Therefore, the chance of falling into situation 2 above increases. Though given the choice of picking between a slightly increased attack surface vs strong passwords, I would pick the latter any day.
Lastly, I'll note that using this method of password managers means that you won't be able to use any accompanying password manager browser extensions. Although honestly, you probably shouldn't be anyway -- copy pasting is the safest way to go. In addition, you should also consider
- avoiding the builtin browser
- avoid using the cloud to sync passwords
- disabling any listening services if possible, or block the listening ports with your host firewall
- sync password vault manually (e.g. use iExplorer to transfer 1Password's sqlite db)
[1] http://research.microsoft.com/pubs/161585/QuestToReplacePasswords.pdf
[2] http://users.ics.forth.gr/~elathan/papers/eurosec15.pdf
[3] http://cyberside.planet.ee/docs/www2007-A%20Large-Scale%20Study%20of%20Web%20Password%20Habits.pdf
[4] https://cups.cs.cmu.edu/soups/2006/proceedings/p44_gaw.pdf
[5] http://www.canberra.edu.au/cis/storage/CIS_PayPal_Whitepaper_FINAL.pdf
[6] http://www.csid.com/wp-content/uploads/2012/09/CS_PasswordSurvey_FullReport_FINAL.pdf
[7] https://www.internetsociety.org/sites/default/files/08%20why-do-people-adopt-or-reject-smartphone-password-managers.pdf
[8] https://blog.lastpass.com/2015/06/lastpass-security-notice.html/
[9] P0 issue 884, 888, 890