Blog

Website

You can access the public version of this website here:
Apple Update Screensaver

Tap anywhere on the screen to open it in full screen mode. Hit Escape to exit full screen mode.

Purpose

I created this website as a demonstration of learning Clojure, ClojureScript, Reagent, etc. I decided a fairly simple project would be to mimic Apple’s update screen, after staring at it recently for an absurd amount of time. The “update” never actually finishes loading and will reset after the minutes remaining falls under a threshold.

TODO

Make it mobile aware so it looks good on mobile browsers.

Development mode

To start the Figwheel compiler, navigate to the project folder and run the following command in the terminal:

lein figwheel

Figwheel will automatically push cljs changes to the browser.
Once Figwheel starts up, you should be able to open the public/index.html page in the browser.

REPL

The project is setup to start nREPL on port 7002 once Figwheel starts.
Once you connect to the nREPL, run (cljs) to switch to the ClojureScript REPL.

Building for production

lein clean
lein package

Getting Started with Create React App

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

`npm start`

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

`npm test`

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

`npm run build`

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

`npm run eject`

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

wasm-by-example

Wasm By Example is a website containing simple examples for how to get things done with wasm.

Motivation

This project is heavily inspired by Go By Example. Wasm is still relatively young, and I thought it would be great to have a similar, hands-on / tutorial / introduction into WebAssembly for those who “learn by doing”.

Getting Started

One-time Setup

Create a GitHub account if you don’t already have one.
Install and set up Git.
Install the latest LTS version of Node.js (which includes npm). An easy way to do so is with nvm. (Mac and Linux: here, Windows: here)
```
nvm install --lts
```
Create your own fork of the wasm-by-example repository by clicking “Fork” in the Web UI. During local development, this will be referred to by git as origin.

Download your fork to a local repository.

git clone git@github.com:<your username>/wasm-by-example.git

Add an alias called upstream to refer to the main torch2424/wasm-by-example repository. Go to the root directory of the newly created local repository directory and run:
```
git remote add upstream git@github.com:torch2424/wasm-by-example.git
```
Fetch data from the upstream remote:
```
git fetch upstream master
```
Set up your local master branch to track upstream/master instead of origin/master (which will rapidly become outdated).
```
git branch -u upstream/master master
```

Branch (do this each time you want a new branch)

Create and go to the branch:

git checkout -b <branch name> master

Building & Running the project

Make sure you have the latest packages (after you pull): npm install
To build the project, run: npm run build
To serve, and build on changes for the project, run: npm run dev

Contributing

Thank you for wanting to contribute! Below is a guide for contributing different parts of the project:

Examples

Examples are the individual examples, concepts, or ideas conveyed for each language. Examples are laid out in the following format:

examples/EXAMPLE_NAME/EXAMPLE_NAME.PROGRAMMING_LANGUAGE.READING_LANGUAGE.md

Where the variables represent the following ideas:

EXAMPLE_NAME – is the name / title of the example.
PROGRAMMING_LANGUAGE – is the programming language used for the code snippets (e.g Rust).
READING_LANGUAGE – is the language that the idea is read / spoken (e.g English).

It is highly recommended examples also offer a demo where reasonable. Demos should be placed:

examples/EXAMPLE_NAME/demo/PROGRAMMING_LANGUAGE

Please place all relevant files there, and feel free to serve via an iframe, or link to the full source code. It is also recommended you offer a README.md to explain the demo, or simply offer build instructions.

Now that we understand how examples are made, let’s see some general guidance for contributing examples:

Creating a new Example

Awesome! Glad to see new examples and ideas! I’d recommended opening an issue before contributing an entirely new example. This way we can discuss if the example idea is beneficial, and to bring awareness to other contributors that ma want to do any translations and things.

After the idea has been discussed, feel free to open a PR following the format explained above, and we can review and add it to the website!

By default, all new examples will be last in the example list on the homepage. To set the order of your example, add your example’s name to the array in build-system/example-order.js to set its order.

Adding a new Programming Language to an existing Example

If you are adding a new programming language, feel free to simply open a new PR with the format explained above, and we can review and add it to the website! NOTE: It is highly recommended you add a demo of your example, unless there is a good reason for not providing one.

Adding a new Reading Language (Translation) to an existing Example

If you are adding a new reading language, feel free to simply open a new PR with the format explained above, and we can review and add it to the website! New reading languages don’t require a new demo or anything like that, and simply translate the written text between examples where it seems right.

Adding a completely new Reading Language (Translation)

If you would like to add a new language that is not supported at all in the project, first of all, THANK YOU SO MUCH! 🙂

To get started with this, you will want to do the following steps:

Open an issue, just to let maintainers know you would like to add a new language, so we can help 🙂
Add your reading language to build-system/homepage.js. As well as, add translations to the fields on the objects with your corresponding lnaguage key (For example, English(US) is "en-us").
Add your reading language to the shell/js/index.js.
See the steps outlined in Adding a new Reading Language (Translation) to an existing Example to start translating examples! They should appear on the homepage as you add them!

Improving the shell (the base website)

Improving the shell (E.g the language switcher or typos in the landing page and things), feel free to open a PR! For larger ideas or new sections of the site, it is recommended to open an issue first for discussion.

Any other contributions

For all other types of contributions (E.g perhaps you are a platform that wants to expand on Wasm By Example or something), please open an issue first describing the idea, and then we can work on a PR that works for the community at large.

Privacy

Google Analytics is used on Wasm By Example, and is only used to record Basic visit data, as the script is only loaded.

License

This work is copyright Aaron Turner and licensed under a Creative Commons Attribution 4.0 License.

Physiology-Informed ECG Delineation Based on Peak Prominence

This Python package implements the Peak Prominence ECG Delineator [1] and provides methods for ECG cleaning and R-peak detection [2], resulting in a complete delineation pipeline. This delineator allows for fast and precise detection of the positions, on- and offsets of morphology waves (e.g., P, R, T) in single or multi-lead ECG signals. An optional multi-lead correction procedure can be applied, leveraging information from all leads if available.

Advantages and Limits

This proposed approach achieves a highly explainable and interpretable wave selection by leveraging prominence information. Hence, wave detection only depends on physiologically motivated parameters chosen so that morphologies of interest are well represented and portrayed, yielding high $F_1$-scores and low errors on established Datasets in comparison to competing methods [1].

NOTE: This approach allows for further customization w.r.t to these parameters so that different parameter choices or other physiologically informed decision rules might result in higher performance or robustness regarding certain morphologies and heartbeat types. Even though, the utilized approach for on- and offset detection yielded great performance it is constrained by typical physiological boundaries. Developing novel prominence computation methods to robustly identify basepoints might therefore yield further improvements.

Installation

You can install the latest version of the prominence-delineator package from the Python Package Index (PyPI) by running:

pip install prominence-delineator

Complete Working Example

A complete working example is provided in example.ipynb, additionally the basic usage is depicted below.

Basic Usage

The ProminenceDelineator takes the sampling_frequency and optionally several physiological parameters as input. Then, R-peaks can be detected using any reliable R-peak detector or with the integrated method (applying the FastNVG [2] approach). Before detecting further waves, the required ECG cleaning can easily be performed by using .clean_ecg(ecg). Finally, morphology waves can be detected using .find_waves() or .find_waves_multilead() for single or multi-lead ECG signals, respectively.

Note: For multi-lead delineation, the ecg and rpeaks input should be in the form of a list or ndarray containing the ECG signals or R-peaks of each lead, respectively. The output will be given as a dictionary with keys denoting the wave type and values lists containing wave positions or lists of wave positions for all leads when processing multi-lead data.

Single Lead ECG Delineation

from prominence_delineator import ProminenceDelineator 

# Create an instance of the ProminenceDelineator
PromDelineator = ProminenceDelineator(sampling_frequency=fs)
# Detect the R-peaks in the ECG signal
rpeaks = PromDelineator.find_rpeaks(ecg)
# Clean the ECG signal
ecg = PromDelineator.clean_ecg(ecg)
# Find waves in the ECG signal using the ProminenceDelineator
waves = PromDelineator.find_waves(ecg, rpeaks=rpeaks)

Multi-Lead ECG Delineation

from prominence_delineator import ProminenceDelineator 

# Create an instance of the ProminenceDelineator
PromDelineator = ProminenceDelineator(sampling_frequency=fs)
# Detect the R-peaks in the multilead ECG signal
multilead_rpeaks = PromDelineator.find_rpeaks(ecg_multilead)
# Clean the ECG signal
ecg_multilead = PromDelineator.clean_ecg(ecg_multilead)
# Find waves in the ECG signal using the find_waves function
multilead_waves = PromDelineator.find_waves_multilead(ecg_multilead, rpeaks_multilead=multilead_rpeaks)

References

[1] Emrich, J., Gargano, A., Koka, T., and Muma, M. (2024), Physiology-Informed ECG Delineation Based on Peak Prominence.
[2] Emrich, J., Koka, T., Wirth, S. and Muma, M. (2023). Accelerated Sample-Accurate R-Peak Detectors Based on Visibility Graphs.

Physiology-Informed ECG Delineation Based on Peak Prominence

This Python package implements the Peak Prominence ECG Delineator [1] and provides methods for ECG cleaning and R-peak detection [2], resulting in a complete delineation pipeline. This delineator allows for fast and precise detection of the positions, on- and offsets of morphology waves (e.g., P, R, T) in single or multi-lead ECG signals. An optional multi-lead correction procedure can be applied, leveraging information from all leads if available.

Advantages and Limits

This proposed approach achieves a highly explainable and interpretable wave selection by leveraging prominence information. Hence, wave detection only depends on physiologically motivated parameters chosen so that morphologies of interest are well represented and portrayed, yielding high $F_1$-scores and low errors on established Datasets in comparison to competing methods [1].

NOTE: This approach allows for further customization w.r.t to these parameters so that different parameter choices or other physiologically informed decision rules might result in higher performance or robustness regarding certain morphologies and heartbeat types. Even though, the utilized approach for on- and offset detection yielded great performance it is constrained by typical physiological boundaries. Developing novel prominence computation methods to robustly identify basepoints might therefore yield further improvements.

Installation

You can install the latest version of the prominence-delineator package from the Python Package Index (PyPI) by running:

pip install prominence-delineator

Complete Working Example

A complete working example is provided in example.ipynb, additionally the basic usage is depicted below.

Basic Usage

The ProminenceDelineator takes the sampling_frequency and optionally several physiological parameters as input. Then, R-peaks can be detected using any reliable R-peak detector or with the integrated method (applying the FastNVG [2] approach). Before detecting further waves, the required ECG cleaning can easily be performed by using .clean_ecg(ecg). Finally, morphology waves can be detected using .find_waves() or .find_waves_multilead() for single or multi-lead ECG signals, respectively.

Note: For multi-lead delineation, the ecg and rpeaks input should be in the form of a list or ndarray containing the ECG signals or R-peaks of each lead, respectively. The output will be given as a dictionary with keys denoting the wave type and values lists containing wave positions or lists of wave positions for all leads when processing multi-lead data.

Single Lead ECG Delineation

from prominence_delineator import ProminenceDelineator 

# Create an instance of the ProminenceDelineator
PromDelineator = ProminenceDelineator(sampling_frequency=fs)
# Detect the R-peaks in the ECG signal
rpeaks = PromDelineator.find_rpeaks(ecg)
# Clean the ECG signal
ecg = PromDelineator.clean_ecg(ecg)
# Find waves in the ECG signal using the ProminenceDelineator
waves = PromDelineator.find_waves(ecg, rpeaks=rpeaks)

Multi-Lead ECG Delineation

from prominence_delineator import ProminenceDelineator 

# Create an instance of the ProminenceDelineator
PromDelineator = ProminenceDelineator(sampling_frequency=fs)
# Detect the R-peaks in the multilead ECG signal
multilead_rpeaks = PromDelineator.find_rpeaks(ecg_multilead)
# Clean the ECG signal
ecg_multilead = PromDelineator.clean_ecg(ecg_multilead)
# Find waves in the ECG signal using the find_waves function
multilead_waves = PromDelineator.find_waves_multilead(ecg_multilead, rpeaks_multilead=multilead_rpeaks)

References

[1] Emrich, J., Gargano, A., Koka, T., and Muma, M. (2024), Physiology-Informed ECG Delineation Based on Peak Prominence.
[2] Emrich, J., Koka, T., Wirth, S. and Muma, M. (2023). Accelerated Sample-Accurate R-Peak Detectors Based on Visibility Graphs.

pacmog

pacmog is a decoding library for the PCM file.
Designed for use in playing the PCM file embedded in microcontroller firmware.
Rust has an include_bytes! macro to embed the byte sequence in the program. Using it, PCM files can be embedded in firmware and used for playback.

Format	Status
WAV 16bit	✅
WAV 24bit	✅
WAV 32bit	✅
WAV 32bit float	✅
WAV 64bit float	✅
IMA ADPCM	✅
AIFF 16bit	✅
AIFF 24bit	✅
AIFF 32bit	✅
AIFF 32bit float	✅
AIFF 64bit float	✅

Example

cargo run --example beep

Low-level: Read the sample at an arbitrary position

use pacmog::PcmReader;

let wav = include_bytes!("../tests/resources/Sine440Hz_1ch_48000Hz_16.wav");
let mut input = &wav[..];
let reader = PcmReader::new(&mut input)?;
let specs = reader.get_pcm_specs();
let num_samples = specs.num_samples;
let num_channels = specs.num_channels;
println!("PCM info: {:?}", specs);

for sample in 0..num_samples {
    for channel in 0..num_channels {
        let sample_value: f32 = reader.read_sample(channel, sample)?;
        println!("{}", sample_value);
    }
}

High-level: PcmPlayer

use pacmog::{PcmPlayer, PcmReader};

let wav = include_bytes!("../tests/resources/Sine440Hz_1ch_48000Hz_16.wav");
let mut input = &wav[..];
let reader = PcmReader::new(&mut input)?;
let mut player = PcmPlayer::new(reader);
let specs = player.reader.get_pcm_specs();
let num_samples = specs.num_samples;
player.set_loop_playing(true);
let mut buffer: [f32; 2] = [0.0f32; 2];
let buf = buffer.as_mut_slice();

for sample in 0..num_samples {
   player.get_next_frame(buf)?;
}

no_std

pacmog works with no_std by default.
No setup is needed.

node-wxcrypto

微信消息加解密 nodejs 版本

Documentation • Change Log

安装

# 使用pnpm
$ pnpm i node-wxcrypto

# 使用yarn
$ yarn add node-wxcrypto

使用

引入和使用

require 引入

const { WxCrypto } = require('node-wxcrypto')

const wxCrypto = new WxCrypto(token, aesKey, appID, options)
const data = await wxCrypto.decrypt(encrypt, timestamp, nonce, options)

import 引入

import { WxCrypto } from 'node-wxcrypto'

const wxCrypto = new WxCrypto(token, aesKey, appID, options)
const data = await wxCrypto.decrypt(encrypt, timestamp, nonce, options)

使用配置

在实例化和加解密方法均支持传入 options: normalizeTags, buildXmlOptions, xmlOptions，加解密方法里面传入的 options 优先级更高。

normalizeTags 支持将 xml 属性由驼峰转下划线分隔的小写形式；buildXmlOptions 透传用于生成 xml 字符串的配置；xmlOptions 透传用于解析 xml 字符串的配置。

注意：normalizeTags 会全量覆盖 xmlOptions 里面的 tagNameProcessors 方法，如果想要自定义 tagNameProcessors，请不要传入 normalizeTags

持将 xml 属性由驼峰转下划线分隔的小写形式：ComponentVerifyTicket => component_verify_ticket

// normalizeTags可传入布尔值或者字符串，传入字符串时使用该字符串分隔，例如：normalizeTags = "__"，得到：`ComponentVerifyTicket => component__verify__ticket`
const wxCrypto = new WxCrypto(token, aesKey, appID, {
  normalizeTags: true,
  buildXmlOptions: {}, // 透传用于生成 xml 字符串的配置
  xmlOptions: {} // 透传用于解析 xml 字符串的配置
})
const data = await wxCrypto.decrypt(encrypt, timestamp, nonce, options)

API

详见：API说明文档

类型

问题和支持

Please open an issue here.

License

MIT

openmrs-esm-root-config

What is this?

openmrs-esm-root-config is an in-browser javascript module that serves as the single-spa root config for OpenMRS. It is the very first javascript module that is loaded, and controls which other modules are loaded and active for any particular URL.

How do I use it?

openmrs-esm-root-config is available on npm to be downloaded.

Usage (no customization)

To accept all OpenMRS defaults for modules, do the following:

npm install --save @openmrs/esm-root-config. Alternatively, go to get the files from jsdelivr.
Make the file node_modules/@openmrs/esm-root-config/dist/openmrs-esm-root-config.defaults.js available in your import map with the name @openmrs/esm-root-config.

Usage (with customization)

To customize which modules and single-spa applications are used, do the following:

Create a new repo that will be your custom root config. For example, ampath-esm-root-config.
npm install --save @openmrs/esm-root-config. Alternatively, go to get the files from jsdelivr.
Make your repo’s bundle available in your import map, with the name @openmrs/esm-root-config.

In your repo’s entry file, add the following code:

import { registerApplication, start } from 'single-spa';
import { registerAllCoreApplications } from '@openmrs/esm-root-config';

// Get all the core applications
registerAllCoreApplications();
// or: registerAllCoreApplicationsExcept(['@openmrs/esm-login', '@openmrs/esm-devtools'])

// Add your own application
registerApplication(
  'my-custom-app',
  () => System.import('my-custom-app'),
  location => location.pathname.startsWith('/custom')
)

// start everything up
start();

API

The following functions are exported from @openmrs/esm-root-config.

registerAllCoreApplications()

registerAllCoreApplications is a function that calls singleSpa.register() for each of the OpenMRS core applications.

Arguments

None

Return value

None (undefined)

Example

import { registerAllCoreApplications } from '@openmrs/esm-root-config';

registerAllCoreApplications();

registerAllCoreApplicationsExcept(applicationNames)

registerAllCoreApplicationsExcept allows you to specify an array of application names that you do not want to be registered from the set of all OpenMRS core applications.

Arguments

applicationNames (required): an array of string names that must correspond with the OpenMRS core applications that you don’t want registered.

Return value

None (undefined)

Example

import { registerAllCoreApplicationsExcept } from '@openmrs/esm-root-config';

registerAllCoreApplicationsExcept(['@openmrs/esm-login', '@openmrs/esm-primary-navigation']);

routePrefix(prefix, location)

routePrefix is a utility function that helps you implement single-spa activity functions. The word “route” refers to the browser’s url and the word “prefix” refers to a prefix in the pathname.

Arguments

prefix (required): A string that starts with a / character. Any time the browser’s url’s pathname starts with that url, your application will be active.
location (required): A Location object. You can just pass in the location given to your activity function.

Return value

A boolean that is true when the location matches the prefix, and false otherwise.

Example

See code examples.

import { registerApplication } from 'single-spa';
import { routePrefix } from '@openmrs/esm-root-config';

registerApplication('my-custom-app', () => System.import('my-custom-app'), isCustomAppActive);

function isCustomAppActive(location) {
  return routePrefix('/custom', location);
}

routeRegex(regex, location)

routeRegex is a utility function that helps you implement single-spa activity functions. The word “route” refers to the browser’s url and the word “prefix” refers to a prefix in the pathname.

Arguments

regex (required). A regular expression that will be matched against the location’s pathname.
location (required). A Location object. You can just pass in the location given to your activity function.

Return value

A boolean that is true when the location matches the prefix, and false otherwise.

Example

import { registerApplication } from 'single-spa';
import { routeRegex } from '@openmrs-esm-root-config';

registerApplication('my-custom-app', () => System.import('my-custom-app'), isCustomAppActive);

function isCustomAppActive(location) {
  return routeRegex(/^patient\/.+\/dashboard/, location);
}

SNU-2D-ProgrammingTools-IDE-

By:

Seanpm2001 / SNU Programming Tools, Et; Al.

Top

`README.md`

Read this article in a different language

Read this description in a different language:

Current language is: English (US) (translations may need to be corrected to fix English replacing the correct language)

[Click/tap here to expand/collapse the language switcher list]

🌐 List of languages

Translations in languages other than English are machine translated and are not yet accurate. No errors have been fixed yet as of February 5th 2021. Please report translation errors here make sure to backup your correction with sources and guide me, as I don’t know languages other than English well (I plan on getting a translator eventually) please cite wiktionary and other sources in your report. Failing to do so will result in a rejection of the correction being published.

Note: due to limitations with GitHub’s interpretation of markdown (and pretty much every other web-based interpretation of markdown) clicking these links will redirect you to a separate file on a separate page that isn’t my GitHub profile page. You will be redirected to the seanpm2001/seanpm2001 repository, where the README is hosted.

Translations are done with Google Translate due to limited or no support for the languages I need in other translation services like DeepL and Bing Translate. For some reason, the formatting (links, dividers, bolding, italics, etc.) is messed up in various translations. It is tedious to fix, and I do not know how to fix these issues in languages with non-latin characters, and right to left languages (like Arabic) extra help is needed in fixing these issues

Index

00.0 – Top

00.1 – Title

00.2 – Read this article in a different language

00.3 – Index

04.1 – Pre-history

04.2 – Alpha History

04.3 – Beta History

04.4 – Modern History

05.0 – Copying

06.0 – Credits

07.0 – Installation

08.0 – Version history

09.0 – Software status

10.0 – Sponsor info

11.0 – Contributers

12.0 – Issues

12.1 – Current issues

12.2 – Past issues

12.3 – Past pull requests

12.4 – Active pull requests

13.0 – Resources

14.0 – Contributing

15.0 – About README

16.0 – README Version history

17.0 – Footer

17.9 – End of file

SNU_2D_ProgrammingTools_IDE_

The Programming language IDE submodule for SNU Programming Tools (2D Mode)

About

See above. This repository is the IDE for that comes with SNUs programming tool set.

Wiki

Click/tap here to view this projects Wiki

If the project has been forked, the Wiki was likely removed. Luckily, I include an embedded version. You can view it here.

History

Write about this projects history here.

Pre-history

No pre-history to show for this project.

Alpha history

No Alpha history to show for this project.

Beta history

No Beta history to show for this project.

Modern history

No Modern history to show for this project.

Copying

View the copying license for this project here (if you haven’t built the project yet with the makefile, here is the original link: COPYINGL

Please note that you also have to follow the rules of the GNU General Public License v3 (GPL3) which you can view here

Credits

View the credits file for this project and see the people who got together to make this project by clicking/tapping here

Installation

View the installation instructions file for this project here

Requirements: Read the instructions for more info, and get the latest up-to-date instructions here

Sponsor info

You can sponsor this project if you like, but please specify what you want to donate to. See the funds you can donate to here

You can view other sponsor info here

Try it out! The sponsor button is right up next to the watch/unwatch button.

Version history

Version history currently unavailable

No other versions listed

Software status

All of my works are free some restrictions. DRM (Digital Restrictions Management) is not present in any of my works.

This sticker is supported by the Free Software Foundation. I never intend to include DRM in my works.

I am ussing the abbreviation “Digital Restrictions Management” instead of the more known “Digital Rights Management” as the common way of addressing it is false, there are no rights with DRM. The spelling “Digital Restrictions Management” is more accurate, and is supported by Richard M. Stallman (RMS) and the Free Software Foundation (FSF)

This section is used to raise awareness for the problems with DRM, and also to protest it. DRM is defective by design and is a major threat to all computer users and software freedom.

Image credit: defectivebydesign.org/drm-free/…

Contributers

Currently, I am the only contributer. Contributing is allowed, as long as you follow the rules of the CONTRIBUTING.md file.

seanpm2001 – x commits (As of 2021, date, at xx:xx pm)

No other contributers.

Issues

Current issues

None at the moment
No other current issues

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Past issues

None at the moment
No other past issues

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Past pull requests

None at the moment
No other past pull requests

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Active pull requests

None at the moment
No other active pull requests

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Resources

Here are some other resources for this project:

Project language file A)

Join the discussion on GitHub

No other resources at the moment.

Contributing

Contributing is allowed for this project, as long as you follow the rules of the CONTRIBUTING.md file.

Click/tap here to view the contributing rules for this project

About README

File type: Markdown document (*.md)

File version: 1 (date)

Line count: 0,415

README version history

Version 1 (Date)

Changes:

Started the file

Added the title section

Added the index

Added the about section

Added the Wiki section

Added the version history section

Added the issues section.

Added the past issues section

Added the past pull requests section

Added the active pull requests section

Added the contributors section

Added the contributing section

Added the about README section

Added the README version history section

Added the resources section

Added a software status section, with a DRM free sticker and message

Added the sponsor info section

ITERATION 5

Updated the title section

Updated the index

Added the history section

Updated the file info section

Updated the file history section

Updated the footer

ITERATION 6

Updated the title section

Fixed and update template links

Updated the index

Added the copying section

Added the credits section

Added the installation section

Updated the resources section

Updated the contributors section

Added the technical notes section

Updated the footer

Updated the file info section

Updated the file history section

No other changes in version 1

Version 2 (Coming soon)

Changes:

Coming soon

No other changes in version 2

You have reached the end of the README file

( Back to top | Exit to GitHub | Exit to Bing | Exit to DuckDuckGo | Exit to Ecosia )

Blog

Website

Purpose

TODO

Development mode

REPL

Building for production

Getting Started with Create React App

Available Scripts

npm start

npm test

npm run build

npm run eject

Learn More

wasm-by-example

Table of Contents

Motivation

Getting Started

One-time Setup

Branch (do this each time you want a new branch)

Building & Running the project

Contributing

Examples

Creating a new Example

Adding a new Programming Language to an existing Example

Adding a new Reading Language (Translation) to an existing Example

Adding a completely new Reading Language (Translation)

Improving the shell (the base website)

Any other contributions

Privacy

License

Physiology-Informed ECG Delineation Based on Peak Prominence

Advantages and Limits

Installation

Complete Working Example

Basic Usage

Single Lead ECG Delineation

Multi-Lead ECG Delineation

References

Physiology-Informed ECG Delineation Based on Peak Prominence

Advantages and Limits

Installation

Complete Working Example

Basic Usage

Single Lead ECG Delineation

Multi-Lead ECG Delineation

References

pacmog

Example

Low-level: Read the sample at an arbitrary position

High-level: PcmPlayer

no_std

node-wxcrypto

Documentation • Change Log

安装

使用

引入和使用

使用配置

API

类型

问题和支持

License

openmrs-esm-root-config

What is this?

How do I use it?

Usage (no customization)

Usage (with customization)

API

registerAllCoreApplications()

Arguments

Return value

Example

registerAllCoreApplicationsExcept(applicationNames)

Arguments

Return value

Example

routePrefix(prefix, location)

Arguments

Return value

Example

`npm start`

`npm test`

`npm run build`

`npm run eject`

`README.md`