| | |
- builtins.object
-
- Authorizer
class Authorizer(builtins.object) |
| |
Authorizer(user_arg=-1)
Authorizes new users, gets credentials for existing users
Can authorize via all four tokens (consumer and access) or
just using the consumer and a verification pin from a link.
Users can protect their API credentials with a password if they want
Creates the OAuth object used to make API calls |
| |
Methods defined here:
- __init__(self, user_arg=-1)
- Sets up instance variable username
:param user_arg: optional argument for a username
- ask_for_password(self)
- Asks new users if they would like to use a password
:return: Returns true if the user wants to use a password,
false if they do not want to use a password
- authorize(self)
- Walks the user through either creating a new user, or logging into a previous one
User files are saved as username.enc and contain an encrypted string containing the
user's tokens
Also handles checking with verification method (tokens or link) the user will use
:return: an OAuthHandler object that can be used to create an API object
- decrypt_user(self, password)
- Decrypts the username.enc file, formats it into a list of tokens
:param username: the chosen username
:param password: the user's password
:return: a list of the API tokens needed to authenticate the user
- encrypt_tokens(self, password, keys_list)
- Encrypts a list of tokens in a .enc file for users with passwords
:param password: the user's password
:param keys_list: the four API tokens needed to authenticate the user in a list
:return: the four API tokens needed to authenticate the user
- get_access_tokens(self)
- Gets the access tokens directly from the user
:return: the access_token and access_secret
- get_csv_tokens(self)
- Gets the API credentials from an existing user's user.csv file
:return: the four API tokens needed to authenticate the user
- get_password(self)
- Gets the user's password, or helps user create one
:return: a password as a string
- get_tokens(self, password)
- Gets the four tokens needed for authentication, encrypts them as a string in username.enc
:param password: the user's password to encrypt the tokens
:return: unencrypted consumer_token, consumer_secret, access_token, access_secret
- get_verification_pin(self, auth)
- Gets the URL to get the verification pin
:param auth: the OAuthHandler object that, when given a pin, produces access tokens
:return: the access_token and access_secret for the user
- handle_user(self, password)
- Handles returning the tokens if the user exists
Otherwise, calls get_tokens()
:param password: the user's password
:return: consumer_token, consumer_secret, access_token, access_secret
- has_password(self)
- Checks if the user is using a password to encrypt their credentials
:param username: the chosen username
:return: True if the user has encrypted their credentials with a password,
False if they are not using a password
- split_keys(self, keys_list)
- Takes a list of keys and splits them into variables
:param keys_list: a list of API tokens
:return: the four API tokens needed to authenticate the user
- store_tokens(self, keys_list)
- Stores a list of tokens in a CSV file for users without passwords
:param keys_list: a list of API tokens
:return: the four API tokens needed to authenticate the user
- user_exists(self)
- Checks if a user's .enc or .csv file exists
:param username: the chosen username
:return: True if it exists, false if otherwise
Data descriptors defined here:
- __dict__
- dictionary for instance variables (if defined)
- __weakref__
- list of weak references to the object (if defined)
| |


Why not using car pool lane?
Do you know USF has carpool permit?
Find people near you who will riding with you.
Meet people who is your college.
Find drivers near you who will share the riding.
Be a nice passenger and enjoy.
Login with your USF account
Start Now


Bootstrap Dual Listbox is a responsive dual listbox widget optimized for Twitter Bootstrap. It works on all modern browsers and on touch devices.
The dual listbox is created from a select multiple by calling .bootstrapDualListbox(settings);
on a selector. The selector can be any element, not just selects. When the method is called on a selector other than a select, then all select childrens are converted into dual list boxes.
var demo1 = $('[name="duallistbox_demo1[]"]').bootstrapDualListbox();
$('.demo2').bootstrapDualListbox({ nonselectedlistlabel: 'Non-selected', selectedlistlabel: 'Selected', preserveselectiononmove: 'moved', moveonselect: false, initialfilterfrom: 'ion ([7-9]|[1][0-2])' });
The options must be added to/removed from the original select.
Note that the bootstrapduallistbox.refresh
event must be triggered on it after manipulating the options.
If there are some highlighted options in the lists, then triggering the bootstrapduallistbox.refresh
event with the optional true
parameter results the highlights to be removed. Example usage: demo2.trigger('bootstrapduallistbox.refresh', true)
It has meaning only when moveonselect
setting is false
.
$("#demo2-add").click(function(){ demo2.append('<option value="apples">Apples</option><option value="oranges" selected>Oranges</option>'); demo2.trigger('bootstrapduallistbox.refresh'); }); $("#demo2-add-clear").click(function(){ demo2.append('<option value="apples">Apples</option><option value="oranges" selected>Oranges</option>'); demo2.trigger('bootstrapduallistbox.refresh', true); });
bootstrap2compatible
false
: Enable for Bootstrap 2.x compatibility.preserveselectiononmove
false
: Selections are cleared on move. This is the forced setting on Android because of a bug.'moved'
: Selection is cleared in the list where the options are moved to, and the moved options are selected after move.'all'
: Selection is preserved between the lists, so the previously selected options are selected even after moving them or other options into their list.moveonselect
true
: The options are automatically moved on selection. This setting is forced on touch devices.false
: The selected options can be moved with a button.initialfilterfrom
''
: This is the initial value of the filter for the unselected values (left side). Default is empty string.initialfilterto
''
: This is the initial value of the filter for the selected values (on the right). Default is empty string.helperselectnamepostfix
'_helper'
: when set, the helper selects are submitted with the original selects name postfixed with this value.false
: the helper selects are not submitted.infotext
'Showing all {0}'
: this is the info text when no filter applied to the options list and the list is not empty.false
: None of the info texts are visible.
infotextfiltered
'<col-md- class="label label-warning">Filtered</col-md-> {0} from {1}'
: this is the info text when not all of the options are visible.infotextempty
'Empty list'
: this is the info text when the list is empty.selectorminimalheight
100
: this is the minimal height of the rendered selects in pixels (normally they inherit the original selects height, but this is 0 in a modal when duallistbox is initialized, so this will be the height in such cases).filterplaceholder
'Filter'
: this is the text of the placeholder for the filter fieldfiltertextclear
'show all'
: this is the text on the button which clears the filtersnonselectedlistlabel
false
: This label is not displayed. Default option.'string'
: The label for the non-selected options listselectedlistlabel
false
: This label is not displayed. Default option.'string'
: The label for the selected options list


{% extends "blog/base.html" %} {% load crispy_forms_tags %} {% block title %}Search{% endblock %} {% block content %}
There are no results for your query.


Changing a user's name
Note: To use this tool, you must have
administrator rights.
To change a user's name, follow these steps:
- From your My Workspace, click the
Users
tab. This will display a list of users defined within the system.
- Under "User Id", click the username of the user you want to edit.
- Edit the "First Name:" and/or "Last Name:" field(s) as you wish,
and then click
Save
.


2. Declarations, Variables, and Method Call Styles
Declarations, Variables, and Method Chaining
Variables in Sandpiper may be set exactly once, making them immutable. You use the hash-rocket =>
to assign them a value.
doge-body => my-doge: rest
Traditional variable assignment is like putting a value into a bucket. In sandpiper, it’s a declaration—a declaration that some name (doge-body
) is equivalent to the value of some expression (my-doge: rest
).
To declare that variable without assigning anything to it yet, use the syntax
there-is doge-body.
This is a kind of “keyword declaration,” which we’ll discuss later. Assignment-free variable declarations won’t be immediately useful, but they’re important to know about.
As an example, we can re-do our earlier string replace by splitting it into pieces, and joining them back together. One way to accomplish this is through a pair of declarations:
pieces => “hoge, fuga, piyo”: split “, ”.
replaced => pieces: join “ ”.
Each declaration ends in a period—this is necessary when you have more than one declaration in a row.
We can simplify this code by chaining the method calls together:
replaced => “hoge, fuga, piyo”: split “, ”: join “ ”.
Implicit Method Calls
You can omit the colon after the receiver in a method call.
“foo”: replace “o” with “!”.
“foo” replace “o” with “!”. ;; same
5: * 3.
5 * 3. ;; same
Doing so comes with a number of intrinsic limitations—particularly, you can only omit the colon where the syntax doesn’t become ambiguous; and call chaining is not possible. For instance, 5 * 3 - 10
won’t give you 5. It’ll look for the *()-()
method, and not be able to find it. Any of the following will work, however:
5: * 3: - 10. ;; explicit
5 * 3: - 10. ;; the first method call in a chain can be implicit
(5 * 3) - 10. ;; otherwise disambiguated
It should be clear, at this point, why the simple arithmetic operators don’t have precedence over one another. They’re chained linearly, left-to-right, like any other methods.
A Brief Introduction to Types
So far, we’ve been writing ducktyped code, that looks and feels like ducktyping in Ruby, Python, Smalltalk, etc. In fact, all Sandpiper code is strongly typed, but it allows you to completely ignore type information in most circumstances, if it’s not helpful for your code. We’ll just briefly touch on Types here.
A type is a set of methods, and can be a class of objects. For instance, the literal “doge”
is an object of type Text
, which tells you how you can interact with it—what methods you can call on it.
In a variable declaration, the variable’s “declaration point,” to this point, has just been the variable’s name. It can also contain the name of the variable’s type in parentheses after the name. For instance, you can re-write
there-is doge.
doge-body => doge: rest.
as
there-is doge (List).
doge-body (List) => doge: rest.
The value Nil
cannot be the value of a variable with a specific, simple type like List
. Nil
has its own class, NilClass
, which doesn’t inherit from Object
. To allow such a variable to refer to Nil as well, you can suffix it with a question mark, to make it Optional: List?
. (While you can’t use an Object
-type variable to refer to Nil, you can use one typed Any
.)
The compiler will infer the types of variables as much as possible. Specifying them explicitly tells Sandpiper to make sure that your variables hold the exact type you’re expecting when the program runs. To the extent that it can do this at compile time, the compiler will make sure all your types line up, and warn you when they don’t. When it can’t do this, it will insert runtime checks. Specifying a variable’s type isn’t usually useful at inline declarations, but can be essential when declaring new classes.


This tool is designed to assist in musical composition and to show which chords in the major/ionian and minor/aeolian modes are most commonly used according to Common Practice. The buttons within the chord boxes are arranged best to worst from top to bottom.


A domain to use when setting cookies, overriding the SSO Domain set in
Crowd (since Crowd 2.5.2). When an SSO Domain is set in Crowd, all
client applications must be in the same domain so cookies can be
shared. A Crowd deployment may have hosts with no common domain suffix,
for example 'domain.example.com' and 'domain.internal'. Even though a
user has already logged in to 'domain.example.com' and has a cookie
set, applications running under 'domain.internal' will not receive this
cookie since the domains differ, and users will be unable to log in.
Set this property in the crowd client application to override the
domain. Applications within the same domain will then be able to share
SSO sessions.
Crowd
configuration documentation


- GasBrake - Static variable in class com.apw.apw3.TrakSim
-
- GasPin - Variable in class com.apw.carcontrol.TrakSimControl
-
- GasServo - Static variable in class com.apw.apw3.TrakSim
-
- getAllBlobs(byte[], int) - Method in class com.apw.pedestrians.PedestrianDetector
-
- getBip(int, int, int, int, IPixel) - Method in class com.apw.pedestrians.blobdetect.BlobDetection
-
- getBlackWhiteRaster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getBlob(BlobDetection.BlobInProgress) - Method in class com.apw.pedestrians.blobdetect.BlobDetection
-
- getBlob(int) - Method in class com.apw.pedestrians.blobdetect.PrimitiveBlobDetection
-
- getBlobs(IImage) - Method in class com.apw.pedestrians.blobdetect.BlobDetection
-
- getBlobs(IImage) - Method in interface com.apw.pedestrians.blobdetect.IBlobDetection
-
- getBlobs(IImage) - Method in class com.apw.pedestrians.blobdetect.PrimitiveBlobDetection
-
- getBlobs() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getBuffersBytesCount(long) - Method in class jssc.SerialNativeInterface
-
Get bytes count in buffers of port
- getBWRGBRaster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getCalibrator() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getColor() - Method in interface com.apw.pedestrians.image.IPixel
-
- getColor() - Method in class com.apw.pedestrians.image.Pixel
-
- getDegreeOffset() - Method in class com.apw.Steering.SteeringBase
-
Gets the degree offset between the origin (center bottom of the screen), and the steerPoint (The point
where the car is attempting to steer towards).
- getDensity() - Method in class com.apw.pedestrians.blobtrack.MovingBlob
-
- getDensity() - Method in class com.apw.pedestrians.blobtrack.UnifiedBlob
-
- getDesiredSpeed() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getEdges() - Method in interface com.apw.carcontrol.CarControl
-
Gets the edges of the screen (if one exists).
- getEdges() - Method in class com.apw.carcontrol.TrakSimControl
-
- getEmergencyStop() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getEstimatedSpeed() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getEventsMask(long) - Method in class jssc.SerialNativeInterface
-
Get events mask
- getEventsMask() - Method in class jssc.SerialPort
-
Getting events mask for the port
- getEventType() - Method in class jssc.SerialPortEvent
-
Getting event type
- getEventValue() - Method in class jssc.SerialPortEvent
-
Getting event value
Event values depending on their types:
RXCHAR - bytes count in input buffer
RXFLAG - bytes count in input buffer (Not supported in Linux)
TXEMPTY - bytes count in output buffer
CTS - state of CTS line (0 - OFF, 1 - ON)
DSR - state of DSR line (0 - OFF, 1 - ON)
RLSD - state of RLSD line (0 - OFF, 1 - ON)
BREAK - 0
RING - state of RING line (0 - OFF, 1 - ON)
ERR - mask of errors
- getExceptionType() - Method in exception jssc.SerialPortException
-
Getting exception type
- GetFacing() - Method in class com.apw.apw3.TrakSim
-
- getFilteredUnifiedBlobs(List<MovingBlob>) - Method in interface com.apw.pedestrians.blobtrack.IMovingBlobDetection
-
- getFilteredUnifiedBlobs(List<MovingBlob>) - Method in class com.apw.pedestrians.blobtrack.MovingBlobDetection
-
- getFlowControlMode(long) - Method in class jssc.SerialNativeInterface
-
Get flow control mode
- getFlowControlMode() - Method in class jssc.SerialPort
-
Get flow control mode
- GetFrameNo() - Method in class com.apw.apw3.TrakSim
-
Gets the current frame count.
- getGas() - Method in interface com.apw.carcontrol.CarControl
-
Gets the current gas (velocity) of the car.
- getGas() - Method in class com.apw.carcontrol.TrakSimControl
-
- getHeight() - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getImage() - Method in interface com.apw.pedestrians.image.IImage
-
- GetImgWide() - Method in class com.apw.apw3.TrakSim
-
Gets the width of the image file (if loaded), or else =0.
- getInputBufferBytesCount() - Method in class jssc.SerialPort
-
Get count of bytes in input buffer
- getLibraryBaseVersion() - Static method in class jssc.SerialNativeInterface
-
Get jSSC Base Version
- getLibraryMinorSuffix() - Static method in class jssc.SerialNativeInterface
-
Get jSSC minor suffix.
- getLibraryVersion() - Static method in class jssc.SerialNativeInterface
-
Get jSSC version.
- getLinesStatus(long) - Method in class jssc.SerialNativeInterface
-
Getting lines states
- getLinesStatus() - Method in class jssc.SerialPort
-
Getting lines status.
- getLinuxMask() - Method in class jssc.SerialPort
-
Getting events mask for the port is Linux OS (for internal use)
- getManualSpeed() - Method in interface com.apw.carcontrol.CarControl
-
Gets the manual speed control of the car.
- getManualSpeed() - Method in class com.apw.carcontrol.TrakSimControl
-
- GetMapSize() - Method in class com.apw.apw3.TrakSim
-
Gets the actual map size as read in from the file.
- getMethodName() - Method in exception jssc.SerialPortException
-
Getting method name during execution of which the exception was called
- getMethodName() - Method in exception jssc.SerialPortTimeoutException
-
Getting method name during execution of which the exception was called
- getMono() - Method in class com.apw.gpu.BlackWhiteRasterKernel
-
Returns a monochrome bayer byte array,
Should be called to retrieve result after kernel is executed.
- getMono() - Method in class com.apw.gpu.BWToRGBKernel
-
Returns a monochromatic raw rgb pixel array,
Should be called to retrieve result after kernel is executed.
- getMono() - Method in class com.apw.gpu.MonochromeRasterKernel
-
Returns a monochrome bayer byte array,
Should be called to retrieve result after kernel is executed.
- getMonochrome2Raster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getMonochromeRaster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getMonoRGB2Raster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getMonoRGBRaster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getMovingBlobs(List<Blob>) - Method in interface com.apw.pedestrians.blobtrack.IMovingBlobDetection
-
- getMovingBlobs(List<Blob>) - Method in class com.apw.pedestrians.blobtrack.MovingBlobDetection
-
- getMovingBlobs() - Method in class com.apw.pedestrians.blobtrack.MovingBlobDetection
-
- GetMyScreenAry() - Method in class com.apw.apw3.TrakSim
-
Gets a pointer to the current image TrakSim is drawing on.
- GetMyScreenDims() - Method in class com.apw.apw3.TrakSim
-
Gets the size of the current image TrakSim is drawing on.
- getNativeLibraryVersion() - Static method in class jssc.SerialNativeInterface
-
Get jSSC native library version
- getNcols() - Method in class com.apw.ImageManagement.ImagePicker
-
- getNewEventThread() - Method in class jssc.SerialPort
-
Create new EventListener Thread depending on the type of operating system
- getNextSpeed() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getNrows() - Method in class com.apw.ImageManagement.ImagePicker
-
- getOsType() - Static method in class jssc.SerialNativeInterface
-
Get OS type (OS_LINUX || OS_WINDOWS || OS_SOLARIS)
- getOutputBufferBytesCount() - Method in class jssc.SerialPort
-
Get count of bytes in output buffer
- getPixel(byte) - Method in class com.apw.pedestrians.PedestrianDetector
-
- getPixels() - Method in class com.apw.ImageManagement.ImagePicker
-
- getPortName() - Method in class jssc.SerialPort
-
Getting port name under operation
- getPortName() - Method in class jssc.SerialPortEvent
-
Getting port name which sent the event
- getPortName() - Method in exception jssc.SerialPortException
-
Getting port name during operation with which the exception was called
- getPortName() - Method in exception jssc.SerialPortTimeoutException
-
Getting port name during operation with which the exception was called
- getPortNames() - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system using default settings:
Search path
Windows - ""(always ignored)
Linux - "/dev/"
Solaris - "/dev/term/"
MacOSX - "/dev/"
RegExp
Windows - ""
Linux - "(ttyS|ttyUSB|ttyACM|ttyAMA|rfcomm)[0-9]{1,3}"
Solaris - "[0-9]*|[a-z]*"
MacOSX - "tty.(serial|usbserial|usbmodem).*"
- getPortNames(String) - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system located on searchPath
- getPortNames(Pattern) - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system matched pattern
- getPortNames(Comparator<String>) - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system matched pattern
- getPortNames(String, Pattern) - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system located on searchPath, matched pattern
- getPortNames(String, Comparator<String>) - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system located on searchPath and sorted by comparator
- getPortNames(Pattern, Comparator<String>) - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system matched pattern and sorted by comparator
- getPortNames(String, Pattern, Comparator<String>) - Static method in class jssc.SerialPortList
-
Get sorted array of serial ports in the system located on searchPath, matched pattern and sorted by comparator
- GetPosn(boolean) - Method in class com.apw.apw3.TrakSim
-
Gets one coordinate of the current car position.
- getProcessedImage() - Method in interface com.apw.carcontrol.CarControl
-
Gets a processed image.
- getProcessedImage() - Method in class com.apw.carcontrol.TrakSimControl
-
- getRecentCameraImage() - Method in interface com.apw.carcontrol.CarControl
-
- getRecentCameraImage() - Method in class com.apw.carcontrol.TrakSimControl
-
- getRenderedImage() - Method in class com.apw.carcontrol.TrakSimControl
-
Gets the image to be rendered on the screen.
- getRGB() - Method in class com.apw.gpu.MonoToRGBKernel
-
Returns raw rgb pixel array,
Should be called to retrieve result after kernel is executed.
- getRgb() - Method in class com.apw.gpu.RGBRasterKernel
-
Returns an rgb raster of a bayer byte array,
Should be called to retrieve result after kernel is executed.
- getRGBImage() - Method in interface com.apw.carcontrol.CarControl
-
- getRGBImage() - Method in class com.apw.carcontrol.TrakSimControl
-
- getRGBRaster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getScaledVelocityX() - Method in class com.apw.pedestrians.blobtrack.MovingBlob
-
This method is used to scale the X velocity of the MovingBlob.
- getScaledVelocityY() - Method in class com.apw.pedestrians.blobtrack.MovingBlob
-
This method is used to scale the Y velocity of the MovingBlob.
- getSerialPortNames() - Method in class jssc.SerialNativeInterface
-
Get serial port names like an array of String
- GetSimFrame(int, int, byte[]) - Method in class com.apw.apw3.TrakSim
-
Essentially the same as NextFrame in fly2cam.FlyCamera.
- getSimple() - Method in class com.apw.gpu.SimpleColorRasterKernel
-
Returns an simple color raster of a bayer byte array,
Should be called to retrieve result after kernel is executed.
- getSimpleColorRaster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getSimpleRGB() - Method in class com.apw.gpu.SimpleToRGBKernel
-
Returns a simple 5 color raw rgb pixel array,
Should be called to retrieve result after kernel is executed.
- getSimpleRGBRaster(byte[]) - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getSteering() - Method in interface com.apw.carcontrol.CarControl
-
Gets the current steering angle of the car
- getSteering() - Method in class com.apw.carcontrol.TrakSimControl
-
- getStoppingAtLight() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getStoppingAtSign() - Method in class com.apw.SpeedCon.SpeedControlModule
-
- getStopRate(double, double) - Method in class com.apw.SpeedCon.CameraCalibration
-
- getStopTime(double, double) - Method in class com.apw.SpeedCon.CameraCalibration
-
- getTimeoutValue() - Method in exception jssc.SerialPortTimeoutException
-
Getting timeout value in millisecond
- getUnifiedBlobs(List<MovingBlob>) - Method in interface com.apw.pedestrians.blobtrack.IMovingBlobDetection
-
- getUnifiedBlobs(List<MovingBlob>) - Method in class com.apw.pedestrians.blobtrack.MovingBlobDetection
-
- getUnixBasedPortNames(String, Pattern, Comparator<String>) - Static method in class jssc.SerialPortList
-
Universal method for getting port names of _nix based systems
- getWidth() - Method in class com.apw.ImageManagement.ImageManagementModule
-
- getWindowsPortNames(Pattern, Comparator<String>) - Static method in class jssc.SerialPortList
-
Get serial port names in Windows
- GoodLog - Static variable in class com.apw.apw3.TrakSim
-
- GoodOpen - Static variable in class com.apw.fakefirm.Arduino
-
- GotBytes(byte[], int) - Method in class com.apw.apw3.TrakSim
-
- GotImgOps(String) - Static method in class com.apw.apw3.TrakSim
-
- GrasColo - Static variable in class com.apw.apw3.TrakSim
-
- GrasDk - Static variable in class com.apw.apw3.TrakSim
-
- GRAV - Static variable in class com.apw.SpeedCon.Constants
-
- GREY_RATIO - Static variable in class com.apw.pedestrians.Constant
-
- Grid_Locns - Variable in class com.apw.apw3.TrakSim
-
- GridBlock(int, int) - Method in class com.apw.apw3.TrakSim
-
Converts a click location on the window to a row&column number
corresponding to the rectangular specification given to NewGridTbl.
- GridLocTable - Static variable in class com.apw.apw3.TrakSim
-
- GroundsColors - Static variable in class com.apw.apw3.TrakSim
-


LinkedIn
Home
What is LinkedIn?
Join Today
Sign In
Email:
Password:
Over 175 million profesionals use LinkedIn to exchange information, ideas and opportunities
Stay informed about your contacts and industry
Find the people & knowledge you need to achieve your goals
Control your professional identy online
Join LinkedIn Today
Sign Up
First Name:
Last Name:
Email:
Password:
6 more characters
±
Already on LinkedIn?
SignIn
Search for someone by name:
First Name:
Last Name:


Enhanced binding syntaxes for Knockout 3+
Using the new APIs in Knockout 3.0.0, this plugin provides a set of enhanced binding syntaxes. Each syntax can be enabled individually as described in the sections below. But generally you’ll just enable everything as follows:
ko.punches.enableAll();
Rather than using the text
binding, you can use double curly-brace syntax to insert dynamic text content. For example:

Hello {{ name }}.

This method works by converting {{expression}}
markup to
before binding.
To enable this syntax, call ko.punches.interpolationMarkup.enable();
.
Rather than using the attr
binding, you can use double curly-brace syntax to insert dynamic attributes. For example:

Element content

This method works by converting title="{{expression}}"
markup to data-bind="attr.title: expression"
before binding. It intelligently handles multiple expressions intermixed with text, and multiple attribute bindings. For example, "This is the {{which}} option."
is converted to "This is the " + ko.unwrap(which) + " option."
. Note that embedded bindings may not work correctly for all attributes.
To enable this syntax, call ko.punches.attributeInterpolationMarkup.enable();
.
Rather than directly calling a function or using a computed observable to format output, you can use the filtering syntax. For example:

This method works by converting expression|filter[:arg1...]
to ko.filters.filter(expression, arg1 ...)
before binding. A matching filter function must exist in ko.filters
.
To enable this syntax, call ko.punches.textFilter.enableForBinding(<binding>);
for each binding that you want to use with filters.
Knockout.Punches includes the following filters:
default:<defaultValue>
- If the value is blank or null, replace it with the given default value.fit:<length>[:<replacement>][:<where>]
- Trim the value if it’s longer than the given length. The trimmed portion is replaced with ...
or the replacement value, if given. By default, the value is trimmed on the right but can be changed to left
or middle
through the where option. For example: name | fit:10::'middle'
will convert Shakespeare
to Shak...are
.json[:space]
- Convert the value to a JSON string using ko.toJSON
. You can give a space value to format the JSON output.lowercase
- Convert the value to lowercase.number
- Format the value using toLocaleString
.replace:<search>:<replace>
- Perform a search and replace on the value using String#replace
.uppercase
- Convert the value to uppercase.You can create your own filters by adding them to ko.filters
. Here is an example:
// Custom filter can be used like "| append: 'xyz'"
ko.filters.append = function(value, arg1) {
return '' + value + arg1;
};
When you have a set of bindings with the same functionality, the namespacing syntax allows you to dynamically create the handlers for those bindings based on which ones are used. For example, if you want to bind to arbitrary data attributes, you could create a data
namespace, which you would then bind as follows:

Here’s how you would define the handler for the data namespace:
ko.bindingHandlers.data = {
getNamespacedHandler: function(binding) {
return {
update: function(element, valueAccessor) {
element.setAttribute('data-' + binding, ko.unwrap(valueAccessor()));
}
};
}
};
As the bindings in your documents are processed, Knockout.Punches looks for bindings with the format x.y: value
that don’t already have a binding handler. It then creates an x.y
handler using the x
namespace handler, or if none is found, it uses a default handler that calls the x
binding with the value {y: value}
. This default behavior allows you to use the namespace syntax to bind events, attributes, styles, and classes using the event
, attr
, style
, and css
namespaces respectively. For example:
<div data-bind="style.color: currentProfit() < 0 ? 'red' : 'black'">

Namespaced bindings allow you to define and interact with dynamic bindings just like any other binding. For example, suppose you want to enable the filter syntax for the title attribute; you can do so by referencing it using attr.title
like this: ko.punches.textFilter.enableForBinding('attr.title');
This will work as long as you bind the title attribute using attr.title
. But what if you want to use filters with the original attr
syntax like attr: {title: name | caps}
? Knockout.Punches provides a simple solution, a preprocessor that converts the attr: {title: name}
syntax to attr.title: name
. To enable this preprocessor, call ko.punches.namespacedBinding.enableForBinding(<binding>);
.
When binding functions in your model to events, it’s easy to simply provide the function reference to the binding such as click: $parent.removePlace
. When bound this way, though, the reference to $parent
is lost; the removePlace
method will be called with a default this
value (the current model object). (See this Github issue for more information.)
By wrapping the method call in an anonymous function, like click: function() {$parent.removePlace($data)}
, the this
value is set correctly. The wrapped callback preprocessor in Knockout.Punches does this for you, so you can use the simple reference syntax and know that this
is the correct object in your method.
To enable this preprocessor, call ko.punches.wrappedCallback.enableForBinding(<binding>);
for each binding that you want to use it with. If you want this functionality for a binding parameter, such as template/afterRender
, call ko.punches.preprocessBindingProperty.setPreprocessor('template', 'afterRender', ko.punches.wrappedCallback.preprocessor);
. If you want to use it for all dynamically created bindings with a certain namespace (such as event
), call ko.punches.namespacedBinding.setDefaultBindingPreprocessor('event', ko.punches.wrappedCallback.preprocessor);
.
If you’re familiar with the original on...
syntax for defining event handlers, you may wish that Knockout allowed you to bind an expression to events. Knockout.Punches provides this ability for event handling using the on
namespace. Thus, for example, if you want to run an expression when the user clicks a button, you could bind it like this:
<button type="button" data-bind="on.click: x = x + 1">Increment</button>
Any of the model and context properties are available in the expression. In addition, you can access the event object through $event
.
If you want to use the expression syntax for other bindings, you can enable it using ko.punches.expressionCallback.enableForBinding(<binding>, <args>);
The args
parameter is a string that defines the names of the parameters available in the expression. For example, you could enable this syntax for the click
binding using ko.punches.expressionCallback.enableForBinding('click', '$data,$event');
ko.punches
.utils
.setBindingPreprocessor(bindingKeyOrHandler, preprocessFn)
- Adds a preprocess function to a binding handler. Automatically handles chaining..setNodePreprocessor(preprocessFn)
- Add a node preprocessor function. Automatically handles chaining..enableAll()
- Enables the enhanced syntaxes as follows:
text
and attr
bindings;attr
, css
, event
, and style
bindings;click
, submit
, and event
bindings,
as well as for optionsAfterRender
, template#beforeRemove
, template#afterAdd
, and template#afterRender
..interpolationMarkup
.wrapExpresssion(expressionText)
- The default version of this function returns a pair of comment nodes for a text binding. By replacing this function, you can define your own extensions to the syntax. The function must return an array of nodes to add..preprocessor(node)
- The preprocess function for the embedded text bindings syntax..enable()
- Enables the embedded text bindings syntax..attributeInterpolationMarkup
.preprocessor(node)
- The preprocess function for the embedded attribute bindings syntax..enable()
- Enables the embedded attribute bindings syntax..textFilter
.preprocessor(input)
- The preprocess function for the filter syntax..enableForBinding(bindingKeyOrHandler)
- Enables the filter syntax for the specified binding..namespacedBinding
.defaultGetHandler(name, namespace, namespacedName)
- Gets a binding handler for the given namespace/name that calls the namespace binding handler with a value of {name: value}
..setDefaultBindingPreprocessor(namespace, preprocessFn)
- Sets a preprocessor for each dynamically created binding for the given namespace..preprocessor(input)
- The preprocess function for the automatic namespacing syntax..enableForBinding(bindingKeyOrHandler)
- Enables the automatic namespacing syntax for the specified binding..wrappedCallback
.preprocessor(input)
- The preprocess function for the wrapped callback syntax..enableForBinding(bindingKeyOrHandler)
- Enables the wrapped callback syntax for the specified binding..expressionCallback
.makePreprocessor(args)
- Returns a preprocess function for the callback expression syntax. args
is a list of parameter names that the binding passes to the callback function..eventPreprocessor(input)
- The preprocess function for event handlers (uses args of $data,$event
)..enableForBinding(bindingKeyOrHandler, args)
- Enables the callback expression syntax for the specified binding..preprocessBindingProperty
.setPreprocessor(bindingKeyOrHandler, property, preprocessFn)
- Enables a preprocess function for a specific property of a binding.ko.filters
- A set of filter functions for use with the filter syntax.
ko.bindingHandlers.on
- The handler for the on
namespace, for expression-based event handling.
ko.getBindingHandler
- This Knockout API is extended by Knockout.Punches to dyntamically create handlers for namespaced bindings.
Knockout 3.0 includes three new APIs to extend the binding system with new syntaxes. Here’s a quick summary of the three methods:
ko.getBindingHandler
to dynamically create binding handlers.ko.bindingProvider.instance.preprocessNode
to modify or replace DOM nodes before bindings are processed.<bindingHandler>.preprocess
to modify the binding value before it is evaluated.License: MIT (http://www.opensource.org/licenses/mit-license.php)
Michael Best
https://github.com/mbest
mbest@dasya.com


Grade: {{"Grade"}} ({{"Score"}}%)
Description: {{"Description"}}
Exists: {{"Exists"}}
Digitized: {{"Digitized"}}
Public: {{"Public"}}
Without cost: {{"Free"}}
Online: {{"Online"}}
Machine-readable: {{"Machine readable"}}
Available in bulk: {{"Available in bulk"}}
No license restrictions: {{"No restrictions"}}
Up-to-date: {{"Up-to-date"}}
In the state repository: {{"In the state repository"}}
Verifiable: {{"Verifiable"}}
Complete: {{"Complete"}}
Comments: {{"Comments"}}
{{"Link"}} This summary last updated on: {{"Last updated"}}


Before Change
n_tasks = 1
data_points = 10
mols = ["CCCCCCCC"] * data_points
X = featurizer(mols)
y = np.random.randint(0, 2, size=(data_points, n_tasks))
After Change
// TODO: This test is a little awkward. The Smiles2Vec model awkwardly depends on a dataset_file being available on disk. This needs to be cleaned up to match the standard model handling API.
def test_smiles2vec_reload():
Test that smiles2vec models can be saved and reloaded.
dataset_file = os.path.join(os.path.dirname(__file__), "chembl_25_small.csv")
max_len = 250
pad_len = 10
max_seq_len = 20
char_to_idx = create_char_to_idx(


Crypto Analyst Tone Vays Unveils $100K Bitcoin (BTC) Timeline – Plus Ethereum, XRP and Ripple Updates
by Daily Hodl StaffFrom an updated take on Bitcoin’s next potential bull run to new support for BTC, ETH and XRP, here’s a look at some of the stories breaking in the world of crypto.
Bitcoin
Crypto analyst Tone Vays is updating his timeline on when he thinks Bitcoin may hit $100,000.
In a new interview with BlockTV, Vays pours cold water on predictions that BTC will break through its all-time high next year.
“Once we break $20K, we can go to $50K or $100K pretty quickly, but I’m not expecting us to break $20K in 2020. I’m really looking for the bull market to really take off around 2022, 2023.”
Vays says he’s still bearish on Bitcoin and thinks the leading cryptocurrency will break below $7,000 before May of next year.
“To me, the big run up was 80% exit out of altcoins, 20% institutional investing. Now that the price is starting to go down, they’re probably not as eager. They’ll wait for a bottom because that’s why they’re a little bit smarter.
At the moment, I still see lower prices. I still think we’re going to go lower than $7,000 before the halving. But after that, that would be the final secondary low. Hopefully it’ll be higher than the $3,000 low back in December. And then we can finally start a bull market after the halving.”
Ethereum and XRP
The crypto exchange Binance is rolling out support for the Turkish lira.
An updated list of coins available for purchase on Binance.com reveals that the exchange is working with the digital wallet company Papara to offer Bitcoin (BTC), Ethereum (ETH) and XRP in exchange for the lira.
So far, Binance does not allow customers to sell crypto assets for the lira.
Ripple
Ripple says a new survey shows many financial service providers still have major concerns about the legality of blockchain technology.
The survey questioned 1,053 professionals across 21 countries who are working directly with payment services at their organizations.
According to the San Francisco startup, 35% of respondents say regulations are too uncertain, and 32% believe current regulations are too restrictive.
“These regulatory concerns, however, vary notably by a payment service providers’ adoption stage, level of digital channel usage and location. Not surprisingly, the next wave of adopters (those nearing implementation) are less concerned about regulation than the late adopters (those in conversation).
Similarly, digital banks that have already transformed the bank model are less concerned than traditional retail banks. Respondents in emerging markets have even stronger concerns about regulations being prohibitive, and advanced markets are the most concerned about uncertain regulations.”
You can check out the full survey here.


Location
Candidate Type:
Candidate Name:
Location Name:
PeopleSoft Location Code:
Street Address:
City:
County:
State:
Zipcode:
Latitude:
Longitude:
From 2C Survey?
Site Details
Elevation (ft AMSL):
Height (ft AGL):
RF Engineer:
Nearest Airport:
Distance to Neareat Airport (mi):
Jurisdiction:
Leasing Agent Name:
Site Acq Company:
Leasing Agent Phone:
Phone Commment for Leasing Phone:
Gate Lock Access:
Crane Accessible:
Telephone Company:
Nearest Phone:
Phone Commment for Nearest Phone:
Power Company:
Power Company Phone:
Phone Commment for Power Company Phone:
Police Station Phone:
Fire Station Phone:
Phone Comment for Police Station Phone:
Phone Comment for Fire Station Phone:
Describe Near-Field Tx Antenna (Obstructions, Terrain, Foliage, Highways)
Tower & Land Owner Phone
Tower Owner Name:
Tower Owner Phone:
Phone Comment for Tower Owner Phone:
Street Address:
City:
State:
Zip Code:
Tower Owner Contact Name:
Tower Owner Contact Phone:
Phone Commment for Tower Owner Contact Phone:
Land Owner Name:
Land Owner Phone:
Phone Comment for Land Owner Phone:
Street Address:
City:
State:
Zip Code:
Land Owner Contact Name:
Land Owner Contact Phone:
Phone Comment for Land Owner Contact Phone:
Tower Information
Raw Land Type:
Height Permittable (ft):
Tower Type:
Rooftop Build Date:
Zoning Classification:
Building Height (ft AGL):
Carrier Tower Company:
Tower Co Site Name:
Tower Co Site Number:
Tower Co Date Confirmed:
Available Height Range (ft AGL):
Tower Co Existing Tenant Heights:
Tower Built?:
Tower Build Date:
Under Construction?:
In Zoning?:
In BP Process?:
Comments:


The second layer is needed because it's impossible to reshape a size 100 vector into the 28x28x1 shape we'd need to create an mnist image. 28 times 28 is 784, and it's easy to see how to reshape between a vector of size 784 to a tensor of size 28x28x1.
After playing around with them for a bit, it's clear that the convolutional model produces much nicer and faster results than simple fully connected layers.
I'm not sure if it has anything to do with the computer I was using, but as much as I tried to change the parameters, I couldn't seem to get away from all of the generated examples looking the same way and not coming close to forming a concrete image. They seemed to get stuck on examples such as the one below.
Again, I'm not sure if it was a bug with my instance of using the website, but even when trying to follow the above question, I seemed to get stuck with the generator producing the same-looking images:


Ads
Home
Order
My Results
I've got a few Ads for you!
each time choose one from the three images , you have 25 rounds


7.2 Policy methods
Initial activities are planned around an initial set of aims articulated below, where additional aims also will be suggested. The URSSI leadership group will regularly review suggestions of new aims, and will determine a rough desired level of activity across the aims.
The policy team will then develop and scope activities to match these desired levels, with review from the Policy Advisory Board, which will also be able to suggest adding or removing aims back to the leadership group.
The policy team will also maintain this listing of active, planned, and potential activities and its mapping to the aim. Activities will be split into those that, if successful, are likely to lead to significant changes in 1-2 years, 3-5 years, and longer-term, with an initial goal of applying 50% of resources to the 1-2 year activities, 40% to the 3-5 year activities, and 10% to the longer-term activities.
7.2.1 Aims
Initially, the policy area will work to address the following set of aims:
- Establish career paths (including titles and evaluation criteria for hiring and promotion).
- addresses Changes 2, 5 (from list of changes at the start of this chapter)
- aims primarily at the people and careers portion of URSSI’s impact goal, and secondarily at the research software ecosystem portion
- Improve the measurement of impact of individuals, especially in activities that are inherently collaborative like software development.
- addresses Changes 1, 2, 3
- aims primarily at the people and careers portion of URSSI’s impact goal, and secondarily at the research software ecosystem portion
- Incentivizes contributions to public goods / infrastructure within the academic credit model
- addresses Changes 1, 3, 5
- aims primarily at the research software sustainability portion of URSSI’s impact goal, and secondarily at the people and careers and research software ecosystem portions
- Disentangle software quality and software impact.
- addresses Changes 1, 4, 5
- aims at the research software ecosystem portion of URSSI’s impact goal
- Better recognize the value and importance of software.
- addresses Changes 1, 2, 3, 5
- aims at the research software ecosystem portion of URSSI’s impact goal
- Improve/increase funding opportunities and stable funding for maintenance of software that is important but doesn’t have a generic market and/or isn’t considered novel in the eyes of the average funder/reviewer. Today “lumpy” project funding (projects that are competitively funded for fixed periods, often with gaps between funded project periods) means that maintenance/sustainability can’t be reliably folded into project costs.
- addresses Changes 1, 4, 5
- aims primarily at the research software ecosystem portion of URSSI’s impact goal, and secondarily at the research software sustainability portion
- Increase the diversity of the development and maintenance community to achieve the diversity of the overall US population.
- addresses Change 6
- aims primarily at the people and careers portion of URSSI’s impact goal, and secondarily at the research software ecosystem portion
7.2.2 Partners
The Policy area will seek to work with partners listed in the “Partners” section of Chapter 3, specifically including:
other NSF SI2/CSSI Institutes & Centers of Excellence (e.g. SGCI, MolSSI, IRIS-HEP), the Research Software Alliance, the Software Sustainability Institute, the US-RSE Association, the (UK) RSE Society, the Academic Data Science Alliance, the Research Data Alliance, the American Association for the Advancement of Science (AAAS) Science & Technology Policy Fellows, CaRCC, OECD, and any other projects and organizations that also seek to define and address overlapping aims.
The Policy area needs to build relationships with the following groups and organizations, and to work closely with them, particularly in policy activities.
Institutional and research leaders in the academic and national laboratory community, such as VCRs, CTOs/CIOs, who can help URSSI penetrate various institutions and disciplines
Representatives from professional academic associations
Representatives from industry (including those already invested and sold on OSS, as well as those skeptically interested)
Representatives from Open Source communities, particularly those that are already effective and working at scale
People working in science policy, such as in AAAS and the National Academies (in particular, AAAS policy fellows might be interested in helping on time-constrained activities that match the purpose and period of their fellowship)
Representatives from organizations and companies serving OSS and RSE communities (e.g. NumFOCUS, Code for Science & Society, GitHub, Code Ocean)
Representatives from organizations that represent other research support roles (e.g., librarians, data stewards, RSEs), to work together to promote all such roles
Representatives from organizations that focus on diversity and inclusion in academia, to encourage them to include software-focused roles where possible
People from the European Commission regarding European Open Science Cloud (EOSC), etc.
Representatives from organizations like the Research Data Alliance and FORCE11
7.2.3 Planned Activity Pool
This is the initial list of activities that URSSI will maintain, and choose from. The specific activities that will be chosen to start depend on the funding level for URSSI. Most activities include an amount of effort (generally in person-months) that is needed to accomplish them. Note that some activities (the items below) include raising additional funds for those activities - that fund raising is part of the activity. Other activities (in the “Unplanned Activity Pool” subsection) are tracked but are beyond the scope of URSSI, and are more likely activities that others might perform, potentially in coordination with URSSI.
Activities are divided into two types:
Policy Research Activities. These activities involve research, such as gathering and analyzing evidence and data.
Policy Advocacy Activities. These activities focus on advocacy. They generally depend on policy research or previously gathered evidence and data.
High-level activities include:
Maintaining the list of potential activities and prioritizing them, including getting inputs from the overall community. These inputs will be collected and recorded by all members of the project in their interactions with the community, as well as by community members, via tagged GitHub issues. Community members will be able to see this list and react with a +1 to issues they think are important, and URSSI will use these reactions as an element of prioritization. (ongoing)
Tracking completed activities and their consequences (ongoing)
Collecting examples of good and bad policy, structures, and interventions from industry and from other disciplines (potential fellow project)
Developing an advocacy roadmap for how to effectively advocate (to universities, foundations, industry, national labs) (policy person & advisory committee, spread over 3 months)
Additionally, while this is a plan and not a proposal (it doesn’t have a budget envelope it is working to fit in, it is not responding to a specific solicitation, and the potential funder’s goals are unclear) we have considered priorities for these activities. Initial activities will mostly focus on research, as most advocacy activities would follow and be based on the results and lessons of the research activities. In addition, as mentioned above, final prioritization will also need inputs from the Policy Advisory Board and the URSSI leadership team. Activities with a preceding “(+)” are considered higher priority than other activities.
<IP_ADDRESS> Career Path Activities (Aim 1)
Faculty career path policy research activities:
- Study tenure guidance and policies, and find/document ways that software work is measured and recognized. Publish examples of successes. (ADSA is interested in partnering on this; the ADSA Career Development Network is mostly faculty facing exactly these challenges. Additionally, RDA is in the processing of developing an Open Science Registry5 as a collaborative platform to share both the intention and outcomes of pilots and other initiatives that specifically address the academic reward system, as an outcome of the European Union Open Source Policy Platform (OSPP) final report (Mendez et al. 2020).) (2 months)
Faculty career path policy advocacy activities:
Promote best practices in recognizing and measuring software work in hiring practices and tenure letters via sample guidance documents for committees, for faculty, and for letter-of-reference authors. (needs focused workshop and follow-through, ~3 months over a year)
Commission a NAS report (similar to the one on Open Source Software Policy Options for NASA Earth and Space Sciences) on career pathways/progression in academia. Would need to define, then raise funds from outside URSSI (~$1m), then work with NAS to define a charge and to contract for the study. (4 months over 2.5 years, overlapping with related item in staff career path policy advocacy activities)
Staff career path policy research activities:
(All the activities below will be coordinated with US-RSE and other national RSE organizations. Additionally, some information already exists that can be mined, such as international and national RSE surveys (Philippe et al. 2019), …)
(+) Document existing (known successful/viable, known failures) career paths for individuals creating research software (2 months)
(+) Examine and document industry career paths vs. national laboratory career paths vs. academic career paths (1 month)
(+) Create and maintain a mailing list for those interested in career paths (mailing list to be supported by Community area) (ongoing, low level of effort)
Create a clearinghouse of job descriptions with criteria for performance assessment; distill out design patterns or different categories for different roles. This could also include documenting salary levels for different job descriptions, and connecting the job descriptions with then learning modules necessary for these jobs (3-4 months, plus ongoing maintenance)
Examine how salaries for RSEs compare with those of other researchers? (needs to follow clearinghouse, 1 month)
Staff career path policy advocacy activities:
(+) Help start organizational “chapters” of research software developers (perhaps called URSSI chapters?) at existing universities / societies / organizations; create handbook, tools, best practices to support local organizers; assign an URSSI “coordinator” / community manager. These chapters could: talk about training, do consulting for problems, host hacky hours, study groups, software days, and come together in a larger event, perhaps a regional workshop or an URSSI-wide conference. Overall, this helps / grows / establishes the community (and make connections that could help chapter members meet the right person for their next career moves).
Done with URSSI Community area; Policy part (1 month) is creating some materials, e.g., guidance on how to set up a chapter, how to align it to local activities, and how to run it.
Also to be coordinated with US-RSE, as regional US-RSE groups might overlap regional URSSI chapters.
Work to promote and support the establishment of RSE capabilities at universities around the US. Provide advice on how to talk to university administrators (and which ones) about this, etc. (1 month, jointly with US-RSE)
Provide examples of language to universities they can use in HR/job ads for RSE positions (1 month, jointly with US-RSE)
Commission a NAS report (similar to the one on Open Source Software Policy Options for NASA Earth and Space Sciences) on {career pathways/progression in academia, recognition of software, evaluation of software developers, inclusion of software in hiring and promotion} Would need to define, then raise funds from outside URSSI (~$1m), then work with NAS to define a charge and to contract for the study. (4 months over 2.5 years, overlapping with related item in faculty career path policy advocacy activities)
<IP_ADDRESS> The impact of individuals (Aim 2)
The impact of individuals policy research activities:
- Identify factors (manual, such as evaluations, and automated, such as crawling repos) that are part of impact and publicize them. Some known factors to investigate include quantifying code contributions, code review, mentoring. Determine good practices (for formatting or housing the information on these factors) so those factors are discoverable and/or queryable. (An initial effort of 6 months will make progress and better scope additional work that could be performed.)
Measuring the impact of individuals policy advocacy activities:
Create champions (e.g. librarians) to promote and educate individuals and projects of these good practices, working with the best practices activity in Community area.
Help individuals understand how they can best promote themselves (e.g., claim software works on ORCID), working with the best practices activity in Community area.
<IP_ADDRESS> Incentivize contributions to public software (Aim 3)
Incentivize contributions to public software policy research activities:
Gather data/examples that show when contributions to public projects increase your citation count or regular metrics (1 month)
(+) Gather examples of successful use of individual contributions to public goods/infrastructure to gain academic promotion (1 month over 3-6 months)
(+) Use regular surveys to better understand why people do and don’t contribute; get data to understand the value of public goods to community (1 month over 3-6 months each year)
Determine a way to make it easy for scientific communities to peer-review public-good software (or contributions to such software), with the idea that peer-review is considered a mark of quality. This could be done by starting a new journal or working with existing journals or conferences, or via existing community organizations or software-focused organizations (ongoing, not well-scoped)
Research to counter the idea that publishing in the small set of “highest impact” journals is key, and expose actual impact of work instead (work with scholcom community, use what they have done, maybe adapt their work for software - maybe 2 months to start)
Incentivize contributions to public software policy advocacy activities:
Work to persuade high-profile individuals to make public contributions to public projects
(+) Share examples of successful use of individual contributions to public goods/infrastructure to gain academic promotion, produce templates, advocacy toolkits and examples to help others to make their case. Similarly, work to persuade people that contributing to projects will increase their products within their normally accepted reward system (e.g., get more collaborators and papers; increase opportunities to meet/work with new/old collaborators; will build social connections/network) (ongoing, not well-scoped)
(+) Show how you can participate in public goods / infrastructure projects (e.g., how to structure an issue, how to write your first PR), collaboratively with best practices activity in URSSI Community area (low initial effort, low ongoing effort to maintain)
Produce templates based on successful use of individual contributions to public goods/infrastructure to gain academic promotion, advocacy toolkits, and examples to help others to make their case (1 month)
Reframe contributions as first class research products / objects (i.e., explain how building the best software is itself science, as it’s both discovery and creation). In order to do this, amplify existing efforts to build a taxonomy of such contributions to make it clear what those contributions are, and encourage people to claim/talk about/take pride in these contributions; work with publishers to highlight these contributions and the people who make them. Also advocate (materials, webinars, ambassadors, etc.) within academic communities (deans, faculty, science societies, review panels, funders) that public software contributions are research (also could be done by cross-disciplinary respected groups, such as the national academies)
(+) Work to revise funder policies to ensure reviewers prioritize grant proposals that reuse, build-upon and contribute back to maintenance of public infrastructure
Create high-profile equivalent of “highest impact” journal for software and data work - where publication is seen as an accomplishment indicating the significance of the software
<IP_ADDRESS> Disentangle software quality and software impact (Aim 4)
Disentangle software quality and software impact policy research activities:
- Create checklists/review guidelines for different levels of peer-review for software; can be tiered, could issue stars or use another rating system; leverage information already available from journals and other resources. (1 week)
Disentangle software quality and software impact policy advocacy activities:
- Disseminate peer-review for software checklists/review guidelines to publishers and other organizations that review software, via a working group. (2 months over 2 years)
<IP_ADDRESS> Better recognize the value and importance of software (Aim 5)
Recognize the value and importance of software policy research activities:
(+) Find science/discovery cases where software was particularly fundamental, particularly digging into software that is not so generally well-known (2 months over 6 months)
(+) Research and deliver case studies in sustainable software value, e.g., NetCDF, HDF5, DS9 image viewer, GCM model(s). How much money was invested in these projects and how did these projects return value to the community? Examples of value could include: number of research projects taking advantage of these solutions, amount saved by not having to reinvent these technologies. (6-to-12-month fellow project)
Quantify the money that has implicitly funded maintenance and sustainability, and has been saved or lost in the shift to open source (e.g., where have funds been spent on one-off software rather than maintaining existing open source software, and where has an investment in software maintenance saved funds from being spent on one-off software) (6-month fellow project)
Calculate bus factor for a bunch of key software in disciplines (partner with CHAOSS, or perhaps 6-month fellow project)
Document maintenance and funding for critical packages for several disciplines, e.g. IRAF in astronomy (6-month fellow project)
Recognize the value and importance of software policy advocacy activities:
(+) Publicize science/discovery cases where software was particularly fundamental, focusing on demonstrating impact of software (1 week/year, ongoing)
(+) Raise awareness that software needs to be maintained (low level, ongoing)
<IP_ADDRESS> Funding opportunities for software maintenance (Aim 6)
Funding opportunities for software maintenance policy research activities:
(+) Review the landscape of funding opportunities for software maintenance (and gather data about them) and provide a public summary, then keep the summary up-to-date. (jointly done with ReSA? Or CZI EOSS?) (1 month and some ongoing work)
Gather case studies of successful commercialization of open source projects and encourage the research community to understand and make use of them (2 months)
Review the scope of maintenance needs by various research disciplines. Determine the order of magnitude of the maintenance backlog for research software (with CHAOSS and others, unscoped)
Funding opportunities for software maintenance policy advocacy activities:
Encourage funding agencies to require software management/maintenance plans (SMPs). Use them to couple the idea of maintenance to the idea of development, to make it clear that just doing development without maintenance doesn’t work. Note that this leads to questions about when maintenance should be stopped, and it’s also unclear how long-term maintenance would be supported (since grants are by definition time-limited). (1-2 months/year ongoing, work with ReSA)
Advocate for funding agencies to provide a funding pool for short-term maintenance grants for existing projects (e.g. CZI’s EOSS program). (1-2 months/year)
(+) Advocate for universities to support maintenance of software developed by their university as part of research impact (or possibly technology transfer), in part by including how software we highlight in the success stories campaign was paid for, including university and RSE contributions, then using this collectively to demonstrate the impact of specific university-funded activities, to encourage other universities to step up. (2 months/year over multiple years)
Encourage companies to provide funds and channel these funds into maintaining research software projects, perhaps via a review process with reviewers from both academic software projects and the companies. This could be done jointly with NumFOCUS or a similar organization, similar to Tidelift (1-2 months/year)
<IP_ADDRESS> Increase diversity of software community (Aim 7)
Diversity and inclusion policy research activities:
(+) Survey US research software projects to examine diversity of leadership and contributors (3 months)
Study/survey contributors who make a single contribution and those who make ongoing contributions vs membership in underrepresented groups (3 months)
(+) Contribute to DISCOVER event cookbook, working with NumFOCUS’s DISC
Other items with CS&S and NumFOCUS’s DISC, for example, creating a cookbook aimed at projects
Diversity and inclusion advocacy activities:
(+) Advertise DISCOVER event cookbook, working with NumFOCUS’s DISC
(+) Other items with CS&S and NumFOCUS’s DISC, such as advertising the cookbook aimed at projects
Reach out to projects to encourage them to mentor Outreachy interns and those from other programs (e.g., Linux Foundation diversity programs, https://opensourcediversity.org/#programs), and to work with Google Summer of Code, maybe include some matchmaking. Consider URSSI as an organization that applies to a set of these programs on behalf of a set of software projects.
Build community mentoring program focused on diversity
Work with RLadies, Women in Data Science, etc.
<IP_ADDRESS> General advocacy activities (not mapped to specific Aims)
Work with REU6 programs? – set up a network of software-focused REUs? Or focus on software aspects of more REUs? (provide training, guidance, language for proposals, …) (2 month to start + ongoing)
Foster competition between universities (and their administrations), as has been done by the SSI in the UK to create RSE groups, by:
Highlighting software work (including internal investments to sustain projects that the university sees as important and prestigious) and successes (including funded projects that focus on software) in some universities.
Ranking the contributions of universities to software or their structure for software developers, and publicizing the ranking (maybe with US-RSE) – via newsletter, blogs, press releases (pontentally run by or at least coordinated with the URSSI community area). This could be based in part on information submitted by the software community, e.g. Laura Noren’s and Brad Stenger’s Data Science Community Newsletter. These rankings and information would also be bi-directionally shared with ReSA.
Work in citation and credit (get publishers to recognize and highlight software in research) (with FORCE11 and others) (minor support of other activities)
Promote software management plans and software sustainability plans as part of proposals (3 months over a year, bringing together community and volunteers, work with ReSA and RDA)
(+) Develop a set of options for how institutions can support research software (e.g., RSE groups, RSE careers, tenure and promotion guidelines) and disseminate it (with US-RSE, starting after year 1)
(+) Create and operate a professional award program (working with other established organizations) e.g., ESA URSSI software award. The URSSI software contribution to research awards: URSSI/ESA (e.g. John Chambers software award from stats association). $10k funding available from URSSI (eventually domain societies would be asked to partially fund the awards). URSSI would need to define the categories, criteria/heuristics, etc. for awards beforehand. And find people (either staff or community volunteers) to run awards processes (accept nominations, make decisions) (2 weeks/year starting in year 2)
(+) Work with NumFOCUS to provide guidance to projects on how to work with (including obtaining funding from) industry (sharing material with incubator area)
(+) Offer training for software development proposals (or point to others who do)
Develop and disseminate best practices for software development proposals (with NumFOCUS or the Capentries)
Training/materials could be asynchronous, or in-person with NSF program officers as well, if they were willing to do so
Licensing (in partnership with OSI, Creative Commons, others)
- Provide (pointers to) guidance on licenses and copyright for research software (little work, partner with OSI and point to existing best practices)
<IP_ADDRESS> Unplanned Activity Pool
The activities listed here are those that would support URSSI but are beyond the scope of URSSI. They are listed here to provide ideas to others, and URSSI would potentially be willing to encourage and support them, but likely without resources.
<IP_ADDRESS>.1 Staff career path policy research activities (Aim 1)
- Comparative study of research success at universities with core RSE groups vs those without. (potential research topic, not to be started by URSSI)
<IP_ADDRESS>.2 Incentivize contributions to public software policy advocacy activities (Aim 3)
- Run a help desk once a week on-line for people who are running into difficulties in making contributions and need help
<IP_ADDRESS>.3 Disentangle software quality and software impact policy research activities (Aim 4)
Define what software quality means.
Define what software impact means and how to measure it. Impact can be looked at in many ways: scientific, economic, societal, etc.
Define how you know what software will be impactful (signals of high impact)
Capture the difference between software quality and software impact in written resources (blog post, paper, etc.)
Conduct a Delphi study or multiple Delphi studies across or between disciplines to determine a consensus on key indicators of software impact and related questions, such as: Does improving the quality of software improve its impact?
Perform randomized experiments of software impact where the treatment is improved software practices
Perform a retrospective study of software quality as related to “impact” of that software.
<IP_ADDRESS>.4 Recognize the value and importance of software policy research activities (Aim 5)
- Study whether higher-quality software produces higher-impact science or more reliable science results
<IP_ADDRESS>.5 Funding opportunities for software maintenance policy advocacy activities (Aim 6)
Provide a system to match open source maintenance needs and open source programmers (e.g., classified ads), to be funded by URSSI, or URSSI could support proposals for such maintenance work (both morally and by providing guidance to the proposer)
Provide fellowships for programmers to “do good stuff” related to maintenance
Attach money for maintenance to some of the to-be-created awards for good software development, jointly named and funded with other communities
<IP_ADDRESS>.6 General advocacy activities (not mapped to specific Aims)
Talk about problems with current software licenses/models and suggest alternatives
Create peer-review and publishing systems that are software appropriate, and not just a version of article appropriate system. For instance, find a software ecosystem-native way to peer-review software inside a code management system, or “publish” software by giving a specific version of code a DOI
References
Mendez, Eva, Rebecca Lawrence, Catriona J. MacCallum, Eva Moar, and Open Science Policy Platform members. 2020. “Progress on Open Science: Towards a Shared Research Knowledge System: Final Report of the Open Science Policy Platform.” European Commission. https://doi.org/10.2777/00139.
Philippe, Olivier, Martin Hammitzsch, Stephan Janosch, Anelda van der Walt, Ben van Werkhoven, Simon Hettrick, Daniel S. Katz, et al. 2019. softwaresaved/international-survey: Public release for 2018 results (version 2018-v.1.0.2). Zenodo. https://doi.org/10.5281/zenodo.2585783.
This link may not yet work.↩
REU is refers to both NSF’s Research Experience for Undergradautes program, as well as being a generic term for summer and other programs that provide undergraduates with research experience.↩


Where do you work?
Spectrum Health
GVSU
Tell us about yourself
Michigan
That's me!
How did you commute today?


{% extends 'dashboard/base.html' %} {% block MainContent %}
| Name | Dosage | Frequency (Times Per Day) | Duration (No. of days) | Comments |
|---|---|---|---|---|
| {{ prescription.name }} | {{ prescription.dosage }} | {{ prescription.frequency_per_day }} | {{ prescription.duration_in_days }} |
"{{ prescription.comments }}" |
There are no drugs prescribed.
{% endif %}There are no tests prescribed.
{% endif %}There are no vaccines added.
{% endif %}


--- title: Jekyll Serif - Jekyll Small Business Theme layout: default bodyClass: page-home ---
This website pertains to Rajat Bansal & Associates, company secretaries firm and is never sent unsolicited to any person or professional. This website is meant solely for the purpose of information and not for the purpose of advertising and solicitation of any assignments or professional engagements in any manner.
Rajat & Associates hereby declares that the contents of this site are true to the best of their knowledge and belief and are in conformity with Guidelines for Advertisement by Company Secretary in Practice as per Guidelines issued by the ICSI.
The contents or claims of the website are the sole and exclusive responsibility of Rajat Bansal & Associates and the Institute of Company Secretaries of India does not own any responsibility whatsoever for such contents or claims by Rajat Bansal & Associates. The content of this website is for informational purposes only and Rajat Bansal & Associates shall not be liable for consequences of any action taken by relying on the material/information provided on this website.
Agree
{{ service.content | markdownify | strip_html | truncate: 100 }}


yet another HTML5/CSS3 presentation thingy
http://lab.hakim.se/reveal-js
Learn at least one new language every year.- The Pragmatic Programmer, p14
Can't mix types or use undefined variables
Prelude> a
<interactive>:1:1: Not in scope: `a'
Prelude> (1 :: Integer) + (1 :: Double)
<interactive>:1:19:
Couldn't match expected type `Integer' with actual type `Double'
...
Must convert before adding
Prelude> read "3" + 1
4
Type inference
Prelude> read "3" + 1.0
4.0
Prelude> read "3"
<interactive>:1:1:
Ambiguous type variable `a0' in the constraint:
...
Prelude> read "3" :: Double
3.0
Undefined constant becomes string and you get:
p h p > echo SESSION_TIMEOUT_ADMIN + 900;
900
With PHP notices on:
p h p > echo SESSION_TIMEOUT_ADMIN + 900;
PHP Notice: Use of undefined constant SESSION_TIMEOUT_ADMIN - assumed 'SESSION_TIMEOUT_ADMIN' in
php shell code on line 1
900


--- layout: default title: Home --- Your browser does not support the audio element.
One resume/portfolio/professional website!
that looks much better than this one
Happy Birthday Eric!
I hope you're having a great day!
Love, Trevor
p.s. click the present below for your gift!


Ariana Grande Takes A Tumble During Florida Gig But Handles It Like A Pro
by Becca LongmireAriana Grande fell over during her Tampa, Florida, show Sunday, but handled it like the pro that she is.
Grande tripped over in her thigh-high heeled boots at the Amalie Arena, but was caught on camera immediately laughing it off as she was given a hand by her dancers.
One fan even pointed out that the musician had managed to fall “on beat.”
Grande replied:
She also told fans later in the show: “Thank you for making me feel loved when I fell earlier. I had to fall.
“It’s been 87 shows and I haven’t fallen yet, so it had to happen,” according to the Tampa Bay Times.


8th of may
REMOTE EDITION
talk
Natural Language Processing for Machine Learning
Alessandro Conflitti
Lead Data Scientist @Talkdesk.
about the talk
In this talk you will learn about how Machine Learning allows for a computer to understand and manipulate human language.
workshop
Use cases of AI and Automation in Communications Network Security
Paulo Pinto
Business Development Manager @Fortinet Portugal
about the workshop
This workshop will consist in a presentation followed by a Q&A session that will erase all of your doubts about AI in communications networks.


{{ . | markdownify }}
{{ end }} {{ with .Site.Params.about.buttonText }} {{ . }} {{ end }}"The staff at First American Home Loans was very friendly and informative. They took the time to undertand our needs and kept us infomed at all times during the process. Now that our loan is closed, my wife and I both agree that this was the best decision for our family."
"We have the peace of mind that we will never have to move or make another mortgage payment."
"Also with the additional cash and savings, we were able to remodel our kitchen and go on a long-overdue vacation!"


4.4 The Types and Classes Dictionary
Type NIL
Type BOOLEAN
System Class FUNCTION
Type COMPILED-FUNCTION
System Class GENERIC-FUNCTION
System Class STANDARD-GENERIC-FUNCTION
System Class CLASS
System Class BUILT-IN-CLASS
System Class STRUCTURE-CLASS
System Class STANDARD-CLASS
System Class METHOD
System Class STANDARD-METHOD
Class STRUCTURE-OBJECT
Class STANDARD-OBJECT
System Class METHOD-COMBINATION
System Class T
Type Specifier SATISFIES
Type Specifier MEMBER
Type Specifier NOT
Type Specifier AND
Type Specifier OR
Type Specifier VALUES
Type Specifier EQL
Function COERCE
Macro DEFTYPE
Function SUBTYPEP
Function TYPE-OF
Function TYPEP
Condition Type TYPE-ERROR
Function TYPE-ERROR-DATUM, TYPE-ERROR-EXPECTED-TYPE
Condition Type SIMPLE-TYPE-ERROR
Copyright 1996, The Harlequin Group Limited. All Rights Reserved.