Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “Extractor”
2008
Suppose we have access to a source of randomness that isn’t completely random, but does contain a lot of randomness. Is there a way to convert this source into a source of truly random bits? Ideally we’d like an algorithm (called an Extractor) that does something like this: weak source
Cited by 0
Pedro Escaleira · Open MIND · 2026
ℹ️ NoteThis repository is part of the PoliFlow framework.For more details, please refer to: https://doi.org/10.5281/zenodo.18632240 PoliFlow Extractor This repository contains two implementations of the PolifFlow Extractor: one for the CNCF Serverless Workflow v0.8 and another for the PoliFlow Language. Extractor for the CNCF Serverless Workflow This Extractor is stored within the serverless-workflow/src/ directory. After installing the requirements (from the requirements.txt file), it can be executed using the following command: python main.py -w [path to workflow file] -s [paths to the subflows files (if there are any)] Using this command, the user can specify the source file with the workflow descriptor and the files with the subflows descriptors (if there are multiple, these must be separated with a space; if there are no subflows, the user does not need to provide the -s flag). The extracted allowed paths are saved in the directory serverless-workflow/src/extracted/ in a new directory with the name of the workflow file (without the extension). For example, if the workflow file is application.sw.yaml, the allowed paths will be saved in serverless-workflow/src/extracted/application/. In this directory, the Extractor will create multiple JSON and YAML files, each pair for each entity (function, event, callback) present in the workflow. The JSON file content can then be used for the PoliFlow Enforcer. The YAML file has the same constructs as the corresponding JSON file but allows the user to more easily understand the paths extracted. Furthermore, we also give the possibility of using the -d flag. If it is set, the Extractor will consider loop iterations as being dependent on the previous ones. However, by default (if the flag is not provided), the loop iterations are considered independent, which is the default behavior of the CNCF Serverless Workflow v0.8. The directory serverless-workflow/test-workflows/ stores multiple examples of serverless workflows. These were already extracted, and the allowed paths are saved in serverless-workflow/src/extracted/. Nevertheless, an example of using the Extractor with one of these workflows is: python main.py -w ../test-workflows/loop.sw.yaml -s ../test-workflows/subloop.sw.yaml Note The requirements in requirements.txt might not be enough. This Extractor script uses the most up to date development version of the CNCF Serverless Workflow Python SDK at the date of writing (commit ab7b6d4d6998be2add8af7494faadd2bb16d1e94). Extractor for the PoliFlow Language The second Extractor implementation in this repository is for the PoliFlow Language. In this implementation, we considered that it would be used for direct-call-based applications, i.e., applications where functions call other functions or services directly (without relying on workflows or events). Therefore, it outputs both rules for inbound and outbound calls. This implementation is stored in the poliflow-language/src/ directory. As with the other Extractor, the requirements are stored in the requirements.txt file. However, it also requires the PoliFlow language package to be installed. The easiest way of doing so is to clone that repository locally and then, in the virtual environment of the Extractor, run: pip install [directory to the cloned PoliFlow language repository] Then, the Extractor can be run with the following command: python main -w [path to workflow file] Then, as with the previous Extractor, it saves the allowed paths in YAML and JSON files within the poliflow-language/src/extracted/ directory, under a directory with the workflow file name.
Cited by 0Open access
Crump, William E., Jr. · The Portal to Texas History (University of North Texas) · 1886
Patent for a new and improved cork extractor. This design consists, "with the side-slitted cork, of the double-wire extractor having loop ends engaging the slits of the cork and extending beyond the same and the securing-wire passing through said loop ends and around the shoulder of the bottle-neck" (lines 47-52).
Cited by 0Open access
Chang-Diaz, Franklin R. · NASA STI Repository (National Aeronautics and Space Administration)
This invention relates to an apparatus and method of removing desirable constituents from an infusible material by infusion extraction. A piston operating in a first chamber draws a solvent into the first chamber where it may be heated, and then moves the heated solvent into a second chamber containing the infusible material, where infusion extraction takes place. The piston then moves the solvent containing the extract through a filter into the first chamber, leaving the extraction residue in the second chamber. The method is applicable to operation in low or micro-gravity environments.
Cited by 0Open access
Digital Collections (East Carolina University)
Turned wooden handle, narrows at center where metal band attaches to rod perpendicular to handle; angled bend at rod center; swinging hook at end of rod; ridges on edges of hook.\n
Cited by 0
http://www.internet-soft.com/extractor.htm · Bulletin of Miscellaneous Information (Royal Gardens Kew) · 2004
This program allows you to download entire Web sites and save them on your hard drive for browsing offline. Sites are saved on your hard drive with their directory structure intact. This can download up to one hundred Web pages, graphics and other files at once. You can even download files from more than one Web site by typing in URLs. Many filtering options are also available, so you can download only the content that you want.
Cited by 0
Kenneth A. Kappy · Clinics in Perinatology · 1981
Cited by 5
Melcher, John C. · The Portal to Texas History (University of North Texas) · 1886
Patent for a new and improved honey extractor. This design "consists in, first, the combination, in a honey-extractor, of the pail, a suitable support for the revolving frame, a revolving frame which is made widest at its top, a perforated cross-piece which extends across the pail, and a spool or drum which is attached to the top of the vertical shaft . . . [and] second, the support which extends across the top of the pail or can, and which is provided with a series of holes so that it can be adapted to cans of different sizes" (lines 13-24).
Cited by 0Open access
Amnon Ta-Shma, et al. · 2004
We study error-correcting codes for highly noisy channels. For example, every received signal in the channel may originate from some half of the symbols in the alphabet. Our main conceptual contribution is an equivalence between error-correcting codes for such channels and extractors. Our main technical contribution is a new explicit error-correcting code based on Trevisan’s extractor that can handle such channels, and even noisier ones. Our new code has polynomial-time encoding and polynomial-time soft-decision decoding. We note that Reed–Solomon codes cannot handle such channels, and our study exposes some limitations on list decoding of Reed–Solomon codes. Another advantage of our equivalence is that when the Johnson bound is restated in terms of extractors, it becomes the well-known Leftover Hash Lemma. This yields a new proof of the Johnson bound which applies to large alphabets and soft decoding. Our explicit codes are useful in several applications. First, they yield algorithms to extract many hardcore bits using few auxiliary random bits. Second, they are the key tool in a recent scheme to compactly store a set of elements in a way that membership in the set can be determined by looking at only one bit of the representation. Finally, they are the basis for the recent construction of high-noise, almost-optimal rate list-decodable codes over large alphabets [1].
Cited by 0
Lewandowski, Piotr, Crombag, Chloe, Rodrigues de Miranda, Benjamin et al. · Research Publications (Maastricht University) · 2022
This library contains functions to get ECHR data.
Cited by 0Open access
Williams, Winfield B. · The Portal to Texas History (University of North Texas) · 1911
Cited by 0Open access
George L. Carpenter · The Portal to Texas History (University of North Texas) · 1918
Patent for sleeve-extractor with improvements, including illustrations.
Cited by 0Open access
Hunt, Thomas M. · The Portal to Texas History (University of North Texas) · 1892
Patent for a staple extractor used for removing wire from the posts of wire fences. Includes illustrations.
Cited by 0Open access
Hiesermann, William F. · The Portal to Texas History (University of North Texas) · 1922
Patent for automobile extractors that are simple yet effective when used for automobile. This automobile extractor is also not expensive to create.
Cited by 0Open access
Mendiratta, Raul Miguel Gomes · Open Repository of the University of Porto (University of Porto) · 2021
Cited by 0Open access
Scientific American · 1883
Cited by 0
Cathriner, Joseph · The Portal to Texas History (University of North Texas) · 1901
Patent for "an improved extractor for the bungs of casks and barrels of all kinds, so that the same can be quickly and conveniently removed from the bung-hole" (lines 8-11).
Cited by 0Open access
Williams, Winfield B. · The Portal to Texas History (University of North Texas) · 1913
Patent for an improved juice extractor including a way to remove the strainer for easy cleaning or replacement, a swivel for the handle, and an overall more efficient device.
Cited by 0Open access
Pedro Escaleira · Zenodo (CERN European Organization for Nuclear Research) · 2026
ℹ️ NoteThis repository is part of the PoliFlow framework.For more details, please refer to: https://doi.org/10.5281/zenodo.18632240 PoliFlow Extractor This repository contains two implementations of the PolifFlow Extractor: one for the CNCF Serverless Workflow v0.8 and another for the PoliFlow Language. Extractor for the CNCF Serverless Workflow This Extractor is stored within the serverless-workflow/src/ directory. After installing the requirements (from the requirements.txt file), it can be executed using the following command: python main.py -w [path to workflow file] -s [paths to the subflows files (if there are any)] Using this command, the user can specify the source file with the workflow descriptor and the files with the subflows descriptors (if there are multiple, these must be separated with a space; if there are no subflows, the user does not need to provide the -s flag). The extracted allowed paths are saved in the directory serverless-workflow/src/extracted/ in a new directory with the name of the workflow file (without the extension). For example, if the workflow file is application.sw.yaml, the allowed paths will be saved in serverless-workflow/src/extracted/application/. In this directory, the Extractor will create multiple JSON and YAML files, each pair for each entity (function, event, callback) present in the workflow. The JSON file content can then be used for the PoliFlow Enforcer. The YAML file has the same constructs as the corresponding JSON file but allows the user to more easily understand the paths extracted. Furthermore, we also give the possibility of using the -d flag. If it is set, the Extractor will consider loop iterations as being dependent on the previous ones. However, by default (if the flag is not provided), the loop iterations are considered independent, which is the default behavior of the CNCF Serverless Workflow v0.8. The directory serverless-workflow/test-workflows/ stores multiple examples of serverless workflows. These were already extracted, and the allowed paths are saved in serverless-workflow/src/extracted/. Nevertheless, an example of using the Extractor with one of these workflows is: python main.py -w ../test-workflows/loop.sw.yaml -s ../test-workflows/subloop.sw.yaml Note The requirements in requirements.txt might not be enough. This Extractor script uses the most up to date development version of the CNCF Serverless Workflow Python SDK at the date of writing (commit ab7b6d4d6998be2add8af7494faadd2bb16d1e94). Extractor for the PoliFlow Language The second Extractor implementation in this repository is for the PoliFlow Language. In this implementation, we considered that it would be used for direct-call-based applications, i.e., applications where functions call other functions or services directly (without relying on workflows or events). Therefore, it outputs both rules for inbound and outbound calls. This implementation is stored in the poliflow-language/src/ directory. As with the other Extractor, the requirements are stored in the requirements.txt file. However, it also requires the PoliFlow language package to be installed. The easiest way of doing so is to clone that repository locally and then, in the virtual environment of the Extractor, run: pip install [directory to the cloned PoliFlow language repository] Then, the Extractor can be run with the following command: python main -w [path to workflow file] Then, as with the previous Extractor, it saves the allowed paths in YAML and JSON files within the poliflow-language/src/extracted/ directory, under a directory with the workflow file name.
Cited by 0Open access
jplie · OpenEdition (OpenEdition) · 2002
Die "Seitenblicke" vom Akademie.de-Newsletter sind doch immer für etwas gut. In der heutigen Ausgabe kommt (u.a. neben dem netbib-Leser/innen bekannten Hinweis auf den "Autoreply-Terror" in URecht) ein Hinweis auf einen Keyword Extractor, welcher Schlüsselbegriffe aus Texten herausziehen kann. Der Versuch mit netbib ergab die Schlüsselworte: Kommentar, Bibliothek, Beitrag, Literatur, weblog, Fun und librarian.
Cited by 0