When you use Mansion Group properties or apps, you trust us with your information. We are committed to keeping that trust. That starts with helping you understand our privacy practices.
This policy describes the information we collect, how it is used and shared, and your choices regarding this information. We recommend that you read this in it's entirety, this overview highlights key points about our privacy practices (including what information we collect, when we collect it, and how we use it).
This policy applies to users of Mansion Group's services anywhere in the world, including users of Mansion Group's apps, websites, features or other services.
Partners: users/companies who Mansion engages into services agreements with as part of fulfilling on our member services.
This policy also applies to those who provide information to Mansion Group in connection with an application to use our services, or whose information Mansion Group otherwise receives in connection with its services (such as contact information of individuals associated with Mansion Group restaurant partners). All those subject to this policy are referred to as "users" for purposes of this policy.
The practices described in this policy are subject to applicable laws in the places in which we operate. This means that we only engage in the practices described in this policy in a particular country or region if permitted under the laws of those places. Please contact us if you have questions on our practices in your country or region.
Mansion Group provides services to users throughout the United States. If you use our services in the United States, Mansion Group Inc. is the data controller for your information.
We process personal information inside of the United States.
Questions, comments and complaints about Mansion Group's data practices can be submitted to Mansion Group's data protection office through email at data@mansion.io.
We process personal information inside of the United States. Mansion Group transfers information of users' outside the United States on the basis of mechanisms approved under applicable laws or when required for user safety or so compelled by government or law enforcement.
Information that you provide to Mansion Group, such as when you create your Mansion Group account through our community advocates, our websites or one of our mobile apps.
Information from other sources, such as Mansion Group partners and third parties that use Mansion Group APIs.
User profile: We collect information when you create or update your Mansion Group account. This may include your name, email, phone number, login name and password, address, payment or banking information (including related payment verification information), government identification numbers such as Social Security number, driver's license or passport if required by law, birth date, photo and signature. This also includes vehicle or insurance information of drivers when relevant or homeowners/renters insurance information. This also includes the preferences and settings that you enable for your Mansion Group account.
Background check information: We may collect background check information if you sign up to use Mansion Group as a tenant, landlord, or special services member. This may include information such as your driver history or criminal record (where permitted by law). This information may be collected by a vendor on Mansion Group's behalf.
Demographic data: We may collect demographic information about you, including through user surveys. In some countries, we may also receive demographic information about you from third parties.
Financial & Credit Data: We may collect information about you, including through third party partners, regarding your ability to pay and other financial and credit information. This information is used solely for the purpose of qualifying you for use of Mansion services in accordance with all applicable laws.
User content: We may collect information that you submit when you contact Mansion Group customer support, provide ratings or compliments for other users, or otherwise contact Mansion Group.
Depending on the Mansion Group services that you use, and your app settings or device permissions, we may collect your precise or approximate location information as determined through data such as GPS, IP address and WiFi.
If you are a driver for one of our Mansion member vehicles, Mansion Group collects location information when the Mansion Group app is running in the foreground (app open and on-screen) or background (app open but not on screen) of your device.
If you are a member and have provided permission for the processing of location data, Mansion Group collects location information when the Mansion Group app is running in the foreground. In certain regions, Mansion Group also collects this information when the Mansion Group app is running in the background of your device if this collection is enabled through your app settings or device permissions.
Members may use the Mansion Group app without enabling Mansion Group to collect their location information. However, this may affect the functionality available on your Mansion Group app. For example, if you do not enable Mansion Group to collect your location information, you will have to manually enter your current location. In addition, location information will be collected from the driver during your trip and linked to your account, even if you have not enabled Mansion Group to collect your location information.
We collect transaction details related to your use of our services, including the type of services you requested or provided, your order details, delivery information, date and time the service was provided, amount charged, distance traveled, and payment method. Additionally, if someone uses your promotion code, we may associate your name with that person.
We collect information about how you interact with our services. This includes information such as access dates and times, app features or pages viewed, app crashes and other system activity, type of browser, and third-party sites or service you were using before interacting with our services. In some cases, we collect this information through cookies, pixel tags, and similar technologies that create and maintain unique identifiers. To learn more about these technologies, please see our Cookie Statement.
We enable users to communicate with each other and Mansion Group through the Mansion Group apps, websites, and other services. For example, we enable drivers and riders, and services partners and recipients, to call or text each other (in some countries, without disclosing their telephone numbers to each other). To provide this service, Mansion Group receives some information regarding the calls or texts, including the date and time of the call/text, and the content of the communications. Mansion Group may also use this information for customer support services (including to resolve disputes between users), for safety and security purposes, to improve our products and services and for analytics.
User feedback, such as as ratings or compliments.
Mansion Group business partners through which you create or access your Mansion Group account, such as payment providers, social media services, on-demand music services, or apps or websites who use Mansion Group's APIs or whose API Mansion Group uses (such as AirBnB or Nest APIs).
Insurance providers (if you are a member and are so required to provide this information).
The owner of an Mansion Group for Business or Mansion Group Family profile that you use.
Mansion Group may combine the information collected from these sources with other information in its possession.
Mansion Group does not sell or share your personal information to third parties for third party direct marketing purposes.
Find relevant offers and properties for you.
Enable transportation, deliveries, and other services to our members.
Offer, obtain, provide or facilitate insurance or financing solutions in connection with our services.
To track the progress of your services.
Enable features that allow you to share information with other people, such as when you submit a complaint about a service provider or property, refer a friend to Mansion Group, split costs, or share your location.
Enable features to personalize your Mansion Group account, such as creating bookmarks for your favorite places, and to enable quick access to previous providers.
Screening tenants and partners prior to enabling their use of our services and at subsequent intervals, including through reviews of background checks where permitted by law, to prevent use of our services by unsafe members.
our Real-Time ID Check feature, which prompts members to share a selfie before entering a property or a shared vehicle. This helps ensure that the member using the app matches the Mansion Group account we have on file, preventing fraud and helping to protect other users.
Mansion Group uses the information we collect to enable communications between our users. For example, a member may text or call another member to confirm a location, or a restaurant or services partner may call a member with information about their order.
Mansion Group may use the information we collect to communicate with you about products, services, promotions, studies, surveys, news, updates and events.
Mansion Group may also use the information to promote and process contests and sweepstakes, fulfill any related awards, and serve you relevant ads and content about our services and those of our business partners. You may receive some of these communications based on your profile as an Mansion Group user.
Mansion Group may also use the information to inform you about elections, ballots, referenda and other political and policy processes that relate to our services.
We may use the information we collect to investigate or address claims or disputes relating to your use of Mansion Group's services, or as otherwise allowed by applicable law, or as requested by regulators, government entities, and official inquiries.
Some of Mansion Group's products, services and features require that we share information with other users or at your request. We may also share your information with our affiliates, subsidiaries and business partners, for legal reasons or in connection with claims or disputes.
For example, if you are a member, we may share your first name, average rating given by other members, and payment history data with other relevant members.
If you are a services member/partner, we may share information with the relevant member including your name and photo; vehicle make, model, color, license plate, and vehicle photo; location; average rating provided by other members; total number of jobs completed; for how long you have been using the Mansion Group app; and contact information (depending upon applicable laws). If you choose to complete a provider profile, we may also share any information associated with that profile, including information that you submit and compliments that past riders have submitted about you. The member recipient will also receive a receipt containing information such as a breakdown of amounts charged, your first name, photo, detailed description of the services completed, and a map of the route you took to their property.
Other people at your request. For example, we may share your ETA and location with a friend at your request, or your trip information when you split a fare with a friend.
Mansion Group business partners. For example, if you requested a service through a partnership or promotional offering made by a third party, Mansion Group may share your information with those third parties. This may include, for example, other apps or websites that integrate with our APIs, suppliers, or services, or those with an API or service with which we integrate, or business partners with whom Mansion Group may partner with to deliver a promotion, a contest or a specialized service.
We love hearing from our users -- including through public forums such as Mansion Group blogs, social media, and certain features on our network. When you communicate with us through those channels, your communications may be viewable by the public.
If you use a profile associated with another party we may share your information with the owner of that profile.
We share information with our subsidiaries and affiliates to help us provide our services or conduct data processing on our behalf. For example, Mansion Group processes and stores information in the United States on behalf of its international subsidiaries and affiliates.
Landlords or property owner organizations.
Homeowners Associations or Condo Owner Associations in which you are applying or live.
Background check providers (drivers and delivery partners only).
Research partners, including those performing surveys or research projects in partnership with Mansion Group or on Mansion Group's behalf.
Vendors that assist Mansion Group to enhance the safety and security of its apps.
Property solution vendors or third party suppliers.
Mansion Group may share your information if we believe it is required by applicable law, regulation, operating agreement, legal process or governmental request, or where the disclosure is otherwise appropriate due to safety or similar concerns.
This includes sharing your information with law enforcement officials, government authorities, airports (if required by the airport authorities as a condition of operating on airport property), or other third parties as necessary to enforce our Terms of Service, user agreements, or other policies, to protect Mansion Group's rights or property or the rights, safety or property of others, or in the event of a claim or dispute relating to your use of our services. If you use another person's credit card, we may be required by law to share information with that credit card holder, including trip information.
Mansion Group may share your information other than as described in this policy if we notify you and you consent to the sharing.
Mansion Group retains user profile and other information for as long as you maintain your Mansion Group account.
Mansion Group retains transaction, location, usage and other information for 7 years in connection with regulatory, tax, insurance or other requirements in the places in which it operates. Mansion Group thereafter deletes or anonymizes such information in accordance with applicable laws.
Users may request deletion of their accounts at any time. Following such request, Mansion Group deletes the information that it is not required to retain, and restricts access to or use of any information it is required to retain.
Mansion Group requires user profile information in order to provide its services, and retains such information for as long you maintain your Mansion Group account.
Mansion Group retains certain information, including transaction, location, device and usage information, for a minimum of 7 years in connection with regulatory, tax, insurance and other requirements in the places in which it operates. Once such information is no longer necessary to provide Mansion Group's services, enable customer support, enhance the user experience or other operational purposes, Mansion Group takes steps to prevent access to or use of such information for any purpose other than compliance with these requirements or for purposes of safety, security and fraud prevention and detection.
You may request deletion of your account at any time through the Privacy Settings in the Mansion Group app, or via Mansion Group's website, or via email to deleteme@mansion.io.
Following such request, Mansion Group deletes the information that it is not required to retain. In certain circumstances, Mansion Group may be unable to delete your account, such as if there is an outstanding credit on your account or an unresolved claim or dispute. Upon resolution of the issue preventing deletion, Mansion Group will delete your account as described above.
Mansion Group may also retain certain information if necessary for its legitimate business interests, such as fraud prevention and enhancing users' safety and security. For example, if Mansion Group shuts down a user's account because of unsafe behavior or security incidents, Mansion Group may retain certain information about that account to prevent that user from opening a new Mansion Group account in the future.
You may also request that Mansion Group provide you with explanation, copies or correction of your data.
The Privacy Settings menu in the Mansion Group member app gives users the the ability to set or update their location and contacts sharing preferences, and their preferences for receiving mobile notifications from Mansion Group. Information on these settings, how to set or change these settings, and the effect of turning off these settings are described below.
Mansion Group uses member's device location services to make it easier to get a safe, reliable ride whenever you need one and to locate properties in your area or other Mansion events. Location data helps improve our services, including suggestions, Mansion member rides, navigation, and customer support.
You may enable/disable, or adjust, Mansion Group's collection of member location information at any time through the Privacy Settings menu in the Mansion Group app, or via the settings on your mobile device. If you disable the device location services on your device, your use of the Mansion Group app will be affected. In addition, location information will be collected from the driver during your trip and linked to your account, even if you have not enabled Mansion Group to collect your location information.
If you have enabled the device location services on your mobile device, you may also enable Mansion Group to share your location with the Mansion courtesy driver from the time you request a ride to the start of your trip. This makes it easier for your driver to pick you up.
You may enable/disable location sharing with your driver at any time through the Privacy Settings menu in the Mansion Group app. You may use the Mansion Group app if you have not enabled location sharing, but it may be more difficult for your driver to locate you.
Mansion Group provides users with trip status notifications and updates related to your account. These notifications are a necessary part of using the Mansion Group app, and cannot be disabled. However, you may choose the method by which you receive these notifications through the Privacy Settings menu in the Mansion Group app.
You may enable Mansion Group to send you push notifications about discounts and news from Mansion Group. You may enable/disable these notifications at any time through the Privacy Settings menu in the Mansion Group app.
Most mobile platforms (iOS, Android, etc.) have defined certain types of device data that apps cannot access without your consent. And these platforms have different permission systems for obtaining your consent. The iOS platform will alert you the first time the Mansion Group app wants permission to access certain types of data and will let you consent (or not consent) to that request. Android devices will notify you of the permissions that the Mansion Group app seeks before you first use the app, and your use of the app constitutes your consent.
After every provider interaction, members and partner providers are able to rate each other, as well as give feedback on how the interaction went. This two-way system holds everyone accountable for their behavior. Accountability helps create a respectful, safe environment for both drivers and riders.
Your member rating is available in the main menu of the Mansion Group Member app.
Your provider rating is available in the Ratings tab of the Mansion Group Partner app.
Provide a detailed explanation regarding the information Mansion Group has collected about you and how it uses that information.
Receive a copy of the information Mansion Group has collected about you.
Request correction of any inaccurate information that Mansion Group has about you.
You can also edit the name, phone number and email address associated with your account through the Settings menu in Mansion Group's apps. You can also look up your services, orders and transaction history in the Mansion Group apps.
We may occasionally update this policy. If we make significant changes, we will notify you of the changes through the Mansion Group apps or through others means, such as email. To the extent permitted under applicable law, by using our services after such notice, you consent to our updates to this policy.


Neural entrapment during uterosacral ligament suspension: an anatomic study of female cadavers.
OBJECTIVE: To describe retroperitoneal neural structures at risk during uterosacral ligament suspension and to estimate risk of neural injury based on uterosacral ligament suspension suture placement technique. METHODS: Uterosacral ligament suspension was performed in 10 unembalmed female cadavers. In each cadaver, bilateral uterosacral ligament suspension sutures were placed using different techniques, as described in the literature. Distances from the ischial spine and instances of neural entrapment were recorded. Biopsy specimens of the deepest (most dorsal) tissue that each suture traversed were immunostained with a nerve-specific (S100) antibody, and the largest nerve diameter was recorded. RESULTS: Median location of sutures relative to the ischial spine did not differ significantly by suture technique. Portions of sacral nerve roots were encircled by uterosacral ligament suspension sutures in seven cadavers. There were no instances of nerve entrapment when sutures were placed while tenting the ligament with an Allis clamp, although these sutures contained a less substantial purchase of connective tissue. In six cadavers, sacral nerves were encircled by sutures placed using a dorsal and posterior arc, regardless of the needle size. In one instance, only the larger CT-1 needle encircled sacral nerve roots. S100 immunostaining confirmed gross findings, with nerve tissue in all specimens (diameter 30-1,225 micrometers). Mean nerve diameter was significantly larger in biopsy specimens in which entrapment was noted grossly (472 micrometers compared with 108 micrometers; P<.001). CONCLUSION: Sacral nerve roots are the most vulnerable neural structures during uterosacral ligament suspension. Suture placement directly into the uterosacral ligament with a dorsal and posterior needle arc results in a higher risk of nerve entrapment compared with ventral tenting of the ligament.


Rare Vintage Casio Programmable Calculator FX-802P with Box, Manual, etc.
Panasonic 554 Advanced Scientific Programmable Calculator JE-554U - Works Great!
Texas Instruments TI-95 PROCALC Handheld Computer, Calculator with Case, Nice!


text:
The ULink Restructure Doesn't Work If You Can Cancel It for Football
Posted on October 18, 2016 October 15, 2016 by Zach Shaner
Sounder Bruce (Flickr)
September 30 was a glorious day for transit ridership in many respects. Link broke 100,000 for the first time, and our system bent but didn't break under the simultaneous pressure of a regular afternoon commute, a Mariners game, and a relatively rare weeknight Husky football game. But the darker side of this is that regular commuters in NE Seattle were thrown under the bus.
We've long supported 2-seat rides in cases in which they strengthen the network, permit greater overall frequency, or offer unquestionable speed advantages, as is the case with Link. But forcing such transfers should come with an explicit guarantee that the network will function no matter the event-related disruption. Reroutes that extend transfer walks beyond a reasonable limit, or that force a 3-seat ride with an intermediate shuttle, are nearly the equivalent of not offering service at all. Choice riders will flee, and the transit-dependent suffer.
Our instincts are all wrong for gameday diversions. We shun the highest capacity and move it far away to let low-capacity vehicles maintain their free and general access. Though the event shuttles are a good and necessary service, and though they queue on Montlake Blvd itself in many cases, general transit availability is more necessary when events cause massive disruptions, not less. If we can't bring ourselves to engineer permanent bus lanes on Montlake yet, we can at least provide them when a capacity crunch demands it.
So a modest proposal: until Northgate Link opens and/or as long as UW Station remains the primary transfer hub in NE Seattle, we should guarantee that we will maintain the integrity of the service network we just overhauled, no matter the event. If we're going to force 2-seat rides, riders deserve to be able to count on them.
79 Replies to "The ULink Restructure Doesn't Work If You Can Cancel It for Football"
PeteyNice says:
That was weeks ago now. I think this article needed to spell out exactly what was changed. If you aren't a Northeast Seattle rider, I doubt you remember. And even then, you likely only remember what happened to your bus.
http://metro.kingcounty.gov/up/spclevent/huskies/pdf/uw-map-sept30-reroutes.pdf
The re-routes for Friday, September 30 were similar to the weekend game re-routes. The main differences were (1) who operated the shuttles, from where, and the RSVP requirement; and (2) how many regular transferrers were impacted.
It would be easy for UW to agree to not play any weeknight games until Northgate Link is open, if it weren't for the potential money they'd be foregoing. But weekend commuters would still be getting disrupted, having to transfer to an extra semi-frequent shuttle between Campus Parkway and UW Station.
After the first year of data with the new situation, I hope Metro and UW can agree to let more regular routes keep their normal path, and to find a better place to let the shuttles lay over than in the middle of Montlake. Bus-only-lanes-for-the-day would help immensely.
huskytbone says:
The UW's schedule is set by the PAC-12, and ESPN has first rights to certain time slots. They don't get to "agree" with it.
The problem was not the event shuttles but the fact that regular bus service was completely eliminated south of NE 55th Street, east of 15th Ave NE, and on Pacific Street except those that cross the Montlake Bridge (48, 271, suburban expresses). That turned an already barely-acceptable quarter-mile gap between UW Station and the 75 and 372 into a half-mile gap (via Pacific Street) or mile gap (via Montlake Blvd). And all they gave us was this lousy 7 1/2 minute shuttle from UWay & Pacific. Just six months ago Metro recognized the extreme importance of the Pacific Street gap and saturated it with buses every 2-3 minutes., and now on game day they think 7 1/2 minutes is enough for the even larger crowds?
The Storm That Wasn't also made me realize another problem with the 75 and 372 transfer. The eastbound stop on Stevens Way has no bus shelter, so if it's raining and windy you have to stand in it for possibly 15-30 minutes. That didn't happen to me because I avoided the area, but i realized that sometime this winter I may not be able to avoid it. A major transfer stop needs a roof.
"The UW's schedule is set by the PAC-12"
The PAC-12 probably doesn't specify the minimum amount of SOV access.
The ultimate problem is that northeast Seattle is a constrained area, with only two four-lane roads to access it south of 65th. The stadiums are right next to a freeway and several 4-6 lane truck roads so they can absorb a lot more crowds.
Inquiring Mind says:
>The ultimate problem is that northeast Seattle is a constrained area, with only two four-lane roads to access it south of 65th.
Which is why we desperately need a *local stops* East-West subway, thank you very much.
Actually, the stadiums are next to two freeways. Or three if you count the stub end of 99 south. (Soon with an extension to Mercer Street! Another win for the DBT: sports-fan access from north Seattle. Please pay the toll with your ticket.)
Michael H says:
The shuttles aren't the whole problem, but they are part of the problem. There effectively are bus-only lanes, but they are for parked buses. Would be nice to use them for moving buses so the regular routes can bypass the mess without significant reroute.
"The eastbound stop on Stevens Way has no bus shelter, so if it's raining and windy you have to stand in it for possibly 15-30 minutes."
If you're going to be standing there for more than a couple of minutes, just walk 300 feet to the southwest to the next stop over, which has a nice, big shelter.
There's no reason to be at the Rainier Vista stop if you're taking the 75. If you're coming from campus, just walk to the stop at Okanogan Lane or the HUB like asdf2 said. If you're coming from UW Station, just take the 65 and transfer at U Village. You're more likely to not be passed by a crushloaded bus and it saves you the walk up Rainier Vista.
Still a problem for 372 riders though. Or riders heading to Fremont on the 31/32 or Northgate on the 67. Since there is inexplicably no bus that travels from UW Station to Campus Parkway without needing to walk at both ends.
"If you're coming from UW Station, just take the 65 and transfer at U Village."
That's two waits of up to 15 minutes each with just a mile between them. It can turn a three-seat ride into a four-seat ride.
"You're more likely to not be passed by a crushloaded bus and it saves you the walk up Rainier Vista."
I've never seen a crushloaded 75. And the fullest ones I've seen are westbound rather than eastbound.
And it's not just for big events. For routine closures of Stevens Way for construction, they route the 75 to 45th, away from UW station, which is insane. That forces another transfer or a 1 mile walk. Is there any rationale to this at all?
The choice of where to re-route route 75 is what is insane. It remains on Stevens Way because that path is supposedly faster for most riders, as well as for the route. It ought to be able to move to Pacific/Montlake when Stevens Way isn't available.
I think Montlake is snow route for the 75, too. Weird that it re-routes to 45th.
Jeff Pittman says:
Montlake is also the snow route for the 372. If you are not familiar with the UW campus it is uphill from 25th Ave NE to Stevens Way and there is no way buses would make it up that street if it is covered by snow and/or ice.
All the routes that normally take Stevens Way, 45th, or 55th switch to Montlake and Pacific when it snows. The car traffic shrinks enormously so it can all fit into one lane without congestion.
Excuse the grammar, I was using a buggy Bluetooth keyboard.
Mark Dublin says:
Who exactly made the decision to do this to bus service? Was it made under a specific threat from the University of Washington? If so, can the public see the language verbatim? And whatever the reason, what can the voting passenger public do to prevent a recurrence?
Thanks for the posting, Zach. Could be most important one this year, because I doubt this is the only time this problem is intended to happen. If somebody is looking to quietly set any kind of precedent which passengers are supposed to just get used to, first step for transit is to remove the "quiet" part.
Mark Dublin
Skylar says:
No idea, but last time I checked, the city owned Pacific St, and the city and state jointly operate Montlake Blvd (AKA SR-513). The city should take two lanes on Pacific and Montlake for bus-only lanes. If UW balks, the city should threaten to use its parking enforcement and police officers to trickle out SOVs at a rate low enough not to impact other traffic. If it means there are people stuck in the parking lots until 2AM, well, I guess they should have taken transit (or walked, biked, etc.).
The streets are publicly owned, and it's simply insulting that we're made to suffer so that the UW football coach can make his millions.
Scott Stidell says:
This service was MANDATED by the City when the stadium was expanded in 1987 and has operated ever since. Buses have served game day crowds (and have been staged at or near the Triangle) since at least 1956 (I have a game day map from that year). Because so many fans take the bus service–i.e. it's a SUCCESS–they have to have the buses stay somewhere. On Saturdays it's not the world's biggest problem because traffic on Montlake is minimal, relatively speaking, and flows reasonably well until the streets become contraflow away from the stadium for an hour or so following the game.
The Montlake problem is a City problem, and one they have studiously avoided trying to fix for eons. Montlake should absolutely have transit only lanes, 24/7, each direction–even if it means (gasp!) widening the street. It's a major route and chokepoint for all of NE Seattle and it is unusable several hours out of every day. The UW isn't going to have an issue with it; their campus master plan involves removing most of the parking along Montlake for new construction anyway, which would be better served by transit. To reiterate: the CITY mandates a vast additional transit service, won't allow the road to be widened and won't form defacto transit lanes during the seven days a year that games occur.
Again, this was the second weekday night game in 71 years. The UW has fought the conference more successfully in this regard than any other program – they don't want the night games either. Most schools have had several and most Pac-12 schools are in areas urban enough that traffic and transit is affected during weekday games.
Maybe rather than parking hundreds of buses on Montlake and Pacific for the Husky shuttles, they should make those lanes transit only throughput and park the coaches in the E3 lot or behind the hospital. They could have someone there with a radio dispatching them one at a time as needed. They would use bus only lane created by not parking them on the shoulder to get to the pickup spots.
I don't know…they do this all the time (and I've never used any of the shuttles for a Husky game), so I tend to think Metro has a good system that works well for dealing with their shuttles, but the queing of the shuttles takes up a lot of capacity from Montlake that could potentially be used to send the regular routes through – bypassing the private vehicles.
MrZ says:
Gotta queue the buses up somewhere and I doubt the UW wants to loose the revenue generated by the E3 lot on a game day.
Yeah, and I'm sure the UW would rather not pay the cost to subsidize the shuttles, but they do. They also may be willing to reduce some of the parking revenue to improve the transit situation .
If metro decided they needed that space on the street, they or the city could also require the UW shuttles be queued somewhere other than on the city streets.
????? says:
shuttles Should queue And load at mason rd. Same place UW stores non-metro buses for big on-campus events
Thank you, my thoughts exactly. Cars and shuttles are by their nature, flexible and frankly one time means of transport which needs to fit around standard fixed routes. And isn't the idea to build upon public transit first, rather than create a whole new shuttle network before every event? After North Link, wouldn't the idea be to run a mosquito fleet of small shuttles to Link stops leading to HSS?
That way when there is a call to use public transit, public transit isn't swamped.
Slowrider says:
I am one of the NE Seattle transit-dependent riders who advocated for the 2-seat ride and value of "the grid"
Geographically, Husky Stadiium station will always be my point of transfer to Link (i.e. N'Gate etc opening has no effect)
I agree with Zach.
It depends on where you are. If you're north of 55th Roosevelt Station is much better, and the 62 makes that possible. When RapidRide 44 goes through to Laurelhurst it will make U-District Station viable without the campus crawl, and that will be more convenient for those who can take it.
eddiew says:
Route 44 may not be extended to Children's. It is a line in a plan.
I think they will probably re-orient a lot of NE Seattle service at a transfer point around U-District station. Or at least I hope they do. They can send buses down the NE 45th street viaduct with speed and simplicity, without having to reroute for construction or even games. I really hope that Metro decides that people who are going places in NE Seattle, use the bus, and would like some speed and simplicity are a bigger priority than saving young energetic UW students some walking on campus by rerouting every bus directly into Stevens Way like their own personal UW taxi-cab.
I just remembered, Metro wants to reroute the buses on campus. So they would come up the Pend Orielle hill and then turn right instead of left on Stevens Way, going past the north campus dorms and the Burke Museum to 43rd Street and the station. But it would require a new road since the part south of the Burke is a sidewalk in grassy open space with stairs down to 15th. So it remains to be seen whether the UW will consent to it. However, I think the UW has its own reasons for wanting to get buses off lower Stevens Way, so those may coincide. I thought that developing open space would be an absolute blocker, but the UW itself has been putting buildings in open space and its new master plan has a lot more buildings, so maybe the space at 42nd isn't sacred.
Here's a concrete example. In the LRP EapidRide 44 and Frequent 75 and 65 all overlap from Children's to 25th. If you're coming southbound on a 75 or 65, who will:
A) Get off at Rainier Vista and do the 5-minute walk to UW Station.
B) Ride all the way through campus to U-District Station.
C) Transfer to RapidRide 44 with a maximum 5-10 minute wait but a straight shot to U-District Station and no campus/Montlake congestion?
The UW Board of Trustees and the City of Seattle ought to prohibit the "Athletics/Show Biz" Department from staging weekday football jousts at their Montlake Dog House. National TeeVee is far less important than running an effective transit program. Saturdays should suffice.
You forgot the money that alumni season-ticket holders bring, and not just the direct income from tickets and concessions, but Husky Fever is also a way to recruit them into giving estate grants and other large sponsorships.
The Pac12 Conference has contracts with Fox and ESPN where each school has to host a weekday night game and the UW has told the conference that it will do so the minimum number of times allowed in the contract. The game on September 30th was the first one since the UW hosted UCLA on a Thursday evening about 4 or 5 years ago. The UW is very much aware the impact a weekday games has on the traffic and accessibility to the stadium area which is why they minimize the number of weekday games they will host
The City Council could set up a situation where a court has to determine which is stronger, a city ordinance or a private contract…
The UW is a state entity. If it can't override the ordinance it can ask the legislature to pre-empt it, saying football is essential to the university's financial well-being. And Montlake Blvd is a state highway.
Hopefully, UW and Metro will be able to reduce the size of the problem next year by not running shuttles all the way to UW from Federal Way, South Renton, and Eastgate.
A shuttle from Federal Way to Angle Lake Station might help, if the Angle Lake parking garage is filling up on game days. Then find a local layover site willing to help out, on the cheap.
South Renton shuttle service should connect at Rainier Beach Station, and then cut a deal for cheap layover space at Rainier Beach High.
Eastgate service may as well head downtown and connect at International District / Chinatown Station, enabling the shuttle buses to lay over at base.
Then, come up with an arrangement for Link to honor shuttle passes as day passes for those days.
This would reduce the shuttle fleet needing to get to the stadium by roughly 1/3, I suspect.
And feeding all these riders into an already full LINK train is going to accomplish what? You may save the need from parking coaches at the UW, but you are going to have a bunch of pissed off riders who can't get on trains. The STB and it's commenters is famous for throwing out all sorts of ideas about truncating routes to feed into LINK, some of it makes sense and most of it does not. They also fail to fully address the transfer penalty, travel time penalty, and most importantly the capacity issue. If you had 3 or 4 buses terminate at a LINK station and all were full, that's 180-240 people making the transfer alone, plus having to contend with all of LINKS existing ridership…
MrZ, tempting to say that LINK advocates and implementers deliberately withheld critical information about urban rail transit worldwide.
But think it's more likely that a lot of the planners came from vast majority of the world's transit systems, who just assume everybody knows that if anybody can get a seat on either game day or ordinary rush hour, you permanently cancel the train for lack of ridership.
At one time early on, I think cars were reserved for ladies. Maybe because local early-1900's Harborviews nationwide could no longer handle all the hat-pin wounds to men whose hands should have been on stanchions or straps.
Though I suspect that anyone suggesting these special arrangements to ladies now would immediately become entitled to special seating due to disability. Also good future-demand fashion metric to ladies' hat designers as to how many hats still have pins.
But I also think that as word gets around about standing fast rides versus seated slow ones, horizontally as well as vertically, people prefer 60 mph elevators to stairs. Or stationary chairs on motionless tires.
Glenn in Portland says:
The current light rail cars are rated at 200 people each, but let's call it 180 because people won't pack that tightly into them under most situations.
If you are running 3 car trains every 6 minutes you get 10 trains per hour.
That's 5,400 per hour. You can't count traffic in both directions because this is an end station and its right at the arena.
For a 70,000 seat stadium, that's not especially great capacity.
Get this up to 28 trains per hour (what MAX does on the surface near the Moda Center arena) with 4 car trains and you've got closer to 20,000 per hour.
Either way, you're dealing with limits imposed by this being an end point station for the time being.
ST does not have enough LRV for what Glenn suggests. They have 62 cars. They can use four-car trains in 2021. today, at six-minute headway, they can use a mixture of two and three cars.
Lazarus says:
@eddiew
ST could put more LRVs in and out of Husky Stadium if the buses were out of the DSTT. Do that one thing and ST could interline a second line from HSS to SS with 3-min headways. That would put more LRVs and more LRV service hours were they are needed. And overall reliability would go up to.
But this situation is temporary. Buses come out of the DSTT soon, and in 2021 (hopefully 2020) HSS will no longer be a terminus.
They just ordered new Link trains last month, to be in service in 2019, so I think in 2019 they can run all 4-car trains. It's a pain that it will be a terminus until 2021, but the 4-car trains alone will be an immense improvement.
FTA requirements for spares ratio planning is for normal peak service levels. Special events and unusual circumstances fall outside this.
62 cars is enough for 20 three car trains plus two spare cars.
The problem is not the shuttles, it's the SOVs. What if UW banned non-VIP cars from the Montlake parking lot and greatly expanded the shuttles to other parking locations? Or we could do like the East Coast does and encourage everybody to take high-capacity transit to the game from their local P&Rs once ST2 is built out.
The UW discourages fans from driving to the stadium by subsidizing the shuttles from the various park and ride locations and by charging large fees for parking near the stadium. They also pay Metro for the shuttles from Ballard and Lake City.
For cars with at least 3 people it cost $30. For 2 people or less it is $40. RV's and motor homes it is $120.00.
If you have a trailer attached it will be an additional $30.
Engineer says:
Jeff Pittman, if tens of thousands of people are willing to fork over hundreds of dollars PER SEAT to see the football game, I somehow doubt that a $10 to $20 per person parking fee ($30 to $40 split between the vehicle occupants) is going to discourage driving a personal vehicle to the game. Most people go in small groups or with a significant other. They need to make the cost to park privately significantly higher than the cost to take the shuttle, especially on a weekday night game. Call it a congestion convenience charge. Or, perhaps, they should just start expanding the campus into the parking lots and eliminating parking spaces. They are sitting on free real estate and using it as a parking lot!
The new UW master plan does envision several buildings in the Montlake lot.
@Engineer,
You would be surprised what discourages people from driving to the games.
I have a neighbor who has season tickets for the Seahawks and I went with him to a game this season. The tickets cost $140 a ticket and he has 2 tickets. For the season he pays $2,800 for 10 homes games as he is required to buy the tickets to the pre-season games.
When we went he parked in a garage uptown about a 20 minute walk each way to the stadium because it only charged $7 to park versus other garages and lots closer to CenturyLink Field which charged anywhere from $30 to $50 which were posted on signs as we were walking to the game. He parked in that garage because he wasn't going to pay that much money to park closer.
So he was willing to pay the $2,800 for the tickets but not more then he has to for parking.
Al Dimond says:
The price of parking is, realistically, irrelevant to traffic congestion as long as the size of the parking lot is constant and it fills up (or comes anywhere near that). It doesn't matter if the price is so high that a lot of people won't pay it. If a full lot holds enough vehicles to cause congestion, the only way to relieve that congestion is to effectively shrink the lot — by physically shrinking it, by limiting the number of spaces that can be used for event parking, or by charging so much money that the lot is left half-empty. It's hard to imagine any rational parking lot owner doing any of that, so any shrinking would have to come via regulation.
The same thing, of course, applies to rush-hour traffic and office parking. But where the city might be able to claim the authority to regulate the overall number of office parking spaces available, UW fights every attempt at city regulation on principle and often wins. So regulating UW event parking would probably require state help; because the Montlake Bridge and Montlake Boulevard are in the state highway system this is plausible, but it doesn't seem politically likely.
UW has a great tailgate tradition. You'll never ban SOV cars. E1 is going to be around a long time.
Also, E1 is built on a landfill. To build anything on it would require a lot of expensive mitigation.
New tradition: Tailgate on Capitol Hill!
It will require mitigation but the university is planning to put several buildings there anyway. Not right away but in the next few decades.
@Brent: Can't, there's no parking there. Don't you read the Time's comments about how nobody goes to Capitol Hill because there's no parking? ;)
@Mike: I've seen that master plan, but like all master plans, I have to wonder if that's just a pie in the sky. Currently, E1 is a net positive revenue source, with little to no maintenance necessary. I would think it would make more sense for the UW to expand north and west of campus before attempting the expensive mitigation of a landfill in a swamp, to build on it.
Granted, U-Village did it, but well before some of the more stringent mitigation laws came into effect.
The solution to full Link trains is to run more of them. That's the usual practice after major events.
September 30 was an outlier because the Mariners were playing a must-win game simultaneously. If UW won't work with others' schedules, the M's, Sounders, and Seahawks can certainly pay attention to the Huskies' schedule in the future. The latter three work with each others' schedules quite commendably, and even pay attention to when Torchlight Parade is happening.
ST could have run trains even more frequently before and after, if it had a larger fleet available (as it will by 2020). Former shuttle riders won't overwhelm Link's capacity, but merely partially make up for the M's crowd that will hopefully never compete with the Huskies' crowd again.
And if a few dozen passengers have to wait five minutes for the next train? Crying over that requires the world's smallest violin.
The schedules for the M's, Sounders and Seahawks are done by their respective leagues and the UW schedule doesn't come into play or is taken into consideration.
In the case of the M's and Seahawks they cannot play at home on the same day. With the M's and Sounders they sometimes have home games on the same day but one will be in the afternoon with the other in the evening and they try to have a least 3 to 4 hours between the end of one game and the start of the other games.
As far as the Torchlight Parade the M's if they are scheduled at home on that Saturday will play in the afternoon and they do so because some of the streets in the stadium area are closed as it is the end of the parade route.
The Sounders do the same thing if they are scheduled at home on that Saturday. In the case of the Seahawks no problem as their first pre-season game is not until around the middle of August.
It cost $5.00 for a roundtrip on the Husky Shuttles and people are not going to pay that if they are forced to transfer to Light Rail somewhere along the way with no guarantee that there will be room for them. Also the shuttles do no accept transfers, passes, Orca and UPASS cards.
This is similar to the shuttles for the Seahawks games except for those games the shuttles only come from the Northgate Transit Center, South Kirkland P&R and Eastgate P&R and for the Seahawks games it is $8.00 roundtrip.
In both cases the shuttles are subsidized by the UW and Seahawks.
That is a point. In European countries a ticket to a sports event or trade conference sometimes doubles as a transit pass for trains to the venue or even the city's entire transit network. No $5 fee involved, pay as you enter.
Jeff, thanks for calling attention to a signature non-problem. King County Executive just has to call UW and tell them that anybody with a problem with the buses they rent using ORCA and UPASS cards can rent buses from somebody else.
If King County Council itself is setting the anti-ORCA policy, phone system handles recall campaigns too. Not like you don't have a block of regular riders already in a combative mood because they're football fans. Some of them can even steal intimidating cheese wedge hats from Wisconsin.
But really, considering traffic hassle and parking prices, I think most riders, who do have choice of driving, don't consider an extra $5 or $8 on their travel fare a deal-killer. Though any crap about putting whole thing on ORCA oughta get somebody killed!
And with game-day operations, one train missed leaves you first in line for next one five minutes later. Probably get a seat too. In other words: Brent, be patient. Average passenger's great grandfather got the family's last transit ride.
But UW music department can certainly arrange their students' first-hand experience in the only paying career reliably open to most of them.
Not major budget item just to give every student about ten dollars in one's to stuff their hat with as they comfort transfer-misery with the 19th century's most depressing nocturnes and dirges. Though the cash they'll collect to make them stop will let the music department bail out the athletic program.
Thanks, SounderBruce, for the escalator picture! Once Northgate Link opens, ST is clearly going to have to let the down escalators at UW Station become stairs before Husky football games.
It is probably unsafe to do so. May even be against the manufacturers recommendations, which would be grounds for a lawsuit, and the defendant would not win that.
Maybe have three escalators going up and one going down before the game, and the reverse after the game.
It's actually pretty common to shut them down in crush load situations. What's more dangerous, people getting crushed at the bottom of the escalator or someone maybe slipping on a step.
I also don't understand why there is a belief that it is more dangerous for people to walk up/down a stationary escalator than a moving one. There are no signs posted that say people should not walk on the moving escalator (or do so at there own risk). The liability issue is a straw man.
@Michael,
Before the UW game, I got scolded by a Securitas rent-a-cop for walking down the escalator. Seattle has gotten very good about walk-left-stand-right, so I have no idea why he felt this was his job. I just ignored him and kept walking down the escalator.
Brent, considering how long and steep those escalators are at UW Station, I don't think they'll make especially good staircases. Especially if they have to handle foot passengers in both directions. One thing worth investigating, though. They may have a mechanism for manually reversing direction.
In that case, station staff, who should be directing escalator users in any case, could also coordinate escalator boarding, and handle the reversing switch. One load going up alternating with one coming down. Also, I think busier system have experience in the most efficient escalator use.
Have read, for instance, that if passengers just board the escalator and ride, rather than Stairmaster mode, everybody has a faster trip.
Dws says:
What about cars? They were only restricted on Pacific?
This is yet another reason why it would be better to maintain the Montlake Flyer stations on the mainline of SR-520. Prior to Husky games most people coming from the Eastside shuttles (I believe Eastgate, S. Renton, S. Kirkland and Houghton all come via 520) as well as routes 255/545 drop off their passengers here. There is really no reason for those shuttles to go any closer to the stadium pre-game. In the new lid configuration all those buses will have to exit on the lid and get drawn into even more congestion on Montlake Blvd.
Zach: please consider the blockage of University Way NE for the farmer's market. Similar issue of less magnitude.
Nick Barnard says:
Not really, the buses move over one block. Its not ideal but its not as if they've moved it multiple blocks and a huge hike away from a major transit connection point.
chuck ramquist says:
"Too much Transit at the UW", I can't believe people on this blog are complaining
We could have solved all this if someone had had the foresight to run a third-world-style bus rapid transit route through campus before all the buildings were constructed.
They're complaining about too little transit in the surrounding neighborhoods.
UW should take some responsibility of getting people in and out of their stadium — because they collect all that ticket gate revenue in the first place! Hire more traffic people! Hire more people to direct transit riders! ST and Metro should help, but frankly UW should have it's feet held to the fire. This is a UW-created problem, and UW needs to correct it on their dime!
As far as the U-Link restructure goes, it's in UW's best interest to both provide a fast way in and out for non-game-goers to the UW Station during game days, especially because some of those are UW students or staff! Whether that's to change the way that Stevens Way operates, to set up a transfer facility away from stadium traffic back-up or something else, UW is the one that has to take the primary role.
SeaStrap says:
Christopher Burke says:
I agree with this posting 100%.
Matt the Engineer says:
Brainstorming here: Tiny gondola line from the flyover stops to the station, then either up the hill to campus or to the medical center – and maybe up to 45th near I-5. Gives you <1 minute wait, 3 minute total trip time transfer from Link to 520 trips. And perhaps could connect I-5 trips to the station without dealing with traffic.
Honestly I don't know much about transit routes and patterns at this hub*, so I'm just throwing this out there.
* though I've sat in a car seemingly forever on Montlake after choosing the wrong route on game day.
I was pondering this again since I got an email about this weekend's reroutes..
I still prefer that the buses stay right where they are, and that Montlake should get game day bus lanes. (I'd also consider moving the routes upto Stevens Way as an acceptable alternative to the buses staying on Montlake.)
That being said, if Metro can't get the bus lanes, instead of running this silly shuttle to UW Station, they should run two shuttle bus routes to where people want to go: Capital Hill Station and Downtown. It'd still be an extra seat for those who are going south of IDS, but at least it avoids the crowd at UW station, and gets more people going where they'd want to.
Put the Downtown shuttle in the DSTT and run some signage on the tunnel advising people who want to transfer to use the shuttle instead.
For people who would be connecting to other busses at UW station, all of those busses are rerouted into the same area around the U District, so they could (and should!) connect there.
Previous PostPrevious Things Are Looking Up for Pierce County Transit Riders
Next PostNext Podcast #27: Centrifugal Forces

redpajama_set_name: RedPajamaCommonCrawl


Designed with an attached center flap to provide more compartments for credit/ID cards and cash compared to other diary type cases out there, eliminating the need to carry a separate wallet.
Earpiece cutout allows you to have phone conversations with the cover closed. Designed and manufactured with precise cut-outs & perfectly molded to hold your device in place without restricting use of the device's camera and buttons.


text:
Sociedade Esportiva Queimadense é uma agremiação esportiva de Queimadas, no estado da Paraíba, fundada a 15 de novembro de 2003.

História
A equipe, filiada à Liga Queimadense de Desportos e à Federação Paraibana de Futebol, foi fundada em 15 de novembro de 2003, porém só estreou no profissionalismo em 2007, ano em que se sagrou campeã paraibana da segunda divisão. Este feito teve importante participação do Treze Futebol Clube, através de uma parceria firmada com a prefeitura de Queimadas, em que cedeu treinador, alguns jogadores profissionais
para o clube e também o Estádio Presidente Vargas, em Campina Grande, para mandar suas partidas.

Jogou a primeira divisão entre 2008 e 2010, quando foi rebaixada. Voltou em 2014, ficando em 9º lugar e novamente caindo para a Segunda Divisão do ano seguinte, a qual não chegou a disputar, optando pelo licenciamento.

Para 2018, chegou a desistir de jogar a Segunda Divisão estadual por falta de estádio, mas voltou atrás e decidiu sediar os jogos no Estádio Romerão, no distrito de Galante.

Em 2021, a equipe mandou seus jogos no Estádio Municipal Moura Filho, em Alagoinha, tendo Jairo Santos como treinador, chegando até as quartas-de-final, sendo eliminada pelo Auto Esporte com 2 derrotas (1 a 0 e 2 a 0).

Em 2022, a Queimadense as outras 9 equipes participantes da Segunda Divisão jogaram naToca do Papão, em Sapé, devido à falta de condições nos estádios dos clubes. O Carcará integrou o grupo B juntamente com , , Serrano e , terminando a primeira fase como líder da chave, com 19 pontos. Após eliminar  e Picuiense nas quartas de final e na semifinal, enfrentou o Serra Branca na decisão, disputada em 2 partidas - perdeu o primeiro jogo por 2 a 0 e no segundo, que ocorreu no estádio Carneirão, em Cruz do Espírito Santo, venceu por 2 a 1 e terminou com o vice-campeonato.

Títulos

Elenco

Ver também
 Campeonato Paraibano de 2008

Links
 Sociedade Esportiva Queimadense

Clubes de futebol da Paraíba
Clubes de futebol fundados em 2003
Queimadas (Paraíba)
Fundações na Paraíba na década de 2000

redpajama_set_name: RedPajamaWikipedia


text:
Q: How to avoid problem in progressbar when multithreading I'm trying to show multithreading process with progress bars so I used "tqdm"
and this is my code:
from time import sleep
from tqdm import tqdm
import threading

def one():
    for i in tqdm(range(11)):
        sleep(1)
def two():
        for i in tqdm(range(11)):
            sleep(1)
def three():
        for i in tqdm(range(11)):
            sleep(1)

if __name__ == "__main__":
    t1 = threading.Thread(target=one)
    t2 = threading.Thread(target=two)
    t3 = threading.Thread(target=three)

    t1.start()
    t2.start()
    t3.start()

    t1.join()
    t2.join()
    t3.join()

After running the code in CMD I've seen this:
G:\>python thread2.py
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.01s/it]
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.01s/it]
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.01s/it]
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.01s/it]
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.01s/it]
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.02s/it]
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.02s/it]
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.01s/it]
G:\>

100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:11<00:00,  1.02s/it]

I wanted only 3 progress bars but as you see, there are 9! How to avoid this problem?

redpajama_set_name: RedPajamaStackExchange


You can make someone feel like a million bucks with just these two simple words! The best part is that is doesn't cost you a nickel or even a moment of your time! Just click to send or share this beautiful emoticon and you can be the most wonderful and most thoughtful guy in the world!


I am happy to announce the Dual 5 Update development has almost reached its completion. Therefore, we are releasing half of the Update on the Beta Server. If everything goes well, the second half will be released this very Sunday (still on Beta).
- Rework of the Monster War to make it more fun and rewarding.
- Max Tactics level increased to 220.
Both parts also contain changes regarding other (smaller) features. The full changelogs will be available as the updates go on.
We will take a few extra days to complete the Part 2 update from the feedback we've received.
This means we won't be releasing it today (sorry) but most likely either Tuesday or Wednesday.
Sorry to announce that but it'll take a few extra days, again.
Real life stuff have been keeping me busy the last two days, therefore I couldn't progress much on the patch. Hopefully this Thursday or Friday the part 2 will be released on the Beta Server.


text:
Q: Django inline - allow adding disable editing Hi. I am asking this question after reading the following questions: Question_1 and Question_2. Question_1 doesn't have any appropriate answers and Question_2 is having an alternative solution but not a perfect solution.
Here I have two models and admins for them.
models.py
class TaskList(models.Model):
    task_name      = models.CharField(max_length = 255, unique = True)
    description    = models.TextField()
    assignee_role  = models.ForeignKey(Group, related_name = "assignee_roles")
    assignee_name  = models.ForeignKey(User, related_name = "assignee_names")

    def __unicode__(self):
        return "%s" % (self.task_name)

class TaskComments(models.Model):
    tasklist = models.ForeignKey(TaskList)
    time     = models.DateTimeField(null = True, blank = True)
    comment  = models.TextField()

    def __unicode__(self):
        return ""

    def save(self, *args, **kwargs):
        self.time = datetime.datetime.now()
        super(TaskComments, self).save(*args, **kwargs)

admin.py
class TaskCommentsInlineAdmin(admin.TabularInline):
    model           = TaskComments
    can_delete      = False

class TaskListAdmin(admin.ModelAdmin):
    inlines      = [TaskCommentsInlineAdmin, ]

    def add_view(self, request, form_url = '', extra_context = None):
        self.readonly_fields = ()
        return super(TaskListAdmin, self).add_view(request, form_url, extra_context)

    def change_view(self, request, form_url = '', extra_context = None):
        self.readonly_fields = ('task_name', 'description', )
        return super(TaskListAdmin, self).change_view(request, form_url, extra_context)

Here the model TaskComments is being used as inline in TaskList.
SCENARIO 1
Here what I want to achieve is:
When Adding task comments

*

*Hide the field "time" and update it in backend.

*Able to type "comments" and save.

When opening after saving comments

*

*Both "Time" and "Comments" field should be visible and readonly for already added comments.

*Able to add new comments as described above.

SCENARIO 2

*

*Same as previous scenario.

*The only addition is, the comment should be editable for the user who added it and readonly for all other users. (I can update and get the user who adds the comment).

These are the things I would like to achieve. I have tried using add_view and change_view in admin. But they are not working for inline. Please provide a solution to achieve these things. Thanks in advance.

A: You have to use the custom version InlineAdmin which uses the custom version of below classes

*

*InlineModelAdmin

*BaseInlineFormSet

You can add your own add_view and change_view on the custom version of InlineModelAdmin to

*

*detect the owner of the record(to allow the edit)

*display the time field

You can enhance the  BaseInlineFormSet to control all the runtime aspects


text:
A study of phase-steepened Alfvén waves in a high-speed stream at 0.29 AU
P. Alexander
Ann. Geophys., 18, 845–851, https://doi.org/10.1007/s00585-000-0845-9,https://doi.org/10.1007/s00585-000-0845-9, 2000
Latitudinal distribution of the solar wind properties in the low- and high-pressure regimes: Wind observations
C. Lacombe, C. Salem, A. Mangeney, J.-L. Steinberg, M. Maksimovic, and J. M. Bosqued
Ann. Geophys., 18, 852–865, https://doi.org/10.1007/s00585-000-0852-x,https://doi.org/10.1007/s00585-000-0852-x, 2000
Connections between whistlers and pulsation activity
J. Verö, B. Zieger, J. Szendröi, M. Vellante, J. Střesğtik, H. Lühr, A. Best, A. Körmendi, J. Lichtenberger, T. Ménesi, P. Bencze, F. Märcz, and V. Wesztergom
About the relationship between auroral electrojets and ring currents
A. Grafe and Y. I. Feldstein
Central polar cap convection response to short duration southward Interplanetary Magnetic Field
P. T. Jayachandran and J. W. MacDougall
Ann. Geophys., 18, 887–896, https://doi.org/10.1007/s00585-000-0887-z,https://doi.org/10.1007/s00585-000-0887-z, 2000
Interhemispheric observations of nightside ionospheric electric fields in response to IMF Bz and By changes and substorm pseudobreakup
T. K. Yeoman, R. V. Lewis, H. Khan, S. W. H. Cowley, and J. M. Ruohoniemi
Observations of ionospheric flows and particle precipitation following a Sudden Commencement
E. Nielsen and F. Honary
Ann. Geophys., 18, 908–917, https://doi.org/10.1007/s00585-000-0908-y,https://doi.org/10.1007/s00585-000-0908-y, 2000
Comparison of the orientation of small-scale electron density irregularities and F region plasma flow direction
E. D. Tereshchenko, B. Z. Khudukon, M. O. Kozlova, O. V. Evstafiev, T. Nygrén, M. T. Rietveld, and A. Brekke
Annual and semiannual variations in the ionospheric F2-layer. I. Modelling
L. Zou, H. Rishbeth, I. C. F. Müller-Wodarg, A. D. Aylward, G. H. Millward, T. J. Fuller-Rowell, D. W. Idenden, and R. J. Moffett
Annual and semiannual variations in the ionospheric F2-layer: II. Physical discussion
H. Rishbeth, I. C. F. Müller-Wodarg, L. Zou, T. J. Fuller-Rowell, G. H. Millward, R. J. Moffett, D. W. Idenden, and A. D. Aylward
The role of vibrationally excited nitrogen and oxygen in the ionosphere over Millstone Hill during 16-23 March, 1990
A. V. Pavlov and K.-I. Oyama
On the possibility of ion-drag to induce dynamic instability in the lower thermosphere neutral gas
C. M. Hall
A modelling study of tropospheric distributions of the trace gases CFCl3 and CH3CCl3 in the 1980s
K.-Y. Wang and D. E. Shallcross
Hysteresis of foF2 at European middle latitudes
D. Burešová and J. Laštovička


text:
Q: Best Resources to learn OO Design and Analysis I am looking for the best resources, videos, books, magazines(I like videos) to learn and master Object Oriented design and analysis. I would really like to know more about trusted and reputable methodologies for structuring your programs, designing classes, and dealing with databases in your programs. So, my question is what are the best resources?
thanks

A: The 'Head First' books are very good:

*

*Object oriented analysis and design

*Design patterns

A: Gotta read Uncle Bob Martin's columns at Object Mentor.  He's been writing good things about object-oriented programming since C++ Report in the 90s.  His SOLID ideas are language-agnostic.

A: Design Patterns by the Gang of Four. One reference book you will always need. It gives great detail on how to structure your code using OO design.
http://en.wikipedia.org/wiki/Design_Patterns

A: I would definitely recommend the "Head First Design Patterns" book. My suggestion is to read through that book atleast once. And once you get a feel of design patterns, use the "Gang of Four Design Patterns" book for quick reference/refresh.
And here are a few links from my bookmarks:

*

*http://sourcemaking.com/design-patterns-and-tips

*http://www.dofactory.com/Patterns/Patterns.aspx
Hope it helps.

A: You will learn this best on a University course, or atleast a good one. You don't have to spend 2 years out to do this - if you can afford £400 - $500 I'd recommend this one.
It teaches you about state, and the other 4 concepts you can read about in a badly expressed way on wikipedia. I'm not convinced you will learn it properly from free resources online, I'd guess you'll just get patchy information.
You can be extremely brainy but the information out there isn't going to be that high calibre for a reason - the brightest minds in software pay for their university courses, lectures, assignments and exams, not just read it on the internet.
For analysis try the M256 course, which is about Object Oriented software development, UML and system design. It sounds dull but contains a lot of background information that you probably will never use but will want to know anyway.


VitaMedica is a line of pharmaceutical-grade supplements that support recovery and wellness. For over 10 years, VitaMedica has been a leading provider of nutritional supplements. These physician formulated nutraceuticals are manufactured in a pharmaceutical facility where the production standards used are similar to those for prescription medications. These strict quality controls ensure that what's on the label is in the finished product. Ingredients are selected based on purity, bioavailability, safety characteristics and documented actions. Using VitaMedica Wellness products in conjunction with topical products and treatments leads to improved skin care results.


text:
Education For Girls App Backed By Plan UK and UK Authors.
The app is being promoted by children's charity, Plan UK and is called Education for Girls. The app asks users how many of a 50 strong list of classic children's books they have read and then goes on to ask the user to make a donation of £3. This donation will buy them a virtual book but is also the amount it costs Plan UK to send one girl to school for a week in Sierra Leone.
Unfortunately across the globe, one in three young girls in poor developing countries is unable to access public education and over 80 million young women aged between 15 and 24 will not have basic reading and writing skills which some see as a human right.
Award winning author, Boyne, described his childhood favourite Treasure Island by Robert Louis Stevenson as a "great adventure story and one of the best coming-of-age novels ever written; the Jim who has outwitted the pirates at the end of the novel is a very different Jim to the shy boy of the opening pages."
Another author and philosopher, AC Grayling cited Swiss Family Robinson as his personal favourite children's classic.
For those who wish to support the app and make a donation, it can be found on Facebook at www.facebook.com/planuk. Download it and be enveloped in wonderful nostalgia as you go through and mark which classics you have read and enjoyed! By contributing to sending a girl to school you are in turn participating in helping young women out of poverty and into a future with some opportunity.
Posted in General By Pandora Books


text:
Why SilverPoint?
Partners & Certifications
Server & Desktop Virtualisation
Hosted Solutions
Email & Spam Security
Connect To A Support Session
Here's What You Need to Know About SD-WAN Technology
Moving from hardware solutions to software solutions isn't a new concept for technology professionals, but network infrastructure has traditionally been a hardware-focused world even as applications move to the cloud. With the introduction of SD-WAN, or Software-Defined Wide Area Networks, IT professionals find themselves needing to retool their understanding of flexible networks and security. The MPLS (Multiprotocol Label Switching) has been in use for decades and is an extremely reliable — yet pricey — option for connectivity. Today's SD-WAN provides the modern organization with the flexibility, scalability, security and efficiency needed to stay competitive in a fast-changing world.
The Basics of SD-WAN
At its most basic, you can think of SD-WAN as a way to tie together a variety of disparate networks as it is equally efficient with internal as well as external internet and even cloud-based applications. Instead of a more rigid WAN network, SD-WAN allows you to configure your network quickly from a centralized location, reducing the potential of human error that can bring your network to its knees and productivity to a screeching halt. Since all variables are driven by software that you configure, this structure can be quickly scaled and new remote locations added without requiring an intense investment in time and physical hardware or redesign.
How Do You Manage a Software-Defined Network?
A key value that you gain when you shift to an SD-WAN is the ability to make shifts locally as well as globally from a centralized dashboard. This makes changes swifter, but also helps protect your network by ensuring that universal security standards are applied at all locations equally. Using an SD-WAN configuration gives you the added benefit of consolidated troubleshooting and error reporting so you can quickly identify any trouble spots or network hotspots and shift resources as needed to add speed and efficiency to your network — something that users are sure to appreciate, even if they never realise it is happening.
What Are the Business Benefits of SD-WAN?
Upgrading your network from a more restrictive model to SD-WAN has a variety of benefits for your organization. While some of these gains are realised upfront, others will continue to add value to your organization over time.
The cost of connectivity using an SD-WAN is less expensive than traditional MPLS, an especially important point when you consider the bandwidth-heavy applications that business users require.
While there is a high level of expertise required for upfront configuration of a software-defined network, ongoing changes are less intensive and can potentially save you consulting fees in the future.
Your business users will appreciate that network availability is high because there is no need to take the network down to make configuration changes or upgrades.
Your technology team is able to define networking rules in the language of business — SLAs, security restraints, apps and users — making the network easier to understand and maintain in the future.
With Gartner noting that nearly 25% of businesses will utilize SD-WAN in 2019, there is a growing body of knowledge within the IT community that makes it easier to find resources to support your network infrastructure. The SD-WAN market is expected to grow to $1.3 billion by 2020.
Cloud-based applications continue to emerge in all sectors of business, and it can be challenging to protect these applications without a consolidated hub of security rules. SD-WAN allows everything from SaaS to traditional connections to be covered under the same business rules.
Branches and remote workers will appreciate having access to the same high quality of connection that they enjoy at the office, instead of having to deal with restrictive security procedures and application latency.
Instead of relying on the hardware to make decisions about connections speed and connections as with MPLS, SD-WAN makes agile decisions about the best way to connect users and the data or applications that they need to access.
What Type of Business Benefits from SD-WAN?
While there are many benefits of SD-WAN, there is one downside that can be a deal-breaker for certain organizations. Software-Defined WAN does provide extremely reliable uptime, but there can be more packet loss than you would see with a hardware-based network. In this case, you may want to consider a hybrid infrastructure that lets you gain the benefits of SD-WAN for the majority of your applications yet maintains any heavy applications that simply cannot abide packet loss on a more traditional MPLS. The majority of organizations are looking for ways to reduce their cost of connectivity and have very heavy use of their internet or intranet connections — making SD-WAN ideal. Businesses that are growing quickly or expanding into new regions are also likely to see gains from making the switch.
Many organizations are seeing that shifting to an SD-WAN model may help them future-proof their business by creating a flexible, scalable and secure model that can grow with their business. From the reduced cost of connections to the high availability environment, it's clear that the conversation around SD-WAN will not be going away in technology groups around the world.
Searching ForA New Technology Company To Support Your Business IT Systems?
SilverPoint Systems can help!
Put Your Trust In The Lower Mainland's Complete Technology Services Company.
Email Address(Privacy Policy):
Your Information Is Safe With Us. SilverPoint Systems will never sell, rent, share or distribute your personal details with anyone. In addition, we will never spam you.
SilverPoint Tech Corner
Each week SilverPoint Systems Shares The Latest How-To Technology Information.
No quicker way to let ghouls into the network ?
Online Free Excel Training: Tips & Techniques For Managing Workbooks
How To Make Your Presentations Rock With Live Captions & Subtitles in PowerPoint
Management. Support. Peace of Mind. Making Your Life Easier.
Why SilverPoint
Network & Data Security
224 – 20316 56 Avenue Langley, BC V3A 3Y7
Follow Silverpoint
© SilverPoint 2023. All rights reserved. | Sitemap | Privacy Policy -


text:
Samarendra Narayan Dev is a national award winner veteran film director. His film career, spanning four decades, has also brought laurels and recognition to Assam. His first independent celluloid depiction, Aranya (1971), was based on the dwindling rhinoceros population in Assam. It brought him the National Award in the best feature film category (regional) in 1971.

During 1970s to 1980s Samarendra Narayan Dev made more women centric films. Aranya 1971, and Putalar Ghar 1976, represented women of different social strata. While in Aranya, Bidya Rao played a carefree woman's character. Putalar Ghar represented the childlike innocence in a young woman and her transitions in life from childhood to adult age.

Early life

Samarendra Narayan Dev, the descendant of Darrang Royal Family was born on 13 October 1940 at Mangaldai in Darrang District of Assam. His father, Bhupendra Narayan Dev, was an honorary magistrate  and a member of Legislative Assembly of Assam. His mother was Saroj Devi. From his childhood he had a craze about stage drama plays. He used to write drama plays and performed from the age of 14. While he was in college he got the opportunity to perform on stage with the likes of the great Bishnu Rabha and Phani Sharma in the drama Siraj. Bhikha (The Alms) and Bandor Aaru Jokhola (The monkey and the ladder) are the two plays for which he received best director's award and also best drama award from Assam Natya Sanmiloni. His play Bheko-Bhaona also got published in Naytya Sankalan, published by Sangeet Natak Academu. Slowly his attention turned towards movies and he wished to become a filmmaker. He went to Kolkata in 1967 and got his first break as an assistant director in the same year under Director Ashutosh Bannerjee in Tini Bhuboner Pare. In 1970  he came back to Assam and started his own movie Arayna, it was produced by a club called United Club constituted of his friends including himself. So they named the production house as "United Production". "Arayna" was critically acclaimed and went on to win National award for best film in regional language. It was heart-warming for him as it dealt on a subject  like wild life protection and was a new experience for the Assamese audience and gained appreciation from them. His second movie PUTALA GHAR also went on to win a national award for best film in regional language.  Altogether he made six movies till date including his comeback movie with an historical subject called "BIR CHILARAI" in 2013. He made many TV series, TV movies and documentaries in Hindi, Assamese and English. In 1995, he got an opportunity to do a Television film on DD-1 named "DARPAN".

Filmography
 FILMS   -
                 ARANYA - 1971 : Won presidential award for best film in regional language.
                 PUTALAGHAR - 1976  : Won National award for best film in regional language.
                 SUNOR HORIN - 1979.
                 KAZIRANGAR KAHINI - 1981.
                 RAJA - 1981.
                 BIR CHILARAI - 2013.

 TELE-FILMS -
                 DAWAR - 1991,
                 DARPAN - 1996,
                 NISHIKTA PRADAH - 1999,
                 MUR GAOR SADHUU - 2001 ( For P.P.C)

 DOCUMENTARIES-
                 DEVADASHI NRITYA - 1994,
                 BIYAS OJAPALI  - 1994,
                 KHULIA BHAORIA - 1994,
                 SUKNANI OJAPALI  AND DEODHANI NRITYA - 1997
                 SWARNAREKHA - 2001

 TV SERIES -
                 SASIPATHOR PUTHI - 1997,
                 AJAK BOROKHOONOR APAKHYAT - 2002
                 INTEZAAR     - 2002,
                 AMRITASHYA PUTRA - 2003,
                 MAA O MERI MAA   - 2003,
                 NAYEE RAAH - 2005,
                 MERA WATON KE LOGO  - 2007,
                 ANDHARAT NIJOR MUKH - 2011.

References

Notes

Assamese-language film directors
Film directors from Assam


SUNNYVALE, Calif. - May 24, 2010 - Greenliant Systems, a company dedicated to developing energy-efficient, highly reliable and secure solid state storage products, today announced that it has acquired the NANDrive, NAND Controller and Specialty Flash Memory assets of Microchip Technology Inc. (NASDAQ: MCHP). The three product lines will form the core of Greenliant's solid state storage product portfolio for the embedded system, data center and mobile Internet markets.
Founded in April 2010 by former SST (Silicon Storage Technology, Inc.) chairman and CEO, Bing Yeh, Greenliant is built upon more than 20 years of expertise in designing low-power, high-quality flash memory, solid state storage and controller products. Greenliant's core management and engineering staff include many of the original NANDrive and NAND Controller design team members.
"By acquiring the NANDrive solid state drive and NAND Controller assets of Microchip Technology, Greenliant is well positioned to take a leadership position in the fast-growing market for solid state storage products," said Bing Yeh, CEO of Greenliant. "We are fully committed to providing continued and uninterrupted support to existing customers of NANDrive, NAND Controllers and Specialty Flash Memory products through our well-established global sales channels and manufacturing partners in wafer foundry, chip packaging and testing. With our team of seasoned technologists and technical marketing experts, Greenliant will continue to develop and market advanced solid state storage solutions for the needs of our rapidly changing world. Green and Reliant, as our corporate name implies, will be the center of our focus. Our corporate mission is to develop and market energy-efficient, highly reliable and secure storage solutions for the embedded system, data center and mobile Internet applications."
Greenliant's flagship product, the award-winning NANDrive solid state drive (SSD), consists of an integrated ATA controller and NAND flash die in a tiny multi-chip package measuring as small as 12mm x 24mm. NANDrive includes built-in microcontroller and file management firmware that communicates with ATA-standard interfaces, eliminating the need for additional or proprietary host software such as Flash File System (FFS) or Memory Technology Driver (MTD) software. Selected as the small form factor SSD choice of tier one companies in the communications, industrial, medical and networking markets, NANDrive products are available in capacities ranging from 512 MByte to 8 GByte and support industrial temperature ranges. Higher capacity NANDrive products will be announced soon.
Comprising the heart of NAND-based storage solutions, Greenliant's NAND Controllers are built upon more than two decades of controller design expertise. Featuring advanced NAND management technology, the NAND Controllers intelligently manage the inherent deficiencies of NAND flash, taking this burden off of the host system and making the system designer's job easier. Greenliant NAND Controllers provide high reliability, increased data integrity, powerful error correction capability, power-down protection and prolonged product life for data storage systems.
Greenliant's Specialty Flash Memory product offering includes the ComboMemory family, consisting of 1.8V and 3.0V standard and address/data bus multiplex flash plus PSRAM combination memory products. Featuring high performance in an extremely small and thin package - as small as 6 x 8 x 1mm - the ComboMemory products are the premier combination memory choice for space- and power-constrained portable devices. The MTP (Many-Time Programmable) family marries the erase capability of flash with the cost effectiveness of EPROM/OTP (one-time programmable) memory. The SSF (Small-Sector Flash) products are ideal for applications requiring fine data granularity, and the multi-bank architecture and Read-while-Write operations of Greenliant's CSF (Concurrent SuperFlash) series make it ideal for wireless applications.
By leveraging more than 20 years of solid state storage design expertise, Greenliant Systems is dedicated to developing energy-efficient, highly reliable and secure storage solutions for the embedded system, data center and mobile Internet markets. The company is currently headquartered in Sunnyvale, California with product development and sales teams in North America, Europe and Asia. For more information about Greenliant Systems, please visit www.greenliant.com.
For more information, read the CEO letter to customers.


text:
A Catholic Meta-History
Marian T. Horvat, Ph.D.
Book review of Beyond Politics: A Meta-Historical View by Solange Strong Hertz
(The Remnant Press: 2003), 291 pp.
The reflective Catholic man considers various aspects of the world as if through the thousand facets of a crystal. As time passes, he selects this or that aspect that better pleases him, in which he better sees and loves God. Just as a man reaches a certain defined way of acting, speaking and working that suit him, so also his way of thinking becomes defined. At a certain period in his life, he can say, "This is how I understand myself and the world around me." When he arrives at this point, he reaches his maturity.
With Beyond Politics: A Meta-Historical View, Solange Strong Hertz illustrates that she achieved this maturity of thinking. The book, a collection of essays, is a synthesis of a ripe and experienced Catholic consideration of History, strongly influenced by the studies of French Catholic Fernand Crombette (d. 1970) and the Cercle Scientifique et Historique [CESHE], a group that promotes and develops Crombette's thinking.
It is important to understand what Mrs. Hertz means by Meta-History (from the Greek meta, meaning beyond), a word that is appearing frequently in modern academia with quite different twists. For example, the whole point of Hayden White's well-known work entitled Metahistory is to show that nothing "is the way it is," everything is a story, an interpretation of a time, a presentation of an ideology. Since for White every account lacks "complete objectivity," no account can claim to be true. No truth exists for what he calls the meta-historians. For them, everything is relative. Today this historic relativism has become widespread. Sadly, since Vatican II, the Holy See has included many scholars of this type among its advisers.
The opposite is true for Mrs. Hertz. She understands Meta-History as highly consistent and with an absolute meaning. It is History seen from its highest causes, which means from the perspective of God. What matters is God's plan for man and society in both the religious and temporal spheres. The deeds of man are to be analyzed in view of this.
The principal facet of the crystal Mrs. Hertz uses to consider God's design for man is Divine Revelation. Drawing not only Scriptures more evident passages, she also interprets veiled and mysterious parts looking for their more profound sense and beauty. From these heights, which she describes as a "juncture between time and eternity," she analyzes History. It is a medieval perspective very attractive to me, even though different from my own.
In History there are changes of eras, marked by the implantation of different types of culture, the installment of various forms of government, the domination by different peoples. To the measure that such changes are legitimate, a people, culture, or institution emits a special brilliance that augments the extrinsic glory of God.
Here is the key question rarely asked today: Is a change legitimate, in the sense of following the divine plan and increasing the glory of God on earth? To what extent does it represent the fruit of fidelity to Catholic teaching? Or does it, on the other hand, break with the continuity expressed by the upright variety of customs and institutions in the history of a people?
Mrs. Hertz asks these questions, and has the courage to give answers that threaten modern man's assumptions about progress, democracy and science, as well as the revolutionary trio of liberty, equality and fraternity. Americans are not accustomed to this sort of analysis, which makes many of her controversial expositions and bold conclusions even more valuable.
Here is one such question: Was the scientific revolution represented by Galileo truly the grand advance in progress it is purported to be? Spurning Scholasticism, the new school upset the true hierarchy of sciences, setting up mathematics over metaphysics and even over theology. Galileo's revolution was much more than a new hypothesis that the earth revolved around the sun; it challenged a literal acceptance of Divine Scripture and set the foundation for a new "dogma," that of the supposed infallibility of science, to replace divine revelation as the ultimate source of truth. Whether you agree with Hertz on heliocentrism or not, it is clear that the scientific revolution brought into question the entire scholastic tradition and fostered a growing skepticism about the possibility of certain knowledge.
What about the American and French Revolutions, which effectively formalized the separation of religion and state and set the rule of the people over the law of God? Do they really indicate a step forward for History by replacing the medieval Catholic order in which rulers were subject to the Kingship of Christ?
Hertz' answer is quite clear: A government that claims to derive its "just powers" not from God, but from the "consent of the governed" should be condemned, as it firmly was by Pope St. Pius X in his apostolic letter addressed to the French Bishops warning against the error of Christian democracy as manifested in the "Sillon" movement. In an important essay in this book titled "The Tears of the Papacy," Mrs. Hertz demonstrates the liberal role of the Church in the rise and acceptance of democracy. Concessions to the new republics began with concordats, like that of Pius VII with Napoleon, just after the French Revolution. Leo XIII sealed the fate of the doomed monarchies with his famous "ralliement" in the Encyclical Au milieu des sollicitudes in 1892, which officially put the forces of the Church behind democracy, and doomed the valiant Catholic movements in Europe fighting to restore the traditional monarchy.
Ah, some might object, but Mrs. Hertz is criticizing the actions of Popes, and this is not Catholic or good. To this objection she devotes a chapter of response, "Peter's Policies." Catholics need to know not only when legitimate authority can be defied, but when it must be defied if God is to be served, she insists. She points out the policies of Popes Benedict XV and Pius XI that furthered the revolution of the liberal secular state. It was a Vatican directive that betrayed the heroic Cristeros in Mexico with an order to put down their arms and support the corrupt anti-Catholic Calles government. Later, she notes, secularization took on new vigor at the Second Vatican Council, which was followed by Paul VI's personal endorsement of the United Nations, "nexus of the godless political apparatus."
Are Catholics to go along with this "havoc wrought in Christ's vineyard?" No, Mrs. Hertz responds. What made such destruction possible was blind obedience, a tool specially forged by the devil to serve the ends of the on-going revolution in the last century. As Hertz concludes, "Any degree of political or religious deformation becomes possible through mindless compliance with authority, and History proves papal authority no exception" (p. 221). We are opportunely reminded that Popes can and do commit serious errors in judgment, and can even deny Christ as St. Peter did. And when they do, Catholics are required to resist.
Before closing this review on Mrs. Hertz's notable Beyond Politics: A Meta-Historical View, I would like to make two more brief comments. First, to those critics who complain about the lack of footnotes and sources in some of Mrs. Hertz' work, I would direct them to this book. She cites valuable sources, especially when she reveals the plots of the secret forces of Freemasonry and the Jewish Kabala to infiltrate the Church. At the end of the book is a concise and interesting bibliography, mostly French works.
Our Lady of La Salette
Second, there is a timely essay on the often-ignored message of Our Lady of La Salette, who appeared to two shepherd children, Maximin Giraud and Melanie Calvat, near La Salette (France) in 1846. Our Lady warned the children of evils threatening her people especially because of blasphemy and the profanation of Sunday, and entrusted to each a secret, instructing Melanie to publish hers in 1858.
After five years of careful examination of the facts surrounding the apparitions, the Church authorized the Cult of Our Lady of La Salette in 1851, and a grand Minor Basilica was built at the site.
Notwithstanding, very soon opposition set in and ardent efforts were made to quash the secret entrusted to Melanie, which was finally published in 1873 with an imprimatur of the Bishop of Naples, Italy. It speaks of the period from 1846 to the era of the manifestation of the Antichrist, with the warning that Rome would lose the Faith and become the seat of the Antichrist.
Why did such hostility to Melanie's secret arise? Could it be because it speaks of a crisis inside the Church, of the infiltration of "the abomination into the holy places?"
Mrs. Hertz publishes the full text of the message of La Salette, without commentary. As Melanie told her director in 1903, "Souls who are God's friends can guess the Secret's meaning without help, and the others won't want to because it applies to them too closely" (ibid.) And if this were clear at the turn of the century, Mrs. Hertz notes, it is even clearer now for those with eye to see.
Book Reviews | Home | Books | CDs | Search | Contact Us | Donate


text:
Q: How to account for both between-subjects and within-subjects covariables? I have a data set I'm trying to analyze and I can't figure out how to include the two different kinds of covariables in my analysis.
Without the covariables, the analysis isn't too complicated. It's a repeated measures design. Every subject took test A and test B. Half took them in one order and half took them in the other order. But I have several covariables that I'd like to include. I actually have way too many covariables, but I've narrowed the list down beforehand. That still leaves two different types of covariables to deal with though. A few were measured along with each individual test, and a few were measured before or after and apply to each subject.
My question is, what analysis technique should I be using to answer the final question, "are the results of test A and test B significantly different?" and how do I include the two different kinds of covariables in that?