qasim-1develop Goto Github PK

hpc

Algoritmos de Aceleramiento con CPU y GPU

hpc-1

Scripts for modifying GPU/CPU

hpc_1

CPU Benchmarking

hpc_cg

High-Performance Computing: CPU Instructions, GPU OpenCL & CUDA, etc. :sunny:

hpips_cpuid

hybird-multi-cloud-training

This repository contains all the key concepts taught to us in our Hybrid Multi Cloud Computing training which includes hands-on training on AWS, OpenStack, Kubernetes, and Terraform.

hybird-storage-dotnet-manage-storage-accounts

Getting Started with Storage - Manage Storage Accounts in Azure Stack Hybrid cloud - in C# asynchronously

hybirdcloud

hybird cloud demo with aws service

hybirdportal

service portal use for paas/saas cloud service

hybrid_multicloud_overlay

MutiCloud_Overlay demonstrates a use case of overlay over one or more clouds such as AWS, Azure, GCP, OCI, Alibaba and a vSphere private infrastructure in Hub and spoke topology, point to point topology and in a Single cloud. Overlay protocols IPv6 and IPv4 are independent of underlying infrastructure. This solution can be integrated with encryption and additional security features.

hydrogen

Matlab simulation of quantum energy levels of Hydrogen atom

hydrogenbondenergy

Calculate energy of hydrogen bond in protein

ibex

Ibex is a small 32 bit RISC-V CPU core (RV32IMC/EMC) with a two stage pipeline, previously known as zero-riscy.

ibm-cloud-cli-release

ibm-cloud-developer-tools

Installation scripts for new IBM Cloud Developer CLI Plugin and it's dependencies.

ibmcloud-labs

A set of IBM Cloud Labs to discover Cloud Foundry, Container, IOT, Watson Conversation and API Connect

icloud-api

iClould Non Public API Implementation

ictmail---mail-app-client

Aplikasi Email Client menggunakan Algoritma Kriptografi AES dan RC4. Khusus email Gmail, Yahoo dan AOL Mail.

illinois-medical-immigration-by-uscis

Medical Examination for U.S. Immigration. All that is necessary to complete your medical exam for USCIS exam. Medical Exams for U.S. Immigration may only be performed by a USCIS Certified Civil Surgeon. United States immigration law requires immigrant visa applicants to obtain certain vaccinations (listed below) prior to the issuance of an immigrant visa. Panel physicians who conduct medical examinations of immigrant visa applicants are required to verify that immigrant visa applicants have met the vaccination requirements, or that it is medically inappropriate for the visa applicant to receive one or more of the listed vaccinations: 1) Hepatitis A, 2) Hepatitis B, 3) Influenza, 4) Influenza type b (Hub), 5) Measles, 6) Meningococcal, 7) Mumps, 8) Pneumococcal, 9) Pertussis, 10) Polio, 11) Rotavirus, 12) Rubella, 13) Tetanus, 14) Varicella. United States Civil Surgeon USCIS Board Certified in Internal Medicine. Suburban Medical & Wellness Center Since June 2006. Graduated with honors at – University of Illinois Urbana – Champaign. Faculty Professor : 1) Mount Sinai Hospital, 2) Rosalind Faranklin University, Chicago, IL, 3) Chicago Medical School Affiliated With : 1) St. Alexius Medical Center, Hoffman Estates, 2) Alexian Brother Medical Center, Elk Grove Village, 3) Northwest Community Hospital, Arlington Heights, 4) Glen Oaks Hospital, Glendale Heights, 5) Lutheran General Hospital, Park Ridge.

inlets

Cloud Native Tunnel written in Go

intel-undervolt

Intel CPU undervolting and throttling configuration tool

intro-to-apis-course

Introduction to APIs course

ipradar2

Real-time detection and defense against malicious network activity and policy violations (exploits, port-scanners, advertising, telemetry, state surveillance, etc.)

iuvolt

Script to undervolt Intel CPUs

java-mail-clients

Send Java Email from GMail, Outlook, Yahoo and Zoho. Demo App to test jHipster tip for Email

javaproject

It contains the code of apple store , its products,customers and sales of the apple products

javasdk

A java software development kit to build app with CloudBoost BaaS

jboss-developer-shared-resources

Shared resources among all JBoss Developer materials

jerusalem2020j2il-repository

Search documentation... Support Dashboard Card Payments Quickstart Securely collect card information from your customers and create a card payment. Supported cards Users in the United States can accept Visa Mastercard American Express Discover JCB Diners Club credit and debit cards. Stripe also supports a range of additional payment methods, depending on the country of your Stripe account. Accepting a card payment using Stripe is a two-step process, with a client-side and a server-side action: From your website running in the customer’s browser, Stripe securely collects your customer’s payment information and returns a representative token. This, along with any other form data, is then submitted by the browser to your server. Using the token, your server-side code makes an API request to create a charge and complete the payment. Tokenization ensures that no sensitive card data ever needs to touch your server so your integration can operate in a PCI compliant way. Step 1: Securely collecting payment information Checkout reference Complete information about available options and parameters is provided in the Checkout reference. The simplest way for you to securely collect and tokenize card information is with Checkout. It combines HTML, JavaScript, and CSS to create an embedded payment form. When your customer enters their payment information, the card details are validated and tokenized for your server-side code to use. To see Checkout in action, click the button below, filling in the resulting form with: Any random, syntactically valid email address (the more random, the better) One of Stripe’s test card numbers, such as 4242 4242 4242 4242 Any three-digit CVC code Any expiration date in the future To get started, add the following code to your payment page, making sure that the form submits to your own server-side code: <form action="your-server-side-code" method="POST"> <script src="https://checkout.stripe.com/checkout.js" class="stripe-button" data-key="pk_test_2DtHIU1N9li5GpmJjyxkQMHh" data-amount="999" data-name="Demo Site" data-description="Example charge" data-image="https://stripe.com/img/documentation/checkout/marketplace.png" data-locale="auto"> </script> </form> We’ve pre-filled the data-key attribute with your test publishable API key—only you can see this value. When you’re ready to go live with your payment form, you must replace the test key with your live key. Learn more about how the keys play into test and live modes. Although optional, we highly recommend also having Checkout collect the user’s ZIP code, as address and ZIP code verifications help reduce fraud. Add data-zip-code="true" to the above and enable declines on verification failures in your account settings. You can also set Checkout to collect the user’s full billing and shipping addresses (using the corresponding parameters). Requiring more than the minimum information lowers the possibility of a payment being declined or disputed in the future. Any fraudulent payments that you process are ultimately your responsibility, so requiring a little more than the minimum amount of information is an effective way to combat fraud. Radar, our modern suite of fraud protection tools, is only available to users who have implemented client-side tokenization. By doing so, it ensures that you can pass the necessary data required for our machine-learning fraud prevention models to make more accurate predictions. The amount provided in the Checkout form code is only shown to the user. It does not set the amount that the customer will be charged—you must also specify an amount when making a charge request. As you build your integration, make sure that your payment form and server-side code use the same amount to avoid confusion. An alternative to the blue button demonstrated above is to implement a custom Checkout integration. The custom approach allows you to use any HTML element or JavaScript event to open Checkout, as well as be able to specify dynamic arguments, such as custom amounts. Stripe.js and Elements If you’d prefer to have complete control over the look and fel of your payment form, you can make use of Stripe.js and Elements, our pre-built UI components. Refer to our Elements quickstart to learn more. Mobile SDKs Using our native mobile libraries for iOS and Android, Stripe can collect your customer’s payment information from within your mobile app and create a token for your server-side code to use. Step 2: Creating a charge to complete the payment Once a token is created, your server-side code makes an API request to create a one-time charge. This request contains the token, currency, amount to charge, and any additional information you may want to pass (e.g., metadata). curl Ruby Python PHP Java Node Go .NET curl https://api.stripe.com/v1/charges \ -u sk_test_fyzWf8eDyljIob76fMVSwIsi: \ -d amount=999 \ -d currency=usd \ -d description="Example charge" \ -d source=tok_6Pk6W3hFiGB7dyNavdvyrFkM These requests expect the ID of the Token (e.g., tok_KPte7942xySKBKyrBu11yEpf) to be provided as the value of the source parameter. Tokens can only be used once, and within a few minutes of creation. Using this approach, your customers need to re-enter their payment details each time they make a purchase. You can also save card details with Stripe for later use. Using this method, returning customers can quickly make a payment without providing their card details again. Next steps Congrats! You can now accept card payments with Stripe using Checkout. You may now want to check out these resources: Creating charges Getting paid Managing your Stripe account Supported payment methods Saving cards Questions? We're always happy to help with code or other questions you might have! Search our documentation, contact support, or connect with our sales team. You can also chat live with other developers in #stripe on freenode. Was this page helpful? Yes No

jet-planes

Jet planes formation releasing coloured smoke in HTML5 canvas.