HTML was once exciting before everyone found all the bugs. So Flex is finally something fascinating and new. Something new where things just might go wrong.
Meouzer
Meouzer is fascinated by bugs. Especially the IE11 bugs concerning wrap-reverse that are still in place after years. For that reason we suggest you do not use IE11 for the demo in order not to get the wrong ideas. Edge, Firefox, Chrome, and Opera are OK.
Flex is a two dimensional layout design based in CSS that positions flex-items within a flex-box. The flex-items are laid out either in rows or columns with wrapping available to prevent overflow. Each row or column is a flex-strip. Every flex-strip is assigned an alignment-box/confinement-box that the items are free to move and stretch around in both vertically and horizontally. In a special circumstance, the alignment boxes themselves can be moved about in a small number of preset ways.
Every flex-box and in fact every alignment-box has a main-axis and a cross-axis to specify position.
However, position is not specified by coordinates, which sounds more strange than it actually is. Flex provides a spectrum of numberless positioning presets.
With row layouts, the main-axis is horizontal, but with column layouts it is vertical. Movement of flex-items is most restricted along the main axis since flex-items can move only so far until they bump into another flex-item in the same flex-strip. Along the cross-axis there is more freedom of movement since there is nothing in the way inside its alignment-box.
Along both the main-axis and cross-axis there are preset means of positioning that are esthetically pleasing. By adjusting margins of flex-items, you have more fine-grained control.
To position with respect to the main-axis use the css style attribute justify-content. To position with respect to the cross-axis use align-items. They work across all alignment boxes in parallel. So if the flex-items in one alignment-box are centered with respect to the cross axis, so are the flex-items in any other alignment-box. If the flex-items in one alignment box are spaced out evenly along the main-axis, so are the flex-items in any other alignment-box.
Flex-items are numbered by the order in which they are entered into the flex-box in HTML code. The first flex-box will be closest to the origin of the two axes. The flex-strips are also numbered. The first flex-strip is the strip containing the first flex-item and will be the flex-strip closest to the origin.
Flex-items always flow along the main axis, i.e., flex-items increase in numbering as you move along the main axis.
Flex-strips flow along the cross axis, i.e., flex-strip numbers increase as you move along in the direction of the cross axis.
Setting the flex-box's css style attribute flex-wrap to wrap-reverse will flip the direction of the cross axis to let the flex-strips flow in the direction opposite to what they otherwise would.
To make an element a flex-box, assign its css style property display a value of "flex" or "inline-flex". Its items or flex-items are simply its direct children.
If a text-node is a direct child of a flex-box, the text-node is a flex-item.
A flex-box may have one of four possible layouts.
See the diagrams below. The yellow box is a flex box with six flex-items. The row and row-reverse layouts each depict two flex-strips (rows). The column and column-reverse layouts each depict two flex-strips (columns).
The numeric labeling indicates the order in which the items were added to the flex-box in HTML code.
Once the axes rules have been read, go over the top row of diagrams very carefully. Based on flex-item numbering, the main-axis is always easy to determine: as mentioned previously, flex-items flow along the main axis. Then the cross axis will be perpendicular to the main axis and point right or down. Once the top row is understood, go over the bottom row where the cross axis has been flipped (so now points left or up). Another way to determine the cross axis is to observe how the flex-strips flow: As mentioned previously, flex-strips flow along the cross-axis.
To describe placement within the flexbox we need a pair of axes relative to which flex items are placed. The following discussion describes how it's done.
It's very convent to take our axes as finite directional lines with a start and an end. Their origin is always at one of the corners of the flexbox. In the diagrams above the axes are supposed to meet precisely at a corner of the flex-box. We simply had to move them so they could be seen.
Suppose a rectangle has sides parallel to the axes. The two sides parallel to the cross-axis are called main-start and main-end. main-end is the one that is furthest along in the direction of the main axis. The two sides parallel to the main-axis are cross-start and cross-end. cross-end is the one that is furthers along in the direction of the cross axis.
The flex-box has four css style properties related to the axes: flex-direction, justify-content, and align-items.
| Axes | flex‑direction |
|
|---|---|---|
| flex-wrap |
|
|
| Positioning | justify‑content | Positions flex-items along the main-axis (in their containment box) |
| align‑items | Positions flex-items along the cross-axis (in their containment box) |
flex-direction specifies the type of layout. It has the four possible values
Refer to the diagrams in lesson three.
| - | |
| Explore flex-direction | Go through all four possibilities for flex-direction in the interactive demo. |
|
Once you are clear, repeatedly quiz/randomize and determine what flex-direction is. |
justify-content positions flex-strips along the main axis. It has five possible values.
| - | |
| Explore justify-content | Go through all five possibilities for justify-content in the interactive demo. |
|
Once you are clear, repeatedly quiz/randomize and determine what justify-content is. |
align-items aligns flex-items along the cross-axis. It has four possible values.
| - | |
| Explore align-items | Go through all four possibilities for align-items in the interactive demo |
|
Once you are clear, repeatedly randomize and determine what align-items is. |
A flex-item will never stretch past its cross-size and max-cross size. For example if the cross-axis is horizontal, width is 200px and max-width is 300px, the flex-item's stretched length will be 200px. If the width wasn't set, then the flex-item's stretched length will be 300px.
Each flex item may set its own align-self property to override the alignment along the cross axis specified by the align-items property. In the demo, as stands for align-self.
The values for align-self follow, and they are the same as the values for align-items.
A flex-box with three items set its align-items property to flex-end However, the third and somewhat pink like box decided to overrule align-items and set itself at the start of the cross-axis by setting its align-self property to flex-start.
So far we have dealt with only one flex strip, but with wrapping there could be more. Each flex-strip gets it's own alignment box, which with respect to alignment takes place. align-self, self-align and even justify-content work with respect to the flex-strip's alignment box. The cross-sizes of the alignment boxes are computed in advance and don't depend upon any css style properties, including justify-content and align-items. Just like the flex-box itself, each alignment box has its own cross-start and cross-end.
Enlarging a flex strip by one extra share of the total amount of free space produces its alignment area.
- A flex box is 200px tall with a flex-direction of row or row-reverse. It has three flex-strips of heights 36px, 60px and 80px with center positioning along the cross axis, what are the sizes of the individual free spaces?
Solution Subtracting the total three sizes from 200px gives a total free space of 24px. Draw a picture and you will see two free spaces get 1/2-share and two free spaces get 1-share for a total of 3-shares = 24px. Each share must then be 8px. Whence, the individual free sizes are 4px, 8px, 8px, and 4px. ■
Remember that normally the cross-axis points down or to the right. Setting flex-wrap to wrap-reverse flips the direction of the cross-axis. Flex strips always flow along the cross axis.
In each of the following exercises start by refreshing the web page an choosing five flex items.
| - | Choose 5 items, hide the axes. | Go through all four possibilities for flex-direction, but each time switch between wrap and wrap-reverse to observe how the cross axis flips direction by examining the item numbering in the flex strips. |
OK! Squishing is more dramatic.
With overflow along the main-axis, Flex in an attempt to prevent overflow will squish, if possible, each flex-item. Flex will ignore widths/heights set on the flex-items and squish them anyway. However, flex will respect min-width/min-heights.
Flex will squish up to but not past the min-width or min-height as the case may be.
| - |
Set flex‑wrap to nowrap |
Toggle between three and five flex-items |
|
With row or row-reverse, the flex-items get squished horizontally along the main-axis.
With column or column-reverse, the flex-items get squished vertically along the main-axis. |
A flex-area is the smallest cross sectional area of the flex-box that contains a flex-strip. If a flex-box sets its align-content property, then the alignment-boxes are the flex-areas: they aren't as described previously. The items in a flex-strip are free to wiggle around in the flex-area as determined by justify-content, align-content, self-align. Of course we now that justify-content, align-content produces parallel wiggling across all flex-areas/alignment-boxes.
Since the cross-size of the alignment-box is smaller than it was before, there is less wiggling room along the cross-axis of any flex-area. In fact the longest flex-item within any given flex-area can't move along the cross-axis at all. It is already at cross-start so setting align-items to start does nothing. It is already centered in the flex-area so setting align-items to center does nothing. It is already at cross-end so setting align-items to end does nothing. It is already stretched across the flex-area so setting align-items to stretch does nothing.
OK! Why are the flex-items in each flex-area above positioned differently? Aren't they supposed to be in positioned in parallel? Well the second and third WERE just like the first, but their purple and green flex-items set their self-align properties individually. Can you tell to what? (to center and to end respectively).
The programming team, meouzer and the cows, decided not to include align-content in the demo because someone will set a value for it and then wonder why the rest of the demo doesn't work as expected.
align-content aligns flex-strips along the cross-axis. It has five possible values.
These are the same values that justify-content has. How align-content works on flex-areas along the cross-axis is the same way that justify-content acts on flex-items along the main-axis.
-Chose 5 items and set flex-wrap to wrap or wrap-reverse. Set align-content to any of its values. Then go through all the possibilities for align-items. You will see very limited movement because the flex-areas are so restricted. Also, pick a flex-item and go through the values for self-align.


Doist is a remote-first company with employees from all around the world. Our mission is to help people do more and stress less. Our interests and hobbies are as varied as our nationalities– and creating amazing products for people like you is what brings us all together.
Pedro is a young and vibrant software engineer, with a strong passion for solving problems in an elegant efficient manner as well as interact and learn with others around him.


--- layout: post title: How to format a disk to FAT32 on a Mac / OS X date: 2015-09-01 08:08:47.000000000 +01:00 type: post published: true status: publish categories: [] tags: - note to self meta: _wpcom_is_markdown: '1' _edit_last: '1' _syntaxhighlighter_encoded: '1' _publicize_twitter_user: "@dvdsmpsn" _wpas_done_all: '1' _pingme: '1' _encloseme: '1' _wpas_skip_11278197: '1' author: David Simpson excerpt_separator: ---
From Alex Plumb on superuser:
If you're comfortable with using the Terminal, try this:
First, look at the partition table by running this command:
diskutil list
You should see something like this:
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *16.0 GB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS Example 15.7 GB disk1s2
The partition we want to change is
/dev/disk1
.We want to change the device to an MBR-formatted FAT32 partition.
To do that, run this command:sudo diskutil eraseDisk FAT32 NAME< MBRFormat /dev/disk1
where
NAME
is the name you want to give to the disk.As mentioned in the comments, you cannot put square brackets into the volume's name lest things mess up. To avoid having everything fail, simply ensure that there are no square brackets in the FAT32 volume's new name.


Step 1: Add Images for both Mask and Non Mask Scenarios
Step 2: Press the Train Button and wait until training complete message appears next to the button
Step 3: Click Start Guessing Button and Test The Model
You have added 0 Images without Mask for training and 0 Images with Mask for training.


Home
About
Facebook
Email
Unofficial Movie Pages
Tumblr
Welcome
Student Internet Security Help Point


{% extends "registration/base.html"%} {% load bootstrap4 %} {% block content %}
Enter your email address below, and we'll email instructions for setting a new one.


THE ICE STORM A film review by Steve Rhodes Copyright 1997 Steve Rhodes
RATING (0 TO ****): *** 1/2
It's frequently the small details that make the difference between a good picture and an outstanding one. Director Ang Lee (SENSE AND SENSIBILITY, EAT DRINK MAN WOMAN, and THE WEDDING BANQUET) is a master at the minutia of story telling.
In THE ICE STORM, set in an unhappy period of the early 1970s when the sexual revolution and the Watergate scandal were both in full swing, Lee uses close-ups of a metaphor-laden metal ice tray to tell the story. The adults in the film, and to lesser extent the teenagers, are as cold to each other as ice, and each will be broken in many ways before their melancholy story ends.
"Ben, you're boring me," complains Sigourney Weaver as a harsh looking Janey Carver to a tired and befuddled Kevin Kline as her lover and neighbor Ben Hood. "I have a husband. I don't have a need for another one." You see, he has committed the cardinal sin of talking seriously to her after their regularly scheduled tryst. She is there for sex and is put off by the effrontery of his speaking to her. James Schamus's script based on the novel by Rick Moody is dead-on in this scene as in all the others.
Carol Oditz's costumes and Michael Bigger's make-up gives the early 70s an accurate but exceedingly ugly look. Never have long lapels and gaudy leisure suits looked worse. Only Joan Allen, who steals the show as Ben's repressed wife Elena, manages to look good in her hairspray-hardened coiffure. A fragile statuette who looks ever in danger of cracking, she plays a wife who tries to ignore her husband's infidelities even as she yearns for some of her own. Like all of the other characters, she is massively unhappy with her life. Kleptomania turns out to be her method for sexual arousal.
Mark Friedberg's sets for the film are set in a depressingly gray and leafless New Canaan, Conn. The days are short and cold as a bleak winter approaches. Again, metaphors abound.
Along with the adults' preoccupation with sex, the kids are beginning to experiment. And I do mean experiment. Christina Ricci, as Ben's 14-year-old daughter Wendy, offers Janey's son Mikey, played wild-eyed by Elijah Wood, a sexual encounter, but with a condition. She must be permitted to wear her large Nixon mask during it. When her father finds them in Janey's basement, he is almost rendered speechless. Afterall, he just left Janey's bed upstairs.
In another scene, Wendy takes Mikey's younger brother Sandy, played with devilish innocence by Adam Hann-Byrd, into the bathroom for the classic game of you-show-me-yours-and-I'll-show-you-mine. When Janey finds them, she hypocritically delivers an overly long and obtuse lecture to Wendy that includes the admonition, "A person's body is his temple." (Yes, "his" since the 1970s predate the political correctness era.)
All of the performances are tour de force, but incredibly depressing. The show offers only a few possibly redemptive scenes.
The film's long ending sequence makes the picture. As its title suggests, it includes an ice storm. During the storm the adults attend a "California key party." Like a grown-up version of spin-the-bottle, each woman gets to go home with the man whose car keys she fishes out of a big bowl. Never has sex seemed more dismal that in this sad game of spouse-swapping. Even when the men get the worse looking ones at the party, they awkwardly seem to jump for joy.  It is a deadly serious and morose morality tale and the slowest and the darkest movie yet from Ang Lee. It is a devastating film that will almost certainly leave you emotionally drained.
THE ICE STORM runs 1:52.  The film would be fine for older and mature teenagers. I strongly recommend the picture to you and give it *** 1/2.
**** = A must see film. *** = Excellent show. Look for it. ** = Average movie. Kind of enjoyable. * = Poor show. Don't waste your money. 0 = Totally and painfully unbearable picture.
REVIEW WRITTEN ON: September 23, 1997
Opinions expressed are mine and not meant to reflect my employer's.
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


From the Death Certificate
for Adolph Harry Siegenthaler
PLACE OF DEATH:
In this community: 2 years
USUAL RESIDENCE --
NAME OF DECEASED Adolph
Harry Siegenthaler
Male, white, married to
Louisa Siegenthaler - age 64
Birth: Nov. 18, 1881 *
Age: 67 years, 2 mos, 0
days
Birthplace: Monroe Co,
Occupation: farmer,
general farming
Father: unknown, born
in
Mother: Magdalena, born
in
Informant: L A
Siegenthaler,
Burial: 1 29 45
Cemetery: Unionport
Embalmer: Dean E.
Tiller
MEDICAL CERTIFICATION
Death: January 18,
1945, 12 noon
Cause of death: coronary
occulsion 6-23-45 due to chronic arterial sclerosis 8 years ago
Physician's statement:
I HEREBY CERTIFY, That I attended deceased from coroner case.
Signed: Dr. John P.
Smarrella, coroner,
Submitter s Notes:
* date is wrong. He was in the June, 1880 census as 8 years
old. Not sure if its Nov. 18, 1871 or
Dec 18, 1881
Provided by Dianne Juhnke
Click here for the Short-Cut Table of Contents


Toggle navigation
That's What She Said Detector
That's what she said detector
{{ response }}
you can try: You're not going fast enough!


{{article.text}}
Posted by {{article.username}} on {{article.timestamp| date: 'MM/dd/yyyy @ h:mm a'}}


{% extends "templates/web.html" %} {% block title %}{{ _("Payment Success") }}{% endblock %} {%- block header -%}
{{ _("Your payment was successfully accepted") }}
{{ frappe.form_dict.redirect_message or _("Continue") }}


Inside which HTML element do we put the JavaScript?
Where is the correct place to insert a JavaScript?
JavaScript is the same as Java.
How do you create a function in JavaScript?
How do you call a function named "myFunction"?
How to write an IF statement in JavaScript?
How do you find the number with the highest value of x and y?
What will the following code return: Boolean(10 > 9)
Which event occurs when the user clicks on an HTML element?
Is JavaScript case-sensitive?


For data managers¶
PMA API dataset files¶
What are dataset files for?
PMA API dataset files contain all of the contents needed to construct PMA API’s
database.
File format
The file format should be an Excel workbook with the .xlsx
file extension.
File naming
The name of the file must be named in very specific way as follows.
api_data-YYYY.MM.DD-v#-xxx
The file name is a hyphen delimited list of values, starting with the dataset type (always ‘api_data’), followed by the date in year, month, day format, followed by the version number (e.g. v1, v12, v100, etc), followed by initials (number of characters in initials does not matter). For example,
api_data-2019.04.22-v1-jef
Worksheets
The worksheets inside the file need to have very specific naming.
There is a single worksheet for each kind of structural metadata, where the
name of the worksheet is the singular noun for that metadata, e.g. country
,
geography
, etc. There is also a single worksheet called translation
, which
contains all language translations. There can be any number of data
worksheets which can be named in any way, so long as the worksheet name starts
with the word ‘data’. It is also possible to create auxiliary worksheets that
will be ignored by PMA API. To create such a worksheet, simply put a double
underscore __
at the start of the worksheet name. Columns inside of the
worksheets must also have very specific naming. Similar to worksheets, you
can also create auxiliary columns that will be ignored by the PMA API by
starting the column name with a double underscore.
Online admin area¶
PMA API offers a few simple features for data management. Namely, you can upload, download, delete, and ‘activate’ datasets.
What is ‘activation’, and how is it different than uploading?
When a dataset is uploaded, it is essentially backed up to an online storage
area. The online storage area is shared between the staging and production
servers. When you upload or delete a dataset, you will notice this change
reflected in the list of available datasets shown whether you are logged into
the staging server or the production server. Since uploading is simply storing
the dataset file online, nothing else happens once it is uploaded; the PMA API
database has not changed yet. In order to update the database with any changes
in the dataset file, we have to ‘activate’. Activation takes that file, reads
it, and imports its contents into the database.
Currently, only one dataset can be ‘active’ at a given time.
Logging in¶
You can log in by accessing the /admin
page. The credentials are pre-created
and are the same on any server, so it is not necessary/possible to register
for a new account. If the credentials have not been provided to you by the time
you read this, please check your credentials sharing service (e.g. LastPass),
or contact the person in charge of PMA API server administration.
Admin area URLs
Staging server: http://api-staging.pma2020.org/admin
Production server: http://api.pma2020.org/admin
Uploading datasets¶
As mentioned previously, uploading a dataset places the dataset in an online storage area that is shared between the staging and production servers. Uploading does not cause the contents of the dataset file to be reflected in the PMA API database. For information on doing that, please refer to the ‘activating datasets’ section.
Downloading datasets¶
Deleting datasets¶
Activating datasets¶
1. Activate and test on staging server¶
1.1. Make sure the dataset is uploaded¶
If the dataset you want to activate appears as a row in the datasets table, proceed to the next step. Otherwise, upload the dataset file first.
1.2. Click the ‘activate’ button¶
1.3. Wait until request resolution¶
A progress bar will display estimated progress percentage as well as a status message of the task that the server is currently executing. Some steps may hang for before you see any updates, even for several minutes. Do not worry about the possibility of a complete frozen state unless you see that the progress has not updated at all in about 20 minutes or so. If that happens, contact the PMA API server administrator.
Progress updates
Success!
1.4. Troubleshoot issues¶
If any issues occur during the activation process, a notification bar will appear. Typically, these messages will include helpful information, such as information about parts of the dataset file that may contain issues that need to be corrected.
1.5. Verify / test on Datalab¶
After the progress bar reaches 100%, the dataset will have been activated. While Datalab does run some automated validation and testing, it is essential to do some manual testing and verification. For example, a good method of testing would be to open up an application that connects to the API, e.g. Datalab, and try to create some charts. If some metadata was added, deleted, or otherwise changed in the latest dataset activated, do you see those changes correctly reflected in Datalab? Are you able to successfully make a chart that utilizes some new data that has been added? Do the numbers or appearance of the graph reflect what you might expect?
Datalab URLs
Staging server: http://datalab-staging.pma2020.org
Production server: http://datalab.pma2020.org
2. Activate and test on production server¶
After the dataset has been activated and tested on the staging server, repeat this same process for the production server.


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
32
33 34 35
36 import xdc.runtime.ILogger;
37 import xdc.runtime.Log;
38 import xdc.rov.ViewInfo;
39
40 /*!
41 * ======== LoggerIdle ========
42 * A logger which routes `Log` events to a users transport function.
43 *
44 * This logger processes log events as they are generated, stores them in
45 * a buffer and during idle sends a section of the buffer to the user's
46 * transport function. If you are seeing no log events or dropping too
47 * many events check that you are not logging too often and have enough idle
48 * time to send. LoggerIdle is compatable with StellarisWare and MWare
49 * devices. Example transports for UART (B92 and F28M35x) and USB (F28M35x)
50 * as well as initialization functions are included in the evmF28M35x.c files
51 * under the device folder in the ti.examples directory.
52 *
53 * @a(Examples)
54 * Configuration example: The following XDC configuration statements
55 * create a logger module, and assign it as the default logger for all
56 * modules.
57 *
58 * @p(code)
59 * var Defaults = xdc.useModule('xdc.runtime.Defaults');
60 * var Diags = xdc.useModule('xdc.runtime.Diags');
61 * var LoggerIdle = xdc.useModule('ti.uia.sysbios.LoggerIdle');
62 *
63 * LoggerIdle.bufferSize = 60;
64 * LoggerIdle.timestamp = false;
65 * LoggerIdle.transportType = LoggerIdle.TransportType_UART;
66 * LoggerIdle.transportFxn = '&LoggerIdle_uartSend';
67 * var LoggerIdleParams = new LoggerIdle.Params();
68 * Defaults.common$.logger = LoggerIdle.create(LoggerIdleParams);
69 * @p
70 */
71
72 @Template("./LoggerIdle.xdt")
73 module LoggerIdle inherits ILogger {
74
75 /*!
76 * ======== TransportType ========
77 * Used to specify the type of transport to use
78 *
79 * This enum is used by the instrumentation host to determine what
80 * the transport is. It is not used by the target code.
81 */
82 enum TransportType {
83 TransportType_UART = 0,
84 TransportType_USB = 1,
85 TransportType_ETHERNET = 2,
86 TransportType_CUSTOM = 3
87 };
88
89 /*!
90 * @_nodoc
91 * ======== ModuleView ========
92 */
93 metaonly struct ModuleView {
94 Bool isEnabled;
95 Bool isTimestampEnabled;
96 Int bufferSize;
97 UInt sequenceNumber;
98 String transportType;
99 String customTransport;
100 }
101
102 metaonly struct RecordView {
103 Int sequence;
104 Long timestampRaw;
105 String modName;
106 String text;
107 Int eventId;
108 String eventName;
109 IArg arg0;
110 IArg arg1;
111 IArg arg2;
112 IArg arg3;
113 IArg arg4;
114 IArg arg5;
115 IArg arg6;
116 IArg arg7;
117 }
118
119 /*!
120 * @_nodoc
121 * ======== rovViewInfo ========
122 */
123 @Facet
124 metaonly config ViewInfo.Instance rovViewInfo =
125 ViewInfo.create({
126 viewMap: [
127 ['Module',
128 {
129 type: ViewInfo.MODULE,
130 viewInitFxn: 'viewInitModule',
131 structName: 'ModuleView'
132 }
133 ],
134 ['Records',
135 {
136 type: xdc.rov.ViewInfo.MODULE_DATA,
137 viewInitFxn: 'viewInitRecords',
138 structName: 'RecordView'
139 }
140 ]
141 ]
142 });
143
144 /*!
145 * ======== RtaData ========
146 * Data added to the RTA MetaData file to support System Analyzer
147 */
148 @XmlDtd metaonly struct RtaData {
149 Int instanceId;
150 }
151
152 /*!
153 * ======== LoggerFxn ========
154 * Typedef for the transport function pointer.
155 */
156 typedef Int (*LoggerFxn)(UChar *, Int);
157
158 /*!
159 * ======== bufferSize ========
160 * LoggerIdle buffer size in 32-bit words.
161 */
162 config SizeT bufferSize = 256;
163
164 /*!
165 * ======== isTimestampEnabled ========
166 * Enable or disable logging the 64b local CPU timestamp
167 * at the start of each event
168 *
169 * Having a timestamp allows an instrumentation host (e.g.
170 * System Analyzer) to display events with the correct system time.
171 */
172 config Bool isTimestampEnabled = true;
173
174 /*!
175 * ======== transportType ========
176 * Transport used to send the records to an instrumentation host
177 *
178 * This parameter is used to specify the transport that the
179 * `{@link #transportFxn}` function will use to send the buffer to
180 * an instrumentation host (e.g. System Analyzer in CCS).
181 *
182 * This parameter is placed into the generated UIA XML file. The
183 * instrumentation host can use the XML file to help it auto-detect as
184 * much as possible and act accordingly.
185 *
186 * If the desired transport is not in the `{@link #TransportType}` enum,
187 * select `{@link #TransportType_CUSTOM}` and set the
188 * `{@link #customTransportType}` string with the desired string.
189 */
190 metaonly config TransportType transportType = TransportType_UART;
191
192 /*!
193 * ======== customTransportType ========
194 * Custom transport used to send the records to an instrumentation host
195 *
196 * If the desired transport is not in the `{@link #TransportType}` enum,
197 * and `{@link #transportType}` is set to `{@link #TransportType_CUSTOM}`,
198 * this parameter must be filled in with the correct transport name.
199 *
200 * If `{@link #transportType}` is NOT set to
201 * `{@link #TransportType_CUSTOM}`, this parameter is ignored.
202 */
203 config String customTransportType = null;
204
205 /*!
206 * ======== transportFxn ========
207 * User defined transport function responsible for transmitting the records
208 */
209 config LoggerFxn transportFxn = null;
210
211 /*!
212 * @_nodoc
213 * ======== writeWhenFull ========
214 *
215 * This configuration parameter has been deprecated. The behavior
216 * is now to always allow wtites when the LoggerIdle buffer is full.
217 *
218 * Allow Log writes to succeed even if the the LoggerIdle buffer is
219 * full.
220 *
221 * LoggerIdle maintains a circular buffer where the Log events are
222 * written. A write pointer indicates the location in the buffer
223 * where the next Log event can be written to, and a read pointer
224 * indicates the location of the next Log event to be sent to the
225 * user's transport function. Log write calls cause the write pointer
226 * to advance, and when Log data is passed to the user's transport
227 * function in the idle loop, the read pointer advances. If the
228 * read pointer catches up the the write pointer, the buffer is
229 * 'empty', and if the write pointer catches up the the read pointer,
230 * the buffer is full.
231 *
232 * The LoggerIdle buffer will fill up, if the idle function to output
233 * the Log data cannot keep up with the Log writes. When this happens,
234 * if writeWhenFull is false, Log writes will not put any new data
235 * into the buffer until the LoggerIdle transportFxn has been called
236 * to empty some of the buffer. As a result, the most recent Log
237 * events could be lost. This is a simple solution to dealing with a
238 * full buffer. Since Log event sizes vary, it avoids having to
239 * determine how much the read pointer must be adjusted to fit a new
240 * Log event. It also allows you to send a large chunk of the buffer
241 * to the transport function in one shot, since the data will not
242 * be overwritten by Log writes during the transfer. If Log events
243 * are infrequent or the idle time is sufficient to get the Log
244 * data out, then disabling writeWhenFull may be appropriate.
245 *
246 * When this flag is set to true, if the LoggerIdle buffer is full,
247 * new Log data will be written over the oldest Log record(s) in the
248 * buffer. The oldest Log records in the buffer will be lost when
249 * this happens.
250 *
251 * The cost of enabling writeWhenFull is an increase in Log write
252 * times when the buffer is full, as the buffer's read pointer will
253 * need adjusting. There is also more overhead to get the Log data
254 * out through the transport function. When writeWhenFull is enabled,
255 * LoggerIdle's idle function will copy one Log record at a time into
256 * a temporary buffer, and send the temporary buffer to the user's
257 * transport function. This is to minimize interrupt latency, as the
258 * buffer's read pointer can now be modified by both the idle function
259 * and Log writes, and must be protected. The advantage, though, is
260 * that you will not lose the most recent Log data when the buffer is
261 * full. If Log events are frequent and the idle time is insufficient
262 * to get the Log data out, then enabling writeWhenFull may be
263 * appropriate.
264 */
265 config Bool writeWhenFull = false;
266
267 /*!
268 * @_nodoc
269 * ======== L_test ========
270 * Event used for benchmark tests
271 */
272 config xdc.runtime.Log.Event L_test = {
273 mask: xdc.runtime.Diags.USER1,
274 msg: "Test Event"
275 };
276
277 /*!
278 * ======== flush ========
279 * Call the transport function to empty out the LoggerIdle buffer.
280 *
281 * This API is not intended for general use, but could be used for
282 * example, in an exception handler to recover the most recent Log
283 * data that was written after the last run of the idle loop.
284 *
285 * NOTE: Calling LoggerIdle_flush() when the idle task was in the
286 * middle of outputting data can result in lost data. Since the idle
287 * function only outputs one Log record at a time, so at most one record
288 * could be lost.
289 */
290 Void flush();
291
292 /*!
293 * @_nodoc
294 * ======== initDecoder ========
295 * Initialize the Java LoggerIdleDecoder for use in the LoggerIdle
296 * 'Records' ROV view.
297 */
298 function initDecoder();
299
300 instance:
301 /*!
302 * ======== create ========
303 * Create a `LoggerIdle` logger
304 *
305 * The logger instance will route all log events it receives to
306 * the Uart.
307 */
308 create();
309
310 @DirectCall
311 override Void write0(xdc.runtime.Log.Event evt, xdc.runtime.Types.ModuleId mid);
312
313 @DirectCall
314 override Void write1(xdc.runtime.Log.Event evt, xdc.runtime.Types.ModuleId mid,
315 IArg a1);
316
317 @DirectCall
318 override Void write2(xdc.runtime.Log.Event evt, xdc.runtime.Types.ModuleId mid,
319 IArg a1, IArg a2);
320
321 @DirectCall
322 override Void write4(xdc.runtime.Log.Event evt, xdc.runtime.Types.ModuleId mid,
323 IArg a1, IArg a2, IArg a3, IArg a4);
324
325 @DirectCall
326 override Void write8(xdc.runtime.Log.Event evt, xdc.runtime.Types.ModuleId mid,
327 IArg a1, IArg a2, IArg a3, IArg a4,
328 IArg a5, IArg a6, IArg a7, IArg a8);
329
330 internal:
331
332 /*!
333 * ======== idleWrite =========
334 * Idle function that calls the transport function.
335 */
336 Void idleWrite();
337
338 /*!
339 * ======== idleWriteEvent =========
340 * Idle function that calls the transport function to write one
341 * Log event.
342 */
343 Void idleWriteEvent();
344
345 Void write(Log.Event evt, xdc.runtime.Types.ModuleId mid,
346 IArg numEventWords,
347 IArg a1, IArg a2, IArg a3, IArg a4,
348 IArg a5, IArg a6, IArg a7, IArg a8);
349
350 struct Module_State {
351 LoggerFxn loggerFxn;
352 Bool enabled;
353 Bool empty;
354 UInt bufferSize;
355 UInt32 idleBuffer[];
356 UInt32 tempBuffer[];
357 UInt32 *bufferRead;
358 UInt32 *bufferWrite;
359 UInt32 *bufferPad; 360
361 UInt32 *bufferEnd;
362 UInt16 eventSequenceNum;
363 };
364
365 struct Instance_State {
366 };
367 }


My profile
Settings
LOG OUT
Welcome
TOM
SUPPORT THIS CREATORR
Support your favorite creator
Prefill form
Amount ($)
Card number
CVV
Expiry
Description
Billing Details
Cardholder Name
Address Line 1
Address Line 2
Postalcode
City
District
Country Code
Phone number
Email
Thank you! Here's your NFT
Their NFT'S up for offering


All Files
(100.0%
covered at
1.25
hits/line)
4 files in total.
25 relevant lines.
25 lines covered and
0 lines missed
-
1
class Country < ActiveRecord::Base
-
1
has_many :projects, dependent: :destroy
-
1
validates :name, :presence => true
-
1
validates :continent, :presence => true
-
1
validates :description, :presence => true
-
-
1
has_attached_file :attached_image, :styles => { :medium => "300x300>", :thumb => "100x100>" }, :default_url => "/images/:style/missing.png"
-
1
validates_attachment_content_type :attached_image, :content_type => /\Aimage\/.*\Z/
-
-
end
-
1
class Project < ActiveRecord::Base
-
1
has_and_belongs_to_many :users
-
1
belongs_to :country
-
-
1
validates_presence_of :total_needed
-
1
validates :name, :presence => true
-
1
validates :description, :presence => true
-
-
1
has_attached_file :project_image, :styles => { :medium => "300x300>", :thumb => "100x100>" }, :default_url => "/images/:style/missing.png"
-
1
validates_attachment_content_type :project_image, :content_type => /\Aimage\/.*\Z/
-
end
-
1
require 'rails_helper'
-
-
1
describe Project do
-
2
it { should validate_presence_of :total_needed }
-
2
it { should validate_presence_of :name }
-
2
it { should validate_presence_of :description }
-
2
it { should have_and_belong_to_many :users }
-
end
-
1
require 'rails_helper'
-
-
1
describe User do
-
2
it { should validate_presence_of :email }
-
2
it { should have_and_belong_to_many :projects}
-
end


NeurotechNeuroTech #HackNights |
|
Wednesday, 7:00 PM (Weekly) q Every Wednesday (previously Thursday) we'll have our #HackNights at District 3 from 18h to 22h ! They are open to beginners and pros. More advanced people will already be working on awesome projects like [... come and you'll see ...] and beginners will have an intro to BCI and will have a tutorial to be up and running with BCI in no time. |
|
Location : Faubourg Tower on Guy and Ste Catherine, 6th Floor, Montréal |
BSYS Coding Nights (Coming soon) |
|
Thursday, 7:00 PM (Weekly) Every Thursday we meet up to work on our projects. Feel free to join us as we try to gain more knowledge and experience. We usually meet up at D3 as the material is stored there. |
|
Location : Faubourg Tower on Guy and Ste Catherine, 6th Floor, Montréal |


Im passionate about showing others their most beautiful selves
Adobe Photoshop, Premiere Pro, Customer Service
Check my IG Check it out


Painted Desert [at73], desert, in Imperia, wilderness
Last updated Turn #106
Painted Desert [at73], desert, in Imperia, wilderness
------------------------------------------------------------------------
9: Stack of nazgul [iu4i], nazgul, number: 3, arrived from the south.
11: Stack of nazgul [iu4i], nazgul, number: 3, went north.
25: Stack of nazgul [fz8c], nazgul, number: 3, arrived from the north.
25: Pack of wolves [fp1e], wolves, number: 5, arrived from the south.
26: Bzee B [c5r], refugee, with one peasant, arrived from the south.
27: Stack of nazgul [fz8c], nazgul, number: 3, went south.
27: Pack of wolves [fp1e], wolves, number: 5, went north.
28: Bzee B [c5r], refugee, with one peasant, went north.
28: Dolf [x2b], refugee, with one riding horse, arrived from the north.
30: Dolf [x2b], refugee, with one riding horse, went south.
Routes leaving Painted Desert:
North, plain, to Buffalo Plains [as73], 7 days
East, desert, to Painted Desert [at74], 8 days
South, desert, to Painted Desert [au73], 8 days
West, plain, to Buffalo Plains [at72], 7 days
Seen here:
Stack of nazgul [er9j], nazgul, number: 4
Stack of nazgul [gm5n], nazgul, number: 3
Bzee B [c5r], refugee, with one peasant
Dolf [x2b], refugee, with one riding horse


HALLELUJAH THE HILLS (director/writer/editor: Adolfas Mekas; cinematographer: Ed Emshwiller; cast: Peter H. Beard (Jack), Sheila Finn (Jack's Vera in Winter), Martin Greenbaum (Leo), Peggy Steffans (Leo's Vera in Summer), Jerome Raphel (Father), Blanche Dee (Mother), Jerome Hill (Convict), Taylor Mead (Convict), Ed Emshwiller (Gideon); Runtime: 88; 1962)
Reviewed by Dennis Schwartz
The cinematographer Ed Emshwiller, once known as Emsh, used a hand-held 135-pound sound camera for some scenes, often composing superimpositions in the camera. The director Adolfas Mekasis is the brother of noted Greenwich Village underground director and film historian Jonas, who is credited with assisting his brother during the shooting. Adolfas has come up with an offbeat, lighthearted romantic/comedy spoof, that gently mocks France's New Wave cinema, which was the vogue among intellectuals at the time. This is a film geared to film buffs and indie lovers who are interested in some of the early 1960s works coming out of the underground cinema movement in the States. There is no political message or drug visualizations here, as the film tends to rely on the energy conveyed by the characters and the fun they seemed to be having with this unpredictable material they had to work with. If you're into sight-gags and strange visual images, then you should be pleased with the enthusiastic direction of this film. I enjoyed it as a look back at a more innocent time in cinema and a chance to watch it poke fun at other arty styles of cinema. The comedy part of the film had the feel of those Buster Keaton silent ones.
The story is about two city boys who take to the woods to find the girl they both love, Vera, and find out which of them she will marry. When her father gleefully tells them, almost jumping for joy to see their expressions sadden, that she married Gideon two months ago because she was tired of waiting for them to ask, the boys take to the woods in the winter climate, trying to recall in their flashbacks the reasons for their obsessive attraction to her.
As an homage to the 'New Wave,' Vera is played by a different actress in the courting scenes with Jack and Leo, which take place during different seasons. I guess they both had different impressions of her, so it does make sense that they see her differently, therefore why not have a different actress play her for each.
The bizarre visuals gave this film its slapstick look, as there was one scene of the boys dancing a Hebrew dance by a campfire in the woods, in another Chinese subtitles appear to the side of a landscape scene, in another the boys frolic in a frozen lake, in one scene there are people instead of birds on the branches of a tree. It was goofy fun. My favorite scene was of the two escaped convicts dressed in their striped prison uniforms, fighting a duel, which brought a fit conclusion to the two lovers and their search for answers.
REVIEWED ON 11/21/2000 GRADE: C
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


Dorothy and the Wizard in Oz
by L. Frank Baum
Chapter 17: “The Nine Tiny Piglets”
Additional Information
- Year Published: 1908
- Language: English
- Country of Origin: United States of America
- Source: Baum, F. L. (1908). Dorothy and the Wizard in Oz. Chicago: Reilly and Britton.
-
Readability:
- Flesch–Kincaid Level: 6.0
- Word Count: 2,403
- Genre: Fantasy
- Keywords: 20th century literature, american literature, books of oz, l. frank baum, self-help
- ✎ Cite This
Downloads
After breakfast Ozma announced that she had ordered a holiday to be observed throughout the Emerald City, in honor of her visitors. The people had learned that their old Wizard had returned to them and all were anxious to see him again, for he had always been a rare favorite. So first there was to be a grand procession through the streets, after which the little old man was requested to perform some of his wizardries in the great Throne Room of the palace. In the afternoon there were to be games and races.
The procession was very imposing. First came the Imperial Cornet Band of Oz, dressed in emerald velvet uniforms with slashes of pea-green satin and buttons of immense cut emeralds. They played the National air called “The Oz Spangled Banner,” and behind them were the standard bearers with the Royal flag. This flag was divided into four quarters, one being colored sky-blue, another pink, a third lavender and a fourth white. In the center was a large emerald-green star, and all over the four quarters were sewn spangles that glittered beautifully in the sunshine. The colors represented the four countries of Oz, and the green star the Emerald City.
Just behind the royal standard-bearers came the Princess Ozma in her royal chariot, which was of gold encrusted with emeralds and diamonds set in exquisite designs. The chariot was drawn on this occasion by the Cowardly Lion and the Hungry Tiger, who were decorated with immense pink and blue bows. In the chariot rode Ozma and Dorothy, the former in splendid raiment and wearing her royal coronet, while the little Kansas girl wore around her waist the Magic Belt she had once captured from the Nome King.
Following the chariot came the Scarecrow mounted on the Sawhorse, and the people cheered him almost as loudly as they did their lovely Ruler. Behind him stalked with regular, jerky steps, the famous machine-man called Tik-tok, who had been wound up by Dorothy for the occasion. Tik-tok moved by clockwork, and was made all of burnished copper. He really belonged to the Kansas girl, who had much respect for his thoughts after they had been properly wound and set going; but as the copper man would be useless in any place but a fairy country Dorothy had left him in charge of Ozma, who saw that he was suitably cared for.
There followed another band after this, which was called the Royal Court Band, because the members all lived in the palace. They wore white uniforms with real diamond buttons and played “What is Oz without Ozma” very sweetly.
Then came Professor Woggle-Bug, with a group of students from the Royal College of Scientific Athletics. The boys wore long hair and striped sweaters and yelled their college yell every other step they took, to the great satisfaction of the populace, which was glad to have this evidence that their lungs were in good condition.
The brilliantly polished Tin Woodman marched next, at the head of the Royal Army of Oz which consisted of twenty-eight officers, from Generals down to Captains. There were no privates in the army because all were so courageous and skillful that they had been promoted one by one until there were no privates left. Jim and the buggy followed, the old cab-horse being driven by Zeb while the Wizard stood up on the seat and bowed his bald head right and left in answer to the cheers of the people, who crowded thick about him.
Taken altogether the procession was a grand success, and when it had returned to the palace the citizens crowded into the great Throne Room to see the Wizard perform his tricks.
The first thing the little humbug did was to produce a tiny white piglet from underneath his hat and pretend to pull it apart, making two. This act he repeated until all of the nine tiny piglets were visible, and they were so glad to get out of his pocket that they ran around in a very lively manner. The pretty little creatures would have been a novelty anywhere, so the people were as amazed and delighted at their appearance as even the Wizard could have desired. When he had made them all disappear again Ozma declared she was sorry they were gone, for she wanted one of them to pet and play with. So the Wizard pretended to take one of the piglets out of the hair of the Princess (while really he slyly took it from his inside pocket) and Ozma smiled joyously as the creature nestled in her arms, and she promised to have an emerald collar made for its fat neck and to keep the little squealer always at hand to amuse her.
Afterward it was noticed that the Wizard always performed his famous trick with eight piglets, but it seemed to please the people just as well as if there had been nine of them.
In his little room back of the Throne Room the Wizard had found a lot of things he had left behind him when he went away in the balloon, for no one had occupied the apartment in his absence. There was enough material there to enable him to prepare several new tricks which he had learned from some of the jugglers in the circus, and he had passed part of the night in getting them ready. So he followed the trick of the nine tiny piglets with several other wonderful feats that greatly delighted his audience and the people did not seem to care a bit whether the little man was a humbug Wizard or not, so long as he succeeded in amusing them. They applauded all his tricks and at the end of the performance begged him earnestly not to go away again and leave them.
“In that case,” said the little man, gravely, “I will cancel all of my engagements before the crowned heads of Europe and America and devote myself to the people of Oz, for I love you all so well that I can deny you nothing.”
After the people had been dismissed with this promise our friends joined Princess Ozma at an elaborate luncheon in the palace, where even the Tiger and the Lion were sumptuously fed and Jim the Cab-horse ate his oatmeal out of a golden bowl with seven rows of rubies, sapphires and diamonds set around the rim of it.
In the afternoon they all went to a great field outside the city gates where the games were to be held. There was a beautiful canopy for Ozma and her guests to sit under and watch the people run races and jump and wrestle. You may be sure the folks of Oz did their best with such a distinguished company watching them, and finally Zeb offered to wrestle with a little Munchkin who seemed to be the champion. In appearance he was twice as old as Zeb, for he had long pointed whiskers and wore a peaked hat with little bells all around the brim of it, which tinkled gaily as he moved. But although the Munchkin was hardly tall enough to come to Zeb’s shoulder he was so strong and clever that he laid the boy three times on his back with apparent ease.
Zeb was greatly astonished at his defeat, and when the pretty Princess joined her people in laughing at him he proposed a boxing-match with the Munchkin, to which the little Ozite readily agreed. But the first time that Zeb managed to give him a sharp box on the ears the Munchkin sat down upon the ground and cried until the tears ran down his whiskers, because he had been hurt. This made Zeb laugh, in turn, and the boy felt comforted to find that Ozma laughed as merrily at her weeping subject as she had at him.
Just then the Scarecrow proposed a race between the Sawhorse and the Cab-horse; and although all the others were delighted at the suggestion the Sawhorse drew back, saying:
“Such a race would not be fair.”
“Of course not,” added Jim, with a touch of scorn; “those little wooden legs of yours are not half as long as my own.”
“It isn’t that,” said the Sawhorse, modestly; “but I never tire, and you do.”
“Bah!” cried Jim, looking with great disdain at the other; “do you imagine for an instant that such a shabby imitation of a horse as you are can run as fast as I?”
“I don’t know, I’m sure,” replied the Sawhorse.
“That is what we are trying to find out,” remarked the Scarecrow. “The object of a race is to see who can win it—or at least that is what my excellent brains think.”
“Once, when I was young,” said Jim, “I was a race horse, and defeated all who dared run against me. I was born in Kentucky, you know, where all the best and most aristocratic horses come from.”
“But you’re old, now, Jim,” suggested Zeb.
“Old! Why, I feel like a colt today,” replied Jim. “I only wish there was a real horse here for me to race with. I’d show the people a fine sight, I can tell you.”
“Then why not race with the Sawhorse?” enquired the Scarecrow.
“He’s afraid,” said Jim.
“Oh, no,” answered the Sawhorse. “I merely said it wasn’t fair. But if my friend the Real Horse is willing to undertake the race I am quite ready.”
So they unharnessed Jim and took the saddle off the Sawhorse, and the two strangely matched animals were stood side by side for the start.
“When I say ‘Go!’” Zeb called to them, “you must dig out and race until you reach those three trees you see over yonder. Then circle ‘round them and come back again. The first one that passes the place where the Princess sits shall be named the winner. Are you ready?”
“I suppose I ought to give the wooden dummy a good start of me,” growled Jim.
“Never mind that,” said the Sawhorse. “I’ll do the best I can.”
“Go!” cried Zeb; and at the word the two horses leaped forward and the race was begun.
Jim’s big hoofs pounded away at a great rate, and although he did not look very graceful he ran in a way to do credit to his Kentucky breeding. But the Sawhorse was swifter than the wind. Its wooden legs moved so fast that their twinkling could scarcely be seen, and although so much smaller than the cab-horse it covered the ground much faster. Before they had reached the trees the Sawhorse was far ahead, and the wooden animal returned to the starting place and was being lustily cheered by the Ozites before Jim came panting up to the canopy where the Princess and her friends were seated.
I am sorry to record the fact that Jim was not only ashamed of his defeat but for a moment lost control of his temper. As he looked at the comical face of the Sawhorse he imagined that the creature was laughing at him; so in a fit of unreasonable anger he turned around and made a vicious kick that sent his rival tumbling head over heels upon the ground, and broke off one of its legs and its left ear.
An instant later the Tiger crouched and launched its huge body through the air swift and resistless as a ball from a cannon. The beast struck Jim full on his shoulder and sent the astonished cab-horse rolling over and over, amid shouts of delight from the spectators, who had been horrified by the ungracious act he had been guilty of.
When Jim came to himself and sat upon his haunches he found the Cowardly Lion crouched on one side of him and the Hungry Tiger on the other, and their eyes were glowing like balls of fire.
“I beg your pardon, I’m sure,” said Jim, meekly. “I was wrong to kick the Sawhorse, and I am sorry I became angry at him. He has won the race, and won it fairly; but what can a horse of flesh do against a tireless beast of wood?”
Hearing this apology the Tiger and the Lion stopped lashing their tails and retreated with dignified steps to the side of the Princess.
“No one must injure one of our friends in our presence,” growled the Lion; and Zeb ran to Jim and whispered that unless he controlled his temper in the future he would probably be torn to pieces.
Then the Tin Woodman cut a straight and strong limb from a tree with his gleaming axe and made a new leg and a new ear for the Sawhorse; and when they had been securely fastened in place Princess Ozma took the coronet from her own head and placed it upon that of the winner of the race. Said she:
“My friend, I reward you for your swiftness by proclaiming you Prince of Horses, whether of wood or of flesh; and hereafter all other horses—in the Land of Oz, at least—must be considered imitations, and you the real Champion of your race.”
There was more applause at this, and then Ozma had the jeweled saddle replaced upon the Sawhorse and herself rode the victor back to the city at the head of the grand procession.
 It’s no place for us, Zeb.”
“It’s lucky we got here, though,” said the boy; and Jim thought of the dark cave, and agreed with him.


@(schemes: List[Scheme])(implicit hubContext: HubContext) @main("Topics - TopicHub") {
Topics are at the heart of how TopicHub helps you discover content. Each topic is an identifier or term belonging to a standard vocabulary or name-space, known as its scheme. Relative to this scheme, the topic describes, characterizes or classifies the item. Topics help organize items into groups that are of interest to subscribers: all articles in a particular journal, everything written by a certain author, etc. Explore the topics within a scheme by clicking on one of the scheme browse links at the left, or search for topics above.


2001 A Space Odyssey Translator
Please Enter Your Name Here:
Enter Your Number Here:
Submit For Results!


As a spirit of wind use your powers to help (literally) prince of the beautiful and mysterious kingdom to avenge his family and save the world.
 Fight your annoying siblings by making up your personal story of success. The game was developed as a 2-week team assignment at UCSC Games and Playable media program
Built with the goal of creating a truly social online VR experience, Spellcasters VR takes the fantasy of magic duels, and turns it into a team based competitive experience. Each player chooses their role (attacker, tank, healer), and draws gestures with their wands to summon offensive or defensive spells. Strategizing in the heat of battle is a must, as each role has unique abilities that will greatly benefit their team members. This project supports multiplatform players using both the HTC Vive and Oculus Rift to connect and play together.
Compete with your friends for the vital resources in the heart of a deadly desert. Survival of the fittest in it's pure form. Rapid project from UCSC Games and Playable media made in Unity3D
Hi! I'm Anton Starodub. I love people. However, human interaction is the most mysterious thing for me. I think, games simplify it a lot. They are the smooth tools of interaction, that disarm us, take away the sharp edges of our personality. They help us to focus on the process of interaction, rather than differences of the opinions or personalities. I'm the game designer, therefore, I'm the communication simplifier. Let's make people communicate! Let's make World a little better.


AZURE DEVOPS – MANAGE YOUR APPLICATION LIFECYCLE IN CLOUD
Application lifecycle management (ALM) is the product lifecycle management of computer programs.
It encompasses requirements management, software architecture, computer programming, software testing, software maintenance, change management, continuous integration, project management, and release management.
An ALM tool should have the capability to maintain all the aspects of a software lifecycle, such as capturing the ideas, users requirement, planning of work, maintaining source code, deploying code using continuous integration and continuous delivery (CI/CD). It should also provide real time project insights to the key stake holders of a project. We can think of an ALM software as one stop shop for a software project/product management as a whole.
In this post we will take a look at Microsoft’s Azure DevOps offering, it’s capability as an ALM solution and will see how you can use it for your ALM journey.
What is Azure DevOps?
In a single sentence, Azure DevOps is a suite of offering in the cloud that you need to build your software product/project from beginning to end.
Azure DevOps, formerly known as Visual Studio Team System (VSTS). It helps you to plan your project, manage source code in repositories like Git, TFVC, Subversion, GitHub and deploys the code through the CI/CD pipeline system to cloud or in on-premise resources.
Additionally it gives a collaborative platform for developers, business users and test engineers, project managers under one umbrella to real time tracking of work and quick shipment of the product.
Six pillars of Azure DevOps
Azure DevOps has six major pillars which helped it to shape as complete ALM offering in the the cloud. Let’s briefly look into the the major pillars of Azure DevOps
Azure Boards is a place to manage and plan all of your work.** All ideas** and business requirements for your software can be captured here. You can create epics, features, user stories and then estimate them and plan capacity of your team members and start the sprint.
Additionally you can have a real time view of the work item progression in Kanban boards, sprint burn down charts.
Azure Repos supports various source control system like Azure Git, Public GitHub, GitHub Enterprise, Microsoft’s own Team foundation version control (TFVC), External Git.
You can choose any one of the repositories for your choice for software development and source code. Once development is done developers can create a pull request with their changes, send it for code review and take part of a collaborative development environment.
Azure Pipelines are used for continuous integration and continuous delivery (CI/CD) of your code. It allows you to ship your code faster.
Once your code is developed and committed to the repos, a build gets triggered in the build pipeline. This build pipeline gets the latest code from the repos, builds them in the build agent. On a successful build, the build artifacts gets published using Release pipeline in your targeted deployment environment.
Azure Test Plans is for planning and executing your manual, automated and load test cases. Once the build is succeeded test engineers can run a set of tests on the build for verification and validation of the desired functionality. And they can raise and log any defects or observation on failure of any of the planned test scenarios in the Azure Boards.
Azure Artifacts manages your private NuGet, npm, Maven packages in a private feed. You can integrate this feed in your favourite IDE such as Visual Studio or Visual Studio Code and restore the packages from this feed while development. Additionally you can integrate this feed in the build pipeline and restore packages from this private repository. Azure Artifacts helps a lot where there are a lot of shared common packages in use in the application and you want to control standards, version of those cross cutting atrifacts.
Azure Overview gives real time insights of the project such as teams velocity, CI/CD results, number of defects raised vs solved at any point of time to name a few. Executive dashboards can be created with inbuilt capability of it. These dashboard helps greatly for executive status reporting with risk and quality matrices.
Additionally it supports creating Wiki pages for the project. Wiki pages can be used to create any documents/ manual which are relevant for the ongoing or a completed project.
ALM with Azure DevOps in action
Now that we have fair understanding of six pillars of Azure DevOps, now lets see how all of these helps in ALM with an example. refer to the Infographic of this post. This describes ALM in action with Azure DevOps very briefly.
In the beginning of the project or product it starts with an idea or some business requirement and after going through multiple steps it takes shape of a usable product. In this example infographic
- 1. Customer comes with requirement.
- 2. Business analysts/ Product owner analyses the requirement and starts documenting them in the Azure Boards. They starts creating Epic, Feature and user stories.
- 3. Engineering team then starts estimating the work and plan those user stories for sprint.
- 3.1. In parallel test engineers starts for Test planning in Test Plans based on the acceptance criteria of the user stories.
- 4. Once sprint kicked in – developers starts picking user stories from the backlogs created at step 2 and starts implementing them.
- 5. Once developers are done with the development they creates a pull request and sends for code review. Upon satisfaction of the code reviewer, developer commits the code in the Azure Repos.
- 6. A build gets triggered in the Build Pipeline as soon as the code gets committed in the Azure Repos using continuous integration (CI). A CI build gets the latest code form the repos, builds them in the build agents, restores any private packages from the feed setup in the Azure Artifacts. It runs unit tests, generates code coverage result and finally generates the build output for deployment. If any one of the steps configured in the build pipeline fails then whole commit gets rejected and developers gets a build failure notification. Developer fixes the build and commits one more time and CI build triggers automatically.
- 7. Build output needs to be moved to the deployment environment. In a Release Pipeline source of the build artifacts is the output of the CI build of previous step 6, destination will be the servers where these artifacts needs to be deployed. In this example it is deploying the artifacts to the Azure Cloud App Services and Azure SQL databases for a TESTING environment (step 7.1). A gate or approval mechanism can be set before the deployment happens, this gives control to the approvers to pick and choose which build to be deploy.
- 8. Now that build is deployed in TESTING environment, test engineers starts testing and verifying the build quality. They run a set of manual, automated and load tests as planned during the planning phase (step 3.1) in Azure Test Plans. If they observe any defects then they log then in Azure Boards backlog and creates a new bug/issue/observation. Developer picks these defects once these are planned and fed back to the sprint, fixes the defects and commits to the Azure Repos which eventually triggers CI/CD in Azure Pipelines.
- 9. If test engineers are satisfied with the build quality and functionality delivered, then this build gets promoted to the upper environment (step 9.1). In this example it is UAT environment for business users to test.
- 10. Business users now gets a new build in UAT environment with all the features planned for the current sprint. Business user starts verifying the build and functionality in UAT environment.
- 11. If business users finds any defects then they log them into the Azure Boards backlogs as bug/observation. Development and build cycle continues once these defects are planned and fed back to the sprint.
- 12. If business users are satisfied with the functionality and the build quality then the build gets promoted to the PRODUCTION environment (step 12.1)
Once this is released to production, end users starts using the system. If any issue occurs in the production then it again gets logged in the Azure Boards backlog as an Incident/ Bug/ Issue.
Like this planning, development and build cycle continues towards shipment of the product. In the whole process key stakeholders of the project keeps an eye on Azure Overview dashboards to identify and mitigate any risks.
Wrap up
Okay, so we are at the end of this post. In this post we have covered six pillars of the Azure Dev Ops and how this can be leveraged to manage your applications life cycle. Azure DevOps is a browser based application in public cloud with first class support and integration with numerous opensource languages and platforms. You can manage your ALM in peace of mind end to end in Azure DevOps.
- If you want to know more about the pricing check this out.
- To learn more about Azure DevOps check this video.
Oh.. wait, In the meanwhile, you can get started with your free account in Azure DevOps and start exploring. Just log in to https://dev.azure.com with your Microsoft account and start your ALM journey in cloud with Azure DevOps.


Home
Trees
Indices
Help
PyGeodesy
[
frames
] |
no frames
]
[
Identifiers
|
Term Definitions
]
Identifier Index
[
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
_
]
E
e
(in
Ellipsoid
)
ellipsoid
(in
AuxLat
)
EPS2
(in
pygeodesy.constants
)
E
(in
Geohash
)
ellipsoid
(in
Datum
)
EPS4
(in
pygeodesy
)
E0
(in
Conic
)
ellipsoid
(in
_EcefBase
)
EPS4
(in
pygeodesy.constants
)
e12
(in
Ellipsoid
)
Ellipsoid
(in
pygeodesy.ellipsoids
)
EPS_2
(in
pygeodesy
)
e2
(in
Ellipsoid
)
ellipsoid
(in
ExactTransverseMercator
)
EPS_2
(in
pygeodesy.constants
)
e2
(in
GeodesicExact
)
ellipsoid
(in
GeodesicExact
)
EPS_2
(in
pygeodesy.nvectorBase
)
e21
(in
Ellipsoid
)
ellipsoid
(in
GeodesicAreaExact
)
epsg
(in
pygeodesy
)
e22
(in
Ellipsoid
)
ellipsoid
(in
KTransverseMercator
)
Epsg
(in
pygeodesy.epsg
)
e22abs
(in
Ellipsoid
)
ellipsoid
(in
LocalCartesian
)
EPSGError
(in
pygeodesy.epsg
)
e22f()
(in
pygeodesy.ellipsoids
)
ellipsoid
(in
RhumbBase
)
epsilon
(in
LatLon
)
e2ab
(in
Triaxial_
)
ellipsoid
(in
RhumbLineBase
)
epsilon
(in
_Basequence
)
e2abs
(in
Ellipsoid
)
ellipsoid
(in
_SolveLineBase
)
equals()
(in
LatLon
)
e2ac
(in
Triaxial_
)
ellipsoid
(in
_SolveLineSolveBase
)
equals()
(in
LatLonBase
)
e2bc
(in
Triaxial_
)
ellipsoid
(in
RefFrame
)
equals()
(in
Vector3dBase
)
e2f()
(in
pygeodesy.ellipsoids
)
ellipsoid
(in
Wm
)
equals3()
(in
LatLonBase
)
e2s()
(in
Ellipsoid
)
ellipsoid()
(in
LatLonEllipsoidalBase
)
equatoradius
(in
_AlbersBase
)
e2s2()
(in
Ellipsoid
)
ellipsoid()
(in
a_f2Tuple
)
equatoradius
(in
_AzimuthalBase
)
e32
(in
Ellipsoid
)
Ellipsoid2
(in
pygeodesy.ellipsoids
)
equatoradius
(in
CassiniSoldner
)
e32abs
(in
Ellipsoid
)
ellipsoidalBase
(in
pygeodesy
)
equatoradius
(in
_EcefBase
)
e4
(in
Ellipsoid
)
ellipsoidalBaseDI
(in
pygeodesy
)
equatoradius
(in
ExactTransverseMercator
)
E_LV95
(in
ChLV9Tuple
)
ellipsoidalExact
(in
pygeodesy
)
equatoradius
(in
KTransverseMercator
)
EasNor2Tuple
(in
pygeodesy.namedTuples
)
ellipsoidalGeodSolve
(in
pygeodesy
)
Equidistant
(in
pygeodesy.azimuthal
)
EasNor3Tuple
(in
pygeodesy.namedTuples
)
ellipsoidalKarney
(in
pygeodesy
)
Equidistant
(in
LatLonEllipsoidalBase
)
EasNorAziRk4Tuple
(in
pygeodesy.css
)
ellipsoidalNvector
(in
pygeodesy
)
Equidistant
(in
LatLon
)
EasNorAziRkEqu6Tuple
(in
pygeodesy.css
)
ellipsoidalVincenty
(in
pygeodesy
)
Equidistant
(in
LatLon
)
EasNorExact4Tuple
(in
pygeodesy.deprecated
)
Ellipsoids
(in
pygeodesy
)
Equidistant
(in
LatLon
)
EasNorRadius3Tuple
(in
pygeodesy.webmercator
)
Ellipsoids
(in
pygeodesy.deprecated.datum
)
equidistant()
(in
pygeodesy.azimuthal
)
east
(in
Aer
)
ellipsoids
(in
pygeodesy
)
EquidistantExact
(in
pygeodesy.azimuthal
)
east
(in
Local9Tuple
)
Ellipsoids
(in
pygeodesy.ellipsoids
)
EquidistantGeodSolve
(in
pygeodesy.azimuthal
)
east
(in
Ned
)
ellipsoids()
(in
LatLonEllipsoidalBase
)
EquidistantKarney
(in
pygeodesy.azimuthal
)
east
(in
XyzLocal
)
elliptic
(in
pygeodesy
)
equirectangular()
(in
pygeodesy.formy
)
easting
(in
Css
)
Elliptic
(in
pygeodesy.elliptic
)
equirectangular()
(in
Vector3dBase
)
easting
(in
Lcc
)
Elliptic3Tuple
(in
pygeodesy.elliptic
)
equirectangular3()
(in
pygeodesy.deprecated
)
easting
(in
Mgrs
)
EllipticError
(in
pygeodesy.elliptic
)
equirectangular_()
(in
pygeodesy.formy
)
easting
(in
Osgr
)
EMPTY
(in
_CapsBase
)
equirectangular_()
(in
pygeodesy.geohash
)
Easting
(in
pygeodesy.units
)
EN
(in
Mgrs
)
equirectangularTo()
(in
Geohash
)
easting
(in
UtmUpsBase
)
en100k
(in
Mgrs
)
equirectangularTo()
(in
LatLonBase
)
eastingnorthing
(in
Mgrs
)
EN2_LV95
(in
ChLV9Tuple
)
errors
(in
pygeodesy
)
eastingnorthing
(in
UtmUpsBase
)
enclosures()
(in
Bounds4Tuple
)
es
(in
Ellipsoid
)
eastingnorthing2()
(in
UtmUpsBase
)
encode()
(in
pygeodesy.epsg
)
es_atanh()
(in
Ellipsoid
)
Ecef
(in
CartesianBase
)
encode()
(in
pygeodesy.gars
)
es_c
(in
Ellipsoid
)
ecef
(in
pygeodesy
)
encode()
(in
pygeodesy.geohash
)
es_tauf()
(in
Ellipsoid
)
Ecef
(in
Cartesian
)
encode()
(in
pygeodesy.wgrs
)
es_taupf()
(in
Ellipsoid
)
Ecef
(in
LatLon
)
encodeEPSG()
(in
pygeodesy.deprecated
)
etm
(in
pygeodesy
)
Ecef
(in
Cartesian
)
endian
(in
_GeoidBase
)
Etm
(in
pygeodesy.etm
)
Ecef
(in
LatLon
)
enStr2()
(in
pygeodesy.deprecated
)
ETMError
(in
pygeodesy.etm
)
Ecef
(in
LatLonBase
)
enstr2()
(in
pygeodesy.streprs
)
euclid
(in
Vector3dBase
)
ecef
(in
LocalCartesian
)
Enu
(in
pygeodesy.ltpTuples
)
euclid()
(in
pygeodesy.fmath
)
ecef
(in
Ltp
)
enu4
(in
XyzLocal
)
euclid_()
(in
pygeodesy.fmath
)
ecef
(in
XyzLocal
)
Enu4Tuple
(in
pygeodesy.ltpTuples
)
euclidean()
(in
pygeodesy.formy
)
Ecef
(in
NvectorBase
)
enumerate()
(in
LatLon2PsxyIter
)
euclidean_()
(in
pygeodesy.formy
)
ecef()
(in
Datum
)
enumerate()
(in
PointsIter
)
euclideanTo()
(in
Geohash
)
ecef()
(in
Ellipsoid
)
enumerate()
(in
_BaseIter
)
euclideanTo()
(in
LatLonBase
)
Ecef9Tuple
(in
pygeodesy.ecef
)
ep2
(in
GeodesicExact
)
evaluate()
(in
AuxDST
)
EcefCartesian()
(in
pygeodesy.deprecated
)
epoch
(in
LatLonEllipsoidalBase
)
exact
(in
RhumbBase
)
EcefError
(in
pygeodesy.ecef
)
epoch
(in
RefFrame
)
exact
(in
RhumbLineBase
)
EcefFarrell21
(in
pygeodesy.ecef
)
Epoch
(in
pygeodesy.units
)
Exact
(in
_SolveLineSolveBase
)
EcefFarrell22
(in
pygeodesy.ecef
)
epoch2date()
(in
pygeodesy.trf
)
exactTM
(in
Datum
)
EcefKarney
(in
pygeodesy.ecef
)
EPS
(in
pygeodesy
)
exactTM
(in
Etm
)
EcefMatrix
(in
pygeodesy.ecef
)
eps
(in
_CompositeBase
)
ExactTransverseMercator
(in
pygeodesy.etm
)
EcefSudano
(in
pygeodesy.ecef
)
EPS
(in
pygeodesy.constants
)
exception_chaining()
(in
pygeodesy.errors
)
EcefVeness
(in
pygeodesy.ecef
)
eps
(in
Elliptic
)
excessAbc()
(in
pygeodesy.deprecated
)
EcefYou
(in
pygeodesy.ecef
)
EPS
(in
pygeodesy.nvectorBase
)
excessAbc_()
(in
pygeodesy.formy
)
egmGeoidHeights()
(in
pygeodesy.geoids
)
EPS0
(in
pygeodesy
)
excessCagnoli_()
(in
pygeodesy.formy
)
elevation
(in
Aer
)
EPS0
(in
pygeodesy.constants
)
excessGirard()
(in
pygeodesy.deprecated
)
elevation
(in
Local9Tuple
)
EPS02
(in
pygeodesy
)
excessGirard_()
(in
pygeodesy.formy
)
elevation
(in
Ned
)
EPS02
(in
pygeodesy.constants
)
excessKarney()
(in
pygeodesy.formy
)
elevation
(in
XyzLocal
)
EPS1
(in
pygeodesy
)
excessKarney_()
(in
pygeodesy.formy
)
elevation2()
(in
pygeodesy.elevations
)
EPS1
(in
pygeodesy.constants
)
excessLHuilier()
(in
pygeodesy.deprecated
)
elevation2()
(in
LatLonEllipsoidalBase
)
EPS1
(in
pygeodesy.nvectorBase
)
excessLHuilier_()
(in
pygeodesy.formy
)
Elevation2Tuple
(in
pygeodesy.elevations
)
EPS1_2
(in
pygeodesy
)
excessQuad()
(in
pygeodesy.formy
)
elevations
(in
pygeodesy
)
EPS1_2
(in
pygeodesy.deprecated
)
excessQuad_()
(in
pygeodesy.formy
)
ellipsoid
(in
_AlbersBase
)
EPS2
(in
pygeodesy
)
extendp
(in
ExactTransverseMercator
)
Home
Trees
Indices
Help
PyGeodesy
Generated by Epydoc 3.0.1 on Sun Aug 20 14:42:04 2023
http://epydoc.sourceforge.net


posted by {{currentBlog.author}} on {{currentBlog.created | date}}
0">tags : {{tag}}{{last ? '' : ', '}}


TiSA: TimeSeriesAnalysis - Is a transcriptomic analysis tool for both RNA sequencing and microarray data
TimeSeriesAnalysis (TiSA) is an analysis and visualization package for RNAseq and microarray data. TS extracts significant genes from time course transcriptomic data by performing differential gene expression on both the conditional and temporal axes. It then employs partitioning algorithm based on recursive thresholding (PART) clustering to identify small genomic clusters of relevance, followed by running the clusters through gprofiler to reveal the biological relevance of each cluster.
You can install the stable version of TimeSeriesAnalysis like so:
install.packages("devtools")
devtools::install_github("Ylefol/TimeSeriesAnalysis@master")
The development version can be installed by replacing ‘master’ with ‘dev’.
Devtools is required for the installation of this package. To install Devtools, visit the Devtools main page
Certain bioconductor packages will have to be installed before installation of TimeSeriesAnalysis. The code snippet below gives the method along with some of the packages that should be installed via this method.
if (!require("BiocManager", quietly = TRUE))
install.packages("BiocManager")
bio_pkgs <- c('DESeq2','GOSemSim','GO.db','limma','ComplexHeatmap',
'AnnotationDbi','GenomeInfoDb','GenomicRanges','Biobase','S4Vectors',
'BioCGenerics','MatrixGenerics','IRanges','BiocFileCache'
'SummarizedExperiment','org.Hs.eg.db','org.Mm.eg.db','org.Ce.eg.db')
BiocManager::install(bio_pkgs)
TimeSeriesAnalysis was developed with user-friendliness in mind, the core script of the package is a Rmarkdown file with explanations of what each code block performs. Computationally intensive code blocks save their work in order to avoid loss of computation time. TimeSeriesAnalysis comes with a test dataset. Users are recommended to first run the package with the test data to then modify the Rmarkdown script with the necessary information for their purposes (input files, organism, genes of interest etc…). The rmarkdown script and the expected result from an example run can be found and downloaded from this repository, they are located in the ‘rmarkdown_method’ folder. If users prefer a script approach, the equivalent of the rmarkdown report is provided in two scripts, one for the computation tasks and a second for the analyses. These two scripts are found in the ‘script_method’ folder.
Three different datasets have been used to test this pipeline, one of which has been preserved as an example datasets for the vignettes of this pipeline. More information on the other datasets can be viewed through the publications listed below.
The PBMC dataset is a time series experiment with three time points that explores and compares three AICDA/AID (Activation Induced Cytidine DeAminase) activation cocktails. The experiment seeked to identify which activation cocktail properly activated AID through both the expression of the AID gene and the activation of class switch recombination.
The MURINE dataset is another AID related time series experiment, where mice were generated and one was given an AID activation cocktail. The experiment contains one replicate per condition and 10 timepoints. Due to only having one replicate per condition per timepoint, subsequent timepoints were combined to create an intermediary timepoint with two replicates in each condition.
The Celegans dataset is an ageing related experiment. Two celegans models were used: BY372 and N2. The first being a parkinsons model and the second being a wild type. Each model was split into two groups, one that would be fed krill oil and the other not (control). Each experiment has three timepoints: Days 1, 3, and 6.
A tutorial using the PBMC data can be found within the pipelines website. Additionally the documentation can be found in the references tab.
In order for the pipeline to run properly, a sample file must be provided. Certain requirements ust be met. Column names should be as indicated below, all spaces should be avoided, timepoints should be numerical. It is also important that the sample column contains the same names as the count files provided. Lastly, replicates should always be followed by a ’_#’ as this numbering will be utilized for the organization of the replicates within certain visualizations. Note that in the below example the three files have the same name (ex: C_1). That is to represent the ‘C_1’ sample at its three different time points.
sample file <- tibble::tribble( ~sample, ~group, ~replicate, ~timepoint, “s-37”, “control”, “C_1”, 1, “s-38”, “control”, “C_1”, 3, “s-39”, “control”, “C_1”, 9, “s-52”, “IgM”, “IgM_1”, 1, “s-53”, “IgM”, “IgM_1”, 3, “s-54”, “IgM”, “IgM_1”, 9, “s-77”, “control”, “C_2”, 1, “s-78”, “control”, “C_2”, 3, “s-79”, “control”, “C_2”, 9, “s-92”, “IgM”, “IgM_2”, 1, “s-93”, “IgM”, “IgM_2”, 3, “s-94”, “IgM”, “IgM_2”, 9 )
require(knitr) kable(sample file, digits = 3, row.names = FALSE, align = “c”, caption = NULL)
For microarray data, a streamlined method is in the works. Currently microarray data needs to be inputed as a Elist, specifically an E list saved as a rds object.
my_path_data<-'data/micro_arr/my_limma_dta.rds'
my_path_sample_dta<-'data/micro_arr/sample_file.csv'
#Set-up time series object parameters
diff_exp_type<-'limma'
The rds file given to ‘my_path_data’ contains the Elist produced by limma processing of microarray data. It is also important to set the differential gene expression type (diff_exp_type) to ‘limma’.
NOTE: You must still install the TimeSeriesAnalysis package as defined above
Since the pipeline’s source code is available, individuals are free to take the code and adapt it as needed. However for users who would like the easiest approach to use the pipeline as is, it is recommended to clone or download this github repository to your local computer and work from the Rmarkdown method folder within the repository. Cloning or downloading can be done from the TimeSeriesAnalysis github page by using the green button called ‘code’. From there, the Rmarkdown file can be edited.
To edit the file, it is recommended to use rstudio, which can be downloaded here. Note that it is recommended to download the free version of RStudio Desktop, not RStudio Server.
The only code block of code is the parameter set-up block (2nd) as well as the title at the very top of the Rmarkdown document.
The pipeline can be launched from rstudio itself by using the ‘knit’ button, or it can be launched from a command line using the following command from the TimeSeriesAnalysis repository:
A manuscript detailing the TimeSeriesAnalysis pipeline published with NAR genomics and bioinformatics. TiSA: TimeSeriesAnalysis—a pipeline for the analysis of longitudinal transcriptomics data The version/DOI of this pipeline used within the manuscript is 10.5281/zenodo.7616032.
A ageing related study was performed in part through the use of TiSA. Krill oil protects dopaminergic neurons from age-related degeneration through temporal transcriptome rewiring and suppression of several hallmarks of aging
A longitudinal COVID-19 study was performed using TiSA. Longitudinal whole blood transcriptomic analysis characterizes neutrophil activation and interferon signaling in moderate and severe COVID-19
The ‘clusterGenomics’ package was no longer maintained on CRAN and therefore the necessary scripts were brought over to this package for it’s implementation without the need to download the clusterGenomics package from source. Within this package, in the ‘R/clusterGenomics.R’ code was written by the authors of clusterGenomics. It was imported to TimeSeriesAnalysis by the authors of TimeSeriesAnalysis.


Class: User Private
- Includes:
- SystemCommand::Mixin
- Defined in:
- utils/user.rb
Overview
This class is part of a private API. This class may only be used in the Homebrew/brew repository. Third parties should avoid using this class if possible, as it may be removed or changed without warning.
A system user.
Class Method Summary collapse
-
.current ⇒ T.attached_class?
private
Return the current user.
Instance Method Summary collapse
-
#gui? ⇒ Boolean
private
Return whether the user has an active GUI session.
Methods included from SystemCommand::Mixin
#system_command, #system_command!
Class Method Details
.current ⇒ T.attached_class?
This method is part of a private API. This method may only be used in the Homebrew/brew repository. Third parties should avoid using this method if possible, as it may be removed or changed without warning.
Return the current user.
28 29 30 31 32 33 34 35 |
# File 'utils/user.rb', line 28 def self.current return @current if defined?(@current) pwuid = Etc.getpwuid(Process.euid) return if pwuid.nil? @current = new(pwuid.name) end |
Instance Method Details
#gui? ⇒ Boolean
This method is part of a private API. This method may only be used in the Homebrew/brew repository. Third parties should avoid using this method if possible, as it may be removed or changed without warning.
Return whether the user has an active GUI session.
17 18 19 20 21 22 23 24 |
# File 'utils/user.rb', line 17 def gui? out, _, status = system_command "who" return false unless status.success? out.lines .map(&:split) .any? { |user, type,| user == self && type == "console" } end |


--- title: Git and GitHub, with a side of Microsoft tags: [ computers, git, github, microsoft, open-source, software ] picture: technonerdmonster music: The Times, They are A'Changing mood: didactic location: Somewhere in cyberspace layout: post posted: Tue Jun 5 10:44:09 PDT 2018 ---
If you develop software and haven't just returned from the moon, you've undoubtedly heard that GitHub is being acquired by Microsoft. Depending on your affiliations you might be spelling "being acquired by" as "selling out to". The rest of you are probably wondering what on Earth a GitHub is, and why Microsoft would want one. Let me explain.
Please note: this post isn't about my opinion of today's news. It's really too early to tell, though I may get into that a little toward the end. Instead, I'm going to explain what GitHub is, and why it matters. But first I have to explain Git.
Git is a version-control system. (Version-control systems are sometimes called "source code management" (SCM) systems. If you look closely you might even have spotted "scm" in git's URL up there at the end of the last paragraph.) Basically, a version-control system lets you record the complete history of a project, with what changes were made, who made the each change, when they changed it, and their notes about what they did and why. It doesn't have to be a software project, either. It can be recipes, photographs, books, the papers you're writing for school, or even blog entries. (Yes, I do.)
Before git, most version-control systems kept track of changes in text
files (which of course is what all source code is) by recording which
lines are different from the previous version. (It's usually done by a
program called diff
.) This was very compact, but it could
also be very slow if you had to undo all the changes between two versions
in order to see what the older one looked like.
Git, on the other hand, is blindingly fast in part because it works in the stupidest way possible (which is why it's called "git"). It simply takes the new version of each file that changed since the last version, zips it up, and stuffs it whole into its repository. So it takes git about the same amount of time to roll a file back two versions or two hundred.
The other thing that makes git fast is where it keeps all of its
version information. Before git, most version-control systems used a
centralized repository on a server somewhere. (Subversion, one of the
best of these, even lets you browse the repository with a web browser.)
That means that all the change information is going over a network. Git
keeps its repository (these days everyone shortens that to "repo") on your
local disk, right next to your working copy, in a hidden subdirectory
called ".git
".
Because its repo is local, and contains the entire history of your
project, you don't need a network connection to use git. On the beach, in
an airplane, on a boat, with a goat, it doesn't matter to git.
It's de-centralized. It gets a little more complicated when more
than one developer is working on a project.
Bob's been in the office all week working on a project. When his boss, Alice, comes back from the open source conference she's been at all week, all she has to do is tell git to fetch all the changes that Bob made while she was away. Git gets them directly from Bob's repo. If Alice didn't make any changes, that's called a "fast-forward" merge -- git just takes the changes that Bob made, copies those files into Alice's repo, updates her working tree, and it's done.
 Now Alice has to merge the two sets of changes, and then let Bob pull the merged files onto his computer. By the way, a "pull" is just a fetch followed by a merge, but it's so common that git has a shorthand way of doing it. (I'm oversimplifying here, but this isn't the time to go into the difference between merge and rebase. It's also not a good time to talk about branches -- maybe some other week.) As you can imagine, this gets out of hand pretty quickly, and it's even worse if there's a whole team working on the project.
The obvious thing to do is for the group to have one repo on a server somewhere that has what everyone agrees is the definitive set of files on it. Bob pushes his changes to the server, and when Alice tries to push her changes, git balks and gives her an error message. Now it's Alice's responsibility to make any necessary fixes and push them to the server. Actually, in a real team, Alice would send her proposed changes around by making a diff and sending email to the other team members to review, and not actually push her changes until someone approves them.
In a large team, this is kind of a hub-and-spokes arrangement. You can see where this is going, right?
GitHub is a company that provides a place for people and projects to put shared git repositories where other people can see them, clone them, and contribute to them. GitHub has become wildly popular, because it's a great place to share software. If you have an open-source software project, putting a public repo on GitHub is the most effective way to reach developers. It's so popular that Google and Microsoft shut down their own code-hosting sites (Google Code and CodePlex respectively) and moved to GitHub. Microsoft, it turns out, is GitHub's biggest contributor.
Putting a public repository on GitHub is free. If you want to set up private repositories, GitHub will charge you for it, and if your company wants to put a clone of GitHub on its own private servers they can buy GitHub Enterprise, but if your software is free, so's your space on GitHub.
That's a bit of a problem, because the software that runs GitHub is not free. That means that they need a steady stream of income to pay their in-house developers, because they're not going to get any help from the open-source developer community. GitHub lost $66 million in 2016, and doesn't really have a sustainable business model that would make them attractive to investors. They needed to get acquired, or they had a real risk of going under. And when a service based on proprietary software goes under, all of their customers have a big problem. But their users? Heh.
Everybody knows the old adage, "if you're getting a service for free you're not the customer, you're the product." That's especially true for companies like Google and Facebook, which sell their users' eyeballs to advertisers. It's a lot less true for a company whose users can leave any time they want, painlessly, taking all their data and their readers with them. I'm sure most of my readers here on Dreamwidth remember what happened to Livejournal when they got bought by the Russians. Well, GitHub is being bought by Microsoft. It's not entirely clear which is worse.
GitHub has an even worse problem than Livejournal did, because "cross-posting" is basically the way git works. There's a company called GitLab that looks a lot like GitHub, except that their core software -- the stuff that wraps a slick web interface around a git repository -- is open source. (They do sell extensions, but most projects aren't going to need them.) If you want to set up your own private GitLab site, it's free, and you can do it in ten minutes with a one-line command. If you find bugs, you can fix them yourself. You'll find a couple of great quotes from their blog at the end of the notes, but the bottom line is that 100,000 repositories have moved from GitHub to GitLab in the last 24 hours.
And once you've moved a project to GitLab, you don't have to worry about what happens to it, because the open-source core of it will continue to be maintained by its community. That's what happened when a company called Netscape went belly-up: Mozilla Firefox is still around and doing fine. And if the fact that GitLab is for profit is a problem for you, there's Apache Allura, gitolite3, gitbucket, and gitweb (to name a few). Go for it!
This so wasn't what I was planning to write today.
Notes: @ Microsoft Reportedly Acquires GitHub | Linux Journal The article ends with a list of alternatives: Gitea Apache Allura GitBucket: A Git platform GitLab @ Microsoft acquires GitHub for $7.5 billion - TFiR " According to reports, GitHub lost over $66 millions in 2016. At the same time GitLab, a fully open source and decentralized service is gaining momentum, giving users a fully open source alternative. " @ Microsoft to acquire GitHub for $7.5 billion | Stories official press release @ Microsoft + GitHub = Empowering Developers - The Official Microsoft Blog @ A bright future for GitHub | The GitHub Blog @ Congratulations GitHub on the acquisition by Microsoft | GitLab " While we admire what's been done, our strategy differs in two key areas. First, instead of integrating multiple tools together, we believe a single application, built from the ground up to support the entire DevOps lifecycle is a better experience leading to a faster cycle time. Second, it’s important to us that the core of our product always remain open source itself as well. " @ GitLab Ultimate and Gold now free for education and open source | GitLab " It has been a crazy 24 hours for GitLab. More than 2,000 people tweeted about #movingtogitlab. We imported over 100,000 repositories, and we've seen a 7x increase in orders. We went live on Bloomberg TV. And on top of that, Apple announced an Xcode integration with GitLab. "


Preparation time
less than 30 mins
Cooking time
30 mins to 1 hour
Serves
Serves 4
Take your curry to the next level with fragrant Thai flavours and perfect sticky rice.
Place all the ingredients for the paste in a blender and blend until smooth.
Heat a wok and add 1 tbsp of the oil. Add the paste and the chicken and cook for a couple of minutes. Then stir in the coconut milk, pea aubergines and lime juice. Cover with a lid and simmer gently for 10-15 minutes, or until the chicken is completely cooked through.
For the sticky rice, rinse the rice 3 times and drain. Put the rice in a saucepan and cover with coconut milk and water to about 1cm/½in above the rice. Add the salt and cover with a lid. Place on the heat and bring to the boil. Boil for 5 minutes, then without opening the lid, turn the heat off and steam for 20 minutes.
Heat a steamer and cook the broccoli and peas for 2-3 minutes.
For the garnish, heat a small frying pan and add the oil. Once hot, add the shallots and fry until golden-brown, drain on kitchen paper.
Place the sticky rice and curry in serving bowls and garnish with the fresh coriander, peanuts and fried shallots. Serve the steamed vegetables on the side.