JUDY BERLIN (1999) / ** 1/2
Directed by Eric Mendelsohn from his screenplay. Starring Bob Dishy, Madeline Kahn, Aaron Harnick. Running time: 93 minutes. Rated AA by the MFCB. Reviewed on October 14th, 2000.
By SHANNON PATRICK SULLIVAN
Eric Mendelsohn's "Judy Berlin" is a quiet, beautifully filmed drama about the mundanity of the suburban lifestyle. Perhaps taking its cue from "The Twilight Zone" (explicitly referenced) which often dealt with similar themes, "Judy Berlin" examines the way people become trapped in their day-to-day life by interrupting their routine with the unexpected, and depicting their reactions.
Set in the Long Island community of Babylon, "Judy Berlin" takes place on a Tuesday in September. It is the second day of school. It is the day the title character, an aspiring actress, is due to leave for California. It is the day of a total solar eclipse. The principal of the local primary school is Arthur Gold (Bob Dishy). His marriage to Alice (Madeline Kahn, in her final film role) has long since exhausted its supply of affection, and he is now engaged in vague, tentative flirtation with teacher Sue Berlin (Barbara Barrie).
Meanwhile, Arthur and Alice's son David (Aaron Harnick) has returned home from Hollywood, where he has been working as a director. David has given up on life, and now endures an aimless existence, wandering the streets of Babylon. He runs into Sue's daughter Judy (Edie Falco), who is leaving town for Hollywood to break into movies. Acquaintances from their high school days, David finds himself inviting Judy to lunch despite himself, but his own experiences in the film industry threaten to taint Judy's sunny outlook.
It may not be obvious at first just why the movie is named after Judy Berlin. She is just one of several vital characters, and comes across as more of a supporting player in David's personal drama than a central protagonist on her own. But unlike all the other characters, Judy is trying to break free of the prison that is Babylon. Her dreams may be pleasant delusions (certainly, her acting abilities are more than a little suspect), her future may well be awash in doubt and uncertainty, but at least Judy is trying to craft her own future. The other principals are trapped in the endless cycle of suburban life. Even David, who did leave town once upon a time, never shed that mentality, and may indeed subvert Judy's intentions with his cynical naysaying.
It is through Judy, and the eclipse, and a elderly retired teacher (Bette Henritze) suffering from Alzheimer's that Mendelsohn gives his characters a chance to break free of this cycle and, concurrently, illustrates just how firmly ensconced in their routine they truly are. The story arc involving Arthur and Sue is probably the best example of this: By the dim light of the eclipse, Arthur finally decides to leave Alice and pursue a relationship with Sue. But he is acting on pure, raw instinct -- "I don't know what I'm doing," he confesses, and he could not be more truthful. Nothing in his life to date has prepared him for this deed; it is foreign to him, no matter how much he desires it, and he fumbles through the encounter like a child riding a bike for the first time.
Alice, meanwhile, undergoes an experience of self-revelation via the eclipse. She is the only one who is really aware that it lasts an unnaturally long time, and this is representative of the way she is slowly becoming cognisant what is happening around here. She knows beyond a shadow of a doubt that Arthur has left her and, moreover, she understands why. Alice tries to comfort herself by making light of the strange eclipse, pretending that she and her housekeeper are "space explorers", but in a sense this is a very apt description. The experiences of the day have led Alice into alien territory, a terrifying and foreign realisation of life beyond the suburban routine.
Unfortunately, although there are many nice character moments in "Judy Berlin", the movie never quite seems to come together; it is less than the sum of its parts. Mendelsohn maintains a decent pace despite his quiet, sometimes tedious subject matter, but a lot of the movie still feels insubstantial. This stems largely from the fact that he has not chosen particularly interesting characters; they serve their respective roles, but most of them fail to really engage us in their struggles. There is nothing distinctive enough to properly draw us in, and as a result, the observations made about them carry less weight than they should.
Certainly, this is not the fault of the actors, who give generally excellent performances. Dishy in particular is great to watch, finding a nice range and perfectly expressing Arthur's deep, fundamental confusion. Harnick is also commendable as David, believably portraying a man utterly disinterested in himself and life in general. Kahn, who died just three months after "Judy Berlin" debuted at the 1999 Toronto Film Festival, has fun with her material, but also has an opportunity to demonstrate her sometimes overlooked dramatic skills (Alice's realisation that Arthur has abandoned her is particular good). Of all the character arcs, though, hers feels the least thought-out, and never really finds a natural conclusion.
"Judy Berlin" is recorded entirely in black and white, and this is a laudable decision by Mendelsohn. Not only does monochrome film accentuate the surreality of Babylon under the eclipse, in the movie's early scenes it also serves to hammer home the sheer mediocrity of suburban living.
In a way, though, this only emphasises the fact that "Judy Berlin" is more an exercise of style than substance. It is lovely to watch, boasts very good performers, and contains some good ideas. But the execution is less than successful, as Mendelsohn never quite finds the proper vehicles through which to express his themes. "Judy Berlin" is kind of like the old cliche about Chinese food: enjoyable at the time, but afterward you're left looking for more.
Copyright © 2000 Shannon Patrick Sullivan. Archived at The Popcorn Gallery, http://www.physics.mun.ca/~sps/movies/JudyBerlin.html
_______________________________________________________________________ / Shannon Patrick Sullivan | "We are all in the gutter, but some of us \ |<EMAIL_ADDRESS>| are looking at the stars." - Oscar Wilde | \___________________________|__________________________________________/ | Popcorn Gallery Movie Reviews www.physics.mun.ca/~sps/movies.html | | Doctor Who: A Brief History of Time (Travel) /drwho.html |
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


Introduce The Dapp
This dapp is an all new innovation built on tron network... so in this section you write details about the platform you are building jgggggggggggggggggg
fhruiogfeygfyrkhfyvr3ggkuf3vgrmkwfvgkufvgwekjvfgfcgcgewkfcgwjcfgjcfghjfcg
A Dapp Based On Tron Network
Decentralize The World
This dapp is an all new innovation built on tron network... so in this section you write details about the platform you are building jgggggggggggggggggg
fhruiogfeygfyrkhfyvr3ggkuf3vgrmkwfvgkufvgwekjvfgfcgcgewkfcgwjcfgjcfghjfcg
In this plan, you will have a look how our project's plan will be :
As you have read, we have alot of goals to provide it for the TRON communities in general and and specially for our Project members. And we wish to get your support to let us reach the roadmap project goals at the time ! We will do our best to let you enjoy by being a member in the project.
To know more about the project, feel free to join our communities to talk more !


I am not too picky when it comes to locations I would like to visit as i like both cold and warm climates, and would like to fully experience what the world has to offer.


Licensed Administrator
License #: 197603600
Phone Number:<PHONE_NUMBER>
Here at Because We Care, we touch your loved one's life with love and care. We offer beautiful living quarters that are safe and healthy: along with 24 hour professional staff to care for individual needs.
We provide a rich program that is incorporated with tender love. Our program aims to enable the residents to maintain the highest possible social, physical and emotional balance in a caring home environment.
15942 Bahama Street
North Hills, 91343


I gained two Citalopram pills from a friend of mine, and decided to try them after researching about the drug for a while. I did not use any MAOI in the last two weeks or even month before taking the Citalopram, and I was not on any sort of medications during that time. I have never taken any anti-depressant drug prior to this experiment, or any SSRI. It is also worth mentioning that I am not supposed to take these pills, I was never diagnosed for any problem that demands anti-depressants. Here is the text I wrote documenting the experiment, as I wrote it in real time:
T+0:00
It is now 22:00 and I just took 1 pill of 20 mg citalopram (brand name – Recital). I had a nice meal about 3 hours earlier (200 grams of meat, with salad aside), and smoked my last hit of weed about 4 hours ago and I am now feeling pretty much lucid.
T+0:30
Swallowed another pill. Feeling pretty normal, with a weird background feeling of... ah... something... can't really tell if this is the pill's effect or just me playing tricks on myself.
T+1:00
Feeling a bit drowsy, buzzed, and somewhat apathetic. Nothing more than that.
T+1:30
I find it a bit hard to focus on the text in my internet explorer. Smoked some tobacco in my pipe earlier, didn't feel any difference in doing so on Citalopram or doing so lucid. I feel a little bit nauseated, but nothing serious.
T+02:00
I feel more drowsy and sedated than before. Nausea decreased and is almost unnoticeable.  My mouth is dry, but I can't say if it is out of the ordinary (a little lack of drinking, and a summer night...) or the effect of the pills.
T+2:30
Effects seem to have stabled or even a bit decreased. Nausea completely gone, a bit less sedated than before, still apathetic, still dry-mouthed. I had some water and coke, and my mouth became dry again, I think I can safely say the pills are at least partially responsible for that. Less thoughts running through my head. Focusing is still harder than usual.
T+3:00
Effects are noticeably decreasing. I am much less apathetic, and also less sedated and drowsy. I can more easily focus. My mouth is somewhat dry, but not as much as before. I am not lucid now, I can still feel the stuff running in my head, but I am surely coming down. Reminds the come-down of a marijuana high, but less aggressive and no mood-shift towards depression (actually the desired effect, Citalopram IS an anti-depressant...).
T+3:30
Most effects have dramatically decreased compared to my situation an hour ago. Still a bit drowsy, but I am not apathetic anymore. My mouth is still dry. I have much more energy now, and my thinking seems pretty normal.
T+4:00
Almost at baseline. I am feeling slightly less focused than usual, again reminding me the final phases of a marijuana comedown. The only effect that seems to last stronger than the others is my dried mouth, but that has also reduced in the last 30 minutes.
All in all, an interesting experience. Wasn't too much fun, while being apathetic was the major downside for me. Feeling drowsy and sedated was nice, the dried mouth was annoying (especially since it lasted after other effects diminished), and the nausea was negligible.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Selection Area
Country
Graph
All
Confirmed Cases
Deaths
Active Cases
Recovered
Cumulative
Daily
Search


Mexicans hit streets to demand end to violence against women
by The Associated PressECATEPEC, Mexico — The women walk barefoot on hot asphalt, clothed in shreds of organza in pastel shades of pink and yellow, the murder victim’s favouritecolours.
They perform a ceremony Saturday in honour of Briseida Carreño, one of the many women killed in a country where violence against women is prevalent and justice for victims is elusive. On average, 10 women are murdered each day in Mexico, making it one of the most dangerous places in the world to be female.
Mexico City’s mayor issued a gender alert this week for the capital, meaning that 20 of Mexico’s 31 federal entities have declared emergencies over the issue.
Activists want more action and are planning demonstrations to mark Monday’s International Day for the Elimination of Violence Women.
The Associated Press


Additional keys:
extra_vars['fqdn']
: Optional. By default the server’s hostname is used as the FQDN in Nginx. You can override this using this key.Installs the official Nginx docker container.
This role is used as a building block for all web applications. Roles, such as WordPress, are configured as reverse proxy items inside Nginx.


select st from Model st where st.name like '%123%' order by st.id 执行
select st from Model st where st.name like '%123%' order by st.id


You're new here!
Sign up with your email and personal details to get started!
Watch demo
Sign Up
Full Name
Email Address
Password
I agree to the
Terms
and
Privacy Policy
.
Sign Up
Or with Social Profile
Already have an account?
Sign In
×
Color Switcher
Reset Default


module.exports = function($scope, $http) {
Responsible for authenticating a user from a form. Two stage validation and authentication. Displays errors and uses $http to make auth request then redirects on success.
module.exports = function($scope, $http) {
two-way bindings
$scope.username = '';
$scope.password = '';
error object (name, message)
$scope.error = null;
Validates both username and password, returns boolean based on whether they passed or failed and sets $scope.error to reflect why
$scope.validate = function() {
if($scope.username.length < 3 || $scope.username.length > 12) {
$scope.error = {
name: 'This username is too long',
message: 'Username should be between 3 and 12 characters long.'
};
return false;
}
if($scope.password.length > 24) {
$scope.error = {
name: 'This password is too long',
message: 'Passwords should be less than 25 characters long.'
};
return false;
}
if(!($scope.password && $scope.username)) {
$scope.error = {
name: 'What are you doing?',
message: 'You must supply a username and password'
};
return false;
}
return true;
};
$scope.change = function() {
$scope.error = null;
};
Validates the form, and if the validation succeeds, makes a HTTP request to the auth REST api. Redirects if the request succeeds, show appropriate error if not.
$scope.login = function() {
if($scope.validate()) {
$http.post('/auth/login', {
name: $scope.username,
password: $scope.password
}).
success(function(res, status) {
if(status === 200) {
res.data.auth holds boolean of success
if(res.data.auth) {
window.location = '/admin';
} else {
$scope.error = res.data.error;
}
} else {
$scope.error = {
name: 'Server error',
message: 'There was a problem with the server.'
}
}
}).
error(function(data, status) {
$scope.error = {
name: 'Server error',
message: 'Oh dear, something went very wrong.'
};
});
};
}
};


Mary is currently a part time student at Epicodus and a project manager at Vibra-Tech Engineers. Her background is in customer service, environmental field work, environmental project mangement and consulting. She hopes to utilize her skills in GIS, project management and coding to secure a position as programmer upon graduating from Epicodus.
Mary loves all things outside and on the water. In her spare time you can find her whitewater kayaking, surfing, sailing, fishing and maintaining her small urban farm in Portland, Oregon.
Mary's first solo practice website using HTML and CSS
Mary's first project using HTML and CSS that uses branching in git


{% load i18n %} {% language 'ru' %}
Hi {{ ticket.assignee.username }},
An issue was created: {{ ticket.title }}. You're assigned to this issue.


Upfront costs are a major barrier to implementing energy efficiency projects in businesses. An important goal of energy efficiency policies and programs is to help minimize these upfront project costs so owners are encouraged to invest in energy reduction improvements. Savings and time investment are factors to consider when an energy upgrade project is offered to the customers.
Many utilities in New York and other states offer incentives, grants or rebates to buildings that install systems that reduce their overall energy consumption. These monetary facilities are funded by charging utility customers in specific rate clases, a monthly bill adjustment factor. Yet, participating in these programs is time consuming, complicated and sometimes expensive.
Our job is to help clients navigate through this complicated process with often-lenghty applications and bureaucratic paperwork and maximize rebates to offset the capital cost of each project . We identify and quantify the most suitable programs for our clients by negotiating with the utilities, filling out applications, arranging all pre and post inspections needed and getting rebate approvals. In addition, our fees are fully contingent on securing and maximizing these cash payments for our clients.
The incentives offered by utilities can be summarized as follows:
There is no standard classification of customer size or type to be eligible to participate in an energy incentive program. The requirements to join the an incentive program depend on the type and size of project, type, size and location of the building.
Commercial and Industrial properties and multi-family building complexes that are installing permanent energy improvements for new construction and existing buildings, inclusive of:


PatentTools Beta
Are these results helpful to you? Could PatentTools be improved? Either way, please take a 1-minute survey to help improve PatentTools.
Results for US Patent #{{pat_num}}.
| Title | {{pat_title}} |
| Assignee |
{{pat_assignee}} Search the web for this assignee. Search for other US patents from this assignee |
| Filing Date | {{pat_file_date}} |
|
Primary Class first listed CPC subclass |
{{pat_class}} |
|
Citations Patents cited by your search target. |
U.S. patents: {{citations_us}} Foreign patents: {{citations_for}} |
| Key Concepts |
|
| Word Cloud |
This page is best displayed on a tablet or larger device.
View this project on GitHub
PatentTools is © 2021, Joshua Hirner.


scrollWatcher is a small library for scroll-based data-driven graphics (without any nasty scrolljacking). It sticks an element at a fixed position onscreen, and then provides the distance scrolled through its (much taller) parent as a percentage.
As seen on WSJ.com in How Fed Rates Move Markets and What ECB Stimulus Has Done. Or scroll down for a live example.
View on GitHub


{% extends "base.html" %}
{% load url from future %}
{% block title %} Weekly FMC - About {% endblock %}
{% block content %}
The Weekly Fewest Moves Challenge (FMC) was made for the SpeedSolving.com web forums so that fewest moves enthusiasts can regularly compete with others and share solutions to the same scramble in order to learn from each other.
Although it is not required to submit a solution, creating an account allows you to reserve a name. Creating accounts will also create a profile for you that lists all of your submissions.
FMC stands for Fewest Moves Challenge. The challenge is to find an algorithm that will solve the cube based on the scramble provided for you.
{% endblock %}


Onepoint.js is a simple library written in JavaScript that organizes scripts with ease. It's perfect for beginners and even for professionals.


End Learning, make English exercises online
Sign up to start making English exercises online. Make exercise and get graded.
We're sorry but end training doesn't work properly without JavaScript enabled. Please enable it to continue.


Pairing & Feedback
í
I wasn’t expecting that the pairing sessions would be so much fun! In addition, they really helped me a lot in understanding particular topics. Although I think I would have been able to solve the challenges on my own, working together was often just faster than doing it alone, I guess.
In my mind, the most rewarding thing of the paring sessions was the improvement of my communication. I don’t think that I benefitted an awful lot on the technical side. However, I learned some cool new tricks from others. Sometimes people had some really helpful ideas, for instance how to solve the problem that the drop down menu for my blog posts was getting more and more bulky with a growing number of entries. This very problem-solving suggestion was particularly nice of the guy, because he thought about the problem after our pairing session and emailed me later on.
I consider myself lucky, because every single person I met during the hangouts was very nice and a pleasure to work with. Maybe that’s because of the thorough DBC member selection process beforehand? I don’t know.
Having said that, it was sometimes a bit tedious to give ASK feedback. Sure, if you desperately want to find something you could give constructive feedback on, you’ll always find something. But in many cases the pairing session went so well, that I felt a bit picky about the feedback I gave. I was a bit nervous when I first received feedback, as I wasn’t really sure of how people liked my style of teamwork. But when I read it, I was surprised how nicely some people thought of me. I didn’t necessarily expect that, because I was often very tired during our sessions, due to the timezone differences. I thought that might have led to some feedback concerning lacks in concentration.
Since the feedback is anonymous, I think it’s okay to publish a sentence from one piece of feedback that I received: „One thing you could do to further improve the communication flow is repeating back the gist of what your pair says/explains, just to let the other person know you got the main ideas down because sometimes I wasn't sure if you fully understood what I said or were a little confused.“
Again this is something constructive regarding my communication. In fact, all the constructive feedback I received was pointed at my style of communication. So I didn’t learn a lot about how better code looks like, but rather how to actually write the code in a teamwork environment.
Based on the feedback I’ve received, I will try to be more precise when speaking, and also to let others know that I understand what they are saying.
So what’s my take on using pairing and feedback to guide learning?
First, I want to cover Pairing independently:
I think pairing is a great way of learning to get along with other people well. It can also accelerate the learning of technical knowledge, as more experienced partners can quickly show you something that they might have researched in hours of work. In addition, pairing is eminently suitable for being creative. I especially recognized this as the challenges got to involve bigger projects. Playing around with an idea with a partner can even be helpful if your partner is not as experienced, because a different viewing angle is always beneficial.
Sometimes it can be a bit tedious, especially when you realize that doing a certain task would take a lot less time when doing it alone. However, even in this case there’s a good chance of improving your communication skills.
Second, my thoughts on Feedback:
There’s no question that, in order to influence one’s learning and communication, feedback is in most cases fundamental. But what I realized now is that most of the Socrates anonymous feedback is fairly inefficient. The reason for this is that most people just take the „constructive“ feedback into consideration. I assume most of us have a healthy psyche and are therefore mentally strong enough to just hear some criticism. For me it’s a bit overkilling to always write how great the session was (in fact, all my sessions really went great), because it’s not important to the skills of my partner anyway. What I would suggest is a traffic light with five lamps, were the fifth lamp means „I was completely satisfied with the session“ and the first lamp means „You should really work on your communication habits“. Moreover there should of course be a text field were you should only enter constructive feedback.
I think positive feedback should be given during the session itself!
In my mind, the most rewarding thing of the paring sessions was the improvement of my communication. I don’t think that I benefitted an awful lot on the technical side. However, I learned some cool new tricks from others. Sometimes people had some really helpful ideas, for instance how to solve the problem that the drop down menu for my blog posts was getting more and more bulky with a growing number of entries. This very problem-solving suggestion was particularly nice of the guy, because he thought about the problem after our pairing session and emailed me later on.
I consider myself lucky, because every single person I met during the hangouts was very nice and a pleasure to work with. Maybe that’s because of the thorough DBC member selection process beforehand? I don’t know.
Having said that, it was sometimes a bit tedious to give ASK feedback. Sure, if you desperately want to find something you could give constructive feedback on, you’ll always find something. But in many cases the pairing session went so well, that I felt a bit picky about the feedback I gave. I was a bit nervous when I first received feedback, as I wasn’t really sure of how people liked my style of teamwork. But when I read it, I was surprised how nicely some people thought of me. I didn’t necessarily expect that, because I was often very tired during our sessions, due to the timezone differences. I thought that might have led to some feedback concerning lacks in concentration.
Since the feedback is anonymous, I think it’s okay to publish a sentence from one piece of feedback that I received: „One thing you could do to further improve the communication flow is repeating back the gist of what your pair says/explains, just to let the other person know you got the main ideas down because sometimes I wasn't sure if you fully understood what I said or were a little confused.“
Again this is something constructive regarding my communication. In fact, all the constructive feedback I received was pointed at my style of communication. So I didn’t learn a lot about how better code looks like, but rather how to actually write the code in a teamwork environment.
Based on the feedback I’ve received, I will try to be more precise when speaking, and also to let others know that I understand what they are saying.
So what’s my take on using pairing and feedback to guide learning?
First, I want to cover Pairing independently:
I think pairing is a great way of learning to get along with other people well. It can also accelerate the learning of technical knowledge, as more experienced partners can quickly show you something that they might have researched in hours of work. In addition, pairing is eminently suitable for being creative. I especially recognized this as the challenges got to involve bigger projects. Playing around with an idea with a partner can even be helpful if your partner is not as experienced, because a different viewing angle is always beneficial.
Sometimes it can be a bit tedious, especially when you realize that doing a certain task would take a lot less time when doing it alone. However, even in this case there’s a good chance of improving your communication skills.
Second, my thoughts on Feedback:
There’s no question that, in order to influence one’s learning and communication, feedback is in most cases fundamental. But what I realized now is that most of the Socrates anonymous feedback is fairly inefficient. The reason for this is that most people just take the „constructive“ feedback into consideration. I assume most of us have a healthy psyche and are therefore mentally strong enough to just hear some criticism. For me it’s a bit overkilling to always write how great the session was (in fact, all my sessions really went great), because it’s not important to the skills of my partner anyway. What I would suggest is a traffic light with five lamps, were the fifth lamp means „I was completely satisfied with the session“ and the first lamp means „You should really work on your communication habits“. Moreover there should of course be a text field were you should only enter constructive feedback.
I think positive feedback should be given during the session itself!


Tests for differential evoked responses in at least one condition using a permutation clustering test. The FieldTrip neighbor templates will be used to determine the adjacency between sensors. This serves as a spatial prior to the clustering. Significant spatiotemporal clusters will then be visualized using custom matplotlib code.
# Authors: Denis Engemann<EMAIL_ADDRESS>#
# License: BSD (3-clause)
import numpy as np
import matplotlib.pyplot as plt
from mpl_toolkits.axes_grid1 import make_axes_locatable
from mne.viz import plot_topomap
import mne
from mne.stats import spatio_temporal_cluster_test
from mne.datasets import sample
from mne.channels import read_ch_connectivity
print(__doc__)
# Set parameters
data_path = sample.data_path()
raw_fname = data_path + '/MEG/sample/sample_audvis_filt-0-40_raw.fif'
event_fname = data_path + '/MEG/sample/sample_audvis_filt-0-40_raw-eve.fif'
event_id = {'Aud_L': 1, 'Aud_R': 2, 'Vis_L': 3, 'Vis_R': 4}
tmin = -0.2
tmax = 0.5
# Setup for reading the raw data
raw = mne.io.Raw(raw_fname, preload=True)
raw.filter(1, 30)
events = mne.read_events(event_fname)
Read epochs for the channel of interest
picks = mne.pick_types(raw.info, meg='mag', eog=True)
reject = dict(mag=4e-12, eog=150e-6)
epochs = mne.Epochs(raw, events, event_id, tmin, tmax, picks=picks,
baseline=None, reject=reject, preload=True)
epochs.drop_channels(['EOG 061'])
epochs.equalize_event_counts(event_id, copy=False)
condition_names = 'Aud_L', 'Aud_R', 'Vis_L', 'Vis_R'
X = [epochs[k].get_data() for k in condition_names] # as 3D matrix
X = [np.transpose(x, (0, 2, 1)) for x in X] # transpose for clustering
load FieldTrip neighbor definition to setup sensor connectivity
connectivity, ch_names = read_ch_connectivity('neuromag306mag')
print(type(connectivity)) # it's a sparse matrix!
plt.imshow(connectivity.toarray(), cmap='gray', origin='lower',
interpolation='nearest')
plt.xlabel('{} Magnetometers'.format(len(ch_names)))
plt.ylabel('{} Magnetometers'.format(len(ch_names)))
plt.title('Between-sensor adjacency')
Out:
<class 'scipy.sparse.csr.csr_matrix'>
Compute permutation statistic
How does it work? We use clustering to bind together features which are similar. Our features are the magnetic fields measured over our sensor array at different times. This reduces the multiple comparison problem. To compute the actual test-statistic, we first sum all F-values in all clusters. We end up with one statistic for each cluster. Then we generate a distribution from the data by shuffling our conditions between our samples and recomputing our clusters and the test statistics. We test for the significance of a given cluster by computing the probability of observing a cluster of that size. For more background read: Maris/Oostenveld (2007), “Nonparametric statistical testing of EEG- and MEG-data” Journal of Neuroscience Methods, Vol. 164, No. 1., pp. 177-190. doi:10.1016/j.jneumeth.2007.03.024
# set cluster threshold
threshold = 50.0 # very high, but the test is quite sensitive on this data
# set family-wise p-value
p_accept = 0.001
cluster_stats = spatio_temporal_cluster_test(X, n_permutations=1000,
threshold=threshold, tail=1,
n_jobs=2,
connectivity=connectivity)
T_obs, clusters, p_values, _ = cluster_stats
good_cluster_inds = np.where(p_values < p_accept)[0]
# Note. The same functions works with source estimate. The only differences
# are the origin of the data, the size, and the connectivity definition.
# It can be used for single trials or for groups of subjects.
Visualize clusters
# configure variables for visualization
times = epochs.times * 1e3
colors = 'r', 'r', 'steelblue', 'steelblue'
linestyles = '-', '--', '-', '--'
# grand average as numpy arrray
grand_ave = np.array(X).mean(axis=1)
# get sensor positions via layout
pos = mne.find_layout(epochs.info).pos
# loop over significant clusters
for i_clu, clu_idx in enumerate(good_cluster_inds):
# unpack cluster infomation, get unique indices
time_inds, space_inds = np.squeeze(clusters[clu_idx])
ch_inds = np.unique(space_inds)
time_inds = np.unique(time_inds)
# get topography for F stat
f_map = T_obs[time_inds, ...].mean(axis=0)
# get signals at significant sensors
signals = grand_ave[..., ch_inds].mean(axis=-1)
sig_times = times[time_inds]
# create spatial mask
mask = np.zeros((f_map.shape[0], 1), dtype=bool)
mask[ch_inds, :] = True
# initialize figure
fig, ax_topo = plt.subplots(1, 1, figsize=(10, 3))
title = 'Cluster #{0}'.format(i_clu + 1)
fig.suptitle(title, fontsize=14)
# plot average test statistic and mark significant sensors
image, _ = plot_topomap(f_map, pos, mask=mask, axis=ax_topo,
cmap='Reds', vmin=np.min, vmax=np.max)
# advanced matplotlib for showing image with figure and colorbar
# in one plot
divider = make_axes_locatable(ax_topo)
# add axes for colorbar
ax_colorbar = divider.append_axes('right', size='5%', pad=0.05)
plt.colorbar(image, cax=ax_colorbar)
ax_topo.set_xlabel('Averaged F-map ({:0.1f} - {:0.1f} ms)'.format(
*sig_times[[0, -1]]
))
# add new axis for time courses and plot time courses
ax_signals = divider.append_axes('right', size='300%', pad=1.2)
for signal, name, col, ls in zip(signals, condition_names, colors,
linestyles):
ax_signals.plot(times, signal, color=col, linestyle=ls, label=name)
# add information
ax_signals.axvline(0, color='k', linestyle=':', label='stimulus onset')
ax_signals.set_xlim([times[0], times[-1]])
ax_signals.set_xlabel('time [ms]')
ax_signals.set_ylabel('evoked magnetic fields [fT]')
# plot significant time range
ymin, ymax = ax_signals.get_ylim()
ax_signals.fill_betweenx((ymin, ymax), sig_times[0], sig_times[-1],
color='orange', alpha=0.3)
ax_signals.legend(loc='lower right')
ax_signals.set_ylim(ymin, ymax)
# clean up viz
mne.viz.tight_layout(fig=fig)
fig.subplots_adjust(bottom=.05)
plt.show()
"""
Exercises
----------
- What is the smallest p-value you can obtain, given the finite number of
permutations?
- use an F distribution to compute the threshold by traditional significance
levels. Hint: take a look at ```scipy.stats.distributions.f```
"""
Total running time of the script: (0 minutes 20.973 seconds)
plot_spatio_temporal_cluster_stats_sensor.py
plot_spatio_temporal_cluster_stats_sensor.ipynb


module G2048: sig
.. end
2048 game logic.
Types
type
square = int option
The type for squares.
type
row = square list
The type for board rows.
type
board = row list
The type for boards.
type
move =
The type for game moves.
L
when the player press the left arrow.
R
when the player press the up arrow.
U
when the player press the up arrow.
D
when the player press the down arrow.
Squares
val empty : square
empty
is an empty square.
val t2 : square
t2
is a square with value 2.
val t4 : square
t4
is a square with value 4.
val t8 : square
t8
is a square with value 8.
val t16 : square
t16
is a square with value 16.
val t32 : square
t32
is a square with value 32.
val t64 : square
t64
is a square with value 64.
val t128 : square
t128
is a square with value 128.
val t256 : square
t256
is a square with value 256.
val t512 : square
t512
is a square with value 512.
val t1024 : square
t1024
is a square with value 1024.
val t2048 : square
t2048
is a square with value 2048.
val square_value : square -> int option
square_value t
is t
's value (if any).
val string_of_square : square -> string
string_of_square t
is t
as a string.
Boards
val create_board : unit -> board
create_board ()
is a new board.
val board_size : board -> int * int
board_size board
is the number of columns and rows in the board.
val fold_board : ('a -> int * int -> square -> 'a) -> 'a -> board -> 'a
fold_board f acc board
folds f
over all the squares of board
with
the zero-based positions and starting with acc
. The left-bottom
corner has position (0,0)
.
Provenance
type
provenance = {
|
shift : int ; |
|
value : int ; |
}
The provenance of a tile. Not used by the online tutorial.
Solutions
module type Solution = sig
.. end
module Default: Solution
module Make:


Since 1994, the Concord Consortium has been developing deeply digital tools and learning activities that capture the power of curiosity and create revolutionary new approaches to science, math and engineering education. This new portal is being developed as a central repository for our simulations and activities, giving teachers and students access to open educational resources across our projects, past and present. The portal currently offers a limited number of research-based activities. We're actively working on adding new resources, so check back often!
Why sign up? When you register as a teacher, you can create classes, assign activities to your students, follow their progress, and view reports of their work.


Latch
public struct Latch
Latch is a simple abstraction around the iOS and OS X keychain API. Multiple Latch instances can use the same service, accessGroup, and accessibility attributes.
-
Create a new instance of Latch with a service, accessGroup, and accessibility.
:param: service The keychain access service to use for records. :param: accessGroup The keychain access group to use - ignored on the iOS simulator. :param: accessibility The accessibility class to use for records.
:returns: An instance of Latch.
Declaration
Swift
public init(service: String, accessGroup: String? = nil, accessibility: LatchAccessibility = .AfterFirstUnlockThisDeviceOnly)
-
Retreives the data for a given key, or returns nil.
Declaration
Swift
public func dataForKey(key: String) -> NSData?
-
Retreives the string value for a given key. It will return nil if the data is not a UTF8 encoded string.
Declaration
Swift
public func stringForKey(key: String) -> String?
-
Set a string value for a given key.
Declaration
Swift
public func setObject(object: String, forKey key: String) -> Bool
-
Set an NSCoding compliant object for a given key.
Declaration
Swift
public func setObject(object: NSCoding, forKey key: String) -> Bool
-
Set an NSData blob for a given key.
Declaration
Swift
public func setObject(object: NSData, forKey key: String) -> Bool
-
Remove an object from the keychain for a given key.
Declaration
Swift
public func removeObjectForKey(key: String) -> Bool
-
Remove all objects from the keychain for the current app. Only available on iOS and watchOS.
Declaration
Swift
public func resetKeychain() -> Bool


Sign in to chat with your Zombie Apocalypse camp.
{{errormessage}}
This field is required
This needs to be a valid email
Don't have an account? Sign Up


Nillllllll
The second option
The third option
Here is the first option
The second option
The third option
Select an Option
Option 1
Option 2
Select an Option
Option 1
Option 2
Select an Option
Option 1
Option 2
Medicine Name
Schedule
Total Days
Medicine Name
Schedule
Total Days


---
layout: sub-page
title: Meet The Team
permalink: /team/
intro_image:
intro_image_absolute: true
intro_image_hide_on_mobile: false
---
{% include get/team.liquid %}
{% assign promoted_teams = team | where: "promoted", true | sort: "weight" %}
{% for team in promoted_teams %}
{% if team.image %}
{% endif %}
{% endfor %}
{% assign teams = team | sort: "weight" | sort: "name" %}
{% for team in teams %}
{% if team.promoted == nil %}
{% if team.image %}
{% endif %}
{% endif %}
{% endfor %}


If you are looking for the CSUG Network Status Page and are not redirected automatically, it now lives
here
.


{% extends "layout.html" %} {% block title %} Your historical market results {% endblock title %} {% block layout-content %} {% if not guesses %}
You have not completed any markets yet.
{% else %}Below are all the markets you have participated in.
| Market | Score | Ending date |
|---|---|---|
{{ g.market.slug }}
|
+{{ g.score|floatformat:2 }}♠ | {{ g.market.end_date }} |
You have earned a total of {{ total|floatformat:2 }}♠ across {{ guesses.count }} markets.
Average spades per market: {{ avg|floatformat:2 }}♠.
{% endif %} {% endblock layout-content %}


Ginzburg-Landau equations have been used to model a wide variety of physical systems. This page simply lists a few of the possible applications, although no details are given. The interested reader is encouraged to consult Aranson and Kramer (2002) for the appropriate references.
Physical systems which undergo an instability described by the RGLE include
In more than one dimension, the system must be anisotropic (eg., electroconvection and convection in an inclined layer) for the RGLE to be applicable. On the other hand, in isotropic systems, the Laplacian operator must be replaced.
Physical systems which undergo an instability described by the CGLE include:


Semantic Grids
Button before grid
Button after grid
Left floated right aligned column
Right floated left aligned column
Center aligned row
Center aligned row
Right Aligned Grid


Australia’s Highest Court Will Hear Cardinal Pell’s Appeal
by ASSOCIATED PRESSCANBERRA, Australia (AP) – Australia’s highest court agreed Wednesday to hear an appeal from the most senior Catholic to be found guilty of sexually abusing children, giving Cardinal George Pell his last chance at getting his convictions overturned.
The decision by the High Court of Australia comes nearly a year after a unanimous jury found Pope Francis’ former finance minister guilty of molesting two 13-year-old choirboys in Melbourne’s St. Patrick’s Cathedral in the late 1990s, shortly after Pell became archbishop of Australia’s second-largest city.
The 78-year-old was sentenced to six years in prison in March and is no longer a member of Francis’ Council of Cardinals or a Vatican official. The Victoria state Court of Appeal rejected his appeal in August.
Pell is in a Melbourne prison, where a newspaper reported last month that he had been given a gardening job. He did not attend the High Court in Canberra to hear the decision Wednesday.
SNAP, an abuse victims’ support group, described the court’s decision as a blow to clergy abuse victims and to the Australian criminal justice system.
“We are disappointed that Cardinal George Pell and his lawyers will have yet another opportunity to attack and re-victimize the former choirboy,” SNAP spokesman Steven Spaner said in a statement.
Two of the seven justices — Michelle Gordon and James Edelman — heard Pell’s application for an appeal and unanimously approved it for a hearing by the full bench. The court rejects around 90% of such applications.
An appeal hearing cannot happen before the justices return from their summer break in early February.
Pell’s lawyers argued in their 12-page application for a High Court appeal that two state appeals court judges made error in dismissing his appeal in August.
The judges made a mistake by requiring Pell to prove the abuse was impossible, rather than putting the onus of proof on prosecutors, the lawyers said.
They also said the two judges erred in finding the jury’s guilty verdicts were reasonable. Pell’s lawyers argued there was reasonable doubt about whether opportunity existed for the crimes to have occurred.
Pell’s lawyers also argued that changes in law over the years since the crimes were alleged have increased the difficulty in testing sexual assault allegations.
They say Pell should be acquitted of all charges for several reasons, including inconsistencies in the accuser’s version of events.
Prosecutors argued there is no basis for the appeal and that the Victorian courts made no errors.
In their written submission to the High Court, prosecutors wrote that Pell’s legal team was asking High Court judges to apply established principles to the facts of the case, which were already carefully and thoroughly explored by the state appeals court.
Pell was largely convicted on the testimony of one victim. The second victim died of an accidental heroin overdose in 2014 when he was 31 without complaining that he had been abused.
After Pell lost his first appeal in a 2-1 decision, the surviving victim, a parent now aged 36, said, “I just hope that it’s all over now.”
Lawyer Vivienne Waller said she spoke on Wednesday to the victim, her client who cannot be identified, and he was “very respectful of the legal process.”
“I can understand that there are many survivors who might feel disappointed by the outcome and I can also understand that there are a lot of people who feel very deeply for my client and are concerned for his wellbeing and those sentiments are greatly appreciated,” Waller told Australian Broadcasting Corp.
“But he is very respectful of the process and I think that the appeals process is an important part of the criminal justice system and the appeals process is an important check and balance,” she added.
Pell’s lawyers did not immediately respond to a request for comment on Wednesday.
Clerical sexual abuse and the Catholic Church’s handling of such cases worldwide have thrown Francis’ papacy into turmoil.
In a little more than a year, the pope has acknowledged he made “grave errors” in Chile’s worst cover-up, Pell was convicted of abuse, a French cardinal was convicted of failing to report a pedophile, and U.S. Cardinal Theodore McCarrick was defrocked after a Vatican investigation determined he molested children and adults.
Pell must serve at least three years and eight months behind bars before he becomes eligible for parole. As a convicted pedophile, he is provided with extra protection from other inmates and spends 23 hours a day in solitary confinement.
By ROD McGUIRK Associated Press
Copyright © 2019 courthousenews.com


This section records information for easy reference.
The unit system used throughout is SI (Système International d'Unités). In addition to the basic units, several derived units are also used. For each unit, the table lists the symbol, a description and the SI name.
| Symbol | Description |
|---|---|
| kg | mass (kilogram) |
| m | length (metre) |
| N | force (newton) |
| Pa | pressure (pascal) |
| s | time (second) |
The table that follows summarizes the symbols used in this document along with their units. The symbols are listed in alphabetical order.
| Symbol | Description | Units |
|---|---|---|
| a | Plate length (long dimension) | m |
| AR | Aspect ratio | -- |
| ARmax | Maximum aspect ratio | -- |
| B | Risk of failure | -- |
| b | Plate width (short dimension) | m |
| capacity | Capacity or load resistance | Pa |
| dmax | Maximum value for one of the dimensions of the glass plate | m |
| dmin | Minimum value for one of the dimensions of the glass plate | m |
| E | Modulus of elasticity of glass | Pa |
| g | Glass type g ∈ {AN,FT,HS} | -- |
| GTF | Glass type factor | -- |
| h | Minimum thickness | m |
| interpY | InterpY | -- |
| interpZ | InterpZ | -- |
| is-safeLoad | Variable that is assigned true when load resistance (capacity) is greater than applied load (demand) | -- |
| is-safeLR | Variable that is assigned true when load resistance (capacity) is greater than load (demand) | -- |
| is-safePb | Variable that is assigned true when calculated probability is less than tolerable probability | -- |
| is-safeProb | Variable that is assigned true when probability of failure is less than tolerable probability of failure | -- |
| J | Stress distribution factor (Function) | -- |
| Jtol | Stress distribution factor (Function) based on Pbtol | -- |
| k | Surface flaw parameter | m12/N7 |
| LDF | Load duration factor | -- |
| Load | Applied load (demand) or pressure | Pa |
| LR | Load resistance | Pa |
| LSF | Load share factor | -- |
| m | Surface flaw parameter | m12/N7 |
| NFL | Non-factored load | Pa |
| Pb | Probability of breakage | -- |
| Pbtol | Tolerable probability of breakage | -- |
| Pf | Probability of failure | -- |
| Pftol | Tolerable probability of failure | -- |
| q | Applied load (demand) | Pa |
| q̂ | Dimensionless load | -- |
| q̂tol | Tolerable load | -- |
| SD | Stand off distance | m |
| SDmax | Maximum stand off distance permissible for input | m |
| SDmin | Minimum stand off distance permissible for input | m |
| SDx | Stand off distance (x-component) | m |
| SDy | Stand off distance (y-component) | m |
| SDz | Stand off distance (z-component) | m |
| t | Nominal thickness t ∈ {2.5,2.7,3.0,4.0,5.0,6.0,8.0,10.0,12.0,16.0,19.0,22.0} | mm |
| td | Duration of load | s |
| TNT | TNT equivalent factor | -- |
| w | Charge weight | kg |
| wmax | Maximum permissible input charge weight | kg |
| wmin | Minimum permissible input charge weight | kg |
| wTNT | Explosive mass in equivalent weight of TNT | kg |
| Abbreviation | Full Form |
|---|---|
| A | Assumption |
| AN | Annealed |
| AR | Aspect Ratio |
| DD | Data Definition |
| FT | Fully Tempered |
| GS | Goal Statement |
| GTF | Glass Type Factor |
| HS | Heat Strengthened |
| IG | Insulating Glass |
| IM | Instance Model |
| LC | Likely Change |
| LG | Laminated Glass |
| LR | Load Resistance |
| N/A | Not Applicable |
| NFL | Non-Factored Load |
| PS | Physical System Description |
| R | Requirement |
| SD | Stand Off Distance |
| SRS | Software Requirements Specification |
| TM | Theoretical Model |
| UC | Unlikely Change |
| Uncert. | Typical Uncertainty |
Software is helpful to efficiently and correctly predict the blast risk involved with the glass slab. The blast under consideration is any kind of man-made explosion. The software, herein called GlassBR, aims to predict the blast risk involved with the glass slab using an intuitive interface.
The following section provides an overview of the Software Requirements Specification (SRS) for GlassBR. This section explains the purpose of this document, the scope of the system, the characteristics of the intended reader, and the organization of the document.
The main purpose of this document is to predict whether a given glass slab is likely to resist a specified blast. The goals and theoretical models used in the GlassBR code are provided, with an emphasis on explicitly identifying assumptions and unambiguous definitions. This document is intended to be used as a reference to provide all information necessary to understand and verify the analysis. The SRS is abstract because the contents say what problem is being solved, but not how to solve it.
This document will be used as a starting point for subsequent development phases, including writing the design specification and the software verification and validation plan. The design document will show how the requirements are to be realized, including decisions on the numerical algorithms and programming environment. The verification and validation plan will show the steps that will be used to increase confidence in the software documentation and the implementation. Although the SRS fits in a series of documents that follow the so-called waterfall model, the actual development process is not constrained in any way. Even when the waterfall model is not followed, as Parnas and Clements point out parnasClements1986, the most logical way to present the documentation is still to "fake" a rational design process.
The scope of the requirements includes getting all input parameters related to the glass slab and also the parameters related to blast type. Given the appropriate inputs, GlassBR predicts whether a glass slab is safe or not.
Reviewers of this documentation should have an understanding of second year calculus, structural mechanics, glass breakage, blast risk, computer applications in civil engineering, and applicable standards for constructions using glass from astm2009, astm2012, and astm2016 in Section: References. The users of GlassBR can have a lower level of expertise, as explained in Section: User Characteristics.
The organization of this document follows the template for an SRS for scientific computing software proposed by koothoor2013 and smithLai2005, with some aspects taken from Volere template 16 rbrtsn2012. The presentation follows the standard pattern of presenting goals, theories, definitions, and assumptions. For readers that would like a more bottom up approach, they can start reading the data definitions in Section: Instance Models and trace back to find any additional information they require.
The goal statements (Section: Goal Statements) are refined to the theoretical models, and the theoretical models (Section: Theoretical Models) to the instance models (Section: Instance Models). The data definitions are used to support the definitions of the different models.
This section describes the stakeholders: the people who have an interest in the product.
The client for GlassBR is a company named Entuitive. It is developed by Dr. Manuel Campidelli. The client has the final say on acceptance of the product.
The customers are the end user of GlassBR.
This section provides general information about the system. It identifies the interfaces between the system and its environment, describes the user characteristics, and lists the system constraints.
Fig:sysCtxDiag shows the system context. A circle represents an external entity outside the software, the user in this case. A rectangle represents the software system itself (GlassBR). Arrows are used to show the data flow between the system and its environment.
The interaction between the product and the user is through a user interface. The responsibilities of the user and the system are as follows:
There are no system constraints.
This section first presents the problem description, which gives a high-level view of the problem to be solved. This is followed by the solution characteristics specification, which presents the assumptions, theories, and definitions that are used.
A system is needed to efficiently and correctly predict the blast risk involved with the glass. GlassBR is a computer program developed to interpret the inputs to give out the outputs which predict whether the glass slab can withstand the blast under the conditions.
This subsection provides a list of terms that are used in the subsequent sections and their meaning, with the purpose of reducing ambiguity and making it easier to correctly understand the requirements. All of the terms are extracted from astm2009 in Section: References.
The physical system of GlassBR, as shown in Fig:physSystImage, includes the following elements:
PS1: The glass slab.
PS2: The point of explosion. Where the bomb, or any kind of man-made explosion, is located. The stand off distance is the distance between the point of explosion and the glass.
Given the dimensions of the glass plane, glass type, the characteristics of the explosion, and the tolerable probability of breakage, the goal statements are:
The instance models that govern GlassBR are presented in Section: Instance Models. The information to understand the meaning of the instance models and their derivation is also presented, so that the instance models can be verified.
This section simplifies the original problem and helps in developing the theoretical model by filling in the missing information for the physical system. The numbers given in the square brackets refer to the Theoretical Models Section: Theoretical Models, General Definitions Section: General Definitions, Data Definitions Section: Data Definitions, Instance Models Section: Instance Models, Likely Changes Section: Likely Changes, or Unlikely Changes Section: Unlikely Changes, in which the respective assumption is used.
This section focuses on the general equations and laws that GlassBR is based on.
| Label | Safety Probability |
|---|---|
| Equation |
is-safeProb = Pf < Pftol
|
| Description | |
| Notes |
If is-safeProb, the glass is considered safe. is-safeProb and is-safeLoad (from TM: isSafeLoad) are either both True or both False. Pf is the probability of failure, Pftol is the tolerable probability of failure. |
| Source | |
| RefBy |
| Label | Safety Load |
|---|---|
| Equation |
is-safeLoad = capacity > Load
|
| Description | |
| Notes |
If is-safeLoad, the glass is considered safe. is-safeProb (from TM: isSafeProb) and is-safeLoad are either both True or both False. LR is the load resistance (also called capacity), Load (also referred as the Demand) is the 3 second duration equivalent pressure. |
| Source | |
| RefBy |
There are no general definitions.
This section collects and defines all the data needed to build the instance models.
| Label | Risk of failure |
|---|---|
| Symbol | B |
| Units | Unitless |
| Equation |
B =
k
(a b)m−1
(E h2)m LDF eJ
|
| Description | |
| Notes |
a and b are dimensions of the plate, where (a ≥ b). h is the minimum thickness, which is based on the nominal thicknesses as shown in DD: minThick. LDF is the load duration factor as defined by DD: loadDurFactor. J is the stress distribution factor (Function), as defined in DD: stressDistFac. |
| Source |
astm2009, beasonEtAl1998 (Eqs. 4-5), and campidelli (Eq. 14) |
| RefBy |
| Label | Minimum thickness |
|---|---|
| Symbol | h |
| Units | m |
| Equation |
h =
1
1000
{
2.16 , t = 2.5
2.59 , t = 2.7
2.92 , t = 3.0
3.78 , t = 4.0
4.57 , t = 5.0
5.56 , t = 6.0
7.42 , t = 8.0
9.02 , t = 10.0
11.91 , t = 12.0
15.09 , t = 16.0
18.26 , t = 19.0
21.44 , t = 22.0
|
| Description | |
| Notes |
t is a function that maps from the nominal thickness (h) to the minimum thickness. |
| Source | |
| RefBy |
| Label | Load duration factor |
|---|---|
| Symbol | LDF |
| Units | Unitless |
| Equation |
LDF = (
td
60
)
m
16
|
| Description | |
| Notes | |
| Source | |
| RefBy |
| Label |
Stress distribution factor (Function) |
|---|---|
| Symbol | J |
| Units | Unitless |
| Equation |
J = interpZ(SDF.txt,AR,q̂)
|
| Description | |
| Notes |
J is the stress distribution factor (Function), which is obtained by interpolating from data shown in Fig:dimlessloadVSaspect. q̂ is the dimensionless load defined in DD: dimlessLoad. AR is the aspect ratio defined in DD: aspect_ratio. |
| Source | |
| RefBy |
| Label | Non-factored load |
|---|---|
| Symbol | NFL |
| Units | Pa |
| Equation |
NFL =
q̂tol E h4
(a b)2
|
| Description | |
| Notes |
a and b are dimensions of the plate, where (a ≥ b). h is the minimum thickness, which is based on the nominal thicknesses as shown in DD: minThick. q̂tol is the tolerable load defined in DD: tolLoad. |
| Source | |
| RefBy |
| Label | Glass type factor |
|---|---|
| Symbol | GTF |
| Units | Unitless |
| Equation |
GTF = {
1 , g = AN
4 , g = FT
2 , g = HS
|
| Description | |
| Notes |
AN is annealed glass. FT is fully tempered glass. HS is heat strengthened glass. |
| Source | |
| RefBy |
| Label | Dimensionless load |
|---|---|
| Symbol | q̂ |
| Units | Unitless |
| Equation |
q̂ =
q (a b)2
E h4 GTF
|
| Description | |
| Notes |
q is the 3 second equivalent pressure, as given in DD: calofDemand. a and b are dimensions of the plate, where (a ≥ b). h is the minimum thickness, which is based on the nominal thicknesses as shown in DD: minThick. GTF is the glass type factor, as given by DD: gTF. q̂ is calculated with reference to A: glassLite. |
| Source |
astm2009 and campidelli (Eq. 7) |
| RefBy |
| Label | Tolerable load |
|---|---|
| Symbol | q̂tol |
| Units | Unitless |
| Equation |
q̂tol = interpY(SDF.txt,AR,Jtol)
|
| Description | |
| Notes |
q̂tol is the tolerable load which is obtained from Fig:dimlessloadVSaspect using Jtol and aspect ratio as parameters using interpolation. Calculations of Jtol and AR are defined in DD: sdfTol and DD: aspect_ratio, respectively. |
| Source | |
| RefBy |
| Label |
Stress distribution factor (Function) based on Pbtol |
|---|---|
| Symbol | Jtol |
| Units | Unitless |
| Equation |
Jtol = ln(ln(
1
1−Pbtol
)
(a b)m−1
k (E h2)m LDF
)
|
| Description | |
| Notes |
Jtol is calculated with reference to Pbtol. a and b are dimensions of the plate, where (a ≥ b). h is the minimum thickness, which is based on the nominal thicknesses as shown in DD: minThick. LDF is the load duration factor as defined by DD: loadDurFactor. Pbtol is the tolerable probability entered by the user. |
| Source | |
| RefBy |
| Label | Stand off distance |
|---|---|
| Symbol | SD |
| Units | m |
| Equation |
SD = √(SDx2+SDy2+SDz2)
|
| Description | |
| Source | |
| RefBy |
| Label | Aspect ratio |
|---|---|
| Symbol | AR |
| Units | Unitless |
| Equation |
AR =
a
b
|
| Description | |
| Notes |
a and b are dimensions of the plate, where (a ≥ b). |
| Source | |
| RefBy |
| Label |
Explosive mass in equivalent weight of TNT |
|---|---|
| Symbol | wTNT |
| Units | kg |
| Equation |
wTNT = w TNT
|
| Description | |
| Source | |
| RefBy |
| Label | Probability of breakage |
|---|---|
| Symbol | Pb |
| Units | Unitless |
| Equation |
Pb = 1−e−B
|
| Description | |
| Notes |
B is the risk of failure, as defined in DD: riskFun. |
| Source | |
| RefBy |
| Label | Load resistance |
|---|---|
| Symbol | LR |
| Units | Pa |
| Equation |
LR = NFL GTF LSF
|
| Description | |
| Notes |
LR is the load resistance, which is also called capacity. NFL is the non-factored load, as defined in DD: nFL. GTF is the glass type factor, as defined in DD: gTF. |
| Source | |
| RefBy |
| Label | Applied load (demand) |
|---|---|
| Symbol | q |
| Units | Pa |
| Equation |
q = interpY(TSD.txt,SD,wTNT)
|
| Description | |
| Notes |
q, or demand, is the 3 second duration equivalent pressure obtained from Fig:demandVSsod by interpolation using stand off distance (SD) and wTNT as parameters. wTNT is defined in DD: eqTNTW. SD is the stand off distance as defined in DD: standOffDist. |
| Source | |
| RefBy |
This section transforms the problem defined in Section: Problem Description into one which is expressed in mathematical terms. It uses concrete symbols defined in Section: Data Definitions to replace the abstract symbols in the models identified in Section: Theoretical Models and Section: General Definitions.
The goal GS: Predict-Glass-Withstands-Explosion is met by IM: isSafePb, IM: isSafeLR.
| Label | Safety Req-Pb |
|---|---|
| Input |
Pb, Pbtol |
| Output | is-safePb |
| Input Constraints |
Pb > 0
Pbtol > 0
|
| Output Constraints | |
| Equation |
is-safePb = Pb < Pbtol
|
| Description | |
| Notes |
If is-safePb, the glass is considered safe. is-safePb and is-safePb (from IM: isSafeLR) are either both True or both False. Pb is the probability of breakage, as calculated in DD: probOfBreak. Pbtol is the tolerable probability of breakage entered by the user. |
| Source | |
| RefBy |
| Label | Safety Req-LR |
|---|---|
| Input |
is-safeLR, LR, q |
| Output | is-safeLR |
| Input Constraints |
LR > 0
q > 0
|
| Output Constraints | |
| Equation |
is-safeLR = LR > q
|
| Description | |
| Notes |
If is-safeLR, the glass is considered safe. is-safePb (from IM: isSafePb) and is-safeLR are either both True or both False. LR is the load resistance (also called capacity), as defined in DD: calofCapacity. q (also referred as the Demand) is the 3 second duration equivalent pressure, as defined in DD: calofDemand. |
| Source | |
| RefBy |
Table:InDataConstraints and Table:OutDataConstraints show the data constraints on the input and output variables, respectively. The column for physical constraints gives the physical limitations on the range of values that can be taken by the variable. The uncertainty column provides an estimate of the confidence with which the physical quantities can be measured. This information would be part of the input if one were performing an uncertainty quantification exercise. The constraints are conservative, to give the user of the model the flexibility to experiment with unusual situations. The column of typical values is intended to provide a feel for a common scenario. Section: Values of Auxiliary Constants gives the values of the specification parameters used in Table:InDataConstraints.
| Var | Physical Constraints | Software Constraints | Typical Value | Uncert. |
|---|---|---|---|---|
| a | a > 0 ∧ a ≥ b | dmin ≤ a ≤ dmax | 1.5 m | 10% |
| AR | AR ≥ 1 | AR ≤ ARmax | 1.5 | 10% |
| b | 0 < b ≤ a | dmin ≤ b ≤ dmax | 1.2 m | 10% |
| Pbtol | 0 < Pbtol < 1 | -- | 8.0⋅10-3 | 0.1% |
| SD | SD > 0 | SDmin ≤ SD ≤ SDmax | 45.0 m | 10% |
| TNT | TNT > 0 | -- | 1.0 | 10% |
| w | w > 0 | wmin ≤ w ≤ wmax | 42.0 kg | 10% |
| Var | Physical Constraints |
|---|---|
| Pb | 0 < Pb < 1 |
FIXME.
This section provides the functional requirements, the tasks and behaviours that the software is expected to complete, and the non-functional requirements, the qualities that the software is expected to exhibit.
This section provides the functional requirements, the tasks and behaviours that the software is expected to complete.
| Symbol | Description | Units |
|---|---|---|
| a | Plate length (long dimension) | m |
| b | Plate width (short dimension) | m |
| g | Glass type g ∈ {AN,FT,HS} | -- |
| Pbtol | Tolerable probability of breakage | -- |
| SDx | Stand off distance (x-component) | m |
| SDy | Stand off distance (y-component) | m |
| SDz | Stand off distance (z-component) | m |
| t | Nominal thickness t ∈ {2.5,2.7,3.0,4.0,5.0,6.0,8.0,10.0,12.0,16.0,19.0,22.0} | mm |
| TNT | TNT equivalent factor | -- |
| w | Charge weight | kg |
| Symbol | Description | Source | Units |
|---|---|---|---|
| AR | Aspect ratio | DD: aspect_ratio | -- |
| E | Modulus of elasticity of glass | A: standardValues | Pa |
| GTF | Glass type factor | DD: gTF | -- |
| h | Minimum thickness | DD: minThick | m |
| k | Surface flaw parameter | A: standardValues | m12/N7 |
| LDF | Load duration factor | DD: loadDurFactor | -- |
| LSF | Load share factor | A: glassLite | -- |
| m | Surface flaw parameter | A: standardValues | m12/N7 |
| SD | Stand off distance | DD: standOffDist | m |
| td | Duration of load | A: standardValues | s |
| Symbol | Description | Source | Units |
|---|---|---|---|
| AR | Aspect ratio | DD: aspect_ratio | -- |
| B | Risk of failure | DD: riskFun | -- |
| GTF | Glass type factor | DD: gTF | -- |
| h | Minimum thickness | DD: minThick | m |
| is-safeLR | Safety Req-LR | IM: isSafeLR | -- |
| is-safePb | Safety Req-Pb | IM: isSafePb | -- |
| J | Stress distribution factor (Function) | DD: stressDistFac | -- |
| Jtol | Stress distribution factor (Function) based on Pbtol | DD: sdfTol | -- |
| NFL | Non-factored load | DD: nFL | Pa |
| q̂ | Dimensionless load | DD: dimlessLoad | -- |
| q̂tol | Tolerable load | DD: tolLoad | -- |
This section provides the non-functional requirements, the qualities that the software is expected to exhibit.
The purpose of the traceability matrices is to provide easy references on what has to be additionally modified if a certain component is changed. Every time a component is changed, the items in the row of that component that are marked with an "X" should be modified as well. Table:Tracey shows the dependencies of theoretical models, instance models, and data definitions with each other. Table:TraceyItemSecs shows the dependencies of requirements on theoretical models, instance models, data definitions, and data constraints. Table:TraceyReqsItems shows the dependencies of theoretical models, instance models, data definitions, likely changes and requirements on the assumptions.
| T1 (TM: isSafeProb) | T2 (TM: isSafeLoad) | IM1 (IM: isSafePb) | IM2 (IM: isSafeLR) | IM3 (DD: riskFun) | DD1 (DD: minThick) | DD2 (DD: loadDurFactor) | DD3 (DD: stressDistFac) | DD4 (DD: nFL) | DD5 (DD: gTF) | DD6 (DD: dimlessLoad) | DD7 (DD: tolLoad) | DD8 (DD: sdfTol) | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| T1 (TM: isSafeProb) | X | X | |||||||||||
| T2 (TM: isSafeLoad) | X | X | X | ||||||||||
| IM1 (IM: isSafePb) | X | X | X | ||||||||||
| IM2 (IM: isSafeLR) | X | X | |||||||||||
| IM3 (DD: riskFun) | |||||||||||||
| DD1 (DD: minThick) | |||||||||||||
| DD2 (DD: loadDurFactor) | |||||||||||||
| DD3 (DD: stressDistFac) | X | ||||||||||||
| DD4 (DD: nFL) | X | X | |||||||||||
| DD5 (DD: gTF) | |||||||||||||
| DD6 (DD: dimlessLoad) | X | X | X | ||||||||||
| DD7 (DD: tolLoad) | X | ||||||||||||
| DD8 (DD: sdfTol) | X |
| T1 (TM: isSafeProb) | T2 (TM: isSafeLoad) | IM1 (IM: isSafePb) | IM2 (IM: isSafeLR) | IM3 (DD: riskFun) | DD1 (DD: minThick) | DD2 (DD: loadDurFactor) | DD3 (DD: stressDistFac) | DD4 (DD: nFL) | DD5 (DD: gTF) | DD6 (DD: dimlessLoad) | DD7 (DD: tolLoad) | DD8 (DD: sdfTol) | Data Constraints (Section: Data Constraints) | R1 (FR: Input-Glass-Props) | R2 (FR: System-Set-Values-Following-Assumptions) | R3 (FR: Check-Input-with-Data_Constraints) | R4 (FR: Output-Values-and-Known-Quantities) | R5 (FR: Check-Glass-Safety) | R6 (FR: Output-Quantities) | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| R1 (in FR: Input-Glass-Props) | ||||||||||||||||||||
| R2 (in FR: System-Set-Values-Following-Assumptions) | ||||||||||||||||||||
| R3 (in FR: Check-Input-with-Data_Constraints) | X | |||||||||||||||||||
| R4 (in FR: Output-Values-and-Known-Quantities) | X | X | ||||||||||||||||||
| R5 (in FR: Check-Glass-Safety) | X | X | ||||||||||||||||||
| R6 (in FR: Output-Quantities) | X | X | X | X | X | X | X | X | X | X |
| A1 (A: glassType) | A2 (A: glassCondition) | A3 (A: explainScenario) | A4 (A: standardValues) | A5 (A: glassLite) | A6 (A: boundaryConditions) | A7 (A: responseType) | A8 (A: ldfConstant) | |
|---|---|---|---|---|---|---|---|---|
| T1 (TM: isSafeProb) | ||||||||
| T2 (TM: isSafeLoad) | ||||||||
| IM1 (IM: isSafePb) | X | X | X | |||||
| IM2 (IM: isSafeLR) | X | X | X | |||||
| IM3 (DD: riskFun) | ||||||||
| DD1 (DD: minThick) | ||||||||
| DD2 (DD: loadDurFactor) | ||||||||
| DD3 (DD: stressDistFac) | ||||||||
| DD4 (DD: nFL) | X | |||||||
| DD5 (DD: gTF) | ||||||||
| DD6 (DD: dimlessLoad) | X | |||||||
| DD7 (DD: tolLoad) | ||||||||
| DD8 (DD: sdfTol) | X | |||||||
| LC1 (LC: Calculate-Internal-Blask-Risk) | X | |||||||
| LC2 (LC: Variable-Values-of-m,k,E) | X | X | ||||||
| LC3 (LC: Accomodate-More-than-Single-Lite) | X | |||||||
| LC4 (LC: Accomodate-More-Boundary-Conditions) | X | |||||||
| LC5 (LC: Consider-More-than-Flexure-Glass) | X | |||||||
| R1 (FR: Input-Glass-Props) | ||||||||
| R2 (FR: System-Set-Values-Following-Assumptions) | X | X | X | |||||
| R3 (FR: Check-Input-with-Data_Constraints) | ||||||||
| R4 (FR: Output-Values-and-Known-Quantities) | ||||||||
| R5 (FR: Check-Glass-Safety) | ||||||||
| R6 (FR: Output-Quantities) |
The purpose of the traceability graphs is also to provide easy references on what has to be additionally modified if a certain component is changed. The arrows in the graphs represent dependencies. The component at the tail of an arrow is depended on by the component at the head of that arrow. Therefore, if a component is changed, the components that it points to should also be changed. Fig:TraceyItemSecs shows the dependencies of theoretical models, instance models, and data definitions on each other. Fig:TraceyReqsItems shows the dependencies of requirements on theoretical models, instance models, data definitions, and data constraints. Fig:TraceyAssumpsOthers shows the dependencies of theoretical models, instance models, data definitions, requirements, and likely changes on assumptions.
This section contains the standard values that are used for calculations in GlassBR.
| Symbol | Description | Value | Unit |
|---|---|---|---|
| ARmax | maximum aspect ratio | 5.0 | -- |
| dmax | maximum value for one of the dimensions of the glass plate | 5.0 | m |
| dmin | minimum value for one of the dimensions of the glass plate | 100.0⋅10-3 | m |
| E | modulus of elasticity of glass | 71.7⋅109 | Pa |
| k | surface flaw parameter | 28.6⋅10-54 | m12/N7 |
| LSF | load share factor | 1 | -- |
| m | surface flaw parameter | 7.0 | m12/N7 |
| SDmax | maximum stand off distance permissible for input | 130.0 | m |
| SDmin | minimum stand off distance permissible for input | 6.0 | m |
| td | duration of load | 3.0 | s |
| wmax | maximum permissible input charge weight | 910.0 | kg |
| wmin | minimum permissible input charge weight | 4.5 | kg |
This appendix holds the graphs (Fig:demandVSsod and Fig:dimlessloadVSaspect) used for interpolating values needed in the models.


| Department | {{ assignment?.department }} | Course | {{ assignment?.course_code }} | Staff Number | {{ assignment?.staff_no }} | Users | {{ assignment?.assignments.users.length }} | Posted on | {{ assignment?.updatedAt | date }} | Deadline | {{ assignment?.submission_date | date }} | Action | View |
|---|


--- subject: Let your voice be heard. Leave a review! ---
Hi \{{lead.First Name}},
Did you know that you’re missing out on free, better-for-you products each and every day? While we’re so happy you are a part of the Moms Meet Community, you haven’t yet unlocked all the benefits (and fun!) of being a Mom Ambassador.
Our Mom Ambassadors are invited to try and review products with their friends and family. Don’t have a large group of moms? You can even try some products by yourself. Becoming a Mom Ambassador is completely free and all we ask in return is your honest feedback.


Grids Bootstraps
COL Large 4
COL Large 4
COL Large 4
COL Med 6
COL Med 6
COL XS 6
COL XS 6
NEST ONE
NEST TWO
TOP LEVEL


2 references to BooleanToObject
System.Management.Automation (2)
engine\interpreter\TypeOperations.cs (2)
132
frame.Push(ScriptingRuntimeHelpers.
BooleanToObject
(frame.Pop() is T));
188
frame.Push(ScriptingRuntimeHelpers.
BooleanToObject
(obj != null && (object)obj.GetType() == type));


I recently had trouble running my javascript code because of a syntax error in a large javascript paragraph. Firstly studied my code as closely as possible to seek out the faults. Secondly I compared my paragraph to the given examples to find where I went wrong. Comparing to the examples given allowed me to find that I had added a comma instead of a semicolon. It felt good to do it myself and not ask for help in that instance (it is important to know when to ask for help). To be very specific when coding, otherwise the computer will spit it back at me!
I always feel it’s very important for me to at the very least try figure out a bug by myself. The feeling of identifying and fixing a bug is great and motivates me to code more. Other techniques I use are obviously examples given, GOOGLE, then if I’m really struggling peers and the Slack community. I feel confident using the resources to help me learn and improve my code.


dt2dv - convert a DTL text representation of a TeX DVI file to a binary DVI file
dt2dv
[input-DTL-file] [output-DVI-file]
In the absence of the -si and -so options, both file arguments are required in the order input-DTL-file output-DVI-file . But also see the OPTIONS section below. No default file extensions are supplied.
dt2dv converts a text representation of a *(Te DVI file, usually produced by the companion dv2dt (1)utility, back to a binary DVI file. DTL
files can be edited, with care, and then restored to DVI form for processing by any *(Te DVI driver program. In DTL files, font directory names and font names are preceded by a length field, which must be updated if the names are modified.
dvitype (1)can also display a textual representation of DVI files, but in some implementations at least, it cannot be used in batch mode, and its output is not well-suited for conversion back to a DVI file.
The format of *(Te DVI files is fully described in Donald E. Knuth, \*(Te\&: The Program , Addison-Wesley (1986), ISBN 0-201-13437-3, as well as in the dvitype (1)literate program source code. Brief descriptions of the DTL and DVI formats are given in dv2dt (1).
-debug Turn on detailed debugging output.
-group Expect each DTL command to be in parentheses.
-si Read all DTL commands from standard input.
-so Write all DVI commands to standard output.
dv2dt (1), dvitype (1), tex (1).
*.dvi binary *(Te DVI file.
*.dtl text representation of a *(Te DVI file in DVI Text Language format.
dt2dv and , dv2dt (1)were written by
Geoffrey Tobin Department of Electronic Engineering La Trobe University Bundoora, Victoria 3083 Australia Tel: +61 3 479 3736 FAX: +61 3 479 3025 Email<EMAIL_ADDRESS>These manual pages were written primarily by
Nelson H. F. Beebe, Ph.D. Center for Scientific Computing Department of Mathematics University of Utah Salt Lake City, UT 84112 Tel: +1<PHONE_NUMBER> FAX: +1<PHONE_NUMBER> Email: <beebe@math.utah.edu>


Logout
Instructions
- Encircle occluded fruits entirely, use your best guess!
- Click and drag to select region.
- Labels can be moved by clicking and dragging.
- Double click to delete an area.


{% for project in include.data %}
{{ project.description }} {{ project.impact }}
{% include /functions/getprojectpubs.html project=project %}


Class Page
Describes a Page in Oqtane
Inheritance
System.Object
Page
Assembly: Oqtane.Shared.dll
Syntax
public class Page : IAuditable, IDeletable
Properties
|
Improve this Doc
View Source
CreatedBy
Username of the creator of this Object.
Declaration
public string CreatedBy { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
CreatedOn
Created Timestamp for this Object.
Declaration
public DateTime CreatedOn { get; set; }
Property Value
| Type |
Description |
| System.DateTime |
|
|
Improve this Doc
View Source
DefaultContainerType
Reference to a Container which will be used for modules on this page.
Declaration
public string DefaultContainerType { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
DeletedBy
Declaration
public string DeletedBy { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
DeletedOn
Declaration
public DateTime? DeletedOn { get; set; }
Property Value
| Type |
Description |
| System.Nullable<System.DateTime> |
|
|
Improve this Doc
View Source
EditMode
Declaration
[Obsolete("This property is deprecated", false)]
[NotMapped]
public bool EditMode { get; set; }
Property Value
| Type |
Description |
| System.Boolean |
|
|
Improve this Doc
View Source
HasChildren
Determines if there are sub-pages. True if this page has sub-pages.
Declaration
[NotMapped]
public bool HasChildren { get; set; }
Property Value
| Type |
Description |
| System.Boolean |
|
|
Improve this Doc
View Source
Icon
Icon file for this page.
TODO: unclear what this is for, and what icon library is used. Probably FontAwesome?
Declaration
public string Icon { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
IsClickable
Declaration
public bool IsClickable { get; set; }
Property Value
| Type |
Description |
| System.Boolean |
|
|
Improve this Doc
View Source
IsDeleted
Declaration
public bool IsDeleted { get; set; }
Property Value
| Type |
Description |
| System.Boolean |
|
|
Improve this Doc
View Source
IsNavigation
Declaration
public bool IsNavigation { get; set; }
Property Value
| Type |
Description |
| System.Boolean |
|
|
Improve this Doc
View Source
IsPersonalizable
Declaration
public bool IsPersonalizable { get; set; }
Property Value
| Type |
Description |
| System.Boolean |
|
|
Improve this Doc
View Source
LayoutType
Declaration
[Obsolete("This property is deprecated", false)]
[NotMapped]
public string LayoutType { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
Level
Declaration
[NotMapped]
public int Level { get; set; }
Property Value
| Type |
Description |
| System.Int32 |
|
|
Improve this Doc
View Source
ModifiedBy
Username of the last user who modified this Object.
Declaration
public string ModifiedBy { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
ModifiedOn
Modified Timestamp for this Object.
Declaration
public DateTime ModifiedOn { get; set; }
Property Value
| Type |
Description |
| System.DateTime |
|
|
Improve this Doc
View Source
Name
Page Name.
TODO: todoc where this is used
Declaration
public string Name { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
Order
Sort order in the list of other sibling pages
Declaration
public int Order { get; set; }
Property Value
| Type |
Description |
| System.Int32 |
|
|
Improve this Doc
View Source
PageId
Declaration
public int PageId { get; set; }
Property Value
| Type |
Description |
| System.Int32 |
|
|
Improve this Doc
View Source
Panes
List of Pane-names which this Page has.
Declaration
[NotMapped]
public List<string> Panes { get; set; }
Property Value
| Type |
Description |
| System.Collections.Generic.List<System.String> |
|
|
Improve this Doc
View Source
ParentId
Reference to the parent Page if it has one.
Declaration
public int? ParentId { get; set; }
Property Value
| Type |
Description |
| System.Nullable<System.Int32> |
|
|
Improve this Doc
View Source
Path
Path of the page.
TODO: todoc relative to what? site root, parent-page, domain?
Declaration
public string Path { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
Permissions
Declaration
[NotMapped]
public string Permissions { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
Resources
List of Resource (CSS, JS) which this page needs to render properly.
Declaration
[NotMapped]
public List<Resource> Resources { get; set; }
Property Value
| Type |
Description |
| System.Collections.Generic.List<Resource> |
|
|
Improve this Doc
View Source
Settings
Declaration
[NotMapped]
public Dictionary<string, string> Settings { get; set; }
Property Value
| Type |
Description |
| System.Collections.Generic.Dictionary<System.String, System.String> |
|
|
Improve this Doc
View Source
SiteId
Declaration
public int SiteId { get; set; }
Property Value
| Type |
Description |
| System.Int32 |
|
|
Improve this Doc
View Source
ThemeType
Reference to a Theme which will be used to show this page.
Declaration
public string ThemeType { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
Title
Page Title which is shown in the browser tab.
Declaration
public string Title { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
Url
Full URL to this page.
TODO: verify that this is the case - does it contain domain etc. or just from domain or alias root?
Declaration
public string Url { get; set; }
Property Value
| Type |
Description |
| System.String |
|
|
Improve this Doc
View Source
UserId
Declaration
public int? UserId { get; set; }
Property Value
| Type |
Description |
| System.Nullable<System.Int32> |
|
Implements


pnmtosir(1) pnmtosir(1) NAME pnmtosir - convert a portable anymap into a Solitaire format SYNOPSIS pnmtosir [pnmfile] DESCRIPTION Reads a portable anymap as input. Produces a Solitaire Image Recorder format. pnmtosir produces an MGI TYPE 17 file for pbm and pgm files. For ppm, it writes a MGI TYPE 11 file. SEE ALSO sirtopnm(1), pnm(5) BUGS AUTHOR Copyright (C) 1991 by Marvin Landis. 20 March 1991 pnmtosir(1)


ABOUT
Learn about the project!
Climate.DF is a project which will focus on the theme of climate change and more specifically, how climate has changed over the years, and how it will change in the future. We are focusing on different accurate and comprehendable visualizations and portraying how factors like temperature, carbon dioxide, and different natural gases disrupt climate patterns. Through regression modeling and time series analysis, we aim to forecast future patterns of climate and provide methods to control climate change using statistical methods.
We aim to showcase prehistoric climate changes in an interactive Shiny Application where the user can select a start and end data and view different temperature changes over the years. We are interested in showcasing different statistics to portray how climate has changed over different geographies. With respect to time-series analysis, we aim to do a global forecast of temperature to give our viewers an idea of the different global temperature changes and use ARIMA models to forecast future temperature changes. Using effective visualizations of maps, we aim to show how different anomalies like temperatures and precipitation change with different continents or countries.
Data Sources
Berkeley Earth Temperature Data
World Bank Climate Data
Rise in Temperatures Data
World Bank API


Category Theory OctoberFest is an informal meeting, covering all areas of category theory and its applications. It is traditionally held in October.
Octoberfest 2019 will be hosted at Johns Hopkins University, Baltimore, Maryland, over the last weekend of October, the 26th/27th. The meeting will start on the morning of Saturday the 26th and end the following afternoon. As is tradition, we will have a plenary talk at 17h00 on Friday the 25th, joint with the Johns Hopkins Category Theory seminar. Mike Shulman will give the plenary talk on the theme of internal languages: “The science of notation: an invitation to internal languages”.
Organisers: tslil clingman, Daniel Fuentes-Keuthan, and David Jaz Myers.Contact the organisers at<EMAIL_ADDRESS>All activity will occur on the Johns Hopkins Homewood campus, please refer to the campus map for specifics, and the Johns Hopkins directions website for further information.
Fri.: 17h-18h45, 205 Krieger Hall Sat.: 09h-17h00, 205 Krieger Hall Sun.: 09h-12h30, 205 Krieger Hall
The slides and videos below, except where otherwise noted by the author, are copyright their respective authors and made available under the terms of the following license: Creative Commons Attribution-ShareAlike 4.0 International License.
| 17h00-18h45 | Mike Shulman | The science of notation: an invitation to internal languages (video) |
For those arriving early, we will be congregating in 413 Krieger Hall before the talk.
| 08h30 | Coffee and registration in Krieger 413 | |
| 09h00 | Raymond Puzio | Posets, Lifting properties, and Completions (video) |
| 09h30 | Gershom Bazerman | Dependency Structures, Locales, and the Idempotent Distributive Lattice Completion (video) (slides) |
| 10h00 | Simon Cho | A quantalic perspective on persistent and magnitude homology (video) (slides) |
| 10h30 | Coffee break in Krieger 413 | |
| 11h00 | Todd Trimble | An Elementary Approach to Elementary Topos Theory (video unavailable) (slides) |
| 11h30 | Steve Awodey | An algebraic proof of the Frobenius condition for cubical sets (video unavailable)(slides) |
| 12h00 | Lunch break | |
| 14h00 | Mathieu Anel | A small object argument for unique factorization systems (video) |
| 14h30 | Andrew Swan | Lifting Problems in a Grothendieck Fibration (video) (slides) |
| 15h00 | Nick Gurski | Pseudofunctors and simplicial categories (video) (slides) |
| 15h30 | Coffee break in Krieger 413 | |
| 16h00 | Ellen Lehet | The Explanatory Value of Category Theory (video) (slides) |
| 16h30 | Noah Chrein | Knowledge Representation and Hierarchical Ontology (video) (slides) |
| 08h30 | Coffee and registration in Krieger 413 | |
| 09h00 | Brandon Shapiro | Algebra on Cell Diagrams & Shape Independent Category Theory (video) (slides) |
| 09h30 | Amit Sharma | The homotopy theory of coherently commutative monodical quasi-categories (video) |
| 10h00 | Michael Horst | A Categorification of Group Cohomology (video) (slides) |
| 10h30 | Coffee break in Krieger 413 | |
| 11h00 | Steve Huntsman | Functorial cluster embedding (video) (slides) |
| 11h30 | Dan Shiebler | Incremental Monoidal Categories (video) (slides) |
We will be competing with “Parent's Weekend” at JHU for hotel space, so attendees are urged to arrange accommodation as soon as proves convenient. Below we have some suggestions for hotels near to the Homewood Campus, or easily accessible via public or hotel transport.
Although there are several airports in surrounding areas, we urge those flying to use Baltimore Washington International as it is the closest and is a short train-journey away from the city. In particular the MARC train runs between the airport and Penn. station, and the Purple Circulator stops at the station.
Parking in official lots is possible, and information about this is available on the JHU visitor parking page. There is a flat 9$/day fee for weekend parking in the South Garage and San Martin Garage
Although registration is optional, we do encourage those wishing to attend to send an email to<EMAIL_ADDRESS>with subject “Registration” so that we can obtain an approximate headcount. There is no deadline for registration.
Talk submission is now closed.


Bayesian analysis of CGH microarrays fitting Hidden Markov Chain models. The selection of the number of states is made via their posterior probability computed by Reversible Jump Markov Chain Monte Carlo Methods. Also returns probabilistic common regions for gains/losses.
| Version: | 2.0.4 |
| Depends: | R (≥ 2.13) |
| Published: | 2015-07-10 |
| Author: | Oscar Rueda and Ramon Diaz-Uriarte. zlib from Jean-loup Gailly and Mark Adler; see README. Function "getHostname.System" from package R.utils by Henrik Bengtsson. |
| Maintainer: | Oscar Rueda <rueda.om at gmail.com> |
| License: | GPL-3 |
| URL: | http://www.r-project.org |
| NeedsCompilation: | yes |
| SystemRequirements: | zlib headers and library. |
| In views: | Bayesian |
| CRAN checks: | RJaCGH results |
| Reference manual: | RJaCGH.pdf |
| Package source: | RJaCGH_2.0.4.tar.gz |
| Windows binaries: | r-devel: RJaCGH_2.0.4.zip, r-release: RJaCGH_2.0.4.zip, r-oldrel: RJaCGH_2.0.4.zip |
| OS X binaries: | r-release: RJaCGH_2.0.4.tgz, r-oldrel: RJaCGH_2.0.4.tgz |
| Old sources: | RJaCGH archive |
Please use the canonical form https://CRAN.R-project.org/package=RJaCGH to link to this page.


LFE Style Guide
1 Introduction
1.1 Motivation and Purpose
LFE has, since its inception in 2008, become increasinly popular in the Erlang and Lisp communities. Contributions to the source code, examples, third-party libraries, and LFE-based applications have steadily risen and are currently undergoing a sharp increase.
As such, our community now has the need for resources we can provide for new-comers -- both to assist in their LFE literacy as well as make contributions easier to write and then get approved for merge.
In summary, this guide recommends formatting and stylistic choices designed to make your code easier for other people to understand.
1.2 License
The material in this document is licensed under Creative Commons 3.0 BY, the same license as the majority of the source material in the The Common Lisp Style Guide.
1.3 Sources
The LFE Style Guide has several sources. The majority of the text is taken directly from the The Common Lisp Style Guide.
Additional sources include the following:
- Tutorial on Good Lisp Programming Style
- The Common Lisp HyperSpec.
- Erlang Documentation
- LFE Programming Rules and Conventions
- Conversations, emails, and IRC chats with Robert Virding, creator of LFE (and co-creator of Erlang).
1.4 Differences from The Common Lisp Style Guide
Large portions of the Common Lisp Style Guide are more formal or too specific to Common Lisp itself to be appropriate for the LFE Style Guide. As such, that content has not been adapted to LFE.
The recent versions of the Common Lisp Style Guide are targeted at Lisp usage inside Google. The LFE Style Guide changes the portions of the guide focused on groups inside Google to instead refer to the larger open source community, the Erlang community, or the LFE community and associated projects.
1.5 Credits
Contributors to the Common Lisp Style Guide:
- Adam Worrall
- Dan Pierson
- Matt Marjanovic
- Matt Reklaitis
- Paul Weiss
- Scott McKay
- Sundar Narasimhan, and several others
Editors of the Common Lisp Style Guide:
- Dan Weinreb
- François-René Rideau
- Jeremy Brown
- Robert Brown
Google is the current sponsor of the Common Lisp Style guide.
Authors of Tutorial on Good Lisp Programming Style:
- Peter Norvig
- Kent Pitman
Learn You Some Erlang
- Fred Hebert
Creator of LFE:
- Robert Virding
Editors of the LFE Style Guide:
- Duncan McGreggor
1.6 See Also
Also be sure to read the related guide, LFE Programming Rules and Conventions.


{% extends "frog/email.html" %} {% block content %} {% if error %}
The video failed to process:
{{ error }}
The site administrators have also been sent an error report and we have top men on it.
{% else %}Your video has finished processing!
video.height %}width="200"{% else %}height="200"{% endif %} /> {% endif %} {% endblock %} {% block footer %} View Video {% endblock %}


| streamhandle = handle assigned when the stream was opened. |
| Once you've completed the use of your TCP/IP stream, close the connection you opened with OpenTCPStream with this command. |
|
; OpenTCPStream/CloseTCPStream Example
Print "Connecting..." tcp=OpenTCPStream( "www.blitzbasement.com",80 ) If Not tcp Print "Failed.":WaitKey:End Print "Connected! Sending request..." WriteLine tcp,"GET http://www.blitzbasement.com HTTP/1.0" WriteLine tcp,Chr$(10) If Eof(tcp) Print "Failed.":WaitKey:End Print "Request sent! Waiting for reply..." While Not Eof(tcp) Print ReadLine$( tcp ) Wend If Eof(tcp)=1 Then Print "Success!" Else Print "Error!" CloseTCPStream tcp WaitKey End |


ABSTRACT
Prokudin G.S, Chupaylenko O.A., Hilevska K.Y., Maidanik K.O. Peculiarities of formation and prospects of development of transport-logistic clusters. Visnyk National Transport University. Series «Technical sciences». Scientific and Technical Collection. - Kyiv: National Transport University, 2020. - Issue 1 (46).
In this article the peculiarities of formation and development of transport-logistic clusters in the advanced countries of the world are considered, as well as prospects for their creation in Ukraine.
Object of research - process of formation and development of transport-logistic clusters.
The purpose of the work is to study the peculiarities of the formation and prospects of the development of transport clusters in order to improve the efficiency of the transport system of the country.
The research method is a comparison and statistical analysis of the structures and characteristics of transport and logistics clusters in the advanced countries of the world.
Modern market conditions require Ukraine to form a competitive logistics system with the further entry into the international world macrosystem, which will allow Ukraine to form a competitive transport system and effective infrastructure, strengthen international relations with other trade regions and countries.
The question of improving competitiveness on the world market is one of the most urgent areas of development for Ukraine, and clusterization is one of the ways of effective economic development and its maintenance on the proper level in the system of world economic relations. Taking into account that the transport and logistics industry plays an important role in the public production of our country, the formation of transport and logistics clusters will have great social and economic significance for both the regional and national economies. Clusters become the poles of economic growth, not only of individual regions in which they are localized, but also of the state as a whole. The task of the state is to create the necessary conditions, an attractive investment environment for the emergence of new ones and the development of existing clusters.
KEYWORDS: TRANSPORT AND LOGISTICS SYSTEM, TRANSPORT AND LOGISTIC CLUSTER, LOGISTIC CENTER.
REFERENCES
Porter, M.E. (2000). Konkurentsiia [Competition]. (Trans). Moscow: Williams [in Russian].
Prokudin G.S. Prospects of cross-border cooperation of Ukraine in transport sphere / GS Prokudin, O.A. Chupaylenko, O.S. Dudnik // International Scientific Conference Innovative Economy: Processes, Strategies, Technologies / Conference Proceedings, Part II, January 27, 2017, Kielce, Poland: The Baltic Publishing. - P. 53-55.
AUTHOR
Prokudin Georgiy S., Ph.D., Engineering (Dr.), National Transport University, head of the department of international transportation and customs control, e-mail<EMAIL_ADDRESS>+380633270243, Ukraine, 01010, city Kyiv, M. Emelyanovich-Pavlenko str. 1, of. 439, orcid.org/0000-0003-2077-5746.
ttupaylenko Olexii A., PhD, associate professor, National Transport University, associate professor department international transportation and customs control, e-mail<EMAIL_ADDRESS>tel. +380975052559, Ukraine, 01010, Kyiv, M. Omelyanovicha-Pavlenko str. 1, of. 437, orcid.org/0000-0002- 2004-0355.
Hilevska K.Yu., PhD, National Transport University, associate professor department international transportation and customs control, e-mail<EMAIL_ADDRESS>tel. +380667675197, Ukraine, 01010, Kyiv, M. Omelyanovicha-Pavlenko str. 1, of. 437, orcid.org/0000-0003-0076-0942.
Maydanik Ekaterina, National Transport University, Postgraduate Student, Department of International Transport and Customs Control, e-mail<EMAIL_ADDRESS>tel.<PHONE_NUMBER>, Ukraine, 01010, city Kiev, Yemelyanovich Pavlenko str. 1, office 437, orcid.org/0000-0002-7083-3417.
REVIEWER
Polishchuk V.P., Doctor of Technical Sciences, Professor, National Transport University, Head of the Department of Transport Systems and Road Safety, Kyiv, Ukraine.
Miamlin S.V., Doctor of Technical Sciences, Professor, Branch "Research and Design and Technological Institute of Railway Transport", Deputy Director, Kyiv, Ukraine.
Article language: Ukrainian
Open Access:
http://publications.ntu.edu.ua/visnyk/46/274.pdf
Print date: 15.04.2020
Online publication date: 27.10.2020


\t
is just literal t
here. For tab, use "$(printf '\t')"
instead.
# Want tab
var=foo\tbar
or
# Want linefeed
var=foo\nbar
var="foo$(printf '\t')bar" # As suggested in warning
var="$(printf 'foo\tbar')" # Equivalent alternative
or
# Literal, quoted linefeed
line="foo
bar"
ShellCheck has found a \t
, \n
or \r
in a context where they just become regular letter t
, n
or r
. Most likely, it was intended as a tab, linefeed or carriage return.
To generate such characters (plus other less common ones including \a
, \f
and octal escapes) , use printf
as in the example. The exception is for linefeeds that would be stripped by command substitution; in these cases, use a literal quoted linefeed instead.
Other characters like \z
generate a [[SC1001]] info message, as the intent is less certain.
None.


Create A Standard Projection
Name
Source
Select Type
Index Streams
Categorize Stream by Path
Categorize Event by Stream Path
Index Events by Event Type
Reading Speed Test Handler
Post