remotebasehq
Inc. – Terms and Conditions of Use
Language:
This agreement was written in English (US). To the extent any translated version of this agreement
conflicts with the English version, the English version controls. Please note that Appendix A contains
certain changes to the general terms for users outside the United States.
Date
of Last Revision:
January
25, 2019
remotebasehq:
Any reference to “remotebasehq” includes both remotebasehq the company and REMOTEBASEHQ the app.
Terms
and Conditions
This
Statement of Terms and Conditions (“Terms and Conditions”) derives from the remotebasehq Principles and
governs our relationship with our users, as well as anyone else who interacts with remotebasehq Services
or the [REMOTEBASEHQ App] (“Services”). This Statement is an agreement between you and remotebasehq Inc.
By using or accessing remotebasehq, you agree to this Statement, as updated from time to time in
accordance with Section 12 (“Amendments”) below. For the purposes of this document, “remotebasehq” or
“we” or “our” means remotebasehq Inc. and its subsidiaries.
Because
remotebasehq provides a wide range of Services, we may ask you to review and accept supplemental terms
that apply to your interaction with a specific app, product, or service. To the extent those
supplemental terms conflict with this statement of terms and conditions, the supplemental terms
associated with the app, product, or service govern with respect to your use of such app, product, or
service to the extent of the conflict.
- Privacy
Your
privacy is very important to us. We designed our Privacy Policy to make important disclosures about
how you can use remotebasehq to share with others and how we collect and can use your content and
information. We encourage you to read the Privacy Policy, and to use it to help you make informed
decisions.
- Sharing
Your Content and Information
You
own all of the content and information you post on remotebasehq. To the extent any of your information
may be shared, you will be able to control how it is shared through your privacy and application
settings. In addition:
-
For
content that is covered by intellectual property rights, like photos and videos (IP content), you
specifically give us the following permission, subject to your privacy and application settings:
you grant us a non-exclusive, transferable, sub-licensable, royalty-free, worldwide license to use
any IP content that you post on or in connection with remotebasehq (“IP License”). This IP License
ends when you delete your IP content or your account unless your content has been shared with
others, and they have not deleted it.
-
When
you delete IP content, it is deleted from the active remotebasehq system. However, you understand
that removed content may persist in backup copies for a reasonable period of time (but will not be
available to others).
-
If
you use an application, the application may ask for your permission to access your content and
information as well as content and information that others have shared with you. We require
applications to respect your privacy, and your agreement with that application will control how the
application can use, store, and transfer that content and information. (To learn more about
Platform, including how you can control what information other people may share with applications,
read our Privacy Policy Page.)
-
If
you publish content or information using a Public setting, it means that you are allowing everyone,
including people outside remotebasehq, to access and use that information, and to associate it with
you (e.g., your name and profile picture).
-
We
always appreciate your suggestions or feedback about remotebasehq, and you understand that these are
offered gratuitously without any expectation of, or right to, compensation for them (just as you
have no obligation to offer them).
- Safety
In
order to facilitate the safety of all users of remotebasehq, we request your help, including the
following commitments by you:
-
You
will not post unauthorized commercial communications (such as spam) on remotebasehq.
-
You
will not collect users’ content or information, or otherwise access remotebasehq, using automated
means (such as harvesting bots, robots, spiders, or scrapers) without our prior permission.
-
You
will not engage in unlawful multi-level marketing, such as a pyramid scheme, on remotebasehq.
-
You
will not upload viruses or other malicious code.
-
You
will not solicit login information or access an account belonging to someone else.
-
You
will not bully, intimidate, or harass any user, and you will take full responsibility for your
actions and their consequences on others, and indemnify and hold harmless remotebasehq for any such
consequences to others.
-
You
will not post content that: is hate speech, threatening, or pornographic; incites violence; or
contains nudity or graphic or gratuitous violence.
-
You
will not develop or operate a third-party application containing alcohol-related, dating or other
mature content (including advertisements) without appropriate age-based restrictions.
-
You
will not use remotebasehq to do anything unlawful, misleading, malicious, or discriminatory.
-
You
will not do anything that could disable, overburden, or impair the proper working or appearance of
remotebasehq, such as a denial of service attack or interference with page rendering or other
remotebasehq functionality.
-
You
will not facilitate or encourage any violations of this Statement or our policies.
- Registration
and Account Security
remotebasehq
users provide their real names and information, and we need your help to keep it that way. Here are
some commitments you make to us relating to registering and maintaining the security of your
account:
-
You
are choosing to join remotebasehq of your own volition. It is your responsibility to keep track of
the rules of the ratings, and you accept the actual outcomes of the ratings provided by our
community via the [remotebasehq App]. We are not liable for the actual ratings provided by our
community.
-
You
will not provide any false personal information on remotebasehq or create an account for anyone other
than yourself without permission.
-
You
will not create more than one personal account.
-
If
we disable your account, you will not create another one without our permission.
-
You
will not use remotebasehq if you are
under
17.

-
You
will keep your contact information accurate and up-to-date.
-
You
will not share your password, let anyone else access your account, or otherwise jeopardize the
security of your account.
-
You
will not transfer your account to anyone without first getting our written permission.
-
If
you select a username or similar identifier for your account, we reserve the right to remove or
reclaim it if we believe it necessary (such as when, for example, a trademark may be
violated).
-
You
understand and agree to assume the risk that, despite reasonable efforts by remotebasehq Inc.,
account security may be compromised and/or private user data may be stolen. In case of such an
intrusion, remotebasehq will take reasonable and diligent measures to notify all affected users of
any such intrusion, and to reestablish full account security as quickly as reasonable possible.
You agree to assume the risk and hold remotebasehq not liable for any such loss, or consequential or
other losses, directly or indirectly related to any such security breach.
- Protecting
Other People's and Companies’ Rights
We
respect other people’s and companies’ rights and expect you to do the same.
-
You
will not post content or take any action on remotebasehq that infringes or violates someone else’s
rights or otherwise violates the law.
-
We
can remove any content or information you post on remotebasehq if we believe that it violates this
Statement, our policies, or applicable laws or regulations.
-
We
provide you with tools to help you protect your intellectual property rights. To learn more, email
us at<EMAIL_ADDRESS>will review your email and will make our best effort to respond, although we cannot guarantee a
response to all emails.
-
If
we remove your content for infringing someone else’s intellectual property rights and you
disagree,
we
will provide you with an opportunity to appeal.
-
If
you repeatedly infringe intellectual property rights of others, we reserve the right to temporarily
or permanently disable your account.
-
You
will not use our copyrights or Trademarks or any confusingly similar marks, except with our prior
written permission. Please contact<EMAIL_ADDRESS>for more information. We will review your email and will make our best effort to respond, although
we cannot guarantee a response to all emails.
-
If
you collect information from users, you will: obtain their consent, make it clear that you (and not
remotebasehq) are the one collecting their information, and post a privacy policy explaining what
information you collect and how you will use it.
-
You
will not post anyone’s identification documents, sensitive financial information, or other private
data on remotebasehq.
-
You
will not send email invitations to non-users without their consent.
-
You
agree to provide truthful and honest ratings based on Your own experiences and actual use of the
platforms for which You provide ratings.
-
You
agree that Your ratings are Your own and do not reflect the opinions of Remotebasehq or its
employees. You agree that Remotebasehq only provides a platform for You to provide Your ratings, and
that Remotebasehq does not itself provide any ratings. You agree that Remotebasehq is not liable for
any ratings You provide on the Remotebasehq platform, or the impact of your ratings on the respective
JF Index results.
-
You
agree that the list of social media platforms available for rating may change from time to time, in
the sole discretion of Jvstfamovs.
- Mobile
and Other Devices
-
We
currently provide our mobile Services for free, but please be aware that your carrier’s normal
rates and fees, such as text messaging and data charges, will still apply.
-
In
the event you change or deactivate your mobile telephone number, you will update your account
information on remotebasehq within a reasonable time to ensure that your messages are not sent to the
person who acquires your old number.
-
You
provide consent and all rights necessary to enable users to sync (including through an application)
their devices with any information that is visible to them on remotebasehq.
- About
Advertisements and Other Commercial Content Served or Enhanced by remotebasehq
Our
goal is to deliver advertising and other commercial or sponsored content that is valuable to our users
and advertisers. In order to help us do that, you agree to the following:
-
You
give us permission to use your name, profile picture, content, and information in connection with
commercial, sponsored, or related content (such as a brand you like) served or enhanced by us.
This means, for example, that you permit a business or other entity to pay us to display your name
and/or profile picture with your content or information, without any compensation to you. If you
have selected a specific audience for your content or information, we will respect your choice when
we use it.
-
We
do not give your content or information to advertisers without your consent.
-
You
understand that we may not always identify paid Services and communications as such.
- Special
Provisions Applicable to Software
-
If
you download or use our software, such as a stand-alone software product, an app, or a browser
plugin, you agree that from time to time, the software may download and install upgrades, updates
and additional features from us in order to improve, enhance, and further develop the
software.
-
You
will not modify, create derivative works of, decompile, or otherwise attempt to extract source code
from us, unless you are expressly permitted to do so under an open source license, or we give you
express written permission.
- remotebasehq’
Proprietary Ranking Algorithms
By
using or accessing remotebasehq, you agree to the application of remotebasehq’ proprietary ranking
algorithms. The algorithms used by remotebasehq to provide its relative ranking of entities are
proprietary and may, in the sole discretion of remotebasehq, be adjusted, revised or otherwise modified
from time to time based on customer or user behaviors, or for any other reason.
- Amendments
By
using or accessing remotebasehq, you agree to this Statement, which may be updated from time to time in
accordance with this Section.
-
We’ll
notify you before we make changes to these terms and give you the opportunity to review the revised
terms before continuing to use our Services.
-
If
we make changes to policies, guidelines or other terms referenced in or incorporated by this
Statement, we will provide reasonable notice.
-
Your
continued use of the remotebasehq Services, following notice of the changes to our terms, policies or
guidelines, constitutes your acceptance of our amended terms, policies or guidelines.
-
The
most current version of the policy will govern our processing of your personal data and will always
be available inside the REMOTEBASEHQ application.
- Termination
If
you violate the letter or spirit of this Statement, or otherwise create risk or possible legal exposure
for us, we may stop providing all or part of our Services to you. We will notify you by email or at
the next time you attempt to access your account. You may also delete your account or disable your
application at any time. At our sole discretion, we may discontinue to offer our Services to anyone,
or everyone, for any reason or for no specific reason at any time. In this case, we have no obligation
to continue providing our Services, and we are not responsible to provide any data to any user,
including current or historical data of any kind. In all such cases, all applicable provisions of this
Statement shall still apply.
- Disputes
-
You
will resolve any
claim, cause of action, or dispute (claim) you have with us arising out of or relating to this
Statement or remotebasehq exclusively
through Arbitration as detailed in the Arbitration Agreement in Appendix B.
-
If
anyone brings a claim against us related to your actions, content or information on remotebasehq, you
will indemnify and hold us harmless from and against all damages, losses, and expenses of any kind
(including reasonable legal fees and costs) related to such claim. Although we provide rules for
user conduct, we do not control or direct users’ actions on remotebasehq and are not responsible for
the content or information users transmit or share on remotebasehq. We are not responsible for any
offensive, inappropriate, obscene, unlawful, or otherwise objectionable content or information you
may encounter on remotebasehq. We are not responsible for the conduct, whether online or offline, of
any user of remotebasehq.
    WE WILL NOT BE LIABLE TO YOU FOR ANY LOST PROFITS OR OTHER
CONSEQUENTIAL, SPECIAL, INDIRECT, OR INCIDENTAL DAMAGES ARISING OUT OF OR IN CONNECTION WITH THIS
STATEMENT OR remotebasehq, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
APPLICABLE LAW MAY NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY OR INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. IN SUCH CASES,
remotebasehq ' LIABILITY WILL BE LIMITED TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW.
- Definitions
-
By
“remotebasehq” or “remotebasehq Services” we mean the features and services we make available,
including through (a) our website at www.remotebasehq.com
and any other remotebasehq branded or co-branded websites (including sub-domains, international
versions, widgets, and mobile versions); (b) our Platform; and (d) other media, brands, products,
services, software (such as a toolbar), devices, or networks now existing or later developed.
remotebasehq reserves the right to designate, in its sole discretion, that certain of our brands,
products, or services are governed by separate terms and not this Statement of Terms and
Conditions.
-
By
“Platform” we mean a set of APIs and services (such as content) that enable others, including
application developers and website operators, to retrieve data from remotebasehq or provide data to
us.
-
By
“information” we mean facts and other information about you, including actions taken by users and
non-users who interact with remotebasehq.
-
By
“content” we mean anything you or other users post, provide or share using our Services.
-
By
“data” or “user data” or “user’s data” we mean any data, including a user’s content or information
that you or third parties can retrieve from remotebasehq or provide to remotebasehq through any
Platform.
-
By
“post” we mean post on remotebasehq or otherwise make available by using remotebasehq.
-
By
“use” we mean use, run, copy, publicly perform or display, distribute, modify, translate, and
create derivative works of.
-
By
“application” we mean any application or website that uses or accesses our Platform, as well as
anything else that receives or has received data from us. If you no longer access our Platform but
have not deleted all data from us, the term application will apply until you delete the data.
-
By
“Trademarks” we mean all current and future registered trademarks of remotebasehq Inc.
- Other
-
This
Statement makes up the entire agreement between the parties regarding remotebasehq and supersedes any
prior agreements.
-
If
any portion of this Statement is found to be unenforceable, the remaining portion will remain in
full force and effect.
-
If
we fail to enforce any part of this Statement, it will not be considered a waiver.
-
Any
amendment to or waiver of this Statement must be made in writing and signed by us.
-
You
will not transfer any of your rights or obligations under this Statement to anyone else without our
consent.
-
All
of our rights and obligations under this Statement are freely assignable by us in connection with a
merger, acquisition, or sale of assets, or by operation of law, or otherwise.
-
Nothing
in this Statement shall prevent us from complying with applicable law.
-
This
Statement does not confer any third-party beneficiary rights.
-
We
reserve all rights not expressly granted to you.
-
You
will comply with all applicable laws when using or accessing remotebasehq.
-
Any
feedback and suggestions are welcome and completely voluntary. remotebasehq does not provide any
compensation for any such feedback and suggestions.
By
using or accessing our
Services,
you agree that we can collect and use such content and information in accordance with the Privacy
Policy as amended from time to time.
Appendix
A – Foreign Users
Special
Provisions Applicable to Users Outside the United States
We
strive to create a global community with consistent standards for everyone, but we also strive to
respect local laws. The following provisions apply to users and non-users who interact with remotebasehq
outside the United States:
-
You
consent to having your personal data transferred to and processed in the United States under United
States law.
-
If
you are located in a country embargoed by the United States or are on the U.S. Treasury
Department’s list of Specially Designated Nationals you will not engage in commercial activities on
remotebasehq (such as advertising or payments) or operate a Platform application or website. You
will not use remotebasehq if you are prohibited from receiving products, Services, or software
originating from the United States.
Special
Provisions Applicable to European Citizens
We
do not manage European Personal Data, therefore our services are not allowed for European Citizens.
Moreover, the App is only available for download in the US App Store, and governed by the US
Laws.
Appendix
B – Arbitration Agreement
remotebasehq
Inc. Arbitration Agreement
-
Any
claim, cause of action, or dispute (claim) you have with us arising out of or relating to
remotebasehq or the Statement of Terms and Conditions (“Agreement”), including, without limitation,
any dispute concerning the construction, validity, interpretation, enforceability or breach of the
Agreement, shall be exclusively resolved by binding arbitration upon a Party’s submission of the
dispute to arbitration. The complaining Party shall seek remedies exclusively through
arbitration. The demand for arbitration shall be made within a reasonable time after the claim,
dispute or other matter in question has arisen, and in no event shall it be made after two years
from when the aggrieved party knew or should have known of the controversy, claim, dispute or
breach.
-
This
agreement to arbitrate shall be specifically enforceable. A Party may apply to any court with
jurisdiction for interim or conservatory relief, including without limitation a proceeding to
compel arbitration.
-
The
arbitration shall be conducted by one arbitrator. If the Parties are not able to agree upon the
selection of an arbitrator, within twenty days of commencement of an arbitration proceeding by
service of a demand for arbitration, the arbitrator shall be selected by the American Arbitration
Association in accordance with the terms of this agreement.
-
The
arbitrator shall have ten years of experience in commercial arbitration and also shall have served
as an arbitrator at least three times prior to their service as an arbitrator in this
arbitration.
-
The
arbitration shall be conducted in accordance with the then existing Commercial Rules of the
American Arbitration Association.
-
The
arbitration shall be conducted in
Austin,
Texas.
-
The
laws of the State of Texas shall be applied in any arbitration proceedings, without regard to
principles of conflict of laws.
-
It
is the intent of the parties that, barring extraordinary circumstances, arbitration proceedings
will be concluded within one hundred and twenty days from the date the arbitrator is appointed.
The arbitrator may extend this time limit in the interests of justice. Failure to adhere to this
time limit shall not constitute a basis for challenging the award.
-
Except
as may be required by law, neither a party nor its representatives may disclose the existence,
content, or results of any arbitration hereunder without the prior written consent of all
parties.
-
The
Parties shall not be entitled to discovery in the arbitration except that any Party shall be
entitled to request no more than 1000 pages of documents and to take three depositions not to
exceed eight hours for each such deposition. Any Party shall be entitled to depose any expert who
will testify in the arbitration proceeding but shall pay the regular hourly rate of such expert
during such deposition.
-
The
Parties shall exchange a copy of all exhibits for the arbitration hearing and shall identify each
witness who will testify at the arbitration, with a summary of the anticipated testimony of such
witness ten days before the arbitration hearing.
-
The
arbitrator shall have no authority to award punitive/consequential/ special/indirect damages. The
arbitrators shall not be entitled to issue injunctive and other equitable relief.
-
The
cost of the arbitration proceeding and any proceeding in court to confirm or to vacate any
arbitration award, as applicable (including, without limitation, reasonable attorneys’ fees and
costs), shall be borne by the unsuccessful party, as determined by the arbitrators, and shall be
awarded as part of the arbitrator’s award. It is specifically understood and agreed that any party
may enforce any award rendered pursuant to the arbitration provisions of this Section by bringing
suit in any court of competent jurisdiction. This Section shall survive the termination or
cancellation of this Agreement, or the users’ discontinuation of remotebasehq Services as defined in
the applicable Terms and Conditions.
-
Each
party shall pay its own proportionate share of arbitrator fees and expenses and the arbitration
fees and expenses of the American Arbitration Association. The arbitrator shall be entitled to
award the foregoing arbitration and administrative fees and expenses as damages in the arbitrators’
discretion.
Appendix
C – Cookie Policy
remotebasehq
Inc. Cookie Policy
-
By
using or accessing remotebasehq, you are consenting to our use of Cookies as outlined below.
Introduction:
What is a cookie?
-
This
Cookie policy helps to explain the occasions when and why cookies may be sent to visitors to the
site (referred to in this policy as “we”, “us” or “our”). “Cookies” are text-only pieces of
information that a website transfers to an individual’s hard drive or other website-browsing
equipment for record-keeping purposes. Cookies allow the Site to remember important information
that is intended to make your use of the site more convenient. A cookie will typically contain the
name of the domain from which the cookie has come, the “lifetime” of the cookie, and a randomly
generated unique number or other value. Certain cookies will be used on the Site regardless of
whether you are logged in to your account or not.
-
Session
Cookies are temporary cookies that remain in the cookie file of your browser until you leave the
Site.
-
Persistent
Cookies remain in the cookie file of your browser for much longer (though how long will depend on
the lifetime of the specific cookie).
Session
cookies may be used to track the total number of visitors to our site, which is typically done on
an anonymous aggregate basis (as cookies do not in themselves carry any personal data). We may
also employ cookies so that we remember your computer when it is used to return to the site to help
customize your remotebasehq experience.
We
may associate personal information with a cookie file in those instances.
How
remotebasehq uses cookies
-
Like
most websites, we use cookies for a variety of purposes in order to improve your online experience,
for analytics and for marketing, but specifically we may use Cookies on the site for the following
purposes:
-
Analytical
Purposes:
we may use cookies to analyze user activity in order to improve the site. For example, we can use
cookies to look at aggregate patterns like the average number of job searches that users perform.
We can use such analysis to gain insights about how to improve the functionality and user
experience of the site.
-
Your
Preferences & User Experience:
We may use cookies to gather certain information about users, such as browser type, server,
language preference, and country setting, in order to store user preferences on our site to make
your user experience more consistent and convenient. For example, we may store the recent searches
you have performed in a cookie so that we can allow you to easily repeat those searches when you
return to our Site. In addition, we use cookies to maintain your logged in state when you visit
our Site repeatedly. We may also use your IP address to determine your geographic location in
order to provide you with the most relevant search results.
-
Marketing:
We may use cookies from third-party partners such as Google and Facebook for marketing purposes.
These cookies enable display of remotebasehq promotional material to you on other sites you visit
across the Internet. remotebasehq may also share information about your behavior on the site with
third parties (including operators of third-party websites and/or social networking sites) in order
to show you targeted advertisements and other content that has been customized for you. We also
use cookies to facilitate targeted ads.
-
Referral
Tracking:
We may use cookies to associate user activity with a third-party website that referred a user to
our site, or to associate user activity that we referred to a third-party website. These
third-party partner websites may receive credit for the activity of users they refer to our site or
give us credit for the activity of users referred to such third-party websites. We do not share
any personal information or information about individual user activities with these partner
entities.
-
Security
Purposes:
We may use cookies to limit certain types of cyber-attacks.
-
Testing,
Usability, and Performance Improvement Purposes:
We may use cookies to ensure users receive a consistent user experience while we conduct testing on
certain aspects of our site in order to improve our product offerings. We also use cookies to
improve the performance and reliability of our site.
-
Fraud/Spam
prevention:
We may use cookies during fraud reviews and investigations.
Managing
cookies in your browser
-
Use
the options in your web browser if you do not wish to receive a cookie or if you wish to set your
browser to notify you when you receive a cookie. You can easily delete and manage any cookies that
have been installed in the cookie folder of your browser by following the instructions provided by
your particular browser manufacturer.
-
You
may also consult your mobile device documentation for information on how to disable cookies on your
mobile device. If you disable all cookies, you may not be able to take advantage of all the
features of our site.
Changes
to our Cookie Policy
-
From
time to time, it may be necessary for us to change this cookie policy. We suggest that you check
here periodically for any changes.
For
more information about REMOTEBASEHQ, please visit www.remotebasehq.com.


Welcome to the Bank!
How much do you want to deposit?
Deposit
How much do you want to withdraw?
Withdraw


Preview: Heat try to bounce back from rough road loss with home showdown against Hornets
by APTV: FOX Sports Sun
TIME: Pregame coverage begins at 7 p.m.
STREAM IT LIVE ON FOX SPORTS GO
Charlotte Hornets (6-11, 10th in the Eastern Conference) vs. Miami Heat (11-4, third in the Eastern Conference)
Miami comes into a matchup against Charlotte as winners of four home games in a row.
Miami went 39-43 overall and 7-9 in Southeast Division games in the 2018-19 season. The Heat averaged 105.7 points per game while shooting 45% from the field and 34.9% from 3-point range last season.
Charlotte went 10-6 in Southeast Division play and 14-27 on the road during the 2018-19 season. The Hornets averaged 23.2 assists per game on 40.2 made field goals last season.
The matchup Monday is the first meeting this season for the two teams.
Heat Injuries: Justise Winslow: out (concussion), KZ Okpala: day to day (left achilles strain), Derrick Jones Jr.: out (hip).
Hornets Injuries: None listed.


Become a Member
Welcome to the Super 8 Film Society. We are a group of film enthusiasts who meet up each month to watch old movies on film, in our own private cinema. We also create our own short film each year, which is entered into film competitions worldwide.


CodeMirror: Pig Latin mode with AutoCompletion
-- Apache Pig (Pig Latin Language) Demo /* This is a multiline comment. */ a = LOAD '/path/to/input' USING PigStorage('\t') AS (x:long, y:chararray, z:bytearray); b = GROUP a BY (x,y,3+4); c = FOREACH b GENERATE flatten(group) as (x,y), SUM(group.$2) as z; STORE c INTO '/path/to/output'; --
Simple mode that handles Pig Latin language.
MIME type defined:
text/x-pig
(PIG code)


MEMBER FORM
Membership Number
Gender
Gender
M
F
First name
Date of Birth
Last name
Join Date
Address
Postcode
Type of Membership
Type-Member
F
S
T
B
Subscription Due Month
Month
January
February
March
April
May
June
July
August
September
October
November
December
Save Record


API Management
Welcome to apiman, open source API management. Use this software to provide
various APIs (Services) to your users (Applications) through a secure, scalable,
and governed Gateway layer. API Management allows Service Developers to centralize
control and analysis of their Services. It also provides a central location for
Application Developers to find and consume available APIs.
Organizations
All services and applications must be managed within the context of an
Organization. You can be a member of multiple Organizations at the same
time, with different roles in each: you can be an Application
Developer in one organization and a Service Developer in another.
Services
Create, find, or manage Services. A Service is also known as an API - anything
that can be invoked remotely by some sort of client (Application). This platform
simply provides a way to expose existing APIs by defining them as Services and
attaching value-added policies to them.
Applications
Create and manage your Applications. An Application is the thing that consumes
APIs (Services). These consumers must be defined in this platform so that
contracts can be created between them and the Services they wish to consume.
System Administration
Hey it looks like you're an administrator! Here are some things only you can do.
These are system-wide settings you're thinking about modifying, so please proceed
with caution.


A properly maintained Fire Extinguisher is your first line of defense against most common fires.
Licensed by the California State Fire Marshall for 34 years, Exxell Fire Systems has the experience to ensure that you have the proper types of Fire Extinguishers that are properly placed where you are protecting life and property.
California regulatory code Title 19 states that where Fire Extinguishers are required by law they are also required to be maintained and certified annually by a licensed company. We provide free estimates of any size or type.
With 34 years of experience in the Fire Protection industry, we know what your business needs to be totally prepared for the events of a fire.
Contact UsIf a fire extinguisher has been used or tampered with it must be recharged with new chemical so it can be used again. We refill it at your business.
Contact UsThe annual maintenance is vital for ensure your fire extinguisher is working when you need it to. Our technitians are the best in the industry!
 In the event of a fire, the main suppression system should be activated first and followed up with the K-Class extinguihser.
We also service restaurant fire suppression systems.The Class ABC fire extinguisher can be used on three different kinds of fires: Class A (ordinary combustibles such as wood or paper), Class B (flammable liquid fires such as grease or gasoline) or Class C (electrical fires).
BC Dry Chemical extinguishers are rated to be used on fires caused by Flammable Liquids, Electrical Rooms, and Pressurized Gases. BC Dry Chemical extinguishers are not recommended for the protection of computers and other sensitive electrical devices which can be damaged by the powder.
Halotron is a clean, non conductive gaseous agent that is an excellent replacement for Halon 1211 extinguishers. Halotron Extinguishers are ideal for fires near electronic data and equipment such as data centers, military electronics, laboratories, warehouses, manufacturing plants, general office areas, computer rooms, control rooms, vehicles, boats, and other areas with electronic equipment. We also service Halon 1211 Fire Extinguisher if already installed.
Carbon Dioxide (Co2) Fire Extinguishers are used for class B flammable liquids fires as well as Class C Electrical fires as they are electrically non-conductive. Carbon Dioxide is a clean, non-contaminating, odorless gas. Carbon Dioxide Fire Extinguishers meet many hospital medical equipment requirements. Co2 Extinguishers are also used for mechanics and factories as they leave no residue.
Suitable for use on metal fires. It incorporates a soft flow extension applicator that ensures the operator's hands are kept away from the extreme heat and prevents inhalation of the toxic fumes caused by the burning metal.


Title of a longer featured blog post
Multiple lines of text that form the lede, informing new readers quickly and efficiently about what’s most interesting in this post’s contents.
Multiple lines of text that form the lede, informing new readers quickly and efficiently about what’s most interesting in this post’s contents.
Some quick example text to build on the card title and make up the bulk of the card's content.
Read MoreSome quick example text to build on the card title and make up the bulk of the card's content.
Read MoreSome quick example text to build on the card title and make up the bulk of the card's content.
Read MoreThis is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer.
Continue readingThis is a wider card with supporting text below as a natural lead-in to additional content. This content is a little bit longer.
Continue reading


A cute rabbit eat eighty percent of their own droppings.
Rabbit habitats include meadows, woods, forests, grasslands, deserts and wetlands.Rabbits live in groups, and the best known species, the European rabbit, lives in underground burrows, or rabbit holes.


You run over and push the librarian down. Before you know it, hands grab you and drag you off them.
When you awaken, you are in some sort of dungeon chained to a stone wall. You stay there for what seems like weeks. All they give you for sustenance is moldy bread and dirty water. How long are they going to keep me here, you think.
  This is what I get for reading! You yell right before you sink into a pile on the floor against the wall and sulk.


Jane Galloway Heitz who starred in Glee and The Big Bang Theory has died
Jane Galloway Heitz, who starred in Glee and The Big Bang Theory, has died in the US of congestive heart failure.
The performer appeared in a number of other notable TV series including Shameless, Grey’s Anatomy, Prison Break and CSI.
The Sun reports that Galloway Heitz died from congestive heart failure at a hospital in Highland Park, Illinois, according to The Hollywood Reporter.
Her passing was first reported in an obituary released by the Chicago Tribune on Wednesday.
She was a widow, a mother of two and grandmother of three.
In The Big Bang Theory Galloway Heitz played the role of Mildred in 2009 and in Glee was Lillian Adler.
The character was the club director of the glee musical program at William McKinley High School.
She made appearances at the beginning and end of the show’s run from 2009 and 2015.
Despite only being physically onscreen in the show twice, a photograph of her was frequently shown in the TV series.
A plaque with it read: “By its very definition, Glee is about opening yourself up to joy.”
The touching words served as a source of inspiration for the character William Schuester, played by Matthew Morrison.
Her character was cited as the reason he decided to take over the glee club.
Her death is another heartbreak for the Glee cast who have had to deal with the passing of Cory Monteith (Finn Hudson) in 2013 and Mark Salling (Noah “Puck” Puckerman) in 2018.
TALENT SPOTTER TO STAR
Prior to her time in the limelight, Galloway Heitz operated her own casting business.
Later she transitioned into acting herself.
The Minneapolis actress first appeared in the 1993 short film Welcome to the Max, according to IMDB.
From there she made her film debut in David Lynch’s The Straight Story in 1999.
Other highlights of her film career included I Know Who Killed Me in 2007 and Just Visiting in 2001.
Galloway Heitz’s funeral is being held on November 30 in Illinois, according to her obituary.
Her family requested donations be made to the American Heart Association and American Diabetes Association instead of flowers.
This article originally appeared in The Sun and is republished here with permission


| Name |
Default |
Description |
| underlined: boolean |
true
|
Deprecated. If true, the text is underlined. |
| disabled: boolean |
false
|
If true, the link is disabled. |
| inheritColor: boolean |
false
|
If true, the color is inherited from parent. |
| text: string |
|
Link text. |
| iconSrc: string |
|
Deprecated. Source of the icon. |
| iconPosition: 'before' | 'after' |
'before'
|
Indicates the position of the icon in the component. |
| href: string |
|
Page to be opened when the user clicks on the link. |
| newWindow: boolean |
false
|
If true, the page is opened in a new browser tab. |
| tabIndexValue: number |
0 |
Value of the tabindex.
|
| margin: string | object |
false
|
Size of the margin to be applied to the component ('xxsmall' | 'xsmall' |
'small' | 'medium' | 'large' | 'xlarge' | 'xxlarge'). You can pass an
object with 'top', 'bottom', 'left' and 'right' properties in order to
specify different margin sizes.
|
| onClick: EventEmitter |
|
If defined, the link will be displayed as a button.
This function will be called when the user clicks the link.
|


array's random number functions allow arrays to be filled with random
numbers efficiently in a single call. Most of these functions use the
array_urand
uniform random object (of type urand), which is
accessible from TCL. The fillgrand()
function makes use of the
TCL accessible array_grand
object, which is
of type gaussrand.
Fill x with random numbers from the uniform distribution over
Fill x with random numbers from the Poisson distribution
Fill x with random numbers from the Gaussian distribution
Fill x with random integers from the range [0..max] such that no two integers are the same.


An existing python script, which named the same as the requesting url but with the 'py' extension, is implicitly executed before rendering views.
After that, the variables defined in the script can be replaced by using a '\$' prefix. Here goes:


Editing an Application File
You can edit the preferences file to change the settings listed in the following table. The preferences file is located in the dislite directory.
|
Preference |
Description |
Default Value |
|
*dislite.EnableIcon |
Displays icons representing entity types in the display panel when the value is set to 1. |
0 |
|
*dislite.EnableGroup |
Enables the Group utility in the Browser. Set the value to 0 to disable the Group utility. |
1 |
|
*dislite.EnableTransform |
Remaps the physical filenames of your source files and directories when the value is set to 1. |
0 |
|
*dislite.Tempdir |
Specify the path to the directory where you want Developer Xpress to store temporary session-based files. |
/usr/tmp |
|
*dislite.ModelSrcRoot |
Specify the top-level directory containing the model files for the service you plan to use. |
|
|
*dislite.SharedSrcRoot |
Specify the top-level directory containing your shared source code files. |
|
|
*dislite.PrivateSrcRoot |
Specify the top-level directory containing your private source code files. |
|


Loading...

Group by:
Severity
Type
Status
Assignee
Apply


Find your tames, view base stats and keep track of their food status. Get notified of pending imprints, the amount of fertilizer and gasoline remaining in your crops and generators. This and much more is available in your profile.
| Steam Name | Character Name | Tribe Name | Discord Tag | Server | Time Online |
|---|---|---|---|---|---|
| {{player.SteamName}} | {{player.CharacterName}} | {{player.TribeName}} | {{player.DiscordName}} | {{server.Key}} | {{player.TimeOnline}} |
| Address | {{server.Address}} |
|---|---|
| Version | {{server.Version}} |
| Player Slots | {{server.OnlinePlayerMax}} |
| Map | {{server.MapName}} |
| In-Game Day | {{server.InGameTime}} |
| Tamed Creatures | {{server.TamedCreatureCount | number}} |
| Cloud Creatures | {{server.CloudCreatureCount | number}} |
| Wild Creatures | {{server.WildCreatureCount | number}} |
| Structures | {{server.StructureCount | number}} |
| Players | {{server.PlayerCount | number}} |
| Tribes | {{server.TribeCount | number}} |
| Last Update | {{server.LastUpdate}} |
| Next Update | {{server.NextUpdate}} |
| Uptime | {{server.ServerStarted ? dataService.toRelativeDate(server.ServerStarted) : '-'}} |
| Steam Name | Character Name | Tribe Name | Discord Tag | Time Online |
|---|---|---|---|---|
| {{player.SteamName}} | {{player.CharacterName}} | {{player.TribeName}} | {{player.DiscordName}} | {{player.TimeOnline}} |


Ditransitive Clauses
Some verbs in some languages allow three core arguments. Clauses with three core arguments are called ditransitive or trivalent. They are often associated with verbs of giving and the semantic roles of actor (the one who gives), theme/patient (the thing that is given) and recipient/goal (the one who receives the given thing). Ditransitive clauses may also be used for concepts related to giving, for example teaching (which can be understood as giving knowledge).
All languages have means to express giving but not all languages have ditransitive clauses. In some languages, either recipient or the theme must be coded as an oblique argument, therefore the verb has only two core arguments and is (mono)transitive or bivalent. And then there are languages like English, where both options are available: I gave John a book is ditransitive, while I gave a book to John is monotransitive.
For more details on the distinction between core and oblique arguments, see Simple Verbal Clauses.
When a clause contains two non-subject core arguments, it is sometimes possible to say that one of them is “direct” and the other “indirect”; then the direct object will be labeled obj and the indirect iobj. Criteria for the distinction are language-specific. On the “coreness scale”, the direct object is considered more “core-like” than the indirect one, therefore one language-specific criterion might be that in the passive voice, the direct object is promoted as the new subject, while the indirect object does not change. Another possible criterion is that the role expressed by the indirect object can be alternatively encoded as an oblique argument, while such an option is not available for the direct object. The right to use the obj label is not bound to one of the two semantic roles; in some languages, the theme will be the direct object and the recipient will be indirect, but in other languages the opposite will hold, or none of the two objects will be clearly indirect.
If it cannot be established that one object is superior to the other, both will be labeled obj.
Coding Strategies
English
Some English verbs allow two objects (i.e., two core arguments following the verb):
- Peter gave Kate a book.
- Tom teaches me mathematics.
The traditional approach outside UD is to call the first object indirect and the second object direct; it is often defined in terms of semantic roles, saying that the recipient is the indirect object. UD avoids referring to semantic roles but it is not so easy to provide supporting evidence that is based on syntax. The passivization criterion actually slightly prefers the recipient to be considered direct. In the above examples, the recipient (Kate, me) is arguably more core than the theme (book, mathematics) because the recipient can be promoted in passivization more readily than the theme (promotion of the theme is not completely ungrammatical though; some speakers of some dialects of English accept it):
- Kate was given a book by Peter. (?A book was given Kate by Peter.)
- I am taught mathematics by Tom. (*Mathematics is taught me by Tom.)
The second object can be promoted more smoothly if both the subject and the first object are recoded as oblique arguments (in the case of to give) or the first object is removed (in the case of to teach):
- A book was given by Peter to Kate.
- Mathematics is taught by Tom. (*Mathematics is taught by Tom to me.)
On the other hand, the recipient can alternatively be expressed as an oblique argument, at least for the verb to give: Peter gave a book to Kate. For the theme, no alternative is available, it has to be encoded as a bare noun phrase (accusative in case of pronouns), which makes it closer to the patient in a primary transitive clause. The evidence thus seems to be conflicting and indecisive.   PUNCT _ _ 3 punct _ _
French
In contrast to English, French can form a ditransitive clause only if the recipient is realized as a pronominal clitic. If it is a full noun phrase, its coding will be always oblique (which means, in French as in English, that a preposition will be used):
- Pierre a donné un livre à Isabelle.
However, the third argument will be coded as core argument if it is a personal pronoun, thus forming a ditransitive clause:
- Pierre lui a donné un livre.
We have two different constructions depending on whether the recipient is a pronoun or a noun. This alone could be used as an argument for saying that lui is the indirect object (iobj) and un livre is the direct object (obj). Another argument is that only the direct object can be promoted to subject in a passive construction:
- Un livre lui a été donné. “A book was given to her.” (*Elle a été donnée un livre.)
Note that a nominative-accusative-dative construction can be used also in
situations where the dative argument is better described as beneficiary rather
than recipient. If the beneficiary is expressed as a dative pronoun (that is,
a core argument), it is still labeled iobj
:
- Il leur achète des livres.
Finally, it is possible that the dative pronoun (representing an oblique noun
phrase) occurs with a verb that takes just two core arguments, e.g., parler
“to speak”. The dative argument behaves here like an indirect object in a
ditransitive clause: it is not promoted to subject in passive constructions.
Therefore it is also labeled iobj
, although normally a monotransitive
clause would have a nsubj
and a direct obj
.
- Je lui parle. (Je parle à Pierre.) “I speak to him.
Spanish
In Spanish, like in French, a recipient realized as a noun must take a preposition (a) but it can be substituted by a dative pronoun (le, les, both genders), which appears without the preposition. However, the situation in Spanish is different in two aspects:
- Since the preposition a is also used to encode animate direct objects, one could argue that it is one of the core coding methods, and thus the recipient should not be considered oblique if it appears with this preposition.
- Clitic doubling – both the pronoun and the prepositional phrase can occur in the same clause.
In fact, the appearance of the preposition a in direct objects is rather exceptional both in Spanish and in the broader context of Romance languages. The preposition is not used with inanimate direct objects, and it is used frequently with various types of adjuncts. Therefore we do not infer that prepositional phrases denoting recipients are core arguments. We treat them as oblique arguments, as in French and other related languages. Also in parallel with these languages, we reserve the iobj label for the dative pronouns le, les.
TBD: Now we have a new problem with clitic doubling.
Previously, if there were both the pronoun and the a-phrase, we would make
the a-phrase iobj
and the pronoun expl. But now the pronoun is core
and the a-phrase is oblique. Shouldn’t then the pronoun have higher priority
and receive iobj
? If so, what should be the a-phrase then?
Dislocated
?
- Pedro dio un libro a Isabel. “Pedro gave Isabel a book.”
- Pedro le dio un libro a Isabel. “Pedro gave Isabel a book.”
- Pedro le dio un libro. “Pedro gave her a book.”
- Santiago me enseña las matemáticas. “Santiago teaches me mathematics.”

There is no doubt that the dative argument is the one that should be labeled as indirect. First, it is optional because it can be substituted by a prepositional phrase and the clause then becomes monotransitive. Second, if the clause is passivized, the direct object is promoted to the subject relation, while the indirect object stays untouched. Hence the indirect object is less core than the direct object.
- Un libro fue dado a Isabel por Pedro. “A book was given to Isabel by Pedro.”
- Un libro le fue dado por Pedro.  PUNCT _ _ 5 punct _ Gloss=.
Similarly to French, the dative pronoun can occur with verbs that only license
one argument, such as hablar “to speak”.
We could rule that the dative pronoun be labeled
iobj
even in these cases, as we did in French. However, the corresponding
noun phrase in French would be oblique. In Spanish, it is a normal direct
object (provided that it is animate) because the preposition a is allowed
with animate direct objects in Spanish:
- [fr] Je lui parle. (Je parle à Pierre.) “I speak to him. (I speak to Pierre.)”
- [es] Le hablo. (Hablo a Pedro.) “I speak to him. (I speak to Pedro.)”
Either this is fine with us, but then we perhaps also want to treat these datives as direct objects if they are pronouns or if the language is French. Or we say that if the a-phrase alternates with a dative pronoun, it is oblique. Or maybe we want to say that dative arguments are core arguments neither in Spanish, nor in French. This would also save us the necessity to explain why they are not core in German and Czech.
Czech
In Czech (as well as in other Slavic languages and also in German), the giving verb takes two arguments, one in the accusative (corresponding to the patient or theme), and one in the dative (corresponding to the recipient). Both are considered objects in the traditional grammar; however, since the dative is not a core case in these languages, it must be labeled obl or obl:arg, and the clause is not ditransitive.
(There are also three-argument verbs where none of the two non-subject arguments is accusative. For example, in Muž vyhrožoval sousedovi smrtí. “A man threatened his neighbor with death.” one of the arguments is dative and the other is instrumental. Neither dative nor instrumental is a core case, hence the clause is intransitive with two oblique arguments.)
There is no difference between nouns and pronouns (except for word order, which is restricted for pronouns that are clitics, but does not play a role in core argument coding).
- Petr dal Katce knihu. “Petr gave Katka a book.”
- Petr jí dal knihu.
The only Czech verb that is capable of forming ditransitive clauses under the UD definition is učit “to teach”, which takes two accusative objects.
- Tomáš mě učí matematiku. “Tomáš teaches me mathematics.”
One object represents the theme (mathematics) and the other the recipient (me). Either one can be omitted and then we have a normal transitive clause with an accusative object that can be promoted via passivization. However, if both arguments are present in the active clause, it is not possible to promote one of them and leave the other untouched; the grammar does not tolerate a bare accusative argument in a passive clause. Also note that there is a slightly archaic alternative where the theme (not the recipient!) takes the dative form. Here the passive might in theory be available but it still sounds clumsy.
- Tomáš učí matematiku. “Tomáš teaches mathematics.”
- Matematika je učena Tomášem. “Mathematics is taught by Tomáš.”
- Tomáš mě učí. “Tomáš teaches me.”
- (Já) jsem učen Tomášem. “I am taught by Tomáš.”
- Tomáš mě učí matematiku. “Tomáš teaches me mathematics.”
- (*Jsem učen matematiku Tomášem. *Matematika je učena mě Tomášem.)
- Tomáš mě učí matematice. “Tomáš teaches me mathematics.” (mathematics in dative)
- (?Jsem učen matematice (Tomášem).) “I am taught mathematics (by Tomáš).”
There thus does not seem to be any evidence that one of the accusatives is more core than the other. We have an example of a clause with two objects, neither of which is indirect.
- Tomáš mě učí matematiku.
Basque
See also: Fernando Zúñiga, Beatriz Fernández (draft 26.6.2014): Grammatical relations in Basque
There are verbs that take all three cases that count as core in Basque:
the ergative, the absolutive and the dative. In such constructions,
the ergative encodes the A function, absolutive the P function (also T function = theme-like),
and dative the G function (goal). In terms of dependency relations, it seems
reasonable to label the ergative as nsubj
, absolutive as obj
and dative
as iobj
just to distinguish them and to acknowledge that absolutives and
ergatives are more frequent than datives; though the grammar does not seem to
target the absolutive argument in specific rules, which would make it
more core-like than the dative.
- (Nik) (zuri) liburua eman dizut.
- Zezenak saihetsa pitzatu zidan.
Note that with some predicates the dative argument can be interpreted as having the beneficiary role. Some authors may argue that this role is already behind the dividing line between arguments and adjuncts, and if a nominal is an adjunct, it cannot be a core argument. However, in Basque the dative argument is cross-referenced by verbal inflection, hence it is clearly a core argument despite its semantic role.
Tagalog
In Tagalog, the verbs of giving form a standard transitive clause in the agent and patient voices, as the recipient is coded as a directional (locative) oblique dependent.
- Nagbigay ang lalaki ng libro sa babae.
However, locative dependents can be topicalized if the verb morphology signals the “locative voice”. Then the locative noun phrase switches to nominative, it becomes a core argument, while the original two core arguments keep core coding, too. Therefore we have a ditransitive clause with three core arguments, even for verbs that are not associated with ditransitives in other languages:
- Aalisan ng babae ng bigas ang sako para sa bata. “A/the woman will take some rice out of the sack for a/the child.” (locative voice)
# sent_id = 3.111c/tl
# text = Aalisan ng babae ng bigas ang sako para sa bata.
# gloss = FUT-take.out-DP ACT woman OBJ rice PIV sack BEN child
# text_en = A/the woman will take some rice out of the sack for a/the child.

Plains Cree
See also:
- Arok Elessar Wolvengrey (2011): Semantic and pragmatic functions in Plains Cree syntax (PhD thesis). Utrecht: LOT. ISBN 978-94-6093-051-5.
Plains Cree cross-references at most two core arguments on the verb. It also has a locative case affix that marks a noun phrase as oblique. If there is a verb which takes three arguments, the third argument is neither cross-referenced, nor marked by the locative case. It is therefore less core than the first two arguments, but more core than ordinary adjuncts. If we accept it as core, it will be labeled iobj, the least core-like argument.
Unlike in some European languages, in Plains Cree it is always the recipient-like argument that is more important and cross-referenced, while the theme stays outside. Hence the recipient (goal) is more core than the theme, and deserves to be labeled obj.
- Nikī-miyāw anima masinahikan. “I gave him/her that book.” (direct voice)
- Nikī-miyik anima masinahikan. “He/she gave me that book.” (inverse voice)
- Nikī-kiskinwahamawāw nēhiyawēwin. “I taught him/her Cree.” (direct voice)
- Nikī-kiskinwahamāk nēhiyawēwin.
In the above example, the verb stem used is for animate objects, while masinahikan “book” is inanimate. That is a proof that the 3rd person singular cross-reference on the verb does not refer to the book but to an animate recipient that is not overtly represented in the sentence.
Summary of Relations
The features discussed in this chapter are nsubj, obj, iobj (core arguments) and obl resp. obl:arg (oblique dependents).
- nsubj — nominal subject, typically the most “core-like” argument.
- obj — nominal object, the second most “core-like” argument. If the third argument shows fewer core properties,
then this is the direct object and the third argument is called indirect object and labeled
iobj
. If both objects are equal in “coreness status”, then both shall be labeledobj
. - iobj — nominal indirect object, the least “core-like” of the three arguments (only if it can be shown that it lacks some core properties that the other object has).
- obl — nominal oblique argument or adjunct.
If some of the
obl
subtypes are used in the language, then the bareobl
denotes the remaining situations not covered by the subtypes.- obl:arg — oblique argument (if the data provider decides to distinguish it from adjuncts)
There are other optional subtypes of these relations defined elsewhere in this documentation or in language-specific guidelines. If such subtypes exist, then quite naturally the label without subtype denotes only the remaining cases, not covered by subtypes.


bbclib.libs.bbclib_transaction module¶
Copyright (c) 2017 beyond-blockchain.org.
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
class
bbclib.libs.bbclib_transaction.
BBcTransaction
(version=1, unpack=None, id_length=None)[source]¶ Bases:
object
Transaction object
-
WITH_WIRE
= False¶
-
add_event
(asset_group_id, reference_indices=None, mandatory_approvers=None, option_approvers=None)[source]¶ Add BBcEvent object in this transaction (for allowing method chain style coding)
-
add_relation
(asset_group_id)[source]¶ Add BBcRelation object in this transaction (for allowing method chain style coding)
-
add_signature
(user_id, key_type=None, private_key=None, public_key=None, keypair=None, no_pubkey=False)[source]¶ Add BBcWitness and BBcSignature objects in this transaction (for allowing method chain style coding)
-
add_signature_object
(user_id=None, signature=None)[source]¶ Add signature in the reserved space
- Parameters
user_id (bytes) – user_id of the signature owner
signature (BBcSignature) – signature
- Returns
True if successful
- Return type
bool
-
create_cross_ref
(transaction_id, domain_id=None)[source]¶ Add BBcCrossRef object in this transaction (for allowing method chain style coding)
-
create_reference
(asset_group_id, ref_transaction=None, event_index_in_ref=0)[source]¶ Add BBcReference object in this transaction (for allowing method chain style coding)
-
digest
()[source]¶ Calculate the digest
The digest corresponds to the transaction_id of this object
- Returns
transaction_id (or digest)
- Return type
bytes
-
get_sig_index
(user_id)[source]¶ Reserve a space for signature for the specified user_id
- Parameters
user_id (bytes) – user_id whose signature will be added to the signature part
- Returns
position (index) in the signature part
- Return type
int
-
set_sig_index
(user_id, idx)[source]¶ Map a user_id with the index of signature list
- Parameters
user_id (bytes) – user_id whose signature will be added to the signature part
idx (int) – index number
-
sign
(key_type=2, private_key=None, public_key=None, keypair=None, no_pubkey=False)[source]¶ Sign the transaction
- Parameters
key_type (int) – Type of encryption key’s curve
private_key (bytes) –
public_key (bytes) –
keypair (KeyPair) – keypair or set of private_key and public_key needs to be given
no_pubkey (bool) – If True, public key is not contained in the BBcSignature object (needs to be given externally when verification)
- Returns
- Return type
-


ArchNadeom, Keeper Of Records.
Stardate #244.
The Book Of Secrets.
Machiel had been searching for it for years. Finally, here at last. In an unmarked tomb. Buried beneath the S.Q.U.I.D. empire. He had found it!
It spoke of battle. It promised of victory.
The secrets it held. The knowledge it could reveal. No enemy could withstand him. There was nothing he could not do with the book in his grasp.

He looked around the room one more time. The cold concrete walls. His Troopers standing at the entrance. The stone pedestal. The thick starlight pouring down through the ceiling. The Book Of Secrets bathed in light atop the slab.
He could feel the tension in the air. Himself holding his breath. The excitement. The suspense. Everything he had been pursuing, bringing him to stand here at this one moment in time.
Machiel reached out and dipped his fingers in the circle of light. It was like touching a waterfall. He turned his palm upward into the starlight, as it glimmered caressingly around his hand. Like jets of warm water. Splashing through his fingers and down his wrist.
It felt of pure energy. Joy. Laughter. Rejuvenation. He couldn’t help but smile.
It was an end to his many years of struggle and pursuit. This rich beautiful starlight running through his fingers. His trophy before him. The Book Of Secrets.
He would finally lay claim to the treasure for which he had been searching for so long. Machiel turned his hand over and touched its pages.
The circle was broken.
The starlight sucked up into the ceiling. Swallowing the room in darkness.
Down the hall, in the blacks of the shadows, there was a deep rumbling. A moist coolness oozed into the room from the passageway. Riding on the backs of the waves of a low billowing fog.
The Troopers backed away from the entrance with their blasters raised. Machiel stepped down from the pedestal, leaving the book behind, and drew his electro-sword. Slowly they converged together in the center of the room. Standing back-to-back. Huddling beneath what little light still came through the ceiling overhead.
Phosphorescent shapes began to move through the fog. Swimming around the edges. Splashing up and smearing down the walls. Leaving green streaks trailing behind them on the porous concrete.
Menacing, they slowly began circling. Easing towards the center of the room. Circling around Machiel and the Troopers. Weaving between their legs. Sliding up their knees. Finding the soft joints in their armor and oozing in cool fingers.
One of the Troopers panicked and started firing wildly at the floor and walls. The shots did nothing. It was all Machiel and the other Trooper could do to restrain him. A single bad ricochet in this confined space could kill any one of them.
Slowly, the fog and phantasms began pouring up the pedestal and into the book. Dark billows of fog and green phosphorescence oozing between the letters. Seeping into the pages. Staining its bamboo darkly like spilled watercolor.
When the last of the fog swept past them and into the book, the cover closed on its own.
The tomb became eerily silent. More frightening than anything they had just witnessed. They were afraid to move lest they disturb the peace of any more otherworldly beings.
 He looked down uncertainly at the book.
It would be a shame to not take it with them. After all the years of searching, despite what they had just seen. There must still be some good in its pages worth salvaging.
He reached out a hand, then paused. Frowning again uncertainly. Then he grabbed the book and picked it up off the pedestal.
The circular room was empty.
They walked back down the hallway. Empty. Into the three door room. The middle door still standing open. Just a barren alcove now. Empty. They stepped out onto the bridge. The fluorescent lights were off. The river had stopped running. No shapes swam in its currents. Empty.
As Machiel stepped on the foot of the stairs, he looked back into the tomb. So lifeless now. Whatever dark magic had existed here before, he feared they now carried out with them.
He was relieved to exit the archives and climb back onto his ship. He dropped the book on his console and sent his Troopers back to their posts.
“Sir, we’ve got an enemy ship inbound. leoliu86 of S.Q.U.I.D. WarFleet.”
“Release the docking lines and detach from the archives. Shields at full power. Turn the ship 135 degrees to port. Nose up 30 degrees from plane. Thrusters full ahead. Meet them head-on.”
Well that was quick.
With the S.Q.U.I.D. leaders retiring, the rest of the warfleet had disbanded. Seeking refuge among the other alliances. Or starting their own anew.
Wolfpack granted shelter to as many ships as its starports could accomodate. Offering them hospitality and a new place to call home.
They were the displaced refugees of a fractured empire. In a galaxy torn apart by war.
leoliu86 either refused to accept the disbandment of his fleet. (An alliance he had dedicated his life towards serving.)  Or was himself looting the coffers of the fallen empire.
Either way, he now engaged Machiel in battle.
“Ready the weapons for fire. Roborob, prepare boarding parties to target the enemy reactors. Fighter pilots, take out the enemy ACLs. Full power to lasers and missiles.”
Machiel opened The Book Of Secrets, “Let’s see what you have for me.”
A green heatless fire rose up from the pages. Swelling up Machiel’s arms and into the console.
Power surges started to sound alarms in the laser systems. Arcs of electricity and sparks began popping from the weapons casements. Rippling with a new unknown power they couldn’t quite contain.
“Open fire! Release that energy build-up before those lasers blow!”
His lasers hammered into leoliu86 with enough force to rock the ship. Green fire crackling around the edge of the beams. Punching clear holes in the enemy shields.
Machiel’s fighters responded immediately and peppered the ship with more gunfire to widen the breaches.
Strangely, Machiel’s missle bay 1 started firing EMPs at the enemy reactors.
“Missile Bay 1, retarget your EMPs on the enemy lasers. We are not clay pigeon shooting.”
Static. Nothing came back over the comms.
“Missile Bay 1, report.”
Static. Still nothing.
“Trooper, head to Missle Bay 1 and report back to me with their status.”
The battle was over in little more than a minute.
leoliu86’s shields were not built to withstand the massive amounts of energy surging from Machiel’s lasers. Once the reactors were distintegrated, his ship became nothing more than a powerless metal bucket floating through space.
“Uh, sir? I think you better get down here,” it was Trooper calling from Missile Bay 1.
The battle was a momentous victory, but how Missle Bay 1 had behaved was undismissable. Those EMPs would cost him an arm-and-a-leg to replace. Had it been a stronger enemy, their mistargetting could have cost him the battle. Machiel was not pleased.
He walked into Missle Bay 1, “Report.”
“Uh, sir. The missile controls would not respond to our commands. The comms went silent and we couldn’t open the doors. We lost control of the room. The missiles just began firing on their own.
“Sir, I hesitate to say this. It was like it had become…. possessed.”
The Book Of Secrets. Machiel remembered the green fire pouring forth from its pages. Up his arms. Into the console.
What had he brought onboard with them? What had he exposed to his ship and crew?


Class: ActiveRecord::Associations::AliasTracker
Do not use. This class is for internal use only.
| Relationships & Source Files | |
| Inherits: | Object |
| Defined in: | activerecord/lib/active_record/associations/alias_tracker.rb |
Overview
Keeps track of table aliases for JoinDependency
Class Method Summary
- .create(connection, initial_table, type_caster)
- .create_with_joins(connection, initial_table, joins, type_caster)
- .initial_count_for(connection, name, table_joins)
-
.new(connection, aliases, type_caster) ⇒ AliasTracker
constructor
table_joins is an array of arel joins which might conflict with the aliases we assign here.
Instance Attribute Summary
- #aliases readonly
Instance Method Summary
Constructor Details
.new(connection, aliases, type_caster) ⇒ AliasTracker
table_joins is an array of arel joins which might conflict with the aliases we assign here
56 57 58 59 60
# File 'activerecord/lib/active_record/associations/alias_tracker.rb', line 56
def initialize(connection, aliases, type_caster) @aliases = aliases @connection = connection @type_caster = type_caster end
Class Method Details
.create(connection, initial_table, type_caster)
[ GitHub ]9 10 11 12 13
# File 'activerecord/lib/active_record/associations/alias_tracker.rb', line 9
def self.create(connection, initial_table, type_caster) aliases = Hash.new(0) aliases[initial_table] = 1 new connection, aliases, type_caster end
.create_with_joins(connection, initial_table, joins, type_caster)
[ GitHub ]15 16 17 18 19 20 21 22 23 24 25
# File 'activerecord/lib/active_record/associations/alias_tracker.rb', line 15
def self.create_with_joins(connection, initial_table, joins, type_caster) if joins.empty? create(connection, initial_table, type_caster) else aliases = Hash.new { |h, k| h[k] = initial_count_for(connection, k, joins) } aliases[initial_table] = 1 new connection, aliases, type_caster end end
.initial_count_for(connection, name, table_joins)
[ GitHub ]27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
# File 'activerecord/lib/active_record/associations/alias_tracker.rb', line 27
def self.initial_count_for(connection, name, table_joins) # quoted_name should be downcased as some database adapters (Oracle) return quoted name in uppercase quoted_name = connection.quote_table_name(name).downcase counts = table_joins.map do |join| if join.is_a?(Arel::Nodes::StringJoin) # Table names + table aliases join.left.downcase.scan( /join(?:\s\w)?\s(\S\s+)?#{quoted_name}\son/ ).size elsif join.respond_to? :left join.left.table_name == name ? 1 : 0 else # this branch is reached by two tests: # # activerecord/test/cases/associations/cascaded_eager_loading_test.rb:37 # with :posts # # activerecord/test/cases/associations/eager_test.rb:1133 # with :comments # 0 end end counts.sum end
Instance Attribute Details
#aliases (readonly)
[ GitHub ]7
# File 'activerecord/lib/active_record/associations/alias_tracker.rb', line 7
attr_reader :aliases
Instance Method Details
#aliased_table_for(table_name, aliased_name)
[ GitHub ]62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81
# File 'activerecord/lib/active_record/associations/alias_tracker.rb', line 62
def aliased_table_for(table_name, aliased_name) if aliases[table_name].zero? # If it's zero, we can have our table_name aliases[table_name] = 1 Arel::Table.new(table_name, type_caster: @type_caster) else # Otherwise, we need to use an alias aliased_name = @connection.table_alias_for(aliased_name) # Update the count aliases[aliased_name] += 1 table_alias = if aliases[aliased_name] > 1 "#{truncate(aliased_name)}_#{aliases[aliased_name]}" else aliased_name end Arel::Table.new(table_name, type_caster: @type_caster).alias(table_alias) end end
#truncate(name) (private)
[ GitHub ]85 86 87
# File 'activerecord/lib/active_record/associations/alias_tracker.rb', line 85
def truncate(name) name.slice(0, @connection.table_alias_length - 2) end


{% extends "base.html" %} {% load jsonify %} {% load el_pagination_tags %} {% block end-head %} {% endblock %} {% block ogtitle %}{% block title %}{{ event.name }} event{% endblock %}{% endblock %} {% block description %}Find detailed information about the {{ event.name }} event including rules, participants, stages, and schedule. Equip yourself with all you need to know to successfully navigate this programming competition.{% endblock %} {% block content %}
Wait for your confirmation in {{ team.name }} team by {{ team.author.first_name }} {{ team.author.last_name }}
Please submit a repeat request after {{ join_request.repeat_request_timedelta|hr_timedelta }} or you can cancel request
{% endwith %}


"EARING "an Old English word (from the Latin aro, I plough), meaning“ploughing.” It is used in the Authorized Version in Genesis 45:6; Exodus 34:21; 1 Samuel 8:12; Deuteronomy 21:4; Isaiah 30:24; but the Revised Version has rendered the original in these places by the ordinary word to plough or till.
"EARING "an Old English word (from the Latin aro, I plough), meaning“ploughing.” It is used in the Authorized Version in Genesis 45:6; Exodus 34:21; 1 Samuel 8:12; Deuteronomy 21:4; Isaiah 30:24; but the Revised Version has rendered the original in these places by the ordinary word to plough or till.


This example is a quick exercise to illustrate how the default, static navbar and fixed to top navbar work. It includes the responsive CSS and HTML, so it also adapts to your viewport and device.
General Guidelines
Do not overload system by doing agressive submissions


AI Projects
Team
Events
contact
×
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
★
Welcome to Movie Recommender
We keep track of the movies you watch and recommend new ones specifically for your taste! To begin, please find some movies using the search bar below and rate them so we know what you like!
MyMovies
Movie Name
MyRating
X
Get Recommendations
AI Projects
Team
Events
contact


| kubeVersion | |
|---|---|
| appVersion | 1.1.1 |
| description | A Library Helm Chart for grouping common logic between bitnami charts. This chart is not deployable by itself. |
| Maintainers |
|
|---|---|
| Sources | |
| Keywords | common helper template function bitnami |
| Param | Default Value | Description |
|---|---|---|
| exampleValue | common-chart | bitnami/common It is required by CI/CD tools and processes. |
## bitnami/common
## It is required by CI/CD tools and processes.
exampleValue: common-chart


Before Change
with ag.record():
outputs = [net(X) for X in data]
loss = [L(yhat, y) for yhat, y in zip(outputs, label_smooth)]
for l in loss:
l.backward()
trainer.step(batch_size)
acc_top1.update(label, outputs)
acc_top5.update(label, outputs)
train_loss += sum([l.sum().asscalar() for l in loss])
After Change
with ag.record():
outputs = [net(X) for X in data]
loss = [L(yhat, y) for yhat, y in zip(outputs, label_smooth)]
ag.backward(loss)
trainer.step(batch_size)
acc_top1.update(label, outputs)
acc_top5.update(label, outputs)
train_loss += sum([l.sum().asscalar() for l in loss])


Coronavirus (COVID-19) content toolkit
How to write about people at higher risk
{% markdown %}
[NHS content on people at higher risk from coronavirus](https://www.nhs.uk/conditions/coronavirus-covid-19/people-at-higher-risk-from-coronavirus/whos-at-higher-risk-from-coronavirus/) last updated: **27 May 2020**.
{% endmarkdown %}
## NHS content on people at higher risk from coronavirus
We have different types of content about people who are at a higher risk of getting seriously ill from coronavirus (COVID-19).
### People at high risk (clinically extremely vulnerable):
{% markdown %}
People at high risk from coronavirus include people who:
- have had an organ transplant
- are having chemotherapy or antibody treatment for cancer, including immunotherapy
- are having an intense course of radiotherapy (radical radiotherapy) for lung cancer
- are having targeted cancer treatments that can affect the immune system (such as protein kinase inhibitors or PARP inhibitors)
- have blood or bone marrow cancer (such as leukaemia, lymphoma or myeloma)
- have had a bone marrow or stem cell transplant in the past 6 months, or are still taking immunosuppressant medicine
- have been told by a doctor they you have a severe lung condition (such as cystic fibrosis, severe asthma or severe COPD)
- have a condition that means they have a very high risk of getting infections (such as SCID or sickle cell)
- are taking medicine that makes them much more likely to get infections (such as high doses of steroids or immunosuppressant medicine)
- have a serious heart condition and are pregnant
{% endmarkdown %}
This content is a summary of the main groups considered to be at high risk of becoming seriously ill from coronavirus – also known as clinically extremely vulnerable.
People in this group are advised to stay at home at all times (called shielding).
{% include('./includes/how-to-use.html') %}
### People at moderate risk (clinically vulnerable):
{% markdown %}
People at moderate risk from coronavirus include people who:
- are 70 or older
- are pregnant
- have a lung condition that's not severe (such as asthma, COPD, emphysema or bronchitis)
- have heart disease (such as heart failure)
- have diabetes
- have chronic kidney disease
- have liver disease (such as hepatitis)
- have a condition affecting the brain or nerves (such as Parkinson's disease, motor neurone disease, multiple sclerosis or cerebral palsy)
- have a condition that means they have a high risk of getting infections
- are taking medicine that can affect the immune system (such as low doses of steroids)
- are very obese (a BMI of 40 or above)
{% endmarkdown %}
This content is a summary of the main groups considered to be at moderate risk of becoming seriously ill from coronavirus – also known as clinically vulnerable.
People in this group are advised to take extra care to follow the advice on social distancing.
{% include('./includes/how-to-use.html') %}
### Voice-friendly version:
{% markdown %}
**Who is at higher risk from coronavirus?**
Coronavirus can make anyone seriously ill. But some people are at higher risk. There are two levels of higher risk: moderate risk and high risk. People at moderate risk – also called clinically vulnerable – include anyone who is over 70 or pregnant. People at high risk – also called clinically extremely vulnerable – include people who’ve had an organ transplant or are having some types of cancer treatment.
{% endmarkdown %}
This content is suited for voice assistants and chatbots. It provides a summary of the information in a voice-friendly structure – for example, by avoiding bullet points.
{% include('./includes/how-to-use.html') %}
### Full version:
{% markdown %}
See our full page on the NHS website about [who’s at higher risk from coronavirus](https://www.nhs.uk/conditions/coronavirus-covid-19/people-at-higher-risk-from-coronavirus/whos-at-higher-risk-from-coronavirus/).
{% endmarkdown %}
This content is best if you have space for a full web page of content and want your users to know all the information and advice on people at higher risk from coronavirus.
{% include('./includes/how-to-use.html') %}
## Where our content comes from
Our content on people at higher risk from coronavirus is based on official guidance from Public Health England (PHE), the office of the UK Chief Medical Officers (CMOs) and NHS Digital.
The content has been adapted and simplified by our content team and checked by the clinical team at NHS Digital.
Original guidance:
- [GOV.UK: Guidance on shielding and protecting people who are clinically extremely vulnerable from COVID-19](https://www.gov.uk/government/publications/guidance-on-shielding-and-protecting-extremely-vulnerable-persons-from-covid-19/guidance-on-shielding-and-protecting-extremely-vulnerable-persons-from-covid-19) (last updated 18 May 2020)
- [NHS Digital: Shielded patients list](https://digital.nhs.uk/coronavirus/shielded-patient-list) (last update 21 May 2020)
## How to write for NHS services
For general information and advice about how to write content for digital NHS services, see the [NHS digital service manual content style guide](https://service-manual.nhs.uk/content).
{% endmarkdown %}


{% extends 'layouts/main.html' %} {% block title %}About{% endblock %} {% block content %}
A backend to power the future of PMA2020 data infrastructure.
The PMA2020 API is built to power public facing and internal applications, as well as various aspects of IT and data infrastructure.
With it, we hope to achieve new frontiers in data analysis, visualization, and dissemination in family planning data, to build a better tomorrow for our children and the world.
{% endblock %}


我目前是新加坡管理大学系统分析与验证小组(SAV)的博士后，现阶段的研究方向是软件工程以及人工智能测试与验证。
| 就读时间 | 学校 | 学院 | 专业 | 导师 | 学位 |
|---|---|---|---|---|---|
| 2016.09-2022.03 | 浙江大学 | 计算机科学与技术 | 计算机科学 | 王新宇教授 | 博士 |
| 2012.09-2016.06 | 浙江大学 | 计算机科学与技术 | 软件工程 | 王新宇教授 | 学士 |
新加坡管理大学系统分析与验证小组，2022.09-，人工智能测试与验证方向
论文发表：“QuoTe: Quality-oriented Testing for Deep Learning Systems”, Jialuo Chen, Jingyi Wang, Xingjun Ma, Youcheng Sun, Jun Sun, Peixin Zhang, and Peng Cheng, ACM Transactions on Software Engineering and Methodology (TOSEM), 2023
浙江大学智能计算与软件中心(ICSOFT)，2018.03-2022.06，人工智能测试与验证方向
合作方：华为，新加坡科技设计大学，新加坡管理大学，新加坡国立大学
项目：基于深度学习的程序文档自动化生成技术研究（国家自然科学基金面上项目）
研究内容：模型鲁棒性（攻击与防御），模型公平性，模型测试
开源项目：GuardAI, FairAI
论文发表：“Automatic Fairness Testing of Neural Classifiers through Adversarial Sampling”, Peixin Zhang, Jingyi Wang, Jun Sun, Xinyu Wang, Guoliang Dong, Xingen Wang, Ting Dai, and Jinsong Dong, IEEE Transactions on Software Engineering (TSE), 2021
“White-box Fairness Testing through Adversarial Sampling”, Peixin Zhang, Jingyi Wang, Jun Sun, Guoliang Dong, Xinyu Wang, Xingen Wang, Jinsong Dong, and Ting Dai, Proceedings of the 42nd International Conference on Software Engineering (ICSE), Seoul, Republic of Korea, 2020 (国际计算机协会软件工程专业杰出论文奖, ACM SIGSOFT Research Highlight)
“Adversarial Sample Detection for Deep Neural Network through Model Mutation Testing”, Jingyi Wang, Guoliang Dong, Jun Sun, Xinyu Wang, and Peixin Zhang, Proceedings of the 41st International Conference on Software Engineering (ICSE), Montreal, Canada, 2019
其它论文：“Detecting Adversarial Samples of Deep Neural Networks through Mutation Testing”, Jingyi Wang, Peixin Zhang, Pengfei Yang, Jun Sun, Dongxia Wang, and Xinyu Wang
新加坡管理大学系统分析与验证小组，2019.09-2020.09，人工智能测试与验证方向
项目：Fuzzing AI-Systems for Adversarial Sample Generation and Mitigation（华为）
Testing and Defending AI-Systems Holistically（华为）
Explaining AI with the Right Level of Abstraction（AISG）
论文发表：“An Empirical Study on Correlation between Coverage and Robustness for Deep Neural Networks”, Yizhen Dong, Peixin Zhang, Jingyi Wang, Shuang Liu, Jun Sun, Jianye Hao, Xinyu Wang, Li Wang, Jin Song Dong, and Dai Ting, 25th International Conference on Engineering of Complex Computer Systems (ICECCS), Singapore, 2020
新加坡科技设计大学系统分析与验证小组，2017.07-2017.10，软件测试方向
研究内容：动态符号执行测试，符号执行测试，机器学习生成测试用例等
开源项目：Ziyuan
论文发表：“Towards Optimal Concolic Testing”, Xinyu Wang, Jun Sun, Zhenbang Chen, Peixin Zhang, Jingyi Wang, and Yun Lin, Proceedings of the 40th International Conference on Software Engineering (ICSE), Gothenburg, Sweden, 2018 (国际计算机协会软件工程专业杰出论文奖)
浙江邦盛科技有限公司，2016.02-2016.09，算法工程师
机器学习算法库：代码结构设计与重构，算法开发，性能调优，模型功能开发等
模型训练管理平台：功能测试（JIRA）；撰写需求文档、操作手册、软件著作权、专利申请书等
数据分析：携程、易宝、苏宁
调研：征信行业，神经网络开源项目
浙江邦盛科技有限公司，2015.08-2015.10，软件工程师
网络爬虫
数据清洗与分析
| 获奖时间 | 奖项 |
|---|---|
| 2023.03 | 浙江大学优秀博士学位论文 |
| 2021.03 | ACM SIGSOFT Research Highlight |
| 2020.11 | 浙江大学三好研究生 |
| 2020.11 | 浙江大学优秀研究生 |
| 2020.07 | 国际计算机协会软件工程专业杰出论文(ACM SIGSOFT Distinguished Paper) |
| 2019.09 | 华为技术合作优秀奖 |
| 2018.12 | 浙江大学三好研究生 |
| 2018.12 | 浙江大学优秀研究生 |
| 2018.11 | 硕士研究生国家奖学金 |
| 2018.09 | 浙江大学优秀团员 |
| 2018.06 | 国际计算机协会软件工程专业杰出论文(ACM SIGSOFT Distinguished Paper) |
| 2016.06 | 浙江大学卓越工程师奖学金 |
| 2016.06 | 浙江大学计算机科学与技术学院三等实习奖学金 |
| 2016.05 | 浙江大学外汇交易大赛第一名 |
| 2015.09 | 浙江大学二等学业奖学金 |
| 2015.07 | 中国外汇交易中心一等奖学金 |
| 2013.12 | 浙江省大学生物理创新竞赛三等奖 |
计算机：擅长JAVA与PYTHON，熟悉tensorfow，了解C/C++、JSP、HTML，了解操作系统原理、网络，有使用MagicDraw、Git、MySQL以及Office等工具的经历
英语：雅思 6.5
其它：中国证券业协会证券从业资格(证券市场基础知识，证券交易，证券投资基金，证券投资分析)
第26届IEEE软件分析、演化与再工程国际会议，2018.09-2019.02，组织委员会成员
搭建官方网站
协助参会人员注册
撰写开闭幕及颁奖演示文稿
志愿者
乐清市“梦想导师计划”志愿者活动，2015.02-2015.08，联合发起人
关注在乐务工人员子女的心理健康发展
为乐籍大学生回报家乡社会搭桥牵线
与乐清市教育局、城南二小、乐清市志愿者协会、乐清市青少年宫进行深度合作
共有8批100余学生参与活动
浙江大学寒假返乡社会实践团，2014.01-2014.02，副团长
对温州市柳市镇电器行业发展现状进行实地调研，并撰写研究报告
与多家500强企业的高级管理人员进行面对面的交流讨论
调研内容涵盖电子商务、物联网以及企业管理等多个领域
浙江大学篮球联盟，2013.09-2014.06，副社长
协会日常管理工作，负责定期组织会员球赛
组织了2013年“新生杯”篮球赛，全校最有影响力的体育赛事之一，负责赛事裁判的管理
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I am a Research Scientist working in the System Analysis and Verification Group (SAV) of Singapore Management University, my recent research areas are software engineering and AI Testing & Verification.
| Period | School | College | Major | Supervisor | Degree |
|---|---|---|---|---|---|
| 2016.09-2022.03 | Zhejiang University | Computer Science and Technology | Computer Science | Prof. Wang Xinyu | Doctor |
| 2012.09-2016.06 | Zhejiang University | Computer Science and Technology | Software Engineering | Prof. Wang Xinyu | Bachelor |
System Analysis and Verification Group (SAV), Singapore Management University，2022.09-，AI Testing & Verification
Publication: “QuoTe: Quality-oriented Testing for Deep Learning Systems”, Jialuo Chen, Jingyi Wang, Xingjun Ma, Youcheng Sun, Jun Sun, Peixin Zhang, and Peng Cheng, ACM Transactions on Software Engineering and Methodology (TOSEM), 2023
Intelligent Computing and Software Center (ICSOFT), Zhejiang University，2018.03-2022.06，AI Testing & Verification
Partners: Huawei, Singapore University of Technology and Design, Singapore Management University, National University of Singapore
Project: Research on Automatic Generation of Program Documents based on Deep Learning (NSFC)
Research Contents: Robustness of model(attack and defense); Fairness of model; Testing for model
Open Source Project: GuardAI, FairAI
Publication: “Automatic Fairness Testing of Neural Classifiers through Adversarial Sampling”, Peixin Zhang, Jingyi Wang, Jun Sun, Xinyu Wang, Guoliang Dong, Xingen Wang, Ting Dai, and Jinsong Dong, IEEE Transactions on Software Engineering (TSE), 2021
“White-box Fairness Testing through Adversarial Sampling”, Peixin Zhang, Jingyi Wang, Jun Sun, Guoliang Dong, Xinyu Wang, Xingen Wang, Jinsong Dong, and Ting Dai, Proceedings of the 42nd International Conference on Software Engineering (ICSE), Seoul, Republic of Korea, 2020 (ACM SIGSOFT Distinguished Paper, ACM SIGSOFT Research Highlight)
“Adversarial Sample Detection for Deep Neural Network through Model Mutation Testing”, Jingyi Wang, Guoliang Dong, Jun Sun, Xinyu Wang, and Peixin Zhang, Proceedings of the 41st International Conference on Software Engineering (ICSE), Montreal, Canada, 2019
Other Paper: “Detecting Adversarial Samples of Deep Neural Networks through Mutation Testing”, Jingyi Wang, Peixin Zhang, Pengfei Yang, Jun Sun, Dongxia Wang, and Xinyu Wang
System Analysis and Verification Group (SAV), Singapore Management University，2019.09-2020.09，AI Testing & Verification
Project: Fuzzing AI-Systems for Adversarial Sample Generation and Mitigation（Huawei）
Testing and Defending AI-Systems Holistically（Huawei）
Explaining AI with the Right Level of Abstraction（AISG）
Publication: “An Empirical Study on Correlation between Coverage and Robustness for Deep Neural Networks”, Yizhen Dong, Peixin Zhang, Jingyi Wang, Shuang Liu, Jun Sun, Jianye Hao, Xinyu Wang, Li Wang, Jin Song Dong, and Dai Ting, 25th International Conference on Engineering of Complex Computer Systems (ICECCS), Singapore, 2020
System Analysis and Verification Group, Singapore University of Technology and Design，2017.07-2017.10，Testing
Research Contents: Concolic testing; Symbolic execution; Generate test case by deep neural network
Open Source Project: Ziyuan
Publication: “Towards Optimal Concolic Testing”, Xinyu Wang, Jun Sun, Zhenbang Chen, Peixin Zhang, Jingyi Wang, and Yun Lin, Proceedings of the 40th International Conference on Software Engineering (ICSE), Gothenburg, Sweden, 2018 (ACM SIGSOFT Distinguished Paper)
Zhejiang Bangsun Technology Ltd.，2016.02-2016.09，Algorithm Engineer
Machine Learning Algorithm Library: Design the code structure and integrate the code, algorithm development, performance tuning, Model’s function development，etc
Management platform: Requirement document, operation manual, software copyright, patent application, etc; Testing
Data Analysis: Ctrip, Yeepay, Suning, etc
Survey: Credit checking industry, neural network open source project
Zhejiang Bangsun Technology Ltd.，2015.08-2015.10，Software Engineer
Web Crawler
Data Cleaning and Analysis
| Time | Honor |
|---|---|
| 2023.03 | Excellent Doctoral Dissertation of Zhejiang University |
| 2021.03 | ACM SIGSOFT Research Highlight |
| 2020.11 | Graduate of Merit/Triple A Graduate of Zhejiang University |
| 2020.11 | Award of Honor for Graduate of Zhejiang University |
| 2020.07 | ACM SIGSOFT Distinguished Paper |
| 2019.09 | Huawei Technology Cooperation Excellence Award |
| 2018.12 | Graduate of Merit/Triple A Graduate of Zhejiang University |
| 2018.12 | Award of Honor for Graduate of Zhejiang University |
| 2018.11 | Master’s National Scholarship |
| 2018.09 | Excellent League Member of Zhejiang University |
| 2018.06 | ACM SIGSOFT Distinguished Paper |
| 2016.06 | Excellent Engineer Scholarship of Zhejiang University |
| 2016.06 | Third Internship Scholarship of College of Computer Science and Technology |
| 2016.05 | First Place of Zhejiang University Foreign Exchange Competition |
| 2015.09 | Second Study Scholarship of Zhejiang University |
| 2015.07 | China Foreign Exchange Trade System First Scholarship |
| 2013.12 | Third Prize of Physics Innovation Competition in Zhejiang |
Computer: Good at JAVA and PYTHON, familiar with tensorfow, know C/C++, JSP and HTML, know OS and network, experience with tools such as MagicDraw, Git, MySQL and Office
English: IELTS 6.5
Others: Securities qualification of the Securities Association of China
The 26th IEEE International Conference on Software Analysis, Evolution and Reengineering(SANER 2019), 2018.09-2019.02, Local Committee Member
Official website construction
Assist participants in registration
Slides for opening, closing and awarding ceremony
Volunteer
“Dream Mentor Program” Volunteering Activities in City Yueqing，2015.02-2015.08，Co-Sponsors
Focus on the mental health development of the workers’ children
Help undergraduate born in Yueqing to repay their hometown
Build deep cooperation with government, schools and volunteer association
A total of 8 batches and more than 100 students participated in the activity
Winter Social Practice Group of Zhejiang University，2014.01-2014.02，Deputy Chief
Field research on the development of electrical industry in Liushi, Wenzhou, write research reports
Discuss face-to-face with senior managers of several top 500 companies
Research focus on e-commerce, internet of things and enterprise management
Basketball Association of Zhejiang University, 2013.09-2014.06, Deputy Head
Daily management of the association and organizing regular games
Organizing the “2013 Freshman Cup” basketball match, responsible for the management of referees
Email1<EMAIL_ADDRESS>Email2<EMAIL_ADDRESS>Email3: pxzhang94@qq.com


On Fifthweek you subscribe to individual creators, and each creator is free to set their own weekly subscription price.
We have no minimum subscription price, allowing everyone to find an appropriate value for their particular content.
We have no setup fees and no monthly fees, so you can get started right away for free.
Once you have paying subscribers you get 80% of your revenue, and we use the remainder to cover transaction costs, currency conversion fees and our running costs.
All fees are covered by us.
Creators own their own content.
We handle that for you.
We currently support PayPal for paying out, with Payoneer coming soon.


Surface topography calculations of Dirichlet's normal energy, relief index, surface slope, and orientation patch count for teeth using scans of enamel caps. Importantly, for the relief index and orientation patch count calculations to work, the scanned tooth files must be oriented with the occlusal plane parallel to the x and y axes, and perpendicular to the z axis. The files should also be simplified, and smoothed in some other software prior to uploading into R.
| Version: | 4.4 |
| Depends: | R (≥ 2.10), alphahull, rgl, Rvcg |
| Suggests: | knitr, rmarkdown, rglwidget |
| Published: | 2018-09-18 |
| Author: | James D. Pampush [aut, cre, cph], Julia M. Winchester [aut, cph], Paul E. Morse [aut, cph], Alexander Q. Vining [aut, cph] |
| Maintainer: | James D. Pampush <jdpampush at gmail.com> |
| License: | ACM |
| NeedsCompilation: | no |
| CRAN checks: | molaR results |
| Reference manual: | molaR.pdf |
| Vignettes: |
Using molaR |
| Package source: | molaR_4.4.tar.gz |
| Windows binaries: | r-devel: molaR_4.4.zip, r-release: molaR_4.4.zip, r-oldrel: molaR_4.4.zip |
| OS X binaries: | r-release: molaR_4.4.tgz, r-oldrel: molaR_4.4.tgz |
| Old sources: | molaR archive |
Please use the canonical form https://CRAN.R-project.org/package=molaR to link to this page.


|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |
| Packages that use Months | |
|---|---|
| org.joda.time | Provides support for dates, times, time zones, durations, intervals, and partials. |
| Uses of Months in org.joda.time |
|---|
| Fields in org.joda.time declared as Months | |
|---|---|
static Months |
Months.EIGHT
Constant representing eight months. |
static Months |
Months.ELEVEN
Constant representing eleven months. |
static Months |
Months.FIVE
Constant representing five months. |
static Months |
Months.FOUR
Constant representing four months. |
static Months |
Months.MAX_VALUE
Constant representing the maximum number of months that can be stored in this object. |
static Months |
Months.MIN_VALUE
Constant representing the minimum number of months that can be stored in this object. |
static Months |
Months.NINE
Constant representing nine months. |
static Months |
Months.ONE
Constant representing one month. |
static Months |
Months.SEVEN
Constant representing seven months. |
static Months |
Months.SIX
Constant representing six months. |
static Months |
Months.TEN
Constant representing ten months. |
static Months |
Months.THREE
Constant representing three months. |
static Months |
Months.TWELVE
Constant representing twelve months. |
static Months |
Months.TWO
Constant representing two months. |
static Months |
Months.ZERO
Constant representing zero months. |
| Methods in org.joda.time that return Months | |
|---|---|
Months |
Months.dividedBy(int divisor)
Returns a new instance with the months divided by the specified divisor. |
Months |
Months.minus(int months)
Returns a new instance with the specified number of months taken away. |
Months |
Months.minus(Months months)
Returns a new instance with the specified number of months taken away. |
static Months |
Months.months(int months)
Obtains an instance of Months that may be cached. |
static Months |
Months.monthsBetween(ReadableInstant start,
ReadableInstant end)
Creates a Months representing the number of whole months
between the two specified datetimes. |
static Months |
Months.monthsBetween(ReadablePartial start,
ReadablePartial end)
Creates a Months representing the number of whole months
between the two specified partial datetimes. |
static Months |
Months.monthsIn(ReadableInterval interval)
Creates a Months representing the number of whole months
in the specified interval. |
Months |
Months.multipliedBy(int scalar)
Returns a new instance with the months multiplied by the specified scalar. |
Months |
Months.negated()
Returns a new instance with the months value negated. |
static Months |
Months.parseMonths(String periodStr)
Creates a new Months by parsing a string in the ISO8601 format 'PnM'. |
Months |
Months.plus(int months)
Returns a new instance with the specified number of months added. |
Months |
Months.plus(Months months)
Returns a new instance with the specified number of months added. |
| Methods in org.joda.time with parameters of type Months | |
|---|---|
boolean |
Months.isGreaterThan(Months other)
Is this months instance greater than the specified number of months. |
boolean |
Months.isLessThan(Months other)
Is this months instance less than the specified number of months. |
Months |
Months.minus(Months months)
Returns a new instance with the specified number of months taken away. |
Months |
Months.plus(Months months)
Returns a new instance with the specified number of months added. |
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |