Research Data Analyst 2 (6256U) 1789 - 1789 - Berkeley, CA 94720
Research Data Analyst 2 (6256U) 1789 - 1789 About Berkeley
The University of California, Berkeley, is one of the world's most iconic teaching and research institutions. Since 1868, Berkeley has fueled a perpetual renaissance, generating unparalleled intellectual, economic and social value in California, the United States and the world. Berkeley's culture of openness, freedom and acceptance—academic and artistic, political and cultural—make it a very special place for students, faculty and staff.
Berkeley is committed to hiring and developing staff who want to work in a high performing culture that supports the outstanding work of our faculty and students. In deciding whether to apply for a staff position at Berkeley, candidates are strongly encouraged to consider the alignment of the Berkeley Workplace Culture with their potential for success at http://jobs.berkeley.edu/why-berkeley.html .
Application Review Date
The First Review Date for this job is: October 14, 2019.
Departmental Overview
The Center for Effective Global Action (CEGA) is the University of California's premiere center for research on global development. CEGA's faculty affiliates use two powerful techniques—rigorous evaluation and economic analysis—to measure the impacts of large-scale social and economic development projects.
Responsibilities
Assists with implementation of business processes. Maintains and develops research gathering, retrieval and reporting systems.
Plans studies, including the design of survey instruments and determining the sampling and reporting procedures.
Collaborates on the design, documentation, testing and implementation of research studies, including assisting with technical aspects of new and renewal applications to Institutional Review Boards..
Writing and Reporting: As needed, provide input into technical aspects of project reports for funders. Provide input as appropriate into academic papers. Assist faculty with literature reviews, drafting such reviews or portions of such reviews. Assists in developing systems for organizing data to analyze, identify and report trends.
Data Analysis: Work with data sets, prepare and run code for data cleaning and analysis. Prepare data for publication and publish in publicly accessible repositories.Gathers and analyzes research data; prepares and summarizes information and/or recommendations.
May be involved in researching, evaluating and selecting new data reporting products.
Prepares reports and/or analysis for internal department constituents.
Independently plans limited studies or assists higher level Analysts in large, complex studies.
Required Qualifications
Bachelor's or Master's degree in economics, social sciences, public policy, mathematics, statistics, or related fields and/or equivalent experience or training.
Training in microeconomics, econometrics, and statistics is required.
Working knowledge of research function.
Working skills in statistical analysis, system programming, database design and data security measures.
Working skills in analysis and consultation.
Skills to communicate complex information in a clear and concise manner both verbally and written.
Hands on experience with Stata or R; experience working with large data sets is required.
Proven ability to handle several different projects/tasks at one time, successfully complete tasks assigned, and meet deadlines.
Salary & Benefits
Hourly Salary Range: $29.12 - $33.53
For information on the comprehensive benefits package offered by the University visit:
http://ucnet.universityofcalifornia.edu/compensation-and-benefits/index.html
Other Information
This is a one year full-time contract position.
Equal Employment Opportunity
The University of California is an Equal Opportunity/Affirmative Action Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or protected veteran status. For more information about your rights as an applicant see: http://www.eeoc.gov/employers/upload/poster_screen_reader_optimized.pdf
For the complete University of California nondiscrimination and affirmative action policy see:
http://policy.ucop.edu/doc/4000376/NondiscrimAffirmAct
To apply, visit https://careerspub.universityofcalifornia.edu/psp/ucb/EMPLOYEE/HRMS/c/HRS_HRAM.HRS_APP_SCHJOB.GBL?Page=HRS_APP_JBPST&Action=U&FOCUS=Applicant&SiteId=21&JobOpeningId=1789&PostingSeq=1


The 11th annual Oxford SIAM-IMA Student Chapter conference will be hosted on Wednesday 1st May 2019 at the Mathematical Institute of the University of Oxford.
The aim of the conference is to encourage greater interaction between the industrial and applied mathematics communities. This opportunity to meet and engage with academics from a wide range of disciplines will be of benefit, in particular, to graduate students and early career researchers.
Participation is completely free and includes food and drink throughout the day.
Contributed talks consist of a 15-minute presentation followed by a 5-minute discussion. The poster session will be 1 hour long and provides excellent opportunities for networking and in-depth discussions about research projects.
Posters may be up to A0 in size however for posters larger than A2, portrait orientation is recommended.
Please submit your abstract for a contributed talk or poster using the submission form by Monday 1st April.
We have some funds available to provide a contribution towards travel costs for attendees. Please indicate on the registration form whether you wish to be considered for these funds.


Vitess is an active open source project. Here is a list of recent and upcoming features the team is focused on: Check with us on our forums for more information.
Vitess has been used internally by YouTube for a few years now, but the first public versions lacked polish and documentation. Version 1.0 was mostly an internal release.
Vitess 2.0 GA was created on July 11, 2016. It was the first major public release.
It contains all the core features of the Vitess product:
Advanced data access:
Advanced manageability features:
Vitess 2.1 is actively being worked on. Apart from the multiple small changes we've been making to address a number of small issues, we are adding the following core features:
Support for distributed transactions, using 2 phase commit.
Resharding workflow improvements, to increase manageability of the process.
Online schema swap, to apply complex schema changes without any downtime.
New dynamic UI (vtctld), rewritten from scratch in Angular 2. We will still have the old UI in Vitess 2.1 as a fallback, but it will be removed in Vitess 2.2.
Update Stream functionality, for applications to subscribe to a change stream (for cache invalidation, for instance).
Improved Map-Reduce support, for tables with non-uniform distributions.
Increase large installation scalability with two-layer vtgate pools (l2vtgate, applicable to 100+ shard installations).
Better Kubernetes support (Helm support, better scripts, ...).
New implementations of the topology services for Zookeeper (zk2
) and etcd
(etcd2
). In Vitess 2.1 they will become the recommended implementations and
the old zookeeper
and etcd
will be deprecated. In Vitess 2.2 only the new
zk2
and etcd2
implementations will remain, so please migrate after upgrade
to Vitess 2.1.
Added support for Consul topology service client.
Initial version of the Master Buffering feature. It allows for buffering master traffic while a failover is in progress, and trade downtime with extra latency.
We already cut the 2.1.0-alpha.1 release, and we are finalizing the last details at the moment. Release ETA is around beginning of 2017.
The following list contains areas where we want to focus next, after the current set of changes. Let us know if one of these areas is of particular interest to your application!
Additional support for cross-shard constructs (IN clause, ordering and filtering, ...).
ExecuteBatch improvements (to increase performance of bulk imports for instance).
Multi-value inserts (across shards or not).
Better support for MySQL DDL constructs.
Support for MySQL 8.0.
Additional Kubernetes integration.
Include resharding workflows in the control panel UI (vtctld).
Support vertical splits to an existing keyspace, so any table can be moved around to any keyspace. Only for unsharded keyspaces, at first.
Out-of-the-box integration with Promotheus for monitoring.
We are considering integration/implementation of the following technologies in our roadmap. For specific features, reach out to us to discuss opportunities to collaborate or prioritize some of the work:
Integration with Mesos and DC/OS.
Integration with Docker Swarm.
Improved support for row-based replication (for Update Stream for instance).
Better integration with Apache Spark (native instead of relying on Hadoop InputSource).


{% seo title=false %}
{{ site.title }}
{% include analytics.html %}
No Frills is a band from toronto.
Debut LP
Downard Dog
coming 2022
Say Hello
Instagram
Facebook
Twitter
Email
Listen
Bandcamp
Spotify
Apple Music
YouTube
Nice To Meet You by No Frills
Shows


Enum HederaFunctionality
- java.lang.Object
-
- java.lang.Enum<HederaFunctionality>
-
- com.hederahashgraph.api.proto.java.HederaFunctionality
-
- All Implemented Interfaces:
com.google.protobuf.Internal.EnumLite
,com.google.protobuf.ProtocolMessageEnum
,java.io.Serializable
,java.lang.Comparable<HederaFunctionality>
public enum HederaFunctionality extends java.lang.Enum<HederaFunctionality> implements com.google.protobuf.ProtocolMessageEnum
The functionality provided by hedera hashgraph
Protobuf enumproto.HederaFunctionality
-
-
Enum Constant Summary
Enum Constants Enum Constant Description ContractCall
Smart Contract CallContractCallLocal
Smart Contract CallContractCreate
Smart Contract Create ContractContractDelete
delete contractContractGetBytecode
Smart Contract, get the byte codeContractGetInfo
Smart Contract get infoContractGetRecords
Contract get the transaction recordsContractUpdate
Smart Contract update contractCryptoAddClaim
crypto add claim to the accountCryptoCreate
crypto create accountCryptoDelete
crypto delete accountCryptoDeleteClaim
crypto delete claim to the accountCryptoGetAccountBalance
crypto get account balanceCryptoGetAccountRecords
crypto get account recordCryptoGetClaim
Crypto get the claimCryptoGetInfo
Crypto get infoCryptoGetStakers
Crypto, get the stakers for the nodeCryptoTransfer
crypto transferCryptoUpdate
crypto update accountFileAppend
File Operation append fileFileCreate
File Operation create fileFileDelete
File Operation delete fileFileGetContents
File Operations get file contentsFileGetInfo
File Operations get the info of the fileFileUpdate
File Operation update fileGetByKey
Smart Contract, get by keyGetBySolidityID
Smart Contract, get by solidity IDNONE
UNSPECIFIED - Need to keep first value as unspecified because first element is ignored and not parsed (0 is ignored by parser)SystemDelete
system delete fileSystemUndelete
system undelete fileTransactionGetRecord
Crypto get the transaction recordsUNRECOGNIZED
-
Field Summary
Fields Modifier and Type Field Description static int
ContractCall_VALUE
Smart Contract Callstatic int
ContractCallLocal_VALUE
Smart Contract Callstatic int
ContractCreate_VALUE
Smart Contract Create Contractstatic int
ContractDelete_VALUE
delete contractstatic int
ContractGetBytecode_VALUE
Smart Contract, get the byte codestatic int
ContractGetInfo_VALUE
Smart Contract get infostatic int
ContractGetRecords_VALUE
Contract get the transaction recordsstatic int
ContractUpdate_VALUE
Smart Contract update contractstatic int
CryptoAddClaim_VALUE
crypto add claim to the accountstatic int
CryptoCreate_VALUE
crypto create accountstatic int
CryptoDelete_VALUE
crypto delete accountstatic int
CryptoDeleteClaim_VALUE
crypto delete claim to the accountstatic int
CryptoGetAccountBalance_VALUE
crypto get account balancestatic int
CryptoGetAccountRecords_VALUE
crypto get account recordstatic int
CryptoGetClaim_VALUE
Crypto get the claimstatic int
CryptoGetInfo_VALUE
Crypto get infostatic int
CryptoGetStakers_VALUE
Crypto, get the stakers for the nodestatic int
CryptoTransfer_VALUE
crypto transferstatic int
CryptoUpdate_VALUE
crypto update accountstatic int
FileAppend_VALUE
File Operation append filestatic int
FileCreate_VALUE
File Operation create filestatic int
FileDelete_VALUE
File Operation delete filestatic int
FileGetContents_VALUE
File Operations get file contentsstatic int
FileGetInfo_VALUE
File Operations get the info of the filestatic int
FileUpdate_VALUE
File Operation update filestatic int
GetByKey_VALUE
Smart Contract, get by keystatic int
GetBySolidityID_VALUE
Smart Contract, get by solidity IDstatic int
NONE_VALUE
UNSPECIFIED - Need to keep first value as unspecified because first element is ignored and not parsed (0 is ignored by parser)static int
SystemDelete_VALUE
system delete filestatic int
SystemUndelete_VALUE
system undelete filestatic int
TransactionGetRecord_VALUE
Crypto get the transaction records
-
Method Summary
All Methods Static Methods Instance Methods Concrete Methods Deprecated Methods Modifier and Type Method Description static HederaFunctionality
forNumber(int value)
static com.google.protobuf.Descriptors.EnumDescriptor
getDescriptor()
com.google.protobuf.Descriptors.EnumDescriptor
getDescriptorForType()
int
getNumber()
com.google.protobuf.Descriptors.EnumValueDescriptor
getValueDescriptor()
static com.google.protobuf.Internal.EnumLiteMap<HederaFunctionality>
internalGetValueMap()
static HederaFunctionality
valueOf(int value)
Deprecated.static HederaFunctionality
valueOf(com.google.protobuf.Descriptors.EnumValueDescriptor desc)
Returns the enum constant of this type with the specified name.static HederaFunctionality
valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name.static HederaFunctionality[]
values()
Returns an array containing the constants of this enum type, in the order they are declared.
-
-
-
Enum Constant Detail
-
NONE
public static final HederaFunctionality NONE
UNSPECIFIED - Need to keep first value as unspecified because first element is ignored and not parsed (0 is ignored by parser)
NONE = 0;
-
CryptoTransfer
public static final HederaFunctionality CryptoTransfer
crypto transfer
CryptoTransfer = 1;
-
CryptoUpdate
public static final HederaFunctionality CryptoUpdate
crypto update account
CryptoUpdate = 2;
-
CryptoDelete
public static final HederaFunctionality CryptoDelete
crypto delete account
CryptoDelete = 3;
-
CryptoAddClaim
public static final HederaFunctionality CryptoAddClaim
crypto add claim to the account
CryptoAddClaim = 4;
-
CryptoDeleteClaim
public static final HederaFunctionality CryptoDeleteClaim
crypto delete claim to the account
CryptoDeleteClaim = 5;
-
ContractCall
public static final HederaFunctionality ContractCall
Smart Contract Call
ContractCall = 6;
-
ContractCreate
public static final HederaFunctionality ContractCreate
Smart Contract Create Contract
ContractCreate = 7;
-
ContractUpdate
public static final HederaFunctionality ContractUpdate
Smart Contract update contract
ContractUpdate = 8;
-
FileCreate
public static final HederaFunctionality FileCreate
File Operation create file
FileCreate = 9;
-
FileAppend
public static final HederaFunctionality FileAppend
File Operation append file
FileAppend = 10;
-
FileUpdate
public static final HederaFunctionality FileUpdate
File Operation update file
FileUpdate = 11;
-
FileDelete
public static final HederaFunctionality FileDelete
File Operation delete file
FileDelete = 12;
-
CryptoGetAccountBalance
public static final HederaFunctionality CryptoGetAccountBalance
crypto get account balance
CryptoGetAccountBalance = 13;
-
CryptoGetAccountRecords
public static final HederaFunctionality CryptoGetAccountRecords
crypto get account record
CryptoGetAccountRecords = 14;
-
CryptoGetInfo
public static final HederaFunctionality CryptoGetInfo
Crypto get info
CryptoGetInfo = 15;
-
ContractCallLocal
public static final HederaFunctionality ContractCallLocal
Smart Contract Call
ContractCallLocal = 16;
-
ContractGetInfo
public static final HederaFunctionality ContractGetInfo
Smart Contract get info
ContractGetInfo = 17;
-
ContractGetBytecode
public static final HederaFunctionality ContractGetBytecode
Smart Contract, get the byte code
ContractGetBytecode = 18;
-
GetBySolidityID
public static final HederaFunctionality GetBySolidityID
Smart Contract, get by solidity ID
GetBySolidityID = 19;
-
GetByKey
public static final HederaFunctionality GetByKey
Smart Contract, get by key
GetByKey = 20;
-
CryptoGetClaim
public static final HederaFunctionality CryptoGetClaim
Crypto get the claim
CryptoGetClaim = 21;
-
CryptoGetStakers
public static final HederaFunctionality CryptoGetStakers
Crypto, get the stakers for the node
CryptoGetStakers = 22;
-
FileGetContents
public static final HederaFunctionality FileGetContents
File Operations get file contents
FileGetContents = 23;
-
FileGetInfo
public static final HederaFunctionality FileGetInfo
File Operations get the info of the file
FileGetInfo = 24;
-
TransactionGetRecord
public static final HederaFunctionality TransactionGetRecord
Crypto get the transaction records
TransactionGetRecord = 25;
-
ContractGetRecords
public static final HederaFunctionality ContractGetRecords
Contract get the transaction records
ContractGetRecords = 26;
-
CryptoCreate
public static final HederaFunctionality CryptoCreate
crypto create account
CryptoCreate = 27;
-
SystemDelete
public static final HederaFunctionality SystemDelete
system delete file
SystemDelete = 28;
-
SystemUndelete
public static final HederaFunctionality SystemUndelete
system undelete file
SystemUndelete = 29;
-
ContractDelete
public static final HederaFunctionality ContractDelete
delete contract
ContractDelete = 30;
-
UNRECOGNIZED
public static final HederaFunctionality UNRECOGNIZED
-
-
Field Detail
-
NONE_VALUE
public static final int NONE_VALUE
UNSPECIFIED - Need to keep first value as unspecified because first element is ignored and not parsed (0 is ignored by parser)
NONE = 0;
- See Also:
- Constant Field Values
-
CryptoTransfer_VALUE
public static final int CryptoTransfer_VALUE
crypto transfer
CryptoTransfer = 1;
- See Also:
- Constant Field Values
-
CryptoUpdate_VALUE
public static final int CryptoUpdate_VALUE
crypto update account
CryptoUpdate = 2;
- See Also:
- Constant Field Values
-
CryptoDelete_VALUE
public static final int CryptoDelete_VALUE
crypto delete account
CryptoDelete = 3;
- See Also:
- Constant Field Values
-
CryptoAddClaim_VALUE
public static final int CryptoAddClaim_VALUE
crypto add claim to the account
CryptoAddClaim = 4;
- See Also:
- Constant Field Values
-
CryptoDeleteClaim_VALUE
public static final int CryptoDeleteClaim_VALUE
crypto delete claim to the account
CryptoDeleteClaim = 5;
- See Also:
- Constant Field Values
-
ContractCall_VALUE
public static final int ContractCall_VALUE
Smart Contract Call
ContractCall = 6;
- See Also:
- Constant Field Values
-
ContractCreate_VALUE
public static final int ContractCreate_VALUE
Smart Contract Create Contract
ContractCreate = 7;
- See Also:
- Constant Field Values
-
ContractUpdate_VALUE
public static final int ContractUpdate_VALUE
Smart Contract update contract
ContractUpdate = 8;
- See Also:
- Constant Field Values
-
FileCreate_VALUE
public static final int FileCreate_VALUE
File Operation create file
FileCreate = 9;
- See Also:
- Constant Field Values
-
FileAppend_VALUE
public static final int FileAppend_VALUE
File Operation append file
FileAppend = 10;
- See Also:
- Constant Field Values
-
FileUpdate_VALUE
public static final int FileUpdate_VALUE
File Operation update file
FileUpdate = 11;
- See Also:
- Constant Field Values
-
FileDelete_VALUE
public static final int FileDelete_VALUE
File Operation delete file
FileDelete = 12;
- See Also:
- Constant Field Values
-
CryptoGetAccountBalance_VALUE
public static final int CryptoGetAccountBalance_VALUE
crypto get account balance
CryptoGetAccountBalance = 13;
- See Also:
- Constant Field Values
-
CryptoGetAccountRecords_VALUE
public static final int CryptoGetAccountRecords_VALUE
crypto get account record
CryptoGetAccountRecords = 14;
- See Also:
- Constant Field Values
-
CryptoGetInfo_VALUE
public static final int CryptoGetInfo_VALUE
Crypto get info
CryptoGetInfo = 15;
- See Also:
- Constant Field Values
-
ContractCallLocal_VALUE
public static final int ContractCallLocal_VALUE
Smart Contract Call
ContractCallLocal = 16;
- See Also:
- Constant Field Values
-
ContractGetInfo_VALUE
public static final int ContractGetInfo_VALUE
Smart Contract get info
ContractGetInfo = 17;
- See Also:
- Constant Field Values
-
ContractGetBytecode_VALUE
public static final int ContractGetBytecode_VALUE
Smart Contract, get the byte code
ContractGetBytecode = 18;
- See Also:
- Constant Field Values
-
GetBySolidityID_VALUE
public static final int GetBySolidityID_VALUE
Smart Contract, get by solidity ID
GetBySolidityID = 19;
- See Also:
- Constant Field Values
-
GetByKey_VALUE
public static final int GetByKey_VALUE
Smart Contract, get by key
GetByKey = 20;
- See Also:
- Constant Field Values
-
CryptoGetClaim_VALUE
public static final int CryptoGetClaim_VALUE
Crypto get the claim
CryptoGetClaim = 21;
- See Also:
- Constant Field Values
-
CryptoGetStakers_VALUE
public static final int CryptoGetStakers_VALUE
Crypto, get the stakers for the node
CryptoGetStakers = 22;
- See Also:
- Constant Field Values
-
FileGetContents_VALUE
public static final int FileGetContents_VALUE
File Operations get file contents
FileGetContents = 23;
- See Also:
- Constant Field Values
-
FileGetInfo_VALUE
public static final int FileGetInfo_VALUE
File Operations get the info of the file
FileGetInfo = 24;
- See Also:
- Constant Field Values
-
TransactionGetRecord_VALUE
public static final int TransactionGetRecord_VALUE
Crypto get the transaction records
TransactionGetRecord = 25;
- See Also:
- Constant Field Values
-
ContractGetRecords_VALUE
public static final int ContractGetRecords_VALUE
Contract get the transaction records
ContractGetRecords = 26;
- See Also:
- Constant Field Values
-
CryptoCreate_VALUE
public static final int CryptoCreate_VALUE
crypto create account
CryptoCreate = 27;
- See Also:
- Constant Field Values
-
SystemDelete_VALUE
public static final int SystemDelete_VALUE
system delete file
SystemDelete = 28;
- See Also:
- Constant Field Values
-
SystemUndelete_VALUE
public static final int SystemUndelete_VALUE
system undelete file
SystemUndelete = 29;
- See Also:
- Constant Field Values
-
ContractDelete_VALUE
public static final int ContractDelete_VALUE
delete contract
ContractDelete = 30;
- See Also:
- Constant Field Values
-
-
Method Detail
-
values
public static HederaFunctionality[] values()
Returns an array containing the constants of this enum type, in the order they are declared. This method may be used to iterate over the constants as follows:for (HederaFunctionality c : HederaFunctionality.values()) System.out.println(c);
- Returns:
- an array containing the constants of this enum type, in the order they are declared
-
valueOf
public static HederaFunctionality valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)- Parameters:
name
- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
java.lang.IllegalArgumentException
- if this enum type has no constant with the specified namejava.lang.NullPointerException
- if the argument is null
-
getNumber
public final int getNumber()
- Specified by:
getNumber
in interfacecom.google.protobuf.Internal.EnumLite
- Specified by:
getNumber
in interfacecom.google.protobuf.ProtocolMessageEnum
-
valueOf
@Deprecated public static HederaFunctionality valueOf(int value)
Deprecated.Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)- Parameters:
value
- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
java.lang.IllegalArgumentException
- if this enum type has no constant with the specified namejava.lang.NullPointerException
- if the argument is null
-
forNumber
public static HederaFunctionality forNumber(int value)
-
internalGetValueMap
public static com.google.protobuf.Internal.EnumLiteMap<HederaFunctionality> internalGetValueMap()
-
getValueDescriptor
public final com.google.protobuf.Descriptors.EnumValueDescriptor getValueDescriptor()
- Specified by:
getValueDescriptor
in interfacecom.google.protobuf.ProtocolMessageEnum
-
getDescriptorForType
public final com.google.protobuf.Descriptors.EnumDescriptor getDescriptorForType()
- Specified by:
getDescriptorForType
in interfacecom.google.protobuf.ProtocolMessageEnum
-
getDescriptor
public static final com.google.protobuf.Descriptors.EnumDescriptor getDescriptor()
-
valueOf
public static HederaFunctionality valueOf(com.google.protobuf.Descriptors.EnumValueDescriptor desc)
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)- Parameters:
desc
- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
java.lang.IllegalArgumentException
- if this enum type has no constant with the specified namejava.lang.NullPointerException
- if the argument is null
-
-


Next: Objectives
Up: INTRODUCTION
Previous: Example Application
SLALIB contains 183 routines covering the following topics:
- String Decoding,
Sexagesimal Conversions
- Angles, Vectors & Rotation Matrices
- Calendars,
Timescales
- Precession & Nutation
- Proper Motion
- FK4/FK5/Hipparcos,
Elliptic Aberration
- Geocentric Coordinates
- Apparent & Observed Place
- Azimuth & Elevation
- Refraction & Air Mass
- Ecliptic,
Galactic,
Supergalactic Coordinates
- Ephemerides
- Astrometry
- Numerical Methods
Next: Objectives
Up: INTRODUCTION
Previous: Example Application
SLALIB --- Positional Astronomy Library
Starlink User Note 67
P. T. Wallace
12 October 1999
E-mail:ptw@star.rl.ac.uk


{% extends "pretixcontrol/event/base.html" %} {% load i18n %} {% load bootstrap3 %} {% load eventurl %} {% block title %}{% trans "Swap Request Statistics" %}{% endblock %} {% block content %}
{% blocktrans trimmed %} With this table, you can see how many users currently want to cancel their orders, and if there are matching orders waiting for approval. You can approve orders (as long as your quotas permit it). {% endblocktrans %}
{% blocktrans trimmed %} When you approve orders, the waiting customers are sent an email that their order is now pending and that they need to pay. Only once they have paid, a matching order waiting to cancel will be canceled. {% endblocktrans %}
| {% trans "Product" %} | {% trans "Waiting swaps" %} | {% trans "Completed swaps" %} | {% trans "Waiting cancelations" %} | {% trans "Completed cancelations" %} |
|---|---|---|---|---|
| {{ line.subevent }} | {{ line.open_swap_requests }} | {{ line.completed_swap_requests }} | {{ line.open_cancelation_requests }} | {{ line.completed_cancelation_requests }} |


getting_started.Rmd
The shinyMixR
package is developed as a graphical user
interface around the nlmixr
and nlmixr2
package. It is build with the shiny
package combined with
bs4Dash
. Many of the functions within the package can also
be used outside the interface within an interactive R session. This
vignette will give a brief introduction on how the package can be used
and what the most important functions are. When working with this
package, there are two important assumptions:
create_proj
function)To get started, first all relevant packages need to be installed, e.g.:
# For development versions
devtools::install_github("richardhooijmaijers/shinyMixR")
# Or for CRAN release
install.packages("shinyMixR")
# It is advised to use the CRAN releas of nlmixr2
install.packages("nlmixr2")
# It is advised to use xpose.nlmixr2 for easy diagnostics
install.packages("xpose.nlmixr2")
The easiest way to get to know the package is to start by creating the necessary folder structure:
library(shinyMixR,quietly = TRUE)
create_proj()
By default, a folder structure is created within the current
directory, which will include some example models. It is however also
possible to create a project in any other folder
(e.g. create_proj(loc='/anypath')
). The following folders
are created:
nlmixr
The interface monitors what happens in these folders. This is important to know because new models and/or data can be copied into these folders or files can be removed. This will then be recognized within the app (after refreshing the overview). This way it is possible to work on data and models separately and plug it in to shinyMixR at a later stage.
Once there is a folder structure present the interface can be started:
run_shinymixr(launch.browser = TRUE)
The interface will be started and a project object will be created in the global environment in which all information is kept/managed. If correct, the interface will open in the default browser and the following will be seen:
On the left side, there is sidebar with various menu items. The content of the main body will open with the model overview but changes based on the selected menu item in the sidebar. The sidebar can be collapsed by clicking the three lines in the top bar, providing more room for the main body.
The overview page can be used to see which models are present in a
project. This overview can be exported to a CSV file and a selection of
columns can be made that should be displayed (all using the
DT
package). Also a tree overview of the models can be
created here, to show how the various models within your project relate
to one another. Within this view there are several main actions one can
perform which are discussed in the the following subsections.
The interface will work with the folder structure which holds all project information. In case new models are added manually or result files are created after a model run, the interface needs to be refreshed to show the latest information. This can be done by clicking the refresh button available in the overview.
Each model file within your project can hold meta data. This meta data consist of:
nlmixr2
package (see
nlmixr2est::nlmixr2AllEst()
for supported methods).saemControl
or
foceiControl
)subset
function in R. This is used to create a subset of
the data passed to the model (e.g. comparable with IGNORE statements in
NONMEM)Using the “Adapt meta data” button within the overview, you can easily create or change the meta data for a model. This meta data will be adapted in the model file itself an can be seen when the model is opened in the editor.
It is possible to write your own scripts that can be used to analyse model results. This script can be used to process the result for one or multiple models at once (the interface will include the name of the selected models in the script). Some example scripts are included in the package and available in the scripts folder when a project is created. It is possible to create your own script by taking one of the example scripts as an example.
It is possible to view and combine the results from the models within a project using the “Create report” button. When results are created using one of the scripts mentioned above, results will be present in a default location. The “Create report” functionality can combine the results in an overall document for easy sharing or discussions.
The edit tab can be used to edit existing models within an editor
including syntax coloring (using the shinyAce
package). It
is also possible to create new models using various templates or to
duplicate existing models. Finally the initial estimates for a model can
be updated using the final estimates of (another) model.
The run tab can be used to run models within a project. It is possible to run one or multiple models at once. Also it is possible to assess the intermediate output or progress for an nlmixr2 run. Furthermore, you can see which models are still running on the background and kill any model submitted from the interface.
The parameter estimates tab can be used to generate a table with parameter estimates. In case multiple models are selected the table will show the results of each run in a separate column. This page is reactive which means that in case a different model is selected, the table is directly updated. There are possibilities to save the table to a latex/pdf or html file, show back-transformed values or to include shrinkage and between subject variability within the output
The goodness of fit tab can be used to generate a the most relevant
goodness of fit plots. Plots can be generate using the
nlmixr.xpose2
package or directly using ggplot
(this can be specified in the settings widget). Also here the plots can
be saved to a latex/pdf or html file. Additional options are present to
pre-process your data, select the type of plot and color observations by
a variable in your data.
The fit plots tab can be used to generate a individual fit plots. In general similar options are present here as for the goodness of fit plots. Additionally the variables for plotting can be selected to enable different types of plots.
The data exploration tab can be used to generate exploratory plots for input or results data. Different types of plots are possible including point, line, boxplot, barplot, histograms and more. Different layers can be added to the plot and simple summary stats can be included. Finally the data can be presented as plot, interactive plotly or table.
When working in an interactive R session, many functions used by the interface are also available from an interactive R session. When working outside the interface it is important to know how to interact with the project object. This object should be created as one of the first steps because other function rely on the availability of this object:
proj_obj <- get_proj()
This function will look in the folder structure to create or update the available information. The result is a list that is build-up as follows:
object
|--- run 1
| |--- model location
| |--- model meta data
| |--- model high level results
|
|--- ...
|
|--- meta data (time of last refresh)
In case this object is not present it will be created by looking at the files present in the current folder structure. In case the object is already present it will check if newer files are present in the current folder and will update the object with this information. Therefore one have to be aware that this function should be submitted manually in case new information is present in the one of the folders.
Once a folder structure is in place and the project object is created, an overview can be created for the available models and, if models are submitted, high level results. It is also possible to display a collapsible d3 tree view of the models. This is mainly useful in case reference to models is provided to show the hierarchy of the models within a project:
Although the nlmixr2
package obviously has the
possibility to run nlmixr models, the shinyMixR package also have a
function available named run_nmx
. the main reason this
function was written is the option to run the model in an external R
session. This is necessary within the interface to overcome the
application from freezing when a model is submitted. Also within an
interactive R session it is convenient because you do not have to wait
for a run to finish. An example how this can be used is given below:
run_nmx("run1")
# progress of a run is written to external text file
# this can be read-in for intermediate assessment
readLines("shinyMixR/temp/run1.prog.txt")
The current version of the package has three functions for assessing
the model results. The first function is to create a simple parameter
table par_table
. By default this function returns a
data.frame. In case multiple models are selected, each column will have
the results of the selected model. The results can also be written to a
PDF (using latex) or html file using the R3port
package:
# Default data frame
par_table(proj_obj,c("run1","run2"))
# output to tex file (compiled to pdf)
par_table(proj_obj, models="run1", outnm="par.tex")
For assessing the goodness of fit, the gof_plot
function
can be used. This function will by default use the
nlmixr.xpose2
package to create 4 different types of plots.
It is also possible to directly create ggplot2 types of plots. By
default the plots will be created within the R session but can also be
written to pdf/html using the R3port
package:
res <- readRDS("./shinyMixR/run1.res.rds")
gof_plot(res)
# gof_plot(res, mdlnm="run1", outnm="gof.tex")
The last plot is an individual fit plot fit_plot
. This
function will also by default use the nlmixr.xpose2
package
to create a plot per individual including the observed data, individual
and population predictions. Also here it is possible to create
ggplot2
types of plots which provide a bit more flexibility
as shown below and plots can be outputted to pdf/html:
res$TRT <- ifelse(as.numeric(res$ID)<6,1,2)
fit_plot(res, by="TRT", PRED="CPRED", type="user",logy=FALSE)
# fit_plot(res, mdlnm="run1", outnm="fit.html")


WITNESS LIST
Aging Committee
April 26, 2012 - 1:00 PM
Attendant Services
Registering, but not testifying:
On:
Crowther, Nancy (Personal Attendant Coalition of Texas)
Innovative Transportation Strategies
On:
Freund, Katherine (ITN America)
Hine, Jim (Public Policy Solutions)
The Economic Value of Family Caregiving
On:
Fredriksen, Amanda (AARP)
The Workforce Serving Aging Texans
On:
Bradberry, Anita (Texas Association for Home Care and Hospice)
Dyer, Carmel (Division of Geriatric and Palliative Medicine at The University of Texas
Medical School at Houston)
Grenwelge, Cheryl (Postsecondary Access and Training in Human Services Program)
Roberts, Eric (Postsecondary Access and Training in Human Services Program)
Weizenbaum, Jon (Department of Aging and Disability Services)
1


Feel free to use this tool... until I run into the API limit. Enter the URL to an image of printed text, click the Read image button. This app will try to OCR the text. Created using Microsoft's Cognitive Vision -Johan
Response:
Formatted output:
Source image:


---
title: psadmin.io Community Wiki
layout: en
permalink: /
no_header: true
short_title: true
---
Welcome!
The Community Wiki is a place for PeopleSoft Administrators to share documentation on setting up new features, how they resolved issues, and anything else they would like to share.
How to use the wiki
On the left are folder to group the various topics related to PeopleSoft Adminstration:
- PeopleTools: Looking to configure a feature that is available under
Main Menu > PeopleTools
? Look under here.
- Database: Articles about managing or working the the database.
- Middleware: Want to read about Tuxedo, Java, WebLogic, COBOL. The middleware folder is for all supporting software that runs PeopleSoft
- PeopleSoft Cloud Architecture: This area include Deployment Packages, Puppet, or anything about automation.
- Server Administration: Articles about working with Windows, Linux, AIX or other server management topics.
How to contribute
Any one can contribute to the Communtiy Wiki. To make a contribution or edit, you'll need a GitHub account. (Optional: Git installed, good text editor, and are familiar with Markdown formatting.)


KEC Student+
Contact Us
Hands behind this Website
Ajay (Web Designer) / Project Architect

Arul (Front-End Developer) / Project Designer

Abinash (Full Stack Web Developer)
Project Lead

Adhithiya (Web App Developer) / Project Analyst

Shareeq (UX Designer) / Project Member

Staff Co-ordinators:
Dr. S. Malliga
(Professor, CSE) |
Dr. N. Shanthi
(HOD, CSE)
Department of Computer Science and Engineering
Kongu Engineering College
Front-End Framework:
Semantic-UI
References:
View Docs
Gotta say something?
Contact us here!


The Flying Dutchman welcomes you into a classic, stylish relaxed atmosphere, serving a gourmet bar menu selection with a grand selection of fine wines and beers. At night, The Flying Dutchman is a perfect sanctuary to wind down after an exciting day. Relax with a refreshing beer, glass of wine or your favourite beverage.
Order Now!