The paper, Neural Responding Machine for Short-Text Conversation, published by L Shang et. al. in 2015, introduces Neural Responding Machine (NRM), a neural network-based response generator for short-text conversation. The NRM takes the general encoder-decoder framework, which formalizes the generation of response as a decoding process based on the latent representation of the input text, while both encoding and decoding are realized with recurrent neural networks (RNN). In this paper, the author demonstrates that the proposed encoder-decoder-based neural network overperform the traditional Retrivial-based methods and Statistical Machine Translation (SMT) based methods.
Dataset for Short-Text Conversation
The author prepares around 4.4 million pairs of conversations from Weibo to train the model. And the dataset is derived from hundreds of millions of post-response pairs by cleaning this raw data including:
- removing trivial responses like “wow”
- filtering out potential advertisements
- removing the response after first 30 ones for topic consistency.
Below is some statistics of the dataset used:
Neural Responding Machines
The neural responding machine generally contains three parts, encoder, context generator and decoder, as shown in the graph below. Here, both encoder and decoder are Recurrent Neural Networks, beasue of its natural ability to summarize and generate word sequence of arbitrary lengths. where $\mathbf{x}=(x_{1},\dots,x_{T})$ is the input sequence ($x_{i}$ denotes the $i$-th word), $\mathbf{h}=(h_{1},\dots,h_{T})$ is a set of high-dimensional hidden representations, $\alpha_{t}$ is the attention signal at time $t$, while $c_{t}$ is the context at time $t$, $y_{t}$ is the generated $t$-th word of response. And the general process is:
- The encoder converts the input sequence $\mathbf{x}$ into the hidden representations $\mathbf{h}$;
- $\mathbf{h}$, along with attention signal $\alpha_{t}$, are fed to the context-generator to build the context $c_{t}$ input to decoder at time $t$.
- The $c_{t}$ is linearly transformed by the transformation matrix $\mathbf{L}$ into a stimulus of generating RNN to produce the $t$-th word $y_{t}$ of response.
Here $\mathbf{L}$ performs the role to transform the representation of post (or some part of it) to the rich representation of many plausible responses, while $\alpha_{t}$ is to determine which part of the hidden representation $\mathbf{h}$ should be emphasized during the generation process, normally, $\alpha_{t}$ is function of historically generated subsequence $(y_{1},\dots,y_{t-1})$, $\mathbf{x}$ or their latent representations.
Encoder and Context Generator
The author introduces three types of encoding schemes: global scheme, local scheme and hybrid scheme (combination of global and local schemes). And the context generator of each scheme is different.
Global Scheme
Graph below visualizes the global scheme of the RNN-encoder and related context generator. The hidden state at time $t$ is computed by $h_{t}=\mathcal{f}(x_{t},h_{t-1})$, while the context generator simply uses the last hidden state as the context vector, i.e, $c_{t}=h_{T}$, it means that final hidden state $h_{T}$ is used as the global representation of the sentence. However, this scheme has drawbacks that a vectorial summarization of the entire post is often hard to obtain and may lose important details for response generation, especially when the dimension of the hidden state is not big enough. It is worth to mentione that $\mathcal{f}(\centerdot)$ can be a logistic function, sophisticated Long Short-Term Memory (LSTM) unit, or Gated Recurrent Unit (GRU). Compared to “Ungated” or vanilla logistic function, LSTM and GRU are specially designed for its long term memory, which is able to store information over extended time steps without too much decay. The author chooses GRU for this task, due to its performance comparable to LSTM on sequence modeling, but less parameters and easier to train.
Local Scheme
Local scheme introduces an attention mechanism, which allows the encoder to dynamically select and linearly combine different parts of the input sequence, say, the contect vector here is computed by $$ c_{t}=\sum_{j=1}^{T}\alpha_{tj}h_{j} $$ where weighting factor $\alpha_{tj}$ is the attention signal to determine which part should be selected to generate the rew word $y_{t}$, which in turn is a function of hidden states $\alpha_{tj}=q(h_{j},s_{t-1})$, $s_{t-1}$ is the hidden state of decoder at time $t-1$, will be introduced later, graph of local scheme is shown below: Basically, the attention mechanism $\alpha_{tj}$ models the alignment between the inputs around position $j$ and the output at position $t$, so it can be viewed as a local matching model. This scheme enjoys the advantage of adaptively focusing on some important words of the input text according to the generated words of response, i.e., it cover the deficit that global scheme lost some important information.
Hybrid Scheme
As mentioned before, global scheme has the summarization of the entire post, while local scheme can adaptively select the important words in post for various suitable responses. Since post-response pairs in STC are not strictly parallel and a word in different context can have different meanings, the author assumes that the global representation in may provide useful context for extracting the local context, therefore complementary to the local scheme. Thus, hybrid scheme is therefore to combine the global and local schemes by concatenating their encoded hidden states to form an extended hidden representation for each time stamp, as shown below: Here the summarization $h_{T}^{g}$ is incorporated into $c_{t}$ and $\alpha_{tj}$ to provide a global context for local matching, thus the context generator function is $$ c_{t}=\sum_{j=1}^{T}\alpha_{tj}\big[h_{j}^{l};h_{T}^{g}\big] $$ where $\big[h_{j}^{l};h_{T}^{g}\big]$ denotes the concatenation of vectors $h_{j}^{l}$ and $h_{T}^{g}$. The author also mention that the context generator in hybrid scheme will evoke different encoding mechanisms in the global encoder and the local encoder, although they will be combined later in forming a unified representation. More specifically, the last hidden state of global scheme plays a role different from that of the last state of local scheme, since it has the responsibility to encode the entire input sentence. This role of global scheme, however, tends to be not adequately emphasized in training the hybrid encoder when the parameters of the two encoding RNNs are learned jointly from scratch. For this the author first initialize hybrid scheme with the parameters of local scheme and global scheme trained separately, then fine ture the parameters in encoder along with training the parameters of decoder.
Decoder
The graph of decoder is shown below, which is essentially a standard RNN language model except conditioned on the context input $\mathbf{c}$. The generation probability of the $t$-th word is computed by $$ p(y_{t}|y_{t-1},\dots,y_{1},\mathbf{x})=\mathcal{g}(y_{t-1},s_{t},c_{t}) $$ where $y_{t}$ is a one-hot word representation, $\mathcal{g}(\centerdot)$ is a softmax activation function, and $s_{t}$ is the hidden state of decoder at time $t$ computed by$$s_{t}=\mathcal{f}(y_{t-1},s_{t-1},c_{t})$$and $\mathcal{f}(\centerdot)$ is a non-linear activation function (i.e., still GRU unit), and the transformation $\mathbf{L}$ is often assigned as parameters of $\mathcal{f}(\centerdot)$.
To learn the parameters of the model, the target is to maximize the likelihood of observing the original response conditioned on the post in the training set. While for a new post, NRMs generate their responses by using a left-to-right beam search with beam size = 10.
Implementation Details and Experiments
The author uses Stanford Chinese word segmenter to split the posts and responses into sequences of words. Since the number of unique words in post text is 125,237, and that of response text is 679,958. The author therefore construct two separate vocabularies for posts and responses by using 40,000 most frequent words on each side, covering 97.8% usage of words for post and 96.2% for response respectively. All the remaining words are replaced by a special token “UNK”. The dimensions of the hidden states of encoder and decoder are both 1000, and the dimensions of the word-embedding for post and response are both 620. Model parameters are initialized by randomly sampling from a uniform distribution between -0.1 and 0.1. Models are trained by stochastic gradient descent algorithm with mini-batch. Below shows the responses generated by different models, where NRM-glo denotes global scheme, NRM-loc represents local scheme and NRM-hyb is the hybrid scheme, while Rtr.-based represents the Retrieval-based method used as a competitor. Above is a general summary of the paper: “Neural Responding Machine for Short-Text Conversation”, I only describe the algorithm introduced in this paper, and I am trying to build this model by myself in the furture.


Shortly after acquiring an advanced diver's license in Bali, I began to explore Thai waters with future plans to exercise my license at any opportunity to tour wreckage and sealife.
Left: Me touring the U.S.S. Liberty in Indonesian waters - sunken during the Six-Day-War.


|
Maurice Herlihy
Maurice Herlihy's research centers on practical and theoretical
aspects of multiprocessor synchronization, with a focus on wait-free and
lock-free synchronization. His 1991 paper ``Wait-Free Synchronization''
won the 2003 Dijkstra Prize in Distributed Computing, and he shared the
2004 Goedel Prize for his 1999 paper ``The Topological Structure of
Asynchronous Computation''.
He has an A.B. degree in Mathematics from Harvard University and a Ph.D.
degree in Computer Science from MIT. He has been an assistant professor
in the Computer Science department at Carnegie Mellon University, a
member of research staff at Digital Equipment Corporation's Cambridge
(MA) Research Lab, and a consultant for Sun Microsystems. He is now
Professor of Computer Science at Brown University. |
| |
Suresh Jagannathan
Suresh Jagannathan is Associate Professor of Computer Science at
Purdue University. Prior to joining Purdue, he was a Senior Research
Scientist at the NEC Research Institute. His interests are in program
analysis, concurrent and distributed systems, and functional
programming. He received his MS and Ph.d from MIT.
|
| |
Shaz Qadeer
Shaz Qadeer is a member of the Software Productivity Tools group at Microsoft Research.
Before joining Microsoft Research, he was a member of the research staff at the Compaq
Systems Research Center from 1999 to 2002. Shaz received his Ph.D. from the EECS Department of the University of California at Berkeley
|
| |
Doug Lea
Doug Lea is a professor of Computer Science at the State University of New York at Oswego. He is author of the book Concurrent Programming in Java, and co-author of the text Object-Oriented System Development.
He is the author of several widely used software packages, as well as articles and reports on object oriented software development including those on specification, design and implementation techniques, distributed object systems, and software reusability
|
| |
Davide Sangiorgi
Davide is a Professor ("Professore Ordinario") of Computer Science
Department of Computer Science
University of Bologna, Italy.
His research interests include Concurrent systems, especially mobile and higher order: semantics, verification techniques. High-level languages for specifying and programming concurrent activities. Systolic automata and systems.
He is "the author of "The pi-calculus: A Theory of Mobile Processes, Cambridge University Press.
|
|
Vijay Saraswat
Vijay Saraswat joined IBM Research in 2003, after a year as
a Professor at Penn State, a couple of years at startups and 13 years at
Xerox PARC and AT&T Research. His main interests are in programming
languages, constraints, logic and concurrency. At IBM, he leads the work
on the design of X10, a modern object-oriented programming language
intended for scalable concurrent computing.
|
|
Peter Sewell
Peter Sewell studied at Cambridge, Oxford, and Edinburgh, taking his
PhD (supervised by Robin Milner) in 1995. Since then he has been in
the Computer Laboratory at Cambridge, and currently holds a Royal Society
University Research Fellowship and a University Senior Lectureship
there. His research is broadly in applied semantics, for distributed
programming languages, security, and network protocols. |
|
Denis Trystam
Denis Trystram obtained a PhD in Applied Mathematics in 1984 and
a second one in Computer Science in 1988 at Polytechnical Institut in
Grenoble
where he is Professor since 1991.
From this time, he is leading a research team on
Scheduling and Combinatorial Optimization applied to parallel and
distributed computing.
He is currently Regional Editor for Europe for the Parallel Computing
Journal
and participates to the Editorial Board of the IEEE TPDS journal.
|
| |
Nobuko Yoshida
Nobuko Yoshida is an EPSRC Advanced Fellow and a Lecturer in Department of Computing
at Imperial College London. She is an invited expert of W3C Web Services Choreography
Working Group. She studied at Keio, Manchester, Edinburgh, Sussex, Leicester
and Imperial. Her research interests include: formalisation of Web Services,
Distributed Java, secure information flow analysis, access control of mobile
computing, typing systems for concurrent computation and programming, Hoare Logics for programming languages, semantics of
concurrency and functional programming. |


{% extends '_base.html' %} {% load static %} {% block title %}About{% endblock title %} {% block meta %} {% endblock meta %} {% block content %}
I am very direct and honest – both in my personal and professional life. So please don’t expect any sugar-coating.
This no-bullshit approach translates perfectly into helping you get the most out of your data. effectively.
I am not going to fetishize iterations to improve a model’s accuracy by 0.0001%. I rather stay focused on the problem we are actually trying to solve. Will that 0.0001% improvement actually add significant value to your business? If any at all, it will be marginal. And even worse, the costs will not justify that tiny bit of improvement.
Understanding your context will help us find solutions that are actually meaningful to your business. In the end, I am here to solve your problems and to make your life easier.
My tech stack is mostly comprised of open-source technologies for extra flexibility and customizability. This is a snippet of tools that I use regularly.
asd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asd asd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asd asd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asd asd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd asdasd asdas dasdasd asdasd
Some dude, Some position, some companyLet’s have a chat about how we can make data work for you. Feel free to reach out via<EMAIL_ADDRESS>or LinkedIn.
Need some new creative ideas and inputs? Check out my case studies or my Github and get some inspiration right away.


% include _head.html%>
<%= title %>
<% include _navbar.html %> <% include _alert.html%>
Title
保存
戻る
一覧へ
<% include _modal.html %>


The format of .csv file must follow this format:
age,job marital,education,default balance,housing loan,contact,day,month,duration,campaign,pdays,previous,poutcome,y.
Description of above data is as follows:
# bank client data:
1 - age (numeric)
2 - job : type of job (categorical: 'admin.','blue-collar','entrepreneur','housemaid','management','retired','self-employed','services','student','technician','unemployed','unknown')
3 - marital : marital status (categorical: 'divorced','married','single','unknown'; note: 'divorced' means divorced or widowed)
4 - education (categorical: 'basic.4y','basic.6y','basic.9y','high.school','illiterate','professional.course','university.degree','unknown')
5 - default: has credit in default? (categorical: 'no','yes','unknown')
6 - housing: has housing loan? (categorical: 'no','yes','unknown')
7 - loan: has personal loan? (categorical: 'no','yes','unknown')
# related with the last contact of the current campaign:
8 - contact: contact communication type (categorical: 'cellular','telephone')
9 - month: last contact month of year (categorical: 'jan', 'feb', 'mar', ..., 'nov', 'dec')
10 - day_of_week: last contact day of the week (categorical: 'mon','tue','wed','thu','fri')
11 - duration: last contact duration, in seconds (numeric). Important note: this attribute highly affects the output target (e.g., if duration=0 then y='no'). Yet, the duration is not known before a call is performed. Also, after the end of the call y is obviously known. Thus, this input should only be included for benchmark purposes and should be discarded if the intention is to have a realistic predictive model.
# other attributes:
12 - campaign: number of contacts performed during this campaign and for this client (numeric, includes last contact)
13 - pdays: number of days that passed by after the client was last contacted from a previous campaign (numeric; 999 means client was not previously contacted)
14 - previous: number of contacts performed before this campaign and for this client (numeric)
15 - poutcome: outcome of the previous marketing campaign (categorical: 'failure','nonexistent','success')
# social and economic context attributes
16 - emp.var.rate: employment variation rate - quarterly indicator (numeric)
17 - cons.price.idx: consumer price index - monthly indicator (numeric)
18 - cons.conf.idx: consumer confidence index - monthly indicator (numeric)
19 - euribor3m: euribor 3 month rate - daily indicator (numeric)
20 - nr.employed: number of employees - quarterly indicator (numeric)
Output variable (desired target):
21 - y - has the client subscribed a term deposit? (binary: 'yes','no')


To Do List
~ Each day I will accomplish one thing on my to do list ~
Event
Date
Submit
Start Your To Do List From Here!
Example: 訂車票
2018-09-21


Released {{ releaseData.release.releaseCreatedAt | date:"MMMM d yyyy 'at' hh:mm a" }}
It looks like the commits in this release didn't match up to any stories in pivotal tracker! Here's
the full log of what went out
Snap, the commit log we received from heroku was empty. I'm not sure why this happens.


I am Speech & Music Technology Researcher & Data Scientist, working with state-of-the-art machine learning algorithms and audio/sound content production, processing, analysis and distribution. Research, storytelling, making strategy, design and innovation is what i am devoted to. I keep it simple, practical, and applicable.


The shape methods listed below are defined in the RVG, RVG::ClipPath, RVG::Group, and RVG::Pattern classes. You can chain the styles method and the transform methods to the shape methods.
obj.circle(radius, cx=0, cy=0) -> circle
Adds a circle to the target object. The arc of a circle begins at the "3 o'clock" point on the radius and progresses towards the "9 o'clock" point. The starting point and direction of the arc are affected by the user space transform in the same manner as the geometry of the object.
obj.ellipse(rx, ry, cx=0, cy=0) -> ellipse
Adds an ellipse to the target object. The arc of an ellipse begins at the "3 o'clock" point on the radius and progresses towards the "9 o'clock" point. The starting point and direction of the arc are affected by the user space transform in the same manner as the geometry of the object.
obj.line(x1=0, y1=0, x2=0, y2=0) -> line
Adds a line to the target object. Lines are never filled.
obj.path(path_data) -> path
Adds a path to the target object.
A path string. The path string has the same syntax as the d= attribute on SVG's path element. See the SVG standard for a complete description of the syntax.
moveto, lineto, and closepath commands
simple uses of cubic Bézier commands within a path
cubic Bézier commands change their shape according to the position of the control points
simple uses of quadratic Bézier commands within a path
simple uses of arc commands within a path
Elliptical arcs: The following illustrates the four combinations of large-arc-flag and sweep-flag and the four different arcs that will be drawn based on the values of these flags.
obj.polygon(x1, y1, x2, y2...) -> polygon
obj.polygon(array) -> polygon
obj.polygon(array1, array2) -> polygon
Adds a closed shape consisting of a series of connected line segments to the target object.
The arguments to polygon
and polyline can be
x = [1, 3, 5, 7, 9] y = [2,4] canvas.polygon(x, y) # is equivalent to canvas.polygon(1,2, 3,4, 5,2, 7,4, 9,2)
It is an error to specify an odd number of coordinates. Array arguments can be any objects that can be converted to arrays by the Kernel#Array method.
obj.polyline(x1, y1, x2, y2...) ->
polyline
obj.polyline(array) -> polyline
obj.polyline(array1, array2) -> polyline
Adds a set of connected lines segments to the target object. Typically a polyline defines an open shape.
See polygon
obj.rect(width, height, x=0, y=0) -> rect
Adds a rectangle to the target object.
You can define a rounded rectangle by chaining the
round
method to rect
:
obj.rect(width, height, x=0,
y=0).round(rx
[, ry
])
The round method accepts two arguments.
If the second argument is omitted it defaults to the value of the first argument.


OpenAudible Help
This open source app aims to let Audible users enhance their experience maximizing their audible library.
Please respect copyright owners by not distributing MP3 files created with OpenAudible.
Setup
Configure your working directory in the preferences. The working directory will contain Audible files (AAX), MP3 files, artwork, and other data.
Your audible account region, user name and password are used to sync your account. You can leave your password blank if you want to ask for it only when needed for a session.
Connecting to Audible
Connecting to audible is done via a web browser. The first time you use the program you should log in to your audible account using the built-in web browser, under the "Controls" menu.
If able to connect, your library can be scanned and all your audible content is show in the main window.
Downloading Files
Before converting or downloading files, you need to select one or more audible books in your library, then select either "Download" or "Convert to MP3" from the Action menu.
Audible files are kept in the AAX directory. Once converted to MP3, you may decide to delete the AAX files.
Exporting
Your audible library can be exported as a web page or Excel list from the File menu
Menus
File
- Console - View error messages and technical logs
- Export Web Page - Creates a web page listing your books that you can host on a private server
- Export Book List - Saves a list of your books to Excel file
- Quit - Exits the application
Edit
- Preferences- Set application directory, audible region, and user name/password
Controls
- Connect to Audible - Attempts to log into your Audible account for content scraping
- Quick Library Sync - Looks for new books and adds them to your library.
- Full Library Sync - Does a complete scan of your library and updates ratings and book meta data.
- Download All from Audible - Downloads all audible books that haven't already been downloaded
- Convert All to MP3 - Converts downloaded files to MP3
- Browser - Opens internal browser. Connecting and logging in to Audible using this browser helps the app get past any "captchas".
Actions (acts on selected books)
- View In Audible - Opens the Browser to the book's Audible page, if available.
- Show MP3 - Opens Explorer/Finder to display the MP3 in the desktop.
- Play Audio Book - Opens MP3 using your system's default MP3 player.
- Download AAX - Downloads selected books from audible
- Convert to MP3 - Converts selected books to MP3
- Refresh Info - Gets missing book meta data from Audible web page and/or files
Help
- Help - Opens the Browser to this page.
- Project Web Page- Goes to http://openaudible.com
- Check for Update- Checks with openaudible.org to see if a new version is availalbe.
- About Open Audible - The about box and copyright info.
Additional Help
This may stop working at any time, due to changes in Audible systems or web site. If this happens, check for an update or open issues.
No technical support is provided. Open Source additions are welcome.
Suggestions welcome by creating an issue or submitting a pull request.


Just a map of tech friendly spaces in London
Based on Hack Spots, Credits to Josh Russell and his google spreadsheet You can find the source code on github.


Tiles contain the content of an md-grid-list
. They span one or more grid
cells vertically or horizontally, and use md-grid-tile-{footer,header}
to
display secondary content.
The md-grid-tile
directive supports "responsive" attributes, which allow
different md-rowspan
and md-colspan
values depending on the currently
matching media query (as defined in $mdConstant.MEDIA
).
In order to set a responsive attribute, first define the fallback value with
the standard attribute name, then add additional attributes with the
following convention: {base-attribute-name}-{media-query-name}="{value}"
(ie. md-colspan-sm="4"
)
With header:
With footer:
Spanning multiple rows/columns:
Responsive attributes:
| Parameter | Type | Description |
|---|---|---|
md-colspan
number
|
number |
The number of columns to span (default 1). Cannot exceed the number of columns in the grid. Supports interpolation. |
md-rowspan
number
|
number |
The number of rows to span (default 1). Supports interpolation. |


CanvasClip ( ImgSlot, src_x, src_y, src_w, src_h )
Saves a portion of the current canvas to an image slot.
Example:
Canvas ( 1, 0, 0, 50, 50 )


A tabs component with ability to programmatically set active tabs or route to individual tabs.
To install this library, run: npm install @ngx-lite/tabs --save and then from your Angular AppModule:
npm install @ngx-lite/tabs --save
AppModule


Apply for a Budgeting Loan
01/02/2016 - 08/02/2016
Completion Rate
94.3%
4% increase
Total applications
577
(+121) 5% increase
Completion time (average)
4m 12s
15s decrease
Processing time (average)
2m 54s
7s decrease
Problem tracing NINO
13 untracable
(+2)
Assisted digital applications
4 completed
(+1)


---
layout: post
title: Some Metasploit and Oracle Notes - Part 2
date: 2009-05-12 20:41:55.000000000 +01:00
categories:
- Metasploit
- Penetration Testing
tags: []
status: publish
type: post
published: true
---
SCOTT CONNECT NO YES NO
SCOTT DBA NO YES NO
SCOTT RESOURCE NO YES NO
It's worth noting that some of these Oracle modules (there's 9 in the current Metasploit svn versions) have required privilege levels (dbms_cdc_publish for example in a vanilla 10GR2 setup needs EXECUTE_CATALOG_ROLE to run which only SYS and users with the DBA role have...), so it's worth trying out several to fit different scenarios...
So here we are with DBA, which to be honest for a lot attackers is all that's needed. The data in the database is likely to be the "crown jewels" which the attackers looking for, but hey we can go further with the wonders of Metasploit and execute code on the underlying operating system...
5. Leverage Oracles functionality to get access to the underlying operating system
So at the moment I don't see a metasploit option for doing this in *nix (there's a win32 command execution module on mc's page), however that's not a serious problem as it turns out the nice guys at Oracle provide ways to do this easily.
A quick google around revealed this paper from Oracle on command execution from a database user and from my running of it, it works fine (although requires creation of new database objects so best suited to an environment that can be rolled back easily...).
So there you go, from nothing to OS access in 5 easy steps, courtesy of Metasploit...


UIRawImage¶
The UIRawImage module.
RawImage CrossFadeAlpha¶
-
UnityEngineUIRawImage.
__CrossFadeAlpha__SystemSingle_SystemSingle_SystemBoolean__SystemVoid
(UnityEngine.UI.RawImage instanceSystem.Single alphaSystem.Single durationSystem.Boolean ignoreTimeScale)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage CrossFadeColor¶
-
UnityEngineUIRawImage.
__CrossFadeColor__UnityEngineColor_SystemSingle_SystemBoolean_SystemBoolean__SystemVoid
(UnityEngine.UI.RawImage instanceUnityEngine.Color targetColorSystem.Single durationSystem.Boolean ignoreTimeScaleSystem.Boolean useAlpha)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage Cull¶
-
UnityEngineUIRawImage.
__Cull__UnityEngineRect_SystemBoolean__SystemVoid
(UnityEngine.UI.RawImage instanceUnityEngine.Rect clipRectSystem.Boolean validRect)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
op_Equality¶
-
UnityEngineUIRawImage.
__op_Equality__UnityEngineObject_UnityEngineObject__SystemBoolean
(UnityEngine.Object UnityEngine.Object)¶
outputs: unnamed (Boolean
)
flow: none
RawImage Equals¶
-
UnityEngineUIRawImage.
__Equals__SystemObject__SystemBoolean
(UnityEngine.UI.RawImage instanceSystem.Object other)¶
outputs: unnamed (Boolean
)
flow: none
RawImage get_canvas¶
-
UnityEngineUIRawImage.
__get_canvas__UnityEngineCanvas
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Canvas
)
flow: none
RawImage get_canvasRenderer¶
-
UnityEngineUIRawImage.
__get_canvasRenderer__UnityEngineCanvasRenderer
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (CanvasRenderer
)
flow: none
RawImage get_color¶
-
UnityEngineUIRawImage.
__get_color__UnityEngineColor
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Color
)
flow: none
RawImage get_defaultMaterial¶
-
UnityEngineUIRawImage.
__get_defaultMaterial__UnityEngineMaterial
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Material
)
flow: none
RawImage get_depth¶
-
UnityEngineUIRawImage.
__get_depth__SystemInt32
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Int32
)
flow: none
RawImage get_enabled¶
-
UnityEngineUIRawImage.
__get_enabled__SystemBoolean
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Boolean
)
flow: none
RawImage get_gameObject¶
-
UnityEngineUIRawImage.
__get_gameObject__UnityEngineGameObject
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (GameObject
)
flow: none
RawImage get_mainTexture¶
-
UnityEngineUIRawImage.
__get_mainTexture__UnityEngineTexture
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Texture
)
flow: none
RawImage get_maskable¶
-
UnityEngineUIRawImage.
__get_maskable__SystemBoolean
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Boolean
)
flow: none
RawImage get_material¶
-
UnityEngineUIRawImage.
__get_material__UnityEngineMaterial
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Material
)
flow: none
RawImage get_materialForRendering¶
-
UnityEngineUIRawImage.
__get_materialForRendering__UnityEngineMaterial
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Material
)
flow: none
RawImage get_name¶
-
UnityEngineUIRawImage.
__get_name__SystemString
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (String
)
flow: none
RawImage get_onCullStateChanged¶
-
UnityEngineUIRawImage.
__get_onCullStateChanged__UnityEngineUIMaskableGraphicCullStateChangedEvent
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (CullStateChangedEvent
)
flow: none
RawImage get_raycastTarget¶
-
UnityEngineUIRawImage.
__get_raycastTarget__SystemBoolean
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Boolean
)
flow: none
RawImage get_rectTransform¶
-
UnityEngineUIRawImage.
__get_rectTransform__UnityEngineRectTransform
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (RectTransform
)
flow: none
RawImage get_texture¶
-
UnityEngineUIRawImage.
__get_texture__UnityEngineTexture
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Texture
)
flow: none
RawImage get_transform¶
-
UnityEngineUIRawImage.
__get_transform__UnityEngineTransform
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Transform
)
flow: none
RawImage get_uvRect¶
-
UnityEngineUIRawImage.
__get_uvRect__UnityEngineRect
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Rect
)
flow: none
RawImage GetComponent¶
-
UnityEngineUIRawImage.
__GetComponent__SystemType__UnityEngineComponent
(UnityEngine.UI.RawImage instanceSystem.Type type)¶
outputs: unnamed (Component
)
flow: none
RawImage GetComponentInChildren¶
-
UnityEngineUIRawImage.
__GetComponentInChildren__SystemBoolean__T
(UnityEngine.UI.RawImage instanceSystem.Boolean includeInactiveSystem.Type type)¶
outputs: T (Object
)
flow: none
RawImage GetComponentInParent¶
-
UnityEngineUIRawImage.
__GetComponentInParent__SystemType__UnityEngineComponent
(UnityEngine.UI.RawImage instanceSystem.Type t)¶
outputs: unnamed (Component
)
flow: none
RawImage GetComponents¶
-
UnityEngineUIRawImage.
__GetComponents__ListT__SystemVoid
(UnityEngine.UI.RawImage instanceSystem.Collections.Generic.List`1[UnityEngine.Object] results)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage GetComponentsInChildren¶
-
UnityEngineUIRawImage.
__GetComponentsInChildren__SystemBoolean_ListT__SystemVoid
(UnityEngine.UI.RawImage instanceSystem.Boolean includeInactiveSystem.Collections.Generic.List`1[UnityEngine.Object] result)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage GetComponentsInParent¶
-
UnityEngineUIRawImage.
__GetComponentsInParent__SystemBoolean_ListT__SystemVoid
(UnityEngine.UI.RawImage instanceSystem.Boolean includeInactiveSystem.Collections.Generic.List`1[UnityEngine.Object] results)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage GetHashCode¶
-
UnityEngineUIRawImage.
__GetHashCode__SystemInt32
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Int32
)
flow: none
RawImage GetInstanceID¶
-
UnityEngineUIRawImage.
__GetInstanceID__SystemInt32
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Int32
)
flow: none
RawImage GetModifiedMaterial¶
-
UnityEngineUIRawImage.
__GetModifiedMaterial__UnityEngineMaterial__UnityEngineMaterial
(UnityEngine.UI.RawImage instanceUnityEngine.Material baseMaterial)¶
outputs: unnamed (Material
)
flow: none
RawImage GetPixelAdjustedRect¶
-
UnityEngineUIRawImage.
__GetPixelAdjustedRect__UnityEngineRect
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Rect
)
flow: none
RawImage GetType¶
-
UnityEngineUIRawImage.
__GetType__SystemType
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Type
)
flow: none
RawImage GraphicUpdateComplete¶
-
UnityEngineUIRawImage.
__GraphicUpdateComplete__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
op_Implicit¶
-
UnityEngineUIRawImage.
__op_Implicit__UnityEngineObject__SystemBoolean
(UnityEngine.Object)¶
outputs: unnamed (Boolean
)
flow: none
op_Inequality¶
-
UnityEngineUIRawImage.
__op_Inequality__UnityEngineObject_UnityEngineObject__SystemBoolean
(UnityEngine.Object UnityEngine.Object)¶
outputs: unnamed (Boolean
)
flow: none
RawImage IsActive¶
-
UnityEngineUIRawImage.
__IsActive__SystemBoolean
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Boolean
)
flow: none
RawImage IsDestroyed¶
-
UnityEngineUIRawImage.
__IsDestroyed__SystemBoolean
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (Boolean
)
flow: none
RawImage LayoutComplete¶
-
UnityEngineUIRawImage.
__LayoutComplete__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage OnCullingChanged¶
-
UnityEngineUIRawImage.
__OnCullingChanged__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage PixelAdjustPoint¶
-
UnityEngineUIRawImage.
__PixelAdjustPoint__UnityEngineVector2__UnityEngineVector2
(UnityEngine.UI.RawImage instanceUnityEngine.Vector2 point)¶
outputs: unnamed (Vector2
)
flow: none
RawImage Raycast¶
-
UnityEngineUIRawImage.
__Raycast__UnityEngineVector2_UnityEngineCamera__SystemBoolean
(UnityEngine.UI.RawImage instanceUnityEngine.Vector2 spUnityEngine.Camera eventCamera)¶
outputs: unnamed (Boolean
)
flow: none
RawImage Rebuild¶
-
UnityEngineUIRawImage.
__Rebuild__UnityEngineUICanvasUpdate__SystemVoid
(UnityEngine.UI.RawImage instanceUnityEngine.UI.CanvasUpdate update)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage RecalculateClipping¶
-
UnityEngineUIRawImage.
__RecalculateClipping__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage RecalculateMasking¶
-
UnityEngineUIRawImage.

__SetAllDirty__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage SetClipRect¶
-
UnityEngineUIRawImage.
__SetClipRect__UnityEngineRect_SystemBoolean__SystemVoid
(UnityEngine.UI.RawImage instanceUnityEngine.Rect clipRectSystem.Boolean validRect)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage SetLayoutDirty¶
-
UnityEngineUIRawImage.
__SetLayoutDirty__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage SetMaterialDirty¶
-
UnityEngineUIRawImage.
__SetMaterialDirty__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage SetNativeSize¶
-
UnityEngineUIRawImage.
__SetNativeSize__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage SetVerticesDirty¶
-
UnityEngineUIRawImage.
__SetVerticesDirty__SystemVoid
(UnityEngine.UI.RawImage instance)¶
outputs: none
flow inputs: unnamed
flow outputs: unnamed
RawImage ToString¶
-
UnityEngineUIRawImage.
__ToString__SystemString
(UnityEngine.UI.RawImage instance)¶
outputs: unnamed (String
)
flow: none


Compilation Errors
DMS/Filter/Filter.php5
| Type | Line | Description |
|---|---|---|
| notice | 34 | Argument $object is missing from the function Docblock |
| notice | 42 | Argument $object is missing from the function Docblock |
| notice | 42 | Argument $property is missing from the function Docblock |
| notice | 50 | Argument $value is missing from the function Docblock |
| notice | 50 | Argument $filter is missing from the function Docblock |
DMS/Filter/Mapping/ClassMetadata.php4
| Type | Line | Description |
|---|---|---|
| notice | 50 | Argument $property is missing from the function Docblock |
| notice | 62 | Argument $metadata is missing from the function Docblock |
| notice | 78 | Argument $property is missing from the function Docblock |
| notice | 78 | Argument $rule is missing from the function Docblock |
DMS/Filter/Mapping/ClassMetadataFactory.php1
| Type | Line | Description |
|---|---|---|
| notice | 46 | Argument $class is missing from the function Docblock |
DMS/Filter/ObjectWalker.php2
| Type | Line | Description |
|---|---|---|
| notice | 71 | Name of argument $propertyName does not match with function Docblock |
| notice | 83 | Name of argument $propertyName does not match with function Docblock |
DMS/Filter/Rules/Alnum.php3
| Type | Line | Description |
|---|---|---|
| error | 15 | No DocBlock was found for Property $unicodeEnabled |
| error | 17 | No DocBlock was found for Property $allowWhitespace |
| notice | 22 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/Boolean.php1
| Type | Line | Description |
|---|---|---|
| notice | 18 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/Float.php1
| Type | Line | Description |
|---|---|---|
| notice | 19 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/Int.php1
| Type | Line | Description |
|---|---|---|
| notice | 19 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/StripNewlines.php1
| Type | Line | Description |
|---|---|---|
| notice | 18 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/StripTags.php1
| Type | Line | Description |
|---|---|---|
| notice | 25 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/ToLower.php1
| Type | Line | Description |
|---|---|---|
| notice | 27 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/ToUpper.php1
| Type | Line | Description |
|---|---|---|
| notice | 27 | Argument $value is missing from the function Docblock |
DMS/Filter/Rules/Trim.php1
| Type | Line | Description |
|---|---|---|
| notice | 25 | Argument $value is missing from the function Docblock |
DMS/Filter/Version.php1
| Type | Line | Description |
|---|---|---|
| error | 13 | No DocBlock was found for Constant VERSION |


Scroll down for schema examples. Select a format for examples from the tabs above or the mobile navigation menu.
This documentation was automatically generated from a v0.1.0 Semoasa document.
Semoasa is a machine-readable format for extensions to Swagger/OpenAPI 2.0 and 3.0 specifications.
Provider: APIs.guru
x-apiClientRegistration example
{ "url": "https://developer.bbc.co.uk/user/register" }
```yaml url: ‘https://developer.bbc.co.uk/user/register’
*A link to a sign-up page for the API.*
A property of the info object, x-apiClientRegistration includes a URL-formatted property url containing the URL to the resource where developers can register to authenticate with the API.
<a href="https://github.com/APIs-guru/openapi-directory/wiki/specification-extensions">APIs.guru OpenAPI Directory Wiki</a>
|Property|Type|Required|Description
|---|---|---|---|
|url|string(uri-ref)|true|No description|
**In the OpenAPI specification v2.0, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/2.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
**In the OpenAPI specification v3.x, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/3.0.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
## x-apisguru-categories
> x-apisguru-categories example
```json
[
"string"
]
- string
A property of the info object, x-apisguru-categories
is an array of valid values from the list of APIs.guru categories.
APIs.guru OpenAPI Directory Wiki
| Property | Type | Required | Description |
|---|---|---|---|
| anonymous | [string] | false | No description |
In the OpenAPI specification v2.0, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
In the OpenAPI specification v3.x, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
x-description-language example
"string"
```yaml string
An ISO-639 two-character language code to identify the natural language used in descriptions, summaries and titles. This can be used as an input to translating these items.
|Property|Type|Required|Description
|---|---|---|---|
|simple|string|false|No description|
**In the OpenAPI specification v2.0, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/2.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
**In the OpenAPI specification v3.x, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/3.0.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
## x-hasEquivalentPaths
> x-hasEquivalentPaths example
```json
true
true
A property of the root
object, x-hasEquivalentPaths
indicates the source specification has multiple paths which map to the same OpenAPI path (possibly disambiguated with HTML fragment identifiers or differently named path parameters).
| Property | Type | Required | Description |
|---|---|---|---|
| simple | boolean | false | No description |
In the OpenAPI specification v2.0, this extension can be used as follows:
| Object | Description |
|---|---|
| SwaggerObject | Description not found |
In the OpenAPI specification v3.x, this extension can be used as follows:
| Object | Description |
|---|---|
| OpenAPIObject | Description not found |
x-logo example
{ "url": "string", "backgroundColor": "string" }
```yaml url: string backgroundColor: string
*A logo for the API.*
A property of the `info` object, the `x-logo` structure holds an absolute URL to the API logo and an optional background colour in HTML hex notation.
<a href="https://github.com/APIs-guru/openapi-directory/wiki/specification-extensions">APIs.guru OpenAPI Directory Wiki</a>
|Property|Type|Required|Description
|---|---|---|---|
|url|string(uri-ref)|true|No description|
|backgroundColor|string|false|No description|
**In the OpenAPI specification v2.0, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/2.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
**In the OpenAPI specification v3.x, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/3.0.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
## x-origin
> x-origin example
```json
[
{
"url": "http://programmes.api.bbc.com/nitro/api",
"contentType": "application/json",
"converter": {
"url": "https://github.com/mermade/bbcparse",
"version": "1.2.0"
}
},
{
"format": "swagger",
"url": "https://raw.githubusercontent.com/Mermade/bbcparse/master/iblApi/swagger.json",
"version": "2.0"
}
]
- url: 'http://programmes.api.bbc.com/nitro/api'
contentType: application/json
converter:
url: 'https://github.com/mermade/bbcparse'
version: 1.2.0
- format: swagger
url: >-
https://raw.githubusercontent.com/Mermade/bbcparse/master/iblApi/swagger.json
version: '2.0'
A property of the info
object, the x-origin
structure is used to document the source and format of an API in the collection. It is used to round-trip the process of keeping the APIs updated.
Please note, if you include an x-origin extension within your API definition APIs.guru will then append to this array if it exists, allowing an audit trail of the source(s) of an API definition. Valid values for format
In your own x-origin
entries you may alternatively use a contentType property instead of a format property. The version property is then optional.
You may also specify the converter and version used.
| Property | Type | Required | Description |
|---|---|---|---|
| anonymous | [object] | false | No description |
| » url | string(uri-ref) | true | No description |
| » format | string | false | No description |
| » version | string | false | No description |
| » contentType | string | false | No description |
| » converter | object | false | No description |
| »» url | string(uri-ref) | false | No description |
| »» version | string | false | No description |
In the OpenAPI specification v2.0, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
In the OpenAPI specification v3.x, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
x-preferred example
"string"
```yaml string
A property of the `info` object, `x-preferred` is a Boolean property which distinguishes between multiple versions of the same API. Where the `x-providerName` and `x-serviceName` are the same, only one definition should be marked `x-preferred: true`. This helps users of the APIs.guru collection organise and display the APIs.
|Property|Type|Required|Description
|---|---|---|---|
|simple|string|false|No description|
**In the OpenAPI specification v2.0, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/2.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
**In the OpenAPI specification v3.x, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/3.0.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
## x-providerName
> x-providerName example
```json
"string"
string
A property of the info
object, x-providerName
is used to identify the domain of the API host. It is added automatically by APIs.guru
| Property | Type | Required | Description |
|---|---|---|---|
| simple | string | false | No description |
In the OpenAPI specification v2.0, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
In the OpenAPI specification v3.x, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
x-serviceName example
"string"
```yaml string
A property of the `info` object, `x-serviceName` is used to distinguish APIs which are served from the same domain. It may be the subdomain if the API uses one. It is added automatically by APIs.guru
|Property|Type|Required|Description
|---|---|---|---|
|simple|string|false|No description|
**In the OpenAPI specification v2.0, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/2.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
**In the OpenAPI specification v3.x, this extension can be used as follows:**
<aside class="warning">
The extension may only be used in the following objects:
</aside>
|Object|Description|
|---|---|
|<a href="https://github.com/OAI/openapi-specification/tree/master/versions/3.0.0.md#infoObject">InfoObject</a>|The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience.|
## x-tags
> x-tags example
```json
[
"string"
]
- string
Also a property of the info
object, x-tags
is an array of free-form keywords/tags applicable to the API.
| Property | Type | Required | Description |
|---|---|---|---|
| anonymous | [string] | false | No description |
In the OpenAPI specification v2.0, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
In the OpenAPI specification v3.x, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
x-unofficialSpec example
true
```yaml true
```
A property of the info
object, x-unofficialSpec
indicates the definition is produced by a third-party, either manually, by scraping existing documentation or converting a proprietary/undocumented format.
| Property | Type | Required | Description |
|---|---|---|---|
| simple | boolean | false | No description |
In the OpenAPI specification v2.0, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |
In the OpenAPI specification v3.x, this extension can be used as follows:
| Object | Description |
|---|---|
| InfoObject | The object provides metadata about the API. The metadata can be used by the clients if needed, and can be presented in editing or documentation generation tools for convenience. |


--- layout: post authors: ["Mike Jackson"] title: "A new UK administrator for Software Carpentry" date: 2013-10-08 time: "09:00:00" tags: ["Community"] ---
We are pleased to welcome Luke Tweddle of EPCC, The University of Edinburgh, to Software Carpentry. Luke is taking over as UK administrator from Mike Jackson on behalf of The Software Sustainability Institute. In his role, Luke will help UK researchers organise bootcamps for their research groups, institutions and communities; help the local organisers of bootcamps create and customize content; attract instructors and helpers; manage registration; advise on publicity; and provide support in all aspects of organising a bootcamp. If you'd like help organising a bootcamp, or if you're interested in becoming an instructor or helper, please get in touch.


Hello I'm Liching. Service desk anaylst by day, Front end web development enthusiast by night. I've recently completed the Front-End Web Developer Nanodegree by Udacity, and I am excited to put all that I have learnt into practice.
Seen something you like? Or just wanna say hi! Contact me on my social media accounts or send me an email, and I'll repond as soon as I can. I Promise.


Beta This is a test version of the layout of this page. Take the survey to help us improve it
Collection
Documents for software suppliers and anyone else interested in past alternative provision (AP) census collections.
If you are looking for documents for the current AP census collection, visit our guide to submitting data for the alternative provision census .
The documents on this page relate to recently closed AP census collections, including:
You can find documents related to AP returns on the National Archives website . Note: the search function is not available on archived content so please use the filters on the left of each page.


EARTH VS. THE FLYING SAUCERS (director: Fred F. Sears; screenwriter: story by Curt Siodmak/book by Donald E. Keyhoe/George Worthing Yates/Ray Marcus; cinematographer: Fred Jackman Jr.; editor: Danny Landres; cast: Hugh Marlowe (Dr. Russell A. Marvin ), Joan Taylor (Carol Marvin), Donald Curtis (Major Huglin ), Morris Ankrum (General Hanley ), Larry J. Blake (Motorcycle cop), 1956)
Reviewed by Dennis Schwartz
A superficial B- movie about flying saucers, offering no relevant views on matters of space exploration, except some might be amused to see Washington D.C. come under attack by flying saucers. Using Ray Harryhausen's flying saucers, this film becomes mostly a special effect experience. It is a good example of the kind of mediocre, paranoiac sci-fi films that were being made at the time. Though, the exception to this uninteresting sci-fi film at the time, might be the one adapted from Robert Heinlein's novel "Rocketship Galileo," which was made as "Destination Moon (50)." But it wasn't until Kubrick came along in the 1960s with his "2001: A SPACE ODYSSEY" that sci-fi films matured into solid ventures and started to be taken seriously.
Somewhere in the desert, on there way to Project Skyhook, a military space exploration project, the civilian project director Dr. Russell Marvin (Hugh Marlowe) and his new wife, Carol (Joan Taylor), observe a flying saucer. The couple are reluctant to report it, seemingly worried about their careers, afraid that their superiors would take them for loonies, if they report that they saw a flying saucer. But back in the lab, Russ discovers the tape recorder recorded the strange sounds made by the saucer, giving them some concrete proof. General Hanley (Morris Ankrum), Carol's father, warns Russ that all the 11 rockets he previously fired into space, supposedly used as observation posts, have crashed mysteriously back to earth. He urges Russ to put a halt to tomorrow's rocket firing, until the mystery is cleared up. But Russ is determined to carry out the mission.
The scientist couple decide to observe the 12th rocket launch from a soundproof bunker. But before the launch begins, a flying saucer is spotted landing on the project site. When the soldiers fire on the three aliens (dressed in lightweight tin armor carrying solidified electricty) departing from the shelter, they shoot one but the others quickly put an electric shield around themselves and the saucer precedes in destroying the entire project site including the rocket. They take General Hanley as a prisoner on their saucer. Once on board, they will steal his mind for their own research purposes but leave his mindless body intact.
The only survivors at the test site are Russ and Carol. While in the bunker, Russ and Carol discover that the sounds they recorded were a message from the flying saucer arranging a meeting. The message was recorded at supersonic speed, but when the batteries failed and the recorder went into slow motion, they were able to hear the message clearly.
It's off to Washington for the rescued couple, to explain their experience to skeptical political and military leaders. Russ grows impatient with the bureaucratic delays and the failure with Washington to try and make contact with the aliens. So he makes radio contact with the aliens on his own and gets another meeting. Carol and a military liason officer, Major Huglin (Donald Curtis), try to stop him but when it is too late for that, they follow him to the meeting place on the beach. A motorcycle policeman also tags along, and all four are forced into the saucer. They hear the bad news that the aliens want to take over the world, but would prefer to do it without destroying the world. They want to arrange a meeting in 56 days of world leaders. They prove they have the means to carry out their mission by blowing up a destroyer. We also learn that they are humanoids, survivors of a disintegrated solar system. When the policman tries to shoot them, they zap his brain and leave him aboard the saucer, while releasing the other three.
Russ explains to the military leaders what the aliens wanted, and claims that he can build a new weapon, an ultra-sonic gun. He does so with the help of scientists from other parts of the world. While he is working on that project, the aliens change the world's weather patterns by causing meteor showers around the sun. This results in storms and the world's communication systems being destroyed.
The silliness of the film is delightfully highlighted by the finale of the flying saucer attack on Washington DC. In some ways it rescues the film from its banal story, its reactionary politics (having the military in the same bed with science), the uninspired acting, and the film's aim of making the aliens the bad guys, by showing the Ray Harryhausen created flying saucers landing in front of the White House, slicing the Washington Monument in half, and waging a full-scale attack on America's capital. There was also the suggestion by one of the generals of the use of a nuclear bomb. Its use was argued against, by Major Huglin, that it would only destroy our country and might not even work against the aliens. The film becomes a classic in sci-fi for its special effects, despite how mundane everything else about this project is.
REVIEWED ON 3/17/2000 GRADE: C-
Dennis Schwartz: "Ozus' World Movie Reviews"
http://www.sover.net/~ozus
<EMAIL_ADDRESS>© ALL RIGHTS RESERVED DENNIS SCHWARTZ
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


The Java Logging APIs, introduced in package java.util.logging, facilitate software servicing and maintenance at customer sites by producing log reports suitable for analysis by end users, system administrators, field service engineers, and software development teams. The Logging APIs capture information such as security failures, configuration errors, performance bottlenecks, and/or bugs in the application or platform.
The core package includes support for delivering plain text or XML-formatted log records to memory, output streams, consoles, files, and sockets. In addition, the logging APIs are capable of interacting with logging services that already exist on the host operating system.


Go to the first, previous, next, last section, table of contents.
The following information describes how to install g77
.
Note that, for users of the GCC-2.95 version of g77
,
much of the information is obsolete,
and is superceded by the
GCC installation procedures.
Such information is accordingly omitted and flagged as such.
The following information was last updated on 1999-07-17:
g77
.
g77
internals before building.
g77
.
For users of the GCC-2.95 version of g77
,
this information is superceded by the
GCC installation instructions.
This is a list of problems (and some apparent problems which don't really mean anything is wrong) that show up when configuring, building, installing, or porting GNU Fortran.
See section `Installation Problems' in Using and Porting GNU CC,
for more information on installation problems that can afflict
either gcc
or g77
.
These problems can occur on most or all systems.
gcc
needn't be patched.
f771
fails.
g77
developers.
LANGUAGES
is ignored.
Compiling g77
requires GNU C, not just ANSI C.
Fixing this wouldn't
be very hard (just tedious), but the code using GNU extensions to
the C language is expected to be rewritten for 0.6 anyway,
so there are no plans for an interim fix.
This requirement does not mean you must already have gcc
installed to build g77
.
As long as you have a working C compiler, you can use a
"bootstrap" build to automate the process of first building
gcc
using the working C compiler you have, then building
g77
and rebuilding gcc
using that just-built gcc
,
and so on.
g77
no longer requires application of a patch file
to the gcc
compiler tree.
In fact, no such patch file is distributed with g77
.
This is as of version 0.5.23
and egcs
version 1.0.
It should be possible to build the runtime without building cc1
and other non-Fortran items, but, for now, an easy way to do that
is not yet established.
This information does not apply to
the GCC-2.95 version of g77
,
It'd be helpful if g77
's `Makefile.in' or `Make-lang.in'
would create the various `stagen' directories and their
subdirectories, so developers and expert installers wouldn't have to
reconfigure after cleaning up.
That help has arrived as of version 0.5.23 of g77
and version 1.1 of egcs
.
Configuration itself no longer creates any particular directories
that are unique to g77
.
The build procedures in `Make-lang.in' take care of
that, on demand.
Prior to version 0.5.23 of g77
and version 1.1 of egcs
,
g77
would sometimes ignore
the absence of f77
and F77
in the
LANGUAGES
macro definition used for the
make
command being processed.
As of g77
version 0.5.23
and egcs
version 1.1,
g77
now obeys this macro
in all relevant situations.
However, in versions of gcc
through 2.8.1,
non-g77
portions of gcc
,
such as g++
,
are known to go ahead and perform various
language-specific activities when their
respective language strings do not appear
in the LANGUAGES
macro in effect
during that invocation of make
.
It is expected that these remaining problems will
be fixed in a future version of gcc
.
A linker bug on some versions of AIX 4.1 might prevent building
when g77
is built within gcc
.
It might also occur when building within egcs
.
See section LINKFAIL
.
g77
has been in alpha testing since September of
1992, and in public beta testing since February of 1995.
Alpha testing was done by a small number of people worldwide on a fairly
wide variety of machines, involving self-compilation in most or
all cases.
Beta testing has been done primarily via self-compilation,
but in more and more cases, cross-compilation (and "criss-cross
compilation", where a version of a compiler is built on one machine
to run on a second and generate code that runs on a third) has
been tried and has succeeded, to varying extents.
Generally, g77
can be ported to any configuration to which
gcc
, f2c
, and libf2c
can be ported and made
to work together, aside from the known problems described in this
manual.
If you want to port g77
to a particular configuration,
you should first make sure gcc
and libf2c
can be
ported to that configuration before focusing on g77
, because
g77
is so dependent on them.
Even for cases where gcc
and libf2c
work,
you might run into problems with cross-compilation on certain machines,
for several reasons.
g77
as a cross-compiler in some cases,
though there are assumptions made during
configuration that probably make doing non-self-hosting builds
a hassle, requiring manual intervention.
gcc
might still have some trouble being configured
for certain combinations of machines.
For example, it might not know how to handle floating-point
constants.
libg2c
is built could make
building g77
as a cross-compiler easier--for example,
passing and using `$(LD)' and `$(AR)' in the appropriate
ways.
(This is improved in the egcs
version of g77
,
especially as of version 1.1.)
libg2c
) for a target
system, depending on the systems involved in the configuration.
(This is a general problem with cross-compilation, and with
gcc
in particular.)
Here are some internal g77
settings that can be changed
by editing source files in `egcs/gcc/f/' before building.
This information, and perhaps even these settings, represent
stop-gap solutions to problems people doing various ports
of g77
have encountered.
As such, none of the following information is expected to
be pertinent in future versions of g77
.
MXUNIT
.
g77
as a cross-compiler.
DATA
initialization.
As distributed, whether as part of f2c
or g77
,
libf2c
accepts file unit numbers only in the range
0 through 99.
For example, a statement such as `WRITE (UNIT=100)' causes
a run-time crash in libf2c
, because the unit number,
100, is out of range.
If you know that Fortran programs at your installation require
the use of unit numbers higher than 99, you can change the
value of the MXUNIT
macro, which represents the maximum unit
number, to an appropriately higher value.
To do this, edit the file `egcs/libf2c/libI77/fio.h' in your
g77
source tree, changing the following line:
#define MXUNIT 100
Change the line so that the value of MXUNIT
is defined to be
at least one greater than the maximum unit number used by
the Fortran programs on your system.
(For example, a program that does `WRITE (UNIT=255)' would require
MXUNIT
set to at least 256 to avoid crashing.)
Then build or rebuild g77
as appropriate.
Note: Changing this macro has no effect on other limits
your system might place on the number of files open at the same time.
That is, the macro might allow a program to do `WRITE (UNIT=100)',
but the library and operating system underlying libf2c
might
disallow it if many other files have already been opened (via OPEN
or
implicitly via READ
, WRITE
, and so on).
Information on how to increase these other limits should be found
in your system's documentation.
Some Fortran programs require output
(writes) to be flushed to the operating system (under UNIX,
via the fflush()
library call) so that errors,
such as disk full, are immediately flagged via the relevant
ERR=
and IOSTAT=
mechanism, instead of such
errors being flagged later as subsequent writes occur, forcing
the previously written data to disk, or when the file is
closed.
Essentially, the difference can be viewed as synchronous error reporting (immediate flagging of errors during writes) versus asynchronous, or, more precisely, buffered error reporting (detection of errors might be delayed).
libg2c
supports flagging write errors immediately when
it is built with the ALWAYS_FLUSH
macro defined.
This results in a libg2c
that runs slower, sometimes
quite a bit slower, under certain circumstances--for example,
accessing files via the networked file system NFS--but the
effect can be more reliable, robust file I/O.
If you know that Fortran programs requiring this level of precision
of error reporting are to be compiled using the
version of g77
you are building, you might wish to
modify the g77
source tree so that the version of
libg2c
is built with the ALWAYS_FLUSH
macro
defined, enabling this behavior.
To do this, find this line in `egcs/libf2c/f2c.h' in
your g77
source tree:
/* #define ALWAYS_FLUSH */
Remove the leading `/* ', so the line begins with `#define', and the trailing ` */'.
Then build or rebuild g77
as appropriate.
g77
, on most machines, puts many variables and arrays on the stack
where possible, and can be configured (by changing
FFECOM_sizeMAXSTACKITEM
in `egcs/gcc/f/com.c') to force
smaller-sized entities into static storage (saving
on stack space) or permit larger-sized entities to be put on the
stack (which can improve run-time performance, as it presents
more opportunities for the GBE to optimize the generated code).
Note: Putting more variables and arrays on the stack
might cause problems due to system-dependent limits on stack size.
Also, the value of FFECOM_sizeMAXSTACKITEM
has no
effect on automatic variables and arrays.
See section Bugs Not In GNU Fortran, for more information.
The g77
build will crash if an attempt is made to build
it as a cross-compiler
for a target when g77
cannot reliably determine the bit pattern of
floating-point constants for the target.
Planned improvements for version 0.6 of g77
will give it the capabilities it needs to not have to crash the build
but rather generate correct code for the target.
(Currently, g77
would generate bad code under such circumstances if it didn't crash
during the build, e.g. when compiling a source file that does
something like `EQUIVALENCE (I,R)' and `DATA R/9.43578/'.)
A warning message is issued when g77
sees code that provides
initial values (e.g. via DATA
) to an aggregate area (COMMON
or EQUIVALENCE
, or even a large enough array or CHARACTER
variable)
that is large enough to increase g77
's compile time by roughly
a factor of 10.
This size currently is quite small, since g77
currently has a known bug requiring too much memory
and time to handle such cases.
In `egcs/gcc/f/data.c', the macro
FFEDATA_sizeTOO_BIG_INIT_
is defined
to the minimum size for the warning to appear.
The size is specified in storage units,
which can be bytes, words, or whatever, on a case-by-case basis.
After changing this macro definition, you must
(of course) rebuild and reinstall g77
for
the change to take effect.
Note that, as of version 0.5.18, improvements have
reduced the scope of the problem for sparse
initialization of large arrays, especially those
with large, contiguous uninitialized areas.
However, the warning is issued at a point prior to
when g77
knows whether the initialization is sparse,
and delaying the warning could mean it is produced
too late to be helpful.
Therefore, the macro definition should not be adjusted to reflect sparse cases. Instead, adjust it to generate the warning when densely initialized arrays begin to cause responses noticeably slower than linear performance would suggest.
g77
used to warn when it was used to compile Fortran code
for a target configuration that is not basically a 32-bit
machine (such as an Alpha, which is a 64-bit machine, especially
if it has a 64-bit operating system running on it).
That was because g77
was known to not work
properly on such configurations.
As of version 0.5.20, g77
is believed to work well
enough on such systems.
So, the warning is no longer needed or provided.
However, support for 64-bit systems, especially in areas such as cross-compilation and handling of intrinsics, is still incomplete. The symptoms are believed to be compile-time diagnostics rather than the generation of bad code. It is hoped that version 0.6 will completely support 64-bit systems.
For users of the GCC-2.95 version of g77
,
this information is superceded by the
GCC installation instructions.
For users of the GCC-2.95 version of g77
,
this information is superceded by the
GCC installation instructions.
For users of the GCC-2.95 version of g77
,
this information is superceded by the
GCC installation instructions.
Go to the first, previous, next, last section, table of contents.


Nothing more. Nothing less. My life began on a small farm next to some budding flowers. It was then that I realised that I was a streamer


We at BuildBlockz.com would be lying if we say real-estate runs in our blood, when it's actually the other way round. Landing a dream home could quickly become a nightmare if anything goes awry in the concrete jungle food chain. To ensure that it doesn't, BuildBlockz brings everyone in the food chain on a common platform - from builders to contractors and architects to interior designers. We are a targeted professional network that aims to create a synergy between different stake-holders in the real-estate sector via connections and specializations. As real-estate revolves everyday, we keep our users updated every minute by recommending the latest trends based on their affordability and feasibility. Block by block we are revamping real-estate the way everyone sees it.
We at BuildBlockz.com would be quite apt if we say that we provide the building blocks for any real estate project. Finding the right professionals for your task is of utmost importance especially because if anything depart from the correct course, the project could quickly deteriorate. To ensure that it doesn't, BuildBlockz brings everyone in the concrete jungle food chain on a common platform - from builders to contractors and architects to interior designers so as to provide a one stop solution. We are a targeted professional network that aims to create a synergy between different stake-holders in the real-estate sector via connections and specializations. As real-estate industry evolves everyday, we keep our users updated every minute by recommending the latest trends based on their affordability and technical feasibility. Block by block we are bringing the real-estate community closer & are simultaneously building strong relationships between the professionals & their clients.
What is Shit Cup rahe cutte
ector via connections and specializations. As real-estate industry evolves everyda their affordability and technical feasibility.
 As real-estate industry evolves everyda
What is Shit Cup rahe cutte
ector via connections and specializations. As real-estate industry evolves everyda their affordability and technical feasibility.
 As real-estate industry evolves everyda
What is Shit Cup rahe cutte
ector via connections and specializations. As real-estate industry evolves everyda their affordability and technical feasibility.
 As real-estate industry evolves everyda
What is Shit Cup rahe cutte
ector via connections and specializations. As real-estate industry evolves everyda their affordability and technical feasibility.
 As real-estate industry evolves everyda


When is the launch?
We're in public beta and you can try it now for free. We will publicly launch in January/February 2021.
Do I need to know how to code
You do not need to know how to code, but in some cases, knowing some code will allow you to build better web apps.
Is Budibase open source?
Budibase is open-source. The builder is licensed AGPL v3, the server is licensed GPL v3, and the client is licensed MPL.
Can I build a website with Budibase?
Budibase is for building internal tools and custom software.
Is Budibase free?
Yes, to an extent. You will never pay for using the builder. There are certain processes you might need to pay for depending on the extent of your usage - for example, hosting and workflows.
Can I become a Budibase partner?
Not yet, but we are exploring the finer details of partnerships so please register your interest: Partnerships