BEIRUT: THE LAST HOME MOVIE A film review by Thomas E. Billings Copyright 1989 Thomas E. Billings
Director: Jennifer Fox. Documentary; USA, 1987, color, 123 minutes. Released by: Circle Releasing Corp.
This documentary tells the story of a woman, Gaby Bustros, who returned to her home in Beirut in 1981 after spending 15 years in the US, and who decides to stay in Beirut despite the ongoing civil war. The Bustros family consists of Gaby and her two older sisters (all in their thirties), her younger brother (in his twenties), and her mother. The family lives in a very large and luxurious mansion located in the Ashrafiya neighborhood of Beirut, scene of some of the most vicious fighting of the Lebanese civil war.
The first half of the film centers on how the family manages to live nearly normal lives, despite the violent war raging around them. The family essentially ignores the fact that artillery shells have landed in their garden, blowing up trees and killing a soldier from the local militia. When the shelling gets really fierce, they close all the window shutters and throw small neighborhood parties while the rockets and artillery explode around them! Many of the interviews in the film have as background noise the gunfire of the war, which seems to never end. The considerable wealth of the Bustros family is a sharp contrast to the chaos and destruction that surrounds them.
A point of considerable discussion in the film is the fact that the family could sell their home at a substantial profit, and move to a safer area (Paris, New York, etc.). However, Gaby's oldest sister refuses to consider the idea and insists on staying. The film suggests that her reluctance to move may be because she finds the war to be "exciting." A more pedestrian & also more plausible explanation is that she has an emotional attachment to the house. Unfortunately, the film does not explore this possibility.
In the middle of the film, there is an interesting conversation with two male friends of the family, which takes place on a sailboat in Beirut harbor. One friend blames the war on the laziness of the Lebanese & their unwillingness to protect their freedom. The other friend claims that war has become a way of life for the Lebanese!
Although the first half of the movie provides an interesting look at life in a war zone from a woman's perspective, the last half of the film is a real disappointment. The film moves into a study of the (failed) love lives of the sisters, their feelings for their late father, and the upcoming wedding of Gaby's brother. In other words, the film degenerates into something resembling a (very boring) soap opera! The only high point of the second half is the spectacular and, yes, beautiful, footage of nighttime artillery & rocket battles in Beirut, and the warm glow of the city as it burns afterward.
I went to see this film because I have some first-hand knowledge of Beirut, having visited the city three times. [My last visit was unscheduled; I was flying standby from New Delhi to Rome, and was offloaded in Beirut at a time when there was active fighting. I had the "privilege" of experiencing the civil war first hand. Moral of story: if you fly standby, don't fly through Beirut!] Also, the local film critics praised the film highly. I was deeply disappointed by the film, and regard it as a rather boring soap opera style documentary. Overall evaluation: poor; recommend you avoid it.
P.S. The Boston PBS station, WGBH, provided some of the funding for this film. This suggests that the film may soon appear on PBS television stations. If you are a supporter of your local PBS station, you might consider sending their programming department a note, suggesting that they not waste any of their (limited) programming budget on this boring film!
Reviewer: Thomas E. Billings; Department of Statistics University of California, Berkeley Reviewer contact<EMAIL_ADDRESS>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


EURO 2020 - Blockchain Bets!

PUBLISH AN OFFER
SELL!
BUY FROM AN OFFER
BUY!


| I l@ve RuBoard |
No amount of genius can overcome a preoccupation with detail
Levy's Eighth Law
Details mess up our pristine code—especially if they change frequently. Every time we have to go in and change the code to accommodate some change in business logic, or in the law, or in management's personal tastes of the day, we run the risk of breaking the system—of introducing a new bug.
So we say "out with the details!" Get them out of the code. While we're at it, we can make our code highly configurable and "soft"—that is, easily adaptable to changes.
First, we want to make our systems highly configurable. Not just things such as screen colors and prompt text, but deeply ingrained items such as the choice of algorithms, database products, middleware technology, and user-interface style. These items should be implemented as configuration options, not through integration or engineering.
Tip 37
Configure, Don't Integrate
Use metadata to describe configuration options for an application: tuning parameters, user preferences, the installation directory, and so on.
What exactly is metadata? Strictly speaking, metadata is data about data. The most common example is probably a database schema or data dictionary. A schema contains data that describes fields (columns) in terms of names, storage lengths, and other attributes. You should be able to access and manipulate this information just as you would any other data in the database.
We use the term in its broadest sense. Metadata is any data that describes the application—how it should run, what resources it should use, and so on. Typically, metadata is accessed and used at runtime, not at compile time. You use metadata all the time—at least your programs do. Suppose you click on an option to hide the toolbar on your Web browser. The browser will store that preference, as metadata, in some sort of internal database.
This database might be in a proprietary format, or it might use a standard mechanism. Under Windows, either an initialization file (using the suffix .ini) or entries in the system Registry are typical. Under Unix, the X Window System provides similar functionality using Application Default files. Java uses Property files. In all of these environments, you specify a key to retrieve a value. Alternatively, more powerful and flexible implementations of metadata use an embedded scripting language (see Domain Languages, for details).
The Netscape browser has actually implemented preferences using both of these techniques. In Version 3, preferences were saved as simple key/value pairs:
SHOW_TOOLBAR: False
Later, Version 4 preferences looked more like JavaScript:
user_pref("custtoolbar.Browser.Navigation_Toolbar.open", false);
But we want to go beyond using metadata for simple preferences. We want to configure and drive the application via metadata as much as possible. Our goal is to think declaratively (specifying what is to be done, not how) and create highly dynamic and adaptable programs. We do this by adopting a general rule: program for the general case, and put the specifics somewhere else—outside the compiled code base.
Tip 38
Put Abstractions in Code Details in Metadata
There are several benefits to this approach:
It forces you to decouple your design, which results in a more flexible and adaptable program.
It forces you to create a more robust, abstract design by deferring details—deferring them all the way out of the program.
You can customize the application without recompiling it. You can also use this level of customization to provide easy work-arounds for critical bugs in live production systems.
Metadata can be expressed in a manner that's much closer to the problem domain than a general-purpose programming language might be (see Domain Languages).
You may even be able to implement several different projects using the same application engine, but with different metadata.
We want to defer definition of most details until the last moment, and leave the details as soft—as easy to change—as we can. By crafting a solution that allows us to make changes quickly, we stand a better chance of coping with the flood of directional shifts that swamp many projects (see Reversibility).
So you've made the choice of database engine a configuration option, and provided metadata to determine the user-interface style. Can we do more? Definitely.
Because business policy and rules are more likely to change than any other aspect of the project, it makes sense to maintain them in a very flexible format.
For example, your purchasing application may include various corporate policies. Maybe you pay small suppliers in 45 days and large ones in 90 days. Make the definitions of the supplier types, as well as the time periods themselves, configurable. Take the opportunity to generalize.
Maybe you are writing a system with horrendous workflow requirements. Actions start and stop according to complex (and changing) business rules. Consider encoding them in some kind of rule-based (or expert) system, embedded within your application. That way, you'll configure it by writing rules, not cutting code.
Less complex logic can be expressed using a mini-language, removing the need to recompile and redeploy when the environment changes. Have a look at page 58 for an example.
When to ConfigureAs mentioned in The power of plain Text, we recommend representing configuration metadata in plain text—it makes life that much easier. But when should a program read this configuration? Many programs will scan such things only at startup, which is unfortunate. If you need to change the configuration, this forces you to restart the application. A more flexible approach is to write programs that can reload their configuration while they're running. This flexibility comes at a cost: it is more complex to implement. So consider how your application will be used: if it is a long-running server process, you will want to provide some way to reread and apply metadata while the program is running. For a small client GUI application that restarts quickly, you may not need to. This phenomenon is not limited to application code. We've all been annoyed at operating systems that force us to reboot when we install some simple application or change an innocuous parameter. |
Enterprise Java Beans (EJB) is a framework for simplifying programming in a distributed, transaction-based environment. We mention it here because EJB illustrates how metadata can be used both to configure applications and to reduce the complexity of writing code.
Suppose you want to create some Java software that will participate in transactions across different machines, between different database vendors, and with different thread and load-balancing models.
The good news is, you don't have to worry about all that. You write a bean—a self-contained object that follows certain conventions—and place it in a bean container that manages much of the low-level detail on your behalf. You can write the code for a bean without including any transaction operations or thread management; EJB uses metadata to specify how transactions should be handled.
Thread allocation and load balancing are specified as metadata to the underlying transaction service that the container uses. This separation allows us great flexibility to configure the environment dynamically, at runtime.
The bean's container can manage transactions on the bean's behalf in one of several different styles (including an option where you control your own commits and rollbacks). All of the parameters that affect the bean's behavior are specified in the bean's deployment descriptor—a serialized object that contains the metadata we need.
Distributed systems such as EJB are leading the way into a new world of configurable, dynamic systems.
We've talked about users and developers configuring dynamic applications. But what happens if you let applications configure each other—software that adapts itself to its environment? Unplanned, spur-of-the-moment configuration of existing software is a powerful concept.
Operating systems already configure themselves to hardware as they boot, and Web browsers update themselves with new components automatically.
Your larger applications probably already have issues with handling different versions of data and different releases of libraries and operating systems. Perhaps a more dynamic approach will help.
Without metadata, your code is not as adaptable or flexible as it could be. Is this a bad thing?
The dodo didn't adapt to the presence of humans and their livestock on the island of Mauritius, and quickly became extinct.[2] It was the first documented extinction of a species at the hand of man.
[2] It didn't help that the settlers beat the placid (read stupid) birds to death with clubs for sport.
Don't let your project (or your career) go the way of the dodo.
For your current project, consider how much of the application might be moved out of the program itself to metadata. What would the resultant "engine" look like? Would you be able to reuse that engine in the context of a different application?
| I l@ve RuBoard |


We're seeking empathetic data and analytics translators
DataSF believes in the responsible, ethical use of data to improve decision-making and service delivery. We are a small team with an ambitious agenda: to empower the use of data in decision making and service delivery across San Francisco. This work requires empathy and deep curiosity.
As a team member you will stretch and challenge yourself. DataSF’s citywide purview empowers you to tackle data problems that touch all aspects of city life: housing, transportation, justice, health, the built environment, and many more. You will have unparalleled ability to help shape our approach to data use in each of these areas.
Current Open Positions:
Not seeing the right fit? Check out all the job openings on our parent team, Digital Services


{% extends 'main/base.html' %} {% load staticfiles %} {% block title %}Reset Password | {{ block.super }}{% endblock %} {% block customstyles %} {% endblock %} {% block main %}
Forgot your password? Please enter your email address. You will receive a link to create a new password via email. *Check your spam


9
1 And God blessed Noah and his sons and said to them, “Be fruitful and multiply and fill the earth.
2 The fear of you and the dread of you shall be upon every beast of the earth and upon every bird of the heavens, upon everything that creeps on the ground and all the fish of the sea. Into your hand they are delivered.
3 Every moving thing that lives shall be food for you. And as I gave you the green plants, I give you everything.
4 But you shall not eat flesh with its life, that is, its blood.
5 And for your lifeblood I will require a reckoning: from every beast I will require it and from man. From his fellow man I will require a reckoning for the life of man.
6 “Whoever sheds the blood of man,
by man shall his blood be shed,
for God made man in his own image.
7 And you, be fruitful and multiply, teem on the earth and multiply in it.”
8 Then God said to Noah and to his sons with him,
9 “Behold, I establish my covenant with you and your offspring after you,
10 and with every living creature that is with you, the birds, the livestock, and every beast of the earth with you, as many as came out of the ark; it is for every beast of the earth.
11 I establish my covenant with you, that never again shall all flesh be cut off by the waters of the flood, and never again shall there be a flood to destroy the earth.”
12 And God said, “This is the sign of the covenant that I make between me and you and every living creature that is with you, for all future generations:
13 I have set my bow in the cloud, and it shall be a sign of the covenant between me and the earth.
14 When I bring clouds over the earth and the bow is seen in the clouds,
15 I will remember my covenant that is between me and you and every living creature of all flesh. And the waters shall never again become a flood to destroy all flesh.
16 When the bow is in the clouds, I will see it and remember the everlasting covenant between God and every living creature of all flesh that is on the earth.”
17 God said to Noah, “This is the sign of the covenant that I have established between me and all flesh that is on the earth.”
Noah's Descendants
18 The sons of Noah who went forth from the ark were Shem, Ham, and Japheth. (Ham was the father of Canaan.)
19 These three were the sons of Noah, and from these the people of the whole earth were dispersed.
20 Noah began to be a man of the soil, and he planted a vineyard.
21 He drank of the wine and became drunk and lay uncovered in his tent.
22 And Ham, the father of Canaan, saw the nakedness of his father and told his two brothers outside.
23 Then Shem and Japheth took a garment, laid it on both their shoulders, and walked backward and covered the nakedness of their father. Their faces were turned backward, and they did not see their father's nakedness.
24 When Noah awoke from his wine and knew what his youngest son had done to him,
25 he said,
“Cursed be Canaan;
a servant of servants shall he be to his brothers.”
26 He also said,
“Blessed be the LORD, the God of Shem;
and let Canaan be his servant.
27 May God enlarge Japheth,
and let him dwell in the tents of Shem,
and let Canaan be his servant.”
28 After the flood Noah lived 350 years.
29 All the days of Noah were 950 years, and he died.


Move
(Edit Menu)To move one graphical element, click on the "Move" icon or "Edit -> Move". Then using the mouse, draw an area that includes the elements. Then, drag the mouse to the new location and release the mouse. As a result, the elements are moved the new place.
[Back]


--- layout: default title: abhi-v-sharma.github.io cv: passive projects: passive contact: passive description: Abhi Sharma is a student, music lover, tech geek, and book nerd. This is his website. ---
I wanted to make a clean, simple website on which to showcase the skills and experiences I'm accumulating, as well as keep an updated log of all the projects I'm working on. Take a look around, and don't hesitate to reach out!


Loans originated
Principal repaid
Loans outstanding
Current
1-15 days late
16-30 days late
31-60 days late
60+ days late
Default
Bad Debt
Average NAR%
Secured Car Loan
€59,719,984
€44,648,384
€15,071,599
€13,436,597
€470,218
€534,502
€629,368
-
-
-
12.1%
Mortgage Loan
€4,529,875
€3,768,786
€761,089
€725,307
-
€3,207
€13,417
€11,251
€7,906
-
13.4%
Invoice Financing
€5,787,531
€3,153,405
€2,634,126
€2,067,779
€132,681
€76,906
€165,171
€163,606
€27,981
-
11.1%


Tommy Dang
Assistant Professor
Department of Computer Science
Texas Tech University
Big Data Visualization, visual analytics, and Virtual Reality
Vung Van Pham, PhD student (Data visualization and visual analytics)
Vinh The Nguyen, PhD student (VR and AR)
Email: Tommy.Dang@ttu.edu


My Team
Jane Manager
Manager
ID: 1
Email:
<EMAIL_ADDRESS>Office number: 1
Jack Engineer
Engineer
ID: 2
Email:
<EMAIL_ADDRESS>GitHub:
jackengineer
Joe Shmo
Engineer
ID: 3
Email:
<EMAIL_ADDRESS>GitHub:
codeshmo
Jane Doe
Engineer
ID: 4
Email:
<EMAIL_ADDRESS>GitHub:
janecodes
Katie Intern
Intern
ID: 5
Email:
<EMAIL_ADDRESS>School: UC Berkeley


• Develop tools for the Breeding4Results information system.
• Assist in the ehancement of existing tools in the Breeding4Results information system.
• Provided data management assistance the Hybrid Rice Breeding and Green Super Rice breeding programs.
• Facilitated capacity building workshops on the creation and management of breeding studies using Breeding4Results information system and related tools.
• Developed web content focused on IT tools and technologies.
• Improved existing company web content.
• Designed, developed, and maintained the TTL program website, both front end and backend, as part of the Management Information System of the program.
• Designed and implemented a number of processes for improving data and information management tools and practices.
• Facilitated the data collection and data analysis of a number of monitoring and evaluation surveys for the different program interventions.
• Led the development of evaluation and data audit reports for various program interventions.
• Managed the data entry of collected data.
• Supported the design and creation of the database for the project information.
• Supported the data analysis of the collected data.
• Aided in the creation and management of the database used in the project activities and organization of the data.
• Analyzed and extracted relevant information from the database to be utilized in project activities.
• Facilitated the data entry of collected data into the database as well as managed the organization of the data.


A snappy introduction that sets out the main argument for the piece. I'll cover the main ideas right here and hint at my conclusion without giving the game away completely.
The public was outraged yesterday by reports that a fox, described by one onlooker as 'quick' and 'brown', had been spotted leaping over a 'lazy dog'.
The public was outraged yesterday by reports that a fox, described by one onlooker as 'quick' and 'brown', had been spotted leaping over a 'lazy dog'.
“If you can talk with crowds and keep your virtue, or walk with kings — nor lose the common touch.”
— Arnold Swarzenegger


Programming Language Suggester
Do you like creating objects?
Do you like strict rules?
Which ice cream flavor do you prefer?
Should white space (spaces and tabs) matter in a programming language?
Do you like complex and confusing things?
Yes!
Yes!
Chocolate
Yes!
Yes I am a masochist!


Studio Behind The Hit VR Game Beat Saber Shows Interest In Developing For Switch
Drop some beats
by Liam DoolanThe developer behind the popular rhythm-based VR game Beat Saber is teasing something that will apparently be revealed on 7th November.
When a Nintendo fan chimed in on this Twitter announcement and asked if the company's hit game was coming to the Switch, this was the reply from the Czech studio behind the game:
We are definitely having something like this in mind for the future. )
At the very least, it sounds as if the Beat Saber team plans to eventually work with Nintendo's hybrid device. The way it's been worded also makes it sound as if such a project could be something similar to the adrenaline-pumping VR title, rather than a port of it.
Would you like to see the Beat Saber developer drop some beats on the Switch? Tell us below.
[via gonintendo.com, old.reddit.com]


The Treble Clef
A clef, in music, is a symbol which indicates the pitch of the notes that are written after it. In the majority of modern music notation, the two clefs which are used are the treble clef (pictured on the staff above) and the bass clef, which will be covered in an advanced lesson.
Pianists will have musical sheets which will have these two clefs joined together, with the right hand playing the treble clef, and the left hand playing the bass clef. Instruments which generally play notes of a higher pitch will only have the treble clef, such as the flute and clarinet. Instruments whose music consists of only the bass clef include the trombone, or the cello.


{border-style px;} #ffffff;} vaccine EMM: countries immunity know RR: measures px; {font-family SA: font-size herd infection spread SARSâ€�CoVâ€� better cases different double; epidemic lower population testing Samuel border-color border-width early immune rate response solid; {font-style {font-weight Akiko Alizon COVIDâ€� Photograph: Research Rino University acquired bold case courier; em; fatality infected long natural pandemic phase possible pt;} quickly social vaccines virus


--- layout: post title: Ruby on Rails 2.3.6 Released categories: - releases author: Jeremy Kemper published: true date: 2010-05-23 07:56:00.000000000 +01:00 ---
We’ve released Ruby on Rails 2.3.6: six months of bug fixes, a handful of new features, and a strong bridge to Rails 3.
We deprecated some obscure and ancient features in Rails 2.3.6 so we could cut them entirely from Rails 3. If your app runs on Rails 2.3.6 without deprecation warnings, you’re in good shape for a smooth sail onward.
This slow-cooked dish is brought to you some 87 committers from our all-volunteer kitchen.
Now, let’s open the goodie bag!
cookies.permanent.signed[:remember_me] = current_user.id
. Read more.alert
and notice
, the most common flash keys in many apps, to self.alert = '...'
and self.notice = '...'
. Add redirect_to url, :alert => '...'
and :notice => '...'
. Read more.label
helper.self.table_name_prefix
. Read more.Post.reset_counters(1234, :comments)
to count the number of comments for post 1234 and reset its comments_count cache.add_
and change_column
support column positioning using :first => true
and :after => :other_column
.gem install yajl-ruby
assert_blank
and assert_present
. Read more.Object#singleton_class
from Ruby 1.8.8, deprecating our Object#metaclass
.Object#presence
that returns the object if it’s #present?
otherwise returns nil
. Example: region = params[:state].presence || params[:country].presence || 'US'
Enumerable#exclude?
to match include?
.Array#rand
to Array#random_element
to avoid collision with Kernel#rand
.Date#
and Time#last_(month|year)
to #prev_(month|year)
for Ruby 1.9 forward compatibility.ActiveResource::Base.include_root_in_json = true
to serialize as a hash of model name → attributes instead of a bare attributes hash. Defaults to false.Peruse the commit log for the full story.


| DOSE: |
20 mg |
oral |
2C-I |
(powder / crystals) |
I recently purchased 100 mg of 2C-i. I was a little worried about the quality and whether or not this stuff would even work at all.
Immediately after i received the package I decided to take just a little to get a feel for it. I would estimate that I took 6-8 mg orally (no scale). The effects were promising, and at least now I knew that it was the real deal. Very mild visuals, and a very speedy rush accompanied this dosage for a few hours after dropping it. Similar to a 1/4-1/2 hit of good lsd. I tried this dose 2 more times and noticed no side effects. At this level it is really good for social situations. It makes it really easy to talk and there is not any paranioia, very enjoyable!
I was really excited about taking a full dose, and I was going to try it with a friend on a saturday. Anticipation got the best of me, and since I didn't have to work Friday, Thursday night seemed like a good time to give it a try. :)
Setting- At home, roomates sleeping, comfortable surroundings, tv and computer to keep me occupied.
Dose- 18-25 mg orally (no scale) It is important to get a scale... I really wish I knew exactly how much I took, because this was the perfect level for me and when I do it again, I would like to have the same experiance. A little more might have been too much, and maybe a little less enjoyable...
[Erowid Note: A volume amount of one powder doesn't necessarily weigh the same as the same volume of another powder. For substances active at such a small dose, eyeballing is particularly unwise. See related article]
9:45 pm- I took 2 small scoops of the 2c-i and put it into a cup and put a little tea in with it. Swallowed it down, no taste at all when mixed with sweet tea.
10:15- At this point I am feeling a little excited and my body is starting to tingle, similar to extacy coming on, but that is the only thing these 2 drugs have in common...
10:45- Starting to notice mild oev's now, very speedy now and I am having trouble sitting still. Everything stays the same and slowly builds for the next hour.
11:45- DAMN!!! All of the sudden it just kicked in hard. Very intense visuals. I am watching tv and peoples faces are stretching, and when they talk there mouths are distorted. I also notice that even in the tv I am catching trails off of things moving around. I am watchin american chopper and when they are welding the sparks seem to fly out of the tv and onto the floor. This stuff is really cool!
12:30- Stronger, stronger, stronger!!! It is still picking up the pace. At this point I would compare it to about 2 hits of really good lsd.  Just tripping really hard... Everything is moving and swaying, patterns everywhere, walls moving. I am still very full of energy and keep going outside to smoke. Outside in the yard it is so completely opposite from the inside.
Everything seems so much more intense. The sky is the most beautiful thing I have ever seen! The clouds are rolling across the sky like the aurora, and there are faces all in the clouds, part of the whole show, the stars I can see are darting around like comets, with rainbow tails, and the trees are all dancing like verticle snakes, waving from top to bottom. I have never seen anything like this, not even on acid. I just want to lay in the driveway and watch the whole show. I cannot explain everything that i was seeing, or express how beautiful it was, but i liked it!
12:45- 3:00- This peak continued the rest of the time, i watched tv and got on the net for a while, still completely amazed the whole time at the visuals. Every bit as intense as what I descibed above. I didnt want it to end, but I knew I needed to get some sleep soon...
4:00-6:00- Slowly fading, trying to sleep but I cannot. Still tripping, even with my eyes closed. The only 2 side effects I noticed kicked in now. My neck hurt really bad, and I couldnt sleep at all. I think my neck hurt from being so tense during the whole trip (very intense). I finally fell asleep around 6:00 and slept well. I also noticed I felt great the next day too, after about 6 hours of sleep...
Summary- I really can't wait to try it again. Other experiances that I read on here made me think that it wasnt that strong and that it was like extacy. This stuff is like strong acid without the paranoia. I definately got my moneys worth!!!! Enjoy!
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.


Preparation time
30 mins to 1 hour
Cooking time
30 mins to 1 hour
Serves
Serves 10-12
Dietary
A Bakewell tart by any other name. Use the jam of your choice - raspberry is the classic option, though cherry also works well.
Equipment and preparation: you will need a 23cm/9in deep-sided, loose bottomed tart tin.
For the pastry, put the butter and flour into a food mixer and mix until the texture resembles breadcrumbs, then add the egg and mix until combined into a firm dough.
Wrap in cling film and place in the fridge to rest for 30 minutes.
For the tart, preheat the oven to 160C/325F/Gas 3.
On a work surface lightly dusted with flour, roll out the pastry to about 3mm thick.
Carefully line a 23cm/9in deep-sided, loose bottomed tart tin with the pastry, pressing the pastry into the edges of the tin. Spread the jam over the base of the tart, then place in the fridge to rest for 10 minutes.
To make the frangipane, beat the butter, vanilla seeds and sugar together in a bowl until pale and fluffy.
Crack in the eggs, one at a time, beating well after each addition, until all of the eggs have been fully incorporated into the mixture. Fold in the ground almonds carefully by hand.
Top the pastry case with the almond mixture and smooth to the edges, then decorate with the blanched almonds, in concentric circles.
Bake the tart in the preheated oven for 35-40 minutes, or until the filling has risen, is cooked through and the surface is pale golden-brown.
For the custard, put the milk and cream in a shallow saucepan with the vanilla pod leftover from making the frangipane filling. Set over a medium heat and bring to the boil.
Meanwhile, whisk the egg yolks and sugar together in a bowl.
When the milk is boiling, pour it onto the eggs whisking all the time, then return the whole mixture to the pan and cook over a gentle heat, whisking occasionally until thick enough to coat the back of a wooden spoon.
Strain into a clean pan and warm through.
To serve, cut the tart into wedges, place onto plates and pour the custard alongside.


{% extends 'base.html' %} {% load static %} {% block title %}Dashboard{% endblock title %} {% block body %} {% block sideman %} {% endblock sideman %}
You have 3 Notification
Server #1 overloaded.
Server #2 overloaded.
Server #3 overloaded.


- egg : Egg data object
The data to be analyzed
- subjgroup : list of strings or ints
String/int variables indicating how to group over subjects. Must be
the length of the number of subjects
- subjname : string
Name of the subject grouping variable
- listgroup : list of strings or ints
String/int variables indicating how to group over list. Must be
the length of the number of lists
- listname : string
Name of the list grouping variable
- analysis : string
This is the analysis you want to run. Can be accuracy, spc, pfr,
temporal or fingerprint
- position : int
Optional argument for pnr analysis. Defines encoding position of item
to run pnr. Default is 0, and it is zero indexed
- permute : bool
Optional argument for fingerprint/temporal cluster analyses. Determines
whether to correct clustering scores by shuffling recall order for each list
to create a distribution of clustering scores (for each feature). The
“corrected” clustering score is the proportion of clustering scores in
that random distribution that were lower than the clustering score for
the observed recall sequence. Default is False.
- n_perms : int
Optional argument for fingerprint/temporal cluster analyses. Number of
permutations to run for “corrected” clustering scores. Default is 1000 (
per recall list).
- parallel : bool
Option to use multiprocessing (this can help speed up the permutations
tests in the clustering calculations)
- match : str (exact, best or smooth)
Matching approach to compute recall matrix. If exact, the presented and
recalled items must be identical (default). If best, the recalled item
that is most similar to the presented items will be selected. If smooth,
a weighted average of all presented items will be used, where the
weights are derived from the similarity between the recalled item and
each presented item.
- distance : str
The distance function used to compare presented and recalled items.
Applies only to ‘best’ and ‘smooth’ matching approaches. Can be any
distance function supported by numpy.spatial.distance.cdist.


{% extends "base.html" %} {% block content %} About About About Built with by Fazle Abbas {% endblock content %}


Tonight I enjoyed an 800 mcg fentanyl lollipop I recently acquired from a friend. I had no idea what to expect, because I have never experimented with Opiates - not even Vicodin. I've been a daily pot-smoker for 3 yrs. now and had not been smoking when I ate the lollipop. Here’s a summary…
I began feeling effects about 15 minutes after letting the berry-flavored lollipop sit between my gums and cheek. It was mostly a slightly warm feeling in my head… it was kind of hard to see straight. I stood up and walked into my living room. I felt kind of wobbly and I was still working on the lollipop. It took me about an hour to finish the lollipop, and by the time I did I was feeling warm all over. I just sat and listened to reggae music. I thought to myself “This drug is no big deal… I just feel a little high, that’s all.” Soon I noticed certain noises around my house kept catching my attention more than usual. At one point I thought I heard a mouse crawling around in my kitchen (paranoia maybe?). I got up and walked around a little bit. I noticed I felt more euphoric, like I was really happy about something.
I sat down more and when I did, I could hardly keep my eyes open. I don’t know why, I wasn’t tired… but for some reason I just could NOT keep my eyes open. That lasted maybe 15 mins and that’s when I started feeling really excellent! Rushes of energy going through my veins for about 30-45 mins. It peaked with a 5-10 minute period of absolute bliss… I had a happiness compared to when MDMA first hits me.
But then suddenly I could feel the incredible high coming to a slow. I have done E about 10 times before and I’m used to the “climax” at the beginning of a 4-6 hr. trip. However with Fentanyl, I found it very odd that it was such a lengthy buildup and the “climax” of the high is closer the end of the trip. Total time of the Fentanyl experience was approx 2 ½ hrs.
The come down was yucky but short-lived. I felt kinda “poisoned” in the limbs and had about 5 minutes of nausea and shakiness. I smoked a bowl and that helped a lot with the come down. In fact, the weed brought the high back temporarily and eased the come down process. Now it has been 3 hrs. since I took it and I feel pretty normal other than being a little tired.
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.


See Android2Wp_SMSConverter project on GitHub for details.
{% with messages = get_flashed_messages() %}
{% if messages %}
Error
{% for message in messages %}
{{ message }}
{% endfor %}
{% endif %}
{% endwith %}
What happen with your uploaded data?
Uploaded files are only processed in memory and are not stored in any way.
If your not confident to send your data online, you can still use alternate methods proposed on GitHub page.


Though reading Jane Austen's Northanger Abbey in this picture, I like to think I concentrate as hard on the sustainability books I've been consuming as I look like I am here.
We live in a really complex society where our attention is being pulled from one side of human circumstance to another. We're bombarded with images and stories of people struggling to make ends meet, of people struggling to make ends meet in a financial crisis caused by any number of reasons (job loss, natural disaster, medical bills), but we're also bombarded with advertisements trying to sell us on what our lives would be like if only we bought this doodad, or that insta-worthy experience. All at the same time we're trying to think about our own futures, our own finances, and what matters to us as individuals1.
The climate crisis adds another layer of complexity on to our already complicated economic society2. In order to do our part often we feel like we need to analyze every single thing we do and consume, need to spend more in order to get something more sustainable, and often times the decisions about how sustainable our lives are (to some extent) are made made before they make it to the consumer. It's enough to make people either not care enough to put the effort in, or to be constantly stressed and worried to a point of fatigue and anxiety.
It concerns me that the choice of whether to be environmentally sustainable or not is in the hands of the consumer who also has to consider their own financial limitations, and most often the consumer is someone who is not as likely to be impacted significantly by global climate change3. It also concerns me that it is in most companies best interest to convince the consumer to buy more than they need, to replace what is still fully functional with something more in vogue, and yet the economic gains from those transactions are mostly not seen by the workers that create products.
What my goal is here is to learn not only what can be done to improve our own lives in an environmentally friendly and pocketbook friendly way, but also to explore what the limitations and benefits are of the strategies in place and being proposed. That involves a lot of reading, and hopefully some thoughtful conversations along the way.
Professionally, I am a software engineer, though studied archeology and environmental science in school. In my personal life, I've got several interests, not least of all are personal finance, environmental sustainability, and socio-economic equality. I'm attracted to the concepts of financial independence (and the FIRE movement) and minimalism, and think in a lot of ways most people's lives could be improved by reducing the level of consumerism that runs rampant in the United States.
I personally buy several things used, don't own a car and am hoping to be able to continue to not need one (full disclosure, my partner does, but I ride in it about once every other week, otherwise I take the bus). We've invested in a backyard compost tumbler, and the average age of all my clothes is about 5 years - some things are more like 15 years old. My big brown CO2 cloud hanging over my attempt at living an environmentally sustainable lifestyle is air travel. I love to travel and see the world, and my family lives 3000 miles away - my partner's family even farther.


Maura Derrane shares rare snaps of son Cal as they enjoy break at Kilkea Castle 23 Nov 2019, 17:35 by Clara Kelly (Image: instagram) (Image: instagram) (Image: instagram) (Image: instagram) (Image: instagram)


| 1 |
Xie_T_2017 |
A system dynamics approach to understanding the One Health concept |
Xie, Tai; Liu, Wenbao; Anderson, Benjamin D.; Liu, Xiaorong; Gray, Gregory C. |
2017 |
2017-09-06 |
None |
N |
PMC5587294 |
28877267.0 |
10.1371/journal.pone.0184430 |
o7qoazzi |
0.922610 |
Lipsitch_2014, Peiperl_2018 |
|
| 2 |
Schick-Makaroff_2016 |
What Synthesis Methodology Should I Use? A Review and Analysis of Approaches to Research Synthesis |
Schick-Makaroff, Kara; MacDonald, Marjorie; Plummer, Marilyn; Burgess, Judy; Neander, Wendy |
2016 |
2016-03-30 |
COMM-USE |
N |
PMC5690272 |
29546155.0 |
10.3934/publichealth.2016.1.172 |
nlv5xndn |
0.902081 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
Östlund_2011, Golding_2017 |
| 3 |
Östlund_2011 |
Combining qualitative and quantitative research within mixed method research designs: A methodological review |
Östlund, Ulrika; Kidd, Lisa; Wengström, Yvonne; Rowa-Dewar, Neneh |
2011 |
2011-03-31 |
PMC |
N |
PMC7094322 |
21084086.0 |
10.1016/j.ijnurstu.2010.10.005 |
850bvb9t |
0.876825 |
Zheng_2020, Nelson_2012 |
Golding_2017 |
| 4 |
Kurup_2019 |
Use of systematic epidemiological methods in outbreak investigations from India, 2008–2016: A systematic review |
Kurup, Karishma K.; John, Denny; Ponnaiah, Manickam; George, Tijo |
2019 |
2019-12-31 |
PMC |
N |
PMC7104104 |
|
10.1016/j.cegh.2019.02.010 |
gqjrwdo2 |
0.823998 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
Halton_2013 |
| 5 |
Al_Thobaity_2017 |
What are the most common domains of the core competencies of disaster nursing? A scoping review |
Al Thobaity, Abdullelah; Plummer, Virginia; Williams, Brett |
2017 |
2017-03-31 |
PMC |
N |
PMC7118449 |
28029612.0 |
10.1016/j.ienj.2016.10.003 |
3ttnd4ow |
0.822914 |
Lipsitch_2014 |
|
| 6 |
Khan_2015 |
The evidence base of primary research in public health emergency preparedness: a scoping review and stakeholder consultation |
Khan, Yasmin; Fazli, Ghazal; Henry, Bonnie; de Villa, Eileen; Tsamis, Charoula; Grant, Moira; Schwartz, Brian |
2015 |
2015-04-28 |
COMM-USE |
N |
PMC4415223 |
25925775.0 |
10.1186/s12889-015-1750-1 |
a6u7qguc |
0.790715 |
Lipsitch_2014 |
|
| 7 |
Lingervelder_2019 |
Point‐of‐care testing in primary care: A systematic review on implementation aspects addressed in test evaluations |
Lingervelder, Deon; Koffijberg, Hendrik; Kusters, Ron; IJzerman, Maarten J. |
2019 |
2019-08-19 |
NONCOMM |
N |
PMC6790572 |
31313873.0 |
10.1111/ijcp.13392 |
c13cv7cj |
0.780324 |
Nelson_2012, Nelson_2012, Zheng_2020 |
Alimi_2017 |
| 8 |
Wang_2019 |
Evaluation of Public Health Emergency Management in China: A Systematic Review |
Wang, Jia; Yuan, Beibei; Li, Zhengmao; Wang, Zhifeng |
2019 |
2019-09-18 |
COMM-USE |
N |
PMC6766041 |
31540510.0 |
10.3390/ijerph16183478 |
0dygete9 |
0.687312 |
|
|
| 9 |
Stirland_2020 |
Measuring multimorbidity beyond counting diseases: systematic review of community and population studies and guide to index choice |
Stirland, Lucy E.; González-Saavedra, Laura; Mullin, Donncha S.; Ritchie, Craig W.; Muniz-Terrera, Graciela; Russ, Tom C. |
2020 |
2020-01-01 |
COMM-USE |
N |
|
|
10.1136/bmj.m160 |
czbhddnm |
0.652043 |
Lipsitch_2014, MacIntyre_2020 |
Alimi_2017 |
| 10 |
GORI_2020 |
Analysis of the scientific literature in the first 30 Days of the novel coronavirus outbreak. |
DAVIDE GORI; Erik Boetto; Maria Pia Fantini |
2020 |
2020-03-30 |
BioRxiv |
Y |
|
|
10.1101/2<IP_ADDRESS>43315 |
11edrkav |
0.649073 |
Lipsitch_2014 |
|
| 11 |
Kan_T_2018 |
Factors influencing seasonal influenza vaccination behaviour among elderly people: a systematic review |
Kan, T.; Zhang, J. |
2018 |
2018-03-31 |
None |
N |
PMC7111770 |
29408191.0 |
10.1016/j.puhe.2017.12.007 |
xz0mf3dw |
0.583915 |
Lipsitch_2014 |
|
| 12 |
Gardner_2018 |
A rapid scoping review of Middle East respiratory syndrome coronavirus in animal hosts |
Gardner, Emma G.; Kelton, David; Poljak, Zvonimir; von Dobschuetz, Sophie; Greer, Amy L. |
2018 |
2018-11-12 |
PMC |
N |
PMC7165840 |
30421581.0 |
10.1111/zph.12537 |
yuky7hml |
0.577856 |
Nelson_2012, Nelson_2012, Lipsitch_2014 |
|
| 13 |
Barasa_2015 |
Setting Healthcare Priorities at the Macro and Meso Levels: A Framework for Evaluation |
Barasa, Edwine W.; Molyneux, Sassy; English, Mike; Cleary, Susan |
2015 |
2015-09-16 |
PMC |
N |
PMC4629697 |
26673332.0 |
10.15171/ijhpm.2015.167 |
9ywao2yt |
0.566992 |
Lipsitch_2014 |
Barasa_2014 |
| 14 |
Dixon_2015 |
What’s Past is Prologue: A Scoping Review of Recent Public Health and Global Health Informatics Literature |
Dixon, Brian E.; Pina, Jamie; Kharrazi, Hadi; Gharghabi, Fardad; Richards, Janise |
2015 |
2015-07-01 |
PMC |
N |
PMC4576440 |
26392846.0 |
10.5210/ojphi.v7i2.5931 |
sd0an0z3 |
0.565670 |
|
Wang_2016 |
| 15 |
Turner_1997 |
Epidemiology, Pathogenesis, and Treatment of the Common Cold |
Turner, Ronald B |
1997 |
1997-06-30 |
PMC |
N |
|
9207716.0 |
10.1016/s1081-1206(10)63213-9 |
q5xp7pa1 |
0.555891 |
Lipsitch_2014, Nelson_2012, Nelson_2012, Zheng_2020 |
|
| 16 |
Choi_2005 |
Twelve Essentials of Science-based Policy |
Choi, Bernard C.K |
2005 |
2005-09-15 |
PMC |
N |
PMC1435713 |
16164820.0 |
|
75ytw7ez |
0.554061 |
Lipsitch_2014 |
|
| 17 |
Barasa_2014 |
Setting healthcare priorities in hospitals: a review of empirical studies |
Barasa, Edwine W; Molyneux, Sassy; English, Mike; Cleary, Susan |
2014 |
2014-03-05 |
COMM-USE |
N |
PMC4353893 |
24604831.0 |
10.1093/heapol/czu010 |
e52wuc0h |
0.526309 |
|
Barasa_2015, Golding_2017 |
| 18 |
Gross_2013 |
China hotel research: A systematic review of the English language academic literature |
Gross, Michael J.; Gao, Hailian; Huang, Songshan (Sam) |
2013 |
2013-04-30 |
PMC |
N |
|
|
10.1016/j.tmp.2012.11.004 |
nuxtxzox |
0.505117 |
Lipsitch_2014 |
|
| 19 |
Martin_2006 |
Epidemiology studies in critical care |
Martin, Greg |
2006 |
2006-04-04 |
PMC |
N |
PMC1550877 |
16606434.0 |
10.1186/cc4897 |
5rfgyiit |
0.504294 |
|
|
| 20 |
Graham_2011 |
The objectives and outcomes of airport privatisation |
Graham, Anne |
2011 |
2011-08-31 |
PMC |
N |
PMC7148682 |
|
10.1016/j.rtbm.2011.05.004 |
v1hfq0jo |
0.496532 |
|
|
| 21 |
Lu_S_2019 |
Population-based surveys and interventions for mental health literacy in China during 1997–2018: a scoping review |
Lu, Shurong; Oldenburg, Brian; Li, Wenjing; He, Yanling; Reavley, Nicola |
2019 |
2019-10-26 |
COMM-USE |
N |
PMC6815452 |
31655552.0 |
10.1186/s12888-019-2307-0 |
pvfhn1wr |
0.484832 |
|
Miller_2019 |
| 22 |
Serrano-Guerrero_2020 |
A relevance and quality-based ranking algorithm applied to evidence-based medicine |
Serrano-Guerrero, Jesus; Romero, Francisco P.; Olivas, Jose A. |
2020 |
2020-07-31 |
PMC |
N |
PMC7114639 |
32114416.0 |
10.1016/j.cmpb.2020.105415 |
wr64fzjf |
0.479166 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
Rosenberg_2010, Rodríguez-Terol_2009, Luo_C_2018, Wang_2016 |
| 23 |
Shi_N_2016 |
Developing clinical practice guidelines for the integration of Chinese medicine and biomedicine: A new process |
Shi, Nannan; Zhong, Linda L.D.; Zhang, Chi; Han, Xuejie; Wang, Yuexi; Liu, Yuqi; Wang, Liying; Liu, Mengyu; Lu, Aiping |
2016 |
2016-12-31 |
PMC |
N |
PMC7102766 |
|
10.1016/j.eujim.2016.11.013 |
hqoluzz2 |
0.475511 |
|
|
| 24 |
Vergoulis_2020 |
BIP4COVID19: Releasing impact metrics data for articles relevant to COVID-19 |
Thanasis Vergoulis; Ilias Kanellos; Serafeim Chatzopoulos; Danae Pla Karidi; Theodore Dalamagas |
2020 |
2020-04-12 |
BioRxiv |
Y |
|
|
10.1101/2<IP_ADDRESS>093 |
6xkm2j0f |
0.471799 |
Nelson_2012, Nelson_2012, Lipsitch_2014 |
|
| 25 |
Cosco_2016 |
Operationalising resilience in longitudinal studies: a systematic review of methodological approaches |
Cosco, T D; Kaushal, A; Hardy, R; Richards, M; Kuh, D; Stafford, M |
2016 |
2016-08-08 |
COMM-USE |
N |
PMC5256275 |
27502781.0 |
10.1136/jech-2015-206980 |
qq6jzcoi |
0.468939 |
|
Johnston_2015 |
| 26 |
Thornton_2020 |
Panel 7 – Pathogenesis of otitis media – a review of the literature between 2015 and 2019 |
Thornton, R.B.; Hakansson, A.; Hood, D.W.; Nokso-Koivisto, J.; Preciado, D.; Riesbeck, K.; Richmond, P.C.; Su, Y.C.; Swords, W.E.; Brockman, K.L. |
2020 |
2020-03-31 |
PMC |
N |
|
31879085.0 |
10.1016/j.ijporl.2019.109838 |
jkm5ans8 |
0.458855 |
Lipsitch_2014 |
|
| 27 |
Berhe_2020 |
Global epidemiology, pathogenesis, immune response, diagnosis, treatment, economic and psychological impact, challenges, and future prevention of COVID-19: A scoping review |
Brhane Berhe; Haftom Legese; Hagos Degefa; Gebre Adhanom; Aderajew Gebrewahd; Fitsum Mardu; Kebede Tesfay; Miglas Welay; Hadush Negash |
2020 |
2020-04-06 |
BioRxiv |
Y |
|
|
10.1101/2<IP_ADDRESS>51052 |
prpooezh |
0.458466 |
Lipsitch_2014 |
|
| 28 |
Vindigni_2017 |
Hospital resuscitation teams: a review of the risks to the healthcare worker |
Vindigni, Stephen M.; Lessing, Juan N.; Carlbom, David J. |
2017 |
2017-10-11 |
COMM-USE |
N |
PMC5637256 |
29046809.0 |
10.1186/s40560-017-0253-9 |
wr73zrha |
0.454563 |
|
|
| 29 |
Ghosh_2020 |
Telemedicine for Diabetes Care in India during COVID19 Pandemic and National Lockdown Period: Guidelines for Physicians |
Ghosh, Amerta; Gupta, Ritesh; Misra, Anoop |
2020 |
2020-04-04 |
PMC |
Y |
|
|
10.1016/j.dsx.2020.04.001 |
na2zbx8g |
0.448284 |
Lipsitch_2014 |
|
| 30 |
Wong_2015 |
Use of ward closure to control outbreaks among hospitalized patients in acute care settings: a systematic review |
Wong, Holly; Eso, Katherine; Ip, Ada; Jones, Jessica; Kwon, Yoojin; Powelson, Susan; de Grood, Jill; Geransar, Rose; Santana, Maria; Joffe, A. Mark; Taylor, Geoffrey; Missaghi, Bayan; Pearce, Craig; Ghali, William A.; Conly, John |
2015 |
2015-11-07 |
COMM-USE |
N |
PMC4636845 |
26546048.0 |
10.1186/s13643-015-0131-2 |
in2sunsy |
0.447029 |
Lipsitch_2014, MacIntyre_2020, Nelson_2012, Nelson_2012 |
|
| 31 |
Schünemann_2006 |
Improving the use of research evidence in guideline development: 13. Applicability, transferability and adaptation |
Schünemann, Holger J; Fretheim, Atle; Oxman, Andrew D |
2006 |
2006-12-08 |
COMM-USE |
N |
PMC1712227 |
17156457.0 |
10.1186/1478-4505-4-25 |
0nvyf9in |
0.433380 |
Lipsitch_2014 |
Khan_2015 |
| 32 |
Gibbs_2019 |
Review of Literature for Air Medical Evacuation High-Level Containment Transport |
Gibbs, Shawn G.; Herstein, Jocelyn J.; Le, Aurora B.; Beam, Elizabeth L.; Cieslak, Theodore J.; Lawler, James V.; Santarpia, Joshua L.; Stentz, Terry L.; Kopocis-Herstein, Kelli R.; Achutan, Chandran; Carter, Gary W.; Lowe, John J. |
2019 |
2019-10-31 |
PMC |
N |
PMC7128392 |
31578975.0 |
10.1016/j.amj.2019.06.006 |
dbrp4vxc |
0.428528 |
Lipsitch_2014 |
|
| 33 |
Zimmerman_2016 |
A healthy degree of suspicion: A discussion of the implementation of transmission based precautions in the emergency department |
Zimmerman, Peta-Anne; Mason, Matt; Elder, Elizabeth |
2016 |
2016-08-31 |
PMC |
N |
PMC7128487 |
27133874.0 |
10.1016/j.aenj.2016.03.001 |
0r86qxz1 |
0.426367 |
Lipsitch_2014 |
|
| 34 |
Luongo_2015 |
Role of mechanical ventilation in the airborne transmission of infectious agents in buildings |
Luongo, J. C.; Fennelly, K. P.; Keen, J. A.; Zhai, Z. J.; Jones, B. W.; Miller, S. L. |
2015 |
2015-12-14 |
PMC |
N |
PMC7165552 |
26562748.0 |
10.1111/ina.12267 |
4r6sj166 |
0.424010 |
|
|
| 35 |
Brown_2018 |
Encephalitis diagnosis using metagenomics: application of next generation sequencing for undiagnosed cases |
Brown, Julianne R.; Bharucha, Tehmina; Breuer, Judith |
2018 |
2018-03-31 |
PMC |
N |
PMC7112567 |
29305150.0 |
10.1016/j.jinf.2017.12.014 |
hel3h25h |
0.420821 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
|
| 36 |
Siempos_2007 |
World wide web resources on control of nosocomial infections |
Siempos, Ilias I; Fragoulis, Konstantinos N; Falagas, Matthew E |
2007 |
2007-01-25 |
PMC |
N |
PMC2151856 |
17254319.0 |
10.1186/cc5116 |
czoul5o8 |
0.417555 |
|
|
| 37 |
Chan_2010 |
Post-traumatic stress disorder among Chinese women survivors of intimate partner violence: A review of the literature |
Chan, C.H.; Tiwari, A.; Fong, D.Y.T.; Ho, P.C. |
2010 |
2010-07-31 |
PMC |
N |
PMC7125845 |
20303490.0 |
10.1016/j.ijnurstu.2010.01.003 |
iwueedmm |
0.416395 |
Lipsitch_2014 |
|
| 38 |
Peiperl_2018 |
Preprints in medical research: Progress and principles |
Peiperl, Larry |
2018 |
2018-04-16 |
COMM-USE |
N |
PMC5901682 |
29659580.0 |
10.1371/journal.pmed.1002563 |
fcfanxtk |
0.414136 |
Lipsitch_2014 |
Rid_A_2016 |
| 39 |
Shank_2012 |
A Review of the Role of Cost–Benefit Analyses in 2-1-1 Diffusion |
Shank, Nancy |
2012 |
2012-12-31 |
PMC |
N |
PMC7135375 |
23157771.0 |
10.1016/j.amepre.2012.08.020 |
e00koo91 |
0.413045 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
|
| 40 |
Zemanick_2017 |
HIGHLIGHTS FROM THE 2016 NORTH AMERICAN CYSTIC FIBROSIS CONFERENCE |
Zemanick, Edith T.; Daines, Cori L.; Dellon, Elisabeth P.; Esthe, Charles R.; BreAnna, Kinghorn; Ong, Thida; Muhlebach, Marianne S. |
2017 |
2017-07-11 |
PMC |
N |
PMC5963883 |
28696526.0 |
10.1002/ppul.23707 |
fj7roabz |
0.409906 |
Lipsitch_2014 |
|
| 41 |
Harris_2020 |
An evidence-based framework for priority clinical research questions for COVID-19 |
Harris, Carlyn; Carson, Gail; Baillie, J Kenneth; Horby, Peter; Nair, Harish |
2020 |
2020-03-31 |
COMM-USE |
Y |
PMC7125419 |
|
10.7189/jogh.10-011001 |
i6pv90s9 |
0.404886 |
|
Cortegiani_2020 |
| 42 |
Lee_D_2013 |
A survey of SNOMED CT implementations |
Lee, Dennis; Cornet, Ronald; Lau, Francis; de Keizer, Nicolette |
2013 |
2013-02-28 |
PMC |
N |
|
23041717.0 |
10.1016/j.jbi.2012.09.006 |
n9uaip6n |
0.397958 |
|
Lingervelder_2019 |
| 43 |
Meslé_2019 |
The use and reporting of airline passenger data for infectious disease modelling: a systematic review |
Meslé, Margaux Marie Isabelle; Hall, Ian Melvyn; Christley, Robert Matthew; Leach, Steve; Read, Jonathan Michael |
2019 |
2019-08-01 |
COMM-USE |
N |
PMC6685100 |
31387671.0 |
10.2807/1560-7917.es.2<IP_ADDRESS>0216 |
s53curl7 |
0.387896 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
|
| 44 |
Rosenberg_2010 |
The most influential articles in critical care medicine |
Rosenberg, Andrew L.; Tripathi, Ravi S.; Blum, James |
2010 |
2010-03-31 |
PMC |
N |
PMC7127294 |
19327953.0 |
10.1016/j.jcrc.2008.12.010 |
41hjajw3 |
0.385624 |
Lipsitch_2014, MacIntyre_2020 |
Wang_2016, Bakri_2018, Asadi-Pooya_2020 |
| 45 |
Vlodavsky_2020 |
Forty Years of Basic and Translational Heparanase Research |
Vlodavsky, Israel; Ilan, Neta; Sanderson, Ralph D. |
2020 |
2020-02-29 |
PMC |
N |
PMC7142273 |
32274705.0 |
10.1007/978-3-030-34521-1_1 |
llha5cze |
0.382750 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
|
| 46 |
Moore_2014 |
Medical relevance of UK-funded non-human primate research published from January 1997 to July 2012 |
Moore, Edward |
2014 |
2014-07-23 |
COMM-USE |
N |
PMC4093757 |
24739383.0 |
10.1177/0141076814530686 |
ci7j70hu |
0.379644 |
|
Cortegiani_2020, Harris_2020 |
| 47 |
Garritty_2017 |
Developing WHO rapid advice guidelines in the setting of a public health emergency |
Garritty, Chantelle M.; Norris, Susan L.; Moher, David |
2017 |
2017-02-28 |
PMC |
N |
PMC7125868 |
27591906.0 |
10.1016/j.jclinepi.2016.08.010 |
2spugw99 |
0.379419 |
Lipsitch_2014 |
|
| 48 |
Lo_Iacono_2017 |
Challenges in developing methods for quantifying the effects of weather and climate on water-associated diseases: A systematic review |
Lo Iacono, Giovanni; Armstrong, Ben; Fleming, Lora E.; Elson, Richard; Kovats, Sari; Vardoulakis, Sotiris; Nichols, Gordon L. |
2017 |
2017-06-12 |
COMM-USE |
N |
PMC5481148 |
28604791.0 |
10.1371/journal.pntd.0005659 |
r9scxa76 |
0.375193 |
|
|
| 49 |
Kowalski_2018 |
Development of rapid guidelines: 1. Systematic survey of current practices and methods |
Kowalski, Sergio C.; Morgan, Rebecca L.; Falavigna, Maicon; Florez, Iván D.; Etxeandia-Ikobaltzeta, Itziar; Wiercioch, Wojtek; Zhang, Yuan; Sakhia, Faria; Ivanova, Liudmila; Santesso, Nancy; Schünemann, Holger J. |
2018 |
2018-07-13 |
COMM-USE |
N |
PMC6044042 |
30005712.0 |
10.1186/s12961-018-0327-8 |
5rdmnnsa |
0.370890 |
Lipsitch_2014 |
Garritty_2017, van_Schalkwyk_2010 |
| 50 |
Tawfik_2019 |
A step by step guide for conducting a systematic review and meta-analysis with simulation data |
Tawfik, Gehad Mohamed; Dila, Kadek Agus Surya; Mohamed, Muawia Yousif Fadlelmola; Tam, Dao Ngoc Hien; Kien, Nguyen Dang; Ahmed, Ali Mahmoud; Huy, Nguyen Tien |
2019 |
2019-08-01 |
COMM-USE |
N |
PMC6670166 |
31388330.0 |
10.1186/s41182-019-0165-6 |
f1f22cyc |
0.369000 |
Lipsitch_2014, Zheng_2020, Nelson_2012 |
Lingervelder_2019 |
| 51 |
Wu_T_2008 |
Traditional Chinese medicine in the treatment of acute respiratory tract infections |
Wu, Taixiang; Yang, Xunzhe; Zeng, Xiaoxi; Poole, Phillippa |
2008 |
2008-08-31 |
PMC |
N |
PMC7134919 |
18590956.0 |
10.1016/j.rmed.2008.03.015 |
f3lv7o4d |
0.368048 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
|
| 52 |
Murdaca_2019 |
Effects of AntagomiRs on Different Lung Diseases in Human, Cellular, and Animal Models |
Murdaca, Giuseppe; Tonacci, Alessandro; Negrini, Simone; Greco, Monica; Borro, Matteo; Puppo, Francesco; Gangemi, Sebastiano |
2019 |
2019-08-13 |
COMM-USE |
N |
PMC6719072 |
31412612.0 |
10.3390/ijms20163938 |
1rmwwjgi |
0.367845 |
Lipsitch_2014 |
|
| 53 |
Mukerji_2015 |
Review of economic evaluations of mask and respirator use for protection against respiratory infection transmission |
Mukerji, Shohini; MacIntyre, C. Raina; Newall, Anthony T. |
2015 |
2015-10-13 |
COMM-USE |
N |
PMC4605092 |
26462473.0 |
10.1186/s12879-015-1167-6 |
fim1ceko |
0.360544 |
|
Liang_2020 |
| 54 |
Miller_2019 |
Mental well-being of international migrants to Japan: a systematic review |
Miller, Russell; Tomita, Yuri; Ong, Ken Ing Cherng; Shibanuma, Akira; Jimba, Masamine |
2019 |
2019-11-03 |
None |
N |
PMC6858191 |
31685498.0 |
10.1136/bmjopen-2019-029988 |
1nkpd0yv |
0.356818 |
|
Golding_2017 |
| 55 |
Ishola_2011 |
Could influenza transmission be reduced by restricting mass gatherings? Towards an evidence-based policy framework |
Ishola, David A.; Phin, Nick |
2011 |
2011-12-31 |
PMC |
N |
PMC7104184 |
23856374.0 |
10.1016/j.jegh.2011.06.004 |
peppszqx |
0.350715 |
Nelson_2012, Nelson_2012, Lipsitch_2014 |
Halton_2013 |
| 56 |
Fontbonne_2020 |
Small animal reproduction: Scientific facts versus dogmas or unverified beliefs |
Fontbonne, Alain |
2020 |
2020-03-11 |
PMC |
N |
|
|
10.1016/j.theriogenology.2020.03.014 |
r6ocr18h |
0.347742 |
|
|
| 57 |
Thiébaut_2018 |
Artificial Intelligence in Public Health and Epidemiology |
Thiébaut, Rodolphe; Thiessard, Frantz |
2018 |
2018-08-29 |
NONCOMM |
N |
PMC6115208 |
30157525.0 |
10.1055/s-0038-1667082 |
xnfrulbf |
0.344406 |
Lipsitch_2014 |
Thiébaut_2017, Wang_2016 |
| 58 |
Dufour_2000 |
Diagnosis and Monitoring of Hepatic Injury. II. Recommendations for Use of Laboratory Tests in Screening, Diagnosis, and Monitoring |
Dufour, D Robert; Lott, John A; Nolte, Frederick S; Gretch, David R; Koff, Raymond S; Seeff, Leonard B |
2000 |
2000-12-01 |
PMC |
N |
PMC7110382 |
11106350.0 |
10.1093/clinchem/46.12.2050 |
ush0rbzz |
0.342332 |
Lipsitch_2014 |
|
| 59 |
Rockett_2004 |
Confirming microarray data—is it really necessary? |
Rockett, John C; Hellmann, Gary M |
2004 |
2004-04-30 |
PMC |
N |
PMC7127508 |
15028276.0 |
10.1016/j.ygeno.2003.09.017 |
zawnbgp1 |
0.339059 |
Zheng_2020, Nelson_2012, Nelson_2012 |
|
| 60 |
Maguire_2020 |
A living systematic review protocol for COVID-19 clinical trial registrations |
Maguire, Brittany J.; Guérin, Philippe J. |
2020 |
2020-04-02 |
COMM-USE |
Y |
PMC7141164 |
|
10.12688/wellcomeopenres.15821.1 |
9lm0sz5p |
0.337247 |
MacIntyre_2020, Nelson_2012, Nelson_2012 |
Cortegiani_2020, Sweiti_2017 |
| 61 |
Campeau_2018 |
Containment measures for emerging and re-emerging vector-borne and other infectious diseases of poverty in urban settings: a scoping review |
Campeau, Laurence; Degroote, Stéphanie; Ridde, Valery; Carabali, Mabel; Zinszer, Kate |
2018 |
2018-09-03 |
COMM-USE |
N |
PMC6120079 |
30173673.0 |
10.1186/s40249-018-0478-4 |
e0ucntn9 |
0.326788 |
|
Halton_2013, Kemunto_2018 |
| 62 |
AminJafari_2020 |
The possible of immunotherapy for COVID-19: A systematic review |
AminJafari, Akram; Ghasemi, Sorayya |
2020 |
2020-06-30 |
PMC |
Y |
|
|
10.1016/j.intimp.2020.106455 |
qr1rk9tr |
0.319512 |
Lipsitch_2014, Nelson_2012, Nelson_2012 |
|
| 63 |
Golding_2017 |
Exploring the psychological health of emergency dispatch centre operatives: a systematic review and narrative synthesis |
Golding, Sarah E.; Horsfield, Claire; Davies, Annette; Egan, Bernadette; Jones, Martyn; Raleigh, Mary; Schofield, Patricia; Squires, Allison; Start, Kath; Quinn, Tom; Cropley, Mark |
2017 |
2017-10-17 |
COMM-USE |
N |
PMC5649589 |
29062596.0 |
10.7717/peerj.3735 |
yrpkfhe8 |
0.318335 |
Lipsitch_2014 |
|
| 64 |
Li_X_2018 |
A comprehensive review and perspectives on pharmacology and toxicology of saikosaponins |
Li, Xiaojiaoyang; Li, Xiaoyu; Huang, Nana; Liu, Runping; Sun, Rong |
2018 |
2018-11-15 |
PMC |
N |
PMC7126585 |
30466994.0 |
10.1016/j.phymed.2018.09.174 |
81kxvj9o |
0.313253 |
|
|
| 65 |
Halter_2017 |
The determinants and consequences of adult nursing staff turnover: a systematic review of systematic reviews |
Halter, Mary; Boiko, Olga; Pelone, Ferruccio; Beighton, Carole; Harris, Ruth; Gale, Julia; Gourlay, Stephen; Drennan, Vari |
2017 |
2017-12-15 |
COMM-USE |
N |
PMC5732502 |
29246221.0 |
10.1186/s12913-017-2707-0 |
e7zc44ca |
0.313071 |
Lipsitch_2014, MacIntyre_2020 |
Golding_2017 |
| 66 |
Bishop-Williams_2017 |
A protocol for a systematic literature review: comparing the impact of seasonal and meteorological parameters on acute respiratory infections in Indigenous and non-Indigenous peoples |
Bishop-Williams, Katherine E.; Sargeant, Jan M.; Berrang-Ford, Lea; Edge, Victoria L.; Cunsolo, Ashlee; Harper, Sherilee L. |
2017 |
2017-01-26 |
COMM-USE |
N |
PMC5267362 |
28122603.0 |
10.1186/s13643-016-0399-x |
i229xv0o |
0.307158 |
Lipsitch_2014, MacIntyre_2020, Nelson_2012, Nelson_2012 |
Alimi_2017, Kenmoe_2019 |
| 67 |
Thiébaut_2017 |
Public Health and Epidemiology Informatics |
Thiébaut, R.; Thiessard, F. |
2017 |
2017-01-01 |
None |
N |
PMC6239244 |
29063574.0 |
10.15265/iy-2017-036 |
oktoqj06 |
0.300036 |
Lipsitch_2014, MacIntyre_2020 |
Thiébaut_2018, Kemunto_2018, Wang_2016 |


{% extends 'base.html'%} {% block content%} {% block styles %} {{super()}} {% endblock %}
Don't have an account? Sign Up


VFORWaTer
{# #}
{# #}
{# #}
{##}
{#TODO: value has to be updated through js before reading to make sure its up-to-date #}
{#Cookie window 2/2#}
{# Virtuelle Forschungsumgebung für die Wasser- und terrestrische Umweltforschung#}
{% trans "Virtual research environment for water and terrestrial environmental research" %}V-FOR-WaTer Portal


Identity Server
Create An Account
Enter all text fields to complete registration
Username
Password
Confirm password
Email
First Name
Last Name
Register
Already have an account?
Sign in


|
CMSIS-Pack
Version 1.7.2
Delivery Mechanism for Software Packs
|
PackChk is a utility for validation of a Software Pack. It operates on the unzipped content of the Software Pack and is located in the directory .\CMSIS\Utilities of the ARM::CMSIS Pack. PackChk is available for Windows and Linux operating systems.
PackChk performs the following operations:
PackChk is invoked from the command line:
| <options> | Short Name | Description |
|---|---|---|
| -i <file> | Check component dependencies | Reference PDSC file(s) used to resolve component dependencies in conditions. |
| -n <file> | Write Pack file name | Write a standardized name for the Software Pack to the specified ASCII file. |
| -s | Verify SVD files | Each SVD file referenced in the *.pdsc file is validated with SVDConv. With this option set, SVDConv.exe is invoked from the same directory as PackChk. |
| -u <url> | Pack Server URL | Verifies that the specified URL matches the <url> element in the *.pdsc file. |
| -v | Verbose | Prints extra process information. |
| -x <msg-list> | Suppress | Suppress all listed validation messages. You can separate the values with blanks to create a list or repeat the option. Ranges are not allowed. Suppressing validation messages does not affect error and warning counters. For a list of messages refer to Validation Messages. |
| -h/-? | Help | Show help. |
Examples
Run PackChk on the package description file called MyVendor.MyPack.pdsc. PackChk verifies the file against the Software Pack that is located in the same directory.
PackChk MyVendor.MyPack.pdsc
Run PackChk on the package description file called MyVendor.MyPack.pdsc in the current directory and try to resolve conditions using the ARM.CMSIS.pdsc file based in another directory.
PackChk MyVendor.MyPack.pdsc -i ..\..\PACK\ARM\CMSIS\ARM.CMSIS.pdsc
Run PackChk on the package description file called MyVendor.MVCM3.pdsc, verify SVD files, verify the URL to the Pack Server, and generate a ASCII text file with the standardized name of the Software Pack.
PackChk "MyVendor.MVCM3.pdsc" -s -u "http://www.myvendor.com/pack" -n packname.txt
Run PackChk on the package description file called MyVendor.MVCM3.pdsc. Suppress validation messages M304 and M331.
PackChk MyVendor.MVCM3.pdsc -x M304 M331 // messages as a list PackChk MyVendor.MVCM3.pdsc -x M304 -x M331 // option repeated
The following table explains the categories for the output messages issued by PackChk utility. Sections below list the errors and warnings and contain recommendations on how to resolve them.
Categories
| Code | Category | Description |
|---|---|---|
| M0xx | Info messages | Help and Progress messages. No action required. |
| M1xx | Internal errors | Internal execution errors |
| M2xx | Invocation Errors | Errors in the command line input. |
| M3xx M4xx | Validation Messages | Errors and Warnings from the pack validation. |
| M5xx | Model Errors | Errors in RTE model creation |
The errors in this category are issued because of an internal error in the PackChk utility.
| Message Number | Type | Description | Details and Actions |
|---|---|---|---|
| M100 | ERROR | GetModuleHandle failed | Contact Arm for clarifications |
| M101 | ERROR | Unknown error! | Contact Arm for clarifications |
| M102 | ERROR | MFC initialization failed | Contact Arm for clarifications |
| M103 | ERROR | Internal Error: 'REF' | Contact Arm for clarifications |
| M104 | ERROR | Path empty when searching for other PDSC files | Execute the check in verbose mode and try to identify the PDSC file intended for use. Correct the PDSC. |
| M107 | WARNING | 'FEATURE' is not supported by current version of 'OS' PackChk. | Some PackChk functionalities are available only on certain OS platforms. For example SVD check is supported only on Windows. Do not use listed 'FEATURE' or change operating system. |
| M108 | TEXT | Reading PDSC File failed! | XML parsing of the PDSC file failed. Verify syntax of the PDSC file. |
| M109 | TEXT | Constructing Model failed! | Contact Arm for clarifications |
| M110 | TEXT | Verifying Model failed | Contact Arm for clarifications |
The errors in this category are issued because of an incorrect command-line input that prevents the PackChk execution.
| Message Number | Type | Message Text | Details and Actions |
|---|---|---|---|
| M200 | ERROR | Invalid arguments! | At least one argument is wrong. Correct the argument. |
| M201 | ERROR | Too many arguments! | The list of arguments is too long. Verify if you have used one argument twice. |
| M202 | ERROR | No PDSC input file specified | Correct the command line. PackChk expects a *.pdsc file name as input. |
| M203 | ERROR | Error reading PDSC file 'PATH/FILENAME'! | Verify the PDSC file for consistency. |
| M204 | ERROR | File not found: 'PATH' | The specified PDSC file could not be found in the PATH displayed in the message. Correct the path or the filename. |
| M205 | ERROR | Cannot create Pack Name file 'PATH' | Check the disk space or your permissions. Correct the path name. |
| M206 | ERROR | Multiple PDSC files found in package: 'FILES' | Only one PDSC file is allowed in a package. Remove unnecessary PDSC files. The message lists all *.pdsc files found. |
| M207 | ERROR | PDSC file name mismatch! Expected: 'PDSC1.pdsc' Actual : 'PDSC2.pdsc' | The PDSC file expected has not been found. Rename or exchange the PDSC file. |
| M208 | ERROR | Error calling SVDConv: 'PATH' | SVDConv utility could not be executed. Verify the permissions. Correct the path name. |
| M209 | ERROR | Unknown Option: 'OPT' | The command line option 'OPT' is not known or invalid. |
| M210 | ERROR | Only one input file to be checked is allowed. | You can only check one PDSC file at a time. |
| M211 | ERROR | Cannot find SVDConv.exe: 'CMDLINE' | SVDConv utility was not found in specified 'CMDLINE'. Copy the SVDConv.exe into the directory of PackChk. Default is CMSIS\Utilities. |
The messages in this category are issued by PackChk during package validation. This can be for example incorrect use of the pack schema in the PDSC file, missing files, broken dependancies and others. ERROR messages must be resolved to ensure that the package is compliant to the CMSIS-format. WARNING messages should be checked and are strongly recommended to be resolved.
| Message Number | Type | Message Text | Details and Actions |
|---|---|---|---|
| M301 | ERROR | Checking Pack URL of PDSC file failed: Expected URL : 'URL1' Package URL : 'URL2' | The URL specified in the package does not match the value entered for comparison in option -u . Check for possible misspellings in both URLs. Refer to /package/url. |
| M302 | ERROR | No vendor tag found in the PDSC file! Add the <vendor> tag and provide the vendor name. For example: <vendor>Keil</vendor> . | Vendor name is mandatory required in the package description but was not found in the /package element in the PDSC file. Within the parent <package> element enter the tag <vendor> and add the vendor name. For example: <vendor>Keil</vendor> . Refer to /package/vendor. |
| M303 | ERROR | No package name found in the PDSC file! Add the <name> tag and provide the package name. For example: <name>MCU-Name_DFP</name> . | Package name is mandatory required in the package description but was not found in the /package element in the PDSC file. Within the parent <package> element enter the tag <name> and add the package name. For example <name>MCU-Name_DFP</name> . Refer to /package/name. |
| M304 | WARNING | No package URL (<url>-tag and/or value) found in PDSC file! | Package URL is mandatory required in the package description but was not found in the /package element in the PDSC file. Within the parent <package> element enter the tag <url> and add the URL that should be used to download the package. Refer to /package/url. |
| M305 | ERROR | No releases ("\<release>" elements in a <releases>-tag) found in PDSC file!" | At least one package release shall be specified in the PDSC file, but none was not found. Use <release> tag to specify release information in <releases> element. Refer to /package/releases/release. |
| M306 | ERROR | No package description found in the PDSC file. Add the <description>-tag and provide a descriptive text. | Package description is mandatory required in the package description but was not found in the /package element in the PDSC file. Within the parent <package> element add the tag <description> and briefly describe the package content. Refer to /package/description. |
| M307 | ERROR | Checking SVD file 'PATH' failed! | Verify the consistency of the *.SVD file. Refer to SVD File Validation. |
| M310 | ERROR | Filename mismatch (case sensitive): PDSC name : 'PDSC_FILENAME' Filename : 'SYSTEM' | Filenames are case sensitive. Correct spelling. |
| M315 | ERROR | Invalid URL / Paths to Drives are not allowed in Package URL: 'URL' | Correct package URL 'URL'. Refer to /package/url. |
| M316 | WARNING | URL must end with slash '/': 'URL' | Correct package URL 'URL'. Refer to /package/url. |
| M323 | ERROR | File/Path not found: 'PATH' | The file or path 'PATH' entered in the PDSC file could not be found. Verify the path information. |
| M324 | WARNING | Board referenced in Example 'EXAMPLE' is undefined: 'VENDOR' : 'BOARD' | The definition of the board referenced in the example application could not be found. Define the board (/package/boards/board) or correct the reference information (/package/examples/example/board). |
| M325 | ERROR | Board 'NAME' redefined, already defined in Line 'LINE': 'PATH' | This board has been defined already in the line 'LINE' of the file 'PATH'. Verify and remove one of the board definitions. Refer to /package/boards/board. |
| M326 | ERROR | Path is not conformant: 'PATH': Absolute Paths or Drive references are not allowed, use Paths relative to PDSC file. | The path needs to be relative to the PDSC file so that a dependency of a certain file system does not occur. |
| M327 | WARNING | Path is not conformant: 'PATH': Backslashes are not recommended, use forward slashes. | Paths to files should adhere to the POSIX standard using forward slashes (/). |
| M328 | ERROR | Version not set for Release Information 'DESCR' | The release defined through the description 'DESCR' requires the attribute <version>. Refer to /package/releases/release. |
| M329 | ERROR | Description not set for Release Information 'VER' | The release defined through the version 'VER' needs a description. Refer to /package/releases/release. |
| M330 | ERROR | Condition redefined: 'COND', already defined in Line 'LINE' | The condition has been defined already in a previous line. Correct the condition name, or remove the duplicate. Refer to /package/conditions/condition. |
| M331 | WARNING | Condition unused: 'COND' | The condition has been defined but not used further. Remove the condition or add condition rules. Refer to /package/conditions/condition. |
| M332 | ERROR | Condition undefined: 'COND' | A condition has been used but not defined. Correct the name of the condition or define the missing condition. Refer to /package/conditions/condition. |
| M333 | WARNING | Component has no condition: Cclass= 'CCLASS', Cgroup= 'CGROUP', Csub='CSUB', Cversion= 'CVER' | The component defined has no condition. If the component has restrictions, then add a condition to the component definition. Refer to /package/components/.../component. |
| M334 | WARNING | Config File has no version: 'PATH' | Specified file 'PATH' does not contain version information. It is recommended to specify versions for configuration files. Add attribute version with the file version in the <file> tag that defines the 'PATH' file in the PDSC. Refer to /package/.../files/file. |
| M335 | WARNING | Component declared as 'Board Support' has no ref to a device: Cclass= 'CCLASS', Cgroup= 'CGROUP', Cversion= 'CVER' | A component defined as 'board support' needs a reference to a device. Add a device or correct the component definition. Refer to attribute Cclass of /package/components/.../component and /package/boards/board/mountedDevice. |
| M336 | WARNING | No reference to a device or device not found: Cclass= 'CCLASS', Cgroup= 'CGROUP', Cversion= 'CVER' | Define the device /package/devices/family/../device or correct the information about the device in the reference. |
| M337 | WARNING | File with category 'CAT' has wrong extension 'EXT': 'PATH' | The extension of the file does not match the file category 'CAT' specified in the category attribute. Verify the extension to match the category. Refer to /package/.../files/file. |
| M338 | WARNING | No releases found. | The PDSC file is missing release information. Add <release> information to the file. Refer to /package/releases element. |
| M339 | WARNING | Include Path 'PATH' must not be a file! | The path specified contains a filename. Correct the path infomation and remove the filename. Refer to /package/.../files/file. |
| M340 | WARNING | Include Path 'PATH' must end with '/' or '\' | Include paths must end with a slash or backslash. Verify and correct the path name. Refer to /package/.../files/file. |
| M341 | WARNING | File with 'COMP' dependency must have extension 'EXT' : 'PATH' | The file 'PATH' with dependency on component 'COMP' must have a specific extension 'EXT'. Verify the dependency and correct the file extension. Refer to /package/.../files/file. |
| M342 | WARNING | File with attribute 'ATTR' must not have category 'CAT': 'PATH' | File 'PATH' is defined with the attribute attr set to 'ATTR'. This conflicts with the file category 'CAT' specified in category attribute. For example attr=config and category=include are not allowed for the same file. Correct the file attribute or the file category. Refer to /package/.../files/file. |
| M343 | WARNING | File with attribute 'ATTR' requires 'ATTR2' attribute: 'PATH' | File 'PATH' is defined with the attribute 'ATTR' that requires presense of attribute 'ATTR2' as well, but such attribute was not found. For example, attr=template requires that attribute select is defined. Add the required attribute 'ATTR2' or correct the attribute 'ATTR' in the <file> element. Refer to /package/.../files/file. |
| M344 | WARNING | File shall have condition containing 'COND': 'PATH' | File definition for 'PATH' shall contain a condition 'COND'. Add attribute condition with the 'COND' in the <file> tag that defines the 'PATH' file. Refer to /package/.../files/file.. |
| M345 | WARNING | URL not found : 'URL' | The specified URL could not be found. Correct the URL. Refer to /package. |
| M346 | WARNING | Referenced device(s) in 'BOARD' not found: 'DEVICE' | The device or devices specified for the board could not be found. Verify and correct the device name or the board name. Refer to /package/boards/board/mountedDevice and /package/boards/board/compatibleDevice. |
| M347 | WARNING | Generator ID in Component Cclass= 'CCLASS', Cgroup= 'CGROUP', Cversion= 'CVER' is undefined: 'GENID' | The generator ID used in the component could not be found. Verify and correct the generator ID (/package/components/.../component), or define the generator ID (ref /package/generators/generator). |
| M348 | WARNING | Feature redefined for 'MCU', see Line 'REF_LINE': 'FEATURE' | This feature 'FEATURE' has been defined already on the same level in line 'REF_LINE'. The feature characteristics defined on line 'LINE' overwrite those from 'REF_LINE'. Correct the feature (/package/devices/family/.../feature). |
| M349 | WARNING | Examples found, but no board description(s) found | Example projects have been found for a board that was not defined. Correct the entry for the examples (/package/examples/example/board) or define the board (/package/boards/board). |
| M350 | WARNING | No 'COMP' found for 'VENDOR' : 'MCU' ('COMPILER') | The package (/package) defines a Vendor-MCU combination for which no component was defined. Define a component (/package/components/.../component) or verify the 'VENDOR' - 'MCU' settings. |
| M351 | WARNING | Component 'COMP' ('COMPID') error for 'VENDOR': 'MCU' ( 'COMPILER'): 'MSG' | An unspecified error was found for the component. The message might give detailed information about the error. |
| M352 | WARNING | No Directories/Files found for 'COMP' ('COMPID') for 'VENDOR': 'MCU' ('COMPILER') | No files or directories could be found for the defined component. Add the missing information. Refer to /package/.../files. |
| M353 | WARNING | No 'FILECAT' File found for Component 'COMP' ('COMPID') for 'VENDOR' : 'MCU' ('COMPILER') | No file with the mentioned file category was found for the component. Verify whether the file exists or correct the information. Refer to attribute category in /package/.../files/file. |
| M354 | WARNING | Multiple 'FILECAT' Files found for Component 'COMP' ('COMPID') for 'VENDOR' : 'MCU' ('COMPILER') | Multiple files with the mentioned file category were found for the specified component. Verify and rename the files, or correct the component settings (/package/.../files/file). |
| M355 | WARNING | No 'FILECAT' Directory found for Component 'COMP' ('COMPID') for 'VENDOR' : 'MCU' ('COMPILER') | The directory specified for the file category was not found. Correct the information in the component settings (/package/components/.../component). |
| M358 | WARNING | Header File 'HFILE' for 'CFILE' missing for Component 'COMP' ('COMPID') for 'VENDOR' : 'MCU' ('COMPILER') | The header file defined for the component could not be found. Verify the header file settings (/package/.../files/file) or whether the file exists. |
| M359 | WARNING | Family has no Device(s) or Subfamilies: 'FAMILY' | The device family has no devices or subfamilies. Add the missing information (/package/devices/family). |
| M360 | WARNING | Subfamily has no Device(s): 'SUBFAMILY' | Add the missing information. Refer to /package/devices/family/subFamily. |
| M361 | WARNING | Generator ID in Taxonomy Cclass= 'CCLASS', Cgroup= 'CGROUP' is undefined: 'GENID' | The generator ID used in the taxonomy is not defined. Define or correct the generator ID (/package/taxonomy element). |
| M362 | WARNING | Not all Component Dependencies for Cclass= 'CCLASS', Cgroup= 'CGROUP', Csub= 'CSUB', Cversion= 'CVER', Capiversion= 'APIVER' can be resolved. RTE Model reports: 'MSG' | Some of the component dependencies could not be resolved. The message might contain additional information. Verify and correct component definition and dependency information. Refer to /package/components/.../component attribute condition. |
| M363 | WARNING | No API defined for Component Cclass= 'CCLASS', Cgroup= 'CGROUP', Csub= 'CSUB', Cversion= 'CVER', Capiversion= 'APIVER' | The package is missing the API information for the specified component. Refer to /package/apis. |
| M364 | WARNING | No Devices for Condition 'COND' available. | The specified condition refers to a device that does not exist. Define the device (/package/devices/family/../device) or correct the information for the condition (/package/conditions/condition). |
| M365 | ERROR | Redefined 'DEVTYPE' 'MCU' found, see Line LINE | Remove duplicate device/variant entries. Refer to /package/devices/family/../device. |
| M366 | ERROR | Redefined 'DEVTYPEEXIST' as 'DEVTYPE' 'MCU' found, see Line LINE | Device has been redefined as variant or vice versa. Remove duplicate device/variant entries. Refer to /package/devices/family/../device. |
| M367 | ERROR | Redefined 'TYPE' 'NAME' found, see Line 'LINE' | Remove duplicate device/variant entries. Refer to /package/devices/family/../device. |
| M369 | WARNING | Feature is already defined for 'DEVICE' and will be added, see Line 'LINE': 'FEATURE'. | This feature 'FEATURE' has been defined already on a higher level and as such it gets added to this 'DEVICE'. This is usually done when some devices have a higher number of basic features. Correct the feature (/package/devices/family/.../feature) if this is a typo. |
| M370 | WARNING | URL is not conformant: 'URL': Backslashes are not allowed in URL, use forward slashes. | Use standard URL notation using forward slashes (/). |
| M371 | ERROR | 'SECTION' Feature for 'MCU': 'FEATURE' unknown. | This feature 'FEATURE' is unknwon to the specified 'MCU'. Correct the feature (/package/devices/family/.../feature) if this is a typo. |
| M372 | ERROR | 'SECTION' Feature for 'MCU': 'FEATURE' misspelled, did you mean 'KNOWNFEATURE' ('DESCR'). | This feature 'FEATURE' resembles the feature 'KNOWNFEATURE'. Correct the feature (/package/devices/family/.../feature) if this is a typo. |
| M373 | ERROR | Unsupported Schema Version: 'VER'. | The schema version is not supported. Verify the attribute schemaVersion of the element /package. |
| M374 | ERROR | While checking Feature for 'MCU': Pname 'CPU' not found. | The processor could not be found for the specified device. Refer to /package/devices/family/../device and /package/devices/family/.../processor. |
| M375 | ERROR | 'path/pdsc_file': No <mountedDevice> for board 'BOARD' found. | If a board element does not contain a <mountedDevice> element, then the examples for this board are not shown and example projects may not appear in the development tools. Refer to /package/boards/board/mountedDevice of /package/boards. |
| M376 | ERROR | Schema Version not set! | Set a valid schema version in the PDSC file. Refer to schemaVersion attribute in the /package. |
| M377 | WARNING | File 'NAME' 'TYPE' must have 'attr="config"' | The category 'TYPE' of the file 'NAME' requires it to be defined as a configuration file. Add the attribute attr="config" to the <file> element that defines the file. Refer to /package/.../files/file. |
| M378 | WARNING | Component Cclass='CCLASS, Cgroup='CGROUP, Csub='CSUB', Cversion='CVER', implements the API defined in 'NAME' but does not attribute 'Capiversion' specifying the version it implements. | Add attribute Capiversion specifying the API version that is implemented in the component described in the message. Refer to /package/components/.../component. |
| M379 | WARNING | No example(s) found for Board '['VENDOR'] 'BOARD'. | There are no examples found for the board 'BOARD'. Provide examples. Refer to /package/examples/example. |
| M380 | WARNING | No description found for ['VENDOR'] 'MCU' | No description was found for the device 'MCU' from 'VENDOR'. Use description attribute to provide information about the device, its subfamily, or family. Refer to /package/devices/family/.../description. |
| M381 | WARNING | Vendor names are not equal: '['VENDOR'] 'MCU', MCU '['VENDOR2'] 'MCU2', see Line 'LINE' | Vendor name specified in the Dvendor attribute for the <mountedDevice> tag does not match the actual device vendor name. Verify and correct vendor name. Refer to /package/boards/board/mountedDevice. |
| M382 | WARNING | Requirement <'TAG'> '['VENDOR'] 'NAME' 'VER' could not be resolved.'MSG' | The package requires a package with name 'NAME' and version 'VER' from vendor 'VENDOR'. That package was not found. Verify the requirement. Use option -i to point to the required package. Refer to /package/requirements/packages. |
| M383 | ERROR | 'TAG' 'NAME' is not conformant to the pattern "'CHAR'" | Unsupported characters are found in the 'NAME' for the tag/attribute 'TAG'. Specify the name using only supported characters from 'CHAR'. |
| M384 | ERROR | Condition 'NAME': Direct or indirect recursion detected. Skipping condition while searching for 'NAME2' | Resolve recursion in condition 'NAME'. |
| M385 | INFO | Release date is empty. | In the <release> tag add attribute date with the release date. Refer to /package/releases/release. |
| M386 | WARNING | Release date is in future: 'RELEASEDATE' (today: 'TODAYDATE') | Set the date to the future. Refer to /package/releases/release. |
| M391 | WARNING | Redefined Item 'NAME': 'MSG | Multiple defitions of item 'NAME' are found. Use unique names for the items listed in the message 'MSG'. |
| M392 | ERROR | Redefined Device or Variant 'NAME': 'MSG' | Multiple defitions of device or variant 'NAME' are found. Use unique names for the devices listed in the message 'MSG'. Refer to /package/devices/family/../device and /package/devices/family/.../device/variant |
| M393 | WARNING | Package has development version 'RELEASEVER' | The package has development version specified in the version attribute. For release use only MAJOR, MINOR and PATCH sections as described in the CMSIS-pack version semantics. Also refer to /package/releases/release. |
| M394 | ERROR | Not Semantic Versioning: 'RELEASEVER' | Package version does not follow expected semantic versioning. Correct the value specified for the version attribute using correct semantic. Refer to /package/releases/release. |
| M395 | WARNING | Release date attribute is not set for release version: 'RELEASEVER' | Specify release date in the attribute date for the returned release version 'RELEASEVER'. Refer to /package/releases/release. |
| M396 | WARNING | Release 'TAG' not consecutive (newest first): 'RELEASEVER', 'RELEASEDATE' (prev.: 'LATESTVER', 'LATESTDATE', see Line 'LINE') | Package releases shall be entered in consecutive way: newest release version and latest date first. Rearrange the releases in the list or correct values for the returned 'TAG' attributes (version or date). Refer to /package/releases/release. |
| M397 | WARNING | File extension '.pdsc' must be lowercase: 'PATH' | The PDSC file shall have lowercase extension .pdsc <>Correct extension of the PDSC file 'PATH'. |
| M398 | ERROR | Attribute 'Dname' missing in expression using 'Pname="'NAME'" | When using attribute Pname in the <condition> element the Dname attribue shall be present as well. Add attribute token{Dname} specifying the device name. Refer to /package/conditions/condition. |
| M399 | WARNING | Attribute 'TAG' is ignored, because 'TAG2' + 'TAG3' is specified | Deprecated attribute 'TAG' is ignored because newer attributes are found. Triggered for id attribute in the /package/devices/family/.../memory element when name or access attributes are present as well. remove deprecated attribute 'TAG' |
| M400 | ERROR | Either attribute 'TAG' or 'TAG2' + 'TAG3' must be specified for 'memory' | <memory> element requires that either attribute id or attributes name and access are specified, but none of those were found. Specify the expected attributes. Refer to /package/devices/family/.../memory. |
| M401 | ERROR | Attribute 'TAG' missing on 'TAG2' | Element 'TAG2' requires attribute 'TAG', but it was not found. Add missing attribute. |
| M402 | ERROR | Attribute 'TAG' missing on 'TAG2' (when 'TAG3' is specified) | Add missing attribute 'TAG' or remove the attribute 'TAG3' in the element 'TAG2'. |
| M403 | ERROR | Redefinition of 'TAG' : 'NAME', see Line 'LINE' | Remove the redefinition of element 'TAG' with name 'NAME'. |
| M404 | WARNING | No 'TAG' found for device 'NAME' | Element 'TAG' is missing for device 'NAME'. Add missing element. |
| Message Number | Type | Message Text | Action |
|---|---|---|---|
| M500 | TEXT | RTE Model reports: 'MSG' | Error while preparing data. See massage for more details. |
| M502 | TEXT | RTE Model reports: #error 'NUM': 'NAME' : 'MSG' | Additional software components required. |
| M504 | TEXT | RTE Model reports: MISSING: – SPACE NAME | Add the missing component. |


\hyphenation{words}
The \hyphenation command declares allowed hyphenation points, where words is a list of words, separated by spaces, in which each hyphenation point is indicated by a - character. For example
\hyphenation{fortran er-go-no-mic}
indicates that "fortran" cannot be hyphenated and indicates allowed hyphenation points for "ergonomic".
This argument to this command should contain words composed only of normal letters. To suggest hyphenation points for strings containing nonletters or accented letters, use the \- command in the input text.
This command is normally given in the preamble.
See also Line and Page Breaking
Go to LaTeX Table of Contents


@ApplicationScoped
@Path(value="customers")
@Produces(value="application/json")
@Consumes(value="application/json")
public class CustomerResource
extends java.lang.Object
| Constructor and Description |
|---|
CustomerResource() |
| Modifier and Type | Method and Description |
|---|---|
javax.ws.rs.core.Response |
create(Customer customer)
Allows for the creation of a Customer object on the database, using the
Customer object passed in as a parameter.
|
javax.ws.rs.core.Response |
delete(java.lang.String id)
Allows for the deletion of a Customer object on the database, using the
Customer object passed in as a parameter, and the id parameter to identify which
Customer needs to be deleted.
|
javax.ws.rs.core.Response |
getAll()
Gets a handle on all of the Customer objects that exist in the database and
returns them in a list in JSON format.
|
javax.ws.rs.core.Response |
getCustomer(java.lang.String id)
Gets a handle on the Customer object, if one exists with the given id that
is passed in as a parameter.
|
javax.ws.rs.core.Response |
update(java.lang.String id,
Customer customer)
Allows an existing Customer object to be modified.
|
@GET public javax.ws.rs.core.Response getAll()
@GET @Path(value="{id}") public javax.ws.rs.core.Response getCustomer(@PathParam(value="id") java.lang.String id)
id,
- the id of the Customer object that is to be returned.@PUT @Path(value="{id}") public javax.ws.rs.core.Response update(@PathParam(value="id") java.lang.String id, Customer customer)
id,
- the id of the Customer object to be modified.customer,
- the new Customer object with the updated information.@POST public javax.ws.rs.core.Response create(Customer customer)
customer,
- the Customer object to be created.@DELETE @Path(value="{id}") public javax.ws.rs.core.Response delete(@PathParam(value="id") java.lang.String id)
id,
- the id of the Customer object to be deleted.


HTML Elements
| Element | Description | Block, Inline or N/A | Container or Empty |
|---|---|---|---|
| <!-- --> | HTML Comments tag is used to insert comments in the source code but not displayed in the browsers. | N/A | Container |
| <!DOCTYPE> | It's not an HTML tag but it's the very first thing in HTML document, so that the browser knows what type of document to expect. | N/A | Empty |
| <a> | It is a hyperlink which is used to link from one page to another. | Inline | Container |
| <article> | It is a self-contained content which can contain entire blog posts, news articles and similar content. | Block | Container |


Before Change
def postprocess_buffer(self, buffers, len):
adv_centered = \
buffers["advantage"][:len] \
- buffers["advantage"][:len].mean(axis=0)
adv_std = buffers["advantage"][:len].std(axis=0)
buffers["advantage"][:len] = adv_centered / (adv_std + 1e-6)
def train(self, batch, **kwargs):
After Change
def postprocess_buffer(self, buffers, len):
adv = buffers["advantage"][:len]
adv = (adv - adv.mean(axis=0)) / (adv.std(axis=0) + 1e-8)
buffers["advantage"][:len] = adv
def train(self, batch, **kwargs):
(states_t, actions_t, returns_t, states_tp1, done_t,


See what we want to say ..
Breakfast is the most important meal of the day so you should make the most of what you eat when you first wake up. Aim to have your first meal within an hour of waking up. A great way to ensure you get the most out of your breakfast is to have a meal that is packed with protein and superfoods to give you tons of energy for the day.
Learn how to clean up your diet in 5 Ways
Eating Healthy When Going Out
Learn how to make a Healthy Dog Food Recipe ....
Starting your own business as a holistic health coach is vastly different from the typical nine-to- five job. It can be a bit overwhelming at first, but once you settle into a routine it can be one of the most rewarding careers ....
Learn how to make a Cauliflower Hummus Pizza ....
Learn the most successful tips in achieving natural weight loss ....
How to make smoked salmon nori wrap in simple steps ....
One of the main questions I get from clients is how to cook and bake healthier. These cookies are a fresh take on that homemade banana bread that my mom baked when I was growing up. They are gluten, dairy free, vegan and best of all ....
Intuitive eating is an approach that bridges the connection between the food you eat, and your mind and body.  It’s one of the best ways to separate physical from emotional feelings and signals and help you foster and build body intuition. It also helps you finally let go of addictions to foods ....
Thursday…I got invited to fly down to the Bahamas and spend the weekend learning from some of the most brilliant entrepreneurs, coaches and CEOs. Initially, I had a million reasons why I couldn’t go.
Almost everyone is aware of the dangers of the sun and the risks of skin cancer. We’re given the statistics, and it makes us want to protect ourselves. With the rise of skin cancer and protection from the sun, the use of sunscreen has also risen. It probably hasn’t even occurred to most of us that the very thing we are using to protect ourselves from the sun’s rays may also be harmful ....
Happy Earth Day! Although every day should be a day that we are thinking about how our life and actions can improve the wellbeing of our planet, this is a special day dedicated to doing just that! Earth Day is also a perfect opportunity to simply raise awareness for how much our planet needs us to thrive.
Why is it important? Well, much like our bodies, if we don’t take care of our environment, then it can no longer provide for us ....
continue reading
With spring comes new produce that's now in season, and we get inspiration for new recipes to freshen and rejuvenate our diet. It's so lovely! I love this salad recipe because of the light, delicate flavors it brings. Unlike most salad recipes, it also features mostly vegetables, without a ton of unhealthy, processed toppings. One of my favorite ingredients in particular is the yummy cabbage that makes the base of the salad.
Cabbage is a low calorie, high nutrient density food- meaning that you can get more "bang for your buck" in terms of health. It's a good source of Vitamin K (which is essential for proper blood clotting), Vitamin C (which helps you fight sickness), energy-boosting Vitamin B6, and many more vitamins and minerals. It's also known to help decrease the risk of cancer and other illnesses.
This Chinese Chicken Salad recipe is a great way to enjoy the delicate flavor of cabbage, mixed with a yummy ginger dressing and a little protein from fresh grilled chicken. Enjoy!!


Hello extensionizr!
To shut this popup down, edit the manifest file and remove the "default popup" key. To edit it, just edit ext/browser_action/browser_action.html. The CSS is there, too.
To shut this popup down, edit the manifest file and remove the "default popup" key. To edit it, just edit ext/browser_action/browser_action.html. The CSS is there, too.


Begin here
friendly console
Why import *?
import *
IDLE
Mu
Other consoles
Editors and Notebooks
Thoughts on design
Use in your project
Contribute
All the tracebacks!
En français