Playing the game is quite straightforward:
-Arrow keys move the character,
-A attacks other players and AI enemies,
-T interacts with npcs, resoures and buildings.
-Clicking the map tells what is in the clicked tile
Currently the game includes:
-Multiplayer with trading and pvp
-Resource mining
-Npcs and AI enemies
-Wearing items to improve the character
-Different buildings (shops, banks etc.)


USD = US Dollars
EUR = Euros
JPY = Japanese Yen
AUD = Australian Dollars
CAD = Canadian Dollars
NZD = Newzealand Dollars
INR = Indian Rupees
RUB = Russian Ruble
SGD = Singapore Dollars
CHF = Swiss Franc
GBP = Pound Sterling
KWD = Kuwaiti Dinar
KYD = Caymanian Dollars
FROM
TO


The DataGrid
component has an API for inline editing of records in the cells. When an item is being
edited, the inline edit UI with default save
and cancel
buttons is displayed.
Attributes:
editorEnabled
- define whether or not the item editor UI is enabled for this
DataGrid
. When the editor is enabled, the user can open it by double-clicking a row or hitting
enter when a row is focused. The editor can also be opened programmatically using
theeditItem(Object)
method.
editorBuffered
- define if the buffered editor mode is active.
editorSaveCaption
- the caption on the save button in the DataGrid
editor.
editorCancelCaption
- the caption on the cancel button in the DataGrid
editor.


Our Mission
We, the members of Karnataka Police, shall uphold the Law and the Rights of all people for a safe and secure
environment, conducive to their internal and external growth and development. Towards this end, we set
for ourselves the following objectives:
- Protect the lives and liberties of the people from criminal and anti- social elements.>
- Earn the good will, support and active assistance of the community.>
- Co-ordinate with other departments of Criminal Justice System.>
- Equal treatment regardless of caste, religion, social and economic status or political affiliations.>
- Due consideration for women, children, senior citizens and weaker sections. Improve professional knowledge,
skills and attitudes and adopt modern methods in police work.>
- Promote human rights and professional values of integrity, honesty and efficiency.>
- Accept and play our role in social transformation and bring about improvement in the quality of life
with society>


--- author: Colene Chow categories: app date: '2011-12-15 00:57:37' permalink: /2011/12/15/building-mobile-apps-in-the-cloud-with-tiggr-and-phonegap/ slug: building-mobile-apps-in-the-cloud-with-tiggr-and-phonegap status: publish title: Building Mobile Apps in the Cloud with Tiggr and PhoneGap type: post format: html tags: - Guest Post - App - iOS ---
Guest blog post by Max Katz
Tiggr - the easiest platform for building mobile apps in the cloud
Tiggr is a cloud-based mobile apps builder. It lets developers build HTML5/JavaScript and native apps very quickly, entirely in the cloud. There is nothing to download, nothing to install, and nothing to configure. Just create a new project, and you are ready to start building your mobile app with HTML5/JavaScript and PhoneGap.
Building mobile UI with jQuery Mobile
To build the mobile UI, there is a visual editor and jQuery Mobile components, as shown below. You simply drag and drop components into the phone area.
You can create multiple screens, navigate between screens, store data in Local Storage, and write custom JavaScript. This means you can create the complete UI for your mobile app and also test in a Web browser.
Testing the mobile app
Testing is one of the most innovative features in Tiggr. There is a big Test button at the top. Clicking that button opens up a browser window with the mobile app in it. Need to test the app on the actual device? Scan the QR code, and e-mail the URL to your device. Don’t forget to make the app public. (More about testing native apps a little bit later.)
Consuming any cloud service
Once the UI is ready, the next step is connecting to cloud services. In Tiggr, you can connect to any cloud REST service. Below is an example of using the service editor to define a connection to Twitter’s search REST service:
Once the service is defined, it is mapped to the UI. A service usually has inputs and outputs. Mapping specifies how different UI components are related to different service parameters for input and output. There is even a visual data mapping editor available (service output is shown on the left, screen components are shown on the right:
The JavaScript column (on the left) allows you to write custom JavaScript to give you more power and flexibility when mapping service to UI (custom JavaScript is also available when mapping UI to service).
One last step is adding an event to invoke the service. For example, on a specific button click (HTML click event) the service could be invoked. You can of course use any other HTML events. With Tiggr this is easy.
Native apps with PhoneGap PhoneGap is an awesome mobile app platform. It takes advantage of Web technologies developers already know: HTML and JavaScript. PhoneGap makes it super easy to wrap any mobile Web app as native, but also provide access to device native features via its elegant and easy-to-use API.
Exporting native app Every app (native) in Tiggr comes with PhoneGap installed. To export the app as native is as simple as clicking the big Export button:
If you are targeting for Android, then you can download Android Release binary (.apk). This file is ready for the Android Market. Tiggr has a Android .apk file editor for you to enter all the necessary information.
If you are targeting iOS, then export iOS xCode project (Eclipse). You can then build the app on your machine or use cloud-based PhoneGap Build service to build for iOS.
As an alternative, for both Android, iOS or any other platform you can download the mobile Web version (Web resources, HTML/CSS/JS) and use PhoneGap Build service to build for the platform.
For example, if you need to build for BlackBerry, then simply download the mobile Web version and upload to PhoneGap Build. It’s that simple.
Using PhoneGap API
What if you need to invoke PhoneGap API to access device features? Well, that’s very simple too. Tiggr comes with Run Custom JavaScript action, which can be invoked on any HTML event.
As an example, we will implement a Vibrate button.
First, we add the click HTML event to the button:
Add an action - Run Custom JavaScript:
and finally add the PhoneGap JavaScript call:
Another option is to create a JavaScript file (Project > JavaScript), write all the custom code in functions in the file, and then invoke any function via the Run Custom JavaScript action.
Note that you can also import an existing JavaScript file (from a URL or via uploading).
Invoking a function from the custom JavaScript file is done via Run Custom JavaScript action:
Testing native apps Once you use a native API, testing in Web browser is no longer as useful. To test native apps, you can use Tiggr Mobile Tester. It’s a native app (Android, iOS) that lists all your mobile app in Tiggr. You simply tap any app in the list to launch the native app for testing. It’s the easiest and fasted way to test a native app without having to install it. The tester app looks like this:
Device components
Being able to invoke custom JavaScript (and PhoneGap API) almost from anywhere makes Tiggr and PhoneGap so powerful. But, that’s not all. Tiggr now has components in the Device palette which are based on PhoneGap API:
This is even simpler than using the API. More components are planned to be added such as Camera and others.
Tiggr and PhoneGap - The ULTIMATE mobile app development combo?
We think so.
You have Tiggr, a cloud-based mobile apps builder. There is nothing to install or configure. Tiggr uses jQuery Mobile, HTML5, JavaScript and CSS to build mobile apps. The app's UI is built inside a visual editor, the app can easily be connected to any cloud service, and the app can be tested at any point in a browser or on a device. At the end, you can export the app source.
Then, you have PhoneGap, a powerful framework that uses HTML5 and JavaScript to build native mobile apps and makes it super easy to access native features in an app, such as contacts and camera. PhoneGap’s cloud-based build service allows you to build quickly for multiple platforms.
When you combine the two, Tiggr and PhoneGap, you get powerful cloud-based HTML5 mobile apps builder with an easy way to incorporate native device features and build for multiple mobile platforms.
Sign up for Tiggr and build your mobile app today.
_Max Katz is Head of Developer Relations for Tiggr at Exadel. You can find his writings about Web and mobile technologies on his blog, and follow him Twitter at @maxkatz. He also runs the Tiggr blog. Lastly, you can always email him at<EMAIL_ADDRESS>_


Design
Colors
Fonts
Open Sans Light
Open Sans Regular
Open Sans Semi-Bold
Open Sans Bold
Open Sans Extra-Bold
Georgia Regular
Georgia Italic
Core
Typography
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
This is a paragraph with an inline link.
This is a blockquote...
If I had to choose a superhero to be, I would pick Superman. He's everything that I'm not.
— Stephen Hawking
Responsive Grid
For containers, rows and columns, Frunt uses the popular bootstrap grid, for now.
Components
Alert
Solid alerts:
Muted alerts:
Block (full-width):
Dismissable (Requires alert JS):
Badge
You can have an inline badge
Or some round badges:
1 2 3
Or...
You can also have a really long badge. Good for notes, or help text.
Burger
| Burger | |
| Active |
Forms
Tables
| Hero | Power | First Appearance |
|---|---|---|
| Atomic Man | Super strength | 1946 |
| Inferno | Breathing flames | 1941 |
| Crimson Rider | Badass cowgirl | 1939 |
Tiles
Tiles can have options: --halves, --thirds, --quarters, --fifths and --sixths. Also, the tiles will wrap automatically, no need for wrapping rows.
Thirds:
Quarters:
Quarters (padded):
You can also add -padded to any of the options for spacing between tiles.
Overlays:
Tiles can display an overlay with content on hover or with an active state.


SCHED_SETAFFINITY
Section: Linux Programmer's Manual (2)Updated: 2008-11-14
Index Return to Main Contents
NAME
sched_setaffinity, sched_getaffinity - set and get a process's CPU affinity maskSYNOPSIS
#define _GNU_SOURCE #include <sched.h> int sched_setaffinity(pid_t pid, size_t cpusetsize, cpu_set_t *mask); int sched_getaffinity(pid_t pid, size_t cpusetsize, cpu_set_t *mask);
DESCRIPTION
A process's CPU affinity mask determines the set of CPUs on which it is eligible to run. On a multiprocessor system, setting the CPU affinity mask can be used to obtain performance benefits. For example, by dedicating one CPU to a particular process (i.e., setting the affinity mask of that process to specify a single CPU, and setting the affinity mask of all other processes to exclude that CPU), it is possible to ensure maximum execution speed for that process. Restricting a process to run on a single CPU also avoids the performance cost caused by the cache invalidation that occurs when a process ceases to execute on one CPU and then recommences execution on a different CPU.A CPU affinity mask is represented by the cpu_set_t structure, a "CPU set", pointed to by mask. A set of macros for manipulating CPU sets is described in CPU_SET(3).
sched_setaffinity() sets the CPU affinity mask of the process whose ID is pid to the value specified by mask. If pid is zero, then the calling process is used. The argument cpusetsize is the length (in bytes) of the data pointed to by mask. Normally this argument would be specified as sizeof(cpu_set_t).
If the process specified by pid is not currently running on one of the CPUs specified in mask, then that process is migrated to one of the CPUs specified in mask.
sched_getaffinity() writes the affinity mask of the process whose ID is pid into the cpu_set_t structure pointed to by mask. The cpusetsize argument specifies the size (in bytes) of mask. If pid is zero, then the mask of the calling process is returned.
RETURN VALUE
On success, sched_setaffinity() and sched_getaffinity() return 0. On error, -1 is returned, and errno is set appropriately.ERRORS
- EFAULT
- A supplied memory address was invalid.
- EINVAL
- The affinity bit mask mask contains no processors that are currently physically on the system and permitted to the process according to any restrictions that may be imposed by the "cpuset" mechanism described in cpuset(7).
- EINVAL
- (sched_getaffinity() and, in kernels before 2.6.9, sched_setaffinity()) cpusetsize is smaller than the size of the affinity mask used by the kernel.
- EPERM
- (sched_setaffinity()) The calling process does not have appropriate privileges. The caller needs an effective user ID equal to the user ID or effective user ID of the process identified by pid, or it must possess the CAP_SYS_NICE capability.
- ESRCH
- The process whose ID is pid could not be found.
VERSIONS
The CPU affinity system calls were introduced in Linux kernel 2.5.8. The system call wrappers were introduced in glibc 2.3. Initially, the glibc interfaces included a cpusetsize argument, typed as unsigned int. In glibc 2.3.3, the cpusetsize argument was removed, but was then restored in glibc 2.3.4, with type size_t.CONFORMING TO
These system calls are Linux-specific.NOTES
After a call to sched_setaffinity(), the set of CPUs on which the process will actually run is the intersection of the set specified in the mask argument and the set of CPUs actually present on the system. The system may further restrict the set of CPUs on which the process runs if the "cpuset" mechanism described in cpuset(7) is being used. These restrictions on the actual set of CPUs on which the process will run are silently imposed by the kernel.sched_setscheduler(2) has a description of the Linux scheduling scheme.
The affinity mask is actually a per-thread attribute that can be adjusted independently for each of the threads in a thread group. The value returned from a call to gettid(2) can be passed in the argument pid. Specifying pid as 0 will set the attribute for the calling thread, and passing the value returned from a call to getpid(2) will set the attribute for the main thread of the thread group. (If you are using the POSIX threads API, then use pthread_setaffinity_np (3) instead of sched_setaffinity().)
A child created via fork(2) inherits its parent's CPU affinity mask. The affinity mask is preserved across an execve(2).
This manual page describes the glibc interface for the CPU affinity calls. The actual system call interface is slightly different, with the mask being typed as unsigned long *, reflecting the fact that the underlying implementation of CPU sets is a simple bit mask. On success, the raw sched_getaffinity() system call returns the size (in bytes) of the cpumask_t data type that is used internally by the kernel to represent the CPU set bit mask.
The cpu_set_t affinity mask size provided by glibc only allows for upto 1024 CPUs. It is possible to build Linux kernels with greater than 1024 CPUs. Any application using the statically sized cpu_set_t will fail with EINVAL on such kernels. It is thus recommended that applications avoid using the statically sized cpu_set_t type, and instead dynamically allocate a mask using the CPU_*_S macros described in the CPU_SET(3) man page. Since it is not possible to determine ahead of time what NR_CPUS value the kernel was built with, applications must be prepared to catch EINVAL, and retry the command with a larger dynamically allocated mask. The example that follows illustrates portable usage.
EXAMPLE
#define _GNU_SOURCE #include <sched.h> #include <stdio.h> #include <errno.h> int main(void) { cpu_set_t *mask; size_t size; int i; int nrcpus = 1024; realloc: mask = CPU_ALLOC(nrcpus); size = CPU_ALLOC_SIZE(nrcpus); CPU_ZERO_S(size, mask); if ( sched_getaffinity(0, size, mask) == -1 ) { CPU_FREE(mask); if (errno == EINVAL && nrcpus < (1024 << 8)) { nrcpus = nrcpus << 2; goto realloc; } perror("sched_getaffinity"); return -1; } for ( i = 0; i < nrcpus; i++ ) { if ( CPU_ISSET_S(i, size, mask) ) { printf("CPU %d is set\n", (i+1)); } } CPU_FREE(mask); return 0; }
SEE ALSO
clone(2), getcpu(2), getpriority(2), gettid(2), nice(2), sched_get_priority_max(2), sched_get_priority_min(2), sched_getscheduler(2), sched_setscheduler(2), setpriority(2), CPU_SET(3), sched_getcpu(3), capabilities(7), pthread_setaffinity_np(3), cpuset(7)COLOPHON
This page is part of release 3.22 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/.
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- RETURN VALUE
- ERRORS
- VERSIONS
- CONFORMING TO
- NOTES
- EXAMPLE
- SEE ALSO
- COLOPHON
This document was created by man2html, using the manual pages.
Time: 05:33:05 GMT, December 24, 2015


In Figma, create a frame named @lottie. This is where your animation will be rendered. It will get its size and position from that rectangle.
[Optional] Control the animation by commenting with code:
{ "arguments": { "loop": true, "autoplay": true, "speed": 3 } }
Paste the frame link here, add your Lottie files, and enjoy 🔥 Time to share it with your friends ?
Create animated mockups in seconds and share them to the world. See the tutorial here.
Only available on desktop at the moment!
Preview
Switch Account


Nick Ooms
Senior Full stack JavaScript Developer
Curriculum Vitae
Summary
Started developing with Borland Turbo Pascal and later some x86 Assembly on a4.77Mhz IBM PC some 25 years ago.
Executed my first XMLHttpRequest (Currently ) back in 1999 on IE5 and was immediately hooked on the freedom and dynamic nature of JavaScript.
In the following years I developed a (now known as SPA or Single Page ApplicaржЮon) framework based on a self-developed XML dialect for defining fully funcржЮonal, resizeable pixel perfect copies of Windows 7 (Windows XP at first with all 3 color themes, followed by office 2003, and later adopted Vista and the Aero look).
I simply love Javascript and have been using it on front & back-end ( Aptana Jaxer followed by Node.js ) for well over 15 years.
R&D
ITEA LASCOT
Large Scale Collaborative Decision Support Technology
Crisis management R&D project for ITEA, for which I created a CEP (Complex Event Processing} engine.
IWT SERKET
SEcuRisation KEeps Threats
R&D project using computer vision based on CCTV camera video for IWT (Instituut voor Innovatiee door Wetenschap en Technologie vlaanderen).
GENESIS FP7
European Commission FP7 R&D Project, for which I developed a semantic modelling framework (Buddata Studio) that can generateva geospaржЮal database (MySQL & PostgreSQL), WebService layer (SOAP , REST WFS 1.1 - 2.0) and front-end SPA based on XSD schemas of INSPIRE standards.
Languages
| Language |
Level |
| Dutch |
Mother Tongue |
| English |
Fluent |
| French |
Intermediate |
Skills
Development Languages
- JavaScript
- TypeSript
- ES3
- ES5
- ES6, ES7, ES8
- Python
- C#
- VB
- C
- Java
- PASCAL
- HTML
- CSS
- XML
- SQL
- Assembly
- GL
- BPMN
Frameworks & Technologies
- Apollo GraphQL
- Docker
- Apollo GraphQL
- JQuery, JQuery UI, ExtJS, Bootstrap
- AngularJS, Angular 2
- React, Flux, Redux, React Router,
- Neo4J, Structr
- MongoDB, MongooseJS
- MySQL, GEOSpaржЮal extensions
- PostgreSQL PostGIS,
- SQL Server, Oracle PLSQL
Operating Systems
- MSDOS
- Windows 3.10 - Windows 10
- Linux, Debian, Fedora, Deepin Linux, Ubuntu, Android
- Mac OS X, iOS
Experience
Porphyrio [09/2019 - 11/2019]
ChatLayer [04/2019 - 06/2019]
Neanex [02/2018 - 02/2019]
Robovision 3D labeller
- WebGL
- ThreeJS
- Vue
- Node.js
Neanex
- WebGL
- Node.js
- Neo4J
- Structr
- React
- Apollo GraphQL
SlickSS [03/2017 - 08/2017]
SlickSS
Freelance & Open Source Projects [04/2015 - 02/2016]
Freelance & Open Source
- ReactJS
- AngularJS
- JavaScript
- Webpack
- RollupJS
- WebGL
- WebAudio
4C / Cronos [11/1998 - 03/2015]
AGIV
- OpenLayers
- Node.js
- JavaScript
- CSS
- HTML5
- XML
- JSON
- Aptana Jaxer
- Buddata Studio (JavaScript-based rich web client)
- Buddata UI Framework (JavaScript codebase used by Buddata Studio)
- Buddata OGC Web Feature Service 2.0
- Enterprise Architect (Sparx)
- ShapeChange 2.0
- Buddata ebXML3.0 Registry Service
- OGC CSW for ebRIM resolver-broker
- Bizagi Process Modeler
- MySQL
- PostgreSQL/PostGIS
Itineris
- C#
- MS Visual Studio
- XSLT
- MS Word templates
- SQLServer
- Microsoft AX
Arcelor Mital Logistics
kZenLabs
- Java
- C#
- Node.js
- Javascript
- HTML5
- CSS
- XML
- JSON
- Aptana Jaxer
- Buddata Studio
- PostgreSQL / PostGIS
- MySQL
GENESIS FP7 - 4CT/kZenLabs
- Java
- C#
- Node.js
- Javascript
- CSS
- HTML5
- XML
- JSON
- Apatan Jaxer
- Buddata Studio (JavaScript-based rich web client)
- Buddata UI Framework (JavaScript codebase used by Buddata Studio)
- Buddata OGC Web Feature Service 2.0
- Buddata OGC Web Processing Service
- Buddata OGC CSW for ebRIM resolver-broker
- PostgreSQL/PostGIS
- MySQL
Business Solutions [12/1997 - 09/1998]
Solvay NV [05/1997 - 11/1997]


Komodo. Contribute to jl777/komodo development by creating an account on GitHub.
I think this is needlessly complicated ... All it really needs is anm RPC to switch it on or off...
and block everything
the wallet code is checking all tx anyway sop I added an extra filter.
but its not very well made, does work though.
1
Strob08-Apr-19 12:30 PM
At the same time as this dwy attack I'm having an ice attack on my home! Many small electricity cuts this morning, but my 5000VA UPS is supporting my server at all time!(edited)
3
3
blackjok3r08-Apr-19 12:30 PM
not sure I will have a blaster working in time, he did say sometime yesterday he was going to put it back a few days becasue he couldnt get it working
ok, one last question (i hope) the pubkey should be the btcpubkey?
NutellaLicka08-Apr-19 01:05 PM
No, it should be the pubkey of your KMD address. BTCpubkey is for mainnet
testnet is notarising AC's(BEER, PIZZA, TXSCLCC) to KMD
MadCryptoHead08-Apr-19 01:05 PM
Ok, the ine that it generates when I create the wallet
NutellaLicka08-Apr-19 01:05 PM
They're the only 4 chains you need to worry about
blackjok3r08-Apr-19 01:06 PM
the pubkey is the same for all coins
BTC or whatever... the address is generated by hashing it with a prefix
NutellaLicka08-Apr-19 01:07 PM
If you do it through iguana
MadCryptoHead08-Apr-19 01:09 PM
Thanks to all, when my extremely busy (and cheap) server manage to start komodo again, I will try all this :S
ComputerGenie 👴👴👴08-Apr-19 01:15 PM
@Strob I did move, but the ping trade-off vs network speed made the move itself a nominal difference
This is all part of a job interview, so I can't give all of my secrets away
1
1
blackjok3r08-Apr-19 01:19 PM
@ComputerGenie 👴👴👴 whats your address ? I need to send you some BEER (edited)
4
ComputerGenie 👴👴👴08-Apr-19 01:19 PM
RBlowMe5iYqz4bYk38aPsz2xwk7z79aLsv
4
1
blackjok3r08-Apr-19 01:21 PM
2500 very small BEERs sent
looks like your script handled that no worries
see how I go, might get the wallet filter working on my node and send million of utxo at tit and see what happens
ComputerGenie 👴👴👴08-Apr-19 01:26 PM
cept for the fact that I had the wrong addy in it and now I have 0.0000
blackjok3r08-Apr-19 01:27 PM
LOL
watching the blocks... the TX cache was like 3000->6000 then 3 blocks later back where it started(edited)
maybe a wallet filter isnt even needed with a good merge script and clean wallet transactions
yeah we didnt have that before... now that I think of it ... wallet filter seems to have too many draw backs comapred to just doing that
merge and clean
ComputerGenie 👴👴👴08-Apr-19 01:31 PM
fwiw, other than adding nExpiryHeight, it's the same script I used for the original attack
2
now if my local wallet will ever sync so I can send it back....
blackjok3r08-Apr-19 01:33 PM
doyou want some more
ComputerGenie 👴👴👴08-Apr-19 01:33 PM
LOL
blackjok3r08-Apr-19 01:34 PM
sent 1 beer in 5c peices
1665 utxos
alright this is enough.
I still have 63% of KMD sync to go, getting bored. Guyess sleepwhile waiting...(edited)
ComputerGenie 👴👴👴08-Apr-19 02:06 PM
LOL my local wallet is 1/40th the size after dropping all of the watch-only data
Strob08-Apr-19 02:22 PM
@ComputerGenie 👴👴👴 I noticed the other day that one of your wallet was like 200MB what were those watch-only data?
ComputerGenie 👴👴👴08-Apr-19 02:23 PM
no, that one is just an assload of txes
Strob08-Apr-19 02:23 PM
ok
ComputerGenie 👴👴👴08-Apr-19 02:24 PM
I have 1 PIZZA wallet that is 370MB without watch-only
Strob08-Apr-19 02:24 PM
mining?
ComputerGenie 👴👴👴08-Apr-19 02:24 PM
that was a fun week
no, back when we were doing mm testing
Strob08-Apr-19 02:25 PM
ok
newvulcan08-Apr-19 02:43 PM
Ok, got the right software all in place, done a reboot and everything appears to have started with no errors except for the last bit (is not official notary). However although I though I had put my details into testnet, I hadn't, so I've just put a PR in - hopefully with that enabled everything should work


The ‘Teardrop Isle’ of Sri Lanka has a great deal to offer travellers – from stunning coastline and beaches to the lush green highlands of the interior, ancient cultures and delicious cuisine. Having been directly in the path of the trade routes even before the days of the spice trade, it’s a multi-faceted country that will keep you fascinated, particularly with its wealth of ancient sites. Here are some of our favourite World Wonders from Sri Lanka. All that’s left to do is wrap your tongue around the place names!The Ancient City of PolonnaruwaFeaturing the ruins of Parakramabahu I dating from the 12th Century, Polonnaruwa was Sri Lanka’s second capital city Sigiriya Site of the famous ‘Lion Mountain’, Sigiriya has been inhabited since the 3rd century BC, and was established as King Kassapa’s capital in the 5th Century AD. and many things also
Inclution
Accommodation in a well appointed room
Meals as per hotel plan
All transfers and sightseeing as per the itinerary in an air-conditioned vehicle.
All Toll taxes, Parking & State Tax.
Exclution
GST 5%
Anything not mentioned under ‘Package Inclusions’
All personal expenses, optional tours and extra meals
Camera fees, alcoholic/non-alcoholic beverages, mineral water and starters
Vehicle service on leisure days for sightseeing not included in the itinerary
Entrance fees at all monuments and museums mentioned in the itinerary
Medical and travel insurance
Tips, laundry and phone calls
Payment policy
Advanced booking Fee
30 days or more before date of departure: 25% of total cost
29 - 20 days before date of departure: 50% of total cost
19 days or less before date of departure: 100% of total cost
Important: The booking stands liable to be cancelled if 100% payment is not received less than 20 days before date of departure.


Object Detection
Image Processing
Below table provides list of object identified in image
Image is getting analyzed ...


If you have a keybase account with at least one Twitter, Github or Reddit proof, you can get 10 ETH of the PoA network.
You have to connect to the private PoA network by connecting your MetaMask to a Custom RPC and unlocking it.


Navbar
Home
(current)
Features
Pricing
Dropdown link
Action
Another action
Something else here
Static Image or Color, on every page of Site
$contents


| Package | Description |
|---|---|
| py4j | |
| py4j.commands | |
| py4j.reflection |
| Class and Description |
|---|
| CallbackClient
A CallbackClient is responsible for managing communication channels: channels
are created as needed (e.g., one per concurrent thread) and are closed after
a certain time.
|
| DefaultGatewayServerListener
This class implements a default
GatewayServerListener . |
| Gateway
A Gateway manages various states: entryPoint, references to objects returned
to a Python program, etc.
|
| GatewayConnection
Manage the connection between a Python program and a Gateway.
|
| GatewayServerListener
A client can implement this listener to be notified of Gateway events.
|
| JVMView
A JVM view keeps track of imports and import searches.
|
| Py4JException
Exception raised when an error is encountered while using Py4J.
|
| Py4JNetworkException
Exception raised when a network error is encountered while using Py4J.
|
| ReturnObject
A ReturnObject wraps a value returned by a method.
|
| Class and Description |
|---|
| Gateway
A Gateway manages various states: entryPoint, references to objects returned
to a Python program, etc.
|
| Py4JException
Exception raised when an error is encountered while using Py4J.
|
| ReturnObject
A ReturnObject wraps a value returned by a method.
|
| Class and Description |
|---|
| CallbackClient
A CallbackClient is responsible for managing communication channels: channels
are created as needed (e.g., one per concurrent thread) and are closed after
a certain time.
|
| Gateway
A Gateway manages various states: entryPoint, references to objects returned
to a Python program, etc.
|
| JVMView
A JVM view keeps track of imports and import searches.
|


{% blocktrans %} As the survey just launched, we are waiting a few days to have enough data points to show you the trends!  If you want to get a transcript with your past responses to the survey, click here! You will be redirected to our Open Humans server which stores your data securely. {% endblocktrans %}
{% blocktrans %} As the survey just launched, we are waiting a few days to have enough data points to show you the trends! Come back later and see what’s happening around you! {% endblocktrans %}


Step 2. Upload Your Data
Input Data
Choose file
Ignore First Line
Output Data
Choose file
Ignore First Line
Is Categorical Data?
Save your data by specifying a unique identifier?


WebVy is a smarter and easier way for small, locally owned businesses to bring in more clients, via the Internet. Our service provides you with everything you need to do just that and more.
We are a small, but growing, group of web developers, designers, and media productionist that understand how hard it is to find quality service without having to spend a fortune or learn a new trade. We are here to help you!
Our main service is providing websites and a server for it to run on. We can find a template that best suits you, or even build you one from scratch! Unlike many other generic services, we offer to maintain it for you overtime, per your request.
CloseIf oyu don't have your own graphics, or need a few more, we've got you covered! We partner with a professional photography business to get you the media production you need to help draw in more clients.
CloseWe know your time is important. That makes it important to us as well. We make sure that the service we provide is not only excellent, but is done in a timely matter so that you can handle the influx of clients!
CloseOur service makes sure that you don't have to worry as much about updating, maintaining, and the constant security of your website/marketing. We handle all of the dirty work and hardware so you don't have to!
We work for you and with you to create the wonderful masterpeice and project you need so that you can promote your business and/or inform your many clients.
CloseWhen all is said and done, your project is completely up-and-running, we don't just leave you in the dark. We are partners even after the initial service. The biggest and best part of our service is the maintanence we preform (mostly per your request) on your website/server. It is a great package deal that is also affordable!
Close


Your privacy is important to us. It is Otto Template Demo's policy to respect your privacy regarding any information we may collect from you across our website, https://otto-template.webflow.io/, and other sites we own and operate.
We only ask for personal information when we truly need it to provide a service to you. We collect it by fair and lawful means, with your knowledge and consent. We also let you know why we’re collecting it and how it will be used.
We only retain collected information for as long as necessary to provide you with your requested service. What data we store, we’ll protect within commercially acceptable means to prevent loss and theft, as well as unauthorized access, disclosure, copying, use or modification.
We don’t share any personally identifying information publicly or with third-parties, except when required to by law.
Our website may link to external sites that are not operated by us. Please be aware that we have no control over the content and practices of these sites, and cannot accept responsibility or liability for their respective privacy policies.
You are free to refuse our request for your personal information, with the understanding that we may be unable to provide you with some of your desired services.
Your continued use of our website will be regarded as acceptance of our practices around privacy and personal information. If you have any questions about how we handle user data and personal information, feel free to contact us.
This policy is effective as of 21 March 2020.


Container Once Retention Strategy
For each job in the queue, an own docker container is started. Once the job has finished, the container is shut down.
Container Idle Retention Strategy
Based on the workload provided by the queue (load average), new docker containers are started on demand. After the job(s) have finished, the container is not shut down immediately.
If no new job was executed on this agent/container during the period of the Idle delay, the container is shut down. Retention time 0 means never being deleted automatically.


[gecode-users] Gecode's Gist
Guido Tack
tack at ps.uni-sb.de
Wed Oct 25 23:23:08 CEST 2006
Hi everyone!
The name "Explorer" seemed already somewhat taken (not only by the Mozart
search tree tool, but also by a commercial company mainly in the OS
market), so we decided to move on to a fresh name for our search tool: The
Graphical Interactive Search Tool, Gist.
>From now on you find the preview of Gist for C++ in the svn at
https://svn.gecode.org/svn/gist/trunk
Cheers,
Guido
--
Guido Tack
http://www.ps.uni-sb.de/~tack
More information about the gecode-users
mailing list


Following IV administration of autologous red cells labeled in vitro with 99mTc pertechnetate, gated equilibrium images were acquired in the left anterior oblique (LAO), anterior (ANT), and left lateral (LAT) projections. Computer estimated left ventricular ejection fraction (LVEF) was calculated from the total counts in the end-systolic and end-diastolic left ventricular regions with background correction.
Dose: mCi
Evaluation of cardiac function.
None.
Morphology:
Wall motion:
Ejection fraction: %
Normal right and left ventricular chamber sizes. Normal right and left ventricular segmental wall motion.


Thrift module: interfaces
Constants
| Constant | Type | Value |
SERVICE_NAME | string | "InterfaceService" |
SERVICE_VERSION | string | "1.0.0" |
Enumerations
Enumeration: InetFamilyType
Enum for indicating the family types supported. Based on this value,
corresponding family will be used in APIs. As of now inet and inet6 families
are supported.
INTF_AF_INET | 2 |
INET Family
|
Data structures
Struct: InterfaceRetStatus
| Key | Field | Type | Description | Requiredness | Default value |
| 1 | err_code | i32 | Error code
| default | |
| 2 | err_str | string | Error string
| default | |
Return status for Interface API calls.
Return code consists of error code and corresponding error string.
Struct: InterfaceAddressConfig
| Key | Field | Type | Description | Requiredness | Default value |
| 1 | port_name | string | | required | |
| 2 | ifl_unit | i32 | | required | |
| 3 | family | InetFamilyType | | required | |
| 4 | interface_address | string | | required | |
Interface address configuration data structure.
Equivalent cli example -
set interfaces ge-1/1/6 unit 0 family inet address <IP_ADDRESS>/24
set interfaces ge-1/1/6 unit 0 family inet6 address abcd::1/64
Services
Service: InterfacesService
List of Interface Service APIs supported in JET
Function: InterfacesService.InterfaceAddressCreate
InterfaceRetStatus
InterfaceAddressCreate(InterfaceAddressConfig
ip_config)
Configure an interface address based on family type passed as input.
Error List:
INVALID_ARGUMENTS - Invalid input arguments
GENERAL_ERROR - General error
EOK - Success
Function: InterfacesService.InterfaceAddressDelete
InterfaceRetStatus
InterfaceAddressDelete(InterfaceAddressConfig
ip_config)
Delete an interface address based on family type passed as input.
Error List:
INVALID_ARGUMENTS - Invalid input arguments
GENERAL_ERROR - General error
EOK - Success


{% extends 'core/base.html' %} {% load static %} {% block content %}
{{course.description}}
You will enroll the course below:
You will release the course below:


BURKINA FASO. WEST AFRICA. Dear Friend, I Mr.Sami mohammad the Chairman of Contract Awarding Committee of the EUROPEAN UNION CONSTRUCTION CONTRACT(ECC) in BURKINA FASO West Africa. I got your information in a business directory from the Burkina Faso Chamber of Commerce and ndustries, when I was searching for a reliable, honest and trust worthy person to entrust this business with. I was simply inspired and
motivated to pick your contact from the directory. After discussing my view and your profile with my colleagues, they were very much satisfied and decided to contact you immediately for this mutual business relationship.
We wish to transfer the sum of USD$36.000,000.00 (Thirty Six million United States Dollars only.) into your personal or company's bank account. This fund was a residue of the over invoiced contract bills awarded by us for the supply of equiment,hard/soft wares, pharmaceuticals/medical items relating to constructing tool's, light and heavy duty vehicles, apparels and other administrative logistics etc for the Burkina Faso Projects.  As the Chairman of CAC, I have the cooperation and mandate of the Financial Director and the Secretary of the Organisation. We arranged and over invoiced the contract funds supplied by different companies from different countries. It was our consensus to seek the assistance of a willing foreigner to provide us with the facilities to transfer this money out of Burkina Faso.< /STRONG>
This is borne out of our belief in the non-stable and sporous political nature of this sub-egion.The original contractors have been duly paid by the Bank of Africa Ouaga-Burkina-Faso in West Africa. (Bank of Africa, Ouaga-Burkina-Faso in West Africa). Through our bankers - Societe Generale Banque. This balance is suspended in the escrow accounts awaiting claims by any foreign company of our choice. We intend to pay out this fund NOW as the organization is winding up its activities and the coast has been achieved.
Based on the laws and ethics of employment, we as civil servants working under this organization, are not allowed to operate a foreign account. This is the more reason why we needed your assistance to provide an account that can sustain this fund for safe keeping and our future investment with your comprehensive advise, assistance and partnership in your country.It is however agreed, as the account owner in this deal to allow you 30% of the entire sum as compensation, 60% will be held on trust for us while 10% will be used to defray any incidental charges and cost during the course of the transaction.
This transaction will be successfully concluded within 14 days if you accord us your unalloyed and due cooperation. You should provide the followings;YOUR COMPANY'S NAME WITH COMPLETE ADDRESS,TEL AND FAX NUMBERS. (if available)THE NAME OF YOUR BANK,ITS ADDRESS WITH TEL, FAX AND TELEX NUMBERS AND YOUR ACCOUNT NUMBER. THE COMPLETE MAILING ADDRESS OF THE BENEFICIARY WITH TELEPHONE AND FAX NUMBERS.
Upon the receipt of this information, the documents and approval with the text will be sent to you for confirmation and then forwarded to the organization for ratification and subsequent payment. As with the case of all organized (sensitive) and conspired DEALS, we solicit for your unreserved
confidentiality and utmost secret in this business. We hope to retire peacefully and lead a honourable business life afterwards. There are no risks involved regards in this business. I sugest you reply me back for more intimate and details discussions. I suggest you get back to me as soon as possible stating your wish in this deal. please reply me through this my alternative email. address<EMAIL_ADDRESS>Yours Faithfully. Mr. SAMI MOHAMMAD (AB).
CaraMail, le seul webmail à vous offrir des fils d'info RSS sans aucun logiciel à installer!


| up: STATUS | index | Zimbu documentation |
|
The builtin type status. It has either the value FAIL or OK. The object methods can be used on a status variable or value: IO.print("It did " .. FAIL.ToString())
|
FUNC $Compare(status other) int @public
FUNC $Equal(status other) bool @public
FUNC $ToString() string @public
FUNC $ToString(string format) string @public
|
| Copyright 2013 Bram Moolenaar All Rights Reserved. |
| Licensed under the Apache License, Version 2.0. See the LICENSE file or obtain a copy at: http://www.apache.org/licenses/LICENSE-2.0 |


-*- html -*-
Merl overview page
Note: EDoc uses @@ and @} as escape sequences, so in the below text, `@@'
must be written `@@@@' and `@}' must be written `@@}'
@author Richard Carlsson
@copyright 2010-2014 Richard Carlsson
@title Merl - Metaprograming in Erlang
@doc Merl is a more user friendly interface to the `erl_syntax' module in
the `syntax_tools' application, making it easy both to build new ASTs
(abstract syntax trees) from scratch and to match and decompose existing
ASTs. For details that are outside the scope of Merl itself, please see the
documentation of `erl_syntax'.
== Quick start ==
To enable the full power of Merl, your module needs to include the Merl
header file:
```-include_lib("merl/include/merl.hrl").'''
Then, you can use the `?Q(Text)' macros in your code to create ASTs or match
on existing ASTs. For example:
```Tuple = ?Q("{foo, 42}"),
?Q("{foo, _@Number}") = Tuple,
Call = ?Q("foo:bar(_@Number)")'''
Calling `merl:print(Call)' will then print the following code:
```foo:bar(42)'''
The `?Q' macros turn the quoted code fragments into ASTs, and lifts
metavariables such as `_@Tuple' and `_@Number' to the level of your Erlang
code, so you can use the corresponding Erlang variables `Tuple' and `Number'
directly. This is the most straightforward way to use Merl, and in many
cases it's all you need.
You can even write case switches using `?Q' macros as patterns. For example:
```case AST of
?Q("{foo, _@Foo}") -> handle(Foo);
?Q("{bar, _@Bar}") when erl_syntax:is_integer(Bar) -> handle(Bar);
_ -> handle_default()
end'''
These case switches only allow `?Q(...)' or `_' as clause patterns, and the
guards may contain any expressions, not just Erlang guard expressions.
If the macro `MERL_NO_TRANSFORM' is defined before the `merl.hrl' header
file is included, the parse transform used by Merl will be disabled, and in
that case, the match expressions `?Q(...) = ...', case switches using
`?Q(...)' patterns, and automatic metavariables like `_@Tuple' cannot be
used in your code, but the Merl macros and functions still work. To do
metavariable substitution, you need to use the `?Q(Text, Map)' macro, e.g.:
```Tuple = ?Q("{foo, _@bar, _@baz}", [{bar, Bar}, {baz,Baz}])'''
The text given to a `?Q(Text)' macro can be either a single string, or a
list of strings. The latter is useful when you need to split a long
expression over multiple lines, e.g.:
```?Q(["case _@Expr of",
" {foo, X} -> f(X);",
" {bar, X} -> g(X)",
" _ -> h(X)"
"end"])'''
If there is a syntax error somewhere in the text (like the missing semicolon
in the second clause above) this allows Merl to generate an error message
pointing to the exact line in your source code. (Just remember to
comma-separate the strings in the list, otherwise Erlang will concatenate
the string fragments as if they were a single string.)
== Metavariable syntax ==
There are several ways to write a metavariable in your quoted code:
- Atoms starting with `@', for example `` '@foo' '' or `` '@Foo' ''
- Variables starting with `_@', for example `_@bar' or `_@Bar'
- Strings starting with ``"'@'', for example ``"'@File"''
- Integers starting with 909, for example `9091' or `909123'
Following the prefix, one or more `_' or `0' characters may be used to
indicate "lifting" of the variable one or more levels, and after that, a `@'
or `9' character indicates a glob metavariable (matching zero or more
elements in a sequence) rather than a normal metavariable. For example:
- `` '@_foo' '' is lifted one level, and `_@__foo' is lifted two
levels
- `_@@@@bar' is a glob variable, and `_@_@bar' is a lifted glob
variable
- `90901' is a lifted variable,`90991' is a glob variable, and `9090091'
is a glob variable lifted two levels
(Note that the last character in the name is never considered to be a lift
or glob marker, hence, `_@__' and `90900' are only lifted one level, not
two. Also note that globs only matter for matching; when doing
substitutions, a non-glob variable can be used to inject a sequence of
elements, and vice versa.)
If the name after the prefix and any lift and glob markers is `_' or `0',
the variable is treated as an anonymous catch-all pattern in matches. For
example, `_@_', `_@@@@_', `_@__', or even `_@__@_'.
Finally, if the name without any prefixes or lift/glob markers begins with
an uppercase character, as in `_@Foo' or `_@_@Foo', it will become a
variable on the Erlang level, and can be used to easily deconstruct and
construct syntax trees:
```case Input of
?Q("{foo, _@Number}") -> ?Q("foo:bar(_@Number)");
...'''
We refer to these as "automatic metavariables". If in addition the name ends
with `@', as in `_@Foo@', the value of the variable as an Erlang term will
be automatically converted to the corresponding abstract syntax tree when
used to construct a larger tree. For example, in:
```Bar = {bar, 42},
Foo = ?Q("{foo, _@Bar@@}")'''
(where Bar is just some term, not a syntax tree) the result `Foo' will be a
syntax tree representing `{foo, {bar, 42}}'. This avoids the need for
temporary variables in order to inject data, as in
```TmpBar = erl_syntax:abstract(Bar),
Foo = ?Q("{foo, _@TmpBar}")'''
If the context requires an integer rather than a variable, an atom, or a
string, you cannot use the uppercase convention to mark an automatic
metavariable. Instead, if the integer (without the `909'-prefix and
lift/glob markers) ends in a `9', the integer will become an Erlang-level
variable prefixed with `Q', and if it ends with `99' it will also be
automatically abstracted. For example, the following will increment the
arity of the exported function f:
```case Form of
?Q("-export([f/90919]).") ->
Q2 = erl_syntax:concrete(Q1) + 1,
?Q("-export([f/909299]).");
...'''
== When to use the various forms of metavariables ==
Merl can only parse a fragment of text if it follows the basic syntactical
rules of Erlang. In most places, a normal Erlang variable can be used as
metavariable, for example:
```?Q("f(_@Arg)") = Expr'''
but if you want to match on something like the name of a function, you have
to use an atom as metavariable:
```?Q("'@Name'() -> _@@@@_." = Function'''
(note the anonymous glob variable `_@@@@_' to ignore the function body).
In some contexts, only a string or an integer is allowed. For example, the
directive `-file(Name, Line)' requires that `Name' is a string literal and
`Line' an integer literal:
```?Q("-file(\"'@File\", 9090).") = ?Q("-file(\"foo.erl\", 42).")).'''
This will extract the string literal `"foo.erl"' into the variable `Foo'.
Note the use of the anonymous variable `9090' to ignore the line number. To
match and also bind a metavariable that must be an integer literal, we can
use the convention of ending the integer with a 9, turning it into a
Q-prefixed variable on the Erlang level (see the previous section).
=== Globs ===
Whenever you want to match out a number of elements in a sequence (zero or
more) rather than a fixed set of elements, you need to use a glob. For
example:
```?Q("{_@@@@Elements}") = ?Q({a, b, c})'''
will bind Elements to the list of individual syntax trees representing the
atoms `a', `b', and `c'. This can also be used with static prefix and suffix
elements in the sequence. For example:
```?Q("{a, b, _@@@@Elements}") = ?Q({a, b, c, d})'''
will bind Elements to the list of the `c' and `d' subtrees, and
```?Q("{_@@@@Elements, c, d}") = ?Q({a, b, c, d})'''
will bind Elements to the list of the `a' and `b' subtrees. You can even use
plain metavariables in the prefix or suffix:
```?Q("{_@First, _@@@@Rest}") = ?Q({a, b, c})'''
or
```?Q("{_@@@@_, _@Last}") = ?Q({a, b, c})'''
(ignoring all but the last element). You cannot however have two globs as
part of the same sequence.
=== Lifted metavariables ===
In some cases, the Erlang syntax rules make it impossible to place a
metavariable directly where you would like it. For example, you cannot
write:
```?Q("-export([_@@@@Name]).")'''
to match out all name/arity pairs in the export list, or to insert a list of
exports in a declaration, because the Erlang parser only allows elements on
the form `A/I' (where `A' is an atom and `I' an integer) in the export list.
A variable like the above is not allowed, but neither is a single atom or
integer, so `` '@@@@Name' '' or `909919' wouldn't work either.
What you have to do in such cases is to write your metavariable in a
syntactically valid position, and use lifting markers to denote where it
should really apply, as in:
```?Q("-export(['@@_@@Name'/0]).")'''
This causes the variable to be lifted (after parsing) to the next higher
level in the syntax tree, replacing that entire subtree. In this case, the
`` '@@_@@Name'/0 '' will be replaced with `` '@@@@Name' '', and the ``/0''
part was just used as dummy notation and will be discarded.
You may even need to apply lifting more than once. To match the entire
export list as a single syntax tree, you can write:
```?Q("-export(['@@__Name'/0]).")'''
using two underscores, but with no glob marker this time. This will make the
entire ``['@@__Name'/0]'' part be replaced with `` '@@Name' ''.
Sometimes, the tree structure of a code fragment isn't very obvious, and
parts of the structure may be invisible when printed as source code. For
instance, a simple function definition like the following:
```zero() -> 0.'''
consists of the name (the atom `zero'), and a list of clauses containing the
single clause `() -> 0'. The clause consists of an argument list (empty), a
guard (empty), and a body (which is always a list of expressions) containing
the single expression `0'. This means that to match out the name and the
list of clauses of any function, you'll need to use a pattern like
`?Q("'@Name'() -> _@_@Body.")', using a dummy clause whose body is a glob
lifted one level.
To visualize the structure of a syntax tree, you can use the function
`merl:show(T)', which prints a summary. For example, entering
```merl:show(merl:quote("inc(X, Y) when Y > 0 -> X + Y."))'''
in the Erlang shell will print the following (where the `+' signs separate
groups of subtrees on the same level):
```function: inc(X, Y) when ... -> X + Y.
atom: inc
+
clause: (X, Y) when ... -> X + Y
variable: X
variable: Y
+
disjunction: Y > 0
conjunction: Y > 0
infix_expr: Y > 0
variable: Y
+
operator: >
+
integer: 0
+
infix_expr: X + Y
variable: X
+
operator: +
+
variable: Y'''
This shows another important non-obvious case: a clause guard, even if it's
as simple as `Y > 0', always consists of a single disjunction of one or more
conjunctions of tests, much like a tuple of tuples. Thus:
- ``"when _@Guard ->"'' will only match a guard with exactly one
test
- ``"when _@@@@Guard ->"'' will match a guard with one or more
comma-separated tests (but no semicolons), binding `Guard' to the list
of tests
- ``"when _@_Guard ->"'' will match just like the previous pattern, but
binds `Guard' to the conjunction subtree
- ``"when _@_@Guard ->"'' will match an arbitrary nonempty guard,
binding `Guard' to the list of conjunction subtrees
- ``"when _@__Guard ->"'' will match like the previous pattern, but
binds `Guard' to the whole disjunction subtree
- and finally, ``"when _@__@Guard ->"'' will match any clause,
binding `Guard' to `[]' if the guard is empty and to `[Disjunction]'
otherwise
Thus, the following pattern matches all possible clauses:
```"(_@@Args) when _@__@Guard -> _@@Body"'''


I was 17 years old, and had never tripped before. I was very experienced with weed, and had experimented with a few other substances, but I had never had mushrooms before. When I was given the opportunity to shroom, I jumped at it.
I read everything I could find about psilocybin. I decided it was safe enough, although I was somewhat worried about having a bad trip. My friends and I decided the beach would be a good environment for the trip. We left early that morning, excited and nervous.
About 8:00 am my friend (Dave) and I crushed the mushrooms into two glasses of orange juice. The mushrooms were smallish, and brown-gray. Not a powerful appearance at all. We downed the cups quickly, making 'yuck' faces. My other two friends (Mike and Dennis) took two hits of acid each instead of mushrooms. None of us had eaten in the past twelve hours.
We walked from the car into the sand and laid out our little camp. A couple towels and a CD player; we were set. About 20 minutes after ingestion, I started laughing at everything. Every comment, every movement was extremely amusing to me. 'They're working,' I announced. Soon I had an intense body high, similar to ecstasy. I noticed little lines wiggling around everything. If I closed my eyes, the brightest kaleidoscope would dance behind my eyelids. Patterns would turn into shapes, people, animals, and combinations of all three.
When I came to my peak, I was completely gone. My friends' talking made very little sense. All four of us would repeat things over and over till it was understood or forgotten about. I ignored everyone, and concentrated on the show. It seemed to me that my mind had become a sort of playground. I could trip watching and listening to the waves, watch the colors as they came in and the patterns that developed in them. Or I could stare at my towel. The texture of it made amazing patterns and was fun to touch, too. There were so many ways to have fun. I would go back and forth between these activities, enjoying myself immensely. I also thought about the deeper topics of life. I decided I wasn't afraid of death. I became friends with all the plant life on the dune next to me; all life was beautiful. I smoked a cigarette for half an hour, maybe more, unlit.
Dave and I decided to walk down to the waves. I stood up and began to walk. Amazing! Moving around felt like the earth was spinning beneath my feet like a treadmill. I realized at that point that I really had very little control over what was going on. 'Man, I can't tell whether I'm awake, or dreaming this.'
'Yeah, I'm tripping out hard, I wish I had more mushrooms, or some of that acid though.'
I had forgotten completely about the mushrooms. I found his comment almost vulgar. I felt I was becoming closer to all life, and all he could think about was more drugs. I felt like no one understood what I had learned, or how I thought. I am not usually an emotional person at all, so these thoughts were very alien to me. We walked back to the group and I sat back down, resuming my wave-watching. The others decided to go back to the car to listen to music on my friend's nice stereo. I elected to stay behind, too content to move.
While alone I pondered life further. Trains of thought were coming and going and evolving so quickly. I would have a stunning revelation, and forget it twenty seconds later. While doing this, I was holding an unlit cigarette, and trying to figure out how to put new batteries in my CD player. A man was suddenly in front of me, saying something. I couldn't understand him, so I stared dumbly. 'Is that a TV you've got there?' I finally understood.
'Uhh no. It's just broken, I'm trying to fix it.' I knew I seemed weird to him. He walked away, and I suddenly felt very ill physically. I got up and started walking to the car, leaving all of our things unguarded. I spotted the car and it seemed to stretch away into the distance, then come rushing back. I felt like I could barely make it to the car. I was completely drained of energy, and I felt very nauseous. I finally made it to the car, opened the door, and fell into the back seat. 'What the fuck?' inquired Mike.
'I don't feel so great, man. I can't move.'
My friends began to panic a little. I didn't care. I was beginning to feel very sleepy. My friends left the car. The heat was unbearable, I took off my shirt and laid across the back seat.  I was hearing screaming voices very loud. They weren't saying anything, just loud primal screams from many voices. I also heard didgeridoos very loudly. I was quite scared and began to wish I was still sleeping at home. I actually fell asleep at one point. I woke up feeling very cold and drenched in sweat. 'I'm actually going to die,' I thought.
My friends came back to the car and tried to make me get up to get water. I replied, 'Fuck off.' They decided that it was best we go back to Mike's house. The thought of him driving us home on his first acid trip terrified me, but I was too out of it to interject.
We got back to his house. I was feeling a little better, but the physical sickness was still there. I came down in the next few hours at his house. I was still feeling out of it when I went to work at 5:00 pm.
I have done mushrooms many times since this occasion. I have never experienced the sickness or had a bad experience since then. I have never tripped as hard since then either. My guess is that I got food poisoning from bacteria on a mushroom or that it was completely imagined. I felt sick long after the affects wore off, so I have to go with the first one.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Etabs to Revit
Create, Update and Remove using Structural Engineering software Etabs
Description
Etabs is a design software for structural engineering. The Etabs data which is export to Excel to generate Revit geometry and size framing appropriately to match the structural engineer's design. The Etabs element id is mapped and placed in a Revit parameter to also update location and sizes in the future.


| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| QueryBuilder
Builder for a Drill query.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| PhysicalOpUnitTestBase |
| SubDirTestWatcher
This is a
TestWatcher which is used to create and delete sub directories before and after unit tests respectively. |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| SubDirTestWatcher
This is a
TestWatcher which is used to create and delete sub directories before and after unit tests respectively. |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| PhysicalOpUnitTestBase |
| SubDirTestWatcher
This is a
TestWatcher which is used to create and delete sub directories before and after unit tests respectively. |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| LogFixture
Establishes test-specific logging without having to alter the global
logback-test.xml file.
|
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| PhysicalOpUnitTestBase |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| PhysicalOpUnitTestBase |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BaseTestQuery
deprecated Use
ClusterTest instead. |
| DrillTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| DrillTest |
| Class and Description |
|---|
| BaseDirTestWatcher
Overview
|
| BaseDirTestWatcher.DirType
An enum used to represent the directories mapped to the dfs.root and
dfs.tmp workspaces respectively.
|
| BaseFixture
Base class for "fixtures." Provides the basics such as the Drill
configuration, a memory allocator and so on.
|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| BufferingQueryEventListener
Drill query event listener that buffers rows into a producer-consumer
queue.
|
| BufferingQueryEventListener.QueryEvent |
| BufferingQueryEventListener.QueryEvent.Type |
| ClientFixture
Represents a Drill client.
|
| ClientFixture.ClientBuilder |
| ClusterFixture
Test fixture to start a Drillbit with provide options, create a client, and
execute queries.
|
| ClusterFixtureBuilder
Build a Drillbit and client with the options provided.
|
| ClusterFixtureBuilder.RuntimeOption |
| ClusterMockStorageFixture |
| ClusterTest
Base class for tests that use a single cluster fixture for a set of
tests.
|
| ConfigBuilder
Builds a
DrillConfig for use in tests. |
| DirTestWatcher
This class is used to create consistently named and safe temp directories for
unit tests.
|
| DrillTest |
| DrillTestWrapper
Encapsulates the options for a Drill unit test, as well as the execution
methods to perform the tests and validation of results.
|
| DrillTestWrapper.TestServices |
| FieldDef
Basic representation of a column parsed from a query profile.
|
| FieldDef.Type |
| FieldDef.TypeHint |
| LegacyOperatorTestBuilder
Deprecated.
Use
OperatorTestBuilder instead. |
| LogFixture
Establishes test-specific logging without having to alter the global
logback-test.xml file.
|
| LogFixture.LogFixtureBuilder
Builds the log settings to be used for a test.
|
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| OperatorFixture.Builder
Builds an operator fixture based on a set of config options and system/session
options.
|
| OperatorFixture.MockFragmentContext
Provide a simplified test-time code generation context that
uses the same code generation mechanism as the full Drill, but
provide test-specific versions of various other services.
|
| OperatorFixture.MockOperatorContext |
| OperatorTestBuilder |
| PhysicalOpUnitTestBase |
| PhysicalOpUnitTestBase.MockExecutorFragmentContext
Note
|
| ProfileParser
Parses a query profile and provides access to various bits of the profile
for diagnostic purposes during tests.
|
| ProfileParser.FragInfo
Information for a fragment, including the operators
in that fragment and the set of minor fragments.
|
| ProfileParser.MinorFragInfo
Information about a minor fragment as parsed from the profile.
|
| ProfileParser.OperatorProfile
Detailed information about each operator within a minor fragment
for a major fragment.
|
| ProfileParser.OperatorSummary
Information about an operator definition: the plan-time information
that appears in the plan portion of the profile.
|
| ProfileParser.TreeVisitor
Visit a tree of operator definitions to support printing,
analysis and other tasks.
|
| QueryBatchIterator
Iterator over batches returned from a query.
|
| QueryBuilder
Builder for a Drill query.
|
| QueryBuilder.PlanMatcher
Collects expected and non-expected query patterns.
|
| QueryBuilder.QuerySummary
Summary results of a query: records, batches, run time.
|
| QueryBuilder.QuerySummaryFuture
The future used to wait for the completion of an async query.
|
| QueryBuilder.VectorQueryReader
VectorQueryReader function interface
|
| QueryResultSet
Returns query results as an iterator over row sets.
|
| QueryRowSetIterator
Converts an incoming set of record batches into an iterator over a
set of row sets.
|
| QueryRowSetReader |
| RestClientFixture
Represents a client for the Drill Rest API.
|
| RestClientFixture.Builder
A builder for the rest client.
|
| SubDirTestWatcher
This is a
TestWatcher which is used to create and delete sub directories before and after unit tests respectively. |
| SubDirTestWatcher.Builder
This is a builder for a
SubDirTestWatcher . |
| TestBuilder |
| TestBuilder.BaselineQueryTestBuilder |
| TestBuilder.CSVTestBuilder |
| TestBuilder.JSONTestBuilder |
| TestBuilder.SchemaTestBuilder |
| TestTools.FileSource |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| OperatorFixture
Test fixture for operator and (especially) "sub-operator" tests.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| DrillTest |
| SubOperatorTest |
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
| Class and Description |
|---|
| BaseTest
Contains patchers that must be executed at the very beginning of test runs.
|
Copyright © 2021 The Apache Software Foundation. All rights reserved.


Presenters and Moderators can draw into presentations and allow this for all users. The default presentation has multiple empty slides
to use as a whiteboard. Moving to a different slide keeps annotations on other slides intact.
The Whiteboard feature can be accessed via a menu on the right side:
Tool
This offers multiple drawing tools. Default is the "pan" tool to move around a zoomed-in presentation (zoom via buttons in bottom right).
Undo
Undo the last action.
Clear
Remove all annotations from the slide.
Multi-User
Allow all users to draw. Everyone's cursor will be visible, so this can also be used to just point to things on a slide.