HTML
CSS
JavaScript
C++
I am a Creative Programmer and Designer with a strong expertise in C/C++ and Data Structures and Algorithms. I currently dabble in Full Stack Web Development particularly in MEAN Stack. I also have some experience in Content Management, Writing and Research Analysis tools.
As a Recent College Graduate, I am (always) Seeking the position of a Full Stack Developer/Software Development Engineer/Analyst to further enhance my organizational worth. Be sure to give me a message in case you have an interesting work or project which i can work on.


2020 Golden Globes host Ricky Gervais' first promotional videos released: 'Is it just what you wanted?'
by Andy SahadeoRicky Gervais is set to host the Golden Globes for the fifth time in January and the first promotional videos have just been released.
Airing during NBC’s coverage of the Macy’s Thanksgiving Day Parade on Thursday, the two short promotional videos show off Gervais in a black tuxedo as he speaks to the camera about hosting the show once again.
GOLDEN GLOBES: RICKY GERVAIS SET TO RETURN AS A HOST FOR FIFTH TIME
Looking dapper in one video, an off-screen voice tells Gervais to “Just say the lines and pour yourself a drink.”
Just as Gervais was about to pour himself a little bit of the bubbly, the comedian looked to the camera and stoically stated, “Hi, I’m Ricky Gervais and I’m hosting the Golden Globes" — before popping the cork and letting the drink spray all over the set.
“Watch out for the camera!” the off-screen voice lamented.
RICKY GERVAIS CALLS OUT LIBERAL ACTIVISTS FOR 'MILKSHAKING' TREND, LIMITING FREE SPEECH
In the other video, Gervais takes a more laid-back stance, but still takes the time to poke fun at hosting the awards show.
“Happy holidays, America. I’m Ricky Gervais and I’m hosting the Golden Globe awards, so there’s your early gift,” he said.
“Is it just what you wanted?” Gervais asked with a sly chuckle.
“No, it’s not, is it?” Gervais asked again as he burst into laughter.
CLICK HERE TO GET THE FOX NEWS APP
Gervais previously hosted the show in 2010, 2011, 2012 and 2016.


Toggle navigation
Schiessel Lab
About
RBP 3D Visualization
About the Schiessel Lab
Description and contact info to be added.


{# {% if socialaccount.providers %}#}
{#
{% blocktrans with site.name as site_name %}Please sign in with one#} {# of your existing third party accounts. Or, sign up#} {# for a {{ site_name }} account and sign in below:{% endblocktrans %}
#} {##} {# #} {##} {# {% include "socialaccount/snippets/login_extra.html" %}#} {##} {# {% endif %}#}
By creating an account, you agree to HomeEdSupply.com's Conditions of Use and Privacy Notice.


| 549 | (A) | Thay Eghtillede to those Olyfauntes that Orrybiłłe were |
| 551 | (C) | Vpon þe olyfauntes he hytte . þat orryble were |
| 545 | (D) | vp-on þe holifauntis he hit þat horrible were |
| 537 | (E) | ¶ Than þe olyfauntes thei hitte . þat oryble were |
| (Ex) | ---- no text ---- | |
| 566 | (L) | Atles on þe olyfauntes þat orible were |
| (P) | ---- no text ---- | |
| 544 | (U) | Than the olifauntes he hit / that horrible were |
| (V) | ---- no text ---- |


Chimney hopes to smoke out a soulmate
Six-year-old Chimney has been described as a “beautiful, solid, love-you-forever type.” One look at his photo and “beautiful” is sure to spring to mind. And Chimney most definitely is tried and true when it comes to affection. But, it does take time for him to reveal his sweet side.
Showing his vulnerability doesn’t come easy. He’s afraid to look at you when he purrs! Chimney just wants to be held and know everything will be all right.
People are to blame for his fear of giving his heart completely. He and his best friend and gorgeous sister, Candle, have had their trust in people shaken time and time again. Initially abandoned with his siblings, they came to ARK and went years with no one offering a home. Then Chimney and Candle were adopted out twice, but had to return to ARK through no fault of their own.
The upheavals and repeated sense of abandonment have surely hurt. How can two such beautiful souls suffer so much bad luck? Are there any steadfast stand-by-you-forever types out there? Someone needs you.
If you are interested in adopting Chimney, email ARK at<EMAIL_ADDRESS>or call 050-1557-2763 Monday to Saturday (bilingual) for more information. Tokyo ARK is an NPO founded by Briton Elizabeth Oliver. It is dedicated to rescuing and rehoming abandoned animals. All animals are vaccinated, neutered and microchipped. Prospective owners are requested to undergo a screening process. Web: www.arkbark.net
GET THE BEST OF THE JAPAN TIMES IN FIVE EASY PIECES WITH TAKE 5
JOIN THE CONVERSATION


A collection of functions for creating high-level graphics,
performing raster-based analysis, processing MODFLOW-based models,
selecting subsets using a genetic algorithm, creating interactive web maps,
accessing color palettes, etc. Used to support packages and scripts written
by researchers at the United States Geological Survey (USGS)
Idaho National Laboratory (INL) Project Office.
| Version: |
0.4.4 |
| Depends: |
R (≥ 3.4.0) |
| Imports: |
checkmate, data.table, GA, graphics, grDevices, htmltools, htmlwidgets, igraph, knitr, leaflet, methods, parallel, raster, rgdal, rgeos, scales, sp, stats, tools, xtable |
| Suggests: |
devtools, dichromat, doParallel, doRNG, githubinstall, gstat, httr, roxygen2, testthat |
| Published: |
2018-11-08 |
| Author: |
Jason C. Fisher [aut, cre] |
| Maintainer: |
Jason C. Fisher <jfisher at usgs.gov> |
| BugReports: |
https://github.com/USGS-R/inlmisc/issues |
| License: |
CC0 |
| Copyright: |
This software is in the public domain because it contains
materials that originally came from the United States
Geological Survey, an agency of the United States Department of
Interior. |
| URL: |
https://github.com/USGS-R/inlmisc |
| NeedsCompilation: |
yes |
| Citation: |
inlmisc citation info |
| Materials: |
README NEWS |
| CRAN checks: |
inlmisc results |


{{project.name}}
{{project.company}}
{{tag}}
{{ project.company }}
{{ $ctrl.overlayProject.description }}
For more information please click here.
Skills used {{tag}}


This repository holds the TypeScript source code of the angular.io quickstart, the foundation for most of the documentation samples and potentially a good starting point for your application.
It's been extended with testing support so you can start writing tests immediately.
This is not the perfect arrangement for your application. It is not designed for production. It exists primarily to get you started quickly with learning and prototyping in Angular
We are unlikely to accept suggestions about how to grow this QuickStart into something it is not. Please keep that in mind before posting issues and PRs.
From time to time the QuickStart will be enhanced with support for new features or to reflect changes to the official Style Guide.
You can update your existing project to an up-to-date QuickStart by following these instructions:
main.ts
file onto src/app/main.ts
in the new projectapp
folder into src/app
src/app/main.ts
if you have one (we now use src/main.ts
instead)index.html
, styles.css
and tsconfig.json
into src/
e2e/
folder into e2e/
.git
folder into your new project's rootNow you can continue working on the new project.
Node.js and npm are essential to Angular development.
Get it now if it's not already installed on your machine.
Verify that you are running at least node v4.x.x
and npm 3.x.x
by running node -v
and npm -v
in a terminal/console window.
Older versions produce errors.
We recommend nvm for managing multiple versions of node and npm.
Clone this repo into new project folder (e.g., my-proj
).
git clone https://github.com/angular/quickstart my-proj
cd my-proj
We have no intention of updating the source on angular/quickstart
.
Discard the .git
folder..
rm -rf .git # OS/X (bash)
rd .git /S/Q # windows
You can quickly delete the non-essential files that concern testing and QuickStart repository maintenance
(including all git-related artifacts such as the .git
folder and .gitignore
!)
by entering the following commands while in the project folder:
xargs rm -rf < non-essential-files.osx.txt
rm src/app/*.spec*.ts
rm non-essential-files.osx.txt
for /f %i in (non-essential-files.txt) do del %i /F /S /Q
rd .git /s /q
rd e2e /s /q
You could start writing code now and throw it all away when you're done. If you'd rather preserve your work under source control, consider taking the following steps.
Initialize this project as a local git repo and make the first commit:
git init
git add .
git commit -m "Initial commit"
Recover the deleted
.gitignore
from the QuickStart repository if you lost it in the Delete non-essential files step.
Create a remote repository for this project on the service of your choice.
Grab its address (e.g. https://github.com/<my-org>/my-proj.git
) and push the local repo to the remote.
git remote add origin <repo-address>
git push -u origin master
See npm and nvm version notes above
Install the npm packages described in the package.json
and verify that it works:
npm install
npm start
Doesn't work in Bash for Windows which does not support servers as of January, 2017.
The npm start
command first compiles the application,
then simultaneously re-compiles and runs the lite-server
.
Both the compiler and the server watch for file changes.

We've captured many of the most useful commands in npm scripts defined in the package.json
:
npm start
- runs the compiler and a server at the same time, both in "watch mode".npm run build
- runs the TypeScript compiler once.npm run build:w
- runs the TypeScript compiler in watch mode; the process keeps running, awaiting changes to TypeScript files and re-compiling when it sees them.npm run serve
- runs the lite-server, a light-weight, static file server, written and maintained by
John Papa and
Christopher Martin
with excellent support for Angular apps that use routing.Here are the test related scripts:
npm test
- compiles, runs and watches the karma unit testsnpm run e2e
- compiles and run protractor e2e tests, written in Typescript (*e2e-spec.ts)The QuickStart documentation doesn't discuss testing. This repo adds both karma/jasmine unit test and protractor end-to-end testing support.
These tools are configured for specific conventions described below.
It is unwise and rarely possible to run the application, the unit tests, and the e2e tests at the same time. We recommend that you shut down one before starting another.
TypeScript unit-tests are usually in the src/app
folder. Their filenames must end in .spec.ts
.
Look for the example src/app/app.component.spec.ts
.
Add more .spec.ts
files as you wish; we configured karma to find them.
Run it with npm test
That command first compiles the application, then simultaneously re-compiles and runs the karma test-runner. Both the compiler and the karma watch for (different) file changes.

Test-runner output appears in the terminal window.
We can update our app and our tests in real-time, keeping a weather eye on the console for broken tests.
Karma is occasionally confused and it is often necessary to shut down its browser or even shut the command down (Ctrl-C
) and
restart it. No worries; it's pretty quick.
E2E tests are in the e2e
directory, side by side with the src
folder.
Their filenames must end in .e2e-spec.ts
.
Look for the example e2e/app.e2e-spec.ts
.
Add more .e2e-spec.js
files as you wish (although one usually suffices for small projects);
we configured Protractor to find them.
Thereafter, run them with npm run e2e
.
That command first compiles, then simultaneously starts the lite-server
at localhost:8080
and launches Protractor.
The pass/fail test results appear at the bottom of the terminal window.
A custom reporter (see protractor.config.js
) generates a ./_test-output/protractor-results.txt
file
which is easier to read; this file is excluded from source control.


AptHunt Forgot Password
{% from "security/_macros.html" import render_field_with_errors, render_field %}
{{ forgot_password_form.hidden_tag() }} {{ render_field_with_errors(forgot_password_form.email, class_="form-control") }} {{ render_field(forgot_password_form.submit, class_="waves-effect waves-light btn btn-default") }}
Login


CPH can acquire replacement values from other HTTP responses by issuing a configured request prior to modifying the current HTTP message.
Consider, for example, a mechanism similar to some anti-CSRF tokens:
- Client requests page
- Server responds with page + unique value
- Client must submit its next request with that unique value
To acquire a value from the response of another HTTP request:
- Either...
- Find the desired HTTP request in Burp Suite, give it a right-click, and choose Send to CPH; or
- Select the appropriate drop-down option in step 3 within the Parameter handling pane and paste a raw HTTP request in the left pane.
- Use the Issue button to confirm that the configured HTTP request will yield the desired response;
- Configure an appropriate regular expression to extract the desired value from that response.
Subsequent requests within scope and containing targeted matches will cause CPH to automatically issue the tab's configured request in order to extract the modification value from its response.


Update: 6 April 2021
The Processing files are now fixed and functional :)
Post: sometime in 2016/2017
Eh... Unfortunately I was not able to recover my second project. I will make another attempt back in Sydney, but no guarantees can be made.
Three projects. First programming assignments in a language that is relatively easy for the peeps to learn and create relatively amazing stuff. Pretty straightforward. No assumed knowledge required. And so, we created and were required to document our process step by step. Showcasing what we have created and putting our content on a peepproject website, which as far as I recall, was designed for the sole purpose of our unit.
My problem was, that I didn't employ more advanced code. No arrays and more compelling solutions. I just had an idea that had to defend itself against the tutors reviewing our works. None of us actually learned in the end how well we did in each of our assignments, for which most of us had pretences against the tutors. Yet, I received a credit.


Week 1 of research in Leeds.
What the prototype is
Most of the users would have failed the Verify journey due to a lack of confidence online and uncertainty with the role of private companies in the journey. Participants were confused as to what information the companies held on them and what they were providing as well as why this process could not be conducted by the government. There was additional concern about this journey in the context of the invitation letter question and several users mentioned they might call up to request an invitation. Other issues included the need for clarification of certain points, such as around length of stay in hospital and marital status, while if they were entering an email they would expect a confirmation that the process was completed which would offer extra reassurance that everything had been done correctly and their claim had been received.


WITNESS LIST Elections Committee (Subcommittee on DISABLED VOTING) March 24, 1999-2:00P HB 1053 For: HARRINGTON, JAMES C. (Self and TEXAS CIVIL RIGHTS PROJECT) Against: PEREZ, J.R. (Self and THE TEXAS ASSOCIATION OF ELECTION ADMINISTRATORS) On: HANSHAW, ELIZABETH (SEC. OF STATE) SIRVELLO, TONY J. (Self and BEVERLY J. KAUFMAN; HARRIS COUNTY CLERK) Registering, but not testifying: For: WESTBROOK, REDGE (COALITION OF TEXANS WITH DISABILITIES) HB 1545 For: HARRINGTON, JAMES C. (TEXAS CIVIL RIGHTS PROJECT) Registering, but not testifying: For: WESTBROOK, REDGE (COALITION OF TEXANS WITH DISABILITIES) HB 1546 For: HARRINGTON, JAMES (Self and TEXAS CIVIL RIGHTS PROJECT) On: SIRVELLO, TONY J. (Self and BEVERLY B. KAUFMAN; HARRIS COUNTY CLERK) Registering, but not testifying: For: WESTBROOK, REDGE (COALITION OF TEXANS WITH DISABILITIES)


Parallelism-resistant Proof-of-Work and first Novel Proof-of-Burn Implementation
Slimcoin is a novel and experimental cryptocurrency created in 2014. It is the first known coin that uses the Proof of Burn mechanism to generate blocks. Additionally, it uses Proof of Work and Proof of Stake, making it the first and unique coin with three different block generation mechanisms.
In 2017, we’re alive and kicking, and we’re different from most other “altcoin” communities. We have no hierarchic and centralized structure - so we have no official development team that benefits from dubious pre-mine or insta-mine mechanisms.
All we want is to continue the exciting Proof of Burn experiment. In a few words, Proof of Burn is a mechanism where you get the right to find blocks if you burn coins.
Sounds crazy, huh? It is perhaps easier to understand as a process of virtual mining. We have prepared an simple explanation (ELI5). And it has very interesting economical properties. It is the only mechanism that allows the users to regulate the available supply in a decentralized way.
SLMs received with this address will be used for rewarding feature developers. Amount in Red is the current amount in the address.
SLMs received with this address will be used for awareness raising via giveaways and faucets.


ansible.plugins.lookup package¶
-
class
ansible.plugins.lookup.
LookupBase
(loader=None, templar=None, **kwargs)[source]¶ Bases:
object
-
run
(terms, variables=None, **kwargs)[source]¶ When the playbook specifies a lookup, this method is run. The arguments to the lookup become the arguments to this method. One additional keyword argument named
variables
is added to the method call. It contains the variables available to ansible at the time the lookup is templated. For instance:"{{ lookup('url', 'https://toshio.fedorapeople.org/one.txt', validate_certs=True) }}"
- would end up calling the lookup plugin named url’s run method like this::
- run([‘https://toshio.fedorapeople.org/one.txt‘], variables=available_variables, validate_certs=True)
Lookup plugins can be used within playbooks for looping. When this happens, the first argument is a list containing the terms. Lookup plugins can also be called from within playbooks to return their values into a variable or parameter. If the user passes a string in this case, it is converted into a list.
Errors encountered during execution should be returned by raising AnsibleError() with a message describing the error.
Any strings returned by this method that could ever contain non-ascii must be converted into python’s unicode type as the strings will be run through jinja2 which has this requirement. You can use:
from ansible.module_utils.unicode import to_unicode result_string = to_unicode(result_string)
-
Submodules¶
ansible.plugins.lookup.cartesian module¶
-
class
ansible.plugins.lookup.cartesian.
LookupModule
(loader=None, templar=None, **kwargs)[source]¶ Bases:
ansible.plugins.lookup.LookupBase
Create the cartesian product of lists [1, 2, 3], [a, b] -> [1, a], [1, b], [2, a], [2, b], [3, a], [3, b]
ansible.plugins.lookup.consul_kv module¶
ansible.plugins.lookup.credstash module¶
ansible.plugins.lookup.csvfile module¶
-
class
ansible.plugins.lookup.csvfile.
CSVRecoder
(f, encoding='utf-8')[source]¶ Bases:
object
Iterator that reads an encoded stream and reencodes the input to UTF-8
ansible.plugins.lookup.dict module¶
ansible.plugins.lookup.dig module¶
-
ansible.plugins.lookup.dig.
make_rdata_dict
(rdata)[source]¶ While the ‘dig’ lookup plugin supports anything which dnspython supports out of the box, the following supported_types list describes which DNS query types we can convert to a dict.
Note: adding support for RRSIG is hard work. :)
-
class
ansible.plugins.lookup.dig.
LookupModule
(loader=None, templar=None, **kwargs)[source]¶ Bases:
ansible.plugins.lookup.LookupBase
-
run
(terms, variables=None, **kwargs)[source]¶ Terms contains a string with things to dig for.
The following formats are supported:
Example Note example.com # A record example.com qtype=A # same example.com/TXT # specific qtype example.com qtype=txt # same <IP_ADDRESS>/PTR - # reverse PTR
- shortcut for <IP_ADDRESS>.in-addr.arpa/PTR
example.net/AAAA @nameserver - # query specified server
- can be comma-sep list of names/addresses
... flat=0 # returns a dict; default is 1 == string
-
ansible.plugins.lookup.dnstxt module¶
ansible.plugins.lookup.env module¶
ansible.plugins.lookup.etcd module¶
-
class
ansible.plugins.lookup.etcd.
Etcd
(url='http://<IP_ADDRESS>:4001', version='v1', validate_certs=True)[source]¶ Bases:
object
ansible.plugins.lookup.file module¶
ansible.plugins.lookup.fileglob module¶
ansible.plugins.lookup.first_found module¶
ansible.plugins.lookup.flattened module¶
ansible.plugins.lookup.hashi_vault module¶
ansible.plugins.lookup.indexed_items module¶
ansible.plugins.lookup.ini module¶
ansible.plugins.lookup.inventory_hostnames module¶
ansible.plugins.lookup.items module¶
ansible.plugins.lookup.lines module¶
ansible.plugins.lookup.list module¶
ansible.plugins.lookup.nested module¶
ansible.plugins.lookup.password module¶
-
class
ansible.plugins.lookup.password.
LookupModule
(loader=None, templar=None, **kwargs)[source]¶
ansible.plugins.lookup.pipe module¶
ansible.plugins.lookup.random_choice module¶
ansible.plugins.lookup.redis_kv module¶
ansible.plugins.lookup.sequence module¶
-
class
ansible.plugins.lookup.sequence.
LookupModule
(loader=None, templar=None, **kwargs)[source]¶ Bases:
ansible.plugins.lookup.LookupBase
sequence lookup module
Used to generate some sequence of items. Takes arguments in two forms.
The simple / shortcut form is:
[start-]end[/stride][:format]As indicated by the brackets: start, stride, and format string are all optional. The format string is in the style of printf. This can be used to pad with zeros, format in hexadecimal, etc. All of the numerical values can be specified in octal (i.e. 0664) or hexadecimal (i.e. 0x3f8). Negative numbers are not supported.
Some examples:
5 -> [“1”,”2”,”3”,”4”,”5”] 5-8 -> [“5”, “6”, “7”, “8”] 2-10/2 -> [“2”, “4”, “6”, “8”, “10”] 4:host%02d -> [“host01”,”host02”,”host03”,”host04”]The standard Ansible key-value form is accepted as well. For example:
start=5 end=11 stride=2 format=0x%02x -> [“0x05”,”0x07”,”0x09”,”0x0a”]This format takes an alternate form of “end” called “count”, which counts some number from the starting value. For example:
count=5 -> [“1”, “2”, “3”, “4”, “5”] start=0x0f00 count=4 format=%04x -> [“0f00”, “0f01”, “0f02”, “0f03”] start=0 count=5 stride=2 -> [“0”, “2”, “4”, “6”, “8”] start=1 count=5 stride=2 -> [“1”, “3”, “5”, “7”, “9”]The count option is mostly useful for avoiding off-by-one errors and errors calculating the number of entries in a sequence when a stride is specified.
ansible.plugins.lookup.shelvefile module¶
ansible.plugins.lookup.subelements module¶
ansible.plugins.lookup.template module¶
ansible.plugins.lookup.together module¶
-
class
ansible.plugins.lookup.together.
LookupModule
(loader=None, templar=None, **kwargs)[source]¶ Bases:
ansible.plugins.lookup.LookupBase
Transpose a list of arrays: [1, 2, 3], [4, 5, 6] -> [1, 4], [2, 5], [3, 6] Replace any empty spots in 2nd array with None: [1, 2], [3] -> [1, 3], [2, None]


{% extends 'index.html' %} {% block title %} Infinite Arbitrary Base Conversion Calculator {% end %} {% block main %}
Examples:
This is a form to convert numbers in arbitrary bases with no limits in integers. The computation is done on the server side.
It uses the algorithm described in here except rindex
is used instead for duplicate letters such as extra 0.
Inspired by this JavaScript implementation.


{% extends "base.html" %} {% import "bootstrap/wtf.html" as wtf %} {% block title %}AllynH - Vault{% endblock %} {% block page_content %}
Welcome, {{ character }}!


Recently Viewed
CCJ textbook
Graphics Card (used)
Physics book
SAT guide
Power Beats New
Used Dresser
A LOT of MtG cards
Signed Destinys Child card
CCJ 2 Electric Boogaloo
Popular
A coffee maker maybe?
XBOX 360 GAMES
P5 bb
Famboyant Homocide's Mountain Retreat
Couch
Blah Blah This is long and stuff
Blah Blah This is long and stuff
Blah Blah This is long and stuff
Blah Blah This is long and stuff


@import play.twirl.api.HtmlFormat @import views.html.common.page.govukTemplate @import components.common.auth.SpireAuthManager @this(spireAuthManager: SpireAuthManager) @(htmlTitle: String, propositionHeading: Html = Html("License controlled items and services"), pageHead: Option[Html] = None)(content: Html) @head = { @pageHead } @bodyEnd = { } @propositionHeadingHtml = {
All content is available under the " + "Open Government Licence v3.0," + " except where otherwise stated
"), crownCopyrightMessage = None, includeUploadScripts = true )(content)


Page 1 of 1
So let's hear your thoughts
Posted:
Tue Jan 09, 2007 10:49 am
by Karl G.
I think making map model "layers" in order to put roofs on things is the best way to go. However, I've found that this adds an interesting opportunity--even more easily, I can add a second layer of map to the world so that houses could have two stories, there could be little hills, etc! What do you think of this idea? I'm not sure how the look would work, but I'm just wondering if this interests anyone as much as it does me
Posted:
Tue Jan 09, 2007 2:43 pm
by Joe M.
sounds interesting, but how would the hills work? It seems that with layers, the incline would be difficult to make work. Can't fight on a hill's slope if there are two parallel planes as the only layers to the world...as far as two-story houses (or dungeons *not* in the mts) goes, though, sounds like it'll work fine.
Posted:
Tue Jan 09, 2007 2:55 pm
by Karl G.
I would think that there would be no interaction between the levels; you would have to be on the same level to fight. The slopes would simply be walls that are sloped up to the next level, in which you can't stand.
Posted:
Tue Jan 09, 2007 3:11 pm
by Serenity
if you want 2 story anything in a xenimus style game youll need to have a warp point to a new dungeon type thing
Posted:
Tue Jan 09, 2007 3:48 pm
by 9sam1
yea layers and stuff are good. was just bout to suggest it lol. cause without them you cant like put the books and tables and stuff.
Posted:
Tue Jan 09, 2007 3:49 pm
by Karl G.
Yep!
Posted:
Tue Jan 09, 2007 3:58 pm
by 9sam1
for the next you need to spread the models out so its easier to choose which one ya want . also make it highlited when you click it so you know if you selected it. it takes me like 10 trys to pick some models lol.
Posted:
Tue Jan 09, 2007 5:01 pm
by Karl G.
Which models in particular? The walls?
Posted:
Tue Jan 09, 2007 7:13 pm
by 9sam1
A ton seem to be like that. there all smushed together. like the armor sign is like on a door and stuff. i think the best thing to do is to spread them out and add it so when you choose something it will highlight it.
Posted:
Tue Jan 09, 2007 11:30 pm
by Karl G.
oh yeah. The arrangements aren't quite finished yet so I haven't spaced things quite right.


| Methods Summary | ||
|---|---|---|
public
|
||
public
|
||
public
|
||
public
|
||
public
|
||
public
|
||
public
|
||
public
|
||
public
|
||
public
|
| Methods inherited from Koren\ErplyBooks\Response\Response |
|---|
__construct() ,
getError() ,
__call()
|
| Properties Summary | ||
|---|---|---|
protected
array
|
$items
Items
|
#
array (
)
|
| Properties inherited from Koren\ErplyBooks\Response\Response |
|---|
$response ,
$body ,
$error
|


All The Heterosexual Nonsense I Was Forced To Endure During Episode 10 Of ‘The Bachelorette’
by Rebecca ShawHello, and welcome to Junkee’s recaps of The Bachelorette Australia, where we watch episodes of The Bachelorette Australia and try to pretend we’re OK with all the hetero nonsense we see in front of us.
Hello angels! It’s me, Charlie. Just kidding, it’s me, Rebecca. I’m sorry I lied and said I was Charlie, but also you aren’t Lucy Liu, so we are both disappointing.
Welcome back to: Me, recapping!
The beautiful Leaning Tower of Patrick has been lovely enough to take over recapping duties the last few episodes due to various Lesbian Emergencies that have kept me from you. Patrick is a true ally to the lesbians, and I shall clutch him to my bosom in thanks the next time we hang out.
This meant that Patrick recapped the episode where dear, sweet Ciarran left, and I just want to reiterate that I am absolutely not over it, and I wish he were still here with us today. I hope he’s very happy, running about on a farm with other ex-Bachelorette contestants, or wherever he may be now.
I am thrilled to be back just in time for hometown visits, even though it makes me very uncomfortable to watch!
There’s just something about the Bachelorette or Bachelor taking a person back to their hometown to meet their family, and having it be a big spectacle and very awkward, and having some people be accepting and some be belligerent and disapproving…what could it be reminding me of.

This is the closest any straight person gets to feeling what it’s like to be the gay one bringing home a partner to Christmas dinner.
I can’t really keep up but from what I remember we are going to be visiting the homes of Boring Handsome Carlin, Very Boring Dog Lover Ryan, Husky Voice Pie Man Jackson and Timm. I’m very curious to see the hometown visits and where all these thrilling and fascinating men come from.
Just kidding!!! I’m only excited to see where Timm comes from. Are they going to pull up to a family of wolves, in the forest where Timm was raised as one of their own? Will they be sucked up into a spaceship? Will his family be a travelling theatre troupe where Timm plays a street urchin every night in regional theatres?
The options are endless. As always I’ll be deciding who is the most annoying in this episode, and there are no rules — it could even be YOU!!!!!!!!!!!!!!!!! (No it couldn’t).
LEAST ANNOYING
TIMM
Timm’s family was normal, and his mum was cute, and I love mums!!!!!!!!!!
Timm not only loves his mum, but also loves his best friend’s mum, and has her name tattooed on him
and when they arrived. his friend revealed he now has Timm’s mum’s name tattooed on him.
It was all a bit weird and a bit cute, which is precisely Timm. Also look how huge the drinks are they made that were the size of Angie’s head. I want to marry into this family.
I actually appreciate Timm even more now after this episode. I think in no way is Angie going to pick him at the end, but I do think he is the most genuine and honest one there.

That was probably due to two things. He brought Angie to his dad’s pie business, and in a throwback to the first episode where he presented her with something she couldn’t eat, this time he brought her gluten-free vegan pies.
If anyone out there took me on a date where they made me personalised pies, and in fact they worked in pies, and I could have pies all the time? I would marry them. It was cute! Also, he grew up with three brothers in a football household and found it hard to be vulnerable and open up about his feelings
This is all EXTREMELY relatable to SOME OF US i’m sure, I couldn’t POSSIBLY say WHOM.
I think he’s just like a generic handsome football party Sydney guy, and that isn’t for me whatosever in literally any context, but no hard feelings. Also at one point when Angie was trying to discuss his feelings he said “I was trying to mentalise how I feel about you”, and I just loved it.
MOST ANNOYING
JACKSON (TIMM’S FRIEND) AND JACKSON’S DAD
Oh my god. I am all for friends and family being protective of their loved ones but I hated watching both of these men.
Jackson made it very clear that he is jealous and doesn’t want Timm to end up with Angie, which is a RED FLAG. Dump this guy Timm. He obviously just doesn’t want to lose his party friend, so basically told Angie that Timm is a party guy and is in no way ready to settle down. DOG.
The worst part though was when he was harshly questioning Angie and patronisingly said “Do you have a spark with any of the other three blokes who are trying to crack onta ya?” Like sorry, do you know how the show works?  I’m not in the MOOD.
And then we came to contestant Jackson’s dad, who had a lot of concerns about Angie being a gold-digger, and not being a hard worker, and just wanting to cash in on his family. Unfortunately he is obviously under the impression that instead of running a pie company, he in fact is Logan Roy from the television show Succession.
If you haven’t seen Succession, this is a very funny jokes! It’s a show about a father and his children all basically fighting and scheming over the biggest media company in the entire world.
Jackson’s Dad is under the impression that Angie is going through all of this simply to claw her way into this huge conglomerate pie business. It was all just very very patronising and awful, saying things like “what’s work for you Ange, you don’t know where your next job is coming from?” and “she’s been on two reality shows, we don’t know what her intentions are.”
 THIS IS NOT SUCCESSION.

RYAN
Ryan and Carlin are both extremely boring. And now we know, not only are they extremely boring, but they are both big liars who lie.
Ryan went on and on about how he would nevvvvvvvvvvvvver do The Bachelorette, it’s not his styyyylllllle, and then we find out that in fact he had applied for a different season. That is a very very clearcut lie.
When Angie asked him about it in this episode, he (very lying-ly) started muttering about how he was in a rut at the time and so he applied and didn’t know who the Bachelorette would be, and he hadn’t gone out of his way to do it, he had been asked to audition, and it hadn’t even crossed his mind to tell her when they were discussing it.
LIES LIES LIES. And really really unfortunately, Angie seemed to talk herself into buying it.
Angie said things like that when she was mad she hadn’t taken into account that he hadn’t applied, they’d approached him, and that he hadn’t gone out of his way to apply, etc. But….he still lied, babe.
He explicitly said that he would never do anything like this, except he already had, and that’s not something you forget! He is a liar, and he’s boring, and if he wins i’m going to have a huge tantrum. He then did the most annoying thing of all which is get upset that she might possible think he’s lying….because he lied.
And he brought his brothers into it, and they all were like “it’s baffling that she thinks he’s lying” — um it’s because she lied, bro. So we had different Ryans with varying levels of hair be like “he’s like super honest and would never lie”
Except he DID lie, very explicitly, and then he got upset and his brothers got upset, and made her feel bad for not trusting him! Don’t trust him Angie, love yourself babe.
I accidentally got this screenshot at a horrible time but i’m leaving it because i’m mad at Ryan. Booooooooo Ryan.
Carlin
Carlin was also dishonest! He never mentioned to her that he was super into getting an acting career going, and his brother blew his cover. It’s just a weird thing to be dishonest about, and then when she confronted him he, again, got upset at her for DARING to not trust him.  Angie, babe, please love yourself. I know he has these arms
And he’s pretty when he cries
But like, he’s dishonest and also again soooooooooo boring. But if I HAD to choose between Ryan and Carlin, I guess I would choose Carlin. But I don’t, because I’m not on this show, and I am a lesbian. Yay for me.
NEVER TO ANNOY AGAIN
Pie pie Jackson! The joke there is that Pie Pie could sound like Bye Bye a little bit. So it was like I was saying Bye Bye Jackson. Thank you for joining my comedy masterclass! I think Jackson was never long for this world, and he is going to be absolutely fine as CEO of Pies.
This episode was one of the more annoying episodes that I can remember in life. The only people that didn’t annoy me were Angie, Timm, and Timm’s mum. Everyone else could have gone on the list. If Timm goes home next week, it’s going to be a real struggle for me. And I am the most important person in this scenario. Also unless Ciarran comes back, Angie should pick nobody!
Thanks for joining me on this journey through cities and towns and heterosexual homes. See you next week!
Rebecca Shaw is the co-host of the very regular comedy podcast Bring A Plate. She tweets @brocklesnitch


| Parameter |
Values |
Default |
Type |
Description |
| Name |
'SaperaLT' |
|
string |
Name of the HALCON interface. |
| HorizontalResolution |
1, 2, 4 |
1 |
integer |
Desired horizontal resolution of the camera image:
- 1: Use full resolution.
- 2: Use half resolution.
- 4: Use quarter resolution.
If you want to use other values for the image resolution, set
it via the camera configuration file specified in the CameraType
parameter. Please note that in case of an image width smaller than 8
this parameter is ignored. Also note that the value of 'ImageWidth'
overwrites the value of 'HorizontalResolution', if no configuration
file is set.
|
| VerticalResolution |
1, 2, 4 |
1 |
integer |
Desired vertical resolution of the camera image:
- 1: Use full resolution.
- 2: Use half resolution.
- 4: Use quarter resolution.
If you want to use other values for the image resolution, set
it via the camera configuration file specified in the CameraType
parameter. Please note that in case of an image height smaller than 8
this parameter is ignored. Also note that the value of 'ImageHeight'
overwrites the value of 'VerticalResolution', if no configuration
file is set.
|
| ImageWidth |
0, <width> |
0 |
integer |
Width of the desired image part ('0' stands for the maximum image width). This value has to be equal or smaller than the maximum image
width.
Note that this parameter will be ignored, if a ccf file is set as
'CameraType' parameter.
|
| ImageHeight |
0, <height> |
0 |
integer |
Height of the desired image part ('0' stands for the maximum image height). This value has to be equal or smaller than the maximum image
height. If the current buffer height is smaller than this parameter value
the resulting HALCON image will be resized to the current buffer height.
Note that this parameter will be ignored, if a ccf file is set as
'CameraType' parameter.
|
| StartRow |
<row> |
0 |
integer |
Row coordinate of the upper left pixel within the desired image part.
|
| StartColumn |
<column> |
0 |
integer |
Column coordinate of the upper left pixel within the desired image part.
|
| Field |
--- |
|
|
Ignored. |
| BitsPerChannel |
--- |
|
|
Ignored (the desired pixel depth will be set accordingly to the parameter settings in the camera configuration file).
|
| ColorSpace |
'default', 'gray', 'raw', 'rgb', 'rgbx', 'yuv' |
'default' |
string |
Using a frame grabber board: If not set to 'rgbx', the parameter is ignored and the desired pixel depth will be set accordingly to the parameter
settings in the camera configuration file. Otherwise, a 4-channel image will
be created, see also the parameter 'pixel_arrangement'. Please note that a
4-channel RGB image looks like a gray value image in HDevelop as by default
only the first image channel will be displayed.
Using a GigE Vision camera: The color space for the resulting HALCON
image will be automatically set. Only with Genie TS Framework the selected
color space value will be set. The value 'rgbx' is only possible for frame
grabber boards.
|
| Generic |
['','num_buffers=<num>', 'cam_params=0'] |
-1 |
mixed |
With the Generic parameter some important values can be set before the camera is initialized. Note that the parameter names including the values must be
strings, e.g., 'num_buffers=5' sets the number of buffers to 5.
The following parameters are available:
- num_buffers:
Number of buffers used for the image acquisition. Note that with default
buffer cycle mode one buffer is used as trash, so the effective number of
available buffers for images is num_buffers - 1.
- cam_params:
Flag to enable access to the GenICam parameters of the connected framegrabber
camera if available. Framegrabbers are not aware of any changes on the camera
configuration at runtime because of this the following limitation need to
be consider:
- The parameters 'Width', 'Height', 'OffsetX' and 'OffsetY' are always mark
as read only. Please use 'image_part' instead.
- When changing the pixel format of the camera, the buffers are not
recreated. A correct configuration file for the framegrabber must be provided,
otherwise a incorrect images might be acquired.
Note:It is possible that changing some of the parameters can stop the
interface and the framegrabber from working correctly. Use at your own risk!
|
| CameraType |
'<configuration_file>', '' |
'' |
string |
Specify the name (including the full path name) of the desired camera configuration file, i.e., the .ccf file. A camera configuration file can be
created with the help of the camera configuration tool CamExpert;
using that tool you can test and save an appropriate configuration for your
camera and pass the complete file name (e.g.,
'C:\Program Files\Teledyne DALSA\Sapera\CamFiles\User\myCameraConfig.ccf').
The configuration file is needed to connect to the camera and receive all
basic parameters like width/height or pixel format of the image.
For GigE Vision cameras it is not necessary to use a camera configuration
file (leave empty string ''). Then the needed values are queried directly
from the camera and the current settings are used.
Note that the value of the parameters 'HorizontalResolution',
'VerticalResolution', 'ImageWidth', or 'ImageHeight' may overwrite the
current settings of the camera, if no configuration file is set.
|
| Device |
'default', 'Genie_C640_1', 'Genie_C640-S3_1', 'Genie_M640_1', 'Genie_M640-S3_1', 'Genie_HM_640_1', 'Genie_C1024_1', 'Genie_M1024_1',
'Genie_HM1024_1', 'Genie_C1400_1', 'Genie_C1400-S3_1', 'Genie_M1400_1',
'Genie_M1400-S3_1', 'Genie_HM1400_1', 'Genie_TS-M2500', 'PC2-CamLink_1',
'Spyder_GigE_Colour_Camera_1', 'X64_1', 'X64-CL_iPro_1',
'X64-CL_Dual_1', 'X64-LVDS_1', 'Xcelera-CL_PX4_1', 'Xtium-CL_PX4',...
|
'0' |
string |
The name of one of the desired Teledyne DALSA image acquisition device. If you have more than one device with the same name, the number at the end of
the device name is counted upwards to access each device separately. If
'default' is specified, the interface will refer to the first device that
can be found. A list of available devices can be queried by calling
info_framegrabber(.., 'device', ...).
Please note that in case of using a GigE Vision camera without setting a
camera configuration file in parameter 'camera_type' the value 'default'
cannot be used as device name. A specific device name has to be set.
|
| Port |
-1, 0, 1, 2, 3, 4, 5 |
-1 |
integer |
Specifies the number of the desired camera port (analog boards only). If -1 is selected, the port will be selected from the configuration file.
In case of GigE Vision cameras this parameter will be ignored. In case of
digital frame grabbers, the correct port has to be set in the camera
configuration file (CCF). Note that the parameter 'port' corresponds to
the Camera Selector (or parameter CORACQ_CAMSEL) of Sapera LT. When using
a digital board this is not equal to the physical connector index.
|
| LineIn |
--- |
|
|
Ignored. |
| Parameter |
Values |
Default |
Type |
Kind |
Description |
| 'available_callback_types' |
['<callback_type>'] |
|
string |
dynamic |
Query all callback types which are supported by this interface. |
| 'available_param_names' |
['<parameters>'] |
|
string |
dynamic |
In case of a Genie GigEVision camera the available parameters supported by this camera are returned. If a framegrabber board is used a list of
all the available static parameters is returned and if the connected
camera supports GenICam and 'cam_params' is set to 1 the interface will
try to query the available parameters from the camera also.
Note: If using multiple cameras connected to the same board, the list
of available parameters will correspond only to the open camera.
|
| 'bits_per_channel' |
'<default>' |
8 |
integer |
pre-defined |
The value is not used, so a default value is returned. |
| 'buffer_cycle_mode' |
'asynchronous', 'next_empty', 'off', 'synchronous', 'synchronous_next_empty_with_trash', 'synchronous_with_trash'
|
'synchronous_next_empty_with_trash' |
string |
dynamic |
Allows you to select the used mode for buffer cycling. As default a mode with a trash buffer is used, which means that the number of image buffers is
num_buffers - 1. If another cycle mode is set, acquisition is stopped and
re-started. Note that an Xfer must exist to change the buffer cycle mode, which
means that you have to call grab_image_start, grab_image, grab_image_async, or
enable continuous_grabbing.
The following modes can be set, but not every hardware supports all modes:
| cycle mode |
description |
| asynchronous |
Always transfer to the next buffer regardless of its state. |
| synchronous |
If next buffer is empty, then transfer to next buffer, otherwise, transfer to current buffer. |
| synchronous_with_trash |
If next buffer is empty, then transfer to the next buffer, otherwise,
transfer to the trash buffer. Repeat transferring to the trash buffer
as long as the next buffer is full. |
| off |
Always transfer to the current buffer. |
| next_empty |
If next buffer is empty, then transfer to next buffer, otherwise,
transfer to next empty buffer in the list. If all buffers are full,
then transfer to current buffer. |
| synchronous_next_empty_with_trash |
If next buffer is empty, then transfer to next buffer, otherwise,
transfer to next empty buffer in the list. If all buffers are full,
then transfer to trash buffer. Repeat transferring to the trash
buffer as long as there is no empty buffer in the list. |
CorXferGetPrm -> CORXFER_PRM_CYCLE_MODE
|
| 'buffer_time_stamp' |
|
0 |
integer |
dynamic |
Internal time stamp of the current SaperaLT buffer. CorBufferGetPrm -> CORBUFFER_PRM_COUNTER_STAMP |
| 'cam_params' |
0, 1 |
|
integer |
|
Flag to enable access to the GenICam parameters of the connected framegrabber camera if available. Framegrabbers are not aware of any
changes on the camera configuration at runtime because of this the following
limitation need to be consider:
- The parameters 'Width', 'Height', 'OffsetX' and 'OffsetY' are always mark
as read only. Please use 'image_part' instead.
- When changing the pixel format of the camera, the buffers are not
recreated. A correct configuration file for the framegrabber must be
provided, otherwise an incorrect images might be acquired.
Note:It is possible that changing some other parameters will stop the
interface and the framegrabber of working correctly. Use at your own
risk!
|
| 'camera_type' |
'<configuration_file>', '' |
'' |
string |
pre-defined |
Current camera type. |
| 'color_space' |
'gray', 'raw', 'rgb', 'rgbx', 'yuv' |
'gray' |
string |
pre-defined |
Desired color space and thus the number of image channels of the resulting HALCON image.
|
| 'continuous_grabbing' |
'disable', 'enable' |
'disable' |
string |
pre-defined |
If the continuous grabbing mode is enabled, the camera grabs all the time. In this mode the operator
grab_image does not grab synchronously, but behaves similar to
grab_image_async. Using this mode you can achieve full frame rate. If the
continuous grabbing mode is disabled, the camera is set to single frame
capture.
|
| 'device' |
'<device_id>' |
'0' |
string |
dynamic |
Current device. |
| 'field' |
'<default>' |
'default' |
string |
pre-defined |
The value is not used, so a default value is returned. |
| 'generic' |
['','num_buffers=<num>', 'cam_params=0'] |
-1 |
mixed |
pre-defined |
Values of the Generic parameter. |
| 'grab_timeout' |
<milliseconds> |
5000 |
integer |
pre-defined |
Current grab timeout in milliseconds. |
| 'horizontal_resolution' |
<resolution> |
1 |
integer |
pre-defined |
Current value of horizontal resolution. |
| 'image_available' |
0, 1 |
|
integer |
dynamic |
Status of the last asynchronous grab command. The value 1 means that the image is already acquired and thus can be fetched by grab_image_async without
delay. Note that this parameter is especially useful in combination with
external triggering.
|
| 'image_height' |
<height> |
0 |
integer |
dynamic |
Height of the image. |
| 'image_part' |
[<row1, col1, row2, col2>] |
|
integer |
dynamic |
Allows you to crop a defined part of the image. In order to define a rectangular region for image acquisition, the point on the left top and
the point on the right bottom have to be entered. If -1 is passed to every
value, the values will be set to their default values. If a value exceeds
the image size, it is set to the maximum allowable value.
|
| 'image_width' |
<width> |
0 |
integer |
dynamic |
Width of the image. |
| 'internal_device_pointer' |
'<handle>' |
|
string |
dynamic |
Returns the internal SDK handle of the current acquisition device which enables direct device access. Use at your own risk!
|
| 'line_in' |
<default> |
-1 |
integer |
pre-defined |
The value is not used, so a default value is returned. |
| 'line_number' |
0, 1, ... <image_height> |
0 |
integer |
dynamic |
Allows you to select the line for the line_end callback to be signaled. This parameter has to be set before activating the callback.
|
| 'multiple_image_num' |
1, 2, 3 |
1 |
integer |
pre-defined |
Special grabbing mode for line scan cameras. |
| 'name' |
'SaperaLT' |
|
string |
pre-defined |
Name of the HALCON interface. |
| 'num_buffers' |
<number> |
3 |
integer |
pre-defined |
Number of buffers used for the image acquisition. Note that with default buffer cycle mode one buffer is used as trash, so the effective number of
available buffers for images is num_buffers - 1.
|
| 'port' |
-1, 0, 1, 2, 3, 4, 5 |
|
integer |
pre-defined |
Current port number. |
| 'revision' |
'<revision>' |
|
string |
pre-defined |
Revision number of the SaperaLT interface. |
| 'start_async_after_grab_async' |
'disable', 'enable' |
'enable' |
string |
pre-defined |
Status of 'start_async_after_grab_async'. |
| 'start_column' |
<column> |
0 |
integer |
pre-defined |
Returns the current start column of the HALCON image. |
| 'start_row' |
<row> |
0 |
integer |
pre-defined |
Returns the current start row of the HALCON image. |
| 'trash_counter' |
0, 1, 2, ... |
|
integer |
dynamic |
Number of images, which could not be fetched (boards only). |
| 'vertical_resolution' |
<resolution> |
1 |
integer |
pre-defined |
Current value of vertical resolution. |
| 'volatile' |
'disable', 'enable' |
'disable' |
string |
pre-defined |
Grayscale only. In the volatile mode the two image acquisition interface buffers are used directly to store HALCON images. This is the
fastest mode avoiding to copy raw images in memory. However, be aware that
older images are overwritten again and again as a side-effect. Thus, you
can only process one image while you grab another image. Older images are
invalid!
|
The parameters below are only for Teledyne DALSA frame grabber boards.
| Parameter |
Values |
Default |
Type |
Description |
| 'bayer_hardware_decoder_method' |
1, 2, 3, 4, 5, 7 |
|
integer |
Method for data conversion of the hardware Bayer decoder. |
| 'bayer_software_decoder' |
'disable', 'enable' |
|
string |
Enables or disables the software Bayer decoder. The setting takes effect with the next call of 'grab_image' or 'grab_image_async'.
|
| 'bayer_software_decoder_alignment' |
'bg_gr', 'gb_rg', 'gr_bg', 'rg_gb' |
'gb_rg' |
string |
Alignment of the upper left 2x2 square of the camera`s Bayer scheme. |
| 'bayer_software_decoder_format' |
'RGB888', 'RGB8888', 'RGB101010' |
'RGB888' |
string |
Output buffer format of the software Bayer decoder. 'RGB101010' is only available, if the input format is MONO16!
|
| 'bayer_software_decoder_method' |
1, 2, 3 |
1 |
integer |
Method for data conversion of the software Bayer decoder.
- method 1: Fast, based on bilinear interpolation.
- method 2: Advanced, preserves image edges. Works only well, if the image
has a strong green content.
- method 3: Advanced, preserves image edges, independent of image green
content.
|
| 'bayer_software_decoder_whitebalance' |
[<wb_red, wb_green, wb_blue>] |
[1.0, 1.0, 1.0] |
integer |
White balance gain for each color channel. You always have to set all three values (floating point). If all values are set to 1.0, no white
balance is used for the software Bayer conversion.
|
| 'bit_ordering' |
'9_10', 'inv', 'msb_10', 'msb_12', 'std' |
|
string |
Digital bit ordering of the camera.
- 9_10: Video data bits 9 and 10 are swapped with bits 0 and 1 (required
by some 10-bit digital cameras).
- inv: The video data bits are inverted (logical NOT).
- msb_10: Video data bits 0-7 connect to the acquisition device input bits
2-9 (required by some 8-bit digital cameras).
- msb_12: Video data bits 4-11 are directed to the input bits 0-7 of the
acquisition device (required by some 12-bit digital cameras).
- std: Standard digital bit ordering.
|
| 'brightness' |
<brightness> |
|
integer |
Brightness of the video signal. Represents the percentage of brightness to add or subtract to the composite video signal (analog only).
|
| 'brightness_blue' |
<brightness_blue> |
|
integer |
Brightness of the blue video signal. Represents the percentage of brightness to add or subtract to the blue video signal
(analog only).
|
| 'brightness_green' |
<brightness_green> |
|
integer |
Brightness of the green video signal. Represents the percentage of brightness to add or subtract to the green video signal
(analog only).
|
| 'brightness_red' |
<brightness_red> |
|
integer |
Brightness of the red video signal. Represents the percentage of brightness to add or subtract to the red video signal
(analog only).
|
| 'cam_reset' |
'disable', 'enable' |
|
string |
Enables or disables the reset pulse to the camera. You must have set the signal properties and the method first.
|
| 'cam_reset_delay' |
<microseconds> |
|
integer |
Reset pulse delay (in microseconds). After receiving a trigger pulse, the acquisition device will wait this delay before generating the reset pulse.
|
| 'cam_reset_duration' |
1...65535000 |
|
integer |
Duration of the reset pulse. |
| 'cam_reset_signal' |
'active_high', 'active_low' |
|
string |
Defines the reset pulse signal. |
| 'cam_trigger' |
'disable', 'enable' |
|
string |
Enables or disables the frame trigger pulse to the camera (area scan only).
|
| 'cam_trigger_delay' |
<microseconds> |
|
integer |
Represents the delay (in microseconds) the acquisition device will wait, before generating the trigger pulse (external, internal or software).
|
| 'cam_trigger_duration' |
<duration> |
|
integer |
The effect of this value differs addicted to the selected method. |
| 'cam_trigger_method' |
1, 2 |
|
integer |
Trigger method of the camera, see Sapera LT documentation for more details.
|
| 'cam_trigger_signal' |
'active_low', 'active_high' |
|
string |
Camera trigger signal. |
| 'contrast' |
<contrast> |
|
integer |
Contrast of the video signal. Represents the percentage of contrast to be applied to the composite video signal (analog only). Step:
1000 (1%).
|
| 'contrast_blue' |
<contrast_blue> |
|
integer |
Contrast of the blue video signal. Represents the percentage of contrast to be applied to the blue video signal (analog only).
Step: 1000 (1%).
|
| 'contrast_green' |
<contrast_green> |
|
integer |
Contrast of the green video signal. Represents the percentage of contrast to be applied to the green video signal (analog
only). Step: 1000 (1%).
|
| 'contrast_red' |
<contrast_red> |
|
integer |
Contrast of the red video signal. Represents the percentage of contrast to be applied to the red video signal (analog only). Step:
1000 (1%).
|
| 'decimate_count' |
<count> |
|
integer |
Number of fields or frames to decimate per second. |
| 'decimate_method' |
'disable', 'even', 'field', 'frame', 'odd' |
|
string |
Decimation method, see Sapera LT documentation for more details.
|
| 'do_force_trigger' |
--- |
|
|
Sends a software trigger. |
| 'do_release_gio_handle' |
--- |
|
|
Releases the actual GIO handle. Note that the actual GIO will also be released by close_framegrabber or if another GIO is opened by
the parameter 'do_set_gio_handle'.
|
| 'do_reset_gio' |
--- |
|
|
Resets the actual GIO. |
| 'do_set_gio_handle' |
<device_id> |
0 |
integer |
Opens a GIO input or output port with the used device id. |
| 'ext_frame_trigger' |
'disable', 'enable' |
|
string |
Enables or disables external frame trigger (line scan cameras only). You must have set the signal properties first.
|
| 'ext_frame_trigger_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
External frame trigger level connected to the acquisition device (line scan cameras only).
|
| 'ext_frame_trigger_signal' |
'active_high', 'active_low', 'double_falling', 'double_rising', 'falling', 'rising'
|
|
string |
External frame trigger signal connected to the acquisition device (line scan cameras only). 'double_rising/falling' means to start
the acquisition on the rising/falling edge of trigger 1 and to end on
the rising/falling edge of trigger 2.
|
| 'ext_frame_trigger_source' |
<source> |
0 |
integer |
Physical input source the external line trigger is connected to on the acquisition device, in the case where the acquisition device has
more than one input.
|
| 'ext_line_trigger' |
'disable', 'enable' |
|
string |
Enables or disables external line trigger (line scan cameras only). You must have set the signal properties first.
|
| 'ext_line_trigger_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
External line trigger level connected to the acquisition device (line scan cameras only).
|
| 'ext_line_trigger_signal' |
'falling', 'rising' |
|
string |
External line trigger signal connected to the acquisition device (line scan cameras only).
|
| 'ext_line_trigger_source' |
<source> |
0 |
integer |
Physical input source the external line trigger is connected to on the acquisition device, in the case where the acquisition device has
more than one input.
|
| 'ext_trigger_delay' |
<delay> |
0 |
integer |
Delay of the external trigger signal in units specified by 'ext_trigger_delay_time_base'.
|
| 'ext_trigger_delay_time_base' |
<time_base> |
0 |
integer |
Granularity of units required to adjust the delay of the external trigger signal with 'ext_trigger_delay'.
|
| 'ext_trigger_duration' |
<duration> |
0 |
integer |
Minimum external trigger pulse duration. For details please refer to the 'Sapera Acquisition Parameter' manual.
|
| 'ext_trigger_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
'TTL' |
string |
External trigger level connected to the acquisition device. |
| 'ext_trigger_signal' |
'active_high', 'active_low', 'falling', 'rising' |
'rising' |
string |
External trigger signal connected to the acquisition device. |
| 'ext_trigger_source' |
0, 1, 2 |
0 |
integer |
Physical input source the external trigger is connected to on the acquisition device, in the case where the acquisition device has
more than one input.
|
| 'frame_integration' |
'disable', 'enable' |
|
string |
Enables or disables the frame integration control (area scan cameras only). You must have set the signal properties and the method first.
|
| 'frame_integration_count' |
1...(2^32)-1 |
|
integer |
Number of frames to integrate. |
| 'frame_integration_method' |
1, 2 |
|
integer |
Frame integration method, see Sapera LT documentation for more details.
|
| 'frame_integration_signal' |
'active_high', 'active_low' |
|
string |
Frame integration signal. |
| 'gio_callback_mask' |
<mask> |
|
integer |
If a interrupt callback for the I/Os has to be set, this parameter sets a mask, which pins will cause the callback to be called. To active a pin, the
value of the mask has to be 1 for it. See also set_framegrabber_callback.
|
| 'gio_connector' |
<number> |
|
integer |
Connector number of the I/O block. Only supported by XIO boards.
|
| 'gio_dir_output' |
<io> |
|
integer |
Specifies which I/O blocks are set as output. If a block is set to 1, it is used as output. Otherwise it is an input.
|
| 'gio_dir_tristate' |
<io> |
|
integer |
Specifies which I/O blocks are set as tristate. If a block is set to 1, it is tri-stated.
|
| 'gio_input_level' |
'12 Volts', '24 Volts', '422', 'LVDS', 'LVTTL', 'OPTO', 'TTL' |
|
string |
Input level of the I/O device. Note that this parameter is only available if the I/O block is set as input.
|
| 'gio_output_type' |
'led', 'npn', 'opto', 'pnp', 'ttl', 'lvttl' |
|
string |
Output type of the I/O block. |
| 'gio_state' |
0, 1 |
|
integer |
State of the general I/O pins. If a pin is set to 1, it will be set to TRUE, otherwise FALSE. To set the mask for the pins to set use the parameter
'gio_state_mask'. Note that you have to set ALL pins you want to set
additionally to the mask, which means, e.g., to activate pins 1 and 3, the mask
and the state has to be set to 0x5. This parameter is not supported by all boards.
|
| 'gio_state_mask' |
<mask> |
|
integer |
Mask for setting the state of the general I/O pins. If a pin is set to 1, it can be set via the value of the parameter 'gio_state'.
|
| 'hue' |
<hue> |
|
integer |
Phase change in degrees applied to the hue control (analog composite or Y/C only).
|
| 'int_frame_trigger' |
'disable', 'enable' |
|
string |
Enables or disables internal frame trigger (area scan cameras only). You must have set the trigger frequency first.
|
| 'int_frame_trigger_freq' |
<mHz> |
|
integer |
Internal frame trigger frequency in milli-Hz (area scan cameras only).
|
| 'int_line_trigger' |
'disable', 'enable' |
|
string |
Enables or disables internal line trigger. You must have set the trigger frequency first.
|
| 'int_line_trigger_freq' |
<Hz> |
|
integer |
Internal line trigger frequency in Hz. |
| 'line_integration' |
'disable', 'enable' |
|
string |
Enables or disables the line integration signal pulse to the camera (line scan cameras only). You have to set the signal properties and the method
first.
|
| 'line_integration_duration' |
<microseconds> |
|
integer |
Specifies the line integration pulse width in microseconds (line scan cameras only).
|
| 'line_integration_method' |
1, 2, 3, 4, 7 |
|
integer |
Line integration method, see Sapera LT documentation for more details (line scan cameras only).
|
| 'line_integration_pulse0_delay' |
<microseconds> |
|
integer |
Line integration delay (in microseconds) of pulse 0. After receiving a trigger pulse, the acquisition device will wait this delay before generating the
line integration pulse 0 (line scan cameras only).
|
| 'line_integration_pulse0_duration' |
<microseconds> |
|
integer |
Line integration pulse 0 width (in microseconds) (line scan cameras only). |
| 'line_integration_pulse0_signal' |
'active_high', 'active_low' |
|
string |
Line integration signal of pulse 0 (line scan cameras only). |
| 'line_integration_pulse1_delay' |
<microseconds> |
|
integer |
Line integration delay (in microseconds) of pulse 1. After receiving a trigger pulse, the acquisition device will wait this delay before generating
the line integration pulse 1 (line scan cameras only).
|
| 'line_integration_pulse1_duration' |
<microseconds> |
|
integer |
Line integration pulse 1 width (in microseconds) (line scan cameras only). |
| 'line_integration_pulse1_signal' |
'active_high', 'active_low' |
|
string |
Line integration signal of pulse 1 (line scan cameras only). |
| 'line_integration_time_base' |
'ns', 'pixel_clk' |
|
string |
Time base of line integration signal (line scan cameras only). |
| 'line_trigger' |
'disable', 'enable' |
|
string |
Enables or disables the line trigger signal pulse to the camera (line scan cameras only). Note that this parameter cannot be enabled if
'line_integration' is enabled and vice versa.
|
| 'line_trigger_delay' |
<delay> |
|
integer |
Delay of the line trigger pulse in units specified by 'line_integration_time_base' (line scan cameras only).
|
| 'line_trigger_duration' |
<duration> |
|
integer |
Duration of the line trigger pulse in units specified by 'line_integration_time_base' (line scan cameras only).
|
| 'line_trigger_method' |
1, 2 |
|
integer |
Output method of the line trigger signal pulse (line scan cameras only).
|
| 'linescan_direction' |
'disable', 'enable', 'camera' |
|
string |
Enables or disables the line scan direction (line scan cameras only). If the framegrabber does not support this feature, but the camera does,
it is possible to attempt to enable direction change directly into the
camera by setting the value 'camera'. However, notice that this may not
work on all devices. If you are successful the parameter
'linescan_direction_source' becomes available and the parameter
'linescan_direction_output' can be used normally.
|
| 'linescan_direction_output' |
'forward', 'reverse' |
|
string |
Linescan direction (line scan cameras only). The value can only be changed if the parameter 'linescan_direction' has been successfully set to 'enable'
or 'camera'.
If the 'camera' value was set on the parameter 'linescan_direction',
then the parameter 'linescan_direction_source' must be set to
'internal' in order to enable the direction change.
|
| 'linescan_direction_signal' |
'active_high', 'active_low' |
|
string |
Signal of the line scan direction (line scan cameras only). |
| 'linescan_direction_source' |
'internal', 'external' |
|
string |
The linescan direction source (line scan cameras only) is the source from where the trigger for the direction change can be set. The source must
be set to 'internal' in order to enable the direction change using the
parameter 'linescan_direction_output'.
|
| 'lut' |
'disable', 'enable' |
'disable' |
string |
Enables or disables the lookup table. Caution: On some acquisition devices, the LUT can not be disabled.
|
| 'pixel_arrangement' |
'line_interleaved', 'pixel_interleaved' |
'pixel_interleaved' |
string |
In case of 4-channel images this parameter is used to set the pixel arrangement, if the output format differs from an RGB format.
|
| 'pixel_clock_detection' |
'falling', 'rising' |
|
string |
Type of pixel clock detection of the video source. |
| 'pixel_clock_ext' |
<Hz> |
|
integer |
External pixel clock frequency in Hz. Note that this parameter is valid only if parameter 'pixel_clock_source' specifies that
an external pixel clock is needed.
|
| 'pixel_clock_int' |
<Hz> |
|
integer |
Internal pixel clock frequency in Hz. Note that this parameter is valid only if parameter 'pixel_clock_source' specifies that
an internal pixel clock is needed.
|
| 'pixel_clock_source' |
'ext', 'ext_int', 'int' |
|
string |
Source of the acquisition device pixel clock. 'ext_int' means that the external pixel clock is used while the acquisition device
simultaneously outputs its own internal pixel clock for other use.
|
| 'port' |
0, 1, 2, 3, 4, 5 |
|
integer |
Number of the desired camera port. |
| 'saturation' |
<saturation> |
|
integer |
Color saturation percentage control (analog composite only). |
| 'shaft_encoder' |
'disable', 'enable' |
|
string |
Enables or disables shaft encoder support of the acquisition device. |
| 'shaft_encoder_drop' |
<number> |
|
integer |
Number of dropped signal edges using a shaft encoder. |
| 'shaft_encoder_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
Shaft encoder level fed to the acquisition device (line scan cameras only).
|
| 'shaft_encoder_multiply' |
<number> |
|
integer |
Number of signal edges generated for each shaft encoder signal edge, when video acquisitions are controlled by an external shaft encoder trigger.
|
| 'sharpness' |
<sharpness> |
|
integer |
Sharpness control applied to the video signal (analog composite only). |
| 'strobe' |
'disable', 'enable' |
|
string |
Enables or disables the strobe pulse. You must have set the signal properties and the method first.
|
| 'strobe_delay' |
<microseconds> |
|
integer |
Strobe pulse delay 1 (in microseconds). |
| 'strobe_delay2' |
<microseconds> |
|
integer |
Strobe pulse delay 2 (in microseconds). |
| 'strobe_duration' |
<microseconds> |
|
integer |
Strobe pulse width (in microseconds). |
| 'strobe_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
Strobe signal level output by the acquisition device. |
| 'strobe_method' |
1, 2 |
|
integer |
Strobe pulse output method, see Sapera LT documentation for more details.
|
| 'strobe_signal' |
'active_high', 'active_low' |
|
string |
Strobe pulse signal. |
| 'time_integration' |
'disable', 'enable' |
|
string |
Enables or disables the time integration signal pulse to the camera (area scan cameras only). You have to set the signal properties and the method
first.
|
| 'time_integration_delay' |
<microseconds> |
|
integer |
Time integration delay (in microseconds). After receiving a trigger pulse, the acquisition device will wait this delay before generating the time
integration pulse(s).
|
| 'time_integration_duration' |
<microseconds> |
|
integer |
Time integration pulse width in microseconds (area scan cameras only). |
| 'time_integration_method' |
1, 2, 3, 4, 5, 6, 7, 8, 10, 11, 12 |
|
integer |
Time integration method, see Sapera LT documentation for more details. |
| 'time_integration_pulse0_delay' |
<microseconds> |
|
integer |
Time integration delay (in microseconds) of pulse 0. After receiving a trigger pulse, the acquisition device will wait this delay before generating
the time integration pulse 0.
|
| 'time_integration_pulse0_duration' |
<microseconds> |
|
integer |
Specifies the time integration pulse 0 width (in microseconds). |
| 'time_integration_pulse0_signal' |
'active_high', 'active_low' |
|
string |
Time integration signal of pulse 0. |
| 'time_integration_pulse1_delay' |
<microseconds> |
|
integer |
Time integration delay (in microseconds) of pulse 1. After receiving a pulse, the acquisition device will wait this delay before generating the
time integration pulse 1.
|
| 'time_integration_pulse1_duration' |
<microseconds> |
|
integer |
Specifies the time integration pulse 1 width (in microseconds). |
| 'time_integration_pulse1_signal' |
'active_high', 'active_low' |
|
string |
Time integration signal of pulse 1. |
The parameters below are only for Teledyne DALSA frame grabber boards.
| Parameter |
Values |
Default |
Type |
Kind |
Description |
| 'bayer_hardware_decoder' |
'disable', 'enable' |
|
string |
dynamic |
Gets the status of the hardware Bayer decoder of the acquisition device. When present and enabled, the Bayer video data is converted into the
specified output format (from the camera configuration file). Note that
this feature is not supported by all board types!
|
| 'bayer_hardware_decoder_method' |
1, 2, 3, 4, 5, 7 |
|
integer |
dynamic |
Method for data conversion of the hardware Bayer decoder. |
| 'bayer_software_decoder' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the software Bayer decoder. The setting takes effect with the next call of 'grab_image' or 'grab_image_async'.
|
| 'bayer_software_decoder_alignment' |
'bg_gr', 'gb_rg', 'gr_bg', 'rg_gb' |
'gb_rg' |
string |
pre-defined |
Alignment of the upper left 2x2 square of the camera`s Bayer scheme. |
| 'bayer_software_decoder_format' |
'RGB888', 'RGB8888', 'RGB101010' |
'RGB888' |
string |
pre-defined |
Output buffer format of the software Bayer decoder. 'RGB101010' is only available, if the input format is MONO16!
|
| 'bayer_software_decoder_method' |
1, 2, 3 |
1 |
integer |
pre-defined |
Method for data conversion of the software Bayer decoder.
- method 1: Fast, based on bilinear interpolation.
- method 2: Advanced, preserves image edges. Works only well, if the image
has a strong green content.
- method 3: Advanced, preserves image edges, independent of image green
content.
|
| 'bayer_software_decoder_whitebalance' |
[<wb_red, wb_green, wb_blue>] |
[1.0, 1.0, 1.0] |
integer |
pre-defined |
White balance gain for each color channel. You always have to set all three values (floating point). If all values are set to 1.0, no white
balance is used for the software Bayer conversion.
|
| 'bit_ordering' |
'9_10', 'inv', 'msb_10', 'msb_12', 'std' |
|
string |
dynamic |
Digital bit ordering of the camera.
- 9_10: Video data bits 9 and 10 are swapped with bits 0 and 1 (required
by some 10-bit digital cameras).
- inv: The video data bits are inverted (logical NOT).
- msb_10: Video data bits 0-7 connect to the acquisition device input bits
2-9 (required by some 8-bit digital cameras).
- msb_12: Video data bits 4-11 are directed to the input bits 0-7 of the
acquisition device (required by some 12-bit digital cameras).
- std: Standard digital bit ordering.
|
| 'brightness' |
<brightness> |
|
integer |
dynamic |
Brightness of the video signal. Represents the percentage of brightness to add or subtract to the composite video signal (analog only).
|
| 'brightness_blue' |
<brightness_blue> |
|
integer |
dynamic |
Brightness of the blue video signal. Represents the percentage of brightness to add or subtract to the blue video signal
(analog only).
|
| 'brightness_green' |
<brightness_green> |
|
integer |
dynamic |
Brightness of the green video signal. Represents the percentage of brightness to add or subtract to the green video signal
(analog only).
|
| 'brightness_red' |
<brightness_red> |
|
integer |
dynamic |
Brightness of the red video signal. Represents the percentage of brightness to add or subtract to the red video signal
(analog only).
|
| 'cam_reset' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the reset pulse to the camera. You must have set the signal properties and the method first.
|
| 'cam_reset_delay' |
<microseconds> |
|
integer |
dynamic |
Reset pulse delay (in microseconds). After receiving a trigger pulse, the acquisition device will wait this delay before generating the reset pulse.
|
| 'cam_reset_duration' |
1...65535000 |
|
integer |
dynamic |
Duration of the reset pulse. |
| 'cam_reset_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Defines the reset pulse signal. |
| 'cam_trigger' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the frame trigger pulse to the camera (area scan only).
|
| 'cam_trigger_delay' |
<microseconds> |
|
integer |
dynamic |
Represents the delay (in microseconds) the acquisition device will wait, before generating the trigger pulse (external, internal or software).
|
| 'cam_trigger_duration' |
<duration> |
|
integer |
dynamic |
The effect of this value differs addicted to the selected method. |
| 'cam_trigger_method' |
1, 2 |
|
integer |
dynamic |
Trigger method of the camera, see Sapera LT documentation for more details.
|
| 'cam_trigger_signal' |
'active_low', 'active_high' |
|
string |
dynamic |
Camera trigger signal. |
| 'camera_model' |
'<model>' |
|
string |
dynamic |
Name of the camera model. |
| 'camera_vendor' |
'<vendor>' |
|
string |
dynamic |
Name of the camera vendor. |
| 'contrast' |
<contrast> |
|
integer |
dynamic |
Contrast of the video signal. Represents the percentage of contrast to be applied to the composite video signal (analog only). Step:
1000 (1%).
|
| 'contrast_blue' |
<contrast_blue> |
|
integer |
dynamic |
Contrast of the blue video signal. Represents the percentage of contrast to be applied to the blue video signal (analog only).
Step: 1000 (1%).
|
| 'contrast_green' |
<contrast_green> |
|
integer |
dynamic |
Contrast of the green video signal. Represents the percentage of contrast to be applied to the green video signal (analog
only). Step: 1000 (1%).
|
| 'contrast_red' |
<contrast_red> |
|
integer |
dynamic |
Contrast of the red video signal. Represents the percentage of contrast to be applied to the red video signal (analog only). Step:
1000 (1%).
|
| 'decimate_count' |
<count> |
|
integer |
dynamic |
Number of fields or frames to decimate per second. |
| 'decimate_method' |
'disable', 'even', 'field', 'frame', 'odd' |
|
string |
dynamic |
Decimation method, see Sapera LT documentation for more details.
|
| 'ext_frame_trigger' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables external frame trigger (line scan cameras only). You must have set the signal properties first.
|
| 'ext_frame_trigger_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
dynamic |
External frame trigger level connected to the acquisition device (line scan cameras only).
|
| 'ext_frame_trigger_signal' |
'active_high', 'active_low', 'double_falling', 'double_rising', 'falling', 'rising'
|
|
string |
dynamic |
External frame trigger signal connected to the acquisition device (line scan cameras only). 'double_rising/falling' means to start
the acquisition on the rising/falling edge of trigger 1 and to end on
the rising/falling edge of trigger 2.
|
| 'ext_frame_trigger_source' |
<source> |
0 |
integer |
dynamic |
Physical input source the external line trigger is connected to on the acquisition device, in the case where the acquisition device has
more than one input.
|
| 'ext_line_trigger' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables external line trigger (line scan cameras only). You must have set the signal properties first.
|
| 'ext_line_trigger_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
dynamic |
External line trigger level connected to the acquisition device (line scan cameras only).
|
| 'ext_line_trigger_signal' |
'falling', 'rising' |
|
string |
dynamic |
External line trigger signal connected to the acquisition device (line scan cameras only).
|
| 'ext_line_trigger_source' |
<source> |
0 |
integer |
dynamic |
Physical input source the external line trigger is connected to on the acquisition device, in the case where the acquisition device has
more than one input.
|
| 'ext_trigger_delay' |
<delay> |
0 |
integer |
dynamic |
Delay of the external trigger signal in units specified by 'ext_trigger_delay_time_base'.
|
| 'ext_trigger_delay_time_base' |
<time_base> |
0 |
integer |
dynamic |
Granularity of units required to adjust the delay of the external trigger signal with 'ext_trigger_delay'.
|
| 'ext_trigger_duration' |
<duration> |
0 |
integer |
dynamic |
Minimum external trigger pulse duration. For details please refer to the 'Sapera Acquisition Parameter' manual.
|
| 'ext_trigger_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
'TTL' |
string |
pre-defined |
External trigger level connected to the acquisition device. |
| 'ext_trigger_signal' |
'active_high', 'active_low', 'falling', 'rising' |
'rising' |
string |
pre-defined |
External trigger signal connected to the acquisition device. |
| 'ext_trigger_source' |
0, 1, 2 |
0 |
integer |
pre-defined |
Physical input source the external trigger is connected to on the acquisition device, in the case where the acquisition device has
more than one input.
|
| 'frame_integration' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the frame integration control (area scan cameras only). You must have set the signal properties and the method first.
|
| 'frame_integration_count' |
1...(2^32)-1 |
|
integer |
dynamic |
Number of frames to integrate. |
| 'frame_integration_method' |
1, 2 |
|
integer |
dynamic |
Frame integration method, see Sapera LT documentation for more details.
|
| 'frame_integration_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Frame integration signal. |
| 'gio_callback_mask' |
<mask> |
|
integer |
dynamic |
If a interrupt callback for the I/Os has to be set, this parameter sets a mask, which pins will cause the callback to be called. To active a pin, the
value of the mask has to be 1 for it. See also set_framegrabber_callback.
|
| 'gio_connector' |
<number> |
|
integer |
dynamic |
Connector number of the I/O block. Only supported by XIO boards.
|
| 'gio_count' |
<num> |
|
integer |
dynamic |
Number of available I/O blocks. |
| 'gio_device_id' |
<id> |
|
integer |
dynamic |
Device id of the actual I/O block. |
| 'gio_dir_output' |
<io> |
|
integer |
dynamic |
Specifies which I/O blocks are set as output. If a block is set to 1, it is used as output. Otherwise it is an input.
|
| 'gio_dir_tristate' |
<io> |
|
integer |
dynamic |
Specifies which I/O blocks are set as tristate. If a block is set to 1, it is tri-stated.
|
| 'gio_event_count_falling_edge' |
<event_count> |
|
integer |
dynamic |
Number of events for the falling edge of the interrupt callback for the I/Os. This parameter only returns values, if the corresponding event has
been registered by the callback.
|
| 'gio_event_count_rising_edge' |
<event_count> |
|
integer |
dynamic |
Number of events for the rising edge of the interrupt callback for the I/Os. This parameter only returns values, if the corresponding event has
been registered by the callback.
|
| 'gio_input_level' |
'12 Volts', '24 Volts', '422', 'LVDS', 'LVTTL', 'OPTO', 'TTL' |
|
string |
dynamic |
Input level of the I/O device. Note that this parameter is only available if the I/O block is set as input.
|
| 'gio_label' |
'<label>' |
|
string |
dynamic |
Name of the actual I/O. |
| 'gio_output_type' |
'led', 'npn', 'opto', 'pnp', 'ttl', 'lvttl' |
|
string |
dynamic |
Output type of the I/O block. |
| 'gio_state' |
0, 1 |
|
integer |
dynamic |
State of the general I/O pins. If a pin is set to 1, it will be set to TRUE, otherwise FALSE. To set the mask for the pins to set use the parameter
'gio_state_mask'. Note that you have to set ALL pins you want to set
additionally to the mask, which means, e.g., to activate pins 1 and 3, the mask
and the state has to be set to 0x5. This parameter is not supported by all boards.
|
| 'gio_state_mask' |
<mask> |
|
integer |
dynamic |
Mask for setting the state of the general I/O pins. If a pin is set to 1, it can be set via the value of the parameter 'gio_state'.
|
| 'hue' |
<hue> |
|
integer |
dynamic |
Phase change in degrees applied to the hue control (analog composite or Y/C only).
|
| 'int_frame_trigger' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables internal frame trigger (area scan cameras only). You must have set the trigger frequency first.
|
| 'int_frame_trigger_freq' |
<mHz> |
|
integer |
dynamic |
Internal frame trigger frequency in milli-Hz (area scan cameras only).
|
| 'int_line_trigger' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables internal line trigger. You must have set the trigger frequency first.
|
| 'int_line_trigger_freq' |
<Hz> |
|
integer |
dynamic |
Internal line trigger frequency in Hz. |
| 'line_integration' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the line integration signal pulse to the camera (line scan cameras only). You have to set the signal properties and the method
first.
|
| 'line_integration_duration' |
<microseconds> |
|
integer |
dynamic |
Specifies the line integration pulse width in microseconds (line scan cameras only).
|
| 'line_integration_method' |
1, 2, 3, 4, 7 |
|
integer |
dynamic |
Line integration method, see Sapera LT documentation for more details (line scan cameras only).
|
| 'line_integration_pulse0_delay' |
<microseconds> |
|
integer |
dynamic |
Line integration delay (in microseconds) of pulse 0. After receiving a trigger pulse, the acquisition device will wait this delay before generating the
line integration pulse 0 (line scan cameras only).
|
| 'line_integration_pulse0_duration' |
<microseconds> |
|
integer |
dynamic |
Line integration pulse 0 width (in microseconds) (line scan cameras only). |
| 'line_integration_pulse0_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Line integration signal of pulse 0 (line scan cameras only). |
| 'line_integration_pulse1_delay' |
<microseconds> |
|
integer |
dynamic |
Line integration delay (in microseconds) of pulse 1. After receiving a trigger pulse, the acquisition device will wait this delay before generating
the line integration pulse 1 (line scan cameras only).
|
| 'line_integration_pulse1_duration' |
<microseconds> |
|
integer |
dynamic |
Line integration pulse 1 width (in microseconds) (line scan cameras only). |
| 'line_integration_pulse1_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Line integration signal of pulse 1 (line scan cameras only). |
| 'line_integration_time_base' |
'ns', 'pixel_clk' |
|
string |
dynamic |
Time base of line integration signal (line scan cameras only). |
| 'line_trigger' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the line trigger signal pulse to the camera (line scan cameras only). Note that this parameter cannot be enabled if
'line_integration' is enabled and vice versa.
|
| 'line_trigger_delay' |
<delay> |
|
integer |
dynamic |
Delay of the line trigger pulse in units specified by 'line_integration_time_base' (line scan cameras only).
|
| 'line_trigger_duration' |
<duration> |
|
integer |
dynamic |
Duration of the line trigger pulse in units specified by 'line_integration_time_base' (line scan cameras only).
|
| 'line_trigger_method' |
1, 2 |
|
integer |
dynamic |
Output method of the line trigger signal pulse (line scan cameras only).
|
| 'linescan_direction' |
'disable', 'enable', 'camera' |
|
string |
dynamic |
Enables or disables the line scan direction (line scan cameras only). If the framegrabber does not support this feature, but the camera does,
it is possible to attempt to enable direction change directly into the
camera by setting the value 'camera'. However, notice that this may not
work on all devices. If you are successful the parameter
'linescan_direction_source' becomes available and the parameter
'linescan_direction_output' can be used normally.
|
| 'linescan_direction_output' |
'forward', 'reverse' |
|
string |
dynamic |
Linescan direction (line scan cameras only). The value can only be changed if the parameter 'linescan_direction' has been successfully set to 'enable'
or 'camera'.
If the 'camera' value was set on the parameter 'linescan_direction',
then the parameter 'linescan_direction_source' must be set to
'internal' in order to enable the direction change.
|
| 'linescan_direction_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Signal of the line scan direction (line scan cameras only). |
| 'linescan_direction_source' |
'internal', 'external' |
|
string |
dynamic |
The linescan direction source (line scan cameras only) is the source from where the trigger for the direction change can be set. The source must
be set to 'internal' in order to enable the direction change using the
parameter 'linescan_direction_output'.
|
| 'lut' |
'disable', 'enable' |
'disable' |
string |
pre-defined |
Enables or disables the lookup table. Caution: On some acquisition devices, the LUT can not be disabled.
|
| 'pixel_arrangement' |
'line_interleaved', 'pixel_interleaved' |
'pixel_interleaved' |
string |
pre-defined |
In case of 4-channel images this parameter is used to set the pixel arrangement, if the output format differs from an RGB format.
|
| 'pixel_clock_11' |
<Hz> |
|
integer |
dynamic |
Pixel clock frequency in Hz, so that the camera image has a 1:1 aspect ratio.
|
| 'pixel_clock_detection' |
'falling', 'rising' |
|
string |
dynamic |
Type of pixel clock detection of the video source. |
| 'pixel_clock_ext' |
<Hz> |
|
integer |
dynamic |
External pixel clock frequency in Hz. Note that this parameter is valid only if parameter 'pixel_clock_source' specifies that
an external pixel clock is needed.
|
| 'pixel_clock_int' |
<Hz> |
|
integer |
dynamic |
Internal pixel clock frequency in Hz. Note that this parameter is valid only if parameter 'pixel_clock_source' specifies that
an internal pixel clock is needed.
|
| 'pixel_clock_source' |
'ext', 'ext_int', 'int' |
|
string |
dynamic |
Source of the acquisition device pixel clock. 'ext_int' means that the external pixel clock is used while the acquisition device
simultaneously outputs its own internal pixel clock for other use.
|
| 'saturation' |
<saturation> |
|
integer |
dynamic |
Color saturation percentage control (analog composite only). |
| 'shaft_encoder' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables shaft encoder support of the acquisition device. |
| 'shaft_encoder_drop' |
<number> |
|
integer |
dynamic |
Number of dropped signal edges using a shaft encoder. |
| 'shaft_encoder_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
dynamic |
Shaft encoder level fed to the acquisition device (line scan cameras only).
|
| 'shaft_encoder_multiply' |
<number> |
|
integer |
dynamic |
Number of signal edges generated for each shaft encoder signal edge, when video acquisitions are controlled by an external shaft encoder trigger.
|
| 'sharpness' |
<sharpness> |
|
integer |
dynamic |
Sharpness control applied to the video signal (analog composite only). |
| 'signal_status' |
<status> |
|
integer |
dynamic |
Current signal status of the camera. |
| 'strobe' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the strobe pulse. You must have set the signal properties and the method first.
|
| 'strobe_delay' |
<microseconds> |
|
integer |
dynamic |
Strobe pulse delay 1 (in microseconds). |
| 'strobe_delay2' |
<microseconds> |
|
integer |
dynamic |
Strobe pulse delay 2 (in microseconds). |
| 'strobe_duration' |
<microseconds> |
|
integer |
dynamic |
Strobe pulse width (in microseconds). |
| 'strobe_level' |
'12 Volts', '24 Volts', 'LVDS', 'LVTTL', 'OPTO', 'RS-422', 'TTL' |
|
string |
dynamic |
Strobe signal level output by the acquisition device. |
| 'strobe_method' |
1, 2 |
|
integer |
dynamic |
Strobe pulse output method, see Sapera LT documentation for more details.
|
| 'strobe_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Strobe pulse signal. |
| 'time_integration' |
'disable', 'enable' |
|
string |
dynamic |
Enables or disables the time integration signal pulse to the camera (area scan cameras only). You have to set the signal properties and the method
first.
|
| 'time_integration_delay' |
<microseconds> |
|
integer |
dynamic |
Time integration delay (in microseconds). After receiving a trigger pulse, the acquisition device will wait this delay before generating the time
integration pulse(s).
|
| 'time_integration_duration' |
<microseconds> |
|
integer |
dynamic |
Time integration pulse width in microseconds (area scan cameras only). |
| 'time_integration_method' |
1, 2, 3, 4, 5, 6, 7, 8, 10, 11, 12 |
|
integer |
dynamic |
Time integration method, see Sapera LT documentation for more details. |
| 'time_integration_pulse0_delay' |
<microseconds> |
|
integer |
dynamic |
Time integration delay (in microseconds) of pulse 0. After receiving a trigger pulse, the acquisition device will wait this delay before generating
the time integration pulse 0.
|
| 'time_integration_pulse0_duration' |
<microseconds> |
|
integer |
dynamic |
Specifies the time integration pulse 0 width (in microseconds). |
| 'time_integration_pulse0_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Time integration signal of pulse 0. |
| 'time_integration_pulse1_delay' |
<microseconds> |
|
integer |
dynamic |
Time integration delay (in microseconds) of pulse 1. After receiving a pulse, the acquisition device will wait this delay before generating the
time integration pulse 1.
|
| 'time_integration_pulse1_duration' |
<microseconds> |
|
integer |
dynamic |
Specifies the time integration pulse 1 width (in microseconds). |
| 'time_integration_pulse1_signal' |
'active_high', 'active_low' |
|
string |
dynamic |
Time integration signal of pulse 1. |
Get the current lookup table.
| Type |
Description |
| 'external_trigger' |
The 'external_trigger' callback corresponds with the CORACQ_VAL_EVENT_TYPE_EXTERNAL_TRIGGER and is only available for framegrabbers that support it.
|
| 'gio_falling_edge' |
If a frame grabber supports general I/Os, a callback can be registered, which will be called if an I/O generates an interrupt. With the
parameter 'gio_callback_mask' the I/O pins, which will call the callback,
can be set. The parameter 'gio_event_count_falling_edge' returns the number
of occurred events. This callback is not supported by GigE Vision cameras.
|
| 'gio_rising_edge' |
If a frame grabber supports general I/Os, a callback can be registered, which will be called if an I/O generates an interrupt. With the
parameter 'gio_callback_mask' the I/O pins, which will call the callback,
can be set. The parameter 'gio_event_count_rising_edge' returns the number
of occurred events. This callback is not supported by GigE Vision cameras.
|
| 'line_end' |
The 'line_end' callback corresponds to the CorXferRegisterCallback(..., CORXFER_VAL_EVENT_TYPE_END_OF_LINE, ...)
command. The callback will be signaled after the line data is written into
the local PC buffer. The parameter 'line_number' has to be set before
activating this callback to specify the desired line at which the callback
will be signaled.
|
| 'readout_end' |
Since the callback corresponds to the CorAcqDeviceRegister(..., 'End of Readout', ...)
(or 'ReadoutEnd' with Genie TS Framework) command, it is only available for
GigE Vision cameras. Note that the callback will be signaled after the image
data is written into the local camera buffer but not yet finally transferred
to the PC.
|
| 'transfer_end' |
The 'transfer_end' callback corresponds to the CorXferRegisterCallback(..., CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFER, ...)
command. The callback will be signaled after the image data is written into
the local PC buffer.
|
| 'data_overflow' |
The 'data_overflow' callback corresponds with the CORACQ_VAL_EVENT_TYPE_DATA_OVERFLOW and is only available for framegrabbers that support it.
|
| 'end_of_even' |
The 'end_of_even' callback corresponds with the CORACQ_VAL_EVENT_TYPE_END_OF_EVEN and is only available for framegrabbers that support it.
|
| 'end_of_field' |
The 'end_of_field' callback corresponds with the CORACQ_VAL_EVENT_TYPE_END_OF_FIELD and is only available for framegrabbers that support it.
|
| 'end_of_frame' |
The 'end_of_frame' callback corresponds with the CORACQ_VAL_EVENT_TYPE_END_OF_FRAME and is only available for framegrabbers that support it.
|
| 'end_of_odd' |
The 'end_of_odd' callback corresponds with the CORACQ_VAL_EVENT_TYPE_END_OF_ODD and is only available for framegrabbers that support it.
|
| 'external_trigger_ignored' |
The 'external_trigger_ignored' callback corresponds with the CORACQ_VAL_EVENT_TYPE_EXTERNAL_TRIGGER_IGNORED and is only available for framegrabbers
that support it.
|
| 'external_trigger_too_slow' |
The 'external_trigger_too_slow' callback corresponds with the CORACQ_VAL_EVENT_TYPE_EXT_LINE_TRIGGER_TOO_SLOW and is only available for
framegrabbers that support it.
|
| 'frame_lost' |
The 'frame_lost' callback corresponds with the CORACQ_VAL_EVENT_TYPE_FRAME_LOST and is only available for framegrabbers that support it.
|
| 'horizontal_sync_lock' |
The 'horizontal_sync_lock' callback corresponds with the CORACQ_VAL_EVENT_TYPE_HSYNC_LOCK and is only available for framegrabbers that support it.
|
| 'horizontal_sync_unlock' |
The 'horizontal_sync_unlock' callback corresponds with the CORACQ_VAL_EVENT_TYPE_HSYNC_UNLOCK and is only available for framegrabbers that support it.
|
| 'line_trigger_too_fast' |
The 'line_trigger_too_fast' callback corresponds with the CORACQ_VAL_EVENT_TYPE_LINE_TRIGGER_TOO_FAST and is only available for
framegrabbers that support it.
|
| 'link_error' |
The 'link_error' callback corresponds with the CORACQ_VAL_EVENT_TYPE_LINK_ERROR and is only available for framegrabbers that support it.
|
| 'no_horizontal_sync' |
The 'no_horizontal_sync' callback corresponds with the CORACQ_VAL_EVENT_TYPE_NO_HSYNC and is only available for framegrabbers that support it.
|
| 'no_pixel_clock' |
The 'no_pixel_clock' callback corresponds with the CORACQ_VAL_EVENT_TYPE_NO_PIXEL_CLK and is only available for framegrabbers that support it.
|
| 'no_vertical_sync' |
The 'no_vertical_sync' callback corresponds with the CORACQ_VAL_EVENT_TYPE_NO_VSYNC and is only available for framegrabbers that support it.
|
| 'pixel_clock' |
The 'pixel_clock' callback corresponds with the CORACQ_VAL_EVENT_TYPE_PIXEL_CLK and is only available for framegrabbers that support it.
|
| 'shaft_encoder_reverse_count_overflow' |
The 'shaft_encoder_reverse_count_overflow' callback corresponds with the CORACQ_VAL_EVENT_TYPE_SHAFT_ENCODER_REVERSE_COUNT_OVERFLOW
and is only available for framegrabbers that support it.
|
| 'start_of_even' |
The 'start_of_even' callback corresponds with the CORACQ_VAL_EVENT_TYPE_START_OF_EVEN and is only available for framegrabbers that support it.
|
| 'start_of_field' |
The 'start_of_field' callback corresponds with the CORACQ_VAL_EVENT_TYPE_START_OF_FIELD and is only available for framegrabbers that support it.
|
| 'start_of_frame' |
The 'start_of_frame' callback corresponds with the CORACQ_VAL_EVENT_TYPE_START_OF_FRAME and is only available for framegrabbers that support it.
|
| 'start_of_odd' |
The 'start_of_odd' callback corresponds with the CORACQ_VAL_EVENT_TYPE_START_OF_ODD and is only available for framegrabbers that support it.
|
| 'user_define' |
The 'user_define' callback corresponds with the CORACQ_VAL_EVENT_TYPE_USER_DEFINE and is only available for framegrabbers that support it.
|
| 'vertical_sync' |
The 'vertical_sync' callback corresponds with the CORACQ_VAL_EVENT_TYPE_VERTICAL_SYNC and is only available for framegrabbers that support it.
|
| 'vertical_timeout' |
The 'vertical_timeout' callback corresponds with the CORACQ_VAL_EVENT_TYPE_VERTICAL_TIMEOUT and is only available for framegrabbers that support it.
|
Not supported by this interface.
Not supported by this interface.


WebEncoder
Upload → Encode →
Watch!
Your browser does not support the video tag.
Go back
by Vitor Mendes Paisante


--- layout: default title: Haiku — Poems made simple subtitle: "Write beautifully" web_title: "Haiku — Vivian Qu" exclude_nav: true description: "Terms of Use and Privacy Policy for Haiku app" permalink: /haiku/privacy-policy ---
This page was last updated on September 12, 2020.
This policy describes the information that I, Vivian Qu, may receive from Haiku app users and how that information is handled.
What I want, what’s most important to me, is:
In other words, I don’t want any private information — except for what is necessary information to be able to identify and fix crashes & bugs, and things like how many times the app has been downloaded.
Much of this policy was proudly copied directly from the Information Superhighway policy. I appreciated the conciseness and readability of IS's policy and thought it worthy of stealing.
If you opt in to send crash logs to developers on iOS, both Apple and I will have copies of your crash logs.
Crash logs are created and stored by Apple, and I access them through Apple’s provided tools: App Store Connect and Xcode.
This data is collected only to facilitate fixing crashing bugs.
Visits to the website are logged via anonymized Google Analytics. I am only interested in basic information like number of visitors to a particular blog post. You can read more about the website's general privacy policy here.


1 300 views
800 visitors
3 800 impressions
Inbox (2)
Your projects
Mobile App
Symu.co$1500
New dashboard
Symu.co$1500
Landing page
Symu.co$1500
New website
Symu.co$1500
Landing page
Symu.co$1500