text:
Clery Act/Crime Stats
Jeanne Clery Disclosure of Campus Security Policyand Campus Crime Statistics Act Report1.Background
2.Reporting Crime
3.Confidential Reporting of Crime
4.Response To Crime
5.Timely Warnings
6.Preparing Annual Disclosure Report
7.Notification and Availability of the Report
8.Fire Safety Report and Fire Log
9.Enforcement and Arrest Authority of University Police
10.Working Relationship between University, State, and Local Police Agencies
11.Access to Campus Facilities and Residence Halls
12.Security Considerations Used in Maintenance
13.Sex Offense Procedures
14.Crime Prevention Programs
15.Drug and Alcohol Abuse Education Programs
16.Possession, Use, and Sale of Alcohol Beverages and Illegal Drugs
17.Sex Offender Information
18.Monitoring of Criminal Activity by Students Off Campus
19.Emergency Notification and Response Procedures
20.Missing Residential Student Notification Policy and Procedures
21.Daily Crime Log
The Jeanne Clery Disclosure of Campus Security Policy and Campus Crime Statistics Act (hereafter the Act) requires post-secondary educational institutions that receive federal funding to publish a disclosure report (hereafter the report) annually. Southern Polytechnic State University is committed to the safety of the university community and to compliance with the Act. The following procedures are established to help promote the safety of our community and to ensure proper disclosure of statistics and polices required by the Act. This Act also meets the Higher Education Act Institutional Disclosure Requirements.
1. Crimes and other emergencies should be reported accurately and promptly to the University Police by telephoning 678-915-5555, by appearing in person at department headquarters located on the ground floor of Norton Hall Building R2, or by stopping an officer on patrol and making a report.
2. University counselors shall, when they deem it appropriate, notify patients who have been the victims of crime how to report crime.
3. If other university personnel are made aware of crimes occurring on campus, they shall promptly report it to the University Police.
4. No person shall dissuade a crime victim from reporting a crime to the proper authorities.
Confidential Reporting of Crime
1. Georgia is an open records state, and all reports are generally open to public inspection after the completion of the investigation pursuant to O.C.G.A 50-18-70.
2. The university will respect confidentiality in accordance with the exceptions to the open records law but has no special provisions for confidential reporting of crimes.
3. This policy does not prohibit university counselors from maintaining confidentiality in accordance with the ethical discharge of their responsibility.
1. The University Police shall promptly investigate all crime reports. Persons found in violation of the law are subject to arrest and prosecution.
2. The University Police shall assist all persons in prosecuting crimes committed against them where sufficient evidence exists and shall apprise all victims of the appropriate prosecutorial processes available to them.
3. A daily log of crime reports shall be maintained at police headquarters in accordance with the provisions of the Act. The log shall be open for public inspection during normal business hours.
4. Minor offenses against public order may, at the discretion of the University Police, be referred to the campus judicial program in lieu of criminal prosecution where the offense lacks a particular victim or the victim declines prosecution.
A timely warning notice is considered for distribution to the SPSU community for all Clery Act crimes that are:
1. Reported to the Police Department.
2. Determined by the University to represent a serious or continuing threat to students and employees.
The decision to issue a timely warning shall be decided on a case-by-case basis. The decision to issue is made by the Chief of Police, who considers all known facts, including whether the crime is to be a serious or continuing threat to students and employees. Certain information may be withheld from a warning if there is a risk of compromising law enforcement efforts. If a crime occurs that would pose a serious or continuing threat to the SPSU Community, a timely warning notice will be issued to the campus community. Timely warning notices are issued through an Emergency Public Broadcast System, Hornet Alert/RaveMobile Safety and/or SPSU Campus Wide Email.
Preparing the Annual Disclosure Report
1. The University Police Chief shall be responsible for preparing the annual disclosure report in accordance with university policy and procedure 411.0.
2. The report shall contain the policy statements required by the Act.
3. The report shall contain the crime statistics and disciplinary referral statistics required by the Act.
4. The crime statistics shall be compiled by the University Police Chief in accordance with the Federal Bureau of Investigation's Uniform Crime Reporting Program.
5. The disciplinary referral statistics shall be reported annually by campus security authorities (defined below) to the University Police Chief.
6. The following definitions are adopted for the purpose of complying with the Act:
a. A crime is reported when a victim or witness brings it to the attention of the University Police or a campus security authority.
b. Campus security authorities are university officials who have significant responsibility for student and campus activities, including, but not limited to, student housing, student discipline, and campus judicial proceedings. These include but are not limited to the Dean of Students, Director of Residence Life, Director of Student Activities, and Athletic Coaches.
c. On campus means any building or property owned or controlled by Southern Polytechnic State University within the same reasonably contiguous geographic area used by the institution in direct support or in a manner related to the institutions educational purposes.
d. Applicable non-campus buildings or property does not apply to Southern Polytechnic State University because there are not any non-campus buildings or property.
e. Applicable Public Property means the street and sidewalks of the 1100 block of South Marietta Parkway, Marietta, GA.
Notification and Availability of the Report
1. The report and statement of policies regarding this Act shall be published electronically on the University Police website http://police.spsu.edu on or before October 1st of each year.
2. Current and prospective students shall be notified of the report by including the notification statement in the student handbook and semester registration booklet. The Director of Records shall also notify current students by e-mailing the notification statement to them prior to the date specified by the Act.
3. The Director of Human Resources shall notify current employees of the report by including the notification statement with all payroll checks and advices prior to the date specified by the Act.
4. The Director of Human Resources shall notify all prospective employees of the report by including the notification statement with all out going employment applications.
5. Printed copies of the report shall be available at police headquarters.
Fire Safety Report and Fire Log
This report contains information related to fire safety issues experienced inside campus housing on the campus of Southern Polytechnic State University. These records are made available in accordance with the requirements of the Higher Education Opportunity Act of 2008. The SPSU Police creates this report annually, relying on police reports and information provided by SPSU Housing.
The SPSU Police Department maintains the fire log, and reports fire statistics annually in conjunction with the "Annual Security Report". This report provides information in compliance with the Jeanne Clery Disclosure of Campus Security Policy and Campus Security Crime Statistics Act. The report will be located on the University Police Website; http://spsu.edu/police alongside the Clery Crime on Campus Report. A paper copy of the Fire Safety Report and Fire Log are available upon request to the University Police in Norton Hall Building R2.
Enforcement and Arrest Authority of University Police
Official Code of Georgia Annotated 20-3-72:
The campus policemen and other security personnel of the university system who are regular employees of the system shall have the power to make arrests for offenses committed upon any property under the jurisdiction of the board of regents and for offenses committed upon any public or private property within 500 yards of any property under the jurisdiction of the board.
Working Relationship between University, State, and Local Police Agencies
The Georgia Bureau of Investigation is a state agency which provides assistance to law enforcement departments statewide, including investigative and crime scene processing services. The University Police relies on assistance from the GBI when necessary.
Neither the Marietta City Police nor the Cobb County Police have responsibility for crime on the SPSU campus; however, both agencies have a long history of assisting and cooperating with the university.
County sheriffs in Georgia are state constitutional officers and as such have state wide jurisdiction, including jurisdiction on state campuses. The Cobb County Sheriff's Department does not generally engage in routine law enforcement activities on the SPSU campus. They do, however, serve court papers, warrants, and other judicial documents to persons on campus when applicable. They also provide assistance to the University Police, including crime scene processing and other services as requested.
Access to Campus Facilities and Residence Halls
1. Facilities
As a public institution, the majority of university buildings and grounds are accessible to the general public during normal business hours. The use of some facilities – The Recreation and Wellness Center, certain areas within the Johnson Library, classrooms, labs, residence halls, athletic facilities and fields, certain areas within the Wilson Student Center – is restricted to SPSU faculty, staff, and students or others who have obtained permission through the office of scheduling and logistics to use the facilities.
O.C.G.A. 16-11-35 provides that persons without legitimate business on campus who act to interfere with the peaceful activities of the campus may be asked to leave. If they refuse to leave, they may be arrested and removed.
2. Residence Halls
The exterior doors to the residence halls are locked. Residents and relevant university personnel are issued keys. University police officers conduct periodic patrols inside the residence halls.
All members of the residence hall community have the responsibility to help secure the community's welfare by ensuring their visitors comply with university regulations, by keeping the external doors closed and by reporting suspicious persons to the university police or housing staff.
3. Apartments
Each apartment resident is responsible for keeping his or her apartment door locked. The university police conduct patrols of the grounds.
Security Considerations Used in Maintenance
The Department of Facilities Management maintains and operates buildings and grounds with a concern for safety, security, and crime prevention. Any person may submit a security related maintenance request to the work order desk at 678-915-7437 or by using the online work order system. If a security related maintenance problem is detected after hours, the university police should be notified. Facilities personnel are on call all hours and will respond when necessary to repair security related problems.
The prompt reporting of sex offenses to the University Police is encouraged. Further assistance can be obtained from the Counseling Office, Campus Nurse, University Housing personnel, or the Dean of Students. Additionally, the Cobb County YWCA operates a 24-hour hotline for information, counseling, and crisis intervention; the phone number is 770-427-3390.
The University Police will vigorously investigate all reports of sex offenses occurring on campus and will help victims of sex offenses occurring off campus contact the appropriate law enforcement authorities.
A complete statement of the university's sex offense policies is contained in the Student Handbook.
The following information is provided for sex offense victims:
The Importance of Evidence Preservation
Preserving evidence is critical to the proper identification and prosecution of suspects.
- An assault victim should not shower, dispose of clothing, or disturb the scene of the crime in any way.
- The police should be called immediately. Any delay in reporting could result in the destruction of evidence
- The victim should have a medical examination and should allow the appropriate evidence to be gathered.
Change in Residence and Academic Situations for Victims
After campus sexual assaults have been reported, the victims of such crimes shall have the right to require that campus personnel take the necessary steps or actions reasonably feasible to prevent any unnecessary or unwanted contact or proximity with alleged assailants, including immediate relocation of the victim to safe and secure alternative housing and transfer of classes if requested by the victim.
Student Disciplinary System
Victims of on-campus sexual assault have the same right to legal assistance, or ability
to have others present, in any campus disciplinary proceeding that the institution
permits to the accused; and the right to be notified of the outcome of such proceeding.
Disciplinary sanctions include probation, suspension,
and expulsion.
The University Police conduct crime prevention/awareness programs. The programs are open to all members of the university community. The programs contain information about personal safety, rape awareness, vehicle security measures, general crime prevention advice, university security measures, the hazards of alcohol and drug abuse, and the most common types of offenses occurring on campus. Special programs are also available that are designed to educate members of the university community about acquaintance rape and help them identify ways to reduce the risk of becoming the victim of acquaintance rape. These programs are available by request almost any time.
Drug and Alcohol Abuse Education Programs
The Department of Recreation Sports and Athletics Coordinator of Health Protection/Wellness sponsors annual programming for drug and alcohol abuse education. The topics vary each year and have employed group discussions, guest lecturers, and demonstrations to raise student awareness.
Possession, Use, and Sale of Alcohol Beverages and Illegal Drugs
Southern Polytechnic State University is committed to operating in accordance with the laws of the state of Georgia in regard to the use, sale, possession and consumption of an alcoholic beverage.
Southern Polytechnic State University is in compliance with section 1213 of the Higher Education Act of 1965 regarding the possession, use and sale of alcoholic beverages and illegal drugs. Any violation of the act or of federal and state laws pertaining to the possession, use and sale of alcoholic beverages and illegal drugs can be dealt with through the criminal justice system and/or referral to the student disciplinary system.
Law enforcement agency information provided by the State of Georgia concerning registered sex offenders may be obtained by clicking on the Georgia Sex Offender Registry link on the University Police website http://police.spsu.edu or the direct link to the website is http://gbi.georgia.gov/00/channel_modifieddate/0,2096,67862954_87983024,00.html
Monitoring of Criminal Activity by Students Off Campus
The university does not monitor the criminal activity of students off campus.
Emergency Notification and Response Procedures
To promote the safety of the population of the Southern Polytechnic State University an early warning system has been established. Through the use of this multi-faceted Emergency Broadcast System, early warnings will be broadcasted by the University Police concerning life threatening emergencies on or near the campus.
In event of a major emergency, the Police Officer-in Charge will then notify the Chief of Police and the Captain of Police Operations. The Police Chief, Captain of Police Operations, or Police Officer-in-Charge, shall then declare a major emergency. This declaration is not necessary in event that a National Weather Service Warning has been issued. The Police Dispatcher should, without delay, begin message protocol after receiving any NWS broadcasted warning or a weather-related emergency siren alert. In addition, if a campus emergency is declared by the University President, the on-duty Police Officer-in-Charge shall instruct the Police Dispatcher to broadcast an emergency message, also without delay.
The Southern Polytechnic State University Police will, without delay, and taking into account the safety of the community, determine the content of the notification and initiate the notification system, unless the notification will compromise efforts to assist victims, respond to, and mitigate the emergency.
Notifications of emergencies are made to the University Police through telephone calls, burglary or fire alarms, emergency call box notifications, calls from neighboring jurisdictions, etc. The University Police Communications Center (Police Dispatch) will notify the Police Officer-in Charge, without delay, of any emergency call. The Police Officer in charge will initiate an immediate investigation into the legitimacy of the call. A major emergency shall be defined as any emergency situation which poses an imminent danger of injury or loss of life to any member of the campus community. This shall include but not be limited to National Weather Service Severe Weather Warnings (Severe Thunderstorm Warning with a Tornado Watch), National Weather Service Tornado Warnings, a Crime in Progress with potential violence (such as an active shooter, armed robbery, etc.), Fire, Explosion, Major Hazardous Material Spill, Earthquake, or Flooding.
Emergency notification is carried out by University Police emergency personnel as described in above procedures. In addition, the University President and members of the University Public Relations Department may initiate emergency messaging.
In event of a large scale emergency, notifications will be made by police radio and or telephone to all surrounding jurisdictions. This notification will be made to the City of Marietta and Cobb County through notification to the Cobb-Marietta 911 Center.
The Southern Polytechnic State University employs five types of campus emergency notification. A Fire Alarm System with all campus housing facilities having smoke detectors and audible alarms, Emergency Public Broadcast System (Spoken or Push-button Pre-recorded Message through the Public Address speakers in all buildings and all Emergency Call Boxes), Hornet Alert / RaveMobile Safety (Telephone, cell-phone and email messages), SPSU campus-wide email and Cobb County Emergency Siren System (activated by Cobb County Emergency Management Agency).
Notification systems are tested at least once annually. The Cobb County Emergency Siren is tested at noon the first Wednesday of each month. Drills and other exercises will be conducted annually with campus notification of said drills made through the University Public Relations Department.
In addition, an Emergency Procedures and Safety Information Pamphlet was produced in 2009 and distributed to all faculty and staff and some students. Copies of the Emergency Procedures and Safety Information Pamphlet are also available from the University Police or Housing Office. This pamphlet contains safety information related to Emergency Telephone Numbers of the University Police, Evacuation Procedures, Shelter in Place Procedures, Medical Emergencies, Tornado or Severe Weather Warning, Fire, Explosion, Tornado Strike or other Building Damage, Hazardous Materials, Psychological Crisis or Suicide Threat, Utility Failure, Flooding or Water Damage and Crime Prevention Tips. A copy of the Emergency Procedures and Safety Information Pamphlet has been placed on the University Police Website http://police.spsu.edu
Missing Residential Student Notification Policy and Procedures
Southern Polytechnic State University's policy regarding missing residential student notification has been placed on the University Police website http://police.spsu.edu
Consistent with Clery Act requirements, the SPSU Police maintains a Daily Crime Log. The Daily Crime Log includes the nature, date, time and general location of each crime reported to the department, as well as it's disposition. The department updates the Daily Crime Log daily, and in accordance with the Clery Act requirements. In rare instances reported duty maybe excluded from the log, particularly in those instances, in which inclusions may compromise an ongoing investigation. Limited information may be temporarily withheld if it could jeopardize an ongoing investigation or the safety of an individual; if the disclosure is prohibited by law; or if the disclosure would compromise the confidentiality of the victim.


text:
Just started your job here at MCC? Begin by completing your online training by going through each of the links below. Then you will be ready to do your job efficiently and safely.
People Places Things
Get Connected
Hiring Essentials
About MCC
Next Steps
General Information
Computer Applications
Safety & Wellness
Emergency Preparedness
College Speak
Rules to Work By
Public Employee Requirements
Employee Giving
Supervision @ MCC
Additional Learning
mesacc.edu | 480-461-7000 | © 2015 Mesa Community College | A Maricopa Community College The Maricopa County Community College District is an EEO/AA institution and an equal opportunity employer of protected veterans and individuals with disabilities.

subset: commoncrawl


text:
Comments about 'Feds release updated guidelines for medical exams in sex assault cases'
- Oldest first
- Newest first
- Most recommended
Login to comment
DeseretNews.com encourages a civil dialogue among its readers. We welcome your thoughtful comments.
— About comments
What You May Have Missed
Most Popular
Across Site
In Utah
- Which U.S. cities are the best for upward...
- Jury orders Siegfried and Jensen to pay...
- IRS commits to not target tax-exempt status...
- LDS Church relationship with Boy Scouts in...
- Motley Crue concert delayed about two hours...
- Wanted Layton man dies in New Mexico plane crash
- Imagine Dragons treated like home team at...
- What consumers need to know about chip...
Most Commented
Across Site
In Utah
- LDS Church relationship with Boy Scouts... 300
- Boy Scouts in Utah, nation face... 141
- LDS Church 're-evaluating' Scouting... 107
- Profane and acclaimed: 'The Book of... 77
- Most Utahns oppose Supreme Court ruling... 68
- Lee takes on new strategy in fight... 45
- IRS commits to not target tax-exempt... 42
- Is report on building prison in Draper... 36


text:
More on Moore here from AW: http://www.profootball24x7.com/break...3&view=archive
Printable View
More on Moore here from AW: http://www.profootball24x7.com/break...3&view=archive
From Scout.com and Aaron Wilson:
Looks like this team is commited to solving the problems, now just start MA tommorow and we will be set.Quote:
OWINGS MILLS -- The Baltimore Ravens cut imposing wide receiver Clarence Moore on Saturday, parting ways with a former sixth-round draft pick who was inactive for three of the first five games. Linebacker Dennis Haley was immediately promoted from the practice squad to take Moore's place on the active roster
Im stoked for some more PT for Demetrius Williams. :thumbup:
You beat me by a minute Tony!
Whats cool is on this board threads can be merged.
Moore deserved it. He alligator armed his way out of here. The INT in the end zone at the end of the half vs. Denver was as much his fault as it was McNair's. He has six inches on Bailey, and could have cut right in front of him. Instead he let Bailey get position (on an underthrown ball) and didn't put up any sort of fight for the ball.
Too bad. The guy has great tools. He just can't get it done cause he lacks the heart. Hopefully he can pull it together somewhere else cause he could definitely be serviceable or better.
How long before the Vikings call?
I never cheer when a Raven fails and gets cut, but this is a positive in that our FO and Billick have learned to call a mistake a mistake and move on. When's the last time we gave up on a guy and cut him? I can't recall us ever cutting a guy midseason for non-performance and I think this is a good thing.
But why do we need another LB?
Adding Dennis Haley to the 53 man roster is probably more for depth since Mike Smith has been on the injury report as questionable with a concussion
Good news. Clarence had such potential, but he's lacking one thing: heart. I'm excited to see Demetrius get some more PT.
I'm not crazy about the Haley move, though. I'd be a bit more interested to see them go after an O-lineman in FA or a trade to fill that spot.
I guess they are really impressed with Haley; I bet they are moving him up to gaurantee that he will remain a Raven.
Moore has potential, but those alligator arms did him no justice. Was he a Florida Gator??:bag: ..:grbac: I liked him and I think if that throw would have been a bit higher, he would have caught it....Not taking anything away from McNair, but Boller makes that throw..:nerd: Boller has a very nice angle on that fade jump ball:thumbup:
Moore is gone??!!!?????!!!
"No Moore"
:nm: :taz: :taz: :taz:
I'm soooo sad :261695:
Let us wish Clarence well in his life endeavors and turn our attention to the job at hand. Onward and forward.
I don't think it was he didn't have the heart, it was more like he didn't have the aggressiveness & meanness to succeed at his position. Good luck to Clarence as he moves on, a too nice guy.
I don't think him not catching that ball is entirely why he's gone.Quote:
I liked him and I think if that throw would have been a bit higher, he would have caught it....Not taking anything away from McNair, but Boller makes that throw.. Boller has a very nice angle on that fade jump ball.
Him letting Champ Bailey catch the ball like he was actually the intended receiver is why I think he's gone.
The play call in itself was pretty stupid IMO to begin with since it's the only play Moore sees the field to begin with, but that's another discussion.
The fact that he did absolutely nothing to try and prevent the INT. or fight for the ball is why he's gone.
You simply cannot let that be an INT. and loose the minimum 3 point field goal in that situation.
Either catch the ball, knock it out of the way or commit offensive pass interference.
Anything to preserve possession!!
He did nothing but jump up and hope the ball was going to be there.
If he hasn't gotten down the fundamentals of playing the receiver position in the only situation he is called upon to perform, then he never will.:hammer:
Don't know anything about the Haley kid, but linebacker is not as big of need as other poisitions are right now regarding depth.
I can only assume and hope that he's a special teams guy that's being brought in to fill in for an ailing Corey Ivy and Gary Stills.
yeah he should have tried harder to knock it down, but if this ball is thrown properly even champ bailey has no chance........
Rack Fanatic! Hell, even when we were kids playing sandlot ball...when a defender got in front of us and we saw that the pass was short, we jumped up and bear hugged the defender, pinning his arms to his side so he couldn't catch the ball.Quote:
Either catch the ball, knock it out of the way or commit offensive pass interference.
Anything to preserve possession!!
McNair took three steps back and launched the ball in Moores general direction.
Moore had no balls to start with, and his off season surgery to have a pair attached was obviously a failure.
The positive is that Moore is still young enough to return to college and choose another profession. I wish Moore the best, but he just does not have it for NFL football. Now, he could always go CFL.
As for where we go, I am excited that this means more playing time for Demetrius, but could this mean that another WR is coming in to take the 4th slot? (Charles Rogers? Randy Moss? *nah on Moss*)
Hope not to start a conspiracy theory -- but this is so unlike Billick and the coaching staff based on the last couple of years of behavior.
Wonder if Bisciotti got involved in any way?
Aaron this is where you can help us out!!
I can't help but feel a little sorry for the guy. He was supposed to be the next great thing at WR. But then I remember how he played...hope some CFL team takes a look at you Clarence!
The only issue I have with this move is promoting a LB to take his spot. Granted, we had inactive WRs, but I get the feeling the active spot will be filled by Haley, and not the man who SHOULD be active...Dan Cody!
As for signing a WR, I'd say we'll either grab Travis LaTenderesse and stash him on the P Sq, or go for a WR recently cut in the 53 man cutdown. Charles Rogers is a remote possibility.


text:
Nokia board chairman Risto Siilasmaa said on a Finnish television show that the company has a contingency plan just in case the company has troubled winning adoption for its Windows Phone-based devices.
Speaking on a program broadcast on Finnish national broadcaster Yle, he reportedly said that the company is confident that Windows Phone 8 will be successful but that the company has a back-up plan in case something should go awry. He didn't specify what that plan includes although a reasonable guess would be that the company would follow the crowd and adopt Android.
He also expressed confidence in Nokia CEO Stephen Elop.
"He came in at a tough time," Siilasmaa reportedly said, adding that Elop's management style had been "good and transparent."
NOK is up 5 cents, or 2.4%, to $2.12.


text:
All is well today in our little townhouse in Springfield. I settled on a cake and ice cream to make for my dad, made them last night, and I think both are going to be really good. Recipes to come!
All is well today because the house smells like more of my crock pottery. That's the term I use for my crock pot cookery. I've been doing more experimenting lately with my slow cooker and it's been fun.
The next thing I want to make in it is short ribs, so if you have any good recipes let me know. I've never, ever made short ribs before. I hadn't even tasted a short rib until I went to Daniel.
Now I can't stop dreaming about short ribs. That short rib I had was amaaazing... I'm guessing they didn't use a crock pot to cook it. Anyway, I'm craving short ribs. I want them now.
Sometimes I get really strong cravings for goat cheese. I wouldn't even say that I love goat cheese or anything... it's okay... it's not my favorite though. But every once in a while I have to have it.
Do you know what I'm talking about? Is it just me? Maybe it is.
I sprinkle it on soups, on breads, on pasta, on eggs, on salads. It's so goaty and funky and creamy and delicious.
Goat cheese reminds me of France and the trip I took with my dad (Happy Birthday, Dad!). We had dinner outside at a little cafe and I had a goat cheese salad, roasted chicken, and a big glass of beaujolais nouveau... and I wasn't even twenty-one yet! That was fun.
That's not much of a story for you, I'm sorry. Goat cheese=France. That's all.
So I guess you could say this recipe is French inspired - I think of pear, thyme, lemon, hazelnut and goat cheese as being French flavors. I used these flavors together to create a sweet and savory recipe.
I made a jam with pear, olive oil, onion, golden raisins, honey, thyme, lemon juice and zest, and used it to spread on some biscuits I made. The biscuits are buttery and rich with goat cheese and toasted hazelnuts.
Make! Enjoy! Pretend you're sitting at a cafe by the Seine while you eat these biscuits and jam.
The woman with the golden pear jam
1 tablespoon olive oil
3 cups finely chopped peeled pear
2/3 cup finely chopped yellow onion
1/4 cup golden raisins
1/4 cup honey
3/4 teaspoon crushed dried thyme leaves
1/4 teaspoon salt
2 tablespoons fresh lemon juice + 1/2 teaspoon finely grated zest
4 teaspoons cornstarch
1 1/4 cups all purpose flour
3/4 cup whole wheat flour (substitute all purpose, if desired)
2 tablespoons granulated sugar
2 1/4 teaspoons baking powder
1 teaspoon baking soda
1/2 teaspoon salt
1/2 cup finely chopped hazelnuts, toasted
8 tablespoons cold unsalted butter, cut into small pieces
3/4 cup crumbled goat cheese
1 large egg
1/3 cup buttermilk
Heat oven to 375 degrees F. Coat a large sheet pan with cooking spray.
Heat olive oil in a large nonstick skillet over medium heat; stir in pear and onion, and cook 15 minutes, stirring frequently, until softened and tender. Stir in raisins, honey, thyme and 1/4 teaspoon salt until combined. In a small bowl, whisk together lemon juice, lemon zest and cornstarch until well combined; stir mixture into skillet until combined. Cook pear mixture for an additional 5 minutes or until thickened and bubbly. Transfer pear jam to a serving dish and set aside.
In a large mixing bowl, sift together flours, sugar, baking powder, baking soda and salt; whisk in hazelnuts until combined. Knead in butter using two forks or a pastry blender, until butter is well incorporated and mixture starts to clump together; stir in goat cheese until combined. In a large mixing bowl, whisk together egg and buttermilk until well combined. Stir dry ingredients into egg mixture until just combined and a soft dough forms – do not overmix!
Take about 1/4 cup of dough and shape into a ball; place on cookie sheet and flatten slightly to a 1/2-inch thickness. Repeat process with remaining dough. Bake 15-17 minutes or until well risen and golden brown. Serve warm biscuits with jam.
Makes 10 biscuits


text:
Thanks for stopping by and browsing thru! This is still a work in progress, but I hope to have it running in full soon! I will be adding patterns shortly, some are free, some to buy. The patterns will be PDFs, so you will need to have Adobe Reader to open them.
I will be adding photos of some of my designs soon, but not all them have patterns available at the moment. I'm working on it! lol
I hope you will enjoy this site as I get it up and going, and I hope you will send me some feedback, suggestions, and pointers, too!
If you're interested in having something made up for you, talk to me! Let's see what we can do!
Thanks for stopping by!


text:
Accessibility tools
Service tools
Language selector
Navigation path
On 30 May 2012, the European Commission adopted its second annual set of policy recommendations to the 27 Member States, and to the euro area as a whole.
On this occasion, José Manuel Barroso, President of the EC, gave a speech at the European Commission in Brussels to present those recommendations which are based on a detailed assessment of the economic, employment and budgetary situation and policies in each country.
Where required, the Commission will spell out further budgetary steps, structural reforms and growth-enhancing measures which Member States should adopt over the following 12 months. The recommendations are to be endorsed by the European Council on 28-29 June 2012 and formally adopted by the Council in July 2012.
The presentation of the Country-Specific Recommendations is a key moment in the "European Semester" of economic policy coordination., Taking the EU's growth strategy as a starting point, the Commission sets out every year Europe's economic policy priorities in the so-called "Annual Growth Survey". The priorities presented in the 2012 Annual Growth Survey, adopted on 23 November 2011, were endorsed by the European Council on 1 March 2012. On that basis, the Member States submitted in April their medium-term budgetary plans and the structural reform measures planned for the following 12 months. The Country-Specific Recommendations are the Commission's response to these. The presentation of the results of the in-depth reviews of 12 Member States is the next step in the Macroeconomic Imbalances Procedure, following the Alert Mechanism report on 14 February. The Alert Mechanism Report concluded that the macroeconomic situation in Belgium, Bulgaria, Cyprus, Denmark, Finland, France, Italy, Hungary, Slovenia, Spain,
Sweden and the UK merited further investigation with a view to assessing the presence of specific imbalances. Where necessary, the Commission will also issue recommendations to take appropriate preventive or corrective action to address these.


text: The Gold Wheels Pawn Shop T-Shirt features Gold Buy Sell Trade graphic large at front. Gold detailing throughout. Thick. A 100% cotton t-shirt. Seamless graphic tag at neck. Available in colorways as seen below. Men's sizes: SM (34-36), MD (38-40), LG (42-44), XL (46-48) unless otherwise noted. Skate Warehouse shows all colors that we have in stock. In rare cases the logo or the color pictured may be slightly different than what is shipped. Model wears a medium.


text:
A method and apparatus for chronologically combining fault data, repair data, and operational parameters for a railroad locomotive. Generally, this data is collected and stored in separate databases. The present invention teaches combining the data so that an ordered analysis reflecting the timing of faults, repairs, and operational information can be carried out to determine the root causes of the faults.
1. A method for analyzing faults from a locomotive, said method comprising:
(a) receiving fault data from a fault database off-board the locomotive, wherein the fault database comprises faults experienced by the locomotive, including information as to when the fault occurred;
(b) receiving operating parameter data from the locomotive, including information as to when the operating parameter data was collected;
(c) receiving repair data from a repair database off-board the locomotive, wherein the repair database comprises repairs performed on the locomotive, including information as to when the repair was performed; and
(d) combining the fault data, the repair data, and the operating parameter data in chronological sequence, to analyze locomotive faults.
2. An article of manufacture comprising a computer program product comprising a computer-usable medium having a computer-readable code therein for analyzing faults from a locomotive using time-tagged data from a plurality of sources, said article of manufacture comprising:
(a) a computer readable program code module for receiving fault data representing the faults experienced by the locomotive, including information as to when the fault occurred;
(b) a computer readable program code module for receiving data representing the operational aspects of the locomotive, including information as to when the operational data was collected;
(c) a computer readable program code module for receiving off-locomotive data selected from the group comprising repair data describing repairs performed on the locomotive including information as to when the repair was performed, maintenance data describing maintenance performed on the locomotive including information as to when the maintenance was performed, and past fault log data describing past faults occurring on the locomotive including information as to when the past fault occurred; and
(d) a computer-readable program code module for combining the fault data, the operational data and the off-locomotive data in chronological sequence for use in analyzing faults from the locomotive.
3. A method for analyzing faults that occur in railroad locomotive operation using time-tagged data from a plurality of sources, said method comprising:
monitoring operation of a railroad locomotive for faults and operational conditions of the locomotive;
transmitting the data indicative of the faults and operational conditions from onboard the locomotive to an off-board location via wireless communications;
accessing off-board data from the group comprising locomotive repair data, maintenance data and past fault log data for the locomotive stored in one or more historical data bases off-board of the locomotive;
combining the onboard data and the off-board data in chronological sequence; and
generating a report including the combined data for use in identifying locomotive operation faults and their causes.
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of claim wherein the step of generating further comprises generating a report including the combined data for use in identifying potential fault conditions on the locomotive.
9. A method for analyzing the effectiveness of repairs made to a railroad locomotive using time-tagged data from a plurality of sources, said method comprising:
monitoring operation of a railroad locomotive for locomotive operational conditions occurring both before and after the time of a repair to the locomotive;
transmitting the data indicative of the operational conditions from onboard the locomotive to an off-board location via wireless communications,
accessing off-board data from the group comprising locomotive repair data, maintenance data and past fault log data for the locomotive stored in one or more historical data bases off-board of the locomotive;
combining the onboard data and off-board data in chronological sequence; and
generating a report of the combined data for use in evaluating the effectiveness of the repair.
This patent application claims the benefit of U.S. Provisional Application No. 60/162,045 filed on Oct. 28, 1999.
The present invention relates generally to machine diagnostics, and more specifically to a system and method that improves diagnostic accuracy by presenting fault and operational data in a chronologically ordered file.
A machine, such as a locomotive or other complex system used in industrial processes, medical imaging, telecommunications, aerospace applications, and power generation may include controls and sensors for monitoring the various systems and subsystems of the machine recording certain operational parameters and generating a fault indication when an anomalous operating condition occurs. Certain of these anomalous conditions may require the imposition of operational restrictions on the machine, without requiring a complete and total shutdown. In any case, because restricted operation can be costly, it is essential to accurately diagnose and quickly repair the machine.
Such complex machines may generate an error log (or fault log), containing information related to a malfunction. The field engineer called to diagnose and repair the machine will first consult the error log to assist with the diagnosis process. The error log presents a "signature" of the machine's operation and can be used by the repair technician to identify specific malfunctions and the operational parameters of the machine before, during and after the fault occurred. Using her accumulated experiences at solving machine malfunctions, the field engineer reviews the error log, identifies the root cause of the fault and then repairs the machine to correct the problem. If the diagnosis was accurate, the repair will correct the machine malfunction. When the error log contains only a small amount of information and the machine is relatively simple, this manual process will work fairly well. However, if the error log is voluminous and the machine is complex, some entries may have an uncertain relationship or perhaps no relationship to the malfunction. It will therefore be difficult for the field engineer to properly review and analyze all the information and successfully diagnose the fault.
To overcome the problems associated with evaluating large amounts of data in error logs, computer-based diagnostic expert systems have been developed and put to use. These diagnostic expert systems are developed by interviewing field engineers to determine how they proceed to diagnose and fix a machine malfunction. The interview results are then translated into rules and procedures that are stored in a repository, which forms a either a rule base or a knowledge base for machine repairs. The rule or knowledge base operates in conjunction with a rule interpreter or a knowledge processor to form the diagnostic expert system. Based on information input by the technician, the rule interpreter or knowledge processor can quickly parse information in the rule or knowledge base to evaluate the operation of the malfunctioning machine and provide guidance to the field engineer. One disadvantage associated with such conventional diagnostic expert systems is the limited scope of the rules or knowledge stored in the repository. The process of knowledge extraction from experts is time consuming, error prone and expensive. Finally, the rules are brittle and cannot be updated easily. To update the diagnostic expert system, the field engineers have to be frequently interviewed so that the rules and knowledge base can be reformulated.
Another class of diagnostic systems use artificial neural networks to correlate operational and fault data with potential root causes. An artificial neural network typically includes a number of input nodes, a layer of output nodes, and one or more "hidden" layer of nodes between the input and output nodes. Each node in each layer is connected to one or more nodes in the preceding and the following layer. The connections are via adjustable-weight links analogous to variable coupling-strength neurons. Before being placed in operation, the artificial neural network must be trained by iteratively adjusting the connection weights, using pairs of known input and output data, until the errors between the actual and known outputs, based on a consistent set of inputs, are acceptably small. A problem with using an artificial neural network for diagnosing machine malfunctions, is that the neural network does not produce explicit fault correlations that can be verified by experts and adjusted if desired. In addition, the conventional steps of training an artificial neural network do not provide a measure of its effectiveness so that more data can be added if necessary. Also, the effectiveness of the neural network is limited and does not work well for a large number of variables.
Case-based reasoning diagnostic expert systems can also be used to diagnose faults associated with malfunctioning machines. Case-based diagnostic systems use a collection of data, known as historical cases, and compare it to a new set of data, a new case, to diagnose faults. In this context, a case refers to a problem/solution pair that represents the diagnosis of a problem and the identification of an appropriate repair (i.e., solution). Case-based reasoning (CBR) is based on the observation that experiential knowledge (i.e., memory of past experiences) can be applied to solving current problems or determining the cause of current faults. The case-based reasoning process relies relatively little on pre-processing of raw input information or knowledge, but focuses instead on indexing, retrieving, reusing, comparing and archiving cases. Case-based reasoning approaches assume that each case is described by a fixed, known number of descriptive attributes and use a corpus of valid historical cases against which new incoming cases can be matched for the determination of the root cause of the fault and the generation of a repair recommendation.
Commonly assigned U.S. Pat. No. 5,463,768 discloses an approach to fault identification using fault or error log data from one or more malfunctioning machines using a CBR approach. Each of the historical error logs contains data representative of fault events occurring within the malfunctioning machines. In particular, a plurality of historical error logs are grouped into case sets of common malfunctions. Common patterns, i.e., identical consecutive rows or strings of error data in the case sets are used for comparison with new error log data. In this comparison process, sections of data in the new error log that are common to sections of data in each of the historical case sets (the historical error logs) are identified. Since the historical error logs have been correlated with a specific repair having a high probability of resolving the fault, the common sections of data in the historical error logs and the new error log can lead to a recommended repair with a high probability of resolving the fault.
U.S. Pat. No. 6,415,395, entitled "Method and System for Processing Repair Data and Fault Log Data to Facilitate Diagnostics", assigned to the assignee of the present invention and herein incorporated by reference, discloses a system and method for processing historical repair data and historical fault log data, where this data is not restricted to sequential occurrences of fault log entries, as in the commonly owned patent described above. This system includes means for generating a plurality of cases from the repair data and the fault log data. Each case comprises a repair and a plurality of related, but distinct faults. For each case, at least one repair and distinct fault cluster combination is generated and then a weight is assigned thereto. This weight value indicates the likelihood that the repair will resolve any of the faults included within that fault cluster. The weight is calculated by dividing the number of times the fault cluster combination occurs in cases comprising related repairs by the number of times the combination occurs in all cases. New fault log data is entered into the system and compared with the plurality of fault log clusters. The repair associated with the matching fault log cluster represents a candidate repair to resolve the new fault. The report output from this system lists the candidate repairs in sequential order according to the calculated weights.
Further, U.S. Pat. No. 6,343.236, entitled "Method and System for Analyzing Fault Log Data for Diagnostics", assigned to the same assignee of the present invention and herein incorporated by reference, discloses a system and method for analyzing new fault log data from a malfunctioning machine, again where the system and method are not restricted to sequential occurrences of fault log entries. The fault log data is clustered based on related faults and then compared with historical fault clusters. Each historic fault cluster has associated with it a repair wherein the correlation between the fault cluster and the repair is indicated by a repair weight. Upon locating a match between the current fault cluster and one or more of the historical fault clusters, a repair action is identified for the current fault cluster based on the repair associated with the matching historical fault cluster.
One particular type of fault that can be advantageously analyzed by certain fault analysis and diagnostic tools is the so-called "no trouble found" fault. Failure conditions that are difficult to diagnose within a complex system may result in such a declaration of no trouble found. Typically, the system experiences intermittent failures and when the system is taken out of service for diagnosis, there is no evidence of a fault or failure, i.e., the fault is intermittent. In this situation, the repair technician declares that the system is failure free and ready for return to service, i.e., no trouble found. Later, the system may experience a repeat failure due to the same problem.
It is believed that the fault and repair analysis tools disclosed in the patent applications described above provide certain advantages and advancements in the art of the diagnostics of complex machines. It would be desirable, however, to provide a system and method to improve the evaluation and identification of faults by undertaking the analysis on a chronologically ordered set of fault data and machine operational information.
The search for an effective tool to diagnose failures occurring in a complex system, such as a railroad locomotive, has been an elusive one. Several such tools are discussed above. The present invention describes a process that systematically combines fault log and machine operational information (sensor readings of various operational parameters commonly referred to as data packs) with maintenance and repair data and fault declaration information into a single chronologically ordered file. With the data ordered chronologically, the present invention offers a more effective tool to diagnose the exact nature and cause of a fault. Combining all of this information, as taught by the present invention, presents the repair analyst with a single file from which the state of the machine can be determined at any time prior to and after the occurrence or recording of a specific fault. By identifying anomalies and analyzing operational parameters occurring immediately prior to the fault (and in some cases, after the fault), the analyst can identify the most probable cause. Additionally, by reviewing the data pack information recorded immediately after a repair or other maintenance action, the analyst can determine the effectiveness of that repair or maintenance activity. The chronologically ordered data presentation also allows the detection of incipient faults based on anomalous conditions and operational parameters. Analysis rules can then be established for later use in recognizing potential fault conditions in the operational data. The present invention can also help to create data filters so that only the information identified as pertinent to a particular fault is analyzed. The filtered out data can be ignored due to its apparent lack of correlation with a specific fault. Using the teachings of the present invention increases the accuracy of failure diagnosis, resulting in more effective (e.g., more timely and less costly) troubleshooting and repair actions. Fewer repeat failures will occur because there will be fewer misdiagnosed cases and fewer no trouble found faults.
The features and advantages of the present invention will become apparent from the following detailed description of the invention when read together with the accompanying drawings in which:
FIG. 1 is a block diagram of one embodiment of a system of the present invention using a processor for processing operation parametric data and fault log data;
FIG. 2 is an illustration of exemplary repair log data;
FIG. 3 is an illustration of exemplary fault log data;
FIG. 4 is a flowchart illustrating operation of the present invention; and
FIGS. 5 and 6 illustrate exemplary data ordered in accordance with the teachings of the present invention.
Before describing in detail the particular fault diagnosis system in accordance with the present invention, it should be observed that the present invention resides primarily in a novel combination of processing steps and hardware elements related to a system for diagnosing faults on a machine. Accordingly, these processing steps and hardware components have been represented by conventional processes and elements in the drawings, showing only those specific details that are pertinent to the present invention, so as not to obscure the disclosure with structural details that will be readily apparent to those skilled in the art having the benefit of the description herein.
FIG. 1 diagrammatically illustrates one embodiment of the diagnostic system 10 of the present invention for analyzing faults for the purpose of identifying root causes, fault patterns, and correlations of these patterns with operational data. The diagnostic system 10 provides a process for automatically harvesting or mining repair data describing related and unrelated repairs, fault log data describing faults or anomalous events, and parametric operational data from one or more machines, such as locomotives. The diagnostic system 10 generates a chronological list of the repair information, fault data, and operational parametric information for analysis by a locomotive repair expert. With the disparate databases combined in a chronologically ordered database, the process of analysis is easier as the potential correlation between various data items is easier to identify.
Although the present invention is described with reference to a locomotive, the diagnostic system 10 can be used in conjunction with any machine where the operational parameters of the machine are monitored. Exemplary applications include complex machinery used in the medical diagnostic field, telecommunications field, and aircraft engine field.
The exemplary diagnostic system 10 illustrated in FIG. 1 includes a processor 12 such as a computer (e.g., a UNIX workstation) having a hard drive, input devices such as a keyboard or a mouse, magnetic storage media (e.g., tape cartridges or disks), optical storage media (e.g., CD-ROM's), and output devices such as a display and a printer. The processor 12 is connected to and processes data contained in a repair database 20 and a fault log database 22.
The repair database 20 includes repair data or records describing repairs or maintenance actions for one or more locomotives. FIG. 2 shows an exemplary portion 30 of the repair data contained in the repair data database 20. The repair data includes a customer identifier in a column 32, a unique locomotive identifier or locomotive road number in a column 33, the repair date in a column 34, a repair code in a column 35, a prose description of the repair in a column 36, a description of the actual repair performed in a column 37, a description of the failure mode that the repair was intended to resolve (if any) in a column 38, the sub-assembly on which the repair was conducted in a column 39, and the primary system to which the repair relates in acolumn 40. The information in the repair database 20 is collected from field support personnel located at the locomotive maintenance facilities. Locomotives are brought into the repair facility as required to undergo repair, and also on a predetermined fixed schedule for regular preventative maintenance and minor repairs. Entries in the repair database are made at that time.
The fault log database 22 includes fault log data indicating faults on the locomotive, as recorded by an on-board monitor system at the locomotive. Further details of an exemplary on-board monitor system can be found in commonly-owned United States patent application bearing the title "On-Board Monitor for a Railroad Locomotive", filed on Oct. 25, 2000 with application Ser. No. 09/696,368.
FIG. 3 shows an exemplary portion 40 of the fault log data stored in the fault log database 22. The fault log data may include a customer identifier in a column 42, a unique locomotive identifier or road number in a column 44, the date that the fault occurred in a column 45, a fault code in a column 46, and a prose description of the fault in a column 50. The time at which the fault occurred is shown in a column 47 and the fault reset time is set forth in a column 48. The values in the columns 47 and 48 are the number of counted intervals from a predetermined start time. These count intervals can be converted to eastern standard time using a well known software decoder and given the start date and time and the count interval. Resetting of a fault can be accomplished automatically or manually. For those faults that do not endanger locomotive operation, after the fault occurs, it will be automatically reset. The recording of this fault serves as a flag indicating the occurrence of an anomalous event (i.e., a fault), but it was only minor or did not prevail for an extended duration. For example, a traction motor current in excess of a threshold value will cause the recording of a fault, but if the current value returns to a normal rating immediately after the spike, the fault will be reset and the locomotive can continue to operate as normal. More serious faults require analysis by human intervention to determine whether the locomotive can continue operation. The occurrence of such faults is recorded and also disables operation of the locomotive subsystem to which it relates. If the locomotive operator or technician determines that continued operation during this fault condition is acceptable, he can manually reset the fault, causing the subsystem to be reactivated. If the nature of the fault is such that operation cannot continue, the locomotive is removed from service. Additional information in the form of operating parametric values when the fault occurred are shown in the fault log 40 within that area designated by a reference character 49. This operational information may include temperature sensor readings, pressure sensor readings, electrical voltage and current readings, and power output readings. Operational states may also be shown within the area designated by the reference character 49. Such operational states include whether the locomotive is in a motoring or a dynamic braking mode, whether any particular subsystem within the locomotive is undergoing a self test, whether the locomotive is stationary, and whether the engine is operating under maximum load conditions.
As taught by the application above entitled "On-Board Monitor for a Railroad Locomotive", the information in the fault log 40 is downloaded a predetermined number of times each day from the locomotive to a remote monitoring and diagnostic center. Certain faults occurring on the locomotive generate an immediate call from the locomotive back to the remote monitoring and diagnostic center, after which the remote monitoring and diagnostic center calls the locomotive for downloading the information shown in the fault log 40. In one embodiment, the remote monitoring and diagnostic center calls the locomotive three times per day to download the fault log data and operational parametric data.
A customer database 25 in FIG. 1 contains additional fault and operational information as recorded by the railroad operating the locomotive. Exemplary information included in each of these data files, which is generally entered by a customer repair technician or the locomotive operator, includes certain faults and anomalous conditions and the time and date of their occurrence. A unique locomotive identifier, for example the locomotive road number, is also included in each data file.
A statistics database 26 includes a plurality of files identifying certain attributes of each locomotive and operational parametric data. For example, a locomotive file in this database includes the version number of significant software applications running on the locomotive, the model number associated with key systems, and other locomotive features (for example, number of engine cylinders and maximum horsepower rating). This file also contains certain cumulative operational statistics such as the cumulative current supplied to the traction motors (in megawatt hours), the current generated by the dynamic braking system (in megawatt hours), the number of engine operational hours, the total number of miles traveled by the locomotive, and the total number of engine hours. Finally, this database includes operational parametric information collected at regular intervals or collected immediately following the occurrence of a fault. The data to be collected and the collection frequency can be either automatically or manually set. Also, in lieu of including the operational parametric data related to a fault in the statistics database, this information can be collected when the fault occurs and made a part of the fault file. In such a case, the operational parametric data would be stored in the fault log database 22, rather than the statistics database 26.
FIG. 4 illustrates the process executed by the processor 12 (see FIG. 1) for creating the chronological listing of repairs, faults, and operational data. At a step 80, repair data is read from the repair database 20. At a step 82, the fault data is read from the fault log database 22. At a step 84, information input by the railroad customer into its own database (referred to as the customer database 25 in FIG. 1) is read by the processor 12. Statistics data from the statistics database 26 is read at a step 86. At a step 88, the processor 12 chronologically orders the various input data and creates a report, as indicated at a step 90.
A representative sample of the chronologically ordered report is illustrated in FIG. 5. Organizing the information from the various databases into a time line structure facilitates analysis of locomotive road failures and identification of fault patterns that can be used for early detection and more robust diagnosis of faults. A column 100 identifies the locomotive based on its unit number or road number. The date and time of the occurrence (where the "occurrence" can be a fault, a repair, or simply the reading of operational data) is listed in a column 102. A column 104 identifies a fault by number and a column 106 identifies the fault with a label. A more complete description of the fault is set forth in a column 108. A column 110 identifies the occurrence time using a sequential counter that begins counting at a predetermined time, where the counting start point is under either automatic or manual control. If the fault is reset, that time, again using the counter sequence, is set forth in a column 112. The remaining columns show data related to certain locomotive parameters. The locomotive speed is set forth in a column 114, the direction in a column 116, the notch setting in a column 118, the engine speed in a column 120, the volts across the traction motors in a column 122, and the current input to the traction motors in a column 124. A column 126 lists a sub-identifying number for the fault shown in the column 104.
FIG. 6 is another chronological listing of various fault events in accord with the present invention, including an overlay of a repair performed on Feb. 27, 1999, in Morrill, Nebr. The repair was intended to resolve the fault represented by fault code 7324. Note that in fact 7324 faults do not appear after the repair on February 27, but faults identified by code 731A continue to appear both before and after the repair.
Additional information that can be included in the time line includes: the cab version, the cumulative number of motor megawatt hours and dynamic brake megawatt hours, the total power produced at the time when the fault occurred, the cumulative number of miles logged by the locomotive, the cumulative engine hours, and the latitude and longitude of the locomotive at the time of the occurrence.
CAB is one of many controller cards on the locomotive and includes a processor with executable software. Periodically, improvements and updates are made to this software and bugs in the software code are fixed, but the modified version of the software is not applied to all locomotives simultaneously. Therefore, it is important to know which version of the software is running on a particular locomotive as this information may help in determining the cause for certain faults or in understanding the behavior of out-of-spec operational parameters in the datapack information.
The first fault listed in the time line of FIG. 5 bears number 731A. Turning to the fault description column 108, this fault relates to the phase modulator associated with inverter 3. As is generally known, a diesel engine of a locomotive is drivingly coupled to an alternator for supplying three phase alternating current, which is then rectified to direct current and then inverted back to frequency controllable alternating current for driving traction motors associated with each locomotive axle. Generally, there is one inverter providing controllable alternating current to each traction motor. The first fault listed involves the phase modulator operative on the positive going portion of the B phase alternating current of the third inverter. The fault may also be caused by a problem in the inverter motor controller/traction motor controller (or IMC 2-3, 4, 7/TMC-3, 0). Certain locomotives include an inverter motor controller while others use a traction motor controller. It should be realized that the potential fault causes listed in the column 108 do not necessarily represent the only conditions leading to fault 731A. Those listed are simply the most likely causes. The fault sub-identification in the column 126 (in this case sub-identification number 4) provides the user with more specific information relative to fault 731A.
Note that within a bubble 130, the fault 731A has occurred twice. Once on Feb. 15, 1999, and again on Feb. 17, 1999. Recognizing that the time line shown in FIG. 5 is merely an excerpt, the analysis of the complete time line may indicate that the fault 731A has occurred on one or more occasions prior to Feb. 15, 1999. The locomotive expert analyzing the time line can identify the first occurrence of fault 731A and the various repairs and operational parameters recorded since that first occurrence. By combining the fault information, repair information, and operational information from separate databases and ordering the information chronologically, the locomotive expert can more easily determine causes and effects as related to the recorded data. The analysis can also identify concurrent faults and perhaps point to a first solution when the faults occur jointly, while a second solution is indicated when only one of the faults occurs. Fault solutions can also be identified dependent upon whether the fault occurs while the locomotive is in the motoring or the dynamic braking mode. Certain faults may occur on one or more of the inverters, indicating a particular solution. But, if all of the inverters manifest a fault, then a different root cause is indicated. By chronologically ordering the data as shown in FIG. 5, the locomotive expert can more easily and efficiently identify related and independent faults so that a more likely successful fault solution can be recommended. Clearly, such a process of careful analysis and identification of joint causes could not be undertaken if the various databases were not combined and chronologically ordered. Further, the root causes identified through the analysis set forth above can be used to create a rule in the expert analysis systems discussed above in the Background section.
One particular fault situation that can be advantageously analyzed using a time line created in accord with the present invention is a so-called "no trouble found" fault. Failure conditions that are difficult to diagnose within a complex system may result in the repair technician's declaration of a no trouble found event because he is unable to either recreate or diagnose the source of the problem. Typically, these no trouble found events occur due to intermittent failures. Or the complexity of the system may obscure the fault condition to a repair technician whose skills are deficient in some area relevant to system performance. No trouble found events are especially troublesome because the locomotive is placed back into service without a resolution of the fault and later may experience a repeat failure due to this same problem. These no trouble found events can also be advantageously analyzed and resolved by the present invention. Recall that certain information in the time line is made available from a customer database. Since the customer is frequently responsible for maintenance and repair of the locomotive, it is the customer repair technician who usually declares a fault to be a no trouble found event. However, when the time line analysis is undertaken by a locomotive repair expert, she may be able to discern the specific nature of the fault and its root cause using the data presented in the time line. As was mentioned above, the relevant time line data that led to the successful resolution of what heretofore had been declared a no trouble found event can be used in the expert systems discussed above to create rules that will be used to successfully identify and solve such faults.
The information contained within a rectangle 140 of FIG. 5 is the customer's record and related description of a locomotive road failure. The noted initial cause of the road failure, based on the customer's recorded comment in the time line, was that one or more traction motors were cut-out, leading to a loss of motive power. The unit was subsequently released as a no trouble found event, because when the technician examined the unit, the traction motors were operating properly. Reviewing the time line of FIG. 5, the locomotive expert can point to the 731A fault as a potential cause of the traction motor cut-out problem. If this was in fact a true no trouble found event (e.g., an intermittent fault), one would not expect to see the reappearance of the 731A fault. In fact, in a bubble 144, the 731A fault continues to log, indicating that the road failure was not a true no trouble found event and that the problem still exists. In fact, it was not until later that the problem causing the 731A fault was finally determined and repaired.
Generally, the invention has been described in conjunction with faults and repair for a single locomotive. Those skilled in the art will recognize that it is advantageous to chronologically combine fault, repair, and statistics information collected from a plurality of locomotives to identify those faults occurring on similar locomotives.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes may be made and equivalent elements may be substituted for elements thereof without departing from the scope of the present invention. In addition, modifications may be made to adapt a particular situation more material to the teachings of the present invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope of the appended claims.
Patent Citations
Non-Patent Citations
Referenced by
Legal Events
Original Image


text: Make every step a touchdown for your kiddos. Run the yards with the football baby socks or cheer on the team with the white pair with 70's inspired gym class baby socks with brown stripes. Sizes 0-12 months, 12-24 months, 2T-4T Composition: 81% Cotton, 17% Nylon, 2% Spandex Weight: 2.0oz - 2 pair pack cotton ankle socks. 2 pair pack cotton ankle socks.


text: Ready to buy Armalite Rifle Parts? Brownells.com has the best selection and pricing around. With 2 Armalite Rifle Parts in stock ranging in price from $14.99 to $179.99, you'll find all the best choices available. As the number one online retailer of gun parts and gunsmith tools, we'll provide excellent customer service, great prices, and top-quality merchandise every day. We're so convinced you'll be happy with all our Armalite Rifle Parts that we offer a 100% customer satisfaction guarantee. If you're not completely satisfied with your purchase let us know so we can make it right. Shop our inventory of Armalite Rifle Parts and place your order on the web or over the phone. Our knowledgeable staff is always here to help meet all your gun parts and gunsmith needs, so never hesitate to ask a question. By email, by phone, or by smoke signal - we're here to help you aim true.


text:
Someone once said, "The people who do things that count don't usually stop to count them."
I have heard service members decorated with medals repeatedly say they were just doing their job, that those who gave their lives are the real heroes.
Contrast this with many athletes who draw attention to themselves, demanding they receive accolades, big salary packages and product endorsements.
And whom do most people feel drawn toward?
Even in "regular" people's lives, we hear, "Look at me! Look at how much I am doing!"
Some people draw attention to themselves by pointing out their busy schedules or accomplishments. They boast to seek praise from others or to boost their self-esteem.
However, we should be drawing attention to God, who has called us to serve others.
In Matthew 6:2-4, Jesus says, "So whenever you give alms, do not sound a trumpet before you, as the hypocrites do in the synagogues and in the streets, so that they may be praised by others. Truly, I tell you, they have received their reward. But when you give alms, do not let your left hand know what your right hand is doing, so that your alms may be done in secret; and your Father who sees in secret will reward you."
If you are doing something for another person, question your motivation. Are you doing it to help that person? On some conscious or unconscious level, are you doing it to bolster yourself in others' eyes?
Finally, please pray for Bostonians who died or were injured Monday during the Boston Marathon bomb blasts.
The Rev. Mark Broadhead is Laurel Hill Presbyterian Church and First Presbyterian Church of Crestview's pastor.


text:
BALTIMORE, Md. – The University of New Hampshire women's basketball team opens up its conference schedule on Monday, Jan. 2 when they visit the reigning America East regular-season champion University of Maryland Baltimore County for a 7 p.m. matchup at RAC Arena. Links to live stats, audio and video will be available at unhwildcats.com.
Monday's matchup between UNH and UMBC will be the 16th meeting all-time between the two programs. New Hampshire won four of the first six meetings against UMBC, but the Retrievers swept the season series last year after the two squads split the season series the previous three years. UMBC claimed the most recent victory, defeating UNH, 63-55, at Lundholm Gymnasium on Feb. 13, 2011.
The University of Maryland Baltimore County women's basketball team fell at Virginia Tech, 57-52, Thursday evening on the second day of the Hokie Classic … UMBC is coming off back-to-back losses and stands at 6-7 on the season … UMBC won the America East regular season last year but fell to Hartford in the semifinals of the conference tournament … Most recently against Virginia Tech, Erin Brown and Brittany Crowell combined for 34 points on 10 3-pointers … Brown tied her career high with six 3-pointers in nine attempts and finished with 18 points, while Crowell set new career bests with 16 points and four triples in eight attempts, as UMBC matched a season high with 10 treys in the game, shooting 47.6 percent from beyond the arc … The Retrievers shot 37.3 percent from the floor in the game while holding Virginia Tech to just 31.0 percent, but while the Hokies shot just 50 percent from the charity stripe, their 16 free throws proved to be the difference in the game, as UMBC went to the line just six times … Brown leads the league in scoring (15.8) and ranks ninth in rebounding (6.8), while Michelle Kurowski tops the conference in free throw percentage (90.9) … As a team, the Retrievers own the best numbers at the charity stripe with a free throw percentage of 73.9.
The University of New Hampshire women's basketball team downed the New Jersey Institute of Technology, 79-71, in the consolation game of the Cyclone Challenge Friday evening … The Wildcats split at the Cyclone Challenge, also losing to host Iowa State, and stand at 7-5 on the season … Denise Beliveau posted 24 points and 12 rebounds for her fifth double-double of the season … Three other Wildcats reached double figures as Morgan Frame finished with 20 points and nine rebounds … Kelsey Hogan and Abigail LaRosa added 13 and 11, respectively, as Hogan dished out four assists and LaRosa was 7-of-8 from the charity stripe … Additionally, Cari Reed recorded a career-high seven assists … On the season, Beliveau ranks sixth in the league in scoring (12.8) and fourth in rebounding (8.4) … Hogan is the most efficient 3-point shooter in the league, clocking in at 47.5 percent from beyond the arc … As a team, UNH leads the conference in 3-point field goal percentage (34.8) and rebounding defense (35.6), and rank second in field goal percentage (37.6).
Denise Beliveau enjoyed her trip to Ames, Iowa last week as the senior averaged 18 points and 7.5 rebounds per game at the Iowa State Cyclone Challenge. In the consolation game against NJIT, Beliveau poured in a season-high 24 points and added a game-high 12 rebounds for her fifth double-double of the season. The senior was highly efficient from the floor as she shot 8-of-14 from the field and 3-of-4 from long range. Her sharpshooting efforts fueled the Wildcats to a victory as she halted a 13-2 NJIT run with eight straight points, including back-to-back 3-pointers, to put UNH back in contention after an early deficit. Beliveau also logged double-digits in the opener against Big-12-foe Iowa State as she chipped in 12 points and added four steals, en route to All-Tournament Team honors.
The UNH starting five accounted for all but two of the team's 79 points in the win over NJIT on Dec. 30. Denise Beliveau led the way with 24 points, while Morgan Frame (20), Kelsey Hogan (13) and Abigail LaRosa (11) also reach double-figures. Cari Reed just missed the mark with nine points and also dished out a career-best seven assists. In all, the team's 79 total points mark the highest scoring output of the season.
Kelley Flynn recorded season highs of 10 points, six rebounds and four blocks at Iowa State in the opening round of the Cyclone Challenge (Dec. 29). The double-digit mark was Flynn's highest scoring output since the season-opener at Brown when she notched 8 points.
Morgan Frame, a junior transfer just four games into her UNH career, erupted for a career-high 35 points and 12 rebounds at Wagner on Dec. 21. Frame shot 15-for-26 from the floor to pace the Wildcats and fell just one point shy of matching the school record for points in a game, earning America East Player of the Week honors for her efforts. She also collected three steals in 41 minutes off the bench. Frame was instrumental throughout the contest as she scored nearly half of UNH's points in the first stanza (13-of-27) to keep the Wildcats within reach at halftime. She went on to net 18 in the second half and four points in overtime to seal the victory. Frame notched a double-double in each of her first two games since becoming eligible as a mid-year transfer last season and is averaging 21.5 points and 9.8 boards per game this season.
New Hampshire is off to a 5-2 start in road games this season, picking up victories over a trio of Ivy Leaguers in Brown, Cornell and Dartmouth, as well as Rhode Island and Wagner. The Wildcats are averaging 58.4 points per game when away from the friendly confines of Lundholm Gymnasium.
Only two players have netted 30-point performances in the America East this season, and both belong to New Hampshire. Morgan Frame owns the highest single-game effort in the league with a 35-point outing at Wagner, while Cari Reed represents the other member of the club with a 32-point showing against Harvard. Additionally, Frame's 15 field goals and Reed's eight 3-pointers are also single-game league-best efforts this season.
New Hampshire has played its best basketball in close games this season as the club is a perfect 4-0 in games decided by five points or less. Most recently, UNH downed Wagner, 73-72, in overtime, thanks to a last-second jumper by Denise Beliveau in extra time. Earlier in the season, Kelsey Hogan tipped in a game-winning buzzer-beater to help UNH beat Cornell. In both those contests, Cari Reed kept the Wildcats in the game with a late 3-pointer, including a timely distance shot at Wagner to send the game into overtime.
Denise Beliveau grabbed a season-best 14 rebounds against Manhattan, marking the most by a Wildcat this season. Beliveau ranks fourth in the America East in rebounding with 8.4 boards per contest and leads the league in defensive rebounds (5.9). As a team, the Wildcats are 7-0 when they pull down more rebounds than the opposition and currently lead the conference in defensive boards (35.6).
Sophomore Kelsey Hogan and junior Cari Reed both rank inside the top-five in the America East for 3-point field goal percentage. Hogan leads the league at 47.5 percent shooting from beyond the arc, while Reed ranks fourth in the conference at 41.1 percent. As a team, UNH owns the best 3-point field goal percentage in the conference, shooting 34.8 percent from behind the arc.
The Wildcats boast four players averaging double-digits is scoring through 12 games this season. Morgan Frame leads the lineup with 21.5 points per game, while Denise Beliveau, Kelsey Hogan and Cari Reed clock in at 12.8, 11.1 and 10.5, respectively.
Senior Denise Beliveau has already logged five double-doubles in just 12 games this season, with three coming on the road against Ivy League teams. She dropped in 10 points and added a game-high 13 rebounds in the season opener at Brown, and posted 18 points and 10 boards at Cornell, leading all players in both categories. After recording 15 points and 13 rebounds at Dartmouth, she led all players with 17 points and 14 rebounds against Manhattan. Most recently, Beliveau dropped a season-best 24 points and added 12 rebounds against NJIT. Beliveau is no stranger to the accomplishment as she posted a conference-best 11 double-doubles last season.


text:
- Home
- Reviews
- Music
- Articles
- Women
- Wrestling
- Podcasts
- Everything Else
- Random
Before I start getting my Nostradamus on I want to look back for just a second. My last Predications and Hopes article in 2012 listed a lot of things and I want to check what came true and what didn't. So let's see…
Since Drake's massive amounts of success and cult like followings (YOLO anyone?) he did get dissed again, this time by Pusha T. Nailed it! Did Nas, Slaughterhouse, Rick Ross and Raekwon release solid albums? Of course it's down to opinion but overall I think so. Nas definitely did. Slaughterhouse did. Rick Ross kind of did but Raekwon was pretty quiet in 2012. He's got all of 2012 I suppose with Wu-Block.
As for the Dark Knight Rises I was right! Even though it wasn't a hard guess this movie was going to be epic I'm still happy it turned out the way it did. I caught a few rappers referencing the movie but not as many as I thought. Either way check Rapsody's verse on Murs & 9th Wonder's "Get Together".
B.o.B.'s Strange Clouds never made it to my CD player so I have no idea if he stepped his game up but judging from what I've heard, he didn't. It's a shame because his earlier mixtapes from '08 and '09 are something I still fuck with today.
As for my hopes Xzibit did release some new music. Not exactly a comeback record but it did feature a Dre beat and appearances from the Alkaholiks. Keep it up X.
Sequel albums weren't really a popular route for 2012 so I guess one of my wishes came true (Lupe's choice was alright in my books though). No big name MC's worthy of each other's attention battled it out. Also sadly Verbose did not grace nappyafro's pages with his presence. Here's hoping for next year.
Now to quote some of you out there that are part of the 'Fronation and talk about the hopes and predictions you had for 2012.
But now it's time to focus on what's in front of us. Here's my list of events I think will happen and what I want to happen. As always comment on what you think will occur and what you wish will happen in 2013. Do it. It will be fun to look back this time next year and look at this article as a sort of time capsule.
Happy 2013 everybody!


text:
The nspluginwrapper is an Open Source compatibility plugin for Netscape 4
(NPAPI) plugins. That is, it enables you to use plugins on platforms they were
not built for. For example, you can use the Adobe Flash plugin on Linux/x86_64,
NetBSD and FreeBSD platforms.
WWW: http://nspluginwrapper.org
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
To install the port: cd /usr/ports/www/nspluginwrapper/ && make install cleanTo add the package: pkg install www/nspluginwrapper
cd /usr/ports/www/nspluginwrapper/ && make install clean
pkg install www/nspluginwrapper
No options to configure
gmake pkgconfig
Number of commits found: 35
Update CentOS base to 6.5, add userland ports
The Fedora 10 infrastructure ports have been in use since June 2009 and, while
having served a great deed, have become unsupported upstream and hence affected
by unfixed security vulnerabilities. In addition to that, many recent Linux
binaries need newer libc / stdlibc++ versions.
This commit adds the linux-c6- userland as drop-in replacement for the -f10
infrastructure, as well as upgrading the linux_base-c6 port to CentOS 6.5.
If you want to switch to linux-c6 ports, please define at /etc/make.conf:
- Catch up with glib20 changes. [1]
- Add couple of upstream patches for nspluginplayer.
PR: ports/186115 [1]
Convert LIB_DEPENDS to new format.
- Update plugin directories to automatically pick up.
- Support staging and tidy up plist.
- Remove article from comment and add LICENSE.
Add NO_STAGE all over the place in preparation for the staging support (cat:
Eradicate USE_GNOME=pkgconfig from www
While here:
- Trim headers
- Convert USE_GMAKE to USES=gmake
Add an upstream patch to fix build with GCC 4.6 (and possibly others).
Prodded by: avg
- Update to 7.31.0
- Bump PORTREVISION for ftp/curl shlib change
- Add TEST_DEPENDS
- Convert to new options framework
- Adjust options:
- Add COOKIES
- Add CYASSL, NSS, POLARSSL, THREADED_RESOLVER, TLS_SRP [1]
- Add GSSAPI and SPNEGO [2]
- Remove KERBEROS4
- Rename LIBIDN to IDN
- Remove TRACKMEMORY [1]
- Sort option handler
- Add SLAVEDIRS: ftp/curl-hiphop
- Cosmetic change
- Cleanup Makefile header
- While I'm here, fix typo (PORTREVSION) in x11-wm/ede/Makefile
Changes: http://curl.haxx.se/changes.html
PR: ports/172325 (-exp run), ports/177369 (based on) [1]
Submitted by: Hirohisa Yamaguchi <email@example.com> [1], hrs (via email) [2]
Exp run by: miwi
* Update the glib to 2.34.3 and gtk20 to 2.24.17 and gtk30 to 3.6.4 which
are the latest stable releases.
* Update vala to the newest stable release 0.18.1, also update a few ports
in the gtk/gnome stack.
* The c++ bindings ports for glib, atk, gconf, etc, have now USE_GNOME toggles.
* Remove pkg-config run depends from glib20 and freetype2. This doesn't
eliminate pkg-config run dependency completely, a second phase is needed
and is planned.
* Support for .:run. and .:build. for USE_GNOME components was added.
Currently only libxml2 and libxslt support this mechanism.
* Updates of the telepathy stack and empathy.
* Trim makefile headers, convert ports to new options, trim off library
versions for some ports.
* Fix other ports so they build with the new glib version.
Thanks to miwi and crees for helping out with some exp-runs.
Approved by: portmgr (miwi & bapt)
Obtained from: gnome team repo
- Update to 1.4.4.
- Chase official URL change.
Update to 1.4.2.
- Update nspluginwrapper to 1.4.0 and assume maintainership. [1]
- Deprecate nspluginwrapper-devel, which is now older than nspluginwrapper.
Approved by: Dave Grochowski (firstname.lastname@example.com) [1]
- Get Rid MD5 support
Update linux-f10-pango to 1.28.3 (+ bump portrevision of dependend ports).
This fixes a security warning from portaudit.
Security: CVE-2009-1194
VuXML: 4b172278-3f46-11de-becb-001cc0377035
Thanks to: Luchesar V. ILIEV <email@example.com> (F10+rpmbuild info)
Update WWW
PR: private mail
Approved by: email@example.com (maintainer timeout; > 14d)
Chase the ftp/curl shlib version bump.
- update to 1.4.1
Reviewed by: exp8 run on pointyhat
Supported by: miwi
- update to jpeg-8
Update MASTER_SITE, current server is unavailable
Approved by: maintainer timeout (email@example.com)
A compatibility plugin for Mozilla NPAPI (development version).
Note: The Linux/i386 RPM was built by me on Fedora 10 via VirtualBox
because the author did not provide them. For more information about
the development branch, please read:
PR: ports/141179
Limit the stack size for plugins. Linux glibc threading behaves
slightly differently with a smaller stack size and the Flash plugins
rely on this behaviour.
Suggested by: dchagin
Patch by: nox
Discussed at: freebsd-emulation
Reminded by: Tijl Coosemans <email@example.com>
- bump all port that indirectly depends on libjpeg and have not yet been bumped
or updated
Requested by: edwin
Welcome to the new linux ports infrastructure which allows using
both current (fc4) and future linux (f8) distributions at one
ports tree.
The patch contains full changes to ports/Mk files and all ports involved.
But only infrastructure is changed. The resulting packages are the same as
before. Hence no need to bump PORTREVISIONs.
The idea was taken from bsd.gnome.mk and others.
More than 130 ports are switched to follow a new linux infrastructure
introduced by changes to bsd.port.mk, bsd.linux-rpm.mk and a new
Thanks for all who was involved and helped me with this work.
And help from Alexander Leidinger was incredible.
Other changes are coming. Stay tuned!
PR: ports/132510
Submitted by: bsam (me)
Exp-run by: portmgr (pav)
Bump the version of the curl shared library after the ftp/curl update
to 7.19.2.
Bump PORTREVISION, even on the ports that do not have a versioned
dependency, since the binaries will most probably still stop working.
- Fix path to npwrapper.so on amd64
- Bump portrevision
PR: ports/130317
Submitted by: Yuri Pankov <email@example.com>
Approved by: David Grochowski <email@example.com> (maintainer)
- Update to version 1.2.2.
- Remove configure patching since it is now unnecessary.
- Switch to USE_XORG and remove USE_XLIB and friends.
PR: ports/130144
Submitted by: Dave Grochowski <email@example.com> (maintainer)
- Update to 1.0.0
Submitted by: Dave Grochowski <email@example.com> (maintainer)
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
- Remove unneeded dependency from gtk12/gtk20 [1]
- Remove USE_XLIB/USE_X_PREFIX/USE_XPM in favor of USE_XORG
- Remove X11BASE support in favor of LOCALBASE or PREFIX
- Use USE_LDCONFIG instead of INSTALLS_SHLIB
- Remove unneeded USE_GCC 3.4+
Thanks to all Helpers:
Dmitry Marakasov, Chess Griffin, beech@, dinoex, rafan, gahr,
ehaupt, nox, itetcu, flz, pav
Tested on: pointyhat
Approved by: portmgr (pav)
Remove support for XFree8-4.
From now on, X_WINDOW_SYSTEM != "xorg" is not supported anymore.
PR: ports/119418
Submitted by: flz
Approved by: portmgr (pav)
- Update to 0.9.91.5
PR: ports/115992
Submitted by: Dave Grochowski <firstname.lastname@example.com> (maintainer)
- This port requires linux-gtk2 instead of the native one
- This port needs both native and linux version of libX11.
Since there is no good way to specify the native one,
repeat the logic in bsd.port.mk here.
Reported by: Henrik Brix Andersen, TooMany Secrets <toomany at toomany.net>
- Respect X11BASE in configure script
PR: ports/112274
Approved by: Dave Grochowski (maintainer)
- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.
- Update to 0.9.91.4
PR: ports/111291
Submitted by: rafan
Approved by: Dave Grochowski <malus.x at gmail.com> (maintainer)
Add nspluginwrapper 0.9.91.3, a compatibility plugin for Netscape 4
(NPAPI) plugins.
PR: ports/111166
Submitted by: Dave Grochowski
Servers and bandwidth provided byNew York Internet, SuperNews, and RootBSD
20 vulnerabilities affecting 50 ports have been reported in the past 14 days
* - modified, not new
All vulnerabilities


text:
Hardt, Stern & Kayne is a progressive, creative and flexible Chicago area law firm with a national and local, broad based, corporate, transactional, real estate and litigation practice, with a specialty in servicing automobile dealers and real estate developers. As a smaller boutique firm, we maintain a collegial environment and provide personal, cost effective, logical, creative and commonsense litigation services to our clients.
Having operated its successful practice in downtown Chicago for many years, the firm cultivated a sophisticated legal practice similar to larger Loop firms. Our recent move to a brand new office building in the forests of Riverwoods,
has furthered our ethic of building personal relationships with clients. Our attorneys focus on our client's needs for positive results. We appreciate the opportunity to serve existing and new clients.


text:
Adorn in Classically Crete (Fits iPhone® 4 & 4s*)
Multi-task magnificently with the newly reimagined Adorn phone case- brilliantly designed to ensure full access to all phone functions and coordinate colorfully with prints in our Glazed Collection.
Out of Stock
- Overview
- Light sky blue, slate grey and eggshell mosaic-inspired medallion design.
- Decorative plastic case
- All phone functions are fully accessible
- Designed to coordinate with prints from our Glazed Collection
- Fits the iPhone® 4 & 4s*
*iPhone is a registered trademark of Apple®. While being a perfectly polished accessory, the Adorn does not provide complete protection for your phone. It will, however, ensure that your phone is as stylish as you are.
Purchase through us and RETURNS ARE SIMPLE. EXCHANGES ARE FREE.
For more information: Petunia Returns
- Reviews