-
checkAffiliation()
-
TODO
- Source:
-
checkEmail()
-
Checks if the user's email address is valid. Highlights the appopriate input element '#inputEmail' if it's not correct.
- Source:
Returns:
true if the user's email address is valid one, otherwise false is returned.
-
checkFirstName()
-
Checks if the user's first name is valid. Highlights the appopriate input element '#inputFirstName' if it's not correct.
- Source:
Returns:
true if the first name is valid (not empty word without digits and special signs), otherwise false is returned.
-
checkLastName()
-
Checks if the user's last name is valid. Highlights the appopriate input element '#inputLastName' if it's not correct.
- Source:
Returns:
true if the last name is valid (not empty word without digits and special signs), otherwise false is returned.
-
initHashtagChange()
-
Defines the behaviour for clicking on "back" or "next" browser buttons aka browser history.
The function opens the appropriate form views.
- Source:


Choose your location: Choose a location India Pakistan Hong Kong Egypt South Africa Angola Brazil Peru Argentina United Kingdom Greece Netherlands Georgia Arizona Pennsylvania Australia Sydney New South Wales
Write your message here:
Name:
Email:
Phone Number:
Awful :( Fantastic :)


--- layout: page title: About header-img: "img/about-bg.png" ---
I am currently pursuing a career in software engineering and am a full time flatiron student .


|
iSensor-SPI-Buffer
1.14
Firmware for the iSensor-SPI-Buffer board to enable full throughput buffered data capture on Analog Devices IMUs
|
Header file for iSensor-SPI-Buffer USB command line register interface. More...
Go to the source code of this file.
Header file for iSensor-SPI-Buffer USB command line register interface.
Copyright (c) Analog Devices Inc, 2020 All Rights Reserved.


Terraform is a declarative language and set of tools for defining infrastructure in code
Initial configuration to tell terraform how to work with your service
Build your resources in repeatable, declarative syntax
Define dynamic values that can be passed in at run-time, or defined as reasonable defaults
Need the ID of an existing resource? Look it up
https://www.terraform.io/docs/configuration/data-sources.html
Expose values from your module, or remotely to other stacks
Do programmey type stuff
https://www.terraform.io/docs/configuration/interpolation.html
provider "aws" {
provider "aws" {
access_key = "foo"
secret_key = "bar"
region = "us-east-1"
}
resource "aws_instance"
resource "aws_instance" "web" {
resource "aws_instance" "web" {
ami = "ami-408c7f28"
instance_type = "t1.micro"
key_name = "chalovich"
}
variable "ami_id" {
variable "ami_id" {
type = "string"
default = "ami-408c7f28"
}
variable "accounts" {
type = "list"
default = [
"111111111",
"222222222",
"333333333"
]
}
variable "accounts" {
type = "map"
default = {
ts = "111111111"
bs = "222222222"
nt = "333333333"
}
}
data "aws_vpc"
data "aws_vpc" "neat" {
data "aws_vpc" "neat" {
id = "${var.vpc_id}"
}
resource "aws_subnet" "web" {
vpc_id = "${data.aws_vpc.neat.id}"
cidr_block = "${var.cidr_block}"
}
Terraform stores the metadata about your instances in a state file
You can store your state in a remote backend, and retrieve it for other projects
data "terraform_remote_state"
data "terraform_remote_state" "aws" {
data "terraform_remote_state" "aws" {
backend = "s3"
data "terraform_remote_state" "aws" {
backend = "s3"
config {
bucket = "tfstate.us-west-2.s3.bcaa.com"
key = "mystatefile"
region = "us-west-2"
}
}