vignettes/sample-scripts-external-genotype-simulation.Rmd
sample-scripts-external-genotype-simulation.Rmd
There are a number of different strategies to generate genotype data for genetic association studies.
Simple bi-allelic SNPs without structure: In the most simple case and assuming bi-allelic SNPs, each SNP is simulated from a binomial distribution with two trials and probability equal to the given allele frequencies. This simple approach does not simulate any dependency between the genotypes as is observed with LD structure in the genome. Simple bi-allelic SNPs can be simulated with PhenotypeSimulator::simulateGenotypes or via PLINK [1]. For large datasets (~ 1 million SNPs), simulation via PLINK is recommended.
Coalescent approaches: Coalescent methods simulate genealogical events backward in time. These events typically include the coalescence of two sequences into a single ancestral lineage, recombination within a sequence or migration between populations. A coalescent-based approach to simulate whole genome data is implemented in GENOME [2] and its output format is supported as an input format for PhenotypeSimulator.
Forward-time approaches: Forward-time simulation methods evolve a population forward in time, subject to arbitrary genetic and demographic factors [3]. Several algorithms are available, many of which allow customisation by building the simulation scheme in R or python, hence the output format of the genotypes can be specified by the user. PhenotypeSimulator offers reading genotypes from delimited-files and as such, any genotypes generated by these programmes can be read (e.g. MetaSim [4] or simuPop [5]).
Resampling approaches: Resampling-based approaches combine existing genotype data into the genotypes of the simulated samples, thereby retaining allele frequency and LD patterns [6]. A standard resampling-based approach that uses common genotype formats (common for the oxford genetics format) is Hapgen2 and an example usage is given below.
Examples for genotype simulation via PLINK, GENOME and Hapgen2 are given below. The corresponding data can be found in the extdata folder.
Download PLINK and create a folder for the PLINK output files. The example below uses PLINK to simulate 1000 SNPs, with allele frequencies between 0 and 1 for 100 controls and 0 cases. PhenotypeSimulator::readStandardGenotypes reads the resulting .bim, .fam, .bed files.
# Serves as output directory for simulation and parameter file
mkdir -p ~/PhenotypeSimulator/inst/extdata/genotypes/plink
cd ~/PhenotypeSimulator/inst/extdata/genotypes/plink
# Write paramter file to simulate 1000 SNPs, with allele frequencies between 0
# and 1 for 100 controls and 0 cases
echo -e "1000\tSNP\t0.00\t1.00\t1.00\t1.00" > plink_sim_par.txt
plink --simulate plink_sim_par.txt \
--simulate-ncases 0 \
--simulate-ncontrols 100 \
--out genotypes_plink
Download GENOME and create a folder for the GENOME output files. The example below uses GENOME to simulate genetic data for a population comprised of three sub-populations with 30, 30 and 40 samples. The simulated POPULATION PROFILE, SNP positions and the genotypes are all saved in genotypes_genome.txt. PhenotypeSimulator::readStandardGenotypes reads genotype information by parsing this output file and extracting the samples information following the line ‘Samples:’
Download hapgen2, hapgen example files and the 1000Genomes data from the impute2 webpage as starting point for the resampling-based genotype simulation with hapgen2. For formating of the 1000Genomes data, have a look at this vignette. The example files contain example haplotypes (ex.haps), legend files (ex.leg) map (ex.map) and TagSNP files (ex.tags). The following examples simulates genotype data for 100 controls and 0 cases with 1000 SNPs from chromosome 1. PhenotypeSimulator::readStandardGenotypes reads the resulting .gen and .samples files.
# contains ex.leg file and serves as output directory
mkdir -p ~/PhenotypeSimulator/inst/extdata/genotypes/hapgen
cd ~/PhenotypeSimulator/inst/extdata/genotypes/hapgen
# contains 1000Genomes haplotype data used for sampling
hapdir=/path/to/CEU.0908.impute.files
hapgen2 -m $hapdir/genetic_map_chr1_combined_b37.txt \
-l ex.leg \
-h $hapdir/chr1.ceu_subset.hap \
-o genotypes_hapgen \
-n 100 0 \
-dl 45162 0 0 0 \
-no_haps_output
1. Chang CC, Chow CC, Tellier LC, Vattikuti S, Purcell SM, Lee JJ. Second-generation PLINK: rising to the challenge of larger and richer datasets. GigaScience. 2015;4: 7. doi:10.1186/s13742-015-0047-8
2. Liang L, Zollner S, Abecasis GR. GENOME: a rapid coalescent-based whole genome simulator. Bioinformatics. 2007;23: 1565–1567. doi:10.1093/bioinformatics/btm138
3. Peng B, Amos CI. Forward-time simulation of realistic samples for genome-wide association studies. BMC Bioinformatics. 2010;11: 442. doi:10.1186/1471-2105-11-442
4. Strand AE. Metasim 1.0: An individual-based environment for simulating population genetics of complex population dynamics. Molecular Ecology Notes. 2002;2: 373–376. doi:10.1046/j.1471-8286.2002.00208.x
5. Peng B, Kimmel M. simuPOP: a forward-time population genetics simulation environment. Bioinformatics. 2005;21: 3686–3687. doi:10.1093/bioinformatics/bti584
6. Wright FA, Huang H, Guan X, Gamiel K, Jeffries C, Barry WT, et al. Simulating association studies: a data-based resampling method for candidate regions or whole genome scans. Bioinformatics. 2007;23: 2581–2588. doi:10.1093/bioinformatics/btm386


This is a simple app to interface with an API that implements a tf-idf algorithm whose goal is to extract the most relevant, or important terms from a text document. You can paste your text into the form, provide a title, and optionally choose a category that you think best represents your document. After submitting, you will receive a list of the n most important terms.
Check this page out for an explanation of how it works, and what happens to your docuent.


{% extends 'base.html' %} {% load static %} {% block main %}
Interested in analyzing this data yourself? Each symptom tracking report has data available via JSON endpoints. You can use this page's own JSON endpoint to automate data retrieval from these: {% url 'reports:public_json' %}
Please share your visualizations and discoveries with us! People are excited to hear what you've done – we'd love to share what others have done. (One place to connect is the #quantifiedflu channel in the Open Humans community Slack. You can use this site to create an account in the Slack: slackin.openhumans.org)
{% if request.user.openhumansmember.account.publish_symptom_reports %}A big thank-you to contributors that have shared their data with the project. 💖 Sharing data is optional; if you're a contributor, log in to manage this in your account settings.
{% endif %}Click the links below to explore symptom reports.
| Date | Member | Reports | Sick Incident | Data sources | {% for member in object_list %}
|---|


Go to the source code of this file.
Functions | |
| bool | fuzzy_control_IO_callback (mofs::FuzzyControl_IO::Request &request, mofs::FuzzyControl_IO::Response &response) |
| int | main (int argc, char **argv) |
Variables | |
| char | controller [100] |
| char * | fileController |
| char * | fileRules |
| mofs::MOFSModel | flc |
| main file of the mofs-ROS package More... | |
| const char * | location = "/home/miguelolivaresmendez/code/fuerte_workspace/sandbox/mofs/include/FLC/" |
| char | rules [100] |
| char * | serviceName |
| bool fuzzy_control_IO_callback | ( | mofs::FuzzyControl_IO::Request & | request, |
| mofs::FuzzyControl_IO::Response & | response | ||
| ) |
| mofs::MOFSModel flc |
main file of the mofs-ROS package
Created on: 27 May 2013 Author: Miguel A. Olivares-Mendez SnT - University of Luxembourg Automation Research Group
mofs was previously a C++ library and now a ROS package developed by Miguel Angel Olivares-Mendez at the Computer Vision Group - Universidad Politecnica de Madrid and at Automation Research Group
Used under the conditions of ROS
any doubts don't hesitate to contact me: migue l.ol ivare smen dez@u ni.l u
| const char* location = "/home/miguelolivaresmendez/code/fuerte_workspace/sandbox/mofs/include/FLC/" |


New Slippery Toilet Coating ‘Stops Poo Sticking’
by Charlie CocksedgeWe’ve all seen it – the phantom poo-er who somehow manages to leave nasty marks all over the bowl.
Do they squat differently? Is their aim slightly off? Or did they just eat something that came out the other end with such violent force they had no choice but to pebbledash the porcelain?
Who knows. One thing’s for sure though, it’s not a pretty sight using the toilet afterwards.
So, like flushing a sparkly loo after you’ve just doused it in bleach, it’s with welcome relief researchers in the US say they’ve created an ‘ultra-slippery toilet coating’, which would not only eliminate the stubborn brown stains, but help save huge quantities of water in the process.
According to scientists at Penn State University, their new development not only cuts the amount of water needed to flush away excrement by 90%, but prevents bacteria from building up while also reducing associated odours.
The researchers say more than 141 billion litres of water are used everyday just to flush toilets. The new, slippery coating could help reduce that figure by 50%.
Speaking to Penn State News, Tak-Sing Wong, Wormley Early Career Professor of Engineering and associate professor of mechanical engineering and biomedical engineering, said:
Our team has developed a robust bio-inspired, liquid, sludge- and bacteria-repellent coating that can essentially make a toilet self-cleaning.
Co-developed by Jing Wang, the product is a two-step spray that would be applied directly to a ceramic toilet bowl. The first spray, composed of molecularly-grafted polymers, would build up an ‘extremely smooth and liquid-repellent foundation’.
Wang said:
When it dries, the first spray grows molecules that look like little hairs, with a diameter of about 1,000,000 times thinner than a human’s.
The second spray then coats those tiny ‘hairs’ with a layer of lubricant, making the surface even more slippery.
Wang added:
When we put that coating on a toilet in the lab and dump synthetic fecal matter on it, [the synthetic fecal matter] just completely slides down and nothing sticks to [the toilet].
The researchers believe the spray-on coating would last for around 500 flushes before it needed to be reapplied. Not only would the spray reduce water waste, but the team hope it could make an impact in the developing world or regions experiencing water scarcity, where it could be used to reduce harmful bacteria in waterless toilets.
Wang said:
Poop sticking to the toilet is not only unpleasant to users, but it also presents serious health concerns.
Tak-Sing Wong added:
Our goal is to bring impactful technology to the market so everyone can benefit.
Just make sure it only gets sprayed in the toilet and not, for example, on the floor or down the stairs, yeah?
Charlie Cocksedge is a journalist at UNILAD. He graduated from the University of Manchester with an MA in Creative Writing, where he learnt how to write in the third person, before getting his NCTJ. His work has also appeared in such places as The Guardian, PN Review and the bin.


New Enzyme
Introduction
To create a custom enzyme, simply provide an enzyme name and the cleavage
pattern as comma separated lists of (one letter) amino acids. It is also
recommended to provide a PSI-MS CV term, as this will be used in, for
example, the mzIdentML export.
If you encounter any issues
with enzymes in SearchGUI, please contact the developers.
Go to top of page


Unique id
Remove all topics with all listeners
Emit event and call subscribed listeners
Topic name
Array of arguments
Number of listeners called
Check if listener with provided token exists
Token of desired listener
Topic which has to contain the listener
Error with message or Listener
Remove listener with provided token
Token of the listener
Topic which has to contain the listener
True if the listener is successfully removed and false if it is not found
Remove topic with all listeners
Topic name
True if the topic is successfully removed and false if it is not found
Pub/Sub for internal event scheduling. All functions are for protected usage. Sub class can use them for implementation of event dispaching.
id Unique Eventer id


1 2 3 4 5 6 7 8 9 10 11 12
13 14 15
16
17 package xdc.runtime;
18
19 /*!
20 * ======== System ========
21 * Basic system services
22 *
23 * This module provides basic low-level "system" services; e.g.,
24 * character output, `printf`-like output, and exit handling.
25 *
26 * This module is gated and other modules use its gate via the
27 * `{@link Gate#enterSystem}` and `{@link Gate#leaveSystem}`. The `System`
28 * gate must be enterable by any thread in a multi-threaded environments. For
29 * example, in many real-time multi-threaded environments some types of
30 * threads, such as Interrupt Service Routines (ISRs), are not allowed to call
31 * operations that block the caller. In such an environment, either the
32 * `System` gate must disable all interrupts or ISRs must never call a function
33 * in the `xdc.runtime` package.
34 */
35
36 @Template("./System.xdt")
37 @Gated
38 @ModuleStartup
39 @DirectCall
40 module System {
41
42 /*!
43 * ======== AtexitHandler ========
44 * `System`'s atexit function prototype.
45 *
46 * Functions of this type can be added to the list of functions that
47 * are executed during application termination.
48 *
49 * @see #atexit
50 */
51 typedef Void (*AtexitHandler)(Int);
52
53 /*!
54 * ======== STATUS_UNKNOWN ========
55 * Unknown exit status value
56 *
57 * When the program exits by calling {@link #exit System_exit()} the
58 * `System`'s `atexit` functions are passed the status value passed to
59 * `System_exit()`. However, if the program exits using
60 * the ANSI C Standard Library `exit()` function, the `System`'s `atexit`
61 * functions are passed `System_STATUS_UNKNOWN`; ANSI C `atexit`
62 * functions are not passed the exit status.
63 */
64 const Int STATUS_UNKNOWN = 0xCAFE;
65
66 /*!
67 * ======== AbortFxn ========
68 * System abort function prototype.
69 *
70 * Functions of this type can be plugged into `System`'s abort function
71 * that will be executed during abnormal application termination.
72 *
73 * @see #abort
74 */
75 typedef Void (*AbortFxn)();
76
77 /*!
78 * ======== ExitFxn ========
79 * System exit function prototype.
80 *
81 * Functions of this type can be plugged into `System`'s exit function that
82 * will be executed during normal application termination.
83 *
84 * @see #exit
85 */
86 typedef Void (*ExitFxn)(Int);
87
88 /*! @_nodoc */
89 @XmlDtd
90 metaonly struct Module_View {
91 String atexitHandlers[];
92 Int numAtexitHandlers;
93 };
94
95 /*! @_nodoc */
96 metaonly struct PathEntryView {
97 String entry;
98 }
99
100 /*!
101 * ======== rovViewInfo ========
102 * @_nodoc
103 */
104 @Facet
105 metaonly config xdc.rov.ViewInfo.Instance rovViewInfo =
106 xdc.rov.ViewInfo.create({
107 viewMap: [
108 ['XDCROOT',
109 {
110 type: xdc.rov.ViewInfo.MODULE_DATA,
111 viewInitFxn: 'viewInitXdcRoot',
112 structName: 'PathEntryView'
113 }
114 ],
115 ['XDCPATH',
116 {
117 type: xdc.rov.ViewInfo.MODULE_DATA,
118 viewInitFxn: 'viewInitXdcPath',
119 structName: 'PathEntryView'
120 }
121 ],
122 ]
123 });
124
125 /*!
126 * ======== A_cannotFitIntoArg ========
127 * Assert that the target's `Float` type fits in an `IArg`
128 *
129 * This assertion is triggered when the `%f` format specifier is used,
130 * the argument treated as an `IArg`, but for the current target
131 * `sizeof(Float)` > `sizeof(IArg)`.
132 */
133 config Assert.Id A_cannotFitIntoArg = {
134 msg: "A_cannotFitIntoArg: sizeof(Float) > sizeof(Arg)"
135 };
136
137 /*!
138 * ======== extendedFormats ========
139 * Optional conversions supported by `{@link #printf System_printf}`
140 *
141 * This string specifies the set of optional argument conversion
142 * specifiers required by the application. By reducing the number of
143 * optional conversions understood by the `System {@link #printf}`
144 * methods, it is possible to significantly reduce the code size
145 * footprint of the `System` module. This configuration parameter
146 * enables one to balance `printf` functionality against code size
147 * footprint.
148 *
149 * The format of this string is simply a concatenated list of the desired
150 * conversion specifiers (with the leading `%` character). For example,
151 * to support both `%f` and `%$L` set `extendedFormats` to `"%$L%f"`.
152 *
153 * To disable all optional converstions, set `extendedFormats` to `null`
154 * or the empty string ("").
155 *
156 * For a complete list of supported extensions, see the
157 * `{@link #printf System_printf}` "Extended_Format_Specifiers" section.
158 *
159 * @a(Note)
160 * If an optional conversion is used by some part of the application and
161 * it is not specified in `extendedFormats`, the conversion character(s)
162 * and leading `%` are treated as ordinary characters to be output. As
163 * a result, all subsequent arguments will almost certainly be converted
164 * using the wrong conversion specifier!
165 *
166 * @see #printf
167 */
168
169 metaonly config String extendedFormats = "%$L%$S%$F";
170
171 /*!
172 * ======== SupportProxy ========
173 * The implementation module of the low-level system functions.
174 *
175 * This configuration parameter allows one to "bind" a different
176 * implementation of the low-level services required to implement
177 * `System`.
178 * @p(code)
179 * var System = xdc.useModule("xdc.runtime.System");
180 * var SysStd = xdc.useModule("xdc.runtime.SysStd");
181 * System.SupportProxy = SysStd;
182 * @p
183 *
184 * If this parameter is not set, it defaults to `{@link SysMin}`.
185 */
186
187 proxy SupportProxy inherits ISystemSupport;
188
189 /*!
190 * ======== maxAtexitHandlers ========
191 * Maximum number of dynamic atexit handlers allowed in the system.
192 *
193 * Maximum number of `System` `atexit` handlers set during runtime via
194 * the `{@link System#atexit}` function.
195 *
196 */
197
198 config Int maxAtexitHandlers = 8;
199
200 /*!
201 * ======== abortFxn ========
202 * Abort handler function
203 *
204 * This configuration parameter allows user to plug in their own abort
205 * function. By default `{@link #abortStd}` which calls ANSI C Standard
206 * `abort()` is plugged in. Alternatively `{@link #abortSpin}` can be
207 * plugged which loops infinitely.
208 *
209 */
210
211 config AbortFxn abortFxn = System.abortStd;
212
213 /*!
214 * ======== exitFxn ========
215 * Exit handler function
216 *
217 * This configuration parameter allows user to plug in their own exit
218 * function. By default `{@link #exitStd}` which calls ANSI C Standard
219 * `exit()` is plugged in. Alternatively `{@link #exitSpin}` can be
220 * plugged which loops infinitely.
221 *
222 */
223
224 config ExitFxn exitFxn = System.exitStd;
225
226 /*!
227 * ======== abort ========
228 * Print a message and abort currently running executable.
229 *
230 * This is called when an executable abnormally terminates.
231 * The `System` gate is entered, the
232 * `{@link #SupportProxy}`'s `abort` function is called
233 * and then `{@link #abortFxn}` is called.
234 * No exit functions bound via `System_atexit()` or the ANSI C Standard
235 * Library `atexit()` functions are executed.
236 *
237 * @param(str) abort message (not a format string)
238 */
239
240 Void abort(CString str);
241
242 /*!
243 * ======== abortStd ========
244 * ANSI C Standard implementation of abortFxn function
245 *
246 * This function calls ANSI C Standard `abort()` to terminate currently
247 * running executable. This function is used by default in
248 * `{@link #abortFxn}`.
249 *
250 */
251
252 Void abortStd();
253
254 /*!
255 * ======== abortSpin ========
256 * Lightweight implementation of abortFxn function
257 *
258 * This functions loops indefinitely. This can used as an alternative
259 * `{@link #abortFxn}` when a lightweight implementation is
260 * required instead of the ANSI C Standard `abort()`.
261 */
262
263 Void abortSpin();
264
265 /*!
266 * ======== atexit ========
267 * Add an exit handler
268 *
269 * `System_atexit` pushes `handler` onto an internal stack of functions
270 * to be executed when system is exiting (e.g. `System_exit` is called).
271 * Up to `{@link #maxAtexitHandlers}` functions can be specified in this
272 * manner. During the exit processing, the functions are popped off the
273 * internal stack and called until the stack is empty.
274 *
275 * The `System` gate is entered before the `System_atexit` functions
276 * are called.
277 *
278 * The `SupportProxy`'s `{@link ISystemSupport#exit}` function is called
279 * after all the atexit functions are called.
280 *
281 * @param(handler) the `AtexitHandler` to invoke during system
282 * exit processing.
283 *
284 * @a(returns)
285 * If `FALSE` is returned, the exit handler was not added and it will
286 * not be called during an exit.
287 */
288
289 Bool atexit(AtexitHandler handler);
290
291 /*!
292 * ======== atexitMeta ========
293 * Add an exit handler during configuration
294 *
295 * This is the static counterpart to `System_atexit()`. This method can
296 * be used to add `atexit` handlers at configuration time. These
297 * handlers do not count against the `maxAtexitHandlers`.
298 *
299 * @param(handler) the `AtexitHandler` to invoke during system
300 * exit processing.
301 */
302
303 metaonly Void atexitMeta(AtexitHandler handler);
304
305 /*!
306 * ======== exit ========
307 * Exit currently running executable.
308 *
309 * This function is called when an executable needs to terminate
310 * normally. This function processes all functions bound via
311 * `System_atexit` and then calls `{@link #exitFxn}`. The
312 * `{@link #SupportProxy}`'s `exit` function is called during this time.
313 *
314 * @param(stat) exit status to return to calling environment.
315 */
316
317 Void exit(Int stat);
318
319 /*!
320 * ======== exitStd ========
321 * Implements an `exitFxn` function
322 *
323 * This function calls ANSI C Standard `exit()` to terminate currently
324 * running executable normally. This function is used by default in
325 * `{@link #exitFxn}`.
326 *
327 * @param(stat) exit status to return to calling environment.
328 */
329
330 Void exitStd(Int stat);
331
332 /*!
333 * ======== exitSpin ========
334 * Implements an `exitFxn` function
335 *
336 * This functions loops indefinitely. This can used as an alternative
337 * `{@link #exitFxn}` when a light weight implementation is
338 * required instead of the ANSI C Standard `exit()`.
339 *
340 * @param(stat) exit status to return to calling environment.
341 */
342
343 Void exitSpin(Int stat);
344
345 /*!
346 * ======== processAtExit ========
347 * Processes all functions bound via `System_atexit`
348 *
349 * This function is called by `System_exit` to process all functions
350 * bound via `System_atexit`. User can add this to ANSI C standard
351 * `atexit` function so that all functions bound via `System_atexit` are
352 * processed when ANSI C standard `exit` function is called.
353 *
354 * @param(stat) exit status which will be passed to all functions
355 * processed.
356 */
357
358 Void processAtExit(Int stat);
359
360 /*!
361 * ======== putch ========
362 * Output a single character
363 *
364 * The `{@link #SupportProxy}`'s `putch` function is called
365 * by this function.
366 *
367 * @param(ch) character to be output.
368 */
369
370 Void putch(Char ch);
371
372 /*!
373 * ======== flush ========
374 * Flush standard System I/O
375 *
376 * This function causes any buffered output characters are "written"
377 * to the output device.
378 *
379 * The `{@link #SupportProxy}`'s `flush` function is called
380 * by this function.
381 */
382
383 Void flush();
384
385 /*!
386 * ======== printf ========
387 * A smaller faster printf
388 *
389 * This function behaves much like the ANSI C Standard `printf`
390 * but does not support the full range of format strings specified by
391 * the C Standard. In addition, several non-standard format specifiers
392 * are recognized.
393 *
394 * @a(Format Strings)
395 * The format string is a character string composed of zero or
396 * more directives: ordinary characters (not %), which are copied
397 * unchanged to the output stream; and conversion specifications, each of
398 * which results in fetching zero or more subsequent arguments. Each
399 * conversion specification is introduced by the character %, and ends
400 * with a conversion specifier. In between there may be (in this order)
401 * zero or more flags, an optional minimum field width, an optional
402 * precision and an optional length modifier.
403 *
404 * @a(Flags)
405 * The following flags are supported:
406 * @p(dlist)
407 * - `-`
408 * The converted value is to be left adjusted on the field
409 * boundary (the default is right justification.)
410 * - `0`
411 * The value should be zero padded. For d, i, o, u, and x
412 * conversions, the converted value is padded on the left
413 * with zeros rather than blanks.
414 * @p
415 *
416 * @a(Field Width)
417 * The optional field width specifier is a decimal digit string (with
418 * nonzero first digit) specifying a minimum field width. If the
419 * converted value has fewer characters than the field width, it will
420 * be padded with spaces on the left (or right, if the left-adjustment
421 * flag has been given). Instead of a decimal digit string one may
422 * write `*` to specify that the field width is given in the next
423 * argument. A negative field width is taken as a '-' flag followed
424 * by a positive field width.
425 *
426 * @a(Precision)
427 * The optional precision specifier is a period ('.') followed by an
428 * optional decimal digit string. Instead of a decimal digit string
429 * one may write `*` to specify that the precision is given in the
430 * next argument which must be of type int.
431 *
432 * If the precision is given as just '.', or the precision is
433 * negative, the precision is taken to be zero. This gives the
434 * minimum number of digits to appear for d, i, o, u, and x
435 * conversions, or the maximum number of characters to be printed from
436 * a string for s conversions.
437 *
438 * @a(Length Modifiers)
439 * The optional length modifier is a single character from the following
440 * list.
441 * @p(dlist)
442 * - `l`
443 * A following integer conversion corresponds to a long int
444 * or unsigned long int argument
445 *
446 * @p
447 *
448 * @a(Conversion Specifiers)
449 * The following conversion specifiers are supported.
450 * @p(dlist)
451 * - `d`, `i`
452 * signed integer
453 * - `u`
454 * unsigned decimal
455 * - `x`
456 * unsigned hex
457 * - `o`
458 * unsigned octal
459 * - `p`
460 * pointer (@ + hex num)
461 * - `c`
462 * character
463 * - `s`
464 * string
465 * @p
466 * @a(Extended Conversion Specifiers)
467 * The following conversion specifiers are optionally supported. See
468 * the `{@link #extendedFormats}` configuration parameter for more
469 * information about how to enable these conversion specifiers.
470 *
471 * @p(dlist)
472 * - `f`
473 * decimal floating point.
474 * - `$`
475 * non-ANSI conversion prefix. This prefix indicates that the
476 * next character identifies a non-ANSI standard conversion. See
477 * the next section for details.
478 * @p
479 *
480 * @a(Non ANSI Conversion Specifiers)
481 * Among the extended conversion specifiers are unique specifiers which
482 * are not part of ANSI printf. These are specified using a $, for
483 * example %$L.
484 *
485 * These unique specifiers do not support the minimum field width
486 * attribute. Certain specifiers have additional restrictions; see below.
487 *
488 * @p(dlist)
489 * - '$L'
490 * The argument is treated as a pointer to a `{@link Types#Label}`
491 * and is converted to an appropriate string.
492 * - '$F'
493 * Displays a file and line number; used for displaying the call
494 * site. This specifier consumes two arguments, the file and line
495 * number, in that order. See an example below.
496 * - '$S'
497 * The argument is treated as a format string, and is recursively
498 * formatted using any following arguments. This specifier does
499 * not support the use of the "precision" field for specifying
500 * maximum string length.
501 * @p
502 *
503 * The following are example uses of the %$F and %$S format specifiers.
504 *
505 * In this call using %$F, the compiler recognizes these symbols and
506 * fills in the file and line number.
507 * @p(code)
508 * System_printf("%$F", __FILE__, __LINE__);
509 * @p
510 * This call outputs, for example,
511 * @p(code)
512 * "MyCode.c", line 35:
513 * @p
514 * Here is an example using %$S, passing a recursive format string.
515 * @p(code)
516 * System_printf("Msg: %$S", "My msg, code: %d", 5);
517 * @p
518 * This outputs:
519 * @p(code)
520 * Msg: My msg, code: 5
521 * @p
522 *
523 * @param(fmt) a 'printf-style' format string
524 *
525 * @a(returns)
526 * `printf` returns the number of characters printed.
527 */
528
529 Int printf(CString fmt, ...);
530
531 /*!
532 * ======== aprintf ========
533 * `{@link #printf}` where all optional arguments are `IArg`s
534 *
535 * This function will treat each argument as though it was widened to be
536 * of type `IArg` prior to being passed to the `{@link #printf}` function
537 *
538 * @see #printf
539 */
540
541 Int aprintf(CString fmt, ...);
542
543 /*!
544 * ======== sprintf ========
545 * Write formated output to a character buffer
546 *
547 * This function is identical to `{@link #printf}` except that the
548 * output is copied to the specified character buffer `buf` followed
549 * by a terminating '\0' character.
550 *
551 * @param(buf) a character output buffer
552 * @param(fmt) a 'printf-style' format string
553 *
554 * @a(returns)
555 * `sprintf` returns the number of characters output not including the
556 * '\0' termination character.
557 */
558
559 Int sprintf(Char buf[], CString fmt, ...);
560
561 /*!
562 * ======== asprintf ========
563 * `{@link #sprintf}` where all optional arguments are `IArg`s
564 *
565 * This function will treat each argument as though it was widened to be
566 * of type `IArg` prior to being passed to the `{@link #sprintf}`
567 * function.
568 *
569 * @see #sprintf
570 */
571
572 Int asprintf(Char buf[], CString fmt, ...);
573
574 /*!
575 * ======== vprintf ========
576 * A VaList printf
577 *
578 * This function is identical to `{@link #printf}` except that its
579 * arguments are passed via a VaList (a "varargs list").
580 *
581 * @param(fmt) a standard 'printf-style' format string.
582 * @param(va) an args list that points to the arguments referenced
583 * by the fmt string
584 *
585 * @a(returns)
586 * `vprintf` returns the number of characters output.
587 */
588
589 Int vprintf(CString fmt, VaList va);
590
591 /*!
592 * ======== avprintf ========
593 * `{@link #vprintf}` where all optional arguments are `IArg`s
594 *
595 * This function will treat each argument as though it was widened to be
596 * of type `IArg` prior to being passed to the `{@link #vprintf}`
597 * function.
598 *
599 * @see #vprintf
600 */
601
602 Int avprintf(CString fmt, VaList va);
603
604 /*!
605 * ======== vsprintf ========
606 * A `VaList` sprintf
607 *
608 * This function is identical to `{@link #sprintf}` except that
609 * its arguments are passed via a `VaList` (a "varargs list").
610 *
611 * @param(buf) a character output buffer
612 * @param(fmt) a standard '`printf`-style' format string.
613 * @param(va) an arguments list that points to the arguments referenced
614 * by the `fmt` string
615 *
616 * @a(returns)
617 * `vsprintf` returns the number of characters output.
618 */
619
620 Int vsprintf(Char buf[], CString fmt, VaList va);
621
622 /*!
623 * ======== avsprintf ========
624 * `{@link #vsprintf}` where all optional arguments are `IArg`s
625 *
626 * This function is identical to `{@link #sprintf}` except that
627 * its arguments are passed via a `VaList` (a "varargs list").
628 *
629 * This function will treat each argument as though it was widened to be
630 * of type `IArg` prior to being passed to the `vsprintf` function
631 *
632 * @see #vsprintf
633 */
634
635 Int avsprintf(Char buf[], CString fmt, VaList va);
636
637 /*!
638 * ======== snprintf ========
639 * Write formated output to a character buffer
640 *
641 * This function is identical to `{@link #sprintf}` except that at most
642 * `n` characters are copied to the specified character buffer `buf`.
643 * If n is zero, nothing is written to character buffer. Otherwise,
644 * output characters beyond the `n` - 1 are discarded rather than
645 * being written to the character buf, and a null character is written
646 * at the end of the characters written into the buffer.
647 *
648 * @param(buf) a character output buffer
649 * @param(n) the maximum number of characters, including '\0', written to
650 * the output buffer `buf`
651 * @param(fmt) a 'printf-style' format string
652 *
653 * @a(returns)
654 * `snprintf` returns the number of characters that would have been
655 * written had `n` been sufficiently large, not counting the terminating
656 * '\0' character. However, if extended conversion specifiers are used
657 * (@see #printf), the return value may be lower than the number of
658 * characters that would be written had `n` been sufficiently large.
659 */
660
661 Int snprintf(Char buf[], SizeT n, CString fmt, ...);
662
663 /*!
664 * ======== vsnprintf ========
665 * A `VaList` snprintf
666 *
667 * This function is identical to `{@link #snprintf}` except that
668 * its arguments are passed via a `VaList` (a "varargs list").
669 *
670 * @param(buf) a character output buffer
671 * @param(n) at most number of characters including '\0' written to
672 * output buffer
673 * @param(fmt) a standard '`printf`-style' format string.
674 * @param(va) an arguments list that points to the arguments referenced
675 * by the `fmt` string
676 *
677 * @a(returns)
678 * `vsnprintf` returns the number of characters that would have been
679 * written had `n` been sufficiently large, not counting the terminating
680 * '\0' character. However, if extended conversion specifiers are used
681 * (@see #printf), the return value may be lower than the number of
682 * characters that would be written had `n` been sufficiently large.
683 */
684
685 Int vsnprintf(Char buf[], SizeT n, CString fmt, VaList va);
686
687 internal:
688
689 /*! struct used to keep track of state during doPrint */
690 struct ParseData {
691 Int width;
692 Bool lFlag;
693 Bool lJust;
694 Int precis;
695 UInt len;
696 Int zpad;
697 Char *end;
698 Bool aFlag;
699 Char *ptr;
700 };
701
702 /*! typedef for generated functions to process extended formats */
703 typedef Int (*ExtendFxn)(Char **, CString *, VaList *, ParseData *);
704
705 /*! config parameter used to call generated function */
706 readonly config ExtendFxn extendFxn = '&xdc_runtime_System_printfExtend__I';
707
708 709 710 711 712 713 714 715 716 717
718 Int printfExtend (Char **bufp, CString *fmt, VaList *va, ParseData *parse);
719
720 /*!
721 * ======== exitFxns ========
722 * @_nodoc
723 * List of functions statically plugged to be called at exit
724 *
725 */
726 metaonly config AtexitHandler exitFxns[];
727
728 /*!
729 * ======== mprintf ========
730 * @_nodoc
731 */
732 function mprintf(fmt, args);
733
734 /*!
735 * ======== doPrint ========
736 * @_nodoc
737 */
738 Int doPrint(Char buf[], SizeT n, CString fmt, VaList *pva, Bool aFlag);
739
740 /*!
741 * ======== lastFxn ========
742 * @_nodoc
743 *
744 * Calls atexit() after all other modules have been initialized
745 * This used to be done in System_Module_startup() but this caused
746 * problems since atexit() uses a heap which isn't necessarily
747 * initialized.
748 */
749 Void lastFxn();
750
751 /*!
752 * ======== putchar ========
753 * @_nodoc
754 *
755 * Write character ch to the buffer and, if the buffer pointer is
756 * non-`NULL`, update the buffer pointer.
757 *
758 * Keeps track of the number of characters written into the buffer by
759 * modifying bufsize `n`. Atmost, `n` - 1 characters are written.
760 */
761 Void putchar(Char **bufp, Char ch, SizeT *n);
762
763 /*!
764 * ======== rtsExit ========
765 * @_nodoc
766 */
767 Void rtsExit();
768
769 /*!
770 * ======== atexitDone ========
771 * @_nodoc
772 */
773 Bool atexitDone();
774
775 /*!
776 * ======== Module_State ========
777 * @_nodoc
778 */
779 struct Module_State {
780 AtexitHandler atexitHandlers[];
781 Int numAtexitHandlers;
782 };
783 }
784 785 786
787


Salmon Cookies
Sales Information Page
Sales statistics as of
Staffing Estimates
The table below estimates store staffing based on the following assumptions:
- Each store should have a minimum of 2 employess on staff at all times
- Each employee can produce on average 20 cookies per hour


INTRO
WebSocket n2o_stream is implemented cowboy_websocket_handler behaviour for WS protocol and cowboy_http_handler handler for XHR protocol. Both protocols are supported in single file. This module is only for using N2O with cowboy web server.
API
The n2o_proto protocol loop is compatible with cowboy and emqttd versions of N2O. The main purpose of this API is to embed N2O into your functional endpoint. In other cases it's called automatically by configuration.
websocket_info({ text | binary, binary() }, term(), term()) -> #reply{}.
The stream function is dedicated for cowboy version of n2o.
websocket_handle({ text | binary, binary() }, term(), term()) -> #reply{}.
This function is called on message arrival.
websocket_init(term(), term(), term()) -> #reply{}.
This function is called on init.
websocket_terminate(term(), term(), term()) -> #reply{}.
This function is called on terminate.
info(term(), term(), term()) -> #reply{}.
The info function is dedicated for HTTP XHR fallback.


Congrats!
Voting campaign [[${campaign_name}]] is over, [[${coins}]] will be listed on Nimera exchange shortly.


| ID | Title | State | Author | Assignee | Labels |
|---|
This page shows GitHub issues in a simple form.
The filter box above accepts a set of filters, each separated by space.
You can /sort on id, recent, or closed.
Pressing enter saves the current search. Pressing esc leaves the text input area.
Clicking an issue title displays details for the issue including comments. Pressing n or j moves to the next issue, and p or k move to the previous one.
Pressing esc closes the issue view, ' focuses search, and c clears the search.


I had just recently had my medication upped from 300mg to 400mg a day and really hadn't noticed much of a difference. Since I had no problems previously going out and partying while on Wellbutrin, it didn't even cross my mind to be concerned. I only found out after the fact that Wellbutrin can reduce your alcohol tolerance.
I'll preface this by saying that I am by no means a stranger to alcohol. I'm a college student and have been drinking since I've been 15 or 16.  Even so, I tend to drink around 7 or 8 drinks on average when I go out and I'm able to maintain myself pretty well. I've never had a full out blackout like I had this night.
At the second party we were at that night, I'm guessing I was on my 4th or 5th drink. The last thing I remember is talking to some familiar faces and working my way through the party (I was aware of my drink, I know it wasn't drugged. That's not how these people roll anyway.). Almost complete blackness after that except for brief moments of consciousness where I remember puking and having my friends help my back home with only one shoe and a disconcerting amount of blood on my white coat. (I think it was from my toe? Not sure.) I had no idea what was going on, where I was, I didn't understand anything. However, it was pretty hard to think at all so oh well.
Once we got back to my dorm I remember my friends telling me that if I didn't stop puking they'd have to call an ambulance. I laid on my side thought that I was probably going to die, go to sleep and simply not wake up. Apparently I kept telling them I was fine and they should go home, but they stayed around and tried to figure out if I would keep breathing. In all honesty, if it was someone else I probably would've wanted them to get medical attention, but I'm very glad that I was just left to be and didn't incur a bunch of hospital bills.
It does say on the bottles not to drink alcohol while on the medication, but I really hadn't noticed any side effects while drinking on doses up to 300mg. That extra 100mg makes a startingly huge difference I suppose (combined with the fact it completely shreds your appetite). I don't think you have to completely abstain while on bupropion (although shrinks would prefer us major depressives to quit in general), but be conscious that it can bite you in the ass very quickly. It seems that just one extra drink can just push you off the edge. Be careful if you must.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


If you require any more information or have any questions about our Terms and Conditions, please feel free to contact us by email at Issa.
These terms and conditions govern your use of this website; by using this website, you accept these terms and conditions in full and without reservation. If you disagree with these terms and conditions or any part of these terms and conditions, you must not use this website.
Unless otherwise stated, www.Issa.be and/or its licensors own the intellectual property rights published on this website and materials used on www.Issa.be. Subject to the license below, all these intellectual property rights are reserved.
You may view, download for caching purposes only, and print pages, files or other content from the website for your own personal use, subject to the restrictions set out below and elsewhere in these terms and conditions.
You must not:
Where content is specifically made available for redistribution, it may only be redistributed within your organisation.
You must not use this website in any way that causes, or may cause, damage to the website or impairment of the availability or accessibility of www.Issa.be or in any way which is unlawful, illegal, fraudulent or harmful, or in connection with any unlawful, illegal, fraudulent or harmful purpose or activity.
You must not use this website to copy, store, host, transmit, send, use, publish or distribute any material which consists of (or is linked to) any spyware, computer virus, Trojan horse, worm, keystroke logger, rootkit or other malicious computer software.
You must not conduct any systematic or automated data collection activities on or in relation to this website without www.Issa.be's express written consent.
This includes:
You must not use this website or any part of it to transmit or send unsolicited commercial communications.
You must not use this website for any purposes related to marketing without the express written consent of www.Issa.be.
Access to certain areas of this website is restricted. www.Issa.be reserves the right to restrict access to certain areas of this website, or at our discretion, this entire website. www.Issa.be may change or modify this policy without notice.
If www.Issa.be provides you with a user ID and password to enable you to access restricted areas of this website or other content or services, you must ensure that the user ID and password are kept confidential. You alone are responsible for your password and user ID security..
www.Issa.be may disable your user ID and password at www.Issa.be's sole discretion without notice or explanation.
In these terms and conditions, “your user content” means material (including without limitation text, images, audio material, video material and audio-visual material) that you submit to this website, for whatever purpose.
You grant to www.Issa.be a worldwide, irrevocable, non-exclusive, royalty-free license to use, reproduce, adapt, publish, translate and distribute your user content in any existing or future media. You also grant to www.Issa.be the right to sub-license these rights, and the right to bring an action for infringement of these rights.
Your user content must not be illegal or unlawful, must not infringe any third party's legal rights, and must not be capable of giving rise to legal action whether against you or www.Issa.be or a third party (in each case under any applicable law).
You must not submit any user content to the website that is or has ever been the subject of any threatened or actual legal proceedings or other similar complaint.
www.Issa.be reserves the right to edit or remove any material submitted to this website, or stored on the servers of www.Issa.be, or hosted or published upon this website.
www.Issa.be's rights under these terms and conditions in relation to user content, www.Issa.be does not undertake to monitor the submission of such content to, or the publication of such content on, this website.
This website is provided “as is” without any representations or warranties, express or implied. www.Issa.be makes no representations or warranties in relation to this website or the information and materials provided on this website.
Without prejudice to the generality of the foregoing paragraph, www.Issa.be does not warrant that:
Nothing on this website constitutes, or is meant to constitute, advice of any kind. If you require advice in relation to any legal, financial or medical matter you should consult an appropriate professional.
www.Issa.be will not be liable to you (whether under the law of contact, the law of torts or otherwise) in relation to the contents of, or use of, or otherwise in connection with, this website:
These limitations of liability apply even if www.Issa.be has been expressly advised of the potential loss.
Nothing in this website disclaimer will exclude or limit any warranty implied by law that it would be unlawful to exclude or limit; and nothing in this website disclaimer will exclude or limit the liability of Issa in respect of any:
By using this website, you agree that the exclusions and limitations of liability set out in this website disclaimer are reasonable.
If you do not think they are reasonable, you must not use this website.
You accept that, as a limited liability entity, www.Issa.be has an interest in limiting the personal liability of its officers and employees. You agree that you will not bring any claim personally against www.Issa.be's officers or employees in respect of any losses you suffer in connection with the website.
Without prejudice to the foregoing paragraph, you agree that the limitations of warranties and liability set out in this website disclaimer will protect www.Issa.be's officers, employees, agents, subsidiaries, successors, assigns and sub-contractors as well as www.Issa.be.
If any provision of this website disclaimer is, or is found to be, unenforceable under applicable law, that will not affect the enforceability of the other provisions of this website disclaimer.
You hereby indemnify www.Issa.be and undertake to keep www.Issa.be indemnified against any losses, damages, costs, liabilities and expenses (including without limitation legal expenses and any amounts paid by www.Issa.be to a third party in settlement of a claim or dispute on the advice of www.Issa.be's legal advisers) incurred or suffered by www.Issa.be arising out of any breach by you of any provision of these terms and conditions, or arising out of any claim that you have breached any provision of these terms and conditions.
Without prejudice to www.Issa.be's other rights under these terms and conditions, if you breach these terms and conditions in any way, www.Issa.be may take such action as www.Issa.be deems appropriate to deal with the breach, including suspending your access to the website, prohibiting you from accessing the website, blocking computers using your IP address from accessing the website, contacting your internet service provider to request that they block your access to the website and/or bringing court proceedings against you.
www.Issa.be may revise these terms and conditions from time-to-time. Revised terms and conditions will apply to the use of this website from the date of the publication of the revised terms and conditions on this website. Please check this page regularly to ensure you are familiar with the current version.
www.Issa.be may transfer, sub-contract or otherwise deal with www.Issa.be's rights and/or obligations under these terms and conditions without notifying you or obtaining your consent.
You may not transfer, sub-contract or otherwise deal with your rights and/or obligations under these terms and conditions.
If a provision of these terms and conditions is determined by any court or other competent authority to be unlawful and/or unenforceable, the other provisions will continue in effect. If any unlawful and/or unenforceable provision would be lawful or enforceable if part of it were deleted, that part will be deemed to be deleted, and the rest of the provision will continue in effect.
These terms and conditions, together with www.Issa.be's Privacy Policy constitute the entire agreement between you and www.Issa.be in relation to your use of this website, and supersede all previous agreements in respect of your use of this website.
These terms and conditions will be governed by and construed in accordance with the laws of , and any disputes relating to these terms and conditions will be subject to the exclusive jurisdiction of the courts of .


This is some text blah blah blah lorem ipseukldsfj dkljsf jkldferio
fdjl dkjf kljds lkjdfs lkjdsf lkjdsf dfskjlfsd lkjdfs lkjfds fdslkjfsd lkj


Home
About
Contact
A Text Adventurer Game
Title of Story
Lorem ipsum text chunk.
What will you do?
First Choice.
Second Choice.
Third Choice.
Fourth Choice.
Undo last choice.
Lost? Search through Doggo's mind.


3.4. Java Keystores and Truststores
Java Keystore File for TLS
Access to the Presto coordinator must be through HTTPS when using Kerberos and LDAP authentication. The Presto coordinator uses a Java Keystore file for its TLS configuration. These keys are generated using keytool and stored in a Java Keystore file for the Presto coordinator.
The alias in the keytool command line should match the principal that the Presto coordinator will use.
You’ll be prompted for the first and last name. Use the Common Name that will be used in the certificate. In this case, it should be the unqualified hostname of the Presto coordinator. In the following example, you can see this in the prompt that confirms the information is correct:
keytool -genkeypair -alias presto -keyalg RSA -keystore keystore.jks
Enter keystore password:
Re-enter new password:
What is your first and last name?
[Unknown]: presto-coordinator.example.com
What is the name of your organizational unit?
[Unknown]:
What is the name of your organization?
[Unknown]:
What is the name of your City or Locality?
[Unknown]:
What is the name of your State or Province?
[Unknown]:
What is the two-letter country code for this unit?
[Unknown]:
Is CN=presto-coordinator.example.com, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
[no]: yes
Enter key password for <presto>
(RETURN if same as keystore password):
Java Truststore File for TLS
Truststore files contain certificates of trusted TLS/SSL servers, or of Certificate Authorities trusted to identify servers. For securing access to the Presto coordinator through HTTPS the clients can configure truststores. For the Presto CLI to trust the Presto coordinator, the coordinator’s certificate must be imported to the CLI’s truststore.
You can either import the certificate to the default Java truststore, or to a custom truststore. You should be careful if you choose to use the default one, since you may need to remove the certificates of CAs you do not deem trustworthy.
You can use keytool to import the certificate to the truststore.
In the example, we are going to import presto_certificate.cer
to a custom
truststore presto_trust.jks
, and you will get a prompt asking if the certificate
can be trusted or not.
$ keytool -import -v -trustcacerts -alias presto_trust -file presto_certificate.cer -keystore presto_trust.jks -keypass <truststore_pass>
Troubleshooting
Java Keystore File Verification
Verify the password for a keystore file and view its contents using keytool.
$ keytool -list -v -keystore /etc/presto/presto.jks


Toggle navigation
Installation
Tutorials
Specification
References
Scala (Scaladoc)
Python (Sphinx)
GitHub repos
Redirect to current specification
Current specification is
version 1.0
.


|
Sensor Fusion Library
0.4.0
Orientation sensing for Espressif (ESP32, ESP8266) processors
|
An easy-to-use interface to the NXP Sensor Fusion version 7 library algorithms. More...
#include "sensor_fusion_class.h"
#include <Stream.h>
#include <stdint.h>
#include "sensor_fusion/sensor_fusion.h"
#include "sensor_fusion/control.h"
#include "sensor_fusion/driver_sensors.h"
#include "sensor_fusion/status.h"
Variables | |
| const float | kDegToRads = PI / 180.0 |
| To convert Degrees to Radians, multiply by this constant. | |
| const float | kCelsiusToKelvin = 273.15 |
| To convert degrees C to K, add this constant. | |
| const float | kGeesToMPerSS = 9.80665 |
| To convert acceleration in G to m/s^2, multiply by this constant. | |
An easy-to-use interface to the NXP Sensor Fusion version 7 library algorithms.
It is configured to work with the Adafruit breakout board #3643 using the NXP FXOS8700 magnetometer/accelerometer and FXAS21002 gyroscope sensor ICs, but can be modified to work with other sensors having an I2C interface. With additional modification, it can also work with SPI interface sensors.
A C++ class provides simple access to the most common sensor fusion functions, but it is also possible to directly interface with the library methods contained in the underlying C files, which are based on those provided by NXP in their version 7.20 release.


The Ethical Forum is pleased to bring you our online magazine, Ethical
Inquiries (and Where to Find Them)! Our Chief Editor, Grace Chen works in
lieu with the rest of our publication branch to put out this magazine once a
semester. Our focus is to use this platform to report on and comment on current
events, environmental, social, and political topics with moral and philosophical
considerations. No matter what area of life it is, ethical considerations remain
relevant in how we treat other people, how we make decisions that affect ourselves
and others and how we balance commitments and others’ perspectives.
This magazine has a team of writers and artists who put out artwork, critical
essays, and other creative works in each issue, but also takes one-time
submissions from anyone who would like to be featured. In order to facilitate more
discourse and interest in ethics and philosophy, there are no submission barriers
based on grade or school, and we are always seeking to expand our audience and
welcome new contributors.
Feel free to submit articles for consideration at this
link.


High Priest Innocentin:
Thank you! Your efforts have definitely put a crimp in the evil plans of the Pagans!


| DOSE: |
15 mg |
oral |
2C-E |
(powder / crystals) |
2c-e is a chemical that I long had an interest in, especially after exploring the ~400ug realm of LSD.
After acquiring the actual substance and dosing out a few capsules, in the range of 10-20mg, because I had heard about how subjective dosing was with this substance. At first, I can't deny that there was some fear and anxiety about taking an RC for the first time, but from what I had read, I figured 2c-e as about as harmless as 2c-b if used responsibly, and it seems (at least, from experience) I was right. I havent seen
any research on long term effects (but I assume they are similar to 2c-b's), but I found that I didn't experience any of the discomfort I had read about the substance, and found it to be fairly light for such a magical, and powerful substance.
I should note that the experiences I am writing about are from oral ingestion, and it seems this substance becomes a psychedelic monolith when used nasally even with doses of 5mg or so, the experience also differs, and becomes much more intense with this Method of Administration (MoA) (and if 2c-t-7 is any indicator, possibly deadly at unexpectedly 'lowish' doses, as 2c-e seems to have a very steep dose/response curse with either of these two MoA's... but exponentially more steep nasally).
[please note that the following was written on a 15mg dose of 2c-e administered orally, towards the end of the trip]
'At this point, my mind is overwhelmed. LSD had never taken as much of a toll on my mind, because it did all the work for me. 2c-e taught me how to 'bend the spoon' myself
and essentially, once you learn how to 'bend' one image, the mind remembers the path. The most striking was: we paused when a fractal art video was interweaving the image of a sun with a twisted smile, but then fading it into the image of a snail. We happened to pause at the transitional period. The mind does not know which image to show, the snail or the sun, so it alternates between the two, then simultaneously sends both of them at us. (AMAZING) The visuals seemed to be completely synchronized (W and I).'
The first time I had taken it, the setting was indoors at a safe place with friends, at least until we knew what we were dealing with. My mindset was actually not the best it could have been, because of my anxiety due to taking a drug I had no prior experience with. However, much like MDMA, when it started to come up, any fear had begun to fade, and even during the most absurdly surreal moments, thought wasn't much more clouded than a strong roll (perhaps 200mg). I've found in reality, if the user knows their limits, and doses it accurately (*extremely* important), there isn't much to be afraid of. Somehow, even though it is of a large series of different synthetic PEA's, with unknown long term effects, this always feels like a substance I can trust.
2c-e taught me more than Lucy had, even at some pretty high doses. And strangely, 2c-e comes on fairly mildly, only to overwhelm me with the bulk of the trip when I'm not expecting it.  As I write this, my mental state is close to sober, yet the screen is distorting. its all just a matter of time, a few seconds. I can do it right now. The spoon WILL BEND. This makes me realize: with enough time and concentration, anything will bend. This can be dangerous. I see the strings.
Crash: almost none. no notable discomfort during the trip either. The next day felt similar to the post-lsd feel. A little scattered, but a definitely pleasant 'afterglow' was present. (sleeping isn't particularly hard either, although at first 2ce felt stimulating) Threshold effects were felt within 15 minutes, but the 'real' trip only hit about 2-3 hours later, with ++ visuals manifesting only after this point. The thought process was about as clear as mdma, even more so, even while serious distortions appear.
Music was amazing, the first half was quite similar to a combo of mdma and mda. Definite euphoria. After 2 hours the mdxx-ish effects fade and more psychedelic effects begin. Once this happened, it became very similar to a mescaline trip.
[comments]
At this dose, the 'mindfuck' is extremely minimal compared to the astounding effects produced. I had seen waves at a pier flow in impossible 3d geometric patterns, I had seen an orb rise out of my carpet, still having the texture of the carpet, and I was actually able to 'play' with this orb. The visuals, while extremely similar to OEVS produced by LSD (which, for me, seem to be the main visual aspects of 2c-e, although friends of mine reported amazing closed eye visuals, I have only gotten CEV's once on this substance), they seem to have an extra dimension to them. 2c-e makes me see things that LSD would not, and visuals seem to be a much bigger part of the trip (whereas with LSD, i dont always get visuals).
I noticed with just a slightly higher dose of 18mg, much more confusion and mindfuck does become present. It is also very interesting that with LSD, if I took a dose that was equivalent in terms of OEV's (which for me would be something like 300ug for an 18mg trip, but of course this varies greatly), it is hard to even finish a sentence, and confusion is so severe that I tend to get lost in my mind. This happened to a lesser extent on doses higher than 15mg, but, since for me 15mg is the 'sweetspot', my mind is very clear for a full-on psychedelic, with outragious visuals.
I have had many intelligent conversations while seeing things like my tripping partner's face rearranging like a jigsaw, my own eyes floating away in a mirror, and I noticed a pattern: if I was, for example, staring at the carpet, it would usually rise towards me in a specific 'snake-like' motion, then doubling, tripling, quadrupling, and then all coming together to form something 3dimensional. The longer I look, the more distorted it gets, and eventually I have to look away, because it becomes just too much.
However, I think that unlike acid (this is the biggest difference between the experiences) 2c-e requires my interaction. In other words, the first time I used it, I found myself feeling simply like I was rolling, until I started noticing little distortions, and then making things distort, by staring at them, and willing them to. The first trip, while still very colorful and visual, was sort of like an introduction. Every trip afterwards made me tumble deeper and deeper into the rabbit-hole. I no longer had to make anything happen, since my mind already knew the path.
Also, important to note, I had always read that 2c-e lasts for 6 hours, but it certainly lasts longer for me, the bulk of the trip is 8hrs while the entire trip is around 12hrs, but even 24hrs later I could induce quite vivid visuals. The only true side effects I had gotten were jaw tension, cold chills on the comeup, and an overall sensitivity to cold while on the substance. Other people I know had taken 2c-e without even knowing what it is, and were also sensitive to cold. If I give any suggestions, do NOT even attempt to eyeball this substance, and even if you have a 0.01 accuracy scale, 10 extra milligrams could be a huge difference. To be on the safe side, I dosed no more than 10-15mg at first and gauged my reaction (I have seen people who didn't take this stuff too seriously take a ~20mg dose and then would refuse to ever touch it again because of the surprising intensity, and some complain that it is too subtle at the same dose).
Overall, this has become my favorite hallucinogen, but not everyone gets these same effects. Another friend specifically sees faces everywhere on it. I also notice that susceptibility varies, and personally while 15mg is more than enough for me, yet another friend needs 50mg (!) to get the same results. The main variable seems to be tolerance/dosage. While the material comes on fairly smoothly, it is not a toy, and in my opinion is definitely more of a wild ride than LSD, however while L is certainly more overwhelming, it seems to me that 2c-e is more powerful and potentially dangerous at the ++++ point.  Much more similar to mescaline than to LSD, this substance, IMO/IME should definitely remain in shulgin's 'Magical Half Dozen'. As Shulgin says himself, most definitely a substance that will reward those experiment with it.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


AZTECA
Starters
Stuffed Jalapeño
$5.99Crispy jalepeno with cheese inside
Cheese Dip
$4.99Zesty Monterrey jack cheese melted to perfection
Fiesta Potatoes
$2.99Fried potato skin topped with sour cream and melted cheese
Cheese Quesadilla
$7.50A large flour tortilla, grilled with olives, tomatoes and shredded cheese
Papas Fritas Con Chile
$8.75French fries smothered with red and green chile and topped with shredded cheese
Main Course
Chicken Enchiladas
$11.99Flour tortilla covered with Picante sauce
Shredded Beef Tacos
$9.994 crispy hardshell tacos, served with lettuce and cheese
Chimichanga
$12.45beef, beans, cheese, topped with guacamole, sour cream and lettuce
Grande Shrimp Fiesta
$100100 jumbo shrimp topped pan-fried in a signature sauce and topped with gold flakes
Desert
Churros
$2.99fried dough dusted with cinnamon
Vanilla cone
$1.00Vanilla ice cream served on a cone
Drinks
Soda
$2.99Coke, Sprite, Fanta, Dr.Pepper
Tea
$5.99Sweet tea, Cold tea, Hot tea


A showcase of skills learned in conjunction
with
and
Forum
Inspiration
Freelance Web Developer.
Design and Communications Consultant.
Family Man.
My Portfolio
See what I've done for others.
Then see what I can do for you.
About Nick
I love my work,
but work alone does not define a person.
Nick's Picks
See what inspires
and drives me.
My Portfolio
See what I've done for others.
Then see what I can do for you.
About Nick
I love my work,
but work alone does not define a person.
Nick's Picks
See what inspires
and drives me.
My Portfolio
See what I've done for others.
Then see what I can do for you.
About Nick
I love my work,
but work alone does not define a person.
Nick's Picks
See what inspires
and drives me.


INSTITUTE BENJAMENTA, OR This Dream People Call Human Life (director/writer:The Brothers Quay; screenwriter: Alan Passes/from texts by Robert Walser; cinematographer: Nicholas Knowland; cast: Mark Rylance (Jakob), Gottfried John (Johannes), Daniel Smith (Kraus), Alice Krige (Lisa), 1995-GB)
Reviewed by Dennis Schwartz
Strange is the norm for this exquisitely made first full-length live action feature from the American-born (they work in London) identical twins, Stephen and Timothy Quay, who have previously achieved cult status for their animation films. This dream-like fantasy film, probably a fairytale story gone amok, filmed in the style of German Expressionism ala "The Cabinet of Dr. Caligari," and most reflective of a Kafkaesque type of story depicting a man trapped by absurd circumstances and his mistrust of society, as the film sets a nightmarish tone. It is loosely based on the novella 'Jakob Von Gunten' by the Swiss author Robert Walser.
The Institute Benjamenta is a boarding school for servants, where the lessons are taught by the siblings, the eccentric despot Johannes Benjamenta (Gottfried John) and the fragile beauty, Lisa Benjamenta (Alice Krige). She teaches by being repetitive to the point of being ridiculous and surreal, as the course of study consists of repeating the lesson over and over, such as the lesson in setting the dining table, as ritualistically the would-be servants keep repeating in unison what their ethereal teacher tells them, as she paces back and forth in front of the blackboard holding onto a pointer made of a deer foot. There are deer antlers that hang on the walls and pine cones and needles on the floors of the classroom. The use of deer must hold some symbolic meaning to the story, but I would only be guessing as to exactly what.The lessons take place in a dilapidated building, with a creepy looking and uninviting interior, setting the claustrophobic atmosphere the film thrives on. The ceilings in the student's rooms are too low to stand up in (ala Dr. Caligari).
The film follows its story through the eyes of Jakob von Gunten (Mark Rylance), who is first seen knocking on the school's door and looking through the peephole at a monkey, as he is about to enroll. He states that he came to this place-which seems to be cut off in time and location from the rest of the world- looking for a chance to be of service to someone in this life. He will remain here until the school crumbles, as it seems to be coming to a slow but sure end, as the director announces no more students will be taken in after Jakob.
What is the reality of life if everything can be turned upside down and what does reality mean, might be some of the things the film is questioning, that is, if one were looking for a theme to this intriguing tale, filmed in a grainy black-and-white monochrome, which added to the film's evocative mood. Another theme might be the Jesus motif, of how can one be like Christ, a humble servant, in a society that craves order and for people to know their place in that order. Jakob asks, "Is there anything Jesus could do for us in this world?" The answer seems to be, become a servant.
The film succeeds in being a hypnotic work of much visual merit, that is different in scope and in intention than other films, probably defying classification into a type of genre it belongs to. There is hardly any dialogue, and the sparse dialogue that is there, does not seem to be that pertinent to the story, as the actors recite their lines as if they were puppets on a string being manipulated by the Quays. The sister asks, at one point, "Am I living in a fairy tale?"
But it is the aesthetics that seem to count for what are the dramatics of the film. Its story of the high and the low in status, each accepting unconditionally their place in society are examined in a most bizarre fashion in the student's and his master's mannerisms, as all the repressed students who willingly serve at their master's discretion go through their eerie robotic movements, and the story has the look of a spellbinding fairytale.
What is also shown, is how twisted and sexually repressed the siblings are, him in need of Jakob as his confidante and slave, showing how fearful he is of life, while she is caressing Jakob's cheeks as if to comfort herself, but it could also be a tabu romantic gesture toward Jakob, indicating their separation is due to class differences. And, of the eight students, Kraus (Daniel Smith) stands out as one wholly accepting of the arrangement of servant and master, accepting without a peep of protest the school's dehumanization policy.
The film runs its course with alternating moods of exhileration and tedium, but proves itself to be visually stimulating overall, with every scene showing the contrasts between the light and dark of life. There was also the memorable weird scene in the beginning of the film, where a face appears distorted through a goldfish bowl.
At the film's conclusion, Jakob questions what he has learned, if he has really become insignificant, implying that instead of things being a mystery, such as the face in the gold fish bowl, knowing about things can be attained by doing what is habitual, as when Kraus teaches him how to clean the bowl, which is enough for him to learn.
What it all means is subject to one's imagination (so much of the film is purposely left unclear), as Jakob wrestles with whether he should rescue Lisa from her melancholy life. But, this unsettling film is, nevertheless, diverting in a positive intellectual way, even as it is subject to much speculative interpretation. You can look at it as a visionary poem or as an allegory on life, either way, the film is original and stimulating, if one can take the very slow pace of its camera work and its tenor of dull melancholy and its inconclusiveness into proper consideration.
The film was stylishly scored by Polish composer Lech Jankowski.
REVIEWED ON 11/15/99 GRADE: B+
Dennis Schwartz: " Ozus' World Movie Reviews"
http://www.sover.net/~ozus
<EMAIL_ADDRESS>© ALL RIGHTS RESERVED DENNIS SCHWARTZ
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


By Eric T Freeman, Elisabeth Robson
What can HTML5 do for you? If you're a web developer looking to use this new version of HTML, you might be wondering how much has really changed. Head First HTML5 introduces the key features -- including improved text elements, audio and video tags, ...
[Publish Date: July 2011]


Sahi Pro - Sahi Flex Support
Introduction
Sahi Pro provides support for automation of flex applications via the Sahi Flex Library (SFL).To enable automation, the flex application needs to be compiled with Sahi's swc file.
info
Different swc files are available for different versions of Flex.
Compile your application with the relevant swc file.
If your application is compiled with Flex 4.0, use sfl4.swc
Sahi's swc files are located in
Compile your application with the relevant swc file.
If your application is compiled with Flex 4.0, use sfl4.swc
Sahi's swc files are located in
sahi_pro/sfl/
folderCompile with sfl.swc using command line
You can compile your flex application with sfl using the following command (Change sfl version as needed)mxmlc yourapp.mxml -include-libraries+=sfl4.swc --output=yourapp.swf
warning
After compilation refresh the browser cache, to make sure that the modified app is available.
Compile using Ant
When compiling using Ant, we need to specify the compiler.include-libraries option<mxmlc file="sample.mxml">
... normal options
<compiler.include-libraries dir="D:/sahi/sfl" append="true">
<include name="sfl4.swc" />
</compiler.include-libraries>
</mxmlc>
warning
After compilation refresh the browser cache, to make sure that the modified app is available.
More details on flex compilation itself via ant is available here
Compile using Adobe Flash Builder (Add SWC files to Flex Builder projects)
- In Flex Builder, select your Flex project in the Navigator.
- Select Project > Properties. The Properties dialog box appears.
- Select Flex Compiler in the tree to the left. The Flex Compiler properties panel appears.
- In the "Additional compiler arguments" field, enter the following command:
-include-libraries "sfl4.swc"
info
In Flex Builder, the entries in the include-libraries compiler option are relative to the Flex Builder installation directory.
The default location of this directory on Windows 32 bit is
and on Windows 64 bit is
The default location of this directory on Windows 32 bit is
C:\Program Files\Adobe\Flex Builder
and on Windows 64 bit is
C:\Program Files(x86)\Adobe\Flex Builder
warning
After compilation refresh the browser cache, to make sure that the modified app is available.
Recording a flex application
From the dashboard, open any browser and navigate to your flex application.
Press ALT and double click on the document window of the page which you want to record.
Sahi's Controller window will popup. You can now start recording your Flex application.
warning
Ctrl + hover (to get a flex element's accessor) will work only if the Flex application is in focus.
To do this, you will have to first click on the Flex application.
To do this, you will have to first click on the Flex application.
Flex APIs are slightly different from the normal JavaScript APIs.
Example
_f("flex_app_id").textinput("username2")
The code above identifies a
mx.controls::TextInput
field inside a flex application identified by _f("flex_app_id")
Identification of Flex Components
Sahi identifies flex components based on the type (class name) of element and one of its visible/significant attributes.The attributes may be one of
label, text, name, automationName, toolTip, id, autoGeneratedName, index
or some other attribute which is relevant to that element.
mx components are identified as lower case of their class names.
Eg.
mx.controls::TextInput
corresponds to API _f("id").textinput("id2")
Spark components are identified with an
s_
prefix.Eg.
spark.components::TextArea
corresponds to API _f("id").s_textarea("id2")
Recognizing Custom Components
Sahi, by default, adds support for most mx and spark components.If your component is not recognized, do the following:
-
CTRL Hover on the element which is a parent of the element you want to recognize.
You can use up/down arrows near the Accessor field on the Controller.
-
Once a parent element is identified, click on the "List Properties" button on the Controller.
It will list down all components inside the parent and also all attributes.
-
In the fully qualified classnames visible, make an intelligent guess to narrow down your element of interest.
Suppose your class name of interest ismy.package::MyClass
To enable Sahi to recognize custom components in your application,
edit
sahi_pro/userdata/config/user_extensions.js
and add,SflWrapper.prototype.addCustomMetaData = function(){
this.addMetaData({qn: "my.package::MyClass",
attributes: ["label", "text", "name", "automationName", "toolTip", "id", "autoGeneratedName", "index"],
action: "click", value: "label", apiName: "myotherclass"});
}
In the above,
- change
my.package::MyClass
to your relevant class - For clickable elements, keep
action:"click"
. For text input elements, useaction:"setValue"
- Set
value
to the attribute which conveys the value of that field.
For example, a dateField will have selectedDate as its value attribute.
This will be visible in the "Value" field on the Controller, and is used in assertions.
- The name of the API is by default the lowercase of the classname. If apiName attribute is specified, that is used instead.
Eg. in the above case, the api becomes_flex("id").myotherclass("id2")
.
If apiName was omitted, the api would have been_flex("id").myclass("id2")
.
Performing actions on Flex elements
Sahi's Action APIs also work with Flex elements.Examples:
_click(_f("mxComponents").button("ColumnChart"));
_setValue(_f("mxComponents").textinput("txt1"), "English");
_setValue(_f("sparkComponents").s_richeditabletext("richEdTxt"),"Hi there!");
_setSelected(_f("sparkComponents").s_combobox(0),"Cucumber");
Relational operators in SFL
SFL supports near, inside, leftOf, rightOf and under APIs.The usage of these APIs is a little different from the Sahi relation APIs.
- The relation APIs are called as member functions.
_f("fid").textinput("u").near(_f("fid").label("User")) _f("mxC").datagriditemrenderer("/@fictitious.com/").rightOf(_f("mxComponents").datagriditemrenderer("Mary Jones"))
-
They can be chained to use multiple relations.
_f("fid").textinput("u").near(_f("fid").label("User")).inside(_f("fid").vgroup("SettingsPanelView"))
Known Issues
- For the CTRL-Hover to work, one needs to click on the Flex app and bring it in focus.
- File upload/download are not currently supported.
- NumericStepper recording does not work. However it can identified from the Controller and scripted.
- Parallel run of scripts using testrunner causes scripts to fail. Keep value of threads to 1 in testrunner.bat
Tips on usage
The flex recorder in Sahi is not as sophisticated as the web recorder.To introspect and identify elements, one can use the Evaluate Expression box.
Ctrl Hover on any Flex element. It will populate something like
_f("sampleId1").textinput("username")
- One can see all attributes of the textinput field by one of the following
- CTRL Hover on element and Click on List Properties
- Copy the accessor into Evaluate Expression box and click "Test->"
- Explicity put component.listProperties() into Evaluate Expression box and click "Test->"
_f("sampleId1").textinput("username").listProperties()
-
To fetch the value of an element, use _getValue() API.
Depending on the type of element, Sahi will correctly return its "value" attribute.
_assertEqual("abcd", _getValue(_f("mxComponents").textarea("textarea")));
-
To fetch the text of an element, use _getText() API.
On flex it fetches the textual content of the component (behaves like innerText in HTML).
_assertEqual("abcd", _getText(_f("mxComponents").textarea("textarea")));
-
To fetch any property of an element, use .get
Example
or_f("sampleId1").textinput("username").get("text")
_f("sampleId1").textinput("username").get("label")
-
To execute any member function of an element, use
.executeFn(arg1, arg2 ...)
Example
or_call(_f("sampleId1").popupbutton("menu").executeFn("open"));
var $fontSize = _fetch(_f("sampleId1").textinput("username").executeFn("getStyle", "fontSize"));
-
To see which Flex components make up a particular component, use introspect()
Example
This will show a list of all elements inside the textinput field._f("flexId").textinput("tId").introspect()
The output may look something like:
textinput0>Panel4>username>HaloBorder17:mx.skins.halo::HaloBorder textinput0>Panel4>username>UITextField8:mx.core::UITextField #abcd
- To see all elements in a flex component, (especially when an element is not identified) use
_f("sampleId1").introspect()
- To check if an element exists, use _exists or .exists()
_assert(_exists(_f("mymovie").datagrid(0))); //or _assert(_f("mymovie").datagrid(0).exists());
- To check if an element is visible, use _isVisible or .isVisible()
_assert(_isVisible(_f("mymovie").datagrid(0))); //or _assert(_f("mymovie").datagrid(0).isVisible());
-
To get data from a grid, use .getGridData()
_assertEqual([["a", "a1"],["b", "b1"]], _f("mymovie").datagrid(0).getGridData());
- If getGridData does not work or if we are dealing with a graph,
it is easier to get the dataprovider of the element and verify that the data is correct.
To get the dataprovider, do
This will return a JSON string. To get an object out of it, use_f("mymovie").datagrid(0).get("dataProvider")
obj will now be an array of objects, which looks something like this:var obj = eval("(" + _f("mymovie").datagrid(0).get("dataProvider") + ")");
[{"balance":"1000","category":"Personel Care","date":"15/12/2010","description":"ATM Fee", "price":"1000","quantity":"1000","payee":"ABC","amount":"1000","datePaid":"15/12/2010", "status":"success","action":"buy"}]
-
Sometimes similar elements may be created in a flex app, but only the top most active container may be of relevance while automation.
For example a tab pane may have multiple tabs and each tab screen may have a "Save" button.
The sequence of navigation of tabs may give different indexes to these different Save buttons.
To fix this, Sahi can be told to strictly work only with visible elements using _setStrictVisibilityCheck
// Force Sahi to only find visible elements _setStrictVisibilityCheck(true, _f("myapp")); // Perform actions on visible elements only _click(_f("myapp").button("Save")); // Remove strict visibility check _setStrictVisibilityCheck(false, _f("myapp"));
- SFL supports indexes and regular expressions just like normal Sahi APIs.
For example, to look for<EMAIL_ADDRESS>we could do
// returns<EMAIL_ADDRESS>_getText(_f("mxComponents").datagriditemrenderer("/@fictitious.com/[2]")); //using relation and regular expression //returns<EMAIL_ADDRESS><EMAIL_ADDRESS>.rightOf(_f("mxComponents").datagriditemrenderer("Maurice Smith")))
-
In some flex apps with lots of dynamically loading parts, it may be customary to show a rotating icon with "Loading..."
or some such message. Sahi can be told to wait till this message disappears using _setFlexReadyCondition.
At the start of your script add this:
<browser> _setFlexReadyCondition(function(fl){ return !_isVisible(fl.uitextfield("Loading...")); }); </browser>
Flex app and SahiPro version
Your Flex app needs to be compiled with the appropriate swc file based on the Flex SDK used.It does not have a dependence on the Sahi Pro version itself.
The swc files available for compilation can be found inside the
sahi_pro/sfl
folder.


Hi, Here's a little about me. A self-taught Developer. i'm always love something about Website and applications and curious about how it's work behind the browser. that's why i choose to learn about web development and applications. And i'm ruby and python enthusiasm. i'm not an expert at it. so, i'm still learning to improve my skills on that. because w'all knew if technology, always improve itself days to days.
My working roadmap
- Front-end Developer (01.2020-Present)
- Event Organizer for Wedding (01.2019-12.2019)
- Bancassurance Consultant at Sinarmas MSIG Life (01.2018-12.2019)
- Temporary Teacher for middle school (06.2017-12.2017)
- Website Layout Designer (HTML, CSS) (03.2013-12.2013)


Defines | |
| #define | AVOID_BANK_CONFLICTS |
Variables | |
| const int | NUM_BANKS = 16 |
| const int | LOG_NUM_BANKS = 4 |
| const int | CTA_SIZE = 128 |
| const int | WARP_SIZE = 32 |
| const int | LOG_CTA_SIZE = 7 |
| const int | LOG_WARP_SIZE = 5 |
| const int | LOG_SIZEOF_FLOAT = 2 |
| const int | SCAN_ELTS_PER_THREAD = 8 |
| const int | SEGSCAN_ELTS_PER_THREAD = 8 |
| const int | maxSharedMemoryPerBlock = 16384 |
| const int | maxThreadsPerBlock = CTA_SIZE |
| #define AVOID_BANK_CONFLICTS |
Set if by default, we want our shared memory allocation to perform additional computation to avoid bank conflicts
| const int NUM_BANKS = 16 |
Number of shared memory banks
| const int LOG_NUM_BANKS = 4 |
log_2(NUM_BANKS)
| const int CTA_SIZE = 128 |
Number of threads in a CTA
| const int WARP_SIZE = 32 |
Number of threads in a warp
| const int LOG_CTA_SIZE = 7 |
log_2(CTA_SIZE)
| const int LOG_WARP_SIZE = 5 |
log_2(WARP_SIZE)
| const int LOG_SIZEOF_FLOAT = 2 |
log_2(sizeof(float))
| const int SCAN_ELTS_PER_THREAD = 8 |
Number of elements per scan thread
| const int SEGSCAN_ELTS_PER_THREAD = 8 |
Number of elements per segmented scan thread
| const int maxSharedMemoryPerBlock = 16384 |
Number of bytes of shared memory in each block
| const int maxThreadsPerBlock = CTA_SIZE |
Maximum number of threads in a CTA


JavaScript: Working with Events
How Events Work
- User does something, like click a link.
- Browser reports the event in the form of an event object, supplied to the designer.
- Designer User can "handle" the event (or not).
What's an Event?
- A JavaScript Object!
- As you browse the web, the browser is constantly telling you what the user is doing.
- You can “listen” for different events.
- When you the browser tells you about an event, you can “handle” it.
Types of Events
- Browser Events
- User Interface Events
- DOM Events
- Form Events
See the lecture slides for lists of common events
How to Handle Events
Step 1: Select an element
var myElem = document.querySelector('.myClass');
Step 2: Tell the browser what event you're listening for and tell it what function should handle the event.
myElem.addEventListner('click', myFunction)
Step 3: Write your fucntion!
function myFunction (event) {
// Do something here...
}
Note: addEventLisener
implicitly sends an event object to the function it calls.
The Event Object
- Gives you a ton of information
- You will commonly work with
event.target
andevent.type
properties - Has two methods:
event.preventDefault()
and event.stopPropagation()
Event Bubbling
An event reaches the "deepest" or most nested element first and then "bubbles" up until it reaches the root document element. You can listen for events on any element the event touches.
Demo
For a working example, see the class demo


Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.
Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.
Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.
Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.
Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.
Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.
jQuery NiftyModal plugin has 18 different amazing effects to give your modals life.
Modals are streamlined, but flexible, dialog prompts with the minimum required functionality and smart defaults.


Edition 2019-20
Edition 2020-21
Some books
Books that I took with me during the first meeting.
Page last modified at Wed, 02 Apr 2014 16:58:19 +02001
Comments welcome


Start Bootstrap
Add POIs
Heatmap
#
Home
(current)
Link
Dropdown
Action
Another action
Something else here


I’ve always been fascinated by the concept of time travel. Though I was introduced to it in fictional books and the Japanese anime Doraemon, it’s a concept that never fails to impress me, even though I’m 18 now. 2 years ago, early March of 2019 to be precise, I chanced upon an article about a quantum computer that travelled 0.5 seconds back in time. I was intrigued and researched more on it since until then, I discarded the concept as being unrealistic. As a result of the research, I learnt more on the same and also on the effects of gravitational waves, which stretches and squeezes space, and was first discovered in 2015 using a very sensitive instrument called LIGO (Laser Interferometer Gravitational-Wave Observatory). These first gravitational waves formed when two black holes collided approximately 1.3 billion years ago, but it took so long for the ripples to reach earth. In this article, I’ll be focusing on the former topic.
About the Auther
S Neha
1st year
Department of Electronics and Communication
“She packed her seven versalia, put her initial into the belt and made herself on the way. When she reached the first hills of the Italic Mountains, she had a last view back on the skyline of her hometown Bookmarksgrove ” — Jean Smith
On March 14 2019, researchers from the Moscow Institute of Physics and Technology (MIPT), who teamed up with experts from the US and Switzerland, successfully reversed time through an IBM quantum computer, be it only for half a second. They hypothesized that time can spontaneously reverse itself for an individual particle for a really small fraction of time; thereby artificially creating a state that evolves in a direction opposite to the thermodynamic direction of time, according to the lead researcher Dr. Gordey Lesovik, who heads the Laboratory of the Physics of Quantum Information at the MIPT. The research was also able to calculate the probability that an electron in empty interstellar space will spontaneously travel back into its recent past.
This is the third hypothesis [after Maxwell’s demon hypothesis suggested by the physicist James Clerk Maxwell; and the theory of gravitational waves suggested by Albert Einstein that gravitational waves could be a natural outcome of his general theory of relativity, which says that very massive objects distort the fabric of time and space, an effect we perceive as gravity] which can violate the second law of thermodynamics concerning the arrow of time, which states that time is linear and can travel in one direction alone, i.e., the forward direction.
Quantum computing focuses on the principles of quantum theory, which deals with modern physics that explain the behavior of matter and energy at an atomic and subatomic level. Quantum computing makes use of quantum phenomena, such as quantum bits, superposition, and entanglement to perform data operations.
Using the quantum computer, the researchers were able to unscramble a set of electrons. A quantum computer comprises electron qubits (quantum version of the classical binary bit physically realized with a two-state device) described by a “one”, a “zero”, or a “superposition” of both states. The time-reversal achieved an 85% success rate in the cases where 2 qubits were involved, but only 50% where 3 qubits were present.
Even though critics do suggest that the statement is false and that the phenomenon is not a violation of the laws of quantum mechanics, this is only a hypothesis. Time reversal, though an exciting field, has the potential to harm the entire world when misused. So, let’s hope that only constructive researches and innovations breakthrough.


---
layout: post
title: Sponsorship Perks
categories: []
tags: []
status: publish
type: post
published: true
meta:
_edit_last: '1'
---
Here's a list of perks we get from our various sponsors:
Buy n Ebooks, Get n Free* - Go to oreilly.com and use discount code: MBBGS


We finally made it to Beast. Overall, a fantastic experience. I would go back in a heartbeat, if only my heart (and wallet) could take that kind of a beating regularly.
Soup
The soup was cucumber and creme fraiche, was airy and cool; some citrus high notes with the cucumber keeping things steady. The flower petals were a beautiful contrast. The chili oil was... missing. Others said they could taste it, but I couldn't. It would've provided perfect dissonance, as well as a textural anchor on the tongue, so my hunch is that it was intended to be drizzled on top, but was forgotten. It was paired with a Gruner Veltliner, worked fine.
Charcuterie
Foie gras bon-bon: Unbelievable on the tongue, but a bit too worshipful. I come from peasant stock, and wanted to eat this on some country bread.
Steak tartare and quail egg on toast: Undoubtedly a highlight of the meal. The tartare was supremely cold with maybe some... scallion and white pepper? I had a minor yolk-splosion, so best to take it all in one bite.
Pork Rillette and house cracker: High expections went unmet. The pork was unnassuming, and the cracker could've been crisper.
Duck, duck liver, cherry and pistachio pate: A nice blend of creamy and roasty. I'm just not a fan of mixing fruit, nuts and meat, so it wasn't my favorite. Also, my less-than-blue blood again was begging for bread or a cracker.
There was also a cornichon on a daub of dijon mustard, a crisp "ice leaf" (IIRC) on a sliced pea salad, and a salami.
All of this was paired with Tessier Cheverny Blanc - wonderful choice: front of the tongue, spicy, light.
Entree
The seared duck breast, alongside a cherry and tomato salsa and pan-fried squash blossoms. The duck was fairly unadorned, which was a great move given it's place in the courses - nice to focus on purity after the charcuterie carnival. The salsa was more of a salad: Rainier cherries and cherry tomatoes halved and in a mild vinegar. It stood up for itself next to the duck.
The only downer of the course was the Grosbois Vielles Chinon that was the paired with it.  The duck cried out for a saltier, earthy red - I'd have chosen a tempranillo maybe.
Salad
Oddly, this was the simplest part of the meal, yet all agreed that it vied for a top spot among the courses. It was some local greens and a few peach slices in a sherry vinaigrette. There were marcona almonds, but as they were whole, they were bystanders. The upstaging of the course was the shaved goat cheese.  Playing the excited voyeur was the Salomon Kogl Riesling - light on the tongue and a nice balance to the piquancy of the sherry.
Cheese
Steve's cheese - one slice each of a sheep, goat and cow cheese, with poached apricots, candied hazelnuts, saffron shortbread and local honeycomb. The sheep's cheese stood out - with a broad nuttiness, definitely was the best choice to contrast the preceding course. The shortbread were little buttons, well-sized to reign in the saffron's tendency to dominate. The honeycomb was what really took this course over the edge, into the realm of culinary primality - a chthonic offering spilt on the civilized craftsmanship of the cheeses.
The Prieler pinot blanc was well paired, provided respite for an overstimulated palate.
Dessert
Lemon verbena meringues with buttermilk ice cream and tayberries and blackberries. The meringue was truly enjoyable, bright and sweet. The wine pairing was JJ Christoffel Urziger Wurzgarten Auslese, and was far too thickly sweet to be served with buttermilk ice cream. We were offered coffee, which was the right choice for this course... but then left us with wine and coffee at the same time, which was awkward.
Tips: The portions were perfect, and the progression of courses was well thought out, so I'd recommend going for all six courses. The wine pairing, with a couple of exceptions, was smart, so I recommend that as well. Go for the second seating, as you'll get more time to linger.


This paragraph should be in green characters.
This paragraph should be in green characters.
This paragraph should be in green characters.


--- layout: post title: livro de eletronica date: '2007-08-17T13:38:00.001-03:00' author: meleu tags: - eletronica modified_time: '2007-08-22T08:11:00.366-03:00' blogger_id: tag:blogger.com,1999:blog-1613465446497619833.post-1115808789944655494 blogger_orig_url: http://mdicas.blogspot.com/2007/08/livro-de-eletronica.html ---