text
stringlengths 0
128k
|
|---|
Email updates
Keep up to date with the latest news and content from BMC Health Services Research and BioMed Central.
Research article
The relationship between safety net activities and hospital financial performance
Jack Zwanziger1, Nasreen Khan2* and Anil Bamezai3
Author Affiliations
1 Health Policy and Administration, School of Public Health, University of Illinois at Chicago, 1603 W Taylor St., Chicago, USA
2 College of Pharmacy, 1 University of New Mexico, Albuquerque, NM, USA
3 RAND Corporation, 1776 Main Street, Santa Monica, CA, USA
For all author emails, please log on.
BMC Health Services Research 2010, 10:15 doi:10.1186/1472-6963-10-15
Published: 14 January 2010
Abstract
Background
During the 1990's hospitals in the U.S were faced with cost containment charges, which may have disproportionately impacted hospitals that serve poor patients. The purposes of this paper are to study the impact of safety net activities on total profit margins and operating expenditures, and to trace these relationships over the 1990s for all U.S urban hospitals, controlling for hospital and market characteristics.
Methods
The primary data source used for this analysis is the Annual Survey of Hospitals from the American Hospital Association and Medicare Hospital Cost Reports for years 1990-1999. Ordinary least square, hospital fixed effects, and two-stage least square analyses were performed for years 1990-1999. Logged total profit margin and operating expenditure were the dependent variables. The safety net activities are the socioeconomic status of the population in the hospital serving area, and Medicaid intensity. In some specifications, we also included uncompensated care burden.
Results
We found little evidence of negative effects of safety net activities on total margin. However, hospitals serving a low socioeconomic population had lower expenditure raising concerns for the quality of the services provided.
Conclusions
Despite potentially negative policy and market changes during the 1990s, safety net activities do not appear to have imperiled the survival of hospitals. There may, however, be concerns about the long-term quality of the services for hospitals serving low socioeconomic population.
|
import { NPC } from './_common'
import { WeightRecord } from '../types'
import { BackgroundName } from './backgroundTraits'
import { ThresholdTable } from '../src/rollFromTable'
import { LifestyleStandardName } from './lifestyleStandards'
interface SocialClass {
/** landRate is a multiple, used in taxation. */
landRate: number
socialClassRollThreshold: number
probability: number
lifestyle: string[]
lifestyleStandards: ThresholdTable<LifestyleStandardName>
defaultBackground: WeightRecord<BackgroundName>
relationships(npc: NPC, otherNpc: NPC): Customer[]
}
interface Customer {
relationship: string
description: string
}
function buildSocialClass<T extends Record<string, SocialClass>> (t: T) { return t }
export const socialClass = buildSocialClass({
'aristocracy': {
landRate: 3,
socialClassRollThreshold: 95,
probability: 10,
lifestyle: ['aristocratic'],
lifestyleStandards: [
[5, 'comfortable'],
[15, 'wealthy'],
[80, 'aristocratic']
],
defaultBackground: {
noble: 10,
knight: 2,
acolyte: 1
},
// this will be more interesting when the relationships are no longer just key pairs
relationships: (npc: NPC, otherNpc: NPC) => [
{
relationship: 'fellow wine lover',
description: `${npc.firstName} introduced ${otherNpc.firstName} to the delightful world of merlots and other delectable alcohols.`
},
{
relationship: 'auction house competitor',
description: `${npc.firstName} and ${otherNpc.firstName} are constantly finding themselves bidding over the same items..`
},
{
relationship: 'dinner guest',
description: `${npc.firstName} had ${otherNpc.firstName} as a dinner guest many moons ago, and ${otherNpc.heshe} quickly returned the favour.`
},
{
relationship: 'fellow art lover',
description: `${npc.firstName} and ${otherNpc.firstName} frequently attend art exhibits and plays together.`
}
]
},
'nobility': {
landRate: 2,
socialClassRollThreshold: 80,
probability: 20,
lifestyle: ['aristocratic', 'wealthy', 'comfortable'],
lifestyleStandards: [
[5, 'modest'],
[30, 'comfortable'],
[60, 'wealthy'],
[5, 'aristocratic']
],
relationships: (npc: NPC, otherNpc: NPC) => [
{
relationship: 'fellow wine lover',
description: `${npc.firstName} introduced ${otherNpc.firstName} to the delightful world of merlots and other delectable alcohols.`
},
{
relationship: 'liesure game competitor',
description: `${npc.firstName} and ${otherNpc.firstName} are friendly rivals in liesure games such as golf and boules.`
},
{
relationship: 'dinner guest',
description: `${npc.firstName} had ${otherNpc.firstName} as a dinner guest many moons ago, and ${otherNpc.heshe} quickly returned the favour.`
},
{
relationship: 'fellow art lover',
description: `${npc.firstName} and ${otherNpc.firstName} frequently attend art exhibits and plays together.`
}
],
defaultBackground: {
'noble': 10,
'knight': 2,
'acolyte': 4,
'guild artisan': 3,
'sage': 4,
'soldier': 2
}
},
'commoner': {
landRate: 1,
socialClassRollThreshold: 60,
probability: 50,
lifestyle: ['comfortable', 'modest', 'poor'],
lifestyleStandards: [
[5, 'poor'],
[45, 'modest'],
[45, 'comfortable'],
[5, 'wealthy']
],
relationships: (npc: NPC, otherNpc: NPC) => [
{
relationship: 'fellow wine lover',
description: `${npc.firstName} introduced ${otherNpc.firstName} to the delightful world of merlots and other delectable alcohols.`
},
{
relationship: 'fellow cat owner',
description: `${npc.firstName} and ${otherNpc.firstName} are both cat owners, which they bond over.`
},
{
relationship: 'dinner guest',
description: `${npc.firstName} had ${otherNpc.firstName} as a dinner guest many moons ago, and ${otherNpc.heshe} quickly returned the favour.`
},
{
relationship: 'fellow theatre lover',
description: `${npc.firstName} and ${otherNpc.firstName} frequently attend plays together.`
}
],
defaultBackground: {
'acolyte': 4,
'guild artisan': 3,
'sage': 4,
'urchin': 3,
'outlander': 2,
'merchant': 3,
'hermit': 1,
'gladiator': 2,
'folk hero': 1,
'criminal': 1,
'charlatan': 2,
'soldier': 5,
'peasant': 10
}
},
'peasantry': {
landRate: 0.5,
socialClassRollThreshold: 20,
probability: 80,
lifestyle: ['modest', 'poor', 'squalid'],
lifestyleStandards: [
[5, 'squalid'],
[60, 'poor'],
[30, 'modest'],
[5, 'comfortable']
],
relationships: (npc: NPC, otherNpc: NPC) => [
{
relationship: 'fellow peasant',
description: `${npc.firstName} and ${otherNpc.firstName} share little in common, save for their poor financial circumstances and low social class.`
},
{
relationship: 'has the same landlord',
description: `${npc.firstName} and ${otherNpc.firstName} have the same landlord.`
}
],
defaultBackground: {
'acolyte': 4,
'sage': 4,
'urchin': 5,
'outlander': 3,
'merchant': 2,
'hermit': 2,
'gladiator': 2,
'folk hero': 1,
'criminal': 2,
'charlatan': 3,
'soldier': 6,
'peasant': 15
}
},
'paupery': {
landRate: 0,
socialClassRollThreshold: 10,
probability: 30,
lifestyle: ['poor', 'squalid', 'wretched'],
lifestyleStandards: [
[5, 'wretched'],
[75, 'squalid'],
[15, 'poor'],
[5, 'modest']
],
relationships: (npc: NPC, otherNpc: NPC) => [
{
relationship: 'fellow wretch',
description: `${npc.firstName} and ${otherNpc.firstName} occasionally help each other out, pooling their resources to scrounge together a meagre stew.`
},
{
relationship: 'same landlord',
description: `${npc.firstName} and ${otherNpc.firstName} have the same landlord.`
}
],
defaultBackground: {
acolyte: 1,
sage: 1,
urchin: 10,
outlander: 3,
merchant: 2,
hermit: 6,
gladiator: 2,
criminal: 5,
charlatan: 4,
soldier: 6,
peasant: 15
}
},
'indentured servitude': {
landRate: 0,
socialClassRollThreshold: 10,
probability: 5,
lifestyle: ['squalid', 'wretched'],
lifestyleStandards: [
[95, 'wretched'],
[5, 'squalid']
],
relationships: (npc: NPC, otherNpc: NPC) => [
{
relationship: 'fellow slave',
description: `${npc.firstName} helped ${otherNpc.firstName} learn the ropes, and stop ${otherNpc.hisher} feet from bleeding so much.`
}
],
defaultBackground: {
urchin: 15,
outlander: 5,
hermit: 10,
gladiator: 1,
criminal: 10,
charlatan: 8,
soldier: 3,
peasant: 8
}
}
})
export type SocialClassName = keyof typeof socialClass
|
<?php
namespace thewbb\thinwork\controllers;
class AcluserController extends BaseAdminController
{
public $tableName = "acl_user";
public function indexAction()
{
}
public function registerAction($template = null){
if(empty($template)){
$template = __DIR__."/../views/acluser/register";
}
$this->view->pick($template);
if ($this->request->isPost()) {
$email = $this->getPost("email");
$password = $this->getPost("password");
$validate = $this->getPost("validate");
if (!$this->security->checkToken()) {
return $this->dispatcher->forward(["controller" => "index", "action" => "show404"]);
}
if(empty($email)){
$this->flashSession->error("邮箱不能为空");
header("location:/register");
exit();
}
if(empty($password)){
$this->flashSession->error("密码不能为空");
header("location:/register");
exit();
}
if(empty($validate)){
$this->flashSession->error("验证码不能为空");
header("location:/register");
exit();
}
$sql = "select * from acl_user where username = '$email'";
$user = $this->fetchOne($sql);
if($user){
$this->flashSession->error("用户已存在");
return;
}
$salt = uniqid();
if($this->redis->get("validate-$email") == $validate){
$this->insert("acl_user", array(
"username" => $email,
"email" => $email,
"password" => sha1($password.$salt),
"salt" => $salt,
));
$this->flashSession->success("恭喜您！注册成功，请让管理员开通权限后登陆！");
header("location:/login");
exit();
}
else{
$this->flashSession->error("验证码错误");
return;
}
}
}
public function loginAction($template = null){
if(empty($template)){
$template = __DIR__."/../views/acluser/login";
}
$this->view->pick($template);
$redirect_url = $this->getPost("redirect_url", "/admin/dashboard");
if($this->request->isPost()){
// check csrf attack
if (!$this->security->checkToken()) {
return $this->dispatcher->forward(["controller" => "index", "action" => "show404"]);
}
$email = $this->getPost("email");
$password = $this->getPost("password");
$keep = $this->getPost("keep");
$sql = "select * from acl_user where username = '$email' limit 1";
$user = $this->fetchOne($sql);
if(empty($user)){
// 用户不存在
$this->flashSession->error("用户不存在");
header("location:/login");exit();
}
else if($user["password"] != sha1($password.$user["salt"])){
// 密码不正确
$this->flashSession->error("密码不正确");
header("location:/login");exit();
}
else if(empty($user["is_valid"])){
// 密码不正确
$this->flashSession->error("用户被锁定");
header("location:/login");exit();
}
else{
$this->session->set("user", $user);
if(empty($user["token"])){
$token = $this->guid();
$this->update("acl_user", array("token" => $token), "id = ".$user["id"]);
}
else{
$token = $user["token"];
}
if($keep == "on"){
$this->cookies->set("token", $token, time() + 30 * 86400);
}
header("location:$redirect_url");
}
}
else{
$this->view->setVars(array("redirect_url" => $redirect_url));
}
}
public function logoutAction(){
$this->session->set("user", null);
$this->cookies->set("token", null);
header("location:/login");
}
public function profileAction(){
echo "profileAction";
}
public function editProfileAction($template = null){
$user = $this->getLoginUser();
if(empty($template)){
$template = __DIR__."/../views/acluser/editprofile";
}
$this->view->pick($template);
if($this->request->isPost()){
// check csrf attack
if (!$this->security->checkToken()) {
return $this->dispatcher->forward(["controller" => "index", "action" => "show404"]);
}
if(empty($user)){
$this->flashSession->error("用户不存在。");
header("location:{$this->controller}/list");exit();
}
$username = $this->getPost("post-username");
$name = $this->getPost("post-name");
$phone = $this->getPost("post-phone");
$email = $this->getPost("post-email");
$password = $this->getPost("post-password");
if(!empty($password) && ((strlen($password) < 6) || (strlen($password) > 32))){
$this->flashSession->error("密码长度为6到32个字符");
header("location:");exit();
}
$params = array(
"username" => $username,
"name" => $name,
"phone" => empty($phone)?null : $phone,
"email" => empty($email)?null : $email,
"password" => sha1($password.$user["salt"]),
);
if(empty($password)){
unset($params["password"]);
}
$this->update("acl_user", $params, "id = ".$user["id"]);
$this->flashSession->success("修改成功");
header("location: /".$this->controller."/list");
}
else{
$fields = [
"username" => ['label' => '用户名', 'readonly' => true],
"name" => ['label' => '姓名'],
"phone" => ['label' => '手机号'],
"email" => ['label' => 'email'],
"password" => ['label' => '密码'],
];
$sql = "select * from $this->tableName where id = {$user["id"]}";
$record = $this->fetchOne($sql);
unset($record["password"]);
if(empty($record)){
throw new Exception("table not exist");
}
foreach($fields as $key => &$field){
$field["data"] = $record[$key];
}
$this->view->setVars([
"controller" => $this->controller,
"action" => $this->action,
"sidebarTemplate" => $this->sidebarTemplate(),
"headerTemplate" => $this->headerTemplate(),
"footerTemplate" => $this->footerTemplate(),
"title" => '修改个人信息',
"fields" => $fields,
"data" => $user,
]);
}
}
public function changePasswordAction(){
echo "changePasswordAction";
}
public function findPasswordAction(){
echo "findPasswordAction";
}
public function registerSendValidateAction(){
// 数据有效性验证
$validation = new Phalcon\Validation();
$validation->add('email', new Email(array('message' => '电子邮箱格式不正确')));
$this->checkRequest($validation, $this->request->getPost());
$expire = 600; //超时时间10分钟
$email = $this->getPost("email");
// 检测用户是否存在
$sql = "SELECT * FROM acl_user where email = '$email'";
$user = $this->fetchOne($sql);
if($user){
$this->returnError('此用户已存在!');
}
if($this->redis->exists("validate-$email")){
// 如果redis中存在验证码
$validate = $this->redis->get("validate-$email");
// 检测验证码发送周期
if($this->redis->ttl("validate-$email") > $expire - 10){
$this->returnInfo('至少需要15秒才能重新发送验证码。');
}
else{
$this->redis->setex("validate-$email", $expire, $validate);
}
}
else{
// 如果redis中不存在，那么创建验证码和时间戳
$validate = mt_rand(1000, 9999);
$this->redis->setex("validate-$email", $expire, $validate);
}
// 发送邮件
$result = $this->sendValidateMail($email, $validate);
$this->returnSuccess($result);
}
public function addAction(){
if(empty($template)){
$template = __DIR__."/../views/acluser/add";
}
$this->view->pick($template);
if($this->request->isPost()){
// check csrf attack
if (!$this->security->checkToken()) {
return $this->dispatcher->forward(["controller" => "index", "action" => "show404"]);
}
$id = $this->getPost("id");
$username = $this->getPost("post-username");
$name = $this->getPost("post-name");
$phone = $this->getPost("post-phone");
$email = $this->getPost("post-email");
$password = $this->getPost("post-password");
$is_valid = $this->getPost("post-is_valid");
$is_super_admin = $this->getPost("post-is_super_admin");
if(!empty($password) && ((strlen($password) < 6) || (strlen($password) > 32))){
$this->flashSession->error("密码长度为6到32个字符");
header("location:");exit();
}
$salt = uniqid();
$params = array(
"username" => $username,
"name" => $name,
"salt" => $salt,
"phone" => empty($phone)?null : $phone,
"email" => empty($email)?null : $email,
"password" => sha1($password.$salt),
"is_valid" => empty($is_valid)?0:1,
"is_super_admin" => empty($is_super_admin)?0:1,
);
if(empty($password)){
unset($params["password"]);
}
$this->insert("acl_user", $params);
$user_id = $this->lastInsertId();
foreach($_POST['post-checkbox'] as $group_id)
{
$this->insert("acl_group_has_user", array("group_id" => $group_id, "user_id" => $user_id));
}
$this->flashSession->success("修改成功");
header("location: /".$this->controller."/list");
}
else{
$fields = [
"username" => ['label' => '用户名'],
"name" => ['label' => '姓名'],
"phone" => ['label' => '手机号'],
"email" => ['label' => 'email'],
"password" => ['label' => '密码'],
"is_valid" => ['label' => '是否有效', 'type' => 'boolean'],
"is_super_admin" => ['label' => '超级管理员', 'type' => 'boolean'],
];
$sql = "select a.*, 0 as granted from acl_group as a";
$records = $this->fetchAll($sql);
$this->view->setVars([
"controller" => $this->controller,
"action" => $this->action,
"sidebarTemplate" => $this->sidebarTemplate(),
"headerTemplate" => $this->headerTemplate(),
"footerTemplate" => $this->footerTemplate(),
"fields" => $fields,
"title" => "添加新用户",
"data" => $records,
]);
}
}
public function editAction($template = null){
if(empty($template)){
$template = __DIR__."/../views/acluser/edit";
}
$this->view->pick($template);
if($this->request->isPost()){
// check csrf attack
if (!$this->security->checkToken()) {
return $this->dispatcher->forward(["controller" => "index", "action" => "show404"]);
}
$id = $this->getPost("id");
$sql = "select * from acl_user where id = $id";
$user = $this->fetchOne($sql);
if(empty($user)){
$this->flashSession->error("用户不存在。");
header("location:{$this->controller}/list");exit();
}
$username = $this->getPost("post-username");
$name = $this->getPost("post-name");
$phone = $this->getPost("post-phone");
$email = $this->getPost("post-email");
$password = $this->getPost("post-password");
$is_valid = $this->getPost("post-is_valid");
$is_super_admin = $this->getPost("post-is_super_admin");
if(!empty($password) && ((strlen($password) < 6) || (strlen($password) > 32))){
$this->flashSession->error("密码长度为6到32个字符");
header("location:");exit();
}
$params = array(
"username" => $username,
"name" => $name,
"phone" => empty($phone)?null : $phone,
"email" => empty($email)?null : $email,
"password" => sha1($password.$user["salt"]),
"is_valid" => empty($is_valid)?0:1,
"is_super_admin" => empty($is_super_admin)?0:1,
);
if(empty($password)){
unset($params["password"]);
}
$result = $this->update("acl_user", $params, "id = $id");
if($result){
$sql = "delete from acl_group_has_user where user_id = $id";
$this->execute($sql);
foreach($_POST['post-checkbox'] as $group_id)
{
$this->insert("acl_group_has_user", array("group_id" => $group_id, "user_id" => $id));
}
$this->flashSession->success("修改成功");
}
{
// 修改失败
}
header("location: /".$this->controller."/list");
}
else{
$id = $this->getQuery("id");
$sql = "select a.*, case when b.user_id is null then 0 else 1 end as granted from acl_group as a left join (select * from acl_group_has_user where user_id = $id) as b on a.id = b.group_id ";
$records = $this->fetchAll($sql);
$fields = [
"username" => ['label' => '用户名'],
"name" => ['label' => '姓名'],
"phone" => ['label' => '手机号'],
"email" => ['label' => 'email'],
"password" => ['label' => '密码'],
"is_valid" => ['label' => '是否有效', 'type' => 'boolean'],
"is_super_admin" => ['label' => '超级管理员', 'type' => 'boolean'],
];
$sql = "select * from $this->tableName where id = $id";
$record = $this->fetchOne($sql);
unset($record["password"]);
if(empty($record)){
throw new Exception("table not exist");
}
foreach($fields as $key => &$field){
$field["data"] = $record[$key];
}
$this->view->setVars([
"controller" => $this->controller,
"action" => $this->action,
"sidebarTemplate" => $this->sidebarTemplate(),
"headerTemplate" => $this->headerTemplate(),
"footerTemplate" => $this->footerTemplate(),
"id" => $id,
"fields" => $fields,
"data" => $records,
]);
}
}
public function listAction(){
$search_fields = [
'id'=> ['label' => 'id'],
"username" => ['label' => '用户名'],
"name" => ['label' => '姓名'],
"group_name" => ['label' => '用户组'],
"phone" => ['label' => '手机号'],
"email" => ['label' => 'email'],
];
$fields = [
"id" => ['label' => 'id'],
"username" => ['label' => '用户名'],
"name" => ['label' => '姓名'],
"group_name" => ['label' => '用户组'],
"phone" => ['label' => '手机号'],
"email" => ['label' => 'email'],
"is_valid" => ['label' => '是否有效', 'type' => 'boolean'],
"is_super_admin" => ['label' => '超级管理员', 'type' => 'boolean'],
"token" => ['label' => 'token'],
"created_at" => ['label' => '创建时间'],
"action" => [
'label' => '操作',
'type' => 'actions',
'actions' => [
'show' => ['label' => "显示"],
'edit' => ['label' => '编辑'],
'remove' => ['label' => '删除']
]
],
];
$sqlCount = "select count(*) from acl_user where 1";
$sqlMain = "select * from (select a.*, GROUP_CONCAT(c.name) as group_name from acl_user as a left join acl_group_has_user as b on a.id = b.user_id left join acl_group as c on b.group_id = c.id group by a.id) as acl_user where 1";
parent::listAction($search_fields, $fields, $sqlCount, $sqlMain);
}
}
|
<?php
/**
* Created by PhpStorm.
* User: Dang Meng
* Date: 2018/9/7
* Time: 14:12
*/
namespace app\index\controller;
use think\Controller;
use think\Db;
class Index extends Controller{
/*
* 大城小屋首页
* */
public function index(){
/*获取用户设备和网络类型*/
$agent = $_SERVER['HTTP_USER_AGENT'];
if(strpos($agent,"NetFront") || strpos($agent,"iPhone") || strpos($agent,"MIDP-2.0") || strpos($agent,"Opera Mini") || strpos($agent,"UCWEB") || strpos($agent,"Android") || strpos($agent,"Windows CE") || strpos($agent,"SymbianOS")){
//手机
echo "<script>window.location.href='/mobile/index/'</script>";
}
//热线电话
$hotLine=Db::table('dcxw_setinfo')->where(['s_key' => 'hotline'])->column('s_value');
$this->assign('hotLine',$hotLine[0]);
//网站导航
$navInfo=Db::table('dcxw_nav')
->where(['nav_isable' => 1])
->order('nav_order desc')
->field('nav_title,nav_url')
->select();
$this->assign('navinfo',$navInfo);
//首页banner
$banner=Db::table('dcxw_banner')->where(['ba_isable' => 1,'ba_via' => 1])->order('ba_order desc')->select();
$this->assign('banner',$banner);
//房源
$house=Db::table('dcxw_house')
->join('dcxw_province','dcxw_province.p_id = dcxw_house.h_p_id')
->join('dcxw_city','dcxw_city.c_id = dcxw_house.h_c_id')
->join('dcxw_area','dcxw_area.area_id = dcxw_house.h_a_id')
->where(['h_isable' => 2])
->whereOr(['h_isable' => 4])
->limit(6)
->order('h_istop,h_view desc')
->field('dcxw_province.p_name,dcxw_city.c_name,dcxw_area.area_name,dcxw_house.*')
->select();
$this->assign('house',$house);
return $this->fetch();
}
}
|
Creating a HUD (scale invariant text / labels) in SVG/Raphael when using setViewBox
I am creating Raphael web app to allow panning and zooming a floor plan. This all works great but I cannot seem to find out how I can add scale invariant text (or other objects) onto the interface. Everything scales and moves when a user pans / zooms. I basically want HUD features to remain in their positions / sizes in spite of any user panning / zooming.
I currently zoom / pan using setViewBox
paper.setViewBox(x,y,newViewBoxWidth,newViewBoxHeight);
Your UI should be in a separate Raphael paper laid on top of your floorplan.
Plain SVG allows nesting SVGs but Raphael doesn't, as it must provide VML fallbacks.
Thanks, I came to this conclusion myself a short while ago
|
import React, { Component } from 'react';
import { connect } from 'react-redux';
import { updatePlayerActiveStatus } from '../../actions/actionCreators';
import CreatePlayerForm from './CreatePlayerForm';
import EditTeamForm from './EditTeamForm';
class Team extends Component {
constructor() {
super();
this.renderPlayers = this.renderPlayers.bind(this);
this.renderHomeAwayNumber = this.renderHomeAwayNumber.bind(this);
this.renderHeader = this.renderHeader.bind(this);
}
componentWillMount() {
if("team" in this.props){
this.team = this.props.team;
} else {
this.team = this.props.teams[this.props.location.payload.id];
}
}
componentWillUpdate(){
if("team" in this.props){
this.team = this.props.team;
} else {
this.team = this.props.teams[this.props.location.payload.id];
}
}
renderHomeAwayNumber(player) {
if (player.awayNumber !== player.homeNumber) {
return player.homeNumber + '/' + player.awayNumber
}
return player.homeNumber;
}
updatePlayerStatus(e, team, player) {
this.props.updatePlayerActiveStatus(team, player);
}
renderHeader() {
return (
<div className="hero-body">
<div className="container">
<h1 className="title">{this.props.seasons[this.team.seasonId].year} {this.team.teamName} ({this.team.abbreviation})</h1>
</div>
<h2 className="subtitle">
{this.team.city + ", " + this.team.state}
</h2>
<p>Head Coach: {this.team.headCoach}</p>
<p>Assistant Coach: {this.team.assistiantCoach}</p>
<EditTeamForm team={this.props.team}/>
</div >
)
}
renderPlayers(key) {
const player = this.team.players[key];
return (
<tr key={key}>
<td><input type="checkbox" defaultChecked={player.isActive} onChange={(e) => this.updatePlayerStatus(e, this.team, player)} /></td>
<td>{this.renderHomeAwayNumber(player)}</td>
<td>{player.fname}</td>
<td>{player.lname}</td>
<td><a className="button is-link">View</a></td>
</tr>
);
}
render() {
return (
<div className="container">
<section className="hero">
{this.renderHeader()}
<table className="table">
<thead>
<tr>
<td>Active</td>
<td>Number</td>
<td>First Name</td>
<td>Last Name</td>
<td></td>
</tr>
</thead>
<tbody>
{Object.keys(this.team.players).map(this.renderPlayers)}
</tbody>
</table>
</section>
<CreatePlayerForm />
</div>
);
}
}
const mapStateToProps = state => state;
Team = connect(
mapStateToProps,
{
updatePlayerActiveStatus
}
)(Team);
export default connect(mapStateToProps, {})(Team);
|
Talk:Helenelunds IK
External links modified
Hello fellow Wikipedians,
I have just modified one external link on Helenelunds IK. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
* Added archive https://web.archive.org/web/20140418114458/http://www.jimbobandy.nu/ to http://www.jimbobandy.nu/
Cheers.— InternetArchiveBot (Report bug) 14:57, 1 November 2017 (UTC)
|
Jake the Dog (episode)
{{Episode {{FA}} {{EpisodeHeader|5|2|Jake the Dog}}
* image = Jakethedog.jpg
* season = 5
* broadcastno = 2
* prod = 1014-106
* airdate = November 12, 2012
* director = Larry Leichliter
* story = Patrick McHale Kent Osborne Pendleton Ward
* writerstoryboard = Cole Sanchez & Rebecca Sugar
* previous = Finn the Human
* next = Five More Short Graybles
Synopsis
Plot
Major characters
* Finn
* Jake
* The Lich
* Prismo
* Farmworld Finn
* Farmworld Jake
* Mrs. Mertens
* Mr. Mertens
* Finn's Baby Brother
* Cosmic Owl
Minor characters
* Bartram
* Choose Bruce
* Farmworld Marceline
* Farmworld Simon Petrikov
* Princess Bubblegum
* Embryo Princess
* Hotdog Princess
* Ice King
* Gunter
* Destiny Gang
* Big Destiny
* Trami
* Tromo
* Snail
Mentioned
* Joshua
Music
* Three Nice Dudes
Trivia
* This is the first episode where the Cosmic Owl is in actual physical form and not a vision.
Cultural references
Episode connections
Errors
* While Finn is wearing the crown, it shows the crown on Simon's body before the bomb explodes.
Production notes
|
import argparse
import glob
import re
import difflib
import prettytable
from common.log import Log
#patterns = ['snowflakeschema','starschema', 'denormalizedschema']
#scalefactors = ['0.1']
#seeds = ['1','2','3','4','5']
def required_length(nmin,nmax):
class RequiredLength(argparse.Action):
def __call__(self, parser, args, values, option_string=None):
if not nmin<=len(values)<=nmax:
msg='argument "{f}" requires between {nmin} and {nmax} arguments'.format(
f=self.dest,nmin=nmin,nmax=nmax)
raise argparse.ArgumentTypeError(msg)
setattr(args, self.dest, values)
return RequiredLength
def initilize_logs(patterns,scalefactors,seeds):
logfiles = []
global logFileDirectory
for scalefactor in scalefactors:
for seed in seeds:
for pattern in patterns:
logfiles.append(Log.find_logfile(pattern,scalefactor,seed,logFileDirectory))
return logfiles
def parse_arguments():
global patterns
global seeds
global scalefactors
global logFileDirectory
parser = argparse.ArgumentParser(description='Compare results of logfiles e.g. --pattern snowflakeschema starschema denormalizedschema --scale 0.5 --seed 5 --system virtuoso_open-source_7.1 ')
parser.add_argument('--pattern', metavar='pattern', type=str, nargs='+', action=required_length(2,3), dest='patterns', required=True , help='enter at least two patterns (space seperated) e.g. snowflakeschema')
parser.add_argument('--seed', metavar='seed', type=str, nargs='+', dest='seeds', required=True , help='enter at least one seed (space seperated) e.g. 99')
parser.add_argument('--scale', metavar='scalefactor', type=str, nargs='+', dest='scalefactors', required=True , help='enter at least one scale (space seperated) e.g. 0.5')
parser.add_argument('--system', metavar='name', type=str, nargs='+', dest='system', required=True , help='enter the name of the DBRMS e.g. virtuoso_open-source_7.1')
args = parser.parse_args()
patterns = args.patterns
seeds = (args.seeds)
scalefactors = (args.scalefactors)
logFileDirectory = "logs/dbserver1/"+args.system[0]
def __compare_results(log1,log2):
results = {}
results[0] = log1.get_pattern()+'_'+log1.get_scale()+'_'+log1.get_seed()+"--"+log2.get_pattern()+'_'+log2.get_scale()+'_'+log2.get_seed()
for i in range(1,len(log1.get_results())+1):
if log1.get_result(i) != log2.get_result(i):
results[i] = "Missmatch"
# print log1.get_filepath()
# print log1.get_result(i)
# print "\n"
# print log2.get_filepath()
# print log2.get_result(i)
# sys.exit()
else:
results[i] = ""
return results
def create_ascii_table(columns):
table = prettytable.PrettyTable()
columns.insert(0,{0:"",1:"Q1",2:"Q2",3:"Q3",4:"Q4",5:"Q5",6:"Q6",7:"Q7",8:"Q8",9:"Q9",10:"Q10",11:"Q11",12:"Q12",13:"Q13",14:"Q14",15:"Q15",16:"Q16",17:"Q17",18:"Q18",19:"Q19",20:"Q20",21:"Q21",22:"Q22"})
for column in columns:
table.add_column(column[0],column)
return table
def compare_all_results(log1, log2, log3 = None):
try:
if log1.get_seed() != log2.get_seed():
raise TypeError('logfiles are not comparable, the seed differs',log1,log2)
elif log1.get_scale() != log2.get_scale():
raise TypeError('logfiles are not comparable, the scalefactor differs',log1,log2)
elif log1.get_results().keys().sort() != log2.get_results().keys().sort():
raise TypeError('logfiles are not comparable, the number of results or which results it contains differs',log1,log2)
elif log3 != None:
if log2.get_seed() != log3.get_seed():
raise TypeError('logfiles are not comparable, the seed differs',log2,log3)
elif log2.get_scale() != log3.get_scale():
raise TypeError('logfiles are not comparable, the scalefactor differs',log2,log3)
elif log2.get_results().keys().sort() != log3.get_results().keys().sort():
raise TypeError('logfiles are not comparable, the number of results or which results it contains differs',log2,log3)
except TypeError as err:
print(err.args)
columns = []
columns.append(__compare_results(log1,log2))
if log3 != None:
columns.append(__compare_results(log1,log3))
columns.append(__compare_results(log2,log3))
return create_ascii_table(columns)
parse_arguments()
logfiles = initilize_logs(patterns, scalefactors, seeds)
for i in range(1,len(seeds)*len(scalefactors)+1):
log1 = logfiles.pop()
log2 = logfiles.pop()
log3 = logfiles.pop()
print compare_all_results(log1,log2,log3)
|
Phorcus turbinatus
Phorcus turbinatus, common name the turbinate monodont, is a species of sea snail, a marine gastropod mollusk in the family Trochidae, the top snails.
Description
The size of the shell varies between 15 mm and 43 mm. The very solid and thick, imperforate shell has a conical shape. It is whitish, tinged with gray, yellowish or greenish, tessellated with numerous spiral series of reddish, purple or chocolate sub-quadrangular blotches. The conoid spire is more or less elevated. The apex is eroded. The about 6 whorls are slightly convex, with impressed spiral lines between the series of blotches, the last generally descending anteriorly. The base of the shell is eroded in front of the aperture. The aperture is very oblique. The thick, smooth outer lip is beveled to an edge. It is pearly and iridescent within. The columella is flattened on the face, bluntly lobed within, pearly, backed by an opaque white layer.
Distribution
This marine species occurs in the following locations:
* Mediterranean Sea
* Greek Exclusive Economic Zone
* Portuguese Exclusive Economic Zone
* Spanish Exclusive Economic Zone (Spain, Canary Islands)
|
how to get object in array list php
I have an array of ways to retrieve paper objects? I try foreach,Trying to get property 'sample_url' of non-object,and Illegal string offset 'sample_url' , how get sample_url in object paper?
"active_joins2": [
{
"join_registration_number": "SS-006672-I-ID",
"join_status": "checked",
"join_tag": "9#science#indonesia#Primary 3",
"student_id": 7502,
"paper": {
"sample_id": 57,
"sample_title": "Science Indonesia Primary 3",
"sample_url":"http:google.com/abc/sample/1548989381.pdf",
"sample_tag": "9#science#indonesia#Primary 3"
}
},
{
"join_registration_number": "MS-006687-I-ID",
"join_status": "checked",
"join_tag": "9#math#indonesia#Primary 3",
"student_id": 7502,
"paper": {
"sample_id": 47,
"sample_title": "Math Indonesia Primary 3",
"sample_url":"http://google.com/sample/1548988991.pdf",
"sample_tag": "9#math#indonesia#Primary 3"
}
}
]
in blade view
@foreach ($item['active_joins2'] as $row => $val)
@php
$string = str_replace('#',' ',$val['join_tag']);
$exString = explode(" ",$string);
@endphp
<a href="{{}}" style="text-decoration:none;">
<div class="card jismo-practice-paper mx-auto mb-3">
<div class="card-body row">
<div class="col-lg-6 col-xl-6 col-md-6 col-sm-6 col-6">
<div class="subject" style='text-transform: capitalize'>{{$exString[1]}}</div>
<div class="language" style='text-transform: capitalize'>{{$exString[2]}}</div>
</div>
<div class="col-lg-6 col-xl-6 col-md-6 col-sm-6 col-6">
<div class="grade">{{$exString[3]}}</div>
<div class="gradenumber">{{$exString[4]}}</div>
</div>
</div>
</div>
</a>
@endforeach
Code snippet is actually a JSON, do you work with JSON or with php array?
This has already been made an array
Do simply with json_decode(), Also your json string is missing starting and ending curly braces i.e { }
$array = json_decode($object,1);
foreach($array['active_joins2'] as $key=>$value){
echo $value['paper']['sample_url'].PHP_EOL;
}
WORKING DEMO: https://3v4l.org/AbsLS
active_joins2 is an array not an object
@MuhamadRahmatSetiawan did you check my working demo?
I think this is json, you can use json_decode function and after that use that in php like array or std object
json_decode
|
Camera
oct. 27, 192s 1,559,285/
' B. F. SCHMIDT CAMERA Filed Sent. 26. 1921 I N V EN TOR.
l A TTORNE Y Y Patented oa. 27, 1925.
UNITED STATES BENJAMIN F. SCHMIDT, OF LOS ANGELES, CALIFORNIA.
CAMERA.
' Application led September 26, 1921. Serial Ifo. 503,178.
T0 all whom it may concern:
Be it known that I, BENJAMIN F. SCHMIDT, a citizen of the United States` residing at Los Angeles, in the county of Los Angeles, State of California, have invented certain new and useful Improvements in Cameras; and I do y declare the. following to be a full, clear, and exact description of the same, reference being had to the accompanying drawings, and to the characters of reference marked ther eon, which form a part of this application.
This invention relates tov improvements in cameras, and particularly to that type of hand-camera generally used by amateur photographers, Which is designed to use lm rolls therein and in which the shutter is aetuated by a spring-pressed iexible cable or wire.
When taking pictures 'with this type of camera, the operator frequently forgets to turn the film-spool after exposing a section of the film, and as in the cameras. now o-n the market there is nothing to prevent the shutter'being again actuated.' a double exposure is the result, both photographs being of course ruined, which apart from the monetary value of the lil m sometimes represents a loss to the photographer of a different and greater nature.
The principal object of my invention is to provide a camera with means for positively preventing a double exposure of the film. or
and a new sect-ion has been t1on for exposure.
in other words ,making it,l impossible to actuate the shutter again until the' exposed film section has'been wound onto the spool p wound in to posi- Another-object is to provide a manually operated means for both releasing or restoring the shutter actuating member to its normal position, and for causing the exposed section of filmA to be wound onto the spool, and the next section to'be positioned in the proper plane for exposure prior to the release of the shutter member.
This does away with the use of the usual hand-winding y apparatus once the first film section is moved to operative position, practically making it impossible for apc film-section to be wound onto the spool until it has been exposed.
A hand winding means v however is provided to wind' the film onto the take-up spool from its outer end to the firstsensitizedsection, '/but as soon as the finger button or handle is released by the operator, it automatically moves to lie Hush with the camera case, and even though it should be rotated while in that position, no turning of the spool will be effected.
This button then being out of the way, accidental winding of the film is thus made impossible since the button must be intentionally moved to an operative position ,before the spool can be rotated thereby.
The tendency to'utilize this hand winding means when unnecessary is also lessened by the fact thatthe release member controlling the release of the shutter contro-l and the winding of the film is much easier and more convenient to use than the other, and would therefore be used by any normally intelligent person. v
Another object is to provide .a structure for the purpose which is relatively simple and not likely to get out of order, and which may be readily incorporated or attached in any modern camera of the type mentioned, without necessitating any structural alterations A being made therein.
These objects I accomplish by means of such structure and relative arrangement of parts asn will full v appear by a perusal of4 the following specification and claims.
In .the drawings similar characters of reference indicate corresponding parts in the several views.
Fig. 1 -is a perspective outline of a folding hand-camera. showing a branched cable actuating means for the shutter and shutter control lock, and the other visible parts, including the manually operated buttons.
Fig. 2 is an en large d transverse section through one end of the camera, showing particularly the hand and automatic spool winding means.
Fig. 3 is. an inner-end view of this structure.
Fig. 4 is a fragmentary cross section taken on al line 4-4 of Fig. 3, showing the shutter control lock v member positioned after the shutter has been actuated, and the release button therefor.
Fig. 5 is a similar view. showing the position of the shutter control-lock after its re please, or when the shutter control member i projecting from tht` Fig. 7 is an en lar ed detached sectional view of the film-spoo hand-winding mechanism.
Fig. 8 is a cross section of the same taken on a line 8-8 of Fig. 7.
l Referring now .more particularly to the characters of reference on the drawings, the numeral 1 denotes the casing of the camera having the usual chamber 2 at one end adapted to receive a take-up spool 3 of the usual character. On the outside of the casing adjacent said chamber is fixed a bearing plate 4 turnably mounted on which axially of the spool 3 and projecting outwardly from the plate is a cylindrical cup 5 centrally in which is turnably mounted a pin 6 on the inner end of which is across bar 7 adapted `to engage the usual slotted recess provided in the spool.
Positioned in the 'cup and fixed ther eon at its outer end is a spiral spring 8 of the usual clock work type, the inner end ofv which is fixed to the ,hub 9 of a pinion 10` mounted on the pin or shaft 6. The hub is free on the shaft, but the latter is caused to rotate therewith only in the direction'of` the unwindingof the spring by means of a v form of one way -grip or overrunning clutch or friction means incorporated in the hub 9, as shown at 11. A similar but oppositely disposed friction engaging means 12 is interposed between the plate 4 and cup 5, so that while the latter may be turned at any time to wind up the spring, said spring cannot impart rotation to the cup in the opposite direction.
Pawl and ratchet mechanisms would serve the same purpose, but I believe the means shown to be simpler, less expensive, and
noiseless in operation.
Journaled in the plate 4 beyond the cup is a gear 13 meshing with the pinion .10. This gear has a spring bar 14 fixed ther eon projecting beyond-the teeth ther eof and normally bearing against a stop pin 15 late 4 into the path of movement of said ar.
Positioned between the bar and-plate and projecting partly under said bar and partly outwardly ther eof is a lock-finger 16 to which is connected a cable or wire 17 which extends through a flexible casing or sleeve 18'to a connection with the similar sleeve 19 containing the shutter actuating cable, both cables being moved in common by a push-button 20. The finger is normally held against the bar ,14 by a spring A21 weaker than the spring bar, and at the end ther eof opposite t e wire 17 has a cam surface 22 on its u perrface and a shoulder 23 at the `inner en of said cam surface,this shoulder bearing against a stop pin 24 mounted on the plate 4 out of the path of movement of the ar 14.
, Mounted in the plate 4 and positioned outside the same is a push-button 25 having a stem 26 projecting through the plate to bear the pinion 10 to turn in one direction, and
the gear 13 in the opposite direction, or with thev bar 14 against the stop .15. Neither gear can then normally rotate, since they are in mesh with each other, and neither can turn without the other.
If the button 25 is depressed when the` finger 16 is held by the stop 24, which will be when Ythe shutter has been actuated and the actuating member 20 of the shutter control wire is pushed in, the finger will then be between the bar 14 land the stem 26, and the latter will press the finger against the bar, raising the same clear of the stop 15, and permitting the gear, and consequently the pinion, to rotate,` the relative proportions ofthe gear and pinion being such that a single revolution of the gear allows a sufficient number of turns of the pinion to rotate the spool 3 to -wind the film`\ ther eon from -one exposed section to the next unexposed section.
The gear however can only have one revolution at a time, since with the rotation ther eof past the pin 15 and around, the bar ultimately comes in contact with the cam surface of the finger, depressing the same clear of the stop, 24, thus allowing the finger to return to a position away from under the bar, as shown in Fig. 5,V in which position the` shutter control cable (which as usual is spring pulled) is likewise released and restored to its normal position. The bar 14 will then resume its normal position and will again abut against and be held by the pin 15, where it will remain until again raised' by the depression 'of the button 25.
Any such depression of the latter however, as long as the finger is not between the bar and stem, will not raise .the bar, since the movement allowed the stem-is not sufficient forthe latter to reach and-raise the bar unless the finger is therebetween.- Thus `as long as the finger and shutter control member are in their released position, there can be no automatic winding of the film. Also when the finger moves to engage the stop 24 with the actuation of the shutter control, itl cannot be released except after the rotation of the gear. which' controls the winding of the exposed fi ln.
' An auxiliary hand-winding structure, normally positioned so that it cannot be aceidentally used, is provided. This consists of a Stem 28, Aslidable and normallyturnable in the member'6. This stem is normally drawn inwardly of said member 6 by a spring 29, and carries on its outer end a turning button .or handle 30 which is normally countersunk in 'a recess 3l provided in the cup 5 The portion of the stem adjacent said handle is smaller than the bore of the member 6, which has a pin 32 projecting there into. y
The stem has at a certain point a rectangul'ar or other flat surfaced portion 33, any one of the sides of which is adapted to move across the inner end of the pin 32 when the handle and stem are drawn outwardly. When such an operation takes place, if the button is then rotated, the flat portion 33 of the stem will be engaged by the pin and the stem will thus be unable to rotate freely of itself, but must also rotate the member 6, and consequently the spool 3 therewith As soon as the fingers are withdrawn from the button however, the latter is drawn to its socketed or countersunk position by the spring 29, and the flat portion of the stem isl moved out of engagement with the screw, said engagement being only had when the stem is pulled out to its fullest extent With the button not socountersunk, or even if only partly drawn out, no rotation will be imparted to the -member 6 with the rotation of the member 28.
In order to draw| said member. outwardly a sufficient distance to disengage the bar 7 from the spool when necessary, a small finger-pressed lever 34 is mounted in the cup and is provided with a fork or yoke 35 en` gaging the member 6 adjacent its outer end, this lever being allowed only sufficient depression as will move the cross bar. of the member 6 clear of the'spool.
It will be noted that rota tive movement of the shaft 6 in one direction only, and independently of the pinion ther eon, may be had by reason of the cooperating clutch or friction structure 11 From the foregoing description it will be' readily seen that I have produced such a device as substantially fulfills the objects of the invention as set forth herein.
While this specification sets forth in detail the present and preferred construction of the device, still in practice such deviations from such detail may be resorted to as do not form a departure from the spiritiof the invention, asdeined by the appended claims.
Having thus described my invention, what I claim as new and useful and desire to secure by Letters Patent, is
l. In a film-roll camera having a shutter actuating means, a member movable with said means, locking means for holding said member from return movement when the shutter actuating means is operated, auto wind the exposed film ther eon will the member be released.
2. In a film-roll camera having a shutter actuating means, a member movable therewith, locking means for holding said member from return movement when the shutter actuating means is operated, automatic means for rotating the film spool, hand means for controlling the operation of the automatic means, and means controlled by the operation of the automatic means for releasing thc member only after the spool has been rotated the number of times necessary to completely wind the exposed film ther eon.
3. In a film-roll camera having a shutter actuating means, a cable movable therewith, locking means for holding said cable from return movement when the shutter actuating means is operated, automatic means for rotating the fl lm spool, hand means for controlling the operation of the automatic means, and means whereby said automatic means will not be placed in operation by said ated.
5. In a film-roll camera having a shutter actuating means,f automatic means for rotating the film spool to wind the film ther eon, hand means for controlling the operation of the automatic means, means whereby the hand means is prevented from setting the automatic means in operation until the shutter has been actuated and means whereby when the shutter actuating means is coactuated it cannot resume its normal position until the automatic Winding means has been operated.
6. In a film-roll camera. having a shutter actua-ting means, automatic` means for rotating the film spool to wind the film ther eon, hand means for controlling the operation of the automatic means, means whereby the hand means is prevented from setting the automatic4 means in operation until the shutyter has been actuated, .means for then preventing the shutter actuating means from returning to its normal position and means controlled by the operation of the automatic means for releasing said actuating means after the spool has been rotated a predetermined number of times.
7 In a film roll-camera having r a shutter actuating means,a shaft adapted to engage the -film spool to turn therewith, spring means for rotating said shaft in one direction only, a pinion on the latter, a gear meshing with the pinion, means normally V holding said gear against rotation, and means whereby said gear may be released to y` turn only when the shutter has been actuated.
8. In a film roll-camera having a shutter actuating means, a shaft adapted to engage the ilm spool to turn therewith, spring means for rotating said shaft in one direction only, a pinion on the latter, a gear meshing with the pinion, means normally holding said gear againstvrotation, and means operatively connected with the shutter actuating means whereby said gear may only be released after said actuating means has been actuated. v
9. In a ii lm roll-camera having a shutter actuating means, a shaft'adapted to engage the ii lm spool to turn therewith, spring means for rotating said shaft in one direction only', a pinion on the latter, a gear meshing with the pinion, means normally holding said gear against rotation, a cable connected lto the shutter actuating means and movable therewith, a finger on the end of said cable adapted to move alongside the edge of the gear when the shutter is actuated and to be then locked in that position, a push button on the exterior of the camera case, and means whereby with the depression of said button only when the iinger isl in locked position the gear will first be released and the finger subsequently unlocked and allowed to return to its normal position.
10. In a film roll-camera having .a shutter actuating means, a. shaft adapted to engage the film spool to turn therewith, spring means for rotating said shaft in one direction only, a pinion on the latter, a gear meshing with the pinion, a flat spring on the gear projecting beyond the edge ther eof, a stop pin positioned to normally engage said spring to hold the gear against rotation, a cable connected' tov the shutter actuating means and movable therewith, a finger on the end of said cable adapted to project bej tween thev flatispring andy the camera case when the shutter is actuated and to be then locked 1n that position, a manually-pressed l' stem adapted to bear against the linger to -force the same against the Hat spring and raise the same clear of the stop pin, and means whereby after the rotation of A,said
gear to a point again adjacent the stop pin,
the finger will be released.
11. .In a film roll-camera having a shutter actuating means, a shaft adapted to engage the film spool to turn therewith, spring means for rota-ting said shaft in one direction only, a pinion on the latter, a gear meshing wit the pinion, a ii at' sprin on the gear projecting beyond the edge t er eo, a stop pin l positioned to normally engage said spring to hold the gear against rotation, a
cable connected lto the V shutter actuating the end of said cable adapted to project between the flat spring and the camera case when4 the shutter is actuated and to be then locked in that position, a manually-pressed stem adapted to bear against the finger to force'the same against the fiat spring and raise the same clear of the stop pin, another stop pin normally holding the linger against return movement, and a cam surface on said finger adapted to be engaged by the iat spring after a predetermined extent of rotation ofthe gear to depress said finger clear of its stop-pin.
12. In a film-roll camera having a shutter actuating means, a cable movable therewith,
locking means for holding the cable from return y movement when the shutter actuating means is actuated and until a new film-section has been placed in position for eX- posure, automatic means for rotating the film-spool, and hand means for controlling the operation of the automatic means effective only after the shutter has been operated.
13. In a film-roll camera having a shutter actuating means, automatic means for rotating the. film-spool to wind the film ther eon, land han-d means dependent upon the prior movement of the shutter control means for controlling the operation of the automatic means only y after the shutter control means V has been operated.
14. In a film-roll camera l having a shutter actuating means, automatic'means for ro tating the film-spool to wind the film ther eon, operable only after the shutter has been operated, hand means for controlling the operation of the automatic means through cooperation with the `shutter control means, means whereby the hand means is prevented from setting the automatic means in operation until the shutter control means has been actuated, and means whereby when the shut section is completely wound on its spool,
hand means for controlling the operation ofthe .automatic meansuonly with the cooperation of the .shutter control means, means whereby a the hand means is prevented from setting in operation until the'shutter has been actuated, and' means controlled by the operation of the automatic means, for releasmg said the automatic meansactuating means only after the spool has 13- erative only after the shutter has been actu;
ated,l means then holding said actuating means inoperative and against return to normal, a pinion on the shaft, a ge ai-.ineshing with the pinion, means normally holding said gear against rotation, and means whereby said gear may be released to turn .only when the shutter control means has been actuated ,and retained in said inop'- erative position.
17. In a film roll camera having a shutter and operating means therefor, automatic means tor winding the film onto its spool operable only after the Shutter has been actuated and then operating only to the extent of winding the exposed film ther eon, hand means controlling the operation of said automatic means, and means preventing the functioning of the hand means more than once between any two consecutive actuations of the shutter.
18. In a lm roll eam era'having a shutter and a depressible actuating member therefor, automatic means for winding the film, hand means controlling the operation of the automatic means, means whereby the shutter actuating member will he locked and held against f return to a normal position after beingfdepressed until the exposed portion of the film has been wound onto its spool, and means whereby the hand means cannot function after being once actuated until the shutter is again actuated.
In testimony wher eof I aix my signature.
BENJAMIN F. SCHMIDT.
|
package grpcservers
import (
"context"
remoteexecution "github.com/bazelbuild/remote-apis/build/bazel/remote/execution/v2"
"github.com/buildbarn/bb-storage/pkg/blobstore"
"github.com/buildbarn/bb-storage/pkg/blobstore/buffer"
"github.com/buildbarn/bb-storage/pkg/digest"
"github.com/buildbarn/bb-storage/pkg/proto/icas"
"github.com/buildbarn/bb-storage/pkg/util"
"google.golang.org/grpc/status"
)
type indirectContentAddressableStorageServer struct {
blobAccess blobstore.BlobAccess
maximumMessageSizeBytes int
}
// NewIndirectContentAddressableStorageServer creates a gRPC service for
// serving the contents of an Indirect Content Addressable Storage
// (ICAS). The ICAS is a Buildbarn specific extension for integrating
// external corpora into the CAS.
func NewIndirectContentAddressableStorageServer(blobAccess blobstore.BlobAccess, maximumMessageSizeBytes int) icas.IndirectContentAddressableStorageServer {
return &indirectContentAddressableStorageServer{
blobAccess: blobAccess,
maximumMessageSizeBytes: maximumMessageSizeBytes,
}
}
func (s *indirectContentAddressableStorageServer) FindMissingReferences(ctx context.Context, in *remoteexecution.FindMissingBlobsRequest) (*remoteexecution.FindMissingBlobsResponse, error) {
instanceName, err := digest.NewInstanceName(in.InstanceName)
if err != nil {
return nil, util.StatusWrapf(err, "Invalid instance name %#v", in.InstanceName)
}
digestFunction, err := instanceName.GetDigestFunction(in.DigestFunction, 0)
if err != nil {
return nil, err
}
inDigests := digest.NewSetBuilder()
for _, partialDigest := range in.BlobDigests {
digest, err := digestFunction.NewDigestFromProto(partialDigest)
if err != nil {
return nil, err
}
inDigests.Add(digest)
}
outDigests, err := s.blobAccess.FindMissing(ctx, inDigests.Build())
if err != nil {
return nil, err
}
partialDigests := make([]*remoteexecution.Digest, 0, outDigests.Length())
for _, outDigest := range outDigests.Items() {
partialDigests = append(partialDigests, outDigest.GetProto())
}
return &remoteexecution.FindMissingBlobsResponse{
MissingBlobDigests: partialDigests,
}, nil
}
func (s *indirectContentAddressableStorageServer) BatchUpdateReferences(ctx context.Context, in *icas.BatchUpdateReferencesRequest) (*remoteexecution.BatchUpdateBlobsResponse, error) {
instanceName, err := digest.NewInstanceName(in.InstanceName)
if err != nil {
return nil, util.StatusWrapf(err, "Invalid instance name %#v", in.InstanceName)
}
digestFunction, err := instanceName.GetDigestFunction(in.DigestFunction, 0)
if err != nil {
return nil, err
}
responses := make([]*remoteexecution.BatchUpdateBlobsResponse_Response, 0, len(in.Requests))
for _, request := range in.Requests {
digest, err := digestFunction.NewDigestFromProto(request.Digest)
if err == nil {
err = s.blobAccess.Put(
ctx,
digest,
buffer.NewProtoBufferFromProto(request.Reference, buffer.UserProvided))
}
responses = append(responses,
&remoteexecution.BatchUpdateBlobsResponse_Response{
Digest: request.Digest,
Status: status.Convert(err).Proto(),
})
}
return &remoteexecution.BatchUpdateBlobsResponse{
Responses: responses,
}, nil
}
func (s *indirectContentAddressableStorageServer) GetReference(ctx context.Context, in *icas.GetReferenceRequest) (*icas.Reference, error) {
instanceName, err := digest.NewInstanceName(in.InstanceName)
if err != nil {
return nil, util.StatusWrapf(err, "Invalid instance name %#v", in.InstanceName)
}
digestFunction, err := instanceName.GetDigestFunction(in.DigestFunction, 0)
if err != nil {
return nil, err
}
digest, err := digestFunction.NewDigestFromProto(in.Digest)
if err != nil {
return nil, err
}
actionResult, err := s.blobAccess.Get(ctx, digest).ToProto(
&icas.Reference{},
s.maximumMessageSizeBytes)
if err != nil {
return nil, err
}
return actionResult.(*icas.Reference), nil
}
|
USC Jane Goodall Research Center
The USC Jane Goodall Research Center is a part of the department of Anthropology at the University of Southern California. It is co-directed by professors of anthropology Craig Stanford, Chris Boehm, Nayuta Yamashita, and Roberto Delgado.
The center was established in 1991 with the joint appointment of Jane Goodall as Distinguished Emeritus Professor in Anthropology and Occupational Science. The center offers USC students the chance to study in Gombe.
|
---
comments: true
date: 2006-04-01 05:27:37
layout: post
slug: how-do-i-trim-the-contents-of-a-form
title: How do I trim the contents of a form?
wordpress_id: 13
categories:
- ColdFusion
---
From [ColdFusion Cookbook](http://www.coldfusioncookbook.com/):
Trimming is an essential part of dealing with an data coming from form textfields or textareas etc. You can of couse trim as and when you need (before validation or database inserts etc) but if you can trim all fields quickly and easily!
``` javascript
<cfloop collection="#form#" item="formfield">
<cfset form[formfield] = trim(form[formfield]) />
</cfloop>
```
This basically loops over a form structure and trims each element. You can use this loop in a function before handing it to your validation or database methods.
[Read the full article](http://www.coldfusioncookbook.com/entry/28/How-do-I-trim-the-contents-of-a-form?)
|
/*!
Hyphenating iterators over strings.
*/
use std::borrow::Cow;
use std::iter::{Cloned, IntoIterator, ExactSizeIterator};
use std::slice;
use std::vec;
use hyphenator::*;
use extended::*;
/// A hyphenating iterator that breaks text into segments delimited by word
/// breaks, and marks them with a hyphen where appropriate.
///
/// Such segments generally coincide with orthographic syllables, albeit
/// within the limited accuracy of Knuth-Liang hyphenation.
#[derive(Clone, Debug)]
pub struct Hyphenating<'m, I> {
inner : I,
mark : &'m str
}
impl<'m, I, S> Hyphenating<'m, I>
where I : Iterator<Item = S>
, S : AsRef<str>
{
/// Turn into an iterator that yields word segments only, without inserting
/// a hyphen or other mark before breaks.
pub fn segments(self) -> I {
self.inner
}
/// Set the mark that will be inserted before word breaks.
pub fn mark_with(&mut self, mark : &'m str) {
self.mark = mark;
}
/// Build a hyphenating iterator from an iterator over string segments.
pub fn new(iter : I) -> Self { Hyphenating { inner : iter, mark : "-" } }
}
impl<'m, I, S> Iterator for Hyphenating<'m, I>
where I : Iterator<Item = S> + ExactSizeIterator
, S : AsRef<str>
{
type Item = String;
fn next(&mut self) -> Option<Self::Item> {
self.inner.next().map(|segment|
if self.inner.len() > 0 {
[segment.as_ref(), self.mark].concat()
} else { segment.as_ref().to_owned() }
)
}
fn size_hint(&self) -> (usize, Option<usize>) { self.inner.size_hint() }
}
impl<'m, I, S> ExactSizeIterator for Hyphenating<'m, I>
where I : Iterator<Item = S> + ExactSizeIterator
, S : AsRef<str> {}
/// A hyphenating iterator with borrowed data.
pub trait Iter<'t> {
type Iter;
fn iter(&'t self) -> Hyphenating<'t, Self::Iter>;
}
impl<'t> Iter<'t> for Word<'t, usize> {
type Iter = Segments<'t, Cloned<slice::Iter<'t, usize>>>;
fn iter(&'t self) -> Hyphenating<'t, Self::Iter> {
Hyphenating::new(Segments::new(self.text, self.breaks.iter().cloned()))
}
}
impl<'t> IntoIterator for Word<'t, usize> {
type Item = String;
type IntoIter = Hyphenating<'t, Segments<'t, vec::IntoIter<usize>>>;
fn into_iter(self) -> Self::IntoIter {
Hyphenating::new(Segments::new(self.text, self.breaks.into_iter()))
}
}
impl<'t> IntoIterator for Word<'t, (usize, Option<&'t Subregion>)> {
type Item = String;
type IntoIter = Hyphenating<'t,
SegmentsExt<'t, vec::IntoIter<(usize, Option<&'t Subregion>)>>
>;
fn into_iter(self) -> Self::IntoIter {
Hyphenating::new(SegmentsExt::new(self.text, self.breaks.into_iter()))
}
}
/// An iterator over borrowed slices delimited by Standard hyphenation
/// opportunities.
#[derive(Clone, Debug)]
pub struct Segments<'t, I> {
text : &'t str,
breaks : I,
start : Option<usize>
}
impl<'t, I> Segments<'t, I> {
pub fn new(text : &'t str, breaks : I) -> Self {
Segments {
text,
breaks,
start : Some(0)
}
}
}
impl<'t, I> Iterator for Segments<'t, I> where I : Iterator<Item = usize> {
type Item = &'t str;
#[inline]
fn next(&mut self) -> Option<Self::Item> {
match self.breaks.next() {
None => self.start.take().map(|i| &self.text[i ..]),
Some(index) => {
let (start, end) = (self.start.unwrap(), index);
let segment = &self.text[start .. end];
self.start = Some(end);
Some(segment)
}
}
}
#[inline]
fn size_hint(&self) -> (usize, Option<usize>) {
let (lower, upper) = self.breaks.size_hint();
let stagger = self.start.iter().len();
(lower + stagger, upper.map(|n| n + stagger))
}
}
impl<'t, I> ExactSizeIterator for Segments<'t, I>
where I : Iterator<Item = usize> + ExactSizeIterator {}
/// An iterator over string segments delimited by Extended hyphenation
/// opportunities. A segment may be borrowed or owned, depending on whether
/// the break requires changes to neighboring letters.
#[derive(Clone, Debug)]
pub struct SegmentsExt<'t, I> {
text : &'t str,
breaks : I,
start : Option<usize>,
queued : Option<(usize, &'t str)>
}
impl<'t, I> SegmentsExt<'t, I> {
pub fn new(text : &'t str, breaks : I) -> Self {
SegmentsExt {
text,
breaks,
start : Some(0),
queued : None
}
}
fn substitute(&mut self, text : &'t str) -> Cow<'t, str> {
match self.queued.take() {
None => Cow::Borrowed(text),
Some((skip, ref subst)) => Cow::Owned([subst, &text[skip ..]].concat())
}
}
}
impl<'t, I> Iterator for SegmentsExt<'t, I>
where I : Iterator<Item = (usize, Option<&'t Subregion>)> {
type Item = Cow<'t, str>;
fn next(&mut self) -> Option<Self::Item> {
match self.breaks.next() {
None => self.start.take().map(|start| self.substitute(&self.text[start ..])),
Some((index, None)) => {
let start = self.start.unwrap();
self.start = Some(index);
Some(self.substitute(&self.text[start .. index]))
},
Some((index, Some(ref subr))) => {
let (start, end) = (self.start.unwrap(), index);
self.start = Some(index);
let (segment_start, fore) = self.queued.take().unwrap_or((start, ""));
let (segment_end, aft) = {
let (subst, queued) = subr.substitution.split_at(subr.breakpoint);
if queued.len() > 0 {
self.queued = Some((subr.right, queued));
}
(end - subr.left, subst)
};
let segment = [fore, &self.text[segment_start .. segment_end], aft].concat();
Some(Cow::Owned(segment))
}
}
}
#[inline]
fn size_hint(&self) -> (usize, Option<usize>) {
let (lower, upper) = self.breaks.size_hint();
let stagger = self.start.iter().len();
(lower + stagger, upper.map(|n| n + stagger))
}
}
impl<'t, I> ExactSizeIterator for SegmentsExt<'t, I>
where I : Iterator<Item = (usize, Option<&'t Subregion>)>
+ ExactSizeIterator {}
|
Wiper blade
ABSTRACT
A wiper blade having a lever assembly and a spoiler integrated in the lever assembly. The wiper blade has a wiper rubber and the lever assembly holding the wiper rubber and being coupled to a wiper arm. The lever assembly has a plurality of levers, adjacent levers of which are hinge-jointed to each other. The lever of the lever assembly includes a spoiler portion forming a section of a spoiler integrated in the lever.
CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims priority from Korean Patent Application No. 10-2011-0127918 (filed on Dec. 1, 2011) and Korean Patent Application No. 10-2012-0073347 (filed on Jul. 5, 2012), the entire subject matters of which are incorporated herein by reference.
TECHNICAL FIELD
The present invention relates to a wiper blade for wiping a windshield of a motor vehicle. More particularly, the present invention relates to a wiper blade with a spoiler.
BACKGROUND
Motor vehicles are equipped with a windshield wiper device for cleaning or wiping a surface of a windshield. The windshield wiper device includes a wiper blade, a wiper arm and a wiper motor oscillating the wiper arm. The wiper blade is releasably coupled to the wiper arm. The wiper blade is placed on the surface of the windshield by the wiper arm. The wiper blade wipes the surface of the windshield while sliding thereon through oscillation motions of the wiper arm.
The wiper blade has an elongated wiper rubber and a frame structure. The wiper rubber is placed in contact with the windshield surface. The frame structure holds and supports the wiper rubber along its length. The frame structure may include an assembly having a main lever and a plurality of yoke levers linked to the main lever. The main lever is connected to the wiper arm. The yoke lever is linked to the main lever or another yoke lever at its middle. The yoke levers hold the wiper rubber.
When a motor vehicle runs, wind or air stream impinging against the windshield applies a force to the wiper blade along the entire length of the wiper blade placed on the windshield. The wiper blade generally stands upright on the surface of the inclined windshield. Thus, the force applied by the wind or air stream acts in a direction of lifting the wiper blade from the surface of the windshield. The faster the motor vehicle runs, the stronger such a lift force would be. This weakens the contact between the wiper rubber and the windshield surface, thus deteriorating wiping performance.
To address the deterioration in wiping performance caused by the lift of a wiper blade, it is known in the art to attach a spoiler to the wiper blade. The spoiler interacts with wind or air stream and thereby applies a force in a direction opposite to the lift of the wiper blade. By way of example, Korean Patent Application Publication No. 10-2003-0031158 discloses a wiper blade with a spoiler attached to a main lever. It is also disclosed in the art to attach a cover to a wiper blade so as to cover a main lever and a yoke lever. By way of another example, Korean Patent Application Publication No. 10-2006-0051763 discloses a wiper blade with such a cover.
SUMMARY
The lower an entire height of the lever assembly holding the wiper blade, the less air resistance the lever assembly could be subjected to. However, the prior art lever assembly of the wiper blade has difficulties in reducing its entire height due to a fur cate configuration of its levers. The wiper blade with the spoiler attached to the lever assembly requires that the spoiler be prepared separately from and attached to the lever assembly. This may increase manufacturing cost of the wiper blade and further lead to detachment of the spoiler from the wiper blade. Further, the wiper blade with the cover covering the lever assembly needs parts for joining the cover to the lever assembly. This may increase the number of the parts of the wiper blade and cause increase in manufacturing cost.
The present invention is directed to solving the aforementioned problems of the prior art. The present invention provides a wiper blade wherein a lever assembly holding a wiper rubber has a low entire height. Further, the present invention provides a wiper blade wherein a spoiler is integrated in a lever assembly.
In one exemplary embodiment of the present invention, the wiper blade includes a wiper rubber and a lever assembly holding the wiper rubber and coupled to a wiper arm. The lever assembly includes a plurality of levers, adjacent levers of which are hinge-jointed to each other. The lever includes a spoiler portion forming a section of a spoiler, which is integrated in the lever.
In an embodiment of the present invention, the spoiler portion includes an inclined surface extending in a longitudinal direction of the wiper rubber and defining the section of a spoiler. At least a portion of a lateral surface of the spoiler portion forms the inclined surface.
In an embodiment of the present invention, the inclined surface comprises a forward inclined surface facing forward in a running direction of a motor vehicle and a backward inclined surface opposed to the forward inclined surface. The lever has at least one air hole in the backward inclined surface.
In an embodiment of the present invention, one of the adjacent levers includes an arm extending from the spoiler portion thereof toward the other of the adjacent levers and holding the wiper rubber at a distal end. The arm is situated in and hinge-jointed to the spoiler portion of the other of the adjacent levers. The arm is hidden in the spoiler portion of the other of the adjacent levers. The arm and the spoiler portion of the one of the adjacent levers extend straight.
In an embodiment of the present invention, the other of the adjacent levers includes a joint portion extending from the spoiler portion thereof toward the one of the adjacent levers and hinge-jointed to the arm. The lever assembly further includes a joint cover that is coupled to the joint portion between the one of the adjacent levers and the other of the adjacent levers. The joint cover has a cross-sectional profile corresponding to a cross-sectional profile of the spoiler portion of the one of the adjacent levers and a cross-sectional profile of the spoiler portion of the other of the adjacent levers.
In an embodiment of the present invention, the lever assembly further includes a joint nested on and hinge-jointed to the arm. The joint is coupled to the spoiler portion of the other of the adjacent levers.
In an embodiment of the present invention, one of the arm and the spoiler portion of the other of the adjacent levers includes a pair of hinge pins, while the other of the arm and the spoiler portion of the other of the adjacent levers includes a pair of fitting holes to which the pair of the hinge pins are fitted respectively. The spoiler portion of the other of the adjacent levers includes a pair of raised portions therein. The raised portions are spaced apart to receive the arm. Opposing end surfaces of the adjacent levers are inclined at an acute angle toward an end of the wiper rubber. An outermost lever of the levers includes: a clamp formed at an end portion of the spoiler portion thereof and holding the wiper rubber; and a pressing portion located opposite to the clamp and bringing the wiper rubber into contact with the clamp. The lever has a plurality of transverse ribs and a longitudinal rib intersecting the transverse ribs.
In an embodiment of the present invention, an outermost lever of the levers includes a clamp formed at an end portion of the spoiler portion thereof and holding the wiper rubber; and a clamp insert fitted to the clamp and bringing the wiper rubber into contact with the clamp.
In an embodiment of the present invention, the lever assembly includes a covering sheet covering an interior of the lever assembly.
In an embodiment of the present invention, the section of a spoiler comprises a central spoiler and an end spoiler adjoining the central spoiler and the plurality of the levers comprises a central lever and a pair of end levers. The central lever includes a pair of central spoiler portions each forming the central spoiler and is coupled to the wiper arm between the central spoiler portions. Each of the end levers includes an end spoiler portion and an end arm. The end spoiler portion forms the end spoiler and adjoins the central spoiler portion. The end spoiler portion holds the wiper rubber. The end arm is hidden in and hinge-jointed to the central spoiler portion. The end arm extends from the end spoiler portion toward the central lever and holds the wiper rubber.
In an embodiment of the present invention, the section of a spoiler comprises a central spoiler, an intermediate spoiler adjoining the central spoiler and an end spoiler adjoining the intermediate spoiler. The plurality of the levers comprises a central lever, a pair of intermediate levers and a pair of end levers. The central lever includes a pair of central spoiler portions each forming the central spoiler and is coupled to the wiper arm between the central spoiler portions. Each of the intermediate levers includes an intermediate spoiler portion and intermediate arm. The intermediate spoiler portion forms the intermediate spoiler and adjoins the central spoiler portion. The intermediate arm is hidden in and hinge-jointed to the central spoiler portion. The intermediate arm extends from the intermediate spoiler portion toward the central lever and holds the wiper rubber. Each of the end levers includes an end spoiler portion and an end arm. The end spoiler portion forms the end spoiler and adjoins the intermediate spoiler portion. The end spoiler portion holds the wiper arm. The end arm is hidden in and hinge-jointed to the intermediate spoiler portion. The end arm extends from the end spoiler portion toward the intermediate lever and holds the wiper rubber. The intermediate lever includes a yoke lever that is hinge-jointed to a distal end of the intermediate arm and holds the wiper rubber at both ends.
In an embodiment of the present invention, the spoiler has a cross-sectional profile that varies in a longitudinal direction of the wiper rubber or includes one of a triangle with both curved legs, a semicircle and a semi ellipse.
In the wiper blades according to the embodiments, the lever assembly includes a plurality of levers and the spoiler portion of each lever forms the section of a spoiler of the wiper blade. The lever assembly is configured such that the spoiler portions of the respective levers are straight adjoined one after another and a portion of one lever except for its spoiler portion is hidden in the spoiler portion of another adjacent lever. Thus, the lever assembly has a low entire height and the spoiler portions adjoined one after another in the lever assembly form a spoiler of the wiper blade. Accordingly, due to the lever assembly with the spoiler integrated therein and having straight-adjoined levers, the wiper blade can have a smaller number of parts and effectively prevent its lift.
BRIEF DESCRIPTION OF THE DRAWINGS
Arrangements and embodiments may be described in detail with reference to the following drawings in which like reference numerals refer to like elements or components, wherein:
FIG. 1 is a perspective view showing a wiper blade in accordance with a first embodiment;
FIG. 2 is a top view of the wiper blade shown in FIG. 1;
FIG. 3 is a front elevational view of the wiper blade shown in FIG. 1;
FIG. 4 is a left side view of the wiper blade shown in FIG. 1;
FIG. 5 is a right side view of the wiper blade shown in FIG. 1;
FIG. 6 is a sectional view taken along the line 6-6 in FIG. 1;
FIG. 7 is a sectional view taken along the line 7-7 in FIG. 1;
FIG. 8 is a perspective view showing a wipe rubber and spring rails of the wiper blade according to the first embodiment;
FIG. 9 is a fragmental front view of the wiper rubber shown in FIG. 8;
FIG. 10 is a front view of a central lever of the wiper blade according to the first embodiment;
FIG. 11 is a top view of the central lever shown in FIG. 10;
FIG. 12 is a bottom view of the central lever shown in FIG. 10;
FIG. 13 is a left side view of the central lever shown in FIG. 10;
FIG. 14 is a front view of an end lever of the wiper blade according to the first embodiment;
FIG. 15 is a top view of the end lever shown in FIG. 14;
FIG. 16 is a bottom view of the end lever shown in FIG. 14;
FIG. 17 is a right side view of the end lever shown in FIG. 14;
FIG. 18 is a left side view of the end lever shown in FIG. 14;
FIG. 19 is an upper perspective view of a clamp insert;
FIG. 20 is a lower perspective view of the clamp insert shown in FIG. 19;
FIG. 21 is a right side view of the clamp insert shown in FIG. 19;
FIG. 22 is a front view of the clamp insert shown in FIG. 19;
FIG. 23 depicts the insertion of the clamp insert to a clamp;
FIG. 24 shows the end lever with the clamp insert fitted thereto;
FIG. 25 is a front view showing an assembly example of the wiper blade according to the first embodiment;
FIG. 26 is a front view of a hinge insert;
FIG. 27 is a left side view of the hinge insert shown in FIG. 26;
FIG. 28 is a right side view of a joint cover;
FIG. 29 is a longitudinally sectional view of the joint cover shown in FIG. 28;
FIG. 30 is a perspective view showing a wiper blade in accordance with a second embodiment;
FIG. 31 is a top view of the wiper blade shown in FIG. 30;
FIG. 32 is a front view of the wiper blade shown in FIG. 30;
FIG. 33 is a left side view of the wiper blade shown in FIG. 30;
FIG. 34 is a right side view of the wiper blade shown in FIG. 30;
FIG. 35 is a front view of an intermediate lever of the wiper blade according to the second embodiment;
FIG. 36 is a top view of the intermediate lever shown in FIG. 35;
FIG. 37 is a bottom view of the intermediate lever shown in FIG. 35;
FIG. 38 is a left side view of the intermediate lever shown in FIG. 35;
FIG. 39 is a left side view of an end lever of the wiper blade according to the second embodiment;
FIG. 40 is a top view of the end lever shown in FIG. 39;
FIG. 41 is a bottom view of the end lever shown in FIG. 39;
FIG. 42 is a left side view of the end lever shown in FIG. 39;
FIG. 43 is a front view showing an assembly example of the wiper blade according to the second embodiment;
FIG. 44 is a perspective view showing a wiper blade in accordance with a third embodiment;
FIG. 45 is a top view of the wiper blade shown in FIG. 44;
FIG. 46 is a front view of the wiper blade shown in FIG. 44;
FIG. 47 is a front view of a central lever of the wiper blade according to the third embodiment;
FIG. 48 is a bottom view of the central lever shown in FIG. 47;
FIG. 49 is a front view of an intermediate lever of the wiper blade according to the third embodiment;
FIG. 50 is a top view of the intermediate lever shown in FIG. 49;
FIG. 51 is a left side view of the intermediate lever shown in FIG. 49;
FIG. 52 is a front view of a yoke lever of the wiper blade according to the third embodiment;
FIG. 53 is a right side view of the yoke lever shown in FIG. 52;
FIG. 54 is a front view of a hinge insert of the yoke lever;
FIG. 55 is a top view of the hinge insert shown in FIG. 54;
FIG. 56 is a front view showing an assembly example of the wiper blade according to the third embodiment;
FIG. 57 is a front view of a wiper blade in accordance with a fourth embodiment;
FIG. 58 is a top view of the wiper blade shown in FIG. 57;
FIG. 59 depicts a coupling example between a joint and an intermediate lever in the wiper blade according to the fourth embodiment;
FIG. 60 depicts a coupling example between an intermediate lever and a central lever in the wiper blade according to the fourth embodiment;
FIG. 61 is a perspective view showing a wiper blade in accordance with a fifth embodiment;
FIG. 62 is a top view of the wiper blade shown in FIG. 61;
FIG. 63 is a front view of the wiper blade shown in FIG. 61;
FIG. 64 is an exploded perspective view of a lever assembly of the wiper blade according to the fifth embodiment;
FIG. 65 is a lower perspective view of the lever assembly shown in FIG. 64;
FIG. 66 is a left side view of a central lever of the lever assembly shown in FIG. 64;
FIG. 67 is a fragmentary longitudinal sectional view of the central lever of the lever assembly shown in FIG. 64;
FIG. 68 is a left side view of an intermediate lever of the lever assembly shown in FIG. 64;
FIG. 69 is a longitudinal sectional view of the intermediate lever of the lever assembly shown in FIG. 64;
FIG. 70 is a left side view of an end lever of the lever assembly shown in FIG. 64;
FIG. 71 is a longitudinal sectional view of the end lever of the lever assembly shown in FIG. 64;
FIG. 72 depicts an assembly example of the wiper blade according to the fifth embodiment;
FIG. 73 is a rear perspective view of a wiper blade in accordance with a sixth embodiment;
FIG. 74 is a top view of the wiper blade shown in FIG. 73;
FIG. 75 is a rear view of the wiper blade shown in FIG. 73;
FIG. 76 is a schematic sectional view taken along the line 76-76 in FIG. 73;
FIG. 77 is a rear view of the wiper blade according to the sixth embodiment showing another example of an air hole;
FIG. 78 is a schematic sectional view taken along the line 78-78 in FIG. 77;
FIG. 79 is an exploded perspective view of a wiper blade in accordance with a seventh embodiment;
FIG. 80 is a bottom view of the wiper blade shown in FIG. 79;
FIG. 81 shows an example of a cross-section of the wiper blade shown in FIG. 79;
FIG. 82 is similar to FIG. 3 and shows another example of a cross-sectional profile of a spoiler; and
FIG. 83 is similar to FIG. 6 and shows yet another example of a cross-sectional profile of a spoiler.
DETAILED DESCRIPTION
Detailed descriptions are made as to embodiments of a wiper blade with reference to the accompanying drawings. The directional term “upper,” “upward” or the like as used herein is generally based on a position, in which a lever assembly is disposed relative to a wiper rubber in the drawings, while the directional term “lower,” “downward” or the like generally refers to a direction opposite to the upper or upward direction. A wiper blade shown in the accompanying drawings may be otherwise oriented (e.g., rotated 180 degrees or at other orientations) and the aforementioned directional terms may be interpreted accordingly. Further, as used herein, the term “longitudinal inner end” or “longitudinal inner end portion” generally refers to an end that is closer to a center of a wiper blade in a longitudinal direction of an element, while the term “longitudinal outer end” or “longitudinal outer end portion” refers to the other end opposite to the inner end or the inner end portion.
Wiper blades according to embodiments have a lever assembly that holds or retains a wiper rubber to be placed on a surface of a windshield. The lever assembly is coupled to a wiper arm and supports the wiper rubber. The lever assembly includes a plurality of levers, which are joined straight one after another in a longitudinal direction of the wiper rubber and are at substantially the same height on the wiper rubber. Two adjacent levers are hinge-jointed to each other.
Further, the wiper blades according to embodiments include a spoiler that produces a reaction force preventing the lift of the wiper blade, which wind or air stream may cause. The spoiler is integrated in the lever assembly in the longitudinal direction of the wiper blade. A spoiler section, which becomes a section of the spoiler, is integrated in each lever of the lever assembly. That is, each lever has a spoiler portion defining said spoiler section. Since the levers are arranged in a straight line, the spoiler portions of the respective levers are adjoined one after another, thus forming the portion or the entirety of the spoiler.
The spoiler portion has at least one or a pair of inclined surfaces that produce the reaction force preventing the lift caused by wind or air stream. The inclined surface extends in the spoiler portion in the longitudinal direction of the wiper rubber and defines the spoiler section that is located in each lever. Further, the inclined surface forms the portion or the entirety of a lateral surface of the spoiler portion. The inclined surface may include a flat surface, a concave or convex curved surface, etc. The pair of the inclined surfaces may be at least partially symmetrical in a width direction of each lever. Further, one of the pair of the inclined surfaces may have a width larger than that of the other.
One or more levers among the levers of the lever assembly have a holding portion configured to hold the wiper rubber. The holding portion comprises an arm that extends from the spoiler portion provided in one of two adjacent levers toward the other of the adjacent levers, which is further inward or outward than the one of the adjacent levers in the lever assembly. Lower edges of the arm and the spoiler portion are approximately straight. That is, the arm and the spoiler extend in a straight line. The adjacent levers are joined to each other in such a manner that the arm of one of the levers is situated in the spoiler portion of the other of the levers and the arm and the spoiler portion of the other lever are hinge-jointed to each other. When the adjacent levers are joined together, the respective spoiler portions are at an approximately equal height on the wiper rubber and the arm of one of the adjacent levers is hidden inside the spoiler portion of the other adjacent levers.
In the embodiments, the lever assembly has a central lever to be coupled to a wiper arm. The lever assembly is constructed in such a manner that levers configured to hold the wiper rubber are joined to the central lever. In one embodiment, the lever assembly includes a central lever and a pair of end levers, thus holding the wiper rubber at four pressure points. The central lever is located in the middle of the lever assembly and the end levers are located at an outermost position in the lever assembly. In another embodiment, the lever assembly includes a central lever, a pair of intermediate levers and a pair of end levers, thus holding the wiper rubber at six or eight pressure points. The intermediate lever is interposed between the central lever and the outermost end lever.
FIGS. 1 to 29 show a wiper blade according to a first embodiment, generally denoted by 100, and elements or components constituting the wiper blade 100. The wiper blade 100 has a wiper strip or wiper rubber 110, which is placed on a surface of a windshield of a motor vehicle, and a lever assembly 1000 holding the wiper rubber 110. Further, the wiper blade 100 includes a pair of spoilers 130L, 130R that produce a reaction force preventing the lift caused by wind or air stream. The left spoiler 130L and the right spoiler 130R are symmetrical relative to a longitudinal center of the wiper rubber 110. The spoilers 130L, 130R are integrally formed in the lever assembly 1000 and extend in the longitudinal direction of the wiper rubber 110.
The wiper rubber 110 may be made from a rubber or plastic material having elasticity. Referring to FIGS. 8 and 9, the wiper rubber 110 has an elongated body portion 111 and a wiper lip 112 longitudinally extending beneath the body portion 111 and contacting the windshield surface. Further, the wiper rubber 110, at either side of the body portion 111, has two rows of grooves 113, 114 that extend in the longitudinal direction of the wiper rubber. A first groove 113 extends along the body portion 111 right below a top side of the body portion 111. A second groove 114 extends along the body portion 111 below the first groove 113. Spring rails 120 are inserted to the first grooves 113 respectively. Both ends of a clamp provided in a lever of the lever assembly 1000 are fitted to the second grooves 114 respectively. Further, a portion, to which an outermost clamp of the clamps of the levers is fitted, is formed in the vicinity of one end of the wiper rubber 110. That is, in the vicinity of the one end of the wiper rubber 110, stoppers 115 protrude between the top side and the first grooves 113 and recesses 116 are defined in edges of the top side due to the stoppers 115. Further, insertion holes 117, to which the ends of the outermost clamp are inserted to, are formed below the recesses 116. The insertion holes 117 are located in the vicinity of the one end of the second groove 114. When the lever assembly 1000 and the wiper rubber 110 are assembled together, the ends of the outermost clamp are fitted to the insertion holes 117 and a part to be inserted to the outermost clamp (this will be described below) is placed in the recesses 116, thus holding the wiper rubber 110 against the outermost clamp.
The spring rails 120 (referred to as a “vertebra” in the art) are inserted to the wiper rubber 110 in the longitudinal direction and impart rigidity to the wiper rubber 110. Further, the spring rails 120 distribute pressure applied by a wiper arm, along the entire length of the wiper rubber 110. The spring rails 120 are made from a metallic material and have a shape of a thin elongated bar. The spring rails 120 are inserted to the first grooves 113 of the wiper rubber 110 respectively. The spring rail 120 has a concave notch 121 at either end and the first groove 113 has a protrusion 118 engaging the notch. Some embodiments may include the spring rails 120 that are inlaid or embedded to the body portion 111 of the wiper rubber 110.
The lever assembly 1000 connects the wiper rubber 110, to which the spring rails 120 are fitted to (hereinafter, the wiper rubber with the spring rails fitted thereto is referred to as a “wiper rubber assembly 110, 120”), to a wiper arm (not shown) of a wiper device. Further, the lever assembly 1000 supports the wiper rubber assembly 110, 120 with respect to the wiper arm. The wiper arm is coupled to a rotating shaft of a wiper motor of the wiper device at its base end and is oscillated by the wiper motor. The wiper blade 100 is coupled to the wiper arm in such a manner that the lever assembly 1000 is releasably attached to a distal end of the wiper arm. The wiper blade 100 wipes the surface of the windshield while sliding thereon through oscillation motions of the wiper arm. In this embodiment, the lever assembly 1000 includes a central lever 1100 centrally located with respect to the wiper rubber assembly 110, 120 and a pair of end levers 1300L, 1300R joined to the central lever respectively. The levers have an elongated hollow shape and may be made by pressing a metallic sheet or injection-molding a plastic material.
Referring to FIGS. 1 to 3, the pair of the spoilers 130L, 130R are formed in an upper surface of the lever assembly 1000 along its longitudinal direction (or along the longitudinal direction of the wiper rubber 110). A portion of the upper surface of the lever assembly 1000 (a portion of an upper or lateral surface of each lever constituting the lever assembly) forms the spoiler 130L, 130R. Each spoiler 130L, 130R reacts to wind or air stream impinging against the wiper blade 100 during running of a motor vehicle and produces a reaction force preventing the wiper blade 100 from being lifted. Such a reaction force is produced by interaction between wind or air stream and a contour of a cross-section (hereinafter referred to as a “cross-sectional profile”) of the spoiler 130L, 130R. The cross-sectional profile may be constant or may vary (e.g. diminish or enlarge) in the longitudinal direction of the lever assembly 1000. That is, the cross-sectional profile may be constant in the longitudinal direction of the lever assembly 1000 or may diminish in width and height dimensions toward a distal end of the wiper blade 100. Further, the cross-sectional profile may be symmetrical or asymmetrical in a width direction of the lever assembly (in a direction perpendicular to the longitudinal direction of the wiper rubber). In this embodiment, as shown in FIGS. 6 and 7, the cross-sectional profile of the spoiler 130L, 130R includes a triangle with somewhat concave legs. That is, the cross-sectional profile of the spoiler 130L, 130R includes a pair of concave curves that are symmetrical in the width direction of the wiper rubber 110.
Since a pair of the end levers 1300L, 1300R are joined to the central lever 1100, each longitudinal half of the lever assembly 1000 has the same configuration. Each spoiler 130L, 130R comprises spoiler sections located in respective levers 1100, 1300L, 1300R of the lever assembly 1000. The spoiler sections of the respective levers are straight adjoined one after another, i.e., they are consecutively adjoined with the spoiler sections of adjacent levers adjoining each other, thereby defining the spoiler 130L, 130R of the wiper blade 100. A spoiler portion included in each lever forms each corresponding spoiler section. Further, a portion of the upper surface of the lever, specifically a portion of a lateral surface of the lever, more specifically a portion or the entirety of the lateral surface of the spoiler portion forms the corresponding spoiler section. In the below descriptions on the wiper blade 100 according to the first embodiment, regarding the spoiler 130L, 130R integrally formed in the lever assembly 1000, a spoiler section integrated in the central lever 1100 to become a section of the spoiler 130L, 130R is referred to as a central spoiler 131L, 131R, while a spoiler section integrated in the end lever 1300L, 1300R to become another section of the spoiler 130L, 130R is referred to as an end spoiler 133L, 133R.
The central lever 1100 is releasably coupled to the distal end of the wiper arm. Referring to FIGS. 10 to 13, the central lever 1100 includes a bracket portion 1110 at its middle. Further, the central lever 1100 includes a pair of central spoiler portions 1120 that extend from the bracket portion 1110 in opposite longitudinal directions (in the longitudinal direction of the wiper rubber 110) and form the central spoiler 131L, 131R respectively.
The bracket portion 1110 generally has a shape of a vertically-pierced rectangular parallelepiped. Fitting apertures 1111 are formed in width wise opposing lateral walls of the bracket portion 1110 respectively. A pin or rivet 1112 (see FIG. 25) is fitted to the fitting apertures 1111. The rivet 1112 participates in connection to the wiper arm. An adaptor (not shown), which is configured to be connected to a corresponding element provided in the distal end of the wiper arm through fitting, snapping, engaging, etc., may be coupled to the rivet 1112. The rivet 1112 may function as a pivot shaft of the wiper blade 100.
A lower edge of the central lever 1100 (lower edges of the bracket portion 1110 and the central spoiler portion 1120) is straight or upwardly curved with slight curvature. The central spoiler portion 1120 has an inverted V-shaped cross-section. The central spoiler portion 1120 has a pair of inclined surfaces 1121F, 1121R that are symmetrical in the width direction of the central lever 1100. The inclined surfaces 1121F, 1121R are located in the lateral surfaces of the central spoiler portion 1120. The inclined surfaces 1121F, 1121R extend in the longitudinal direction of the wiper rubber 110 in the central lever 1100 and form the lateral surfaces of the central spoiler portion 1120. Accordingly, the central spoiler 131L, 131R is integrated in the central lever 1100 through the central spoiler portion 1120 having the inclined surfaces 1121F, 1121R. An apex portion 1122 interconnects the inclined surfaces 1121F, 1121R at their upper edges.
The inclined surfaces 1121F, 1121R may include a flat, concave or convex surface. In this embodiment, the inclined surfaces 1121F, 1121R are concave. A width of the apex portion 1122 becomes sharply narrow from the bracket portion 1110 and is then constant. The inclined surfaces 1121F, 1121R are concave in harmony with such a width of the apex portion 1122. Thus, the cross-sectional profile of the central spoiler 131L, 131R, which the inclined surfaces 1121F, 1121R of the central spoiler portion 1120 define, is generally a triangle with both concave legs. The central spoiler portion 1120 has a stepped surface 1124 that is further inward than a longitudinal outer end portion 1123. The stepped surface 1124 is inclined at an acute angle toward the center of the central lever 1100. The longitudinal outer end portion 1123 has width and height dimensions less than those of the central spoiler portion 1120. Further, the central lever 1100 has a joint portion 1125 extending from the longitudinal outer end portion 1123 of the central spoiler portion 1120. The joint portion 1125 has an inverted U-shaped cross-section and has width and height dimensions less than those of the outer end portion 1123. Further, the central spoiler portion 1120 has an arm receiving portion 1126 that receives a portion of the end lever 1300L, 1300R and hides the same therein. The arm receiving portion 1126 is defined by a space between the inclined surfaces 1121F, 1121R and an interior space of the joint portion 1125. The joint portion 1125 has a slit 1127 at its top and indentations 1128 at its lower edge. A positioning protrusion of a joint cover (this will be described below) is inserted to the slit 1127 of the joint portion and the slit 1127 participates in positioning the joint cover. A claw of the joint cover (this will be described below) engages the indentation 1128 of the joint portion, thereby preventing separation of the joint cover.
Each end lever 1300L, 1300R is joined to the central lever 1100 and holds the wiper rubber assembly 110, 120. Descriptions are made as to the end lever 1300L with reference to FIGS. 14 to 18. The end lever 1300R and the end lever 1300L are symmetrical in the longitudinal direction of the lever assembly 1000. The end lever 1300L, 1300R includes an end arm 1310 to be situated in the arm receiving portion 1126 of the central spoiler portion 1120 and an end spoiler portion 1320 oppositely extending from the end arm 1310. The end arm 1310 has an inverted U-shaped cross-section. The end spoiler portion 1320 has an inverted V-shaped cross-section. The end arm 1310 extends from a longitudinal inner end portion 1323 of the end spoiler portion 1320 toward the central lever 1100. A lower edge of the end arm 1310 and a lower edge of the end spoiler portion 1320 form an approximately straight line.
The end spoiler 133L, 133R is integrally formed in the end spoiler portion 1320 of the end lever 1300L, 1300R. The end spoiler portion 1320 has a pair of inclined surfaces 1321F, 1321R that are symmetrical in the width direction of the end lever 1300L, 1300R. The inclined surfaces 1321F, 1321R are located in the lateral surfaces of the end spoiler portions 1320. The inclined surfaces 1321F, 1321R extend in the longitudinal direction of the wiper rubber 110 in the end lever 1300L, 1300R and form the lateral surfaces of the end spoiler portion 1320. Accordingly, the end spoiler 133L, 133R is integrated in the end lever 1300L, 1300R through the end spoiler portion 1320 having the inclined surfaces 1321F, 1321R. An apex portion 1322 interconnects the inclined surfaces 1321F, 1321R at their upper edges. The inclined surfaces 1321F, 1321R may include a flat, concave or convex surface. In this embodiment, the inclined surfaces 1321F, 1321R are concave in the width direction of the end lever 1300L, 1300R. Further, a height dimension of the inclined surfaces 1321F, 1321R decreases gradually toward the distal end of the wiper blade 100. Further, lower edges of the inclined surfaces 1321F, 1321R approach each other at the distal end of the end lever 1300L, 1300R, thereby forming a round distal end of the end lever 1300L, 1300R along with the apex portion 1322. The inclined surfaces 1321F, 1321R of the end spoiler portion 1320 may be curved with the same curvature as that of the inclined surfaces 1121F, 1121R of the central spoiler portion 1120, or curved with a curvature varying therefrom. In this embodiment, the inclined surfaces 1321F, 1321R of the end spoiler portion 1320 is curved with the same curvature as that of the inclined surfaces 1121F, 1121R at the stepped surface 1124 of the central spoiler portion 1120.
Each end lever 1300L, 1300R has two clamps 1311, 1325 for holding the wiper rubber assembly 110, 120. A longitudinal inner clamp 1311 is formed at a distal end of the end arm 1310. A longitudinal outer clamp 1325 is formed at a lower edge of the end spoiler portion 1320 in the vicinity of a longitudinal outer end thereof.
As shown in FIG. 17, the clamp 1311 has a generally rectangular cross-section with its bottom side cut away partially and thus both ends thereof extend inwardly. When the end lever 1300L, 1300R is coupled to the wiper rubber assembly 110, 120, an upper inner surface of the clamp 1311 is placed on a top side of the wiper rubber 110 and lateral portions of the clamp 1311 sandwich the spring rail 120 and a portion of the wiper rubber 110 adjacent thereto and the both ends of the clamp 1311 are inserted to the second groove 114.
Referring to FIGS. 14 and 18, the clamp 1325 extends from the lower edge of the end spoiler portion 1320 in a V shape. Both ends of the clamp 1325 are inserted to the second groove 114 of the wiper rubber 110. A longitudinal outer surface 1325 a of the clamp 1325 is inclined longitudinally outwardly, while a longitudinal inner surface 1325 b is inclined longitudinally inwardly. A portion of the end lever 1300L, 1300R, at which the clamp 1325 is located, is hollow. To ensure fixation between the clamp 1325 and the wiper rubber 110, a clamp insert 1330 is fitted to the clamp 1325. The clamp insert 1330 is intervened between the wiper rubber 110 and the portion of the end lever 1300L, 1300R where the clamp 1325 is located. That is, as shown in FIG. 14, the lever assembly 1000 has the clamp insert 1330 that is fitted to the clamp 1325 of the end lever 1300L, 1300R to fix the wiper rubber assembly 110, 120 to the clamp 1325. FIGS. 16 to 18 do not show the clamp insert 1330 to clearly depict the interior of the end lever.
Reference is made to FIGS. 19 to 24 and descriptions are made as to the clamp insert 1330. The clamp insert 1330 is shaped to mate with a cross section formed by the inclined surfaces 1321F, 1321R, the apex portion 1322 and the clamp 1325 in the end lever 1300L, 1300R. Further, the clamp insert 1330 is configured to snap-engage the clamp 1325 and sandwich or pinch the wiper rubber 110. The clamp insert 1330 has a body portion 1331, a pair of sandwiching portions 1332 located beside the body portion 1331 and coupled to the clamp 1325, and a pressing portion 1333 formed in the body portion 1331 to abut or press the top side of the wiper rubber 110. The body portion 1331 extends in the longitudinal direction of the end lever 1300L, 1300R. On a top side of the body portion 1331 is formed a longitudinally-extending head portion 1334, which contacts the inner surface of the apex portion 1322 of the end lever or is positioned with a slight gap therebetween. A sandwiching space 1338, in which an upper portion of the wiper rubber 110 is received, is defined between the body portion 1331 and the sandwiching portion 1332.
The sandwiching portion 1332 is formed in a rib portion 1335 extending the top side of the body portion 1331. Thus, the sandwiching portion 1332 can snap-engage the clamp 1325 through the rib portion 1335 elastically bending inwardly and outwardly of the body portion 1331. The sandwiching portion 1332 extends in the longitudinal direction of the body portion 1331. Claws 1336, 1337 are formed at longitudinal inner and outer ends of the sandwiching portion 1332 respectively. The longitudinal outer claw 1336 engages the longitudinal outer surface 1325 a of the clamp 1325. A longitudinally leading end of the outer claw 1336 is inwardly inclined for easy insertion of the clamp insert 1330 to the clamp 1325. The longitudinal inner claw 1337 engages the longitudinal inner surface 1325 b of the clamp 1325. Further, a longitudinal inner surface of the outer claw 1336 and a longitudinal outer surface of the inner claw 1337 are inclined to correspond to the longitudinal outer surface 1325 a and the longitudinal inner surface 1325 b of the clamp 1325 respectively.
At least a portion of the body portion 1331 protrudes downwardly to thus form the pressing portion 1333. The pressing portion 1333 is formed to be located above the both ends of the clamp 1325 when the clamp insert 1330 is fitted to the clamp 1325. An underside of the pressing portion 1333 is placed on or abuts the top side of the wiper rubber 110, thereby fixing the wiper rubber 110 to the clamp 1325 or pressing the wiper rubber against the both ends of the clamp 1325.
FIGS. 23 and 24 depict an example coupling between the end lever 1300L, 1300R and the clamp insert 1330. As shown in FIG. 23, the clamp insert 1330 snap-engages the clamp 1325 through insertion. The clamp insert 1330 is situated inside the end lever 1330L, 1300R and then is pushed toward the clamp 1325. Then, the outer claw 1326 is brought into abutment with the inner surface 1325 b of the clamp 1325. Since the sandwiching portion 1332 may be pushed toward the body portion 1331 via the rib portion 1335, the outer claw 1336 of the clamp insert 1330 can pass the clamp 1325. If the clamp insert 1330 is fitted to the clamp 1325, then the longitudinal outer and inner surfaces 1325 a, 1325 b of the clamp 1325 are between the outer claw 1336 and the inner claw 1337 of the clamp insert 1330. As shown in FIG. 24, when the lever assembly 1000 and the wiper rubber assembly 110, 120 are coupled to each other, the pressing portion 1333 of the clamp insert 1330 presses the top side of the wiper rubber 110 downwardly (toward the both ends of the clamp 1325). Alternatively, the pressing portion 1333 of the clamp insert 1330 is placed on the top side of the wiper rubber 110 with little gap. Thus, the wiper rubber 110 is firmly fixed to the clamp 1325 via the clamp insert 1330.
The central lever 1100 and the end lever 1300L, 1300L are joined to each other via hinge-joint. When the central lever 1100 and the end lever 1300L, 1300R are joined to each other, the end arm 1310 of the end lever is situated in the arm receiving portion 1126 of the central spoiler portion 1120 and is thus hidden within the central spoiler portion 1120 when viewed from outside. In other words, in the lever assembly 1000, a portion (e.g., the end arm 1310) of one of the adjacent levers (e.g., the end lever 1300L, 1300R) is inside the spoiler portion of the other of the adjacent levers (e.g., the central lever 1100), which is further inward than said one of the adjacent levers. The central lever 1100 and the end lever 1300L, 1300R are joined to each other through a hinge-joint portion 1400L, 1400R penetrating through both the joint portion 1125 of the central lever and the end arm 1310 of the end lever. The hinge-joint portion 1400L, 1400R may include, but is not limited to, a rivet joint or pin joint. In this embodiment, the hinge-joint portion 1400L, 1400R includes a rivet joint.
Referring to FIG. 25, the hinge-joint portion 1400L, 1400R includes a rivet 1410 serving as a hinge shaft and a hinge insert 1420 coupled to the rivet 1410. Through apertures 1126 for hinge-joint are formed in the joint portion 1125 of the central lever 1100 in a width direction thereof. Also, through apertures 1312 are formed in a portion of the end arm 1310 corresponding to the joint portion 1125 in a width direction thereof. Referring to FIGS. 26 and 27, the hinge insert 1420 has an inverted U-shaped cross-section. The hinge insert 1420 has through apertures 1421 in its opposing lateral portions. Further, the hinge insert 1420 has a width wise-oriented slit 1422 in its top and indentations 1423 at its lower edge. The slit 1422 and the indentation 1423 correspond to the slit 1127 and the indentation 1128 of the joint portion 1125 of the central lever respectively.
The hinge insert 1420 is nested on the end arm 1310 such that the through apertures 1421 and the through apertures 1312 are in alignment with each other. Thereafter, the joint portion 1125 of the central lever 1100 is nested on the hinge insert 1420 such that its through apertures 1126 are aligned with the through apertures 1421. The rivet 1410 is pierced through the through apertures 1126, 1421, 1312 and then riveted thereto, thus forming the hinge-joint portion 1400L, 1400R.
Referring to FIG. 25, when the central lever 1100 and the end lever 1300L, 1300R are joined to each other, the joint portion 1125 of the central lever 1100 is nested on the end arm 1310 of the end lever 1300L, 1300R with the hinge insert 1420 therebetween and the hinge-joint portion 1400L, 1400R is formed between the central lever 1100 and the end lever 1300L, 1300R. The lever assembly 1000 includes a joint cover 1430, which is disposed between the central lever 1100 and the end lever 1300L, 1300R to cover the hinge-joint portion 1400L, 1400R.
Referring to FIGS. 28 and 29, the joint cover 1430 has an inverted V-shaped cross-section. The joint cover 1430 has a pair of inclined surfaces 1431F, 1431R symmetrical in a width direction thereof. An apex portion 1432 interconnects the inclined surfaces 1431F, 1431R. The inclined surface 1431F, 1431R is concave. A curvature of the inclined surface 1431F, 1431R is equal to those of the inclined surface 1121F, 1121R of the central spoiler portion and the inclined surfaces 1321F, 1321R of the end spoiler portion. A height dimension of the inclined surface 1431F, 1431R decreases gradually from a longitudinal inner end 1435 toward a longitudinal outer end 1436. A cross-sectional profile of the joint cover 1430 corresponds to both the cross-sectional profile of the central spoiler portion 1120 and the cross-sectional profile of the end spoiler portion 1320. That is, the cross-sectional profile of the joint cover 1430 decreases gradually in its height dimension toward the distal end of the lever assembly 1000. The joint cover 1430 has the cross-section profile achieving such decrease. In this embodiment, the cross-sectional profile of the joint cover 1430 includes a triangle having concave legs.
The longitudinal inner end 1435 is inclined at the same angle as the stepped surface 1124 of the central spoiler portion 1120 and is capable of contacting the stepped surface 1124 of the central spoiler portion 1120. The longitudinal outer end portion 1123 of the central spoiler portion 1120 is situated within the inclined surfaces 1431F, 1431R of the joint cover. Further, the longitudinal outer end 1436 is inclined at the same angle as a stepped surface 1324 of the end spoiler portion 1430 and is capable of contacting the stepped surface 1324 of the end spoiler portion 1320. The joint cover 1430 snap-engages the joint portion 1125 of the central lever. The joint cover 1430 has a protrusion or claw 1433 protruding from a lower inner surface of the inclined surface 1431F, 1431R. The claw 1433 snap-engages the indentation 1128 of the joint portion 1125. Further, the joint cover 1430 has a pair of positioning protrusions 1434 protruding from a lower surface of the apex portion 1432. The positioning protrusions 1434 are inserted to the slit 1127 of the joint portion 1125.
The stepped surface 1124 of the central lever 1100 is inclined at an acute angle inwardly of the wiper blade 100, while the stepped surface 1324 of the end lever 1300L, 1300R is inclined at an acute angle toward the distal end of the wiper blade 100. Further, the longitudinal inner end 1435 and outer end 1436 of the joint cover 1430 are inclined in harmony with such inclination of the stepped surfaces. Thus, when no load acts on the wiper blade 100, the central spoiler portion 1120, the joint cover 1430 and the end spoiler portion 1320 can become open with some gap therebetween. On the contrary, when a downward load acts on the wiper blade 100 (e.g., when the wiper arm applies a force to the wiper blade toward the windshield), the central spoiler portion 1120, the joint cover 1430 and the end spoiler portion 1320 are brought into close abutment with one another in the longitudinal direction of the lever assembly 1000. That is, with the stepped surfaces 1124, 1423 inclined as described above and the shape of the joint cover 1430 corresponding thereto, the end lever 1300L, 1300R cannot pivot upwardly relative to the central lever 1100. Accordingly, when a downward load acts on the wiper blade 100, the lever assembly 1000 can bring the wiper rubber 110 into strong contact with the windshield along its entire length.
Descriptions are made as to an example assembly of the wiper blade 100 according to the first embodiment with reference to FIG. 25.
In an assembly wherein the central lever 1100 and the end levers 1300L, 1300R are hinge-jointed to each other, the joint cover 1430 is snap-engaged to the joint portion 1125 of the central lever. By pressing the joint cover 1430 against the joint portion 1125, the claws 1433 of the joint cover 1430 snap-engage the indentations 1128 of the joint portion 1125 and the positioning protrusions 1434 of the joint cover 1430 are inserted to the slit 1127 of the joint portion 1125, thus coupling the joint cover 1430 to the joint portion 1125 and thereby completing the lever assembly 1000.
By fitting the clamps 1325, 1311 of the end levers 1300L, 1300R to the second groove 114 of the wiper rubber 110, the lever assembly 1000 and the wiper rubber assembly 110, 120 are coupled to each other. First, the both ends of the clamp 1325 of the end lever 1300L with the clamp insert 1330 fitted thereto are positioned in the second groove 114 of the wiper rubber 110 and then the wiper rubber assembly 110, 120 is slid along the lever assembly 1000. Subsequently, the both ends of the clamps 1311 of the end lever 1300L are positioned in the second groove 114 and then the wiper rubber assembly 110, 120 is slid along the lever assembly 1000. Thereafter, the clamps 1311, 1325 of the end lever 1300R is positioned in the second groove 114 one after the other, and the wiper rubber assembly 110, 120 is slid along the lever assembly 1000. If the both ends of the clamp 1325 of the end lever 1300L are fitted to the insertion holes 117 and the sandwiching portions 1332 of the clamp insert 1330 are placed in the recess 116, then the wiper rubber assembly 110, 120 is fixed to the lever assembly 1000.
Referring again to FIGS. 1 to 5 showing the assembled wiper blade 100, the lever assembly 1000 holds and supports the wiper rubber assembly 110, 120 at four positions (i.e., at four pressure points) via the clamps 1325, 1311 of the end lever 1300L, 1300R. Further, the central lever 1100 and the end levers 1300L, 1300R are straight arranged along the length of the wiper rubber 110 and are at the same height on the wiper rubber 110. Further, in the assembled wiper blade 100, the inclined surfaces 1121F, 1121R of the central spoiler portion 1120, the inclined surfaces 1431F, 1431R of the joint cover 1430 and the inclined surfaces 1321F, 1321R of the end spoiler portion 1320 are straight adjoined one after another, thereby defining the spoiler 130L, 130R with the cross-sectional profile varying in the longitudinal direction.
FIGS. 30 to 43 show a wiper blade according to a second embodiment, generally denoted by 200, and elements or components constituting the wiper blade 200. The wiper blade 200 according to this embodiment is configured to hold the wiper rubber at six pressure points. The wiper blade 200 has a longer length when compared to the wiper blade 100 according to the first embodiment and its lever assembly has a configuration for the longer length. In FIGS. 30 to 43, the same elements or components as those of the wiper blade 100 of the first embodiment are denoted by the same reference numerals.
Referring to FIGS. 30 to 43, the wiper blade 200 according to the second embodiment has a wiper rubber 210, which contacts the windshield surface, and a lever assembly 2000 holding and supporting the wiper rubber 210. Further, the wiper blade 200 includes a pair of spoilers 230L, 230R that produce a reaction force preventing the lift caused by wind or air stream. The left spoiler 230L and the right spoiler 230R are symmetrical relative to a longitudinal center of the wiper rubber 210. The spoilers 230L, 230R are integrated in the lever assembly 2000 and extend in the longitudinal direction of the wiper rubber 210.
The wiper rubber 210 has the same configuration as that of the wiper rubber 110 of the first embodiment and has a length longer than the wiper rubber 110. Spring rails 220 are inserted to the first grooves 113 to thus impart rigidity to the wiper rubber 210 (see FIG. 43). Hereinafter, the wiper rubber 210 with the spring rails 220 fitted thereto is referred to as a wiper rubber assembly 210, 220.
The lever assembly 2000 connects the wiper rubber assembly 210, 220 to the wiper arm and supports the wiper rubber assembly 210, 220 with respect to the wiper arm. The wiper blade 200 is coupled to the wiper arm in such a manner that the lever assembly 2000 is releasably joined to the distal end of the wiper arm. In this embodiment, the lever assembly 2000 includes a central lever 1100 centrally located in the wiper rubber assembly 210, 220, a pair of intermediate levers 2200L, 2200R joined to the central lever 1100 respectively and a pair of end levers 2300L, 2300R joined to the intermediate lever 2200L, 2200R respectively. The levers 1100, 2200L, 2200R, 2300L, 2300R constituting the lever assembly 2000 are straight arranged along a longitudinal direction of the wiper rubber 210. The adjacent levers are hinge-jointed to each other. The levers 1100, 2200L, 2200R, 2300L, 2300R have an elongated hollow shape and may be made by pressing a metallic sheet or injection molding a plastic material.
Similar to the first embodiment, a cross-sectional profile of the spoiler 230L, 230R for producing the reaction force includes a triangle having concave legs. The cross-sectional profile of the spoiler 230L, 230R decreases gradually in a height dimension toward a distal end of the wiper blade 200. Each spoiler 230L, 230R comprises spoiler sections located in the respective levers 1100, 2200L, 2200R, 2300L, 2300R. The spoiler sections of the respective levers are straight adjoined one after another, i.e. they are consecutively adjoined with the spoiler sections of adjacent levers adjoining each other, thereby defining the spoiler 230L, 230R. As described below regarding the spoiler 230L, 230R integrated in the lever assembly 2000, a spoiler section integrated in the central lever 1100 is referred to as a central spoiler 131L, 131R, and another spoiler section integrated in the intermediate lever 2200L, 2200R is referred to as an intermediate spoiler 232L, 232R, and yet another spoiler section integrated in the end lever 2300L, 2300R is referred to as an end spoiler 233L, 233R.
Each intermediate lever 2200L, 2200R is joined to the central lever 1100 and holds the wiper rubber assembly 210, 220. Descriptions are made as to the intermediate lever 2200L with reference to FIGS. 35 to 38. The intermediate lever 2200L and the intermediate lever 2200R are symmetrical in the longitudinal direction of the lever assembly 2000. The intermediate lever 2200L, 2200R includes an intermediate arm 2210 to be situated in the arm receiving portion 1126 of the central spoiler portion 1120 and an intermediate spoiler portion 2220 oppositely extending from the intermediate arm 2210. The intermediate arm 2210 has an inverted U-shaped cross-section. The intermediate spoiler portion 2220 has an inverted V-shaped cross-section. The intermediate arm 2210 extends from a longitudinal inner end portion 2223 of the intermediate spoiler portion 2220 toward the central lever 1100. A lower edge of the intermediate arm 2210 and a lower edge of the intermediate spoiler portion 2220 form an approximately straight line.
Each intermediate lever 2200L, 2200R has a clamp 2211 for fixing the wiper rubber assembly 210, 220. The clamp 2211 is formed at a distal end of the intermediate arm 2210. The clamp 2211 has the same shape as the clamp 1311 of the first embodiment. When the intermediate lever 2200L, 2200R and the wiper rubber assembly 210, 220 are coupled to each other, both ends of the clamp 2211 is inserted to the second groove 114 of the wiper rubber 210.
The intermediate spoiler 232L, 232R is integrally formed in the intermediate spoiler portion 2220. The intermediate spoiler portion 2220 has a pair of inclined surfaces 2221F, 2221R that are symmetrical in the width direction of the intermediate lever 2200L, 2200R. The inclined surfaces 2221F, 2221R are located in the lateral surfaces of the intermediate spoiler portion 2220. The inclined surfaces 2221F, 2221R extend in the longitudinal direction of the wiper rubber 210 in the intermediate lever 2200L, 2200R and form the lateral surfaces of the intermediate spoiler portion 2220. Accordingly, the intermediate spoiler 232L, 232R is integrated in the intermediate lever 2200L, 2200R through the intermediate spoiler portion 2220 having the inclined surfaces 2221F, 2221R. An apex portion 2222 interconnects the inclined surfaces 2221F, 2221R at their upper edges. The inclined surfaces 2221F, 2221R are concave in the width direction of the intermediate lever 2200L 2200R. Further, a height dimension of the inclined surfaces 2221F, 2221R decrease gradually toward the longitudinal outer end of the intermediate lever 2200L, 2200R. The inclined surfaces 2221F, 2221R of the intermediate spoiler portion 2220 may be curved with the same curvature as that of the inclined surfaces 1121F, 1121R of the central spoiler portion 1120, or curved with a curvature varying therefrom. In this embodiment, the inclined surfaces 2221F, 2221R of the intermediate spoiler portion 2220 is curved with the same curvature as that of the inclined surfaces 1121F, 1121R at the stepped surface 1124 of the central spoiler portion 1120. The curvature of the inclined surface 2221F, 2221R is constant in the longitudinal direction of the intermediate spoiler portion 2220.
The central lever 1100 and the intermediate lever 2200L, 2200R are joined to each other via a hinge-joint portion 2400L, 2400R penetrating through the joint portion 1125 and the intermediate arm 2210. When the central lever 1100 and the intermediate lever 2200L, 2200R are joined to each other, the intermediate arm 2210 of the intermediate lever is situated in the arm receiving portion 1126 of the central spoiler portion 1120 and is thus hidden within the central spoiler portion 1120 when viewed from outside. In other words, a portion (e.g., the intermediate arm 2210) of one of the adjacent levers (e.g., the intermediate lever 2200L, 2200R) is inside the spoiler portion of the other of the adjacent levers (e.g., the central lever 1100), which is further inward than said one of the adjacent levers.
The hinge-joint portion 2400L, 2400R between the central lever 1100 and the intermediate lever 2200L, 2200R has the same configuration as the hinge-joint portion 1400L, 1400R of the first embodiment. Referring to FIG. 43, the hinge-joint portion 2400L, 2400R includes the rivet 1410 serving as a hinge shaft and the hinge insert 1420 coupled to the rivet 1410. Through apertures 2212 a for hinge-joint are formed in a portion of the intermediate arm 2210, which corresponds to the joint portion 1125 of the central lever 1100, in a width direction thereof. The hinge insert 1420 is nested on the intermediate arm 2210 such that the through apertures 1421 and the through apertures 2212 a are in alignment with each other. Thereafter, the joint portion 1125 of the central lever 1100 is nested on the hinge insert 1420 such that the through apertures 1126 are aligned with the through apertures 1421. The rivet 1410 is pierced through the through apertures 1126, 1421, 2212 a and then riveted thereto, thus forming the hinge-joint portions 2400L, 2400R.
The intermediate lever 2200L, 2200R includes a joint portion 2227, which extends from a longitudinal outer end portion 2225 of the intermediate spoiler portion 2220 toward the distal end of the wiper blade 200 and has an inverted U-shaped cross section. The joint portion 2227 has width and height dimensions less than the longitudinal outer end portion 2225 of the intermediate spoiler portion 2220. The intermediate spoiler portion 2220 has an arm receiving portion 2226 receiving a portion of the end lever 2300L, 2300R. The arm receiving portion 2226 is defined by a space between the inclined surfaces 2221F, 2221R and an interior space of the joint portion 2227. The joint portion 2227 participates in hinge-joint to the end lever 2300L, 2300R. The joint portion 2227 has a slit 2228 at its top and indentations 2229 at its lower edge. The slit 2228 and the indentations 2229 participate in engagement with the joint cover 1430′.
The end levers 2300L, 2300R are joined to the intermediate levers 2200L, 2200R respectively and hold the wiper rubber assembly 210, 220. The end lever 2300L, 2300R according to this embodiment has the same configuration as the end lever 1300L, 1300R of the first embodiment. Further, the end lever 2300L, 2300R has a length shorter than the end lever 1300L, 1300R of the first embodiment.
Descriptions are made as to the end lever 2300L with reference to FIGS. 39 to 42. The end lever 2300L and the end lever 2300R are symmetrical in the longitudinal direction of the lever assembly 2000. The end lever 2300L, 2300R includes an end arm 2310 to be situated in the arm receiving portion 2226 of the intermediate spoiler portion 2220 and an end spoiler portion 2320 oppositely extending from the end arm 2310. The end arm 2310 has an inverted U-shaped cross-section. The end spoiler portion 2320 has an inverted V-shaped cross-section. The end arm 2310 extends from a longitudinal inner end portion 2323 of the end spoiler portion 2320 toward the intermediate lever 2200L, 2200R. A lower edge of the end arm 2310 and a lower edge of the end spoiler portion 2320 form an approximately straight line. The inner end portion 2323 has width and height dimensions less than the longitudinally inner stepped surface 2324 of the end spoiler portion 2320. Two clamps 2325, 2311 of each end lever 2300L, 2300R fix the wiper rubber assembly 210, 220. The clamp 2325 is formed at a lower edge of the end spoiler portion 2320 in the vicinity of its longitudinal outer end. The clamp 2311 is formed at a distal end of the end arm 2310. The clamps 2311, 2325 have the same shape as the clamps 1311, 1325 of the end lever 1300L, 1300R of the first embodiment. As shown in FIG. 39, the clamp insert 1330 of the first embodiment is fitted to the clamp 2325 to fix the wiper rubber 210 to the clamp 2325.
The end spoiler portion 2320 has a pair of inclined surfaces 2321F, 2321R that are symmetrical in the width direction of the end lever 2300L, 2300R. The inclined surfaces 2321F, 2321R are located in the lateral surfaces of the end spoiler portions 2320. The inclined surfaces 2321F, 2321R extend in the longitudinal direction of the wiper rubber 210 in the end lever 2300L, 2300R and form the lateral surfaces of the end spoiler portion 2320. Accordingly, the end spoiler 233L, 233R is integrated in the end lever 2300L, 2300R through the end spoiler portion 2320 having the inclined surfaces 2321F, 2321R. An apex portion 2322 interconnects the inclined surfaces 2321F, 2321R at their upper edges. The inclined surfaces 2321F, 2321R are concave in the width direction of the end lever 2300L, 2300R. Further, a height dimension of the inclined surfaces 2321F, 2321R decreases gradually toward the longitudinal outer end of the end lever 2300L, 2300R. Further, lower edges of the inclined surfaces 2321F, 2321R approach each other at the distal end of the end lever 2300L, 2300R, thereby forming a round distal end of the end lever 2300L, 2300R along with the apex portion 2322. The inclined surfaces 2321F, 2321R may be curved with the same curvature as that of the inclined surfaces 2221F, 2221R of the intermediate spoiler portion 2220, or curved with a curvature varying therefrom. In this embodiment, the inclined surfaces 2321F, 2321R of the end spoiler portion 2320 is curved with a curvature greater than that of the inclined surfaces 2221F, 2221R of the intermediate spoiler portion.
The intermediate lever 2200L, 2200R and the end lever 2300L, 2300R are joined to each other via a hinge-joint portion 2400′L, 2400′R penetrating through the joint portion 2227 of the intermediate lever and the end arm 2310 of the end lever. When the intermediate lever 2200L, 2200R and the end lever 2300L, 2300R are joined to each other, the end arm 2310 is situated in the arm receiving portion 2226 of the intermediate spoiler portion 2220 and is thus hidden within the intermediate spoiler portion 2220 when viewed from outside.
Referring to FIG. 43, when the central lever 1100 and the intermediate lever 2200L, 2200R are joined to each other, the joint portion 1125 of the central lever 1100 is nested on the intermediate arm 2210 of the intermediate lever 2200L, 2200R with the hinge insert 1420 intervened therebetween and the hinge-joint portion 2400L, 2400R is formed therebetween. Further, when the intermediate lever 2200L, 2200R and the end lever 2300L, 2300R are joined to each other, the joint portion 2227 of the intermediate lever 2200L, 2200R is nested on the end arm 2310 of the end lever 2300L, 2300R with the hinge insert 1420 intervened therebetween and the hinge-joint portion 2400′L, 2400′R is formed therebetween. The lever assembly 2000 includes the joint covers 1430, 1430′ disposed between the levers to cover the hinge-joint portions 2400L, 2400R, 2400′L, 2400′R. The joint cover 1430 snap-engages the joint portion 1125 of the central lever between the central lever 1100 and the intermediate lever 2200L, 2200R. The joint cover 1430′ snap-engages the joint portion 2227 of the intermediate lever between the intermediate lever 2200L, 2200R and the end lever 2300L, 2300R. The joint cover 1430′ has a configuration similar to the configuration of the joint cover 1430. A cross-sectional profile of the joint cover 1430′ decreases in height dimension toward the end lever 2300L, 2300R. Further, a curvature of the inclined surface 1431F, 1431R of the joint cover 1430′ increases toward the end lever 2300L, 2300R.
The stepped surface 1124 of the central spoiler portion 1120 and a stepped surface 2224 b of the intermediate spoiler portion 2220 are inclined at an acute angle inwardly of the wiper blade 200, while a stepped surface 2224 a of the intermediate spoiler portion 2220 and a stepped surface 2324 of the end spoiler portion 2320 are inclined at an acute angle toward the distal end of the wiper rubber 210. Further, the longitudinal both ends of the joint covers 1430, 1430′ are inclined in harmony with such inclination of the stepped surfaces. Thus, when no load acts on the wiper blade 200, the central spoiler portion 1120, the joint cover 1430, the intermediate spoiler portion 2220, the joint cover 1430′ and the end spoiler portion 2320 can become open with a slight gap therebetween. With the stepped surfaces 1124, 2224 a, 2224 b, 2324 inclined as described above and the shapes of the joint covers 1430, 1430′ corresponding thereto, the intermediate lever 2200L, 2200R and the end lever 2300L, 2300R cannot pivot upwardly relative to the central lever 1100. Accordingly, when a downward load acts on the wiper blade 200, the central spoiler portion 1120, the joint cover 1430, the intermediate spoiler portion 2220, the joint cover 1430′ and the end spoiler portion 2320 is brought into close abutment with one another in the longitudinal direction, thereby bringing the wiper rubber 210 into strong contact with the windshield.
Descriptions are made as to an example assembly of the wiper blade 200 according to the second embodiment with reference to FIG. 43.
In an assembly wherein the central lever 1100, the intermediate lever 2200L, 2200R and the end lever 2300L, 2300R are hinge-jointed to one another, the joint covers 1430, 1430′ are snap-engaged to the hinge-joint portions 2400L, 2400R, 2400′L, 2400′R respectively by pressing the joint cover 1430 and the joint cover 1430′ against the joint portion 1125 of the central lever and the joint portion 2227 of the intermediate lever respectively. The claws 1433 of the joint covers 1430, 1430′ snap-engage the indentations 1128, 2229 of the joint portions 1125, 2227 and the positioning protrusions 1434 of the joint covers 1430, 1430′ are inserted to the slits 1127, 2228 of the joint portions 1125, 2227, thus coupling the joint covers 1430, 1430′ to the hinge-joint portions 2400L, 2400R, 2400′L, 2400′R.
By fitting the clamps 2325, 2311 of the end levers 2300L, 2300R and the clamps 2211 of the intermediate levers 2200L, 2200R to the second groove 114 of the wiper rubber 210, the lever assembly 2000 and the wiper rubber assembly 210, 220 are coupled to each other. For example, the wiper rubber assembly 210, 220 is slid along the lever assembly 2000 while sequentially inserting the following: the clamp 2325 of the end lever 2300L with the clamp insert 1330 fitted thereto, the clamp 2311 of the end lever 2300L, the clamp 2211 of the intermediate lever 2200L, the clamp 2211 of the intermediate lever 2200R, the clamp 2311 of the end lever 2300R and the clamp 2325 of the end lever 2300R with the clamp insert 1330 fitted thereto. If the both ends of the clamp 2325 of the end lever 2300L is fitted to the insertion holes 117 and the sandwiching portions 1332 of the clamp insert 1330 are placed in the recess 116, the wiper rubber assembly 210, 220 is fixed to the lever assembly 2000.
Referring again to FIGS. 30 to 34 showing the assembled wiper blade 200, the lever assembly 2000 holds the wiper rubber assembly 210, 220 at six pressure points via the clamps 2325, 2311 of the end levers 2300L, 2300R and the clamps 2211 of the intermediate levers 2200L, 2200R. Further, the central lever 1100, the intermediate levers 2200L, 2200R and the end levers 2300L, 2300R are straight arranged along the length of the wiper rubber 210 and are at the same height on the wiper rubber 210. Further, in the assembled wiper blade 200, the inclined surfaces 1121F, 1121R of the central spoiler portion 1120, the inclined surfaces 1431F, 1431R of the joint cover 1430, the inclined surfaces 2221F, 2221R of the intermediate spoiler portion 2220, the inclined surfaces 1431F, 1431R of the joint cover 1430′ and the inclined surfaces 2321F, 2321R of the end spoiler portion 2320 are straight adjoined one after another, thereby defining the spoiler 230L, 230R having the cross-sectional profile with its height dimension decreasing toward the distal end of the wiper blade 200.
FIGS. 44 to 56 show a wiper blade according to a third embodiment, generally denoted by 300, and elements or components constituting the wiper blade 300. The wiper blade 300 according to this embodiment is configured to hold the wiper rubber at eight pressure points. The wiper blade 300 according to the third embodiment has a longer length when compared to the wiper blades 100, 200 according to the first and second embodiments and its lever assembly has a configuration for such a longer length. In FIGS. 44 to 56, the same elements or components as those of the wiper blades 100, 200 of the first and second embodiments are denoted by the same reference numerals.
Referring to FIGS. 44 to 46, the wiper blade 300 according to the third embodiment has a wiper rubber 310, which contacts the windshield surface, and a lever assembly 3000 holding and supporting the wiper rubber 310. Further, the wiper blade 300 includes a pair of spoilers 330L, 330R, which produce a reaction force preventing the lift caused by wind or air stream and are symmetrical relative to a longitudinal center of the wiper rubber 310. The spoilers 330L, 330R are integrated in the lever assembly 3000 and extend in the longitudinal direction of the wiper rubber 310.
The wiper rubber 310 has the same configuration as those of the wiper rubbers 110, 210 of the first and second embodiments and has a length longer than the wiper rubbers 110, 210. Spring rails 320 (see FIG. 56) are inserted to the first grooves 113 of the wiper rubber 310 to thus impart rigidity to the wiper rubber 310. The spring rail 320 has the same configuration as and a length longer than the spring rail 120 of the first embodiment. Hereinafter, the wiper rubber 310 with the spring rails 320 fitted thereto is referred to as a wiper rubber assembly 310, 320.
In this embodiment, the lever assembly 3000, which connects the wiper rubber assembly 310, 320 to the wiper arm, includes a central lever 3100, a pair of intermediate levers 3200L, 3200R joined to the central lever 3100 respectively and a pair of the end levers 2300L, 2300R joined to the intermediate lever 2200L, 2200R respectively. The levers 3100, 3200L, 3200R, 2300L, 2300R constituting the lever assembly 3000 are straight arranged along a longitudinal direction of the wiper rubber 310. The adjacent levers are hinge-jointed to each other. The levers 3100, 3200L, 3200R, 2300L, 2300R have an elongated hollow shape and may be made by pressing a metallic sheet or injection molding a plastic material
The spoiler 330L, 330R is integrated in an upper surface of the lever assembly 3000 (an upper or lateral surface of each lever constituting the lever assembly) along a longitudinal direction thereof (along a longitudinal direction of the wiper rubber 310). Similar to the first and second embodiments, a cross-sectional profile of the spoiler 330L, 330R for producing the reaction force includes a triangle having concave legs. The cross-sectional profile of the spoiler 330L, 330R decreases in a height dimension toward a distal end of the wiper blade 300. Each spoiler 330L, 330R comprises spoiler sections located in respective levers 3100, 3200L, 3200R, 3300L, 3300R. The spoiler sections of the respective levers are straight adjoined one after another, i.e. they are consecutively adjoined with the spoiler sections of adjacent levers adjoining each other, thereby defining the spoiler 330L, 330R. A spoiler portion of each lever forms the spoiler section. Specifically, a portion or an entirety of a lateral surface of each spoiler portion forms the spoiler section. In the below descriptions, regarding the spoiler 330L, 330R formed in the lever assembly 3000, a spoiler section integrated in the central lever 3100 is referred to as a central spoiler 331L, 331R, and another spoiler section integrated in the intermediate lever 3200L, 3200R is referred to as an intermediate spoiler 332L, 332R, and yet another spoiler section integrated in the end lever 2300L, 2300R is referred to as an end spoiler 233L, 233R.
The central lever 3100 is located in the middle of the wiper rubber assembly 310, 320. The central lever 3100 is releasably coupled to the distal end of the wiper arm. The central lever 3100 has the same configuration as the central lever 1100 of the first embodiment. The central spoiler 331L, 331R integrally formed in the central lever 3100 is longer than the central spoiler 131L, 131R of the central lever 1100.
Referring to FIGS. 47 and 48, the central lever 3100 includes a pair of central spoiler portions 3120, which extend from the centrally-located bracket portion 1110 in opposite directions in the longitudinal direction of the wiper rubber 310 and define the central spoiler 331L, 331R. The central spoiler portion 3120 has an inverted V-shaped cross-section. A lower edge of the central lever 3100 is straight or upwardly curved with a slight curvature.
The central spoiler portion 3120 includes a pair of inclined surfaces 3121F, 3121R that are symmetrical in the width direction of the central lever 3100. The inclined surfaces 3121F, 3121R are located in the lateral surfaces of the central spoiler portion 3120. The inclined surfaces 3121F, 3121R extend in the longitudinal direction of the wiper rubber 310 in the central lever 3100 and form the lateral surfaces of the central spoiler portion 3120. Accordingly, the central spoiler 331L, 331R is integrated in the central lever 3100 through the central spoiler portion 3120 having the inclined surfaces 3121F, 3121R. An apex portion 3122 interconnects the inclined surfaces 3121F, 3121R at their upper edges.
The inclined surfaces 3121F, 3121R includes a concave surface. A width of the apex portion 3122 becomes sharply narrow from the bracket portion 1110 and then is constant. The inclined surfaces 3121F, 3121R are concave in harmony with such width variance of the apex portion 3122. Thus, the cross-sectional profile of the central spoiler 331L, 331R, which the inclined surfaces 3121F, 3121R of the central spoiler portion 3120 define, is generally a triangle having both concave legs. The central spoiler portion 3120 has an arm receiving portion 3126 that receives a portion of the intermediate lever 3200L, 3200R. The arm receiving portion 3126 is defined by a space between the inclined surfaces 3121F, 3121R and an interior space of the joint portion 1125.
Each intermediate lever 3200L, 3200R is joined to the central lever 3100 and holds the wiper rubber assembly 310, 320. Descriptions are made as to the intermediate lever 3200L with reference to FIGS. 49 to 51. The intermediate lever 3200L and the intermediate lever 3200R are symmetrical in the longitudinal direction of the lever assembly 3000. The intermediate lever 3200L, 3200R includes an intermediate arm 3210 to be situated in the arm receiving portion 3126 of the central lever 3100 and an intermediate spoiler portion 3220 oppositely extending from the intermediate arm 3210. The intermediate arm 3210 has an inverted U-shaped cross-section. The intermediate spoiler portion 3220 has an inverted V-shaped cross-section. The intermediate spoiler portion 3220 has a stepped surface 3224 a at a longitudinal inner end portion 3223. The longitudinal inner end portion 3223 has width and height dimension less than the stepped surface 3224 a. The intermediate arm 3210 extends from the longitudinal inner end portion 3223 toward the central lever 3100. A lower edge of the intermediate arm 3210 and a lower edge of the intermediate spoiler portion 3220 form an approximately straight line.
The intermediate spoiler portion 3220 has a pair of inclined surfaces 3221F, 3221R, which are symmetrical in the width direction of the intermediate lever 3200L, 3200R and are located in the lateral surfaces of the intermediate spoiler portion 3220. The inclined surfaces 3221F, 3221R extend in the longitudinal direction of the wiper rubber 310 in the intermediate lever 3200L, 3200R and form the lateral surfaces of the intermediate spoiler portion 3220. Accordingly, the intermediate spoiler 332L, 332R is integrated in the intermediate lever 3200L, 3200R through the intermediate spoiler portion 3220 having the inclined surfaces 3221F, 3221R. An apex portion 3222 interconnects the inclined surfaces 3221F, 3221R at their upper edges. The inclined surfaces 3221F, 3221R are concave in the width direction of the intermediate lever 3200L 3200R. The inclined surfaces 3221F, 3221R is curved with the same curvature as that of the inclined surfaces 3121F, 3121R at the stepped surface 1124 of the central spoiler portion 3120. Further, a height dimension of the inclined surfaces 3221F, 3221R decreases gradually toward a longitudinal outer end of the intermediate lever 3200L, 3200R.
The central lever 3100 and the intermediate lever 3200L, 3200R are joined to each other via a hinge-joint portion 3400L, 3400R penetrating through the joint portion 1125 of the central lever and the intermediate arm 3210 of the intermediate lever. When the central lever 3100 and the intermediate lever 3200L, 3200R are joined to each other, the intermediate arm 3210 is situated in the arm receiving portion 3126 of the central spoiler portion 3120 and is thus hidden within the central spoiler portion 3120 when viewed from outside. The hinge-joint portion 3400L, 3400R has the same configuration as the hinge-joint portion 1400L, 1400R of the first embodiment. Through apertures 3212 a for hinge-joint are formed in a portion of the intermediate arm 3210, which corresponds to the joint portion 1125 of the central lever 3100, in a width direction thereof. The hinge insert 1420 is nested on the intermediate arm 3210 such that the through apertures 1421 and the through apertures 3212 a in alignment with each other. Thereafter, the joint portion 1125 of the central lever 3100 is nested on the hinge insert 1420 such that the through apertures 1126 are aligned with the through apertures 1421. The rivet 1410 is pierced through the through apertures 1126, 1421, 3212 a and then riveted thereto, thus forming the hinge-joint portions 3400L, 3400R.
The intermediate lever 3200L, 3200R includes a joint portion 3227, which extends from a longitudinal outer end portion 3225 of the intermediate spoiler portion 3220 toward the distal end of the wiper blade 300 and has an inverted U-shaped cross section. The joint portion 3227 has width and height dimensions less than the longitudinal outer end portion 3225 of the intermediate spoiler portion 3220. The intermediate spoiler portion 3220 has an arm receiving portion 3226 receiving the end arm 2310 of the end lever. The arm receiving portion 3226 is defined by a space between the inclined surfaces 3221F, 3221R and an interior space of the joint portion 3227. The joint portion 3227 participates in hinge-joint to the end lever 2300L, 2300R. The joint portion 3227 has a slit 3228 at its top and indentations 3229 at its lower edge. The slit 3228 and the indentations 3229 participate in engagement with the joint cover 1430′.
In this embodiment, each intermediate lever 3200L, 3200R holds the wiper rubber assembly 310, 320 at two pressure points. For connection to the wiper rubber assembly 310, 320, each intermediate lever 3200L, 3200R has a yoke lever 3230 hinge-jointed to a distal end of the intermediate arm 3210. Referring to FIGS. 52 and 53, the yoke lever 3230 has an inverted U-shaped cross-section and includes yoke arms 3231 extending from a central through aperture 3232 in opposite directions. Clamps 3233 for holding the wiper rubber assembly 310, 320 are formed at both ends of the yoke arms 3231 of the yoke lever 3233 respectively. The clamps 3233 have the same shape as the clamp 1311 of the first embodiment.
A joint portion 3211 for hinge connection to the yoke lever 3230 is formed at the distal end of the intermediate arm 3210. Through apertures 3213 are formed in both lateral walls of the joint portion 3211. A distal end surface 3214 of the intermediate arm 3210 is inclined at an acute angle toward the center of the wiper rubber assembly 310, 320. A hinge insert 3240 shown in FIGS. 54 and 55 connects the yoke lever 3230 to the intermediate arm 3210. The hinge insert 3240 has a body 3241 of an inverted U-shaped cross-section such that a portion of the yoke lever 3230 with the through apertures 3232 formed therein is fitted to the body 3241. Through apertures 3242 are formed in both lateral walls of the body 3241 respectively. A stepped portion 3243 is formed in the vicinity of a longitudinal inner end of the body 3241. The stepped portion 3243 is formed with a stopper surface 3344 that abuts the distal end surface 3214 of the intermediate arm 3210 to thus restrict rotation of the hinge insert 3340 or the yoke lever 3230. The intermediate arm 3210 and the yoke lever 3230 are hinge-jointed to each other in the following manner: the hinge insert 3240 is nested on a midway portion of the yoke lever 3230; the hinge insert 3240 is inserted to the joint portion 3211 formed at the distal end of the intermediate arm 3210; and a rivet or pin is fitted to the through apertures 3232 of the yoke lever 3230, the through apertures 3242 of the hinge insert 3240 and the through apertures 3213 of the intermediate arm 3210 and is then riveted thereto.
Each end lever 2300L, 2300R is hinge-jointed to the intermediate lever 3200L, 3200R and holds the wiper rubber assembly 310, 320. When the intermediate lever 3200L, 3200R and the end lever 2300L, 2300R are hinge-joined to each other, the end arm 2310 is situated in the arm receiving portion 3226 of the intermediate spoiler portion 3220 and is thus hidden within the intermediate spoiler portion 3220 when viewed from outside. The intermediate lever 3200L, 3200R and the end lever 2300L, 2300R are joined to each other through a hinge-joint portion 3400′L, 3400′R penetrating through both the joint portion 3227 and the end arm 2310. Through apertures 3212 b for hinge-joint are formed in the joint portion 3227 of the intermediate lever 3200L, 3200R in a width direction. The hinge insert 1420 is nested on the end arm 2310 of the end lever such that the through apertures 1421 and the through apertures 2312 are aligned with each other. Thereafter, the joint portion 3227 of the intermediate lever 3200L, 3200R is nested on the hinge insert 1420 such that the through apertures 3212 b are aligned with the through apertures 1421. The rivet 1410 is pierced through the through apertures 3212 b, 1421, 2312 and is riveted thereto, thereby forming the hinge-joint portion 3400′L, 3400′R.
Referring to FIG. 56, the lever assembly 3000 includes the joint cover 1430, which is disposed between the central lever 3100 and the intermediate lever 3200L, 3200R to cover the hinge-joint portion 3400L, 3400R, and the joint cover 1430′, which is disposed between the intermediate lever 3200L, 3200R and the end lever 2300L, 2300R to cover the hinge-joint portion 3400′L, 3400′R. The joint cover 1430 snap-engages the joint portion 1125 of the central lever. The joint cover 1430′ snap-engages the joint portion 3227 of the intermediate lever.
The wiper rubber assembly 310, 320 and the lever assembly 3000 are coupled to each other by fitting the clamps 3233 of the yoke lever 3230 and the clamps 2311, 2325 of the end levers 2300L, 2300R to the second groove 114 of the wiper rubber 310. If the both ends of the clamp 2325 of the end lever 2300L are inserted to the insertion holes 117 and the sandwiching portion 1332 of the clamp insert 1330 is placed in the recesses 116, then the wiper rubber assembly 310, 320 are fixed to the lever assembly 3000.
In the assembled wiper blade 300, when no load acts on the wiper blade 300, the central spoiler portion 3120, the joint cover 1430, the intermediate spoiler portion 3220, the joint cover 1430′ and the end spoiler portion 2320 can become open with a slight gap therebetween. With the inclined stepped surfaces 1124, 3224 a, 3224 b, 2324 and the shapes of the joint covers 1430, 1430′ corresponding thereto, the intermediate lever 3200L, 3200R and the end lever 2300L, 2300R cannot pivot upwardly relative to the central lever 3100. Accordingly, when the wiper arm applies a force to the wiper blade 200 toward the windshield, the central spoiler portion 3120, the joint cover 1430, the intermediate spoiler portion 3220, the joint cover 1430′ and the end spoiler portion 2320 are brought into close abutment with one another in the longitudinal direction, thereby bringing the wiper rubber 310 into strong contact with the windshield.
Referring again to FIGS. 44 to 46 showing the assembled wiper blade 300, the lever assembly 3000 holds the wiper rubber assembly 310, 320 at eight pressure points via the clamps 2325, 2311 of the end levers 2300L, 2300R and the clamps 3233 of the yoke levers 3230. Further, the central lever 3100, the intermediate levers 3200L, 3200R and the end levers 2300L, 2300R are straight arranged along the length of the wiper rubber 310 and are at the approximately same height on the wiper rubber 310. Further, in the assembled wiper blade 300, the inclined surfaces 3121F, 3121R of the central spoiler portion 3120, the inclined surfaces 1431 f, 1431R of the joint cover 1430, the inclined surfaces 3221F, 3221R of the intermediate spoiler portion 3220, the inclined surfaces 1431F, 1431R of the joint cover 1430′ and the inclined surfaces 2321F, 2321R of the end spoiler portion 2320 are straight adjoined one after another, thereby defining the spoiler 330L, 330R having the cross-sectional profile with its height dimension decreasing gradually toward the distal end of the wiper blade 300.
In another embodiment similar to this embodiment, the wiper rubber assembly 310, 320 can be held at eight pressure points without the yoke lever 3230. In such an example, the lever assembly may be constructed such that two intermediate levers each having the clamp at its distal end of the intermediate arm (e.g., the intermediate lever 2200L, 2200R in the second embodiment) are juxtaposed. That is, the lever assembly of such an example may be configured such that the central lever, the first and second intermediate levers (e.g., intermediate levers similar to the intermediate lever 2200L, 2200R) and the end levers may be straight arranged and hinge-jointed one another.
FIGS. 57 to 60 show a wiper blade 400 according to a fourth embodiment and elements or components constituting the wiper blade 400. In a lever assembly 4000 of the wiper blade 400 according to this embodiment, opposing end surfaces of adjacent levers directly face to each other with little gap therebetween. To this end, the lever assembly 4000 includes a hinge-joint portion of a joint, which is hinge-jointed to the arm of one of the adjacent levers, and which is hidden in and coupled to the spoiler portion of the other of the adjacent levers. Via said joint, the arm of the one of the adjacent levers and the spoiler portion of the other of the adjacent levers, which is further inward than said one of the levers, are hinge-jointed to each other. Accordingly, the wiper blade 400 according to this embodiment does not include the joint cover 1430, 1430′ in the foregoing embodiments. In FIGS. 57 to 60, the same elements or components as those of the wiper blade 200 of the second embodiment are denoted by the same reference numerals.
Referring to FIGS. 57 and 58, the lever assembly 4000 of the wiper blade 400 holds the wiper rubber assembly 210, 220. The spoiler 430L, 430R is integrated in an upper surface of the lever assembly 4000 (an upper or lateral surface of each lever constituting the lever assembly) along a longitudinal direction of the wiper rubber 210. Each spoiler 430L, 430R produces a reaction force preventing the lift of the wiper blade 400. Similar to the second embodiment, a cross-sectional profile of the spoiler 430L, 430R for producing the reaction force includes a triangle having concave legs. The cross-sectional profile of the spoiler 430L, 430R decreases in a height dimension toward a distal end of the wiper blade 400. The lever assembly 4000 includes a central lever 4100 centrally located in the wiper rubber assembly 210, 220, a pair of intermediate levers 4200L, 4200R hinge-jointed to both longitudinal ends of the central lever 4100 respectively and a pair of the end levers 2300L, 2300R hinge-joined to both longitudinal ends of the intermediate levers 4200L, 4200R respectively. Each spoiler 430L, 430R comprises a central spoiler 431L, 431R, which is integrated in the central lever 4100 to become a section of the spoiler 430L, 430R, an intermediate spoiler 432L, 432R, which is integrated in the intermediate lever 4200L, 4200R to become another section of the spoiler 430L, 430R, and an end spoiler 233L, 233R, which is integrated in the end lever 2300L, 2300R to become yet another section of the spoiler 430L, 430R. Each lever has a spoiler portion forming the spoiler section.
Referring to FIGS. 58 and 59, the central lever 4100 includes a pair of central spoiler portions 4120, which extend from the bracket portion 1110 in opposite directions in the longitudinal direction of the wiper rubber 210 and define the central spoiler 431L, 431R respectively.
The central spoiler portion 4120 has a pair of inclined surfaces 4121F, 4121R that are symmetrical in the width direction of the central lever 4100. The inclined surfaces 4121F, 4121R are located in the lateral surfaces of the central spoiler portion 4120. The inclined surfaces 4121F, 4121R extend in the longitudinal direction of the wiper rubber 210 in the central lever 4100 and form the lateral surfaces of the central spoiler portion 4120. Accordingly, the central spoiler 431L, 431R is integrated in the central lever 4100 through the central spoiler portion 4120 having the inclined surfaces 4121F, 4121R. A longitudinal outer end surface 4123 of the central spoiler portion 4120 is inclined at an acute angle toward the distal end of the wiper rubber 210. The intermediate lever 4200L, 4200R includes the intermediate arm 2210 to be situated inside the central spoiler portion 4120 and an intermediate spoiler portion 4220 oppositely extending from the intermediate arm 2210. A lower edge of the intermediate arm 2210 and a lower edge of the central spoiler portion 4220 form an approximately straight line. The intermediate spoiler portion 4220 has a pair of inclined surfaces 4221F, 4221R, which are symmetrical in the width direction of the intermediate lever 4200L, 4200R. The inclined surfaces 4221F, 4221R extend in the longitudinal direction of the wiper rubber 210 in the intermediate lever 4200L, 4200R and form the lateral surfaces of the intermediate spoiler portion 4220. Accordingly, the intermediate spoiler 432L, 432R is integrated in the intermediate lever 4200L, 4200R through the intermediate spoiler portion 4220.
When the central lever 4100 and the intermediate lever 4200L, 4200R are joined to each other, the intermediate arm 2210 is situated inside the central spoiler portion 4120 and is thus hidden within the central spoiler portion 4120 when viewed from outside. The intermediate arm 2210 is hinge-jointed to the central spoiler portion 4120 via the joint 4400.
The joint 4400 has a generally triangular cross-section so as to fit inside the central spoiler portion 4120. Height and width dimensions of the joint 4400 are determined such that a longitudinal outer end portion 4410 of the joint is nested on a portion (e.g., the intermediate arm 2210) of one of the adjacent levers (e.g., the intermediate lever 4200L, 4200R) and a longitudinal inner end portion 4420 of the joint is fitted to the spoiler portion of the other of the adjacent levers (e.g., the central lever 4100), which is further inward than said one of the adjacent levers. The joint 4400 and the intermediate lever 4200L, 4200R are joined to each other by means of hinge-joint between inner surfaces of the joint 4400 and through apertures 2212 a formed in the intermediate arm 2210. When hinge-jointed, the longitudinal end portion 4410 of the joint 4400 is nested on the longitudinal inner end portion 2223 of the intermediate spoiler portion 4220.
The joint 4400 has an element snap-engaging the spoiler portion of the other of the adjacent levers (e.g., the central lever 4100). Specifically, the joint 4400 has snap protrusions 4430 at its longitudinal inner lower edge. A longitudinal outer end surface of the snap protrusion 4430 is inclined toward the distal end of the wiper rubber 210. Further, the joint 4400 has an element to be fitted to the end surface of the spoiler portion of the other of the adjacent levers (e.g., the central lever 4100). Specifically, the joint 4400 has two mating protrusions 4440 at either longitudinal outer end surface. The spoiler portion of the other of the adjacent levers (e.g. the central spoiler portion 4120 of the central lever 4100) has an element for snap-engagement with the joint 4400. A snap notch 4124, to which the snap protrusion 4430 is fitted, is formed at a lower edge of the central spoiler portion 4120. Further, the spoiler portion of the other of the adjacent levers (e.g. the central spoiler portion 4120 of the central lever 4100) has an element for engagement with the joint 4400. Mating notches 4125 mating the mating protrusions 4440 are formed in an outer end surface 4123 of the central spoiler portion 4120.
Referring to FIGS. 59 and 60, the intermediate arm 2210 with the joint 4400 hinge-jointed thereto is inserted to the inside of the central spoiler portion 4120 and the joint 4400 attached to the intermediate lever 4200L, 4200R is pushed into the central spoiler portion 4120. Then, the inner surface of the central spoiler portion 4120 is moved along or slid on the outer surface of the joint 4400 and then the outer end surface 4123 of the central spoiler portion 4120 abuts the longitudinal inner stepped surface 2224 a of the intermediate spoiler portion 4220 or faces the same with little gap therebetween. Further, the mating protrusions 4440 of the joint 4400 are fitted to the mating notches 4125 of the central spoiler portion 4120 and the snap protrusion 4430 of the joint 4400 snap-engages the snap notch 4124 of the central spoiler portion 4120, thereby coupling the joint 4400 to the central lever 4100.
The intermediate lever 4200L, 4200R and the end lever 2300L, 2300R are also joined to each other by means of the above-described joint. In this case, the joint between the intermediate lever 4200L, 4200R and the end lever 2300L, 2300R has width and height dimensions less than those of the above-described joint 4400. Further, a longitudinal outer end surface of the intermediate spoiler portion 4220 of the intermediate lever 4200L, 4200R is inclined toward the distal end of the wiper rubber 210. Mating notches are formed in the longitudinal outer end surface of the intermediate spoiler portion 4220 and a snap notch is formed at the lower edge of the intermediate spoiler portion 4220. The joint between the intermediate lever 4200L, 4200R and the end lever 2300L, 2300R is joined to the end arm 2310 of the end lever 2300L, 2300R by means of hinge-joint and has mating protrusions and snap protrusions corresponding to the mating notches and the snap notches respectively.
The above-described joint and the connection configuration using the same may be employed to a lever assembly configured to hold the wiper rubber at four pressure points (e.g., the lever assembly 1000 of the first embodiment) or a lever assembly configured to hold the wiper rubber at eight pressure points (e.g., the lever assembly 3000 of the third embodiment).
FIGS. 61 to 72 show a wiper blade according to a fifth embodiment, generally denoted by 500, and elements or components constituting the wiper blade 500. In a lever assembly 5000 of the wiper blade 500 according to this embodiment, opposing end surfaces of adjacent levers face to each other with little gap therebetween. Further, in this embodiment, a hinge-joint portion between adjacent levers of the lever assembly 5000 directly hinge-joints an arm, which is provided in one of the adjacent levers of the lever assembly 5000 to hold the wiper rubber, to an inside of a spoiler portion of the other of the adjacent levers. Such a hinge-joint configuration may be employed to any one of the wiper blades 100, 200, 300 of the foregoing embodiment. In FIGS. 61 to 72, the same elements or components as those of the wiper blade 200 of the second embodiment are denoted by the same reference numerals.
Referring to FIGS. 61 to 63, the wiper blade 500 according to the fifth embodiment has a lever assembly 5000 holding and supporting the wiper rubber assembly 210, 220. Further, the wiper blade 500 includes a pair of spoilers 530L, 530R. The left spoiler 530L and the right spoiler 530R are symmetrical relative to a longitudinal center of the wiper rubber 210. The spoilers 530L, 530R are integrated in the lever assembly 5000 and extend in the longitudinal direction of the wiper rubber 210.
The lever assembly 5000 connects the wiper rubber assembly 210, 220 to the wiper arm and supports the wiper rubber assembly 210, 220 with respect to the wiper arm. In this embodiment, the lever assembly 5000 includes a central lever 5100 centrally located in the wiper rubber assembly 210, 220, a pair of intermediate levers 5200L, 5200R joined to the central lever 5100 respectively and a pair of end levers 5300L, 5300R joined to the intermediate levers 5200L, 5200R respectively. The central lever, the intermediate lever and the end lever have an appearance similar to the central lever, the intermediate lever and the end lever of the foregoing embodiments respectively. The levers are straight arranged along the length of the wiper rubber 210 to thus constitute the lever assembly 5000. Adjacent levers are hinge-jointed to each other. The levers 5100, 5200L, 5200R, 5300L, 5300R have an elongated hollow shape and may be made by injection molding a plastic material.
The pair of the spoilers 530L, 530R are integrated in an upper surface of the lever assembly 5000 along the longitudinal direction of the wiper rubber 210. A portion of the upper surface of the lever assembly 5000 (a portion of an upper or lateral surface of each lever constituting the lever assembly) defines the spoiler 530L, 530R.
Each spoiler 530L, 530R reacts to wind or air stream impinging against the wiper blade 500 during running of a motor vehicle and produces a reaction force preventing the wiper blade 500 from being lifted. Such a reaction force is produced by interaction between wind or air stream and a cross-sectional profile of the spoiler 530L, 530R. The cross-sectional profile of the spoiler 530L, 530R may be constant along the length of the lever assembly 5000 or vary in width and height dimensions toward a distal end of the wiper blade 500. Further, the cross-sectional profile may be symmetrical or asymmetrical in a width direction of the wiper rubber assembly (in a direction perpendicular to the longitudinal direction of the wiper rubber). In this embodiment, similar to the foregoing embodiments, the cross-sectional profile of the spoiler 530L, 530R includes a triangle having somewhat concave legs.
Each spoiler 530L, 530R comprises spoiler sections located in the respective levers 5100, 5200L, 5200R, 5300L, 5300R of the lever assembly 5000. The spoiler sections of the respective levers are straight adjoined one after another, i.e. the spoiler sections of the respective levers are straight adjoined one after another with the spoiler sections of adjacent levers adjoining each other, thereby defining the spoiler 530L, 530R. A portion of the upper surface of the lever, specifically a portion or the entirety of the lateral surface of the spoiler portion forms the spoiler section. Further, a spoiler portion included in each lever forms each spoiler section. In the below descriptions of the wiper blade 500 according to the fifth embodiment, regarding the spoiler 530L, 530R formed in the lever assembly 1000, a spoiler section integrated in the central lever 5100 to become a section of the spoiler 530L, 530R is referred to as a central spoiler 531L, 531R, and a spoiler section integrated in the intermediate lever 5200L, 5200R to become another section of the spoiler 530L, 530R is referred to as an intermediate spoiler 532L, 532R, and a spoiler section integrated in the end lever 5300L, 5300R to become yet another section of the spoiler 530L, 530R is referred to as an end spoiler 533L, 533R.
The central lever 5100 centrally located in the lever rubber assembly 210, 220 is releasably coupled to the distal end of the wiper arm. Referring to FIGS. 64 to 67, the central lever 5100 includes a bracket portion 5110 at its middle. The bracket portion 5110 has a shape of a vertically-pierced rectangular parallelepiped. A pin is formed in the middle of the bracket portion 5110 in a direction perpendicular to the longitudinal direction of the central lever 5100. The pin 5111 participates in connection to the wiper arm. An adaptor (not shown), which is configured to be connected to a corresponding element provided in the distal end of the wiper arm through fitting, snapping, engaging, etc., may be coupled to the pin 5111. The pin 5111 may function as a pivot shaft of the wiper blade 500.
Further, the central lever 5100 includes a pair of central spoiler portions 5120, which extend in opposite directions from the bracket portion 5110 in the longitudinal direction of the wiper rubber 210 and form the central spoiler 531L, 531R. The central spoiler portion 5120 has an inverted V-shaped cross-section. A lower edge of the central lever 5100 (lower edges of the bracket portion 5110 and the central spoiler portion 5120) is straight or curved with a slight curvature. The central spoiler portion 5120 includes a pair of inclined surfaces 5121F, 5121R that are symmetrical in a width direction of the central lever 5100. The inclined surfaces 5121F, 5121R are located in the lateral surfaces of the central spoiler portion 5120. The inclined surfaces 5121F, 5121R extend in the longitudinal direction of the wiper rubber 510 in the central lever 5100 and form the lateral surfaces of the central spoiler portion 5120. Accordingly, the central spoiler 531L, 531R is integrated in the central lever 5100 through the central spoiler portion 5120 having the inclined surfaces 5121F, 5121R. An apex portion 5122 interconnects the inclined surfaces 5121F, 5121R at their upper edges.
The inclined surfaces 5121F, 5121R includes a concave surface. A width of the apex portion 5122 becomes sharply narrow from the bracket portion 5110 and is then constant. The inclined surfaces 5121F, 5121R are concave in harmony with such a width of the apex portion 5122. Thus, the cross-sectional profile of the central spoiler 531L, 531R is generally a triangle having both concave legs. The central spoiler portion 5120 has an arm receiving portion 5126 that receives a portion of the intermediate lever 5200L, 5200R and hides the same therein. The arm receiving portion 5126 is defined by a space between the inclined surfaces 5121F, 5121R. A longitudinal outer end surface 5123 of the central spoiler portion 5120 is inclined at an acute angle toward the distal end of the wiper rubber 210. The central lever 5100 has a plurality of transverse ribs 5127, which are oriented in the width direction, and a longitudinal rib 5128, which is oriented in the longitudinal direction and intersects the transverse ribs 5127. The transverse ribs 5127 and the longitudinal rib 5128 protrude such that they do not interfere with a top side of a portion of the intermediate lever 5200L, 5200R to be situated in the central spoiler portion 5120.
Each intermediate lever 5200L, 5200R is joined to the central lever 5100 and holds the wiper rubber assembly 210, 220. Descriptions are made as to the intermediate lever 5200L with reference to FIGS. 64, 65, 68 and 69. The intermediate lever 5200L and the intermediate lever 5200R are symmetrical in the longitudinal direction of the lever assembly 5000. The intermediate lever 5200L, 5200R includes an intermediate arm 5210 to be situated in the arm receiving portion 5126 of the central spoiler portion 5120 and an intermediate spoiler portion 5220 oppositely extending from the intermediate arm 5210. The intermediate arm 5210 has an inverted U-shaped cross-section. The intermediate spoiler portion 5220 has an inverted V-shaped cross-section. The intermediate arm 5210 extends from a longitudinal inner end surface 5223 of the intermediate spoiler portion 5220 toward the central lever 5100. A lower edge of the intermediate arm 5210 and a lower edge of the intermediate spoiler portion 5220 form an approximately straight line.
Each intermediate lever 5200L, 5200R has a clamp 5211 for fixing the wiper rubber assembly 210, 220. The clamp 5211 is formed at a distal end of the intermediate arm 5210. The clamp 5211 has a generally rectangular cross-section with its bottom side cut away partially and thus both ends thereof extend inwardly. When the intermediate lever 5200L, 5200R and the wiper rubber assembly 210, 220 are coupled to each other, an upper inner surface of the clamp 5211 is placed on a top side of the wiper rubber 210 and lateral portions of the clamp 5211 sandwich the spring rail 220 and a portion of the wiper rubber 210 adjacent thereto and the both ends of the clamp 5211 are inserted to the second groove 114 of the wiper rubber (see FIG. 72).
The intermediate spoiler 532L, 532R is integrally formed in the intermediate lever 5200L, 5200R. The intermediate spoiler portion 5220 has a pair of inclined surfaces 5221F, 5221R that are symmetrical in the width direction of the intermediate lever 5200L, 5200R. The inclined surfaces 5221F, 5221R are located in the lateral surfaces of the intermediate spoiler portion 5220. The inclined surfaces 5221F, 5221R extend in the longitudinal direction of the wiper rubber 210 in the intermediate lever 2200L, 2200R and form the lateral surfaces of the intermediate spoiler portion 5220. Accordingly, the intermediate spoiler 532L, 532R is integrated in the intermediate lever 5200L, 5200R through the intermediate spoiler portion 5220 having the inclined surfaces 5221F, 5221R. An apex portion 5222 interconnects the inclined surfaces 5221F, 5221R at their upper edges. The inclined surfaces 5221F, 5221R includes a concave surface. Further, a height dimension of the inclined surfaces 5221F, 5221R decreases gradually toward a longitudinal outer end of the intermediate lever 5200L, 5200R The inclined surfaces 5221F, 5221R may be curved with the same curvature as that of the inclined surfaces 5121F, 5121R of the central spoiler portion 5120, or curved with a curvature varying therefrom. In this embodiment, the inclined surfaces 5221F, 5221R of the intermediate spoiler portion 5220 is curved with the same curvature as that of the inclined surfaces 5121F, 5121R at the outer end surface 5123 of the central spoiler portion 5120.
The intermediate spoiler portion 5220 has an arm receiving portion 5226, which receives a portion of the end lever 5300L, 5300R and hides the same therein. The arm receiving portion 5226 is defined by a space between the inclined surfaces 5221F, 5221R. The intermediate lever 5200L, 5200R has a plurality of transverse ribs 5227 and a longitudinal rib 5228 therein. The transverse ribs 5227 are oriented in the width direction. The longitudinal rib 5228 is oriented in the longitudinal direction and intersects the transverse ribs 5227. The transverse ribs 5227 and the longitudinal rib 5228 are located in the intermediate arm 5210 as well as the intermediate spoiler portion 5220. Further, the transverse ribs 5227 and the longitudinal rib 5228 in the intermediate spoiler portion 5220 protrude such that they do not interfere with a portion of the end lever 5300L, 5300R to be situated in the intermediate spoiler portion 5220.
The central lever 5100 and the intermediate lever 5200L, 5200R are joined to each other via a hinge-joint portion hinge-jointing the interior of the central spoiler portion 5120 and the intermediate arm 5210. When the central lever 5100 and the intermediate lever 5200L, 5200R are joined to each other, the intermediate arm 5210 of the intermediate lever is situated in the arm receiving portion 5126 of the central spoiler portion 5120 and is thus hidden within the central spoiler portion 5120 when viewed from outside. In other words, a portion (e.g., the intermediate arm 5210) of one of the adjacent levers (e.g., the intermediate lever 5200L, 5200R) is situated in and hinge-jointed to the spoiler portion of the other of the adjacent levers (e.g., the central lever 5100), which is further inward than said one of the adjacent levers.
The hinge-joint portion of this embodiment comprises a pair of hinge pins 5411 and a pair of fitting holes 5421 to which the hinge pins 5411 are fitted respectively. Hinge engagement between the hinge pins 5411 and the fitting holes 5421 makes the hinge-joint portion. In this embodiment, the hinge pins 5411 are disposed in the arm receiving portion 5126 of the central spoiler portion 5120, while the fitting holes 5421 are disposed in the intermediate arm 5210 of the intermediate lever 5200L, 5200R.
The central lever 5100 has an element for restricting the intermediate arm 5210 from moving in the width direction of the central lever 5100 so that the intermediate lever 5200L, 5200R joined to the central lever can be retained relative to the central lever 5100 without shake. Said element is configured such that the intermediate arm 5210 is inserted to the element and the movement in its width direction is restricted. The element comprises a pair of opposing surface portions or protrusion portions, which are located in the arm receiving portion 5126 of the central spoiler portion 5120, and to which the intermediate arm 5210 can be inserted or fitted. In this embodiment, the element comprises two pairs of raised surfaces 5131, 5132 formed in a lower inner surface of the central spoiler portion 5120. The raised surfaces 5131, 5132 of each pair are opposed to each other inside the central spoiler portion 5120 and protrude inwardly of the central spoiler portion 5120. The hinge pins 5411 protrude from the raised surfaces 5131 inwardly of the central spoiler portion 5120. The hinge pin 5411 has a beveled surface 5411 a at its lower portion to facilitate fitting to the fitting holes 5421. When the central lever 5100 and the intermediate lever 5200L, 5200R are joined to each other, the intermediate arm 5210 is inserted or fitted in between the raised surfaces 5131, 5132. Spacing between the raised surfaces 5131, 5132 of each pair is almost equal to or somewhat greater than the width of the intermediate arm 5210.
The fitting holes 5421 may pierce through the lateral portions of the intermediate arm 5210 or be formed at a predetermined depth. The fitting holes 5421 are spaced from the longitudinal inner end surface 5223 of the intermediate spoiler portion 5220 by the spacing between the longitudinal outer end surface 5123 of the central spoiler portion 5120 and the hinge pin 5411.
The end levers 5300L, 5300R are joined to the intermediate levers 5200L, 5200R respectively and hold the wiper rubber assembly 210, 220. Descriptions are made as to the end lever 5300L with reference to FIGS. 64, 65, 70 and 71. The end lever 5300L and the end lever 5300R are symmetrical in the longitudinal direction of the lever assembly 5000. The end lever 5300L, 5300R includes an end arm 5310 to be situated in the arm receiving portion 5226 of the intermediate spoiler portion 5220 and an end spoiler portion 5320 oppositely extending from the end arm 5310. The end arm 5310 has an inverted U-shaped cross-section. The end spoiler portion 5320 has an inverted V-shaped cross-section. The end arm 5310 extends from a longitudinal inner end surface 5323 of the end spoiler portion 5320 toward the central lever 5100. A lower edge of the end arm 5310 and a lower edge of the end spoiler portion 5320 form an approximately straight line.
The end spoiler 533L, 533R is integrally formed in the end lever 5300L, 5300R. The end spoiler portion 5320 has a pair of inclined surfaces 5321F, 5321R that are symmetrical in the width direction of the end lever 5300L, 5300R. The inclined surfaces 5321F, 5321R are located in the lateral surfaces of the end spoiler portion 5320. The inclined surfaces 5321F, 5321R extend in the longitudinal direction of the wiper rubber 210 in the end lever 5300L, 5300R and form the lateral surfaces of the end spoiler portion 5320. Accordingly, the end spoiler 533L, 533R is integrated in the end lever 5300L, 5300R through the end spoiler portion 5320 having the inclined surfaces 5321F, 5321R. An apex portion 5322 interconnects the inclined surfaces 5321F, 5321R at their upper edges. The inclined surfaces 5321F, 5321R includes a concave surface. Further, a height dimension of the inclined surfaces 5321F, 5231R decreases gradually toward the distal end of the wiper blade 500. Further, lower edges of the inclined surfaces 5321F, 5321R approach each other at a distal end of the end lever 5300L, 5300R, thereby forming a round distal end of the end lever 5300L, 5300R along with the apex portion 5322. The inclined surfaces 5321F, 5321R may be curved with the same curvature as that of the inclined surfaces 5221F, 5221R of the intermediate spoiler portion 5220, or curved with a curvature varying therefrom. In this embodiment, the inclined surfaces 5321F, 5321R of the end spoiler portion is curved with the curvature greater than that of the inclined surfaces 5221F, 5221R at the outer end surface 5224 of the intermediate spoiler portion 5220.
The end lever 5300L, 5300R has a plurality of transverse ribs 5327 and a longitudinal rib 5328 therein. The transverse ribs 5327 are oriented in the width direction. The longitudinal rib 5328 is oriented in the longitudinal direction and intersects the transverse ribs 5327. The transverse ribs 5327 and the longitudinal rib 5328 are located in the end arm 5310 as well as the end spoiler portion 5320.
Each end lever 5300L, 5300R has two clamps 5325, 5311 for fixing the wiper rubber assembly 210, 220. A longitudinal inner clamp 5311 is formed at a distal end of the end arm 5310. The clamp 5311 has the same configuration as the clamp 5211 of the intermediate lever. A longitudinal outer clamp 5325 is formed at a lower edge of the end spoiler portion 5320 in the vicinity of a longitudinal outer end thereof. The clamp 5325 extends from the lower edge of the end spoiler portion 5320 in a V shape. Both ends of each clamp 5311, 5325 are inserted to the second groove 114 of the wiper rubber 210. A pair of longitudinally extending ribs 5329 are formed inside the end spoiler portion 5320 opposite the clamp 5325. A portion of the rib 5329 above the both ends of the clamp 5325 protrude downwardly to form a pressing portion 5333. When the lever assembly 5000 and the wiper rubber assembly 210, 220 are coupled to each other, the pressing portion 5333 presses the top side of the wiper rubber 210 downwardly (toward the both ends of the clamp 5325) or is placed on the top side of the wiper rubber 210 with little gap. Thus, the wiper rubber 210 is firmly fixed to the clamp 5325 by the pressing portion 5333.
The intermediate lever 5200L, 5200R and the end lever 5300L, 5300R are joined to each other via a hinge-joint portion hinge-jointing the interior of the intermediate spoiler portion 5220 and the end arm 5310 to each other. When the intermediate lever 5200L, 5200R and the end lever 5300L, 5300R are joined to each other, the end arm 5310 is situated in the arm receiving portion 5226 of the intermediate spoiler portion 5220 and is thus hidden within the intermediate spoiler portion 5220 when viewed from outside.
The hinge-joint portion between the intermediate lever 5200L, 5200R and the end lever 5300L, 5300R comprises a pair of hinge pins 5412 and a pair of fitting holes 5422 to which the hinge pins 5412 are fitted respectively. The hinge pins 5412 are disposed in the arm receiving portion 5226 of the intermediate spoiler portion 5220. The fitting holes are disposed in the end arm 5310.
The intermediate lever 5200L, 5200R has an element for restricting the end arm 5310 from moving in the width direction of the intermediate lever 5200L, 5200R so that the end lever 5300L, 5300R joined to the intermediate lever can be retained relative to the intermediate lever 5200L, 5200R without shake. Said element in the intermediate lever 5200L, 5200R has the same configuration as the element described above in connection with the central lever 5100. As said element, two pairs of raised surfaces 5231, 5232 are formed in a lower inner surface of the intermediate lever 5200L, 5200R. The raised surfaces 5231, 5232 of each pair are opposed to each other inside the intermediate spoiler portion 5220 and protrude inwardly of the arm receiving portion 5226. The hinge pins 5412 protrude from the raised surfaces 5231 inwardly of the arm receiving portion 5226. The hinge pin 5412 has a beveled surface 5412 a at its lower portion to facilitate fitting to the fitting holes 5422. When the intermediate lever 5200L, 5200R and the end lever 5300L, 5300R are joined to each other, the end arm 5310 is inserted or fitted in between the raised surfaces 5231, 5232. Spacing between the raised surfaces 5231, 5232 of each pair is almost equal to or somewhat greater than the width of the end arm 5310.
The fitting holes 5422 may pierce through the lateral portions of the end arm 5310 or be formed at a predetermined depth. The fitting holes 5422 are spaced from the longitudinal inner end surface 5323 of the end spoiler portion 5320 by the spacing between the longitudinal outer end surface 5224 of the intermediate spoiler portion 5220 and the hinge pin 5412. A guide groove 5423 for guiding the insertion of the hinge pin 5412 is formed from a top side of the end arm 5310 to the fitting hole 5422.
Descriptions are made as to an example assembly of the wiper blade 500 according to the fifth embodiment with reference to FIG. 72.
The longitudinal outer end surface 5123 of the central spoiler portion 5120 and the longitudinal inner end surface 5223 of the central spoiler portion 5220 are approximated and one of them is pressed or pushed down against the other of them. Then, the hinge pins 5411 of the central spoiler portion 5120 enter the fitting holes 5421 while pressing or pinching an upper portion of the intermediate arm 5210. Subsequently, the hinge pins 5411 snap-engage the fitting holes 5421, thereby hinge-jointing the central lever 5100 and the intermediate lever 5200L to each other via the hinge pins 5411 and the fitting holes 5421. When the central lever 5100 and the intermediate lever 5200L are joined to each other, a portion of the intermediate arm 5210 adjacent to the fitting hole 5421 and another portion further inward than the portion are sandwiched between the raised surfaces 5131 as well as between the raised surfaces 5132. The intermediate lever 5200L and the end lever 5300L are joined to each other in the above-described manner. That is, the longitudinal outer end surface 5224 of the intermediate spoiler portion 5220 and the longitudinal inner end surface 5323 of the end lever 5300L are approximated and one of them is pressed against the other of them. Then, the hinge pins 5412 of the intermediate spoiler portion 5220 snap-engage the fitting holes 5422 of the end arm 5210, thereby hinge-jointing the intermediate lever 5200L and the end lever 5300L to each other. Hinge-joint between the central lever 5100 and the intermediate lever 5200R and hinge-joint between the intermediate lever 5200R and the end lever 5300L are made in the above-described manner.
By fitting the clamps 5325, 5311 of the end levers 5300L, 5300R and the clamps 5211 of the intermediate levers 5200L, 5200R to the second groove 114 of the wiper rubber 210, the wiper rubber assembly 210, 220 and the lever assembly 5000 are coupled to each other. For example, the clamps 5325, 5311 of the end lever 5300L, the clamp 5211 of the intermediate lever 5200L, the clamp 5211 of the intermediate lever 5200R and the clamps 5311, 5325 of the end lever 5300R are inserted to the second groove 114 of the wiper rubber one after another while sliding the wiper rubber assembly 210, 220 along the lever assembly 5000. If the both ends of the clamp 5325 of the end lever 5300L is fitted to the insertion holes 117, then the wiper rubber assembly 210, 220 is fixed to the lever assembly 5000.
Referring again to FIGS. 61 to 63 showing the assembled wiper blade 500, the lever assembly 5000 holds the wiper rubber assembly 210, 220 at six pressure points via the clamps 5325, 5311 of the end levers 5300L, 5300R and the clamps 5211 of the intermediate levers 5200L, 5200R. Further, the central lever 5100, the intermediate levers 5200L, 5200R and the end levers 5300L, 5300R are straight arranged along the length of the wiper rubber 210 and are at the same height on the wiper rubber 210. Further, in the assembled wiper blade 500, the inclined surfaces 5121F, 5121R of the central spoiler portion 5120, the inclined surfaces 5221F, 5221R of the intermediate spoiler portion 5220 and the inclined surfaces 5321F, 5321R of the end spoiler portion 5320 are straight adjoined one after another, thereby defining the spoiler 530L, 530R having the cross-sectional profile varying in the longitudinal direction and having a decreasing height dimension. The longitudinal end surface 5123 of the central lever 5100, the longitudinal end surfaces 5223, 5224 of the intermediate lever 5200L, 5200R and the longitudinal end surface 5323 of the end lever 5300L, 5300R are inclined at an acute angle toward the distal end of the wiper blade 500. Thus, the intermediate lever 5200L, 5200R and the end lever 5300L, 5300R cannot pivot upwardly relative to the central lever 5100. Accordingly, when a downward load acts on the wiper blade 500, the lever assembly 5000 brings the wiper rubber 210 into strong contact with the windshield.
In this embodiment, the hinge pins 5411, 5412 are located in the central spoiler portion 5120 and the intermediate spoiler portion 5220, while the fitting holes 5421, 5422 are located in the intermediate arm 5210 and the end arm 5310. In another embodiment, the hinge pins may be disposed in the intermediate arm 5210 and the end arm 5310, while the fitting holes corresponding to the hinge pins may be in the arm receiving portion 5126 of the central spoiler portion 5120 and the arm receiving portion 5226 of the intermediate spoiler portion 5220. Further, wiper blades according to other embodiments may be configured to hold the wiper rubber at four or eight pressure points by means of the above-described hinge-joint portion. That is, opposing end surfaces of two adjacent levers in the lever assembly 1000 of the first embodiment or the lever assembly 3000 of the third embodiment may be inclined toward the distal end of the wiper rubber and hinge joint between the adjacent levers may comprise the hinge pins 5411, 5412 and the fitting holes 5421, 5422.
FIGS. 73 to 78 show a wiper blade 600 according to a sixth embodiment. The wiper blade 600 includes a lever assembly having an additional element that prevents the lift of the wiper blade or minimizes an eddy flow phenomenon occurring inside the lever assembly.
|
# Redis Persistent Pub Sub
This Redis module (available in Redis 4.x) adds a new queue implementation different from the Redis Pub/Sub (i.e. SUBSCRIBE, PUBLISH etc).
This new implementation enables clients to disconnect from the server and retrieve messages whenever it reconnects. It also provides message ack:ing (and nack:ing), as well as retries for messages that are not acked within the timeout specified when fetching messages.
More documentation will follow.
|
trouble formatting serial data from python enumeration
So I get a list of mentions from twitter, and need to know the index of each mention. To do this I use:
for idx, result in enumerate(mentions, start = 48):
message = result['text']
print idx, message
which returns
48 " first message"
as expected. However, I need to use this index for some serial data that requires me to convert the index into hex. So.. I use:
hidx = hex(idx)
which then returns 0x30. However I need to somehow have this result in the exact format of "\x30" so that I can use serial to write:
serial.write("\x30")
what is the best way to accomplish this? If I keep my hex-converted index code the way it is, I get that pesky extra 0 and no backslash that causes the serial code to actually write serial.write(0x30), which is not what I need. Im hoping to find a way that, because of the for loop, I will receive:
serial.write("\x30")
serial.write("\x31")
serial.write("\x32")
ect. for as many mentions as I need.
Is there a way to strip the first zero and add the \? Maybe a better way? Im new to python and serial communication so any help will be much appreciated.
(Assuming Python 2) "\x30" is a 1-byte string and the byte in question is the one at ASCII code 48:
>>> print repr('\x30')
'0'
So, all you need to do to emit it is serial.write(chr(idx)) -- no need to mess with hex!
|
But its over a week now and nova primes unvaulted. I play on console. If DE warframe to be a good game, they should first allow players to actually to play smoothly. I have spent 500 hours+ and I dont want it to be wasted on a bug
|
Board Thread:Role Play/@comment-25684606-20150718204313/@comment-25684606-20150823233011
Cult
Rosalinde stopped at the exit as she saw Dena still being there.
"Don't you want to go with him?"
|
JON N. and Teresa N., personally and as guardians for Patricia N., Plaintiffs, v. BLUE CROSS BLUE SHIELD OF MASSACHUSETTS, Defendant.
Civil Action No. 08-10776-JLT.
United States District Court, D. Massachusetts.
Feb. 16, 2010.
Jonathan M. Feigenbaum, Phillips & Angley, Boston, MA, James L. Harris, Jr., Bradley R. Sidle, Brian S. King, Attorney at Law, Salt Lake City, UT, for Plaintiffs.
Joseph D. Halpern, Blue Cross Blue Shield Law Dept., Boston, MA, Robert G. Wing, Prince Yeats & Geldzahler, Salt Lake City, UT, for Defendant.
MEMORANDUM
TAURO, District Judge.
I. Introduction
This action challenges a denial of health insurance benefits under an employee welfare benefits plan, established pursuant to the Employee Retirement Income Security Act of 1974 (“ERISA”). Plaintiffs Jon N. and Teresa N. are parents and legal guardians of Patricia N. (“Patricia” or “Trida”), a minor, who is insured under a health insurance plan sponsored by her father’s employer and administered by Defendant Blue Cross Blue Shield of Massachusetts (“Blue Cross”). Plaintiffs allege that Blue Cross improperly denied reimbursement for inpatient substance abuse and mental health treatment that Patricia received at the Island View Residential Treatment Center (“Island View”) from August 30, 2006, to June 22, 2007. For the following reasons, Defendant’s Motion for Summary Judgment [# 50] is ALLOWED and Plaintiffs’ Motion for Summary Judgment [# 57] is DENIED.
II. Background
A. Patricia’s Medical History and Treatment
Prior to her admission at Island View, Patricia had a long history of emotional and behavioral health issues. To address these problems, she received, beginning in 2004, individual outpatient therapy from Amy Lilavois, a Licensed Mental Health Counselor. But in June of 2006, Ms. Lilavois observed that, despite therapy and medication, Patricia’s behavior had become more risky. Ms. Lilavois therefore recommended residential treatment. An educational consultant who evaluated Patricia’s treatment history agreed with this recommendation. And so, Plaintiffs enrolled Patricia in Second Nature Entrada Wilderness Program (“Second Nature”). There, from June 29, 206 to August 29, 2006, she was treated for Major Depressive Disorder, Bulimia Nervosa, Alcohol Dependence, Marijuana Abuse, Oppositional Defiant Disorder, and Parent-Child Relational Problem.
The Confidential Psychological Assessment Report completed by Second Nature on August 8, 2006, states that “Trida denies any suicidal ideation ... Tricia denies any obsessions or compulsions, paranoia, auditory or visual hallucinations, racing thoughts, excessive energy, attentional difficulties, as well as grandiosity.” Nonetheless, two licensed clinical psychologists, who treated Patricia at Second Nature, recommended additional treatment at a secure residential facility upon her discharge from the program. Based on these recommendations, Plaintiffs procured residential treatment for Patricia at Island View, where she remained from August 30, 2006, until June 22, 2007. Patricia’s treatment at Island View included individual therapy, group therapy, and family therapy, substance abuse counseling, academic and recreational programs, and ongoing medication evaluation and management.
Clinicians at Island View conducted a Psychiatric Evaluation upon Patricia’s admission, which confirmed Second Nature’s report that Patricia “has had no recent cutting or self-harm behavior. In the remote past she has had some suicidal ideation, however, has none currently and has never made any suicide attempt.... [C]urrently feels mildly depressed.” The Psychiatric Evaluation also states that Patricia’s “mood is mildly depressed and affect is congruent. Her thought content is without hallucinations, delusions, suicidal or homicidal ideation....The resident denies a desire to hurt or kill herself and there are no substantial self-harm, i.e. cutting, or suicidal risk factors present. The resident is oriented to person, time and place, sober, non-psychotic, attentive and cooperative.”
A Suicide Assessment completed at Island View on August 30, 2006, reports no suicide attempts or thoughts of suicide. The Psychiatric Admitting Note similarly records “[n]o suicide attempt” and “[tjhought content without hallucinations/delusions, suicidal ideation, homicidal ideation. Mood mildly depressed, affect congruent!” Progress Notes for August 30, 2006, state that “Trida indicated that she felt like she was no risk for attempting suicide or self-harm at this time. She indicated that she was not experiencing enough stress or anxiety or depression to feel suicidal.”
B. Patricia’s Coverage Under the Plan
Patricia is a participant in her father’s health benefits plan (the “Plan”), which Blue Cross funds and administers. The Plan includes a provision for “Mental Health and Substance Abuse Treatment,” which covers “biologically-based mental conditions,” such as major depressive disorder, and other mental conditions, including drug addiction and alcoholism.
Under the proper circumstances, the Plan covers inpatient hospital care, acute or subacute residential treatment, partial hospitalization, and intensive outpatient treatment, along with routine outpatient treatment. But the contract between Blue Cross and Plaintiff Jon N., the Blue Care Elect Subscriber Certificate, specifies that such coverage will only be provided for those services that are “medically necessary.”
Under the terms of the Subscriber Certificate, “Blue Cross and Blue Shield decides which covered services are medically necessary.” To qualify, all services must be (1) “[consistent with the diagnosis and treatment of [the participant’s] condition”; (2) “[e]ssential to improve [the participant’s] health outcome and as beneficial as any established alternatives covered by this contract”; (3) “[a]s cost effective as any established alternatives”; and (4) “[f]urnished in the least intensive type of medical care setting required.” Importantly, the Plan grants Blue Cross “full discretionary authority to make decisions regarding eligibility for benefits,” as well as “to conduct medical necessity review.”
In evaluating whether residential psychiatric care is medically necessary to treat a participant’s condition, Blue Cross physician reviewers use the initial review InterQual Behavioral Health Criteria (“InterQual Criteria”). The InterQual Criteria are utilization review guidelines- used widely throughout the industry to determine the level of care required by an individual plan participant. The InterQual Criteria contain initial review guidelines (“InterQual Initial Review Criteria”), which physician reviewers use to determine whether the participant qualifies for admission to a particular type of treatment facility, and concurrent review guidelines (“InterQual Concurrent Review Criteria”), which physician reviewers use to determine whether a participant who initially qualified for admission to a treatment facility qualifies for continued care in the facility. Additionally, they include separate subsets of criteria by which to evaluate the necessity of different levels of inpatient treatment. Listed in order of decreasing intensity, those levels are subacute psychiatric care, psychiatric residential treatment, and psychiatric therapeutic group home.
When Blue Cross denies a claim, the Plan provides members with the right to seek external review by the Massachusetts Department of Public Health’s Office of Patient Protection (“OPP”), pursuant to M.G.L. c. 1760. Under the terms of the Subscriber Certificate, any decision rendered by way of the OPP external review process “will be accepted as the final decision” on coverage, once it has been sought by the participant.
C. Review of Plaintiffs’ Claims for Reimbursement
On August 31, 2006, Plaintiffs requested authorization from Blue Cross for Patricia’s treatment at Island View. Dr. William Lesner, a board-certified Child and Adolescent psychiatrist, reviewed Plaintiffs’ claim on behalf of Blue Cross. After speaking with a nurse at Island View and reviewing the relevant clinical notes, Dr. Lesner concluded in a letter to Plaintiffs dated September 5, 2006, that Patricia met the criteria for treatment in an outpatient setting, but that subacute residential treatment, such as that provided by Island View, was not medically necessary.
In a letter dated November 20, 2006, Mary Covington, Plaintiff Jon N.’s authorized representative, appealed Blue Cross’ denial of benefits and provided additional medical records in support of the claim. A second Blue Cross physician reviewer, Dr. Kerim Munir, reviewed the original clinical notes, as well as the supplemental medical records, and upheld the initial decision denying coverage. Dr. Munir similarly communicated this decision to Plaintiffs, informing them that, although Blue Cross did not find subacute residential treatment to be medically necessary for Patricia’s condition, Blue Cross would authorize treatment in an outpatient setting.
Plaintiffs again appealed the denial of benefits on January 19, 2007, and requested that Blue Cross provide them with the physician reviewer’s opinion, clinical rationale, and the reasons for the denial in relation to the InterQual Criteria. Blue Cross consulted with a third physician reviewer, Dr. Elyce Kearns, who also determined that “[t]he member does not meet criteria for admission to the Acute Residential treatment level of care also known as psychiatric subacute care.” Accordingly, Dr. Kearns upheld the denial of coverage. On January 30, 2007, a Case Specialist in Blue Cross’ Grievance Program followed up with a letter explaining the reasons for Dr. Kearns’ decision.
On February 9, 2007, Blue Cross received two additional doctors’ letters from Plaintiffs, providing supplemental information pertaining to Patricia’s treatment. Blue Cross treated this supplementary information as constituting an additional member appeal and once again had Dr. Lesner, the initial reviewing physician, review Plaintiffs’ claim for coverage. Dr. Lesner reviewed all of the information provided up to that time and again concluded that Patricia did not meet the InterQual Criteria for subacute residential treatment.
On February 19, 2007, Mary Covington sought external review of the coverage denials by OPP. OPP assigned the appeal to Maximus CHDR (“Maximus”), an independent external review agency located in Virginia, with offices in New York and throughout the country. Maximus provides utilization review services for numerous government clients, including federal agencies such as the Centers for Medicare and Medicaid Services, the Office of Personnel Management, the Department of Defense, and the Department of Veterans Affairs, as well approximately thirty state regulatory agencies. As required by M.G.L. c. 1760, the assignment to Maxi-mus was random.
On March 20, 2007, a Blue Cross Case Specialist sent Maximus the complete file for Patricia’s grievance, along with a cover letter summarizing the case, as required by OPP regulations. Maximus assigned the case to one of its contracted psychiatrist reviewers, a practicing physician who is board-certified in adult psychiatry and child and adolescent psychiatry with experience in treatment of patients with Patricia’s diagnoses.
Between January 1, 2006 and December 31, 2008, the Maximus physician reviewer assigned to Patricia’s case reviewed six Blue Cross cases in Massachusetts. He reversed Blue Cross in two of those cases, partially reversed in one, and affirmed in three. He completed eleven independent medical reviews for other Massachusetts health plans during the same time period. In those cases he reversed four times, partially reversed twice, and affirmed five times. A Quality Assurance review of his work by a Maximus Medical Director for the same period revealed no errors or problems. Notably, the only compensation a Maximus reviewer receives for his work in a case like this is a flat fee of $150.00 per review.
The Maximus reviewer upheld the denial of coverage, concluding, as had all of the other reviewers, that treatment at a subacute residential level of care was not medically necessary for Patricia. “Although a seriously disturbed individual obviously in need of psychiatric treatment I believe that treatment could have been rendered appropriately [to Patricia] in a less restrictive manner. I concur -with other reviewers.” On April 3, 2007, Blue Cross informed Plaintiffs of OPP’s decision to uphold the denial of coverage based on Maximus’ independent review.
On August 8, 2007, Blue Cross received a provider appeal from Island view that included additional medical records, updating treatment through May 31, 2007. On August 21, 2007, Dr. Lesner reviewed the prior clinical notes and the medical record as supplemented by Island View, and decided to send the case out for external same specialty standard review at MCMC Peer Review Analysis (“MCMC”), an external independent review agency. MCMC’s review was conducted by Dr. Danielle C. Suykerbuyk, who is board certified in Psychiatry & Neurology/ Psychiatry and Child and Adolescent Psychiatry & Neurology, and is an actively practicing specialist in those areas. Dr. Suykerbuyk was asked to determine first whether Patricia met the InterQual Initial Review Criteria for admission to psychiatric subacute care and, if so, whether she met the InterQual Concurrent Review Criteria for continued care throughout the intervention. Dr. Suykerbuyk found that Patricia did not meet the InterQual Initial Review Criteria for admission to subacute residential treatment, but that her symptoms did qualify for care at an outpatient level. Because Dr. Suykerbuyk concluded that the Plan did not provide coverage for Patricia’s care based on the initial review criteria, she found it unnecessary to apply the concurrent review criteria to determine whether there might be coverage for continued care. Based on this final external review, Dr. Lesner informed Plaintiffs and Island View that Blue Cross remained firm in its denial of coverage for Patricia’s residential treatment.
III. Discussion
A. Standard of Review
In an ERISA action of this nature, review is “confined to the administrative record before the ERISA plan administrator” and, thus, “the district court sits more as an appellate tribunal than as a trial court. It does not take evidence, but, rather, evaluates the reasonableness of an administrative determination in light of the record compiled before the plan fiduciary.” In this context, “summary judgment is simply a vehicle for deciding the issue,” and “the non-moving party is not entitled to the usual inferences in its favor.”
The Supreme Court set out the standards of decision for an ERISA denial of benefits action in Firestone Tire & Rubber Co. v. Bruch. The appropriate standard of review depends on whether the Plan grants the administrator “discretionary authority to determine eligibility for benefits or to construe the terms of the plan.” If the administrator lacks discretion under the Plan, a court must review the decision de novo. If the Plan grants the administrator discretion, however, a court reviews the administrator’s decision under the deferential arbitrary and capricious standard. But if the court determines that the plan administrator operated under a conflict of interest in reviewing the participant’s claim, the court must weigh such conflict as a factor in determining whether the plan administrator’s denial of benefits was an abuse of discretion.
“The threshold question, then, is whether the provisions of the employee benefit plan ... reflect a clear grant of discretionary authority to determine eligibility for benefits.” The Plan at issue here explicitly gives Blue Cross “full discretionary authority to make decisions regarding eligibility for benefits” and “to conduct medical necessity review.” The Plan further provides that “[a]ll determinations of Blue Cross and Blue Shield with respect to any matter within its assigned responsibility will be conclusive and binding on all persons unless it can be shown that the interpretation or determination was arbitrary or capricious.” It appears to this court, therefore, that Blue Cross’s discretionary authority under the plan is abundantly clear.
Nonetheless, Plaintiffs argue that, although the terms of the contract between Blue Cross and Jon N.’s employer provide for the requisite discretionary authority, the Subscriber Certificate does not give adequate notice to participants of any grant of discretionary authority to Blue Cross. Plaintiffs, therefore, submit that the proper standard of review is de novo. This court is unpersuaded by Plaintiffs’ argument. Plaintiffs’ Subscriber Certificate clearly states that “Blue Cross and Blue Shield decides which covered services are medically necessary and appropriate.... ” This certainly suffices to notify participants of Blue Cross’s discretion with regard to coverage determinations. Accordingly, this court finds it appropriate to review the administrator’s decision under the arbitrary and capricious standard of review.
Further, this court finds that the arbitrary and capricious standard is not affected by any conflict of interest in this case. Plaintiff argues that Blue Cross operates under a conflict of interest and, therefore, deserves less deference because Blue Cross both funds the plan and evaluates benefits claims. The Supreme Court recently clarified in Metropolitan Life Insurance, Co. v. Glenn that this “dual role” indeed creates a conflict of interest.
In such a case, however, the conflict of interest is but one factor among many that may “act as a tiebreaker when the other factors are closely balanced, the degree of closeness necessary depending upon the tiebreaking factor’s inherent or case-specific importance.” The Court went on to note that the administrator’s dual role “should prove less important (perhaps to the vanishing point) where the administrator has taken active steps to reduce potential bias and to promote accuracy.”
“[C]ourts are duty-bound to inquire into what steps a plan administrator has taken to insulate the decisionmaking process against the potentially pernicious effects of structural conflicts.... [I]n cases in which a conflict has in fact infected a benefit-denial decision, such a circumstance may justify a conclusion that the denial was itself arbitrary and capricious.” Importantly, however, a real conflict must exist. “[A] chimerical, imagined, or conjectural conflict will not strip the fiduciary’s determination of the deference that otherwise would be due.” Notably, Plaintiffs bear the burden of demonstrating that a conflict of interest has infected the denial of benefits decision under review.
Blue Cross concedes that it indeed has such an structural conflict of interest, but argues that the conflict is neutralized by the fact that OPP rendered the final decision on Plaintiffs’ claim. The Plan delegates decision-making authority to the external review agency selected by OPP whenever a participant invokes his right to third-party review, as Plaintiffs did here. The Plan also provides that the ensuing adjudication “will be accepted as the final decision.”
Plaintiffs chose to exercise their right to external review through OPP, which the Plan plainly identified as binding on the parties. Plaintiffs present no credible evidence that Maximus was affected by Blue Cross’s structural conflict of interest. Maximus has no apparent affiliation with Blue Cross and reviewed Plaintiffs’ claim independently, without any deference to Blue Cross’s initial decision. OPP paid Maximus the standard fee dictated by its contract with the agency and Maximus’ physician reviewer was, in turn, given the standard fee paid out by Maximus for such a review. Plaintiff has presented no evidence that Blue Cross controls or influences either OPP’s selection of an external review agency or the external review agency’s selection of its physician reviewers.
Further, even though the Plan dictates that OPP’s decision will be binding on the Plaintiffs, Blue Cross commissioned a second external review of the claim after Plaintiffs submitted supplementary medical records updating treatment from the OPP review through May 31, 2007. As such, Plaintiffs have clearly “taken advantage of an external review process that is expressly designed to reduce the potentially pernicious effects of Blue Cross’s structural conflict, and Blue Cross’s conflict of interest has been diminished ‘to the vanishing point’ as a result.”
In the alternative, Plaintiffs argue that this court should review the administrator’s determination de novo because the physician reviewers failed to utilize the proper criteria to evaluate the treatment received by Patricia at Island View. The InterQual Criteria include separate sets of criteria by which to evaluate the necessity of subacute psychiatric care, psychiatric residential treatment, and placement in a psychiatric therapeutic group home. The physician reviewers applied only the criteria relating to subacute treatment, but did not apply criteria to determine whether residential care or a therapeutic group home might have been medically necessary for Patricia.
Plaintiffs contend that this was an abuse of Blue Cross’s discretion because (1) Massachusetts Mental Health Parity Law requires Blue Cross to provide coverage for intermediate inpatient care at levels less intensive than subacute treatment and (2) the care that Patricia received at Island View was in fact less intensive than subacute treatment. Defendant, on the other hand, submits that the physician reviewers appropriately evaluated Patricia’s treatment using only the subacute care criteria because (1) Massachusetts law does not require Blue Cross to provide coverage for residential treatment other than subacute care and partial hospitalization and (2) in any case, the care provided by Island View was indeed subacute, based on a comparison of the services provided with the InterQual Criteria’s description of subacute care.
Plaintiffs rely on the language of Bulletin 2003-11 from the Massachusetts Commissioners of Mental Health and Insurance, entitled “Intermediate Care as part of Mental Health Parity Benefits”. The Bulletin states that mental health benefits must “consist of a range of medically necessary inpatient, intermediate, and outpatient services to take place in the least restrictive clinically appropriate setting. ... Intermediate services include, but are not limited to, Level III community-based detoxification, acute residential treatment, partial hospitalization, day treatment, and crisis stabilization.... While no statute requires coverage for custodial residential services, Chapter 80 mandates carriers to provide intermediate care services for the medically necessary treatment of behavioral disorders.”
Plaintiffs argue that this missive from the Commonwealth of Massachusetts requires Blue Cross to cover all medically necessary residential services. Defendant counters that Blue Cross provides the range of coverage contemplated by the Bulletin by providing benefits for inpatient hospital care, acute or subacute residential treatment, partial hospitalization, and intensive outpatient treatment.
This court agrees with Defendant. Even assuming that the Bulletin is binding law with which Blue Cross must comply, the Bulletin’s plain language only appears to require coverage for a range of mental health services that includes some form of intermediate residential care. Blue Cross does so by providing coverage for medically necessary subacute residential treatment, partial hospitalization, and intensive outpatient care. This court cannot reasonably interpret the Bulletin to require Blue Cross to provide coverage for all forms of intermediate care.
Notably, the range of coverage provided by the Plan is implicitly approved by the Commissioner of the Massachusetts Division of Insurance through its accreditation of Blue Cross as a health benefits carrier. Given that the Plan covers intermediate care in the form of acute or subacute residential treatment, partial hospitalization, and intensive outpatient care, the physician reviewers appropriately applied only the InterQual Criteria for subacute care. It is Blue Cross’s policy to consider psychiatric subacute care, partial hospitalization, and intensive outpatient care and then to authorize coverage for the least restrictive clinically appropriate setting. Here, the physician reviewers determined that Patricia’s case required intensive outpatient treatment, but nothing more. Blue Cross was not further required to consider whether Patricia qualified for other types of intermediate care for which Blue Cross does not provide coverage.
Moreover, even assuming that the Bulletin relied on by Plaintiffs indeed required Blue Cross to cover lesser levels of inpatient treatment, this court is persuaded that the care Patricia received at Island View (the care for which coverage was requested) was in fact subacute psychiatric care.
Plaintiffs have presented no evidence to rebut Defendant’s argument that Patricia’s treatment qualified as subacute psychiatric care under the definition provided by the InterQual Criteria. The InterQual Criteria describe subacute care as involving intensive therapies, behavior modification, psychopharmacology, nursing assessment and intervention, diagnostic evaluation, and educational planning, all of which were part of Patricia’s treatment program at Island View. In contrast, the guidelines describe the two lesser levels of residential care without reference to any of these services. Additionally, the levels of residential care are distinguished within the InterQual Criteria by the frequency of therapy provided: a “residential treatment center” needs provide therapy only three times per week, whereas subacute psychiatric care must include at least five therapy sessions per week. Patricia received seven therapy sessions a week, in the form of five group, one individual, and one family therapy session.
In light of the evidence that Patricia indeed received subacute care at Island View, this court finds Blue Cross’s decision to determine coverage for the services provided based on the InterQual Criteria for subacute care to be entirely appropriate.
Based on the foregoing, this court reviews Blue Cross’s decision under the arbitrary and capricious standard.
B. Substantial Evidence
“The scope of review under the ‘arbitrary and capricious’ standard is narrow and a court is not to substitute its judgment for that of the [administrator].” Review is deferential, and the administrator’s decision must be upheld as long as “it is reasoned and supported by substantial evidence.” “Evidence is substantial if it is reasonably sufficient to support a conclusion, and the existence of contrary evidence does not, in itself, make the administrator’s decision arbitrary.” The only issue for the court is whether the administrator’s denial of benefits is irrational, with any doubts resolved in favor of the administrator. Viewed in light of this deferential standard, this court finds that substantial evidence supports Blue Cross’s decision to deny Plaintiffs reimbursement for Patricia’s residential treatment at Island View.
The Plan clearly covers only treatments that are “medically necessary” and “[flurnished in the least intensive type of setting required.” During the review process, three licensed physicians conducted separate reviews of Plaintiffs’ case on behalf of Blue Cross and determined that the subacute treatment provided to Patricia was not medically necessary. This determination was then confirmed by an independent external review commissioned by OPP and a second external review commissioned by a Blue Cross physician reviewer.
Plaintiffs argue that the observations and treatment recommendations from Patricia’s treating physicians at Second Nature and Island View are entitled to greater weight than the opinions of the physician reviewers whose decisions were based solely on review of medical records. In support of this argument Plaintiffs rely on a line of case law from other districts, which suggests that when mental health is at issue an opinion based on personal examination is inherently more reliable than an opinion based on a cold record.
In Island View Residential Treatment Center v. Bluecross and Blueshield of Massachusetts, the court rejected an identical argument and found that neither Supreme Court nor First Circuit precedent recognizes an exception, in the context of ERISA cases, to the general rule that the opinions of treating and reviewing physicians receive equal weight. Further, the line of cases offered to suggest that the opinions of treating physicians are entitled to more weight (notably, the same line of cases offered here) involves the determination of whether a claimant is disabled. In other words, the parties to those cases disputed the claimant’s diagnosis, which is not at issue in an ERISA denial of benefits action.
This court does not disagree that a diagnosis provided by a treating physician is likely to be more reliable than one provided by a reviewing physician. In contrast, however, the process of reviewing a claim for benefits does not rely on the nuances that can be observed through personal examination of the participant. Rather, it is confined to the process of applying a standardized and narrowly defined list of qualifying criteria to the participant’s particular set of symptoms, as documented by treating physicians in the participant’s medical records, to determine whether a participant qualifies for coverage for certain type of treatment under the Plan. Such a mechanical process would seem to be no more or less reliable when conducted by a reviewing physician than when conducted by a treating physician.
Blue Cross cannot arbitrarily discredit the contrary opinion of Patricia’s treating physicians, but neither must Blue Cross give any special weight to a treating physician’s opinion, or even explain why his opinion was not given as much weight as that of the reviewing physicians. As such, the existence of five separate medical opinions supporting Blue Cross’s decision substantially justifies Blue Cross’s denial of benefits, and the contrary conclusions drawn by Patricia’s treating psychologists at Second Nature and Island View are not enough to render the decision irrational.
Plaintiffs have not seriously called into question the reliability of the medical opinions of the reviewing physicians. Plaintiffs argue that the Maximus reviewers opinion lacks credibility because his license to practice was temporarily suspended twenty-nine years ago. This argument carries little weight, however, since his license was reinstated without restrictions in 1983 and he has been practicing and teaching in the field of psychiatry since that time. Moreover, even disregarding the Maximus reviewer’s opinion, Blue Cross’s denial of benefits is still supported by four additional medical opinions, including a second external reviewer, the independence of which has also not been questioned.
The physician reviewers utilized the InterQual Initial Review Criteria to determine whether subacute residential treatment was medically necessary for Patricia. Those criteria provide that some form of residential treatment is necessary only if the participant exhibits certain symptoms or behaviors, labeled Clinical Indications, within the week prior to admission to the residential care facility. These symptoms or behaviors must be in the form of (1) chronic or persistent danger to self or others, as evidenced by such things as self-mutilation or unmanageable aggressive behavior, (2) persistent violation of court orders, or (3) habitual substance abuse, accompanied by increasing anxiety, depressed mood, mania, or psychotic symptoms.
The reviewing doctors each concluded independently that Patricia did not exhibit any of the requisite clinical indications within the week before admission. When Patricia was discharged from Second Nature immediately prior to admission at Island View, her condition was reported to be stable. Second Nature medical staff repeatedly indicated that Patricia was not homicidal, suicidal, or a danger to herself or others. Similarly, at her admission to Island View, the admission record indicated that Patricia did not suffer any hallucinations or homicidal or suicidal ideation. Patricia herself reported upon admission that she had not recently experienced hallucinations, delusions, suicidal ideation, or destructive behavior.
Though Patricia had engaged in some self-mutilation, aggressive behaviors, and substance abuse in the past, there is no indication from any source that she had displayed such behaviors within the week prior to admission as required by the InterQual Criteria. In short, the medical personnel at both Second Nature and Island View and Patricia herself specifically ruled out the very symptoms that would have qualified Patricia’s treatment as “medically necessary”.
Moreover, the InterQual Initial Review Criteria require that the participant have been discharged or transferred from a psychiatric hospital within twenty-four hours prior to admission to an inpatient subacute treatment facility. In this case, Patricia entered Island View immediately upon leaving Second Nature, which was neither a hospital nor a subacute treatment center. Accordingly, even if the reviewers had determined that Patricia met the Clinical Indications criteria, they would have nonetheless been required to find that Patricia did not satisfy the InterQual Initial Review Criteria for admission to a subacute psychiatric treatment facility such as Island View.
Based on the foregoing, this court cannot conclude that Blue Cross’s decision to deny coverage for Patricia’s treatment at Island View was irrational.
IV. Conclusion
For the foregoing reasons, Defendant’s Motion for Summary Judgment [# 50] is ALLOWED and Plaintiffs Motion for Summary Judgment [# 57] is DENIED.
AN ORDER HAS ISSUED.
ORDER
For the reasons set forth in the accompanying memorandum, Defendant’s Motion for Summary Judgment [# 50] is ALLOWED and Plaintiffs’ Motion for Summary Judgment [# 57] is DENIED. This case is DISMISSED.
IT IS SO ORDERED.
. 29 U.S.C. § 1001, et. seq.
. All facts presented are drawn from the Administrative Record [hereinafter "AR”], as that is the only factual record this court is permitted to review. Orndorf v. Paul Revere Life Ins. Co., 404 F.3d 510, 518 (1st Cir.2005).
.AR 68.
. AR 111.
. AR 114. See also AR 178 (“denies she is currently feeling suicidal .... has never attempted suicide”).
. AR 160, 195 ("Level of Risk: None = no suicidal ideation.”).
. AR 182, 183.
. AR 196, 516.
. AR 36-37.
. AR 42-45.
. AR 14-15, 25.
. AR 14-15.
. AR 2.
. AR 4, 8.
. AR43E.
. AR 285-86.
. AR 62.
. AR 305.
. Decl. of Joseph Halpern in Support of Def.'s Mem. Mot. Summ. Judg., Ex. C, Naughton Dep., Ex. 2, 735-46.
. Decl. of Joseph Halpern in Support of Def.’s Mem. Mot. Summ. Judg., Ex. C, Naughton Dep., 43-44.
. Id. at 35-39.
. Decl. of Joseph Halpern in Support of Def.’s Mem. Mot. Summ. Judg., Ex. C, Naughton Dep., Ex. 3, 764.
. Orndorf, 404 F.3d at 518.
. Leahy v. Raytheon Co., 315 F.3d 11, 18 (1st Cir.2002).
. Orndorf, 404 F.3d at 517.
. 489 U.S. 101, 109 S.Ct. 948, 103 L.Ed.2d 80 (1989).
. Id. at 115, 109 S.Ct. 948.
. Id.
. Id.
. Id. (internal quotations omitted).
. Leahy, 315 F.3d at 15.
. AR at 2.
. Id.
. See Rodriguez-Abreu v. Chase Manhattan Bank, N.A., 986 F.2d 580, 584 (1st Cir.1993) (finding that an ERISA plan must comply with technical requirements relating to the delegation of discretionary authority to qualify for a deferential standard of review).
. AR at 14-15.
. See Smith v. Blue Cross Blue Shield of Massachusetts, Inc., 597 F.Supp.2d 214, 219 (D.Mass.2009).
. 554 U.S. 105, 128 S.Ct. 2343, 2346, 171 L.Ed.2d 299 (2008).
. Id. at 2351.
. Id.
. Denmark v. Liberty Life Assurance Co. of Boston, 566 F.3d 1, 9 (1st Cir.2009) (citing Glenn, 128 S.Ct. at 2351).
. Wright v. R.R. Donnelley & Sons Co. Group Benefits Plan, 402 F.3d 67, 74 (1st Cir.2005).
. Id.
. AR 62.
. See Smith, 597 F.Supp.2d at 220 (quoting Metropolitan Life Insurance, Co. v. Glenn, 554 U.S. 105, 128 S.Ct. 2343, 2351, 171 L.Ed.2d 299 (2008)).
. See, Pl.'s Mem. Supp. Summ. Judg., Ex. A, Division of Insurance Regulatory Information Bulletin 2003-11.
. Id.
. See AR 42-45 (describing the inpatient services for which Blue Cross provides coverage).
. See, e.g., M.G.L. c. 176B § 4; 211 CMR 52.06(4), 52.96(7), 53.13(8).
. See Pl.’s Mem. Summ. Judg., Ex. A, Horn Dep., 71-73.
. See, Pl.’s Mem. Summ. Judg., Aff. of Brian King, Ex. C., InterQual Res., 7.
. See Pl.’s Statement of Material Facts, ¶ 21 (citing AR 82-273).
. Id. at 8.
. Id.
. AR 91.
. Motor Vehicle Mfrs. Ass'n of U.S., Inc. v. State Farm Mut. Auto. Ins. Co., 463 U.S. 29, 43, 103 S.Ct. 2856, 77 L.Ed.2d 443 (1983).
. Gannon v. Metro. Life Ins. Co., 360 F.3d 211, 213 (1st Cir.2004)
. Id.
. Liston v. Unum Corp. Officer Severance Plan, 330 F.3d 19, 24 (1st Cir.2003).
. AR 14-15.
. See, e.g., Westphal v. Eastman Kodak Co., 2006 WL 1720380, 2006 U.S. Dist. LEXIS 41494 (W.D.N.Y.2006).
. See Island View, 2007 WL 4589335, at *23-24, 2007 U.S. District LEXIS 94901, at *76 (citing Nord, 538 U.S. at 834, 123 S.Ct. 1965; Gannon v. Metropolitan Life. Ins. Co., 360 F.3d 211, 214 (1st Cir.2004)).
. Id.
. See Smith, 597 F.Supp.2d at 219 (citing Black & Decker Disability Plan v. Nord, 538 U.S. 822, 834, 123 S.Ct. 1965, 155 L.Ed.2d 1034 (2003) (reasoning that “if a consultant engaged by a plan may have an 'incentive' to make a finding of ‘not disabled,' so a treating physician, in a close case, may favor a finding of 'disabled'")); Island View Residential Treatment Center v. Bluecross and Blueshield
of Massachusetts, Inc., 2007 WL 4589335, at *24-25, 2007 U.S. District LEXIS 94901, at *74 (D.Mass.2007).
. See, e.g., AR 111, 657.
. AR 285-86.
|
Male Majungasaurus
The male Majungasaurus was only featured in Last Killers.
He feasted on a carcass that the Majungasaurus family had been banqueting on before. When he roared at a Majungasaurus hatchling, the female Majungasaurus went crazy. The male backed down and ate the carcass from the other side, when the female struck again and killed the male. The Majungasaurus family then cannibalised on the dead male.
Trivia:
|
User blog comment:Doue/Steak of the devil/@comment-28241556-20131021132033
Unfortunately, you can't edit until the Halloween to prove that you are indeed the devil.
|
package manageme.logic.commands.module;
import static manageme.logic.commands.CommandTestUtil.assertCommandFailure;
import static manageme.logic.commands.CommandTestUtil.assertCommandSuccess;
import static manageme.testutil.TypicalIndexes.INDEX_FIRST;
import static manageme.testutil.TypicalIndexes.INDEX_SECOND;
import static manageme.testutil.TypicalManageMe.getTypicalManageMe;
import static org.junit.jupiter.api.Assertions.assertFalse;
import static org.junit.jupiter.api.Assertions.assertTrue;
import org.junit.jupiter.api.Test;
import manageme.commons.core.Messages;
import manageme.commons.core.index.Index;
import manageme.logic.commands.CommandResult;
import manageme.model.Model;
import manageme.model.ModelManager;
import manageme.model.UserPrefs;
import manageme.model.module.Module;
/**
* Contains integration tests (interaction with the Model) and unit tests for
* {@code ReadModuleCommand}.
*/
public class ReadModuleCommandTest {
private Model model = new ModelManager(getTypicalManageMe(), new UserPrefs());
@Test
public void execute_validIndexUnfilteredList_success() {
Module moduleToRead = model.getFilteredModuleList().get(INDEX_FIRST.getZeroBased());
ReadModuleCommand readModuleCommand = new ReadModuleCommand(INDEX_FIRST);
CommandResult expectedCommandResult = new CommandResult(readModuleCommand.MESSAGE_SUCCESS, false, false, true);
ModelManager expectedModel = new ModelManager(model.getManageMe(), new UserPrefs());
expectedModel.setReadModule(moduleToRead);
assertCommandSuccess(readModuleCommand, model, expectedCommandResult, expectedModel);
}
@Test
public void execute_invalidIndexUnfilteredList_throwsCommandException() {
Index outOfBoundIndex = Index.fromOneBased(model.getFilteredModuleList().size() + 1);
ReadModuleCommand readModuleCommand = new ReadModuleCommand(outOfBoundIndex);
assertCommandFailure(readModuleCommand, model, Messages.MESSAGE_INVALID_MODULE_DISPLAYED_INDEX);
}
@Test
public void equals() {
ReadModuleCommand readModuleFirstCommand = new ReadModuleCommand(INDEX_FIRST);
ReadModuleCommand readModuleSecondCommand = new ReadModuleCommand(INDEX_SECOND);
// same object -> returns true
assertTrue(readModuleFirstCommand.equals(readModuleFirstCommand));
// same values -> returns true
ReadModuleCommand deleteFirstCommandCopy = new ReadModuleCommand(INDEX_FIRST);
assertTrue(readModuleFirstCommand.equals(deleteFirstCommandCopy));
// different types -> returns false
assertFalse(readModuleFirstCommand.equals(1));
// null -> returns false
assertFalse(readModuleFirstCommand.equals(null));
// different module -> returns false
assertFalse(readModuleFirstCommand.equals(readModuleSecondCommand));
}
}
|
Recurrence following Resection of Intraductal Papillary Mucinous Neoplasms: A Systematic Review to Guide Surveillance
Patients who undergo resection for non-invasive IPMN are at risk for long-term recurrence. Further evidence is needed to identify evidence-based surveillance strategies based on the risk of recurrence. We performed a systematic review of the current literature regarding recurrence patterns following resection of non-invasive IPMN to summarize evidence-based recommendations for surveillance. Among the 61 studies reviewed, a total of 8779 patients underwent resection for non-invasive IPMN. The pooled overall median follow-up time was 49.5 months (IQR: 38.5–57.7) and ranged between 14.1 months and 114 months. The overall median recurrence rate for patients with resected non-invasive IPMN was 8.8% (IQR: 5.0, 15.6) and ranged from 0% to 27.6%. Among the 33 studies reporting the time to recurrence, the overall median time to recurrence was 24 months (IQR: 17, 46). Existing literature on recurrence rates and post-resection surveillance strategies for patients with resected non-invasive IPMN varies greatly. Patients with resected non-invasive IPMN appear to be at risk for long-term recurrence and should undergo routine surveillance.
Background
Pancreatic Intraductal Papillary Mucinous Neoplasms (IPMN) are a type of premalignant cystic neoplasm that develops within the pancreatic duct.The incidence of IPMN has been increasing in recent years, likely due to an increase in the use of crosssectional imaging for other causes [1].This has led to some authors to classify IPMNs as part of a larger group of "Pancreatic Incidentalomas" [2].As a premalignant lesion, IPMN can be detected across a range of different stages of the neoplastic spectrum, ranging from low-grade dysplasia to invasive carcinoma.
While modern techniques to diagnose IPMN have improved in recent years, riskstratifying the malignant potential of these lesions remains challenging.Several consensusbased guidelines exist to help guide the management of these complex cystic neoplasms [2,3].As the overwhelming majority of IPMN have a benign course and morbidity of pancreatic resection remains high, risk-based surveillance constitutes the mainstay of management.Despite this, there remains a lack of accurate pre-operative staging for IPMNs, as nearly onehalf of patients who undergo resection for IPMNs harbor only low-grade dysplasia [2,3].For patients with IPMN that harbor "worrisome" or "high-risk stigmata" for malignancy, surgical resection remains the primary treatment.
For patients who undergo surgical resection for IPMN, the optimal frequency and type of post-resection surveillance remains unclear.Previous studies hypothesized IPMN as a "field defect", suggesting that the entire pancreatic gland remains at risk of developing recurrent IPMN or invasive carcinoma even after complete surgical resection of the index IMPN [4].Recurrent disease necessitating repeat surgical resection has been reported to be as high as 62% during long-term (10-year) follow-up [4].For patients found to have invasive carcinoma after resection of IPMN, post-resection surveillance strategies are based on established rates and patterns of recurrences.Yet, there is significant heterogeneity in consensus recommendations for surveillance for patients found to have either no, lowgrade, or high-grade dysplasia.For example, the American Gastroenterological Association (AGA) recommends against routine surveillance after the resection of IPMN without invasive malignancy or high-grade dysplasia, whereas European guidelines recommend that all patients with IPMN should undergo lifetime surveillance after surgery [5].Whether the degree of dysplasia, or other clinicopathologic features, should influence these strategies remains unknown.As a result, surveillance strategies are highly variable in practice largely determined by individual practice patterns.
In the context of conflicting data and disparate consensus-based recommendations, we aimed to systematically review the current literature regarding recurrence patterns following resection of non-invasive IPMN to summarize evidence-based recommendations for surveillance.
Literature Search Strategy
We conducted a comprehensive search strategy in the MEDLINE database for studies published between January 2000 through January 2022.The following keywords and Medical Subject Headings were included in our search: "IPMN" or "Intraductal Papillary Mucinous Neoplasm" and "follow-up" or "surveillance" or "recurrence" or "progression".The references of relevant articles were also reviewed to identify additional eligible publications.The methodology utilized the standards of the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA).This systematic review was not registered.
Design and Study Selection
Two researchers (AS, VT) independently reviewed all potentially eligible studies for inclusion in the review.The titles and abstracts of the identified studies were screened.When deemed necessary, full-texts of relevant articles were retrieved and carefully assessed against the eligibility criteria.Studies were eligible for inclusion if they reported on the recurrence or surveillance patterns among patients who underwent resection for initially non-invasive IPMN.The exclusion criteria were as follows: (1) case studies, (2) studies including patients with other cystic neoplasms that were not IPMN, (3) studies lacking data about recurrence/progression rates, (4) reports that examined patients who had unconfirmed IPMN or did not undergo surgical resection as the primary treatment, and (5) non-empirical studies such as conference abstracts that did not proceed to publication in peer-reviewed journals.Only studies available in English were considered eligible.
Data Extraction
Data regarding type of study, type of IPMN, type of surgical resection, follow-up time, frequency and type of surveillance, and recurrence/progression rates were collected from each paper.When multiple studies analyzed the same population (i.e., series from the same hospital), data were extracted from the larger study or the study with longer follow-up time.
To identify such studies, we assessed each study's setting (name of hospital, university affiliation, and location) and time period, as well as each study's investigators.
Statistical Analysis
Summary statistics were reported as total and percentage for categorical variables and as median values and interquartile ranges unless stated otherwise for continuous variables.The results were not pooled into a meta-analysis due to the variation and substantial heterogeneity among the included studies.Two reviewers (AS, VT) compiled the data for data synthesis and analysis.
Literature Search and Study Selection
A total of 1867 studies were identified using the MEDLINE database (Figure 1).After evaluation, 905 were selected for further review after excluding 962 studies that were not related to the study topic.A further 762 publications were excluded as these studies focused primarily on surveillance without data on surgical resection, were case studies, had patients with presumed or non-confirmed IPMN, or did not include data on IPMN recurrence.Moreover, 77 studies were excluded as these articles were either published before the year 2000, focused on other cystic neoplasms with less than 10 cases of IPMN, or had median follow-up time shorter than 3 months.This screening process yielded 61 studies that were included in our review for analysis (Figure 1) .Among the 61 studies included, 44 were retrospective in nature (72.1%) and the remaining 17 (27.9%)were prospective.
from each paper.When multiple studies analyzed the same population (i.e., series from the same hospital), data were extracted from the larger study or the study with longer follow-up time.To identify such studies, we assessed each study's setting (name of hospital, university affiliation, and location) and time period, as well as each study's investigators.
Statistical Analysis
Summary statistics were reported as total and percentage for categorical variables and as median values and interquartile ranges unless stated otherwise for continuous variables.The results were not pooled into a meta-analysis due to the variation and substantial heterogeneity among the included studies.Two reviewers (AS, VT) compiled the data for data synthesis and analysis.
Literature Search and Study Selection
A total of 1867 studies were identified using the MEDLINE database (Figure 1).After evaluation, 905 were selected for further review after excluding 962 studies that were not related to the study topic.A further 762 publications were excluded as these studies focused primarily on surveillance without data on surgical resection, were case studies, had patients with presumed or non-confirmed IPMN, or did not include data on IPMN recurrence.Moreover, 77 studies were excluded as these articles were either published before the year 2000, focused on other cystic neoplasms with less than 10 cases of IPMN, or had median follow-up time shorter than 3 months.This screening process yielded 61 studies that were included in our review for analysis (Figure 1) .Among the 61 studies included, 44 were retrospective in nature (72.1%) and the remaining 17 (27.9%)were prospective.
Baseline Characteristics
Overall, a total of 9733 patients with clinical, radiological, or pathological diagnosis of IPMN were included; 8779 patients underwent resection for non-invasive disease (Table
Baseline Characteristics
Overall, a total of 9733 patients with clinical, radiological, or pathological diagnosis of IPMN were included; 8779 patients underwent resection for non-invasive disease (Table 1).20 studies (32.8%) were published between 2000-2009, including patient data from 1979-2006.41 studies (67.2%) were published in 2010 or later, including patient data from 1987-2020.Among the 61 studies included, sample sizes ranged from as few as 15 patients to the largest retrospective cohort study that included 827 patients [57].Most studies included patients with branch duct, main duct, and mixed-type IPMN (n = 39), whereas 4 studies (6.6%) included patients with only main duct IPMN; 5 studies included patients with only branch duct IPMN (8.2%), and 1 study (1.6%) included patients with only mixed-type IPMN.The remaining 12 studies (19.7%) included various combinations of two IPMN types (main and branch duct or main and mixed-type).
Patterns of Post-Resection Surveillance
The pooled overall median follow-up time for patients with resected non-invasive IPMN was 49.5 months (IQR: 38.5-57.7).Median follow-up times ranged between 14.1 months and 114 months.Of the 61 studies included in this review, 30 reported details on the intensity of post-resection surveillance for patients with non-invasive IPMN (Table 2).The most commonly reported frequency of post-resection surveillance was every 6 months (n = 10, 33%), followed by every 6 to 12 months (n = 6, 20%), every 3 to 6 months (n = 6, 20%), and yearly (n = 3, 10%) (Figure 2).Two studies had more specific post-resection surveillance schedules such as every 3 months for the first year, every 6 months for the second year, and yearly thereafter [63] or more intense surveillance after 2 years depending on tumor invasiveness [31].One study by Yamaguchi et al. reported 3-month post-resection surveillance for the first 2 years followed by every 6 months after.Kwon et al. reported post-resection surveillance schedules of 1, 3, and 6 months for the first year, then yearly afterwards.Forty-two studies reported the imaging modalities used for post-resection surveillance.The most common modality used was a combination of computed tomography (CT) and magnetic resonance imaging (MRI) (n = 15, 35.7%).This was followed by a combination of CT/MRI and ultrasound (US) imaging (either endoscopic or abdominal) (n = 13, 31.0%),CT imaging alone (n = 10, 23.8%), or a combination of CT and US (n = 2, 4.8%).Several studies reported alternative imaging modalities including positron emission tomography (PET) scan (n = 1, 2.4%), magnetic resonance cholangiopancreatography (n = 5, 11.9%), or endoscopic resonance cholangiopancreatography imaging (n = 2, 4.8%).Three studies (7.1%) reported using blood tumor markers as a means of surveillance after surgical resection.
Recurrence Rates and Patterns
The definition of "recurrence" was not explicitly defined in the majority of studies.However, for studies that define define recurrence, it was identified as a new IPMN or cancer in the remnant gland following resection.The overall median recurrence rate for patients with resected non-invasive IPMN was 8.8% (IQR: 5.0, 15.6).Reported recurrence rates ranged from 0% to 27.6%.Among the 33 studies reporting the time to recurrence, the overall median time to recurrence was 24 months (IQR: 17, 46) (Table 3).Among papers reporting mean or average time to recurrence, the overall mean time to recurrence was 40.8 months (SD, 29.4).Of the 61 studies included in this study, only 8 studies reported recurrence rates with location of recurrence.Among a total of 1380 patients from these 8 studies, 130 (9.4%) patients had a recurrence of a non-invasive IPMN recurrence, 63 (4.6%) patients developed PDAC, and 5 (0.4%) patients developed metastatic PDAC disease.Six reported disease-free survival (DFS) at 1-year.The overall 1-year DFS was 95.1% (IQR: 90.0, 97.8).5-year DFS was 88% (IQR: 82.5, 94) among twenty-seven studies and 10-year DFS was 78% (IQR: 72.8-86.1)among seven studies.Only 5 studies reported overall survival (OS) rates with a cumulative OS of 92% (IQR: 81, 92) at 5 years.
Discussion
Patients who undergo resection for non-invasive IPMN remain at risk for developing recurrent IPMN and/or PDAC [4].To our knowledge, this is the largest systematic review of recurrence rates and post-resection surveillance for patients who have undergone resection for non-invasive IPMN.With advances in imaging technology in recent years, and the increased incidence of IPMN, the current study is important to help guide long-term management for patients with non-invasive IPMN.In the current study, recurrence rates varied greatly and ranged from 0% to 27.6%.Furthermore, the reporting of recurrence rates was non-uniform across studies.These data have important implications that can help guide and standardize post-resection surveillance schedules as well as standardize the reporting of future studies related to long-term outcomes among patients with resected non-invasive IPMN.
In the current study, the pooled median recurrence rate was 8.8% (IQR, 5.0, 15.6) with a median time to recurrence of 24 months (IQR, for all patients who underwent resection for non-invasive IPMN.These findings are in line with previously reported recurrence rates ranging between 1% and 20% [27,65,67].The definition of recurrence may even, in fact, vary across studies, as some investigators may not consider a new IPMN as a true "recurrence", but rather as a de facto new lesion within the remnant pancreas and introduce bias into the findings [68].Despite this lack of a clear definition, previous studies have indicated that patients are at risk of recurrence even beyond 10 years post-resection [4].The current median follow-up time in the current study was only 49.5 months; therefore, the incidence of recurrence may have been under-represented as recurrences likely occurred beyond this time period.There are several proposed factors that may increase the risk of post-resection recurrence and help guide post-resection surveillance patterns such as IPMN with low-or high-grade dysplasia, a margin-positive resection, certain genetic mutations (i.e., SMAD4, TP53 etc.), and having a family history of PDAC [2].Despite the likelihood of recurrence, it does appear that salvage treatment may be possible as long-term overall survival remains high at 92% at 5 years.Furthermore, it is important to note that recurrence rates in the included studies reported recurrences of IPMN as well as PDAC.However, the reported recurrence rates of invasive PDAC after resection of non-invasive IPMN were less than 1% among the included studies.
There are numerous consensus-based guidelines that offer recommendations for the management of post-resection surveillance for patients with non-invasive IPMN [2,3,[69][70][71].However, these guidelines are largely based off low-quality evidence and consensus statements and vary greatly in their type and frequency of surveillance schedules.For instance, guidelines from the American College of Radiology do not comment on any type of postresection surveillance whereas the Fukuoka guidelines recommend lifetime cross-sectional imaging surveillance until patients are no longer surgical candidates [2,72].In the current systematic review, there was significant variation in the frequency of post-resection surveillance utilized.Furthermore, the type of surveillance also varied greatly.For instance, most studies reported using CT or MRI, however several studies utilized ultrasonography and endoscopic ultrasonography for surveillance.
Based on the pooled recurrence rates and patterns found in the current study, we recommend cross-sectional imaging every 6-12 months for all patients with resected IPMN.Future research should focus on identifying biomarkers and other features that allow for tailored risk-based surveillance.Similarly, based on the likelihood of recurrence, as well as the possibility of long-term recurrence, we recommend lifelong post-resection surveillance, as long as the patient remains a surgical candidate.Novel treatment strategies for IPMN such as chemotherapeutic and thermal ablation argue further in favor of lifelong follow-up regardless of the ability to undergo pancreatic resection.
There are several limitations of this systematic review largely due to the quality of evidence and heterogeneity of the studies included.The retrospective nature of most of the studies included introduces potential selection bias.Moreover, details regarding follow-up frequencies, recurrence rates, and median or average time to recurrence were missing from numerous studies and highlights the need for more standardized reporting of IPMN outcomes.Additionally, several studies did not stratify according to non-invasive or invasive disease and thus were unable to be included in the current review.Due to these limitations, we did not pool results of the included studies statistically, preventing us from carrying out a meta-analysis.These limitations highlight the need for future prospective trials to generate sufficient high-quality evidence to guide practice for these patients.
Conclusions
In conclusion, existing literature on recurrence rates and post-resection surveillance strategies for patients with resected non-invasive IPMN varies greatly.Patients with resected non-invasive IPMN appear to be at risk for long-term recurrence and should undergo routine surveillance.Future work should focus on creating evidence-based standardized recommendations to guide patient surveillance.
Figure 1 .
Figure 1.Flow chart of literature search and study selection.
Figure 1 .
Figure 1.Flow chart of literature search and study selection.
Figure 2 .
Figure 2. Frequencies and patterns of post-resection surveillance strategies.
Figure 2 .
Figure 2. Frequencies and patterns of post-resection surveillance strategies.
Table 3 .
Recurrence data following resection for IPMN among included studies.
|
The majority’s analysis on this point is, roughly, that none of the plaintiffs challenged the use of the funds as those uses are reflected in this record, therefore we need not consider those uses. But, accepting the majority’s premise that plaintiffs could have challenged those uses, does their failure to do so mean that we can ignore those uses for judging whether or not the program exacts a tax? I think not; the majority’s answer does not meet the challenge because there is nothing in the law that says that plaintiffs must have raised such challenges before we are required to consider the use of the money in deciding the question before us. There is a disconnect in the majority’s analysis. And I note that while perhaps such individual challenges to expenditures could have been made each time the money was spent, it would make no practical or legal sense to piecemeal the litigation as opposed to challenging the entire program as a tax.
Health and Safety Code section 39712 in pertinent part provides:
“(b) Moneys shall be used to facilitate the achievement of reductions of greenhouse gas emissions in this state . . . and, where applicable and to the extent feasible:
“(1) Maximize economic, environmental, and public health benefits to the state.
“(2) Foster job creation by promoting in-state greenhouse gas emissions reduction projects carried out by California workers and businesses.
“(3) Complement efforts to improve air quality.
“(4) Direct investment toward the most disadvantaged communities and households in the state.
“(5) Provide opportunities for businesses, public agencies, Native American tribes in the state, nonprofits, and other community institutions to participate in and benefit from statewide efforts to reduce greenhouse gas emissions.
“(6) Lessen the impacts and effects of climate change on the state’s communities, economy, and environment.
“(c) Moneys appropriated from the fund may be allocated, consistent with subdivision (a), for the purpose of reducing greenhouse gas emissions in this state through investments that may include, but are not limited to, any of the following:
“(1) Funding to reduce greenhouse gas emissions through energy efficiency, clean and renewable energy generation, distributed renewable energy generation, transmission and storage, and other related actions, including, but not limited to, at public universities, state and local public buildings, and industrial and manufacturing facilities.
“(2) Funding to reduce greenhouse gas emissions through the development of state-of-the-art systems to move goods and freight, advanced technology vehicles and vehicle infrastructure, advanced biofuels, and low-carbon and efficient public transportation.
“(3) Funding to reduce greenhouse gas emissions associated with water use and supply, land and natural resource conservation and management, forestry, and sustainable agriculture.
“(4) Funding to reduce greenhouse gas emissions through strategic planning and development of sustainable infrastructure projects, including, but not limited to, transportation and housing.
“(5) Funding to reduce greenhouse gas emissions through increased in-state diversion of municipal solid waste from disposal through waste reduction, diversion, and reuse.
“(6) Funding to reduce greenhouse gas emissions through investments in programs implemented by local and regional agencies, local and regional collaboratives, Native American tribes in the state, and nonprofit organizations coordinating with local governments.
‘“(7) Funding research, development, and deployment of innovative technologies, measures, and practices related to programs and projects funded pursuant to this chapter.”
And, Health and Safety Code section 39719 provides:
‘“(a) The Legislature shall appropriate the annual proceeds of the fund for the purpose of reducing greenhouse gas emissions in this state in accordance with the requirements of Section 39712.
‘“(b) To carry out a portion of the requirements of subdivision (a), annual proceeds are continuously appropriated for the following:
‘“(1) Beginning in the 2015-16 fiscal year, and notwithstanding Section 13340 of the Government Code, 35 percent of annual proceeds are continuously appropriated, without regard to fiscal years, for transit, affordable housing, and sustainable communities programs as following:
‘“(A) Ten percent of the annual proceeds of the fund is hereby continuously appropriated to the Transportation Agency for the Transit and Intercity Rail Capital Program created by Part 2 (commencing with Section 75220) of Division 44 of the Public Resources Code.
‘“(B) Five percent of the annual proceeds of the fund is hereby continuously appropriated to the Low Carbon Transit Operations Program created by Part 3 (commencing with Section 75230) of Division 44 of the Public Resources Code. Funds shall be allocated by the Controller, according to requirements of the program, and pursuant to the distribution formula in subdivision (b) or (c) of Section 99312 of, and Sections 99313 and 99314 of, the Public Utilities Code.
‘“(C) Twenty percent of the annual proceeds of the fund is hereby continuously appropriated to the Strategic Growth Council for the Affordable Housing and Sustainable Communities Program created by Part 1 (commencing with Section 75200) of Division 44 of the Public Resources Code. Of the amount appropriated in this subparagraph, no less than 10 percent of the annual proceeds, shall be expended for affordable housing, consistent with the provisions of that program.
“(2) Beginning in the 2015-16 fiscal year, notwithstanding Section 13340 of the Government Code, 25 percent of the annual proceeds of the fund is hereby continuously appropriated to the High-Speed Rail Authority for the following components of the initial operating segment and Phase I Blended System as described in the 2012 business plan adopted pursuant to Section 185033 of the Public Utilities Code:
“(A) Acquisition and construction costs of the project.
“(B) Environmental review and design costs of the project.
“(C) Other capital costs of the project.
“(D) Repayment of any loans made to the authority to fund the project.
“(c) In determining the amount of annual proceeds of the fund for purposes of the calculation in subdivision (b), the funds subject to Section 39719.1 shall not be included.”
Health and Safety Code section 39713 provides:
“(a) The investment plan developed and submitted to the Legislature pursuant to Section 39716 shall allocate a minimum of 25 percent of the available moneys in the fund to projects located within the boundaries of, and benefiting individuals living in, communities described in Section 39711.
“(b) The investment plan shall allocate a minimum of 5 percent of the available moneys in the fund to projects that benefit low-income households or to projects located within the boundaries of, and benefiting individuals living in, low-income communities located anywhere in the state.
“(c) The investment plan shall allocate a minimum of 5 percent of the available moneys in the fund either to projects that benefit low-income households that are outside of, but within a 1/2 mile of, communities described in Section 39711, or to projects located within the boundaries of, and benefiting individuals living in, low-income communities that are outside of, but within a 1/2 mile of, communities described in Section 39711.
“(d) For purposes of this subdivision, the following definitions shall apply:
“(1) ‘Low-income households’ are those with household incomes at or below 80 percent of the statewide median income or with household incomes at or below the threshold designated as low income by the Department of Housing and Community Development’s list of state income limits adopted pursuant to Section 50093.
“(2) ‘Low-income communities’ are census tracts with median household incomes at or below 80 percent of the statewide median income or with median household incomes at or below the threshold designated as low income by the Department of Housing and Community Development’s list of state income limits adopted pursuant to Section 50093.
“(e) Moneys allocated pursuant to one subdivision of this section shall not count toward the minimum requirements of any other subdivision of this section.”
Health and Safety Code section 39711 referenced in Health and Safety Code section 39713 quoted above provides in relevant part:
“(a) The California Environmental Protection Agency shall identify disadvantaged communities for investment opportunities related to this chapter. These communities shall be identified based on geographic, socioeconomic, public health, and environmental hazard criteria, and may include, but are not limited to, either of the following:
“(1) Areas disproportionately affected by environmental pollution and other hazards that can lead to negative public health effects, exposure, or environmental degradation.
“(2) Areas with concentrations of people that are of low income, high unemployment, low levels of homeownership, high rent burden, sensitive populations, or low levels of educational attainment.”
Item 3900-011-3228 of the Budget Act of 2013 (Stats. 2013, ch. 20, § 2, Item 3900-011-3228) provides that the State Controller will, upon the order of the Director of Finance, transfer $500 million from the Greenhouse Gas Reduction Fund to the General Fund as a loan.
Health and Safety Code section 39719.1 provides:
“(a) Of the amount loaned from the fund to the General Fund pursuant to Item 3900-011-3228 of Section 2.00 of the Budget Act of 2013, four hundred million dollars ($400,000,000) shall be available to the High-Speed Rail Authority pursuant to subdivision (b).
“(b) The portion of the loan from the fund to the General Fund described in subdivision (a) shall be repaid to the fund as necessary based on the financial needs of the high-speed rail project. Beginning in the 2015-16 fiscal year, and in order to carry out the goals of the fund in accordance with the requirements of Section 39712, the amounts of all the loan repayments, notwithstanding Section 13340 of the Government Code, are continuously appropriated from the fund to the High-Speed Rail Authority for the following components of the initial operating segment and Phase I Blended System as described in the 2012 business plan adopted pursuant to Section 185033 of the Public Utilities Code:
“(1) Acquisition and construction costs of the project.
“(2) Environmental review and design costs of the project.
“(3) Other capital costs of the project.
“(4) Repayment of any loans made to the authority to fund the project.”
Thus, the revenues generated by the auctions can be used by the state for, at least:
(1) funding to maximize economic, environmental and public health benefits to the state;
(2) funding to foster job creation by promoting in-state greenhouse gas emissions projects;
(3) funding to improve air quality;
(4) funding to direct investment in disadvantaged communities;
(5) funding to provide opportunities for businesses, public agencies, Native American tribes and others to participate in and enjoy the benefits of the reduction of greenhouse gases;
(6) funding to lessen the impacts of climate change on the state’s communities, economy and environment;
(7) funding to promote energy efficiency, renewable energy generation, distributed renewable energy generation, transmission and storage and other related actions at, among other places universities, state and local public buildings, and industrial and manufacturing abilities;
(8) funding to develop state-of-the-art systems to move goods and freight, advanced technology vehicles and vehicle infrastructure, advance biofuels, and low-carbon transportation;
(9) funding to reduce greenhouse gas emissions associated with water use and supply, land and natural resource conservation and management, forestry, and sustainable agriculture;
(10) funding strategic planning and development of sustainable infrastructure projects including transportation and housing;
(11) funding for in-state diversion of municipal solid waste through waste reduction, diversion, and reuse;
(12) funding to lower emissions through investments in programs implemented by local and regional agencies and others coordinating with local governments;
(13) funding for research, development, and deployment of innovative technologies, measures and practices;
(14) a continuous appropriation of 10 percent of the proceeds from the auction fund for the transit and intercity rail;
(15) a continuous appropriation of 5 percent for low-carbon transit programs;
(16) a continuous appropriation of 20 percent for the affordable housing and sustainable communities program; and
(17) a continuous appropriation of 25 percent to high-speed rail.
To the obvious broad use of the auction revenues, and in order to avoid having to consider the effect of the use of the proceeds on the question before us, respondents argue that the uses of the proceeds are merely advancing the intent of the program, that is, to reduce greenhouse gases and are, therefore, used more narrowly than general revenue funds.
Asked during oral argument what the expenditures on affordable housing had to do with emissions, respondents said the affordable housing was to be built near places of employment and transportation hubs to encourage public transportation and reduce greenhouse gas emissions accordingly. Following that line of argument would probably allow the proceeds to be spent on education on the theory that a better educated populace on the question of greenhouse gas emissions would be more likely to seek to reduce those emissions in the future.
Respondents’ argument conflates funding of the costs of administering the auction program with funding of the goals of cap and trade.
And here is the magic, the sleight of hand, of respondents’ argument. Since an argument can be, and has been, made that nearly all human activity (and, apparently, some animal activity) increases greenhouse gases, voila, auction funds can be used to address nearly any human activity without being considered a tax that generates general revenue, thus avoiding the prohibitions of Proposition 13, so long as the use of the funds has any tenuous connection to the reduction of greenhouse gases, connections that can always be found if one reaches far enough.
Howard Jarvis Taxpayers Assn. v. County of Orange (2003) 110 Cal.App.4th 1375 [2 Cal.Rptr.3d 514] (Howard Jarvis) is instructive. There, the City of Huntington Beach amended its city charter effective July 1978 (1) to mandate the city’s participation in a retirement system, (2) gave the city council discretion to establish reasonable compensation and fringe benefits as appropriate and (3) established an excise tax on real property to fund the retirement program.
After that, and after the passage of Proposition 13, the city added to those city retirement benefits and collected increased excises tax to fund those additional benefits. A taxpayer brought suit contending the excise tax, to the extent it funded additional retirement benefits granted after July 1978, violated Proposition 13.
The city argued there was no violation because the 1978 city charter language gave the city a right to levy the excess tax for virtually anything so long as the costs the excess tax funded related to city employee retirement benefits “including ‘giv[ing] a house ... to every employee as they retire . . . [¶] . . . .’ ” (Howard Jarvis, supra, 110 Cal.App.4th at p. 1383.)
The court disagreed and observed that the city’s argument would eviscerate Proposition 13 adding: “Under City’s interpretation, it would have virtually unfettered power to spend whatever sum of money and levy excess taxes to obtain the revenue, as long as the expenditure was designated ‘retirement.’ This was one of the very things Proposition 13 was enacted to combat.” (.Howard Jarvis, supra, 110 Cal.App.4th at p. 1384.)
So too here. The state’s argument gives it “virtually unfettered” power to spend whatever money the auction program raises so long as the purpose of the money is to a theoretical reduction of greenhouse gases.
Despite the practically unlimited use of the auction program’s revenues for state projects, the state seeks to end-run the provisions of Proposition 13 by labeling the wide and varied uses of that revenue as uses that address (not necessarily reduce), however tangentially, greenhouse gas emissions. The majority’s “decoupling” of the question of the use of the revenues generated by the auction program is, to say the least, unconvincing.
IV
The Auction Program as a Tax
It needs to be noted that the auction program revenues are not necessary to the funding of the cap-and-trade program in general or the auction program in particular.
Health and Safety Code section 38597 says: “The [State Air Resources Board] may adopt by regulation, after a public workshop, a schedule of fees to be paid by the sources of greenhouse gas emissions regulated pursuant to this division, consistent with Section 57001. The revenues collected pursuant to this section, shall be deposited into the Air Pollution Control Fund and are available upon appropriation, by the Legislature, for purposes of carrying out this division.”
Pursuant to the statutory authority granted by Health and Safety Code section 38597, the State Air Resources Board adopted California Code of Regulations, title 17, section 95200 (Cal. Code of Regs., tit. 17, §§ 95200, 95203), which provides: “The purpose of this subarticle is to collect fees to be used to carry out the California Global Warming Solutions Act of 2006 (Stats. 2006; Ch. 488; Health and Safety Code sections 38500 et seq.), as provided in Health and Safety Code section 38597.”
The State Air Resources Board also adopted California Code of Regulations, title 17, section 95203 which further provides:
“(a) Total Required Revenue (TRR).
“(1) The Required Revenue (RR) shall be the total amount of funds necessary to recover the costs of implementation of AB 32 program expenditures for each fiscal year, based on the number of personnel positions, including salaries and benefits and all other costs, as approved in the California Budget Act for that fiscal year.
“(2) The RR shall also include any amount required to be expended by ARB in defense of this subarticle in court.
“(3) If there is any excess or shortfall in the actual revenue collected for any fiscal year, such excess or shortfall shall be carried over to the next year’s calculation of the Total Revenue Requirement. If ARB does not expend or encumber the full amount authorized by the California Legislature for any fiscal year, the amount not expended or encumbered in that fiscal year shall be carried over and deducted from the next year’s calculation of the Total Revenue Required.
“(4) The annual Total Revenue Requirement is equal to the annual RR adjusted for the previous fiscal year’s excess or shortfall amount, as provided in subsection (a)(4).” (Cal. Code of Regs., tit. 17, § 95203, subd. (a), italics omitted.)
It would thus appear that auction proceeds are not intended, or, more importantly needed, to pay for the costs of implementation of Assembly Bill No. 32 (2005-2006 Reg. Sess.).
The only reasonable conclusion one can reach is that the auction proceeds are intended to, and do, generate general revenue to the State of California. It is apparent that by respondent’s express acknowledgement, this revenue may be used for any program that, arguably, might reduce greenhouse gases. But, as noted above, the effort to reduce greenhouse gases essentially encompasses all aspects of human activity and thus the use of the auction revenues by the state is virtually unlimited. Thus, the purchase of auction credits which, on this record, are imposed on Morning Star and businesses similarly situated, creates revenue to pay for a nearly unlimited variety of public services. (See, County of Fresno v. Malmstrom, supra, 94 Cal.App.3d at p. 983 [‘“Taxes are raised for the general revenue ... to pay for a variety of public services”].) This is a tax increase on businesses knowingly structured to avoid the provisions of Proposition 13.
Accepting the argument that there is social value to the cap-and-trade program, questions of the social value of any given law are the province of the Legislature and the Governor. It is the province of the courts to decide questions of law and the constitutionality of the laws and to do so based solely on the law regardless of the social value of the challenged legislation.
My colleagues and I have worked diligently on what is obviously a complex and difficult appeal. They, in good faith, have reached a conclusion different than mine. I simply cannot agree with their analysis or their result.
Given that the auction program is, for Morning Star and businesses that are similarly situated, compulsory if they are to remain in business in California and that the auction program creates, in actual effect, general revenue, I can only conclude that the program is a tax in “something else” clothing and that the auction program, not having been passed by a two-thirds vote in the Legislature, violates Proposition 13.
I would reverse the judgment.
The petitions of all appellants for review by the Supreme Court were denied June 28, 2017, S241948. Cantil-Sakauye, C. J., did not participate therein.
Further undesignated statutory references are to the Health and Safety Code.
Although regulations state that the allowances confer no property rights (Cal. Code Regs., tit. 17, §§ 95802, subd. (a)(299), 95820, subd. (c)), the trial court correctly found they are valuable commodities, a point we explain below (see pt. IIC.4., post).
We grant all pending requests for judicial notice, except as to items A and B of the Board’s supplemental request, jointly opposed by plaintiffs, as those items consist of federal documents neither presented to the trial court (see Brosterhous v. State Bar (1995) 12 Cal.4th 315, 325-326 [48 Cal.Rptr.2d 87, 906 P.2d 1242]) nor considered by the Board during the rulemaking process; nor are they properly responsive to our supplemental briefing order.
Intervener National Association of Manufacturers (NAM) correctly points out that a Board regulation cannot restrain the Legislature, nor can one Legislature bind the hands of a future one (see In re Collie (1952) 38 Cal.2d 396, 398 [240 P.2d 275]), therefore another Legislature might attempt to change current limits on the use of auction proceeds.
See Statutes 2012, chapter 39, section 25; Statutes 2012, chapter 807; Statutes 2012, chapter 830; and Statutes 2012, chapter 21, section 15.11 (California’s Budget Act of 2012). Contrary to Morning Star Packing Company’s repeated assertions, under the Budget Act of 2012, the $500 million diversion could not be used for general revenue purposes, but instead was made “available to support the regulatory purposes of’ the Act. (See Stats. 2012, ch. 21, § 15.11.)
The other parties to Morning Star’s petition are Dalton Trucking, Inc.; California Construction Trucking Association; Merit Oil Company; Ron Cinquini Farming; Construction Industry Air Quality Coalition; Robinson Enterprises, Inc.; Loggers Association of Northern California, Inc.; Norman R. “Skip” Brown; Joanne Browne; Robert McClernon; and the National Tax Limitation Committee.
We have received substantial amicus curiae briefing as follows: (1) The California Taxpayers Association; (2) the California Manufacturers and Technology Association (CMTA); and (3) the National Federation of Independent Business Small Business Legal Center, Owner-Operated Independent Drivers Association, Inc., and Associated California Loggers (NFIB), on behalf of plaintiffs; and (4) Dr. Dallas Burtraw and 16 other economics and public policy scholars, assisted by students from the University of California, Berkeley School of Law Environmental Law Practice Project (Burtraw); and (5) The Nature Conservancy, assisted, inter alia, by students from the UCLA School of Law Frank G. Wells Environmental Law Clinic, on behalf of the Board and EDF. In response to a supplemental briefing order, we received an amicus curiae brief by the International Emissions Trading Association (IETA), in part representing offset credit developers and major power producers including Pacific Gas & Electric Co., the Sacramento Municipal Utility District, and Southern California Edison Co.; IETA’s brief supports the Board’s regulations as against the Proposition 13 challenge.
The fact the Legislative Analyst opined that an allowance auction was not necessary to meet the Act’s goal is not dispositive. It is the Board’s opinion that counts, and even if an auction were not strictly necessary, the Board could find it was more effective and therefore reasonably necessary, a finding well within its legal purview.
The Board followed eight other commands in crafting regulations, including to “minimize leakage” (§ 38562, subd. (b)(8)), which is a reduction of in-state emissions “offset by an increase . . . outside the state.” (§ 38505, subd. (j).) Leakage includes businesses choosing to leave California rather than comply with the regulations. The regulations classify industrial sectors by risk of leakage, and adjust the amount of free allowances accordingly. (See Cal. Code Regs., tit. 17, § 958700
Although we have granted CalChamber’s unopposed request for judicial notice, tendering dictionary definitions of “distribution,” we find no serious ambiguity in the term as used herein. (Cf. Miller Brewing Co. v. Department of Alcoholic Beverage Control (1988) 204 Cal.App.3d 5, 12-15 [250 Cal.Rptr. 845] [finding ambiguity in “distribution” as used in the context of liquor marketing, and giving it the broadest meaning]; California Mfrs. Assn. v. Public Utilities Com. (1979) 24 Cal.3d 836, 843-848 [157 Cal.Rptr. 676, 598 P.2d 836] [similar holding].) We need not address whether distribution of allowances has a technical meaning as discussed in the briefs.
The Board was concerned windfalls could pass to entities contrary to the public good, as had happened “during the first phase of the European Union Emissions Trading Scheme. . . . Researchers emphasize that windfalls occurred because facilities were awarded free allowances and yet still passed opportunity costs through to consumers.” Amici curiae Burtraw and The Nature Conservancy emphasize and elaborate on these economic fairness concerns.
It is true, as CalChamber points out, that the Environmental Protection Agency guide also states existing programs allocated free allowances. That does not change the fact that the Legislature knew a choice would have to be made about whether or not to auction allowances, if the Board decided to adopt a cap-and-trade program.
NAM and CalChamber argue such a broad delegation—if intended—would be unlawful, but fail to provide coherent analysis or separately head the point, which therefore is forfeited. (See In re S.C. (2006) 138 Cal.App.4th 396, 408 [41 Cal.Rptr.3d 453].) Moreover, there was no abdication of legislative power, because the Act sets the boundaries of the Board’s discretion, and the policy goals. (See Hess Collection Winery v. Agricultural Labor Relations Bd. (2006) 140 Cal.App.4th 1584, 1604-1605 [45 Cal.Rptr.3d 609].)
We note that taxes must be levied by the legislative, not executive, branch. (See Hilliard, Law of Taxation (1875) § 1, p. 1; 1 Cooley, A Treatise on the Law of Taxation (3d ed. 1903) the Nature of the Power to Tax, p. 43 (Cooley).) Nor can the legislature delegate the power to tax to an administrative board, although a board can value property and collect taxes. (See 71 Am.Jur.2d (2001) State and Local Taxation, § 107, pp. 393-394.) Here, because we find no tax (see pt. II, post), we need not consider whether, if the revenue generated by the auction sales were a tax, it could have been created by the Board and then ratified by the Legislature. (See pt. IC.L, post.)
We have acknowledged that floor statements provide cognizable legislative history of a bill. (Kaufman & Broad Communities, Inc. v. Performance Plastering. Inc. (2005) 133 Cal.App.4th 26, 31-32 [34 Cal.Rptr.3d 520] (Kaufman).)
The Legislative Analyst’s opinion, in part, was that a “cap-and-trade program differs from a carbon tax in that the cost of emitting each ton of CO2e is not decided by the regulator. Rather, the cost is determined, in effect, by the emissions sources themselves through trading of emissions allowances.” (Legis. Analyst, Evaluating the Policy Trade-offs in ARB’s Cap-and-trade Program (Feb. 9, 2012) p. 6.)
In addition to the proposed signing statement, the enrolled bill report also includes three different draft veto messages. Their' inclusion shows that not all documents found in such reports are relevant or persuasive indications of legislative intent. (See Jones, supra, 2 Cal.5th at pp. 395-396; Kaufman, supra, 133 Cal.App.4th at pp. 40-42.)
According to a Legislative Analyst report in the record, “Traditionally, California has relied upon direct regulatory measures to achieve emissions reductions and meet other environmental goals. Such regulations, commonly referred to as command-and-control measures, typically require specific actions on the part of emissions sources to achieve the desired emissions reductions or other goals. ... In contrast, market-based mechanisms provide economic incentives to achieve emissions reductions, without specifying how emissions sources are to achieve those reductions.” (Legis. Analyst, Evaluating the Policy Trade-offs in ARB’s Cap-and-trade Program, supra, p. 5.) Either way, the Legislature could have specified how the proceeds would be used if the Board adopted a cap-and-trade program. But it could also conclude such a specification might tilt the scale in favor of such a program, rather than ensuring the Board—the agency with expertise in the subject matter—had maximum flexibility, within legislative parameters.
We note that the trial court found “a Senate Committee report on [Senate Bill No.] 31 reflects an understanding that [Assembly Bill No.] 32 already authorized auctions.”
Contrary to the Board’s evident view, the constitutional doubt canon is distinct from the constitutional avoidance doctrine, whereby it is often deemed prudent to address a statutory or other ground to avoid reaching a constitutional ground. (See, e.g.. People v. McKay (2002) 27 Cal.4th 601, 608, fn. 3 [117 Cal.Rptr.2d 236, 41 P.3d 59].)
Also contrary to CalChamber’s apparent view, nothing in Shaw v. People ex rel. Chiang (2009) 175 Cal.App.4th 577 [96 Cal.Rptr.3d 379] (Shaw) addresses ratification. Rather, the case involved legislative violation of spending strictures, an issue we address in part IIC.6., post.
We were not asked to decide whether an administrative or legislative attempt to extend the cap-and-trade rules promulgated under the Act beyond 2020 would be subject to Proposition 26’s terms, and do not purport to do so.
In contrast, as mentioned earlier. Proposition 26 “shifted to the state or local government the burden of demonstrating that any charge, levy or assessment is not a tax.” (Schmeer. supra. 213 Cal.App.4th at p. 13224
This provision was amended by Proposition 26, as discussed in part IC.2., ante.
Plaintiffs emphasize this last finding, arguing that it is possible to connect any human activity to GHG emissions, meaning there is no definable regulatory horizon. Our dissenting colleague appears to accept this view.
A point pressed by the Board and EDF, in defense of the trial court’s ruling, is that the Board had no puipose to generate revenue, and therefore any auction revenue is merely a “byproduct” of the regulations. They point out that Proposition 13 restricted changes “for the purpose of increasing revenues” (Cal. Const., art. XIII A, former §3) and contend revenue generation was not the purpose of the auction system. But the Board concedes it knew the auctions would generate revenue, and it adopted the regulations with such knowledge, therefore it intended to generate revenue, whether or not that was its prime motivation. (See People v. Colantuono (1994) 7 Cal.4th 206, 217-218 [26 Cal.Rptr.2d 908, 865 P.2d 704] [oblique intention; where the actor knows likely consequence, is not explicitly motivated to achieve it, yet still acts, the actor intends the consequence]; City of Madera v. Black (1919) 181 Cal. 306, 314 [184 P. 397] [“Persons, even when acting officially, are presumed to intend the necessary consequences of their acts”]; Evid. Code, § 665.) Therefore, as plaintiffs maintain, we cannot characterize billions of dollars of anticipated auction revenues as a fortuitous byproduct of the regulations.
The fact a declaration appears in the record and was not directly contravened does not necessarily establish the truth of its contents. A trial court is free to disbelieve evidence whether or not contradicted, if there is a rational basis for doing so. (See Foreman & Clark Corp. v. Fallon (1971) 3 Cal.3d 875, 890 [92 Cal.Rptr. 162, 479 P.2d 362]; Hicks v. Reis (1943) 21 Cal.2d 654, 659-660 [134 P.2d 788].) For example, the Rabo declaration in large part hinged on the claimed lack of awareness of feasible alternative technologies, but does not set forth what steps Morning Star took to educate itself. Nor did Morning Star include declarations from engineers or scientists that support its economist’s view that no feasible alternatives to currently used emissions control methods exist. But even if the Rabo declaration were wholly complete and unassailable, it would make no difference to the analysis of the legal question before us, as we explain post in this section.
After oral argument in this case, our Supreme Court granted review in an unrelated case, raising the following two issues: “(1) Can a statute be challenged on the ground that compliance with it is allegedly impossible? (2) If so, how is the trial court to make that determination?” (National Shooting Sports Foundation, Inc. v. State of California (2016) 6 Cal.App.5th 298 [210 Cal.Rptr.3d 867], review granted Mar. 22, 2017, S239397.) Those issues arguably speak to Morning Star’s act of submitting the Rabo declaration—material outside the normal administrative record—to the trial court. However, we express no view on the procedural propriety of such action herein.
Morning Star argues “for those who choose to remain in California, the state income tax does not somehow become ‘voluntary’ and not a tax. Merely because a company like Morning Star chooses to continue to do business in the state by purchasing allowances at auction does not make the auction payments any more ‘voluntary’ or any less of a tax.” This argument is unpersuasive, because Morning Star need not leave the state to avoid buying auction credits. Instead, like any other covered entity, it can modify its polluting behavior or obtain offset credits. Both of these options, admittedly, may be costly, but not necessarily any more so than if the Board had imposed a command-and-control cap on emissions. This seems to be another iteration of a point we reject. The fact that the auction system may result in costs does not make the auction system a tax.
Under the Act, the Board was to consider “direct emission reduction measures.” (§ 38561, subd. (b).) This is another term for command-and-control measures.
Contrary to the dissent’s view, we do indeed “recognize that this litigation is not between private parties, but between plaintiffs and the state.” (Dis. opn., post, at p. 660.) Our point is that private parlies (such as Morning Star) are holding a thing of value once they acquire the auction credits, regardless of how and from whom the credits were acquired.
Whether such a system would be deemed an impermissible burden on intrastate travel presents an entirely different question not relevant to this discussion, and not before us. (But see Tobe v. City of Santa Ana (1995) 9 Cal.4th 1069, 1100-1101 [40 Cal.Rptr.2d 402, 892 P.2d 1145]; Allen v. City of Sacramento (2015) 234 Cal.App.4th 41, 60 [183 Cal.Rptr.3d 654] [“Otherwise lawful ordinances that have an indirect or incidental impact on the right to travel and do not discriminate among classes of persons by penalizing the exercise of the right to travel are not constitutionally impermissible”].)
We do not disregard plaintiffs’ arguments regarding the propriety of the expenditures merely because plaintiffs have not specifically challenged those expenditures, as our dissenting colleague suggests. (Dis. opn., post, at pp. 661-662, 669.) Simply put, the expenditures are not relevant here.
|
Arrizz
Arrizz was a drow elf in the Moonsea.
History
Near Cormanthor, Arrizz met the moon elf scout Deriel Rethslane and the two fell in love.
Appearances
* Harried in Hillsfar
* Shackles of Blood
|
/* eslint-disable jsx-a11y/label-has-associated-control */
import React, { useEffect, useState } from "react";
import { useHistory } from "react-router-dom";
import API from "../utils/API";
import teams from "../utils/constants";
import "./selection.css";
function Selection() {
const [player1, setPlayer1] = useState(null);
const [player2, setPlayer2] = useState(null);
const history = useHistory();
const onChange = function (event) {
event.target.name === "player1" ? setPlayer1(event.target.value) : setPlayer2(event.target.value);
};
useEffect(async () => {
const { data } = await API.checkUser();
data ? history.push(`/play/${data._id}`) : history.push("/selection");
}, []);
const startGame = async (e) => {
e.preventDefault();
if (!(player1 && player2)) {
return;
}
API.createGame({ player1, player2 }).then((res) => {
history.push(`/play/${res.data}`);
});
};
return (
<div className="home tempCheck">
<h1 id="intro">Choose Your Teams</h1>
<div className="playSelect1">
<h2 id="playerone"> Player 1: <span id="teamName">{player1}</span></h2>
{teams.map((team) => (
<div key={`${team}One`}>
<input key={`${team}InputOne`} id={team} type="radio" value={team} name="player1" onChange={onChange} required />
<label key={`${team}LabelOne`} className={`playerDecks ${team}`} htmlFor={team} />
</div>
))}
</div>
<div className="playSelect2">
<h2 id="playertwo">Player 2: <span id="teamName">{player2}</span></h2>
{teams.map((team) => (
<div key={`${team}Two`}>
<input id={`player2 ${team}`} type="radio" value={team} name="player2" onChange={onChange} required />
<label className={`playerDecks ${team}`} htmlFor={`player2 ${team}`} />
</div>
))}
</div>
<button type="submit" id="playButton" onClick={startGame}>
<span>Start</span>
</button>
</div>
);
}
export default Selection;
|
//
// UserAPI.swift
//
// Generated by swagger-codegen
// https://github.com/swagger-api/swagger-codegen
//
import Alamofire
public class UserAPI: APIBase {
/**
Confirm a user registration with email verification token.
- parameter uid: (query)
- parameter token: (query)
- parameter redirect: (query) (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userConfirm(uid uid: String, token: String, redirect: String? = nil, completion: ((error: ErrorType?) -> Void)) {
userConfirmWithRequestBuilder(uid: uid, token: token, redirect: redirect).execute { (response, error) -> Void in
completion(error: error);
}
}
/**
Confirm a user registration with email verification token.
- GET /Users/confirm
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- parameter uid: (query)
- parameter token: (query)
- parameter redirect: (query) (optional)
- returns: RequestBuilder<Void>
*/
public class func userConfirmWithRequestBuilder(uid uid: String, token: String, redirect: String? = nil) -> RequestBuilder<Void> {
let path = "/Users/confirm"
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"uid": uid,
"token": token,
"redirect": redirect
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<Void>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Count instances of the model matched by where from the data source.
- parameter _where: (query) Criteria to match model instances (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userCount(_where _where: String? = nil, completion: ((data: TWInlineResponse200?, error: ErrorType?) -> Void)) {
userCountWithRequestBuilder(_where: _where).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Count instances of the model matched by where from the data source.
- GET /Users/count
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"count" : 1.3579000000000001069366817318950779736042022705078125
}}]
- parameter _where: (query) Criteria to match model instances (optional)
- returns: RequestBuilder<TWInlineResponse200>
*/
public class func userCountWithRequestBuilder(_where _where: String? = nil) -> RequestBuilder<TWInlineResponse200> {
let path = "/Users/count"
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"where": _where
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWInlineResponse200>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Create a new instance of the model and persist it into the data source.
- parameter data: (body) Model instance data (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userCreate(data data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userCreateWithRequestBuilder(data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Create a new instance of the model and persist it into the data source.
- POST /Users
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter data: (body) Model instance data (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userCreateWithRequestBuilder(data data: TWUser? = nil) -> RequestBuilder<TWUser> {
let path = "/Users"
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Create a change stream.
- parameter options: (query) (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userCreateChangeStreamGetUsersChangeStream(options options: String? = nil, completion: ((data: NSURL?, error: ErrorType?) -> Void)) {
userCreateChangeStreamGetUsersChangeStreamWithRequestBuilder(options: options).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Create a change stream.
- GET /Users/change-stream
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example=""}]
- parameter options: (query) (optional)
- returns: RequestBuilder<NSURL>
*/
public class func userCreateChangeStreamGetUsersChangeStreamWithRequestBuilder(options options: String? = nil) -> RequestBuilder<NSURL> {
let path = "/Users/change-stream"
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"options": options
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<NSURL>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Create a change stream.
- parameter options: (form) (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userCreateChangeStreamPostUsersChangeStream(options options: String? = nil, completion: ((data: NSURL?, error: ErrorType?) -> Void)) {
userCreateChangeStreamPostUsersChangeStreamWithRequestBuilder(options: options).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Create a change stream.
- POST /Users/change-stream
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example=""}]
- parameter options: (form) (optional)
- returns: RequestBuilder<NSURL>
*/
public class func userCreateChangeStreamPostUsersChangeStreamWithRequestBuilder(options options: String? = nil) -> RequestBuilder<NSURL> {
let path = "/Users/change-stream"
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"options": options
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<NSURL>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Delete a model instance by {{id}} from the data source.
- parameter id: (path) Model id
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userDeleteById(id id: String, completion: ((data: AnyObject?, error: ErrorType?) -> Void)) {
userDeleteByIdWithRequestBuilder(id: id).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Delete a model instance by {{id}} from the data source.
- DELETE /Users/{id}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example="{}"}]
- parameter id: (path) Model id
- returns: RequestBuilder<AnyObject>
*/
public class func userDeleteByIdWithRequestBuilder(id id: String) -> RequestBuilder<AnyObject> {
var path = "/Users/{id}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [:]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<AnyObject>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "DELETE", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Check whether a model instance exists in the data source.
- parameter id: (path) Model id
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userExistsGetUsersidExists(id id: String, completion: ((data: TWInlineResponse2002?, error: ErrorType?) -> Void)) {
userExistsGetUsersidExistsWithRequestBuilder(id: id).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Check whether a model instance exists in the data source.
- GET /Users/{id}/exists
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"exists" : true
}}]
- parameter id: (path) Model id
- returns: RequestBuilder<TWInlineResponse2002>
*/
public class func userExistsGetUsersidExistsWithRequestBuilder(id id: String) -> RequestBuilder<TWInlineResponse2002> {
var path = "/Users/{id}/exists"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [:]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWInlineResponse2002>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Check whether a model instance exists in the data source.
- parameter id: (path) Model id
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userExistsHeadUsersid(id id: String, completion: ((data: TWInlineResponse2002?, error: ErrorType?) -> Void)) {
userExistsHeadUsersidWithRequestBuilder(id: id).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Check whether a model instance exists in the data source.
- HEAD /Users/{id}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"exists" : true
}}]
- parameter id: (path) Model id
- returns: RequestBuilder<TWInlineResponse2002>
*/
public class func userExistsHeadUsersidWithRequestBuilder(id id: String) -> RequestBuilder<TWInlineResponse2002> {
var path = "/Users/{id}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [:]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWInlineResponse2002>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "HEAD", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Find all instances of the model matched by filter from the data source.
- parameter filter: (query) Filter defining fields, where, include, order, offset, and limit (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userFind(filter filter: String? = nil, completion: ((data: [TWUser]?, error: ErrorType?) -> Void)) {
userFindWithRequestBuilder(filter: filter).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Find all instances of the model matched by filter from the data source.
- GET /Users
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example=[ {
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
} ]}]
- parameter filter: (query) Filter defining fields, where, include, order, offset, and limit (optional)
- returns: RequestBuilder<[TWUser]>
*/
public class func userFindWithRequestBuilder(filter filter: String? = nil) -> RequestBuilder<[TWUser]> {
let path = "/Users"
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"filter": filter
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<[TWUser]>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Find a model instance by {{id}} from the data source.
- parameter id: (path) Model id
- parameter filter: (query) Filter defining fields and include (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userFindById(id id: String, filter: String? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userFindByIdWithRequestBuilder(id: id, filter: filter).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Find a model instance by {{id}} from the data source.
- GET /Users/{id}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter id: (path) Model id
- parameter filter: (query) Filter defining fields and include (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userFindByIdWithRequestBuilder(id id: String, filter: String? = nil) -> RequestBuilder<TWUser> {
var path = "/Users/{id}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"filter": filter
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Find first instance of the model matched by filter from the data source.
- parameter filter: (query) Filter defining fields, where, include, order, offset, and limit (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userFindOne(filter filter: String? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userFindOneWithRequestBuilder(filter: filter).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Find first instance of the model matched by filter from the data source.
- GET /Users/findOne
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter filter: (query) Filter defining fields, where, include, order, offset, and limit (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userFindOneWithRequestBuilder(filter filter: String? = nil) -> RequestBuilder<TWUser> {
let path = "/Users/findOne"
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"filter": filter
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Login a user with username/email and password.
- parameter credentials: (body)
- parameter include: (query) Related objects to include in the response. See the description of return value for more details. (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userLogin(credentials credentials: AnyObject, include: String? = nil, completion: ((data: AnyObject?, error: ErrorType?) -> Void)) {
userLoginWithRequestBuilder(credentials: credentials, include: include).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Login a user with username/email and password.
- POST /Users/login
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example="{}"}]
- parameter credentials: (body)
- parameter include: (query) Related objects to include in the response. See the description of return value for more details. (optional)
- returns: RequestBuilder<AnyObject>
*/
public class func userLoginWithRequestBuilder(credentials credentials: AnyObject, include: String? = nil) -> RequestBuilder<AnyObject> {
let path = "/Users/login"
let URLString = TweakApiAPI.basePath + path
let parameters = credentials.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<AnyObject>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Logout a user with access token.
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userLogout(completion: ((error: ErrorType?) -> Void)) {
userLogoutWithRequestBuilder().execute { (response, error) -> Void in
completion(error: error);
}
}
/**
Logout a user with access token.
- POST /Users/logout
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- returns: RequestBuilder<Void>
*/
public class func userLogoutWithRequestBuilder() -> RequestBuilder<Void> {
let path = "/Users/logout"
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [:]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<Void>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Counts accessTokens of User.
- parameter id: (path) User id
- parameter _where: (query) Criteria to match model instances (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeCountAccessTokens(id id: String, _where: String? = nil, completion: ((data: TWInlineResponse200?, error: ErrorType?) -> Void)) {
userPrototypeCountAccessTokensWithRequestBuilder(id: id, _where: _where).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Counts accessTokens of User.
- GET /Users/{id}/accessTokens/count
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"count" : 1.3579000000000001069366817318950779736042022705078125
}}]
- parameter id: (path) User id
- parameter _where: (query) Criteria to match model instances (optional)
- returns: RequestBuilder<TWInlineResponse200>
*/
public class func userPrototypeCountAccessTokensWithRequestBuilder(id id: String, _where: String? = nil) -> RequestBuilder<TWInlineResponse200> {
var path = "/Users/{id}/accessTokens/count"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"where": _where
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWInlineResponse200>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Creates a new instance in accessTokens of this model.
- parameter id: (path) User id
- parameter data: (body) (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeCreateAccessTokens(id id: String, data: TWAccessToken? = nil, completion: ((data: TWAccessToken?, error: ErrorType?) -> Void)) {
userPrototypeCreateAccessTokensWithRequestBuilder(id: id, data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Creates a new instance in accessTokens of this model.
- POST /Users/{id}/accessTokens
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"created" : "2000-01-23T04:56:07.000+00:00",
"id" : "aeiou",
"ttl" : 1.3579000000000001069366817318950779736042022705078125,
"userId" : 1.3579000000000001069366817318950779736042022705078125
}}]
- parameter id: (path) User id
- parameter data: (body) (optional)
- returns: RequestBuilder<TWAccessToken>
*/
public class func userPrototypeCreateAccessTokensWithRequestBuilder(id id: String, data: TWAccessToken? = nil) -> RequestBuilder<TWAccessToken> {
var path = "/Users/{id}/accessTokens"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWAccessToken>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Deletes all accessTokens of this model.
- parameter id: (path) User id
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeDeleteAccessTokens(id id: String, completion: ((error: ErrorType?) -> Void)) {
userPrototypeDeleteAccessTokensWithRequestBuilder(id: id).execute { (response, error) -> Void in
completion(error: error);
}
}
/**
Deletes all accessTokens of this model.
- DELETE /Users/{id}/accessTokens
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- parameter id: (path) User id
- returns: RequestBuilder<Void>
*/
public class func userPrototypeDeleteAccessTokensWithRequestBuilder(id id: String) -> RequestBuilder<Void> {
var path = "/Users/{id}/accessTokens"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [:]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<Void>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "DELETE", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Delete a related item by id for accessTokens.
- parameter id: (path) User id
- parameter fk: (path) Foreign key for accessTokens
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeDestroyByIdAccessTokens(id id: String, fk: String, completion: ((error: ErrorType?) -> Void)) {
userPrototypeDestroyByIdAccessTokensWithRequestBuilder(id: id, fk: fk).execute { (response, error) -> Void in
completion(error: error);
}
}
/**
Delete a related item by id for accessTokens.
- DELETE /Users/{id}/accessTokens/{fk}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- parameter id: (path) User id
- parameter fk: (path) Foreign key for accessTokens
- returns: RequestBuilder<Void>
*/
public class func userPrototypeDestroyByIdAccessTokensWithRequestBuilder(id id: String, fk: String) -> RequestBuilder<Void> {
var path = "/Users/{id}/accessTokens/{fk}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
path = path.stringByReplacingOccurrencesOfString("{fk}", withString: "\(fk)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [:]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<Void>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "DELETE", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Find a related item by id for accessTokens.
- parameter id: (path) User id
- parameter fk: (path) Foreign key for accessTokens
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeFindByIdAccessTokens(id id: String, fk: String, completion: ((data: TWAccessToken?, error: ErrorType?) -> Void)) {
userPrototypeFindByIdAccessTokensWithRequestBuilder(id: id, fk: fk).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Find a related item by id for accessTokens.
- GET /Users/{id}/accessTokens/{fk}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"created" : "2000-01-23T04:56:07.000+00:00",
"id" : "aeiou",
"ttl" : 1.3579000000000001069366817318950779736042022705078125,
"userId" : 1.3579000000000001069366817318950779736042022705078125
}}]
- parameter id: (path) User id
- parameter fk: (path) Foreign key for accessTokens
- returns: RequestBuilder<TWAccessToken>
*/
public class func userPrototypeFindByIdAccessTokensWithRequestBuilder(id id: String, fk: String) -> RequestBuilder<TWAccessToken> {
var path = "/Users/{id}/accessTokens/{fk}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
path = path.stringByReplacingOccurrencesOfString("{fk}", withString: "\(fk)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [:]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWAccessToken>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Queries accessTokens of User.
- parameter id: (path) User id
- parameter filter: (query) (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeGetAccessTokens(id id: String, filter: String? = nil, completion: ((data: [TWAccessToken]?, error: ErrorType?) -> Void)) {
userPrototypeGetAccessTokensWithRequestBuilder(id: id, filter: filter).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Queries accessTokens of User.
- GET /Users/{id}/accessTokens
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example=[ {
"created" : "2000-01-23T04:56:07.000+00:00",
"id" : "aeiou",
"ttl" : 1.3579000000000001069366817318950779736042022705078125,
"userId" : 1.3579000000000001069366817318950779736042022705078125
} ]}]
- parameter id: (path) User id
- parameter filter: (query) (optional)
- returns: RequestBuilder<[TWAccessToken]>
*/
public class func userPrototypeGetAccessTokensWithRequestBuilder(id id: String, filter: String? = nil) -> RequestBuilder<[TWAccessToken]> {
var path = "/Users/{id}/accessTokens"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let nillableParameters: [String:AnyObject?] = [
"filter": filter
]
let parameters = APIHelper.rejectNil(nillableParameters)
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<[TWAccessToken]>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "GET", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Patch attributes for a model instance and persist it into the data source.
- parameter id: (path) User id
- parameter data: (body) An object of model property name/value pairs (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeUpdateAttributesPatchUsersid(id id: String, data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userPrototypeUpdateAttributesPatchUsersidWithRequestBuilder(id: id, data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Patch attributes for a model instance and persist it into the data source.
- PATCH /Users/{id}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter id: (path) User id
- parameter data: (body) An object of model property name/value pairs (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userPrototypeUpdateAttributesPatchUsersidWithRequestBuilder(id id: String, data: TWUser? = nil) -> RequestBuilder<TWUser> {
var path = "/Users/{id}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "PATCH", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Patch attributes for a model instance and persist it into the data source.
- parameter id: (path) User id
- parameter data: (body) An object of model property name/value pairs (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeUpdateAttributesPutUsersid(id id: String, data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userPrototypeUpdateAttributesPutUsersidWithRequestBuilder(id: id, data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Patch attributes for a model instance and persist it into the data source.
- PUT /Users/{id}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter id: (path) User id
- parameter data: (body) An object of model property name/value pairs (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userPrototypeUpdateAttributesPutUsersidWithRequestBuilder(id id: String, data: TWUser? = nil) -> RequestBuilder<TWUser> {
var path = "/Users/{id}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "PUT", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Update a related item by id for accessTokens.
- parameter id: (path) User id
- parameter fk: (path) Foreign key for accessTokens
- parameter data: (body) (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userPrototypeUpdateByIdAccessTokens(id id: String, fk: String, data: TWAccessToken? = nil, completion: ((data: TWAccessToken?, error: ErrorType?) -> Void)) {
userPrototypeUpdateByIdAccessTokensWithRequestBuilder(id: id, fk: fk, data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Update a related item by id for accessTokens.
- PUT /Users/{id}/accessTokens/{fk}
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"created" : "2000-01-23T04:56:07.000+00:00",
"id" : "aeiou",
"ttl" : 1.3579000000000001069366817318950779736042022705078125,
"userId" : 1.3579000000000001069366817318950779736042022705078125
}}]
- parameter id: (path) User id
- parameter fk: (path) Foreign key for accessTokens
- parameter data: (body) (optional)
- returns: RequestBuilder<TWAccessToken>
*/
public class func userPrototypeUpdateByIdAccessTokensWithRequestBuilder(id id: String, fk: String, data: TWAccessToken? = nil) -> RequestBuilder<TWAccessToken> {
var path = "/Users/{id}/accessTokens/{fk}"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
path = path.stringByReplacingOccurrencesOfString("{fk}", withString: "\(fk)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWAccessToken>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "PUT", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Replace attributes for a model instance and persist it into the data source.
- parameter id: (path) Model id
- parameter data: (body) Model instance data (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userReplaceById(id id: String, data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userReplaceByIdWithRequestBuilder(id: id, data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Replace attributes for a model instance and persist it into the data source.
- POST /Users/{id}/replace
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter id: (path) Model id
- parameter data: (body) Model instance data (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userReplaceByIdWithRequestBuilder(id id: String, data: TWUser? = nil) -> RequestBuilder<TWUser> {
var path = "/Users/{id}/replace"
path = path.stringByReplacingOccurrencesOfString("{id}", withString: "\(id)", options: .LiteralSearch, range: nil)
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Replace an existing model instance or insert a new one into the data source.
- parameter data: (body) Model instance data (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userReplaceOrCreate(data data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userReplaceOrCreateWithRequestBuilder(data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Replace an existing model instance or insert a new one into the data source.
- POST /Users/replaceOrCreate
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter data: (body) Model instance data (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userReplaceOrCreateWithRequestBuilder(data data: TWUser? = nil) -> RequestBuilder<TWUser> {
let path = "/Users/replaceOrCreate"
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Reset password for a user with email.
- parameter options: (body)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userResetPassword(options options: AnyObject, completion: ((error: ErrorType?) -> Void)) {
userResetPasswordWithRequestBuilder(options: options).execute { (response, error) -> Void in
completion(error: error);
}
}
/**
Reset password for a user with email.
- POST /Users/reset
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- parameter options: (body)
- returns: RequestBuilder<Void>
*/
public class func userResetPasswordWithRequestBuilder(options options: AnyObject) -> RequestBuilder<Void> {
let path = "/Users/reset"
let URLString = TweakApiAPI.basePath + path
let parameters = options.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<Void>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Update instances of the model matched by {{where}} from the data source.
- parameter _where: (query) Criteria to match model instances (optional)
- parameter data: (body) An object of model property name/value pairs (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userUpdateAll(_where _where: String? = nil, data: TWUser? = nil, completion: ((data: TWInlineResponse2001?, error: ErrorType?) -> Void)) {
userUpdateAllWithRequestBuilder(_where: _where, data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Update instances of the model matched by {{where}} from the data source.
- POST /Users/update
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"count" : 1.3579000000000001069366817318950779736042022705078125
}}]
- parameter _where: (query) Criteria to match model instances (optional)
- parameter data: (body) An object of model property name/value pairs (optional)
- returns: RequestBuilder<TWInlineResponse2001>
*/
public class func userUpdateAllWithRequestBuilder(_where _where: String? = nil, data: TWUser? = nil) -> RequestBuilder<TWInlineResponse2001> {
let path = "/Users/update"
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWInlineResponse2001>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: false)
}
/**
Patch an existing model instance or insert a new one into the data source.
- parameter data: (body) Model instance data (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userUpsertPatchUsers(data data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userUpsertPatchUsersWithRequestBuilder(data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Patch an existing model instance or insert a new one into the data source.
- PATCH /Users
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter data: (body) Model instance data (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userUpsertPatchUsersWithRequestBuilder(data data: TWUser? = nil) -> RequestBuilder<TWUser> {
let path = "/Users"
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "PATCH", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Patch an existing model instance or insert a new one into the data source.
- parameter data: (body) Model instance data (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userUpsertPutUsers(data data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userUpsertPutUsersWithRequestBuilder(data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Patch an existing model instance or insert a new one into the data source.
- PUT /Users
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter data: (body) Model instance data (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userUpsertPutUsersWithRequestBuilder(data data: TWUser? = nil) -> RequestBuilder<TWUser> {
let path = "/Users"
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "PUT", URLString: URLString, parameters: convertedParameters, isBody: true)
}
/**
Update an existing model instance or insert a new one into the data source based on the where criteria.
- parameter _where: (query) Criteria to match model instances (optional)
- parameter data: (body) An object of model property name/value pairs (optional)
- parameter completion: completion handler to receive the data and the error objects
*/
public class func userUpsertWithWhere(_where _where: String? = nil, data: TWUser? = nil, completion: ((data: TWUser?, error: ErrorType?) -> Void)) {
userUpsertWithWhereWithRequestBuilder(_where: _where, data: data).execute { (response, error) -> Void in
completion(data: response?.body, error: error);
}
}
/**
Update an existing model instance or insert a new one into the data source based on the where criteria.
- POST /Users/upsertWithWhere
- API Key:
- type: apiKey access_token (QUERY)
- name: access_token
- examples: [{contentType=application/json, example={
"emailVerified" : true,
"lastUpdated" : "2000-01-23T04:56:07.000+00:00",
"credentials" : "{}",
"challenges" : "{}",
"created" : "2000-01-23T04:56:07.000+00:00",
"realm" : "aeiou",
"id" : 1.3579000000000001069366817318950779736042022705078125,
"email" : "aeiou",
"username" : "aeiou",
"status" : "aeiou"
}}]
- parameter _where: (query) Criteria to match model instances (optional)
- parameter data: (body) An object of model property name/value pairs (optional)
- returns: RequestBuilder<TWUser>
*/
public class func userUpsertWithWhereWithRequestBuilder(_where _where: String? = nil, data: TWUser? = nil) -> RequestBuilder<TWUser> {
let path = "/Users/upsertWithWhere"
let URLString = TweakApiAPI.basePath + path
let parameters = data?.encodeToJSON() as? [String:AnyObject]
let convertedParameters = APIHelper.convertBoolToString(parameters)
let requestBuilder: RequestBuilder<TWUser>.Type = TweakApiAPI.requestBuilderFactory.getBuilder()
return requestBuilder.init(method: "POST", URLString: URLString, parameters: convertedParameters, isBody: false)
}
}
|
How to create a custom setup wizard
I am trying to create a ADDIN SETUP PROJECT in VS 2022 for Revit. and I had some problems
I want to create a Custom Installation Wizard Where the following actions Should be included.
License Agreement (Like img)
Choose checkbox for version (Like img)
Example: if(cb2019 = true) => location for Directories "C/ProgramData/Revit/Addin/2019"
if(cb2020 = true) => location for Directories "C/ProgramData/Revit/Addin/2020"
The "visual studio installer" projects are easy to use, but are somewhat limited, and I'm not sure if it supports what you want to do. Wix is another installer framework that is very flexible, but is somewhat difficult to use.
|
Please answer the following question: Here's a logic test: Vicky tried to bend a rubber tube into a circle. She then tried to do the same thing with a glass tube. One of them bent into a circle and the other one broke. Which one did she successfully bend into a circle? (A) the rubber tube (B) the glass tube Choose the answer between "a glass tube" and "a rubber tube".
Answer:
a glass tube
|
# Data Structures (Arrays, Stacks, Queues, and Linked Lists)
**What is an array?**
An array is a data structure that manages a collection of items
## Demo
~~~
int[] array = new int[3];
array[0] = 5;
array[1] = 8;
~~~
**What is a stack?**
A data structure that manages data in a First In Last Out (FILO) or Last In First Out (LIFO) manner
Has 3 important methods: Push, Pop, Peek
**What is a stack used for?**
Processing data as it comes in, where the most recent item is processed next
Retry transfers that just failed
Depth First Search algorithm
Application management (application stack)
## Demo
~~~
Stack<string> stack = new Stack<string>();
stack.Push("A");
stack.Push("B");
stack.Pop();
stack.Push("C");
stack.Pop();
stack.Pop();
~~~
**What is a queue?**
A data structure that manages data in a First In First Out (FIFO) or Last In Last Out (LILO) manner
Has 3 important methods: Enqueue, Dequeue, Peek
**What is a queue used for?**
Processing data in the order it came in
Line (queue) at a store or amusement park
Breadth First Search algorithm
# Demo
~~~
Queue<string> queue = new Queue<string>();
queue.Enqueue("A");
queue.Enqueue("B");
queue.Dequeue();
queue.Enqueue("C");
queue.Dequeue();
queue.Dequeue();
~~~
**What is a linked list?**
A data structure that manages data by linking together nodes
There are two types of linked lists: (singly) linked list, doubly linked list
**What is a linked list used for?**
Managing data that needs to be traversed in steps, one at a time
# Demo
~~~
LinkedList<string> linkedList = new LinkedList<string>();
linkedList.AddLast(new LinkedListNode<string>("A"));
linkedList.AddLast(new LinkedListNode<string>("B"));
linkedList.AddLast(new LinkedListNode<string>("C"));
~~~
|
The Cliff Face (comic story)
is a Doctor Who Adventures comic strip published in 2012.
Summary
Named characters
* The Doctor
* Amy Pond
* Rory Williams
* Henrietta Fenner
Original print details
* Publication with page count and closing captions
* 1) DWA 277 (4 pages) DON’T MISS ANOTHER NEW ADVENTURE NEXT TIME!
* No reprints to date.
Continuity
Timeline
* This story is set before Bumble of Destruction
* This story is set after The Time Gallery
|
User:Adsellers/Sandbox FamilySearch Wiki:WikiProject New England Town Headers Part Two
Purpose
To Standardize the New England Town Pages
Contact
<EMAIL_ADDRESS>
Task Lists
This project is found in tab Part 41
* Connecticut Task List
* Maine Task List
* Massachusetts Task List
* New Hampshire Task List
* Rhode Island Task List
* Vermont Task List
Project Instructions
To update the Headers and Information in the New England Town pages, one section at a time
* This is an example of a finished Town for updated headers and information
* Monroe, Fairfield County, Connecticut Genealogy
* Bethel, Connecticut at Wikipedia
* Town of Bethel, CT at Bethel-ct.gov
Part One
* Copy and paste this Wiki Text code after the Descriptions Section
Populated Places
|
import SignatureV2 from "./structs/signature";
export declare type HexString<L extends number> = string;
export declare type Hash = HexString<32>;
export declare type Address = HexString<40>;
export declare type RsvSignature = [/*r: */ HexString<32>, /*s: */ HexString<32>, /*v: */ HexString<1>];
export declare type RpcSignature = HexString<65>;
export declare type Signature = RpcSignature | RsvSignature | SignatureV2;
export declare type SignStrategy = (...args: any[]) => Promise<Signature>;
export interface SignedEntity {
signature: Signature;
toABI(): any[];
}
|
DROP TABLE IF EXISTS books;
CREATE TABLE books (
id SERIAL PRIMARY KEY,
title VARCHAR (255),
author VARCHAR (255),
img VARCHAR (255),
description TEXT,
isbn VARCHAR(255),
bookshelf VARCHAR (255)
);
INSERT INTO books (title, author, img, description,isbn,bookshelf)
VALUES('A Cat in the Wings','Lydia Adamson','http://books.google.com/books/content?id=wfHFAg_3oY8C&printsec=frontcover&img=1&zoom=1&edge=curl&source=gbs_api','Available Digitally for the First Time Murder takes a bow at the ballet','9781101578896','not available');
INSERT INTO books (title, author, img, description,isbn,bookshelf)
VALUES('Dune','Frank Herbert','http://books.google.com/books/content?id=B1hSG45JCX4C&printsec=frontcover&img=1&zoom=5&edge=curl&source=gbs_api','Follows the adventures of Paul Atreides, the son of a betrayed duke given up for dead on a treacherous desert planet and adopted by its fierce, nomadic people, who help him unravel his most unexpected destiny.','9781101578896','fantacy');
|
Thread:Firefox20z/@comment-31595317-20191111011413/@comment-31595317-20191208220229
(the bad guys are obsessed with beautiful women, so he decides to break in disguised as one)
|
from argparse import ArgumentParser
from functools import partial
from os import path
from pkg_resources import resource_filename
from offswitch import __version__
from .destroy import destroy
config_join = partial(path.join, path.dirname(__file__), "config")
def _build_parser():
"""
CLI parser builder using builtin `argparse` module
:returns: instanceof ArgumentParser
:rtype: ```ArgumentParser```
"""
parser = ArgumentParser(description="Destroy compute nodes")
parser.add_argument(
"-s",
"--strategy",
help="strategy file [providers.sample.json]",
default=resource_filename("offswitch.config", "providers.sample.json"),
)
parser.add_argument(
"-p",
"--provider",
help="Only switch off this provider. Can be specified repetitively.",
action="append",
)
parser.add_argument(
"-d",
"--delete",
help="Only switch off this name. Can be specified repetitively.",
action="append",
)
parser.add_argument(
"--version", action="version", version="%(prog)s {}".format(__version__)
)
return parser
if __name__ == "__main__":
args = _build_parser().parse_args()
destroy(args.strategy, args.provider, args.delete)
|
Generic Collections in ArrayList
I'm trying to build on my introductory Java knowledge and I'm branching out into Data Structures.
I'm looking at the ArrayList and I'm not understanding the following:
List<String> myList = new ArrayList<String>();
I googled type parameter but I don't really understand why it's necessary and what it's doing (both for the call to the constructor and in initialising the variable); if someone could explain it to me in simple speak, that would be great.
Thanks
Google for "Java tutorial generics"
its giving you type safety so that get() returns a String not an Object. List is an interface that ArrayList implements which is what I think you are asking aka initialising.
http://docs.oracle.com/javase/tutorial/extra/generics/index.html
First of all, I would strongly suggest that you read the Java generics tutorial.
Secondly, to answer your question simply. By using a generic type like this you are forcing the compiler to use strong type checking on the code using this instance.
If you defined your list as:
List myList = new ArrayList();
You would be able to add objects of any type to it, such as:
myList.add(new Integer());
myList.add(new Long());
By declaring the list as:
List<String> myList = new ArrayList<String>();
You are telling the compiler that this list will only accept Strings, so:
myList.add(new Integer());
will throw a compile time error.
In Java 7 you can use the Diamond operator instead (think of it as inverse type inference, if that helps), so:
List<String> myList = new ArrayList<>();
It means that you can only add objects to this List that are of class String or sub-classes of String.
Generics are generally more useful with Interfaces than Concrete classes.
To understand this, you'll need to understand how generics work in java. In short words, the type allows the Generic ArrayList to cast each element to a type and return each object as type.
The Implementation looks something like this
public class ArrayList<T>{
public void add(T element)
public <T> get()
}
In your example, this allows you to use the array list with Strings
In the background objects still were objects but where castet for each read / write access.
So you have something like a typesafety ( which can be broken as you can read here).
This is an example of Generics, but for a while you can get away without knowing the gory details of Generics -- tutorials will show you how to write a class like ArrayList; for now you just need to know how to use it.
Prior to Generics, you would declare a List like this:
List l = new ArrayList();
... and a List contained a collection of objects. The Java runtime didn't care what kind of object you put in.
l.add(new Integer(3);
l.add("A String");
... and the Java runtime couldn't tell you what type the object you got out was, so you had to cast it:
String s = (String) l.get(1); // throws a ClassCastException if object is not a String
This meant that all kinds of programming errors that could be detected by the compiler, if only the language could express itself better, were only able to be caught at runtime.
So, instead, let's add something that says what the List contains:
List<String> l = new ArrayList<String>();
This means that you can only add() Strings to the list, and anything you get() from the list will be a String:
l.add(new Integer(1)); // compile error -- incompatible types
l.add("Hello"); // works
String s = l.get(0); // works, without casting
It works with polymorphism. So if Apple and Banana are subclasses of Fruit:
List<Fruit> fruitList = new ArrayList<Fruit>();
fruitList.add(new Apple());
fruitList.add(new Banana());
If you look at the JavaDoc for List, you'll see that it's documented as List<E> - where E is a placeholder for whatever type you plug in when you declare the variable.
The methods are documented in the same way: boolean add(E e), E get(int index), and so on.
Generics tell to compiler that ArrayList can contain only String objects.
The type parameter in your case String says the ArrayList can hold only String and no other types allowed. It also helps when you retrieve the value from the ArrayList you would be sure that the output is String and can directly assign to a String.
With this declaration you're just setting the data type of the ArrayList. In this way you ensure that the ArrayList is an array of strings
The main usage of generics is to provide type safety. If you do not use generics, objects will come out as a reference of type object. Before generics there was no way to declare the type of an arraylist,so its add() method took type object by default.
For simple eg. to understand generics is as follows
ArrayList<String> l=new ArrayList<String>();
l.add(null); // It will add type of string
Here, with generics you can now only put string objects in the ArrayList and the objects will come out as a reference of type string.
In short, with generics you can create type-safe collections where more problems are caught at compile time instead of run time
|
Freezing
If the heat stat drops to zero Zoey freezes to death.
The dialogue is as follows:
My entire body was trembling in the cold wind, and I had lost my senses in both hands and feet.
"It's so, so cold.... Mom, dad, everyone.... Where did you go....?
"I, I, I'm going.... to find you, so just.... wait a b-bit longer......"
I grit my teeth and huddled up hugging my legs, but the nasty cold kept digging into my body.
My heavy eyelids finally closed, and I fell into deep sleep one last time.
|
/* Copyright (c) 2015 David Hoskin <[email protected]> */
#include <X11/Xlib.h>
#include <X11/extensions/XTest.h>
#include <stdio.h>
/* Works fine for p9p acme, but grab inherently takes focus on every keypress. */
/* This breaks things like Firefox menus. */
/* Todo: hjkl? */
#define F1 67
#define F2 68
#define F3 69
#define F(k) (k-F1+1)
/* Todo: use XK_Pointer_Button1 etc, or at least XK_F1. */
int buttons[3];
void
key(XKeyEvent e)
{
/*printf("key f%d %s\n", F(e.keycode), e.type == KeyPress? "down": "up");*/
XTestFakeButtonEvent(e.display, F(e.keycode), e.type == KeyPress, 0);
return;
}
int
main(void)
{
Display *d;
Window root;
XEvent e;
int f;
int er;
d = XOpenDisplay(NULL);
if(d == NULL){
perror("could not open display");
return 1;
}
root = DefaultRootWindow(d);
for(f = F1; f <= F3; ++f)
XGrabKey(d, f, AnyModifier, root, 1, GrabModeAsync, GrabModeAsync);
while(!XNextEvent(d, &e)){
if(e.type == KeyPress || e.type == KeyRelease)
key(e.xkey);
else
printf("unknown event %d\n", e.type);
}
return 0;
}
|
WIP: Sphericart integration
This PR aims at integrating SpheriCart https://github.com/lab-cosmo/sphericart to p4ml. Todo list that I come up with but feel free to update edit. This also fixes a bug that the current real solid harmonics returns NaN when an (approximately) zero vector is given or does not evaluate.
[x] p4ml interface for real solid harmonics in SpheriCart
[ ] normalization of real solid harmonics in SpheriCart which compatible with current p4ml
If we want to retire the old backend entirely (though this sounds to me too ambitious):
[ ] make sure all the laplacian/derivative/pullback/pushforward of previous solid/spherical harmonics can be called exactly the same as before
[ ] check the normalization is correct for each basis, or provide an option normlization = :p4ml which recovers the previous normalization
[ ] and possibly evaluate the complex spherical harmonics via a transformation? This sounds something to be done in SpheriCart
[ ] update documentation, and maybe tag a minor version?
CC @zhanglw0521 @TSGut
If we want to retire the old interface entirely
What do you mean by "the old interface"? The interface should remain the same only the backend - i.e. the code that generates the basis will be sphericart?
I think all your points are very doable and should be doen.
If we want to retire the old interface entirely
What do you mean by "the old interface"? The interface should remain the same only the backend - i.e. the code that generates the basis will be sphericart?
Sorry that was a typo - yes I mean backend.
Something like this should give a correct scaling up to a sign. This comes from the Condon-Shortley Sign Convention. Is there a better way to fix this other than modifying the sign at the end of the output directly?
function generate_Flms(L::Integer; normalisation = :p4ml, T = Float64)
Flm = OffsetMatrix(zeros(L+1, L+1), (-1, -1))
for l = 0:L
Flm[l, 0] = sqrt(2)
for m = 1:l
Flm[l, m] = Flm[l, m-1] / sqrt((l+m) * (l+1-m))
end
end
return Flm
end
Are you saying that you need to rescale the Ylm output vector by a sign after the computation, and this cannot be done at the stage of precomputing the Flms?
Are you saying that you need to rescale the Ylm output vector by a sign after the computation, and this cannot be done at the stage of precomputing the Flms?
Yes exactly.
this is unfortunate. But do we really care about the sign convention?
@DexuanZhou -- what do you think? Can you also ask Huajie? (i can't find his github name right now)
@DexuanZhou -- what do you think? Can you also ask Huajie? (i can't find his github name right now)
Sorry I just saw this message. In our current simulation of Schrodinger equations, I think the sign convention is not a problem, we will be happy as long as it is a complete basis.
But I am not sure whether this could become an issue in future project. For example, when we consider some symmetry of the system and evaluate the Clebsch-Gordan coefficients?
Using it as a single basis function, I agree with Huajie that the sign convention shouldn't matter much. The only potential issue arises when we compare with chemical basis functions, where they might express one-body basis as f = a_1f_1+a_2f_2+a_3f_3. In such cases, we need to be very careful to ensure that the coefficients align properly; for instance, adjusting coefficients to -a1, a2, and a3 as needed.
That sound to me like we should try to recover the correct signs. I'll discuss with Jerry.
... on the other hand we can just fix the signs in the clebsch-gordans ...
this PR seems to have gone stale. What shall we do?
I remember there is a normalization to be fixed before merging, but for some reason (which I don't remember) this can only be done on Sphercart end.
So exactly what is needed at the Sphericart end?
I remember we didn't arrive at a conclusion but we decide to make a issue on that end to discuss it (which I forgot to). I just skim over the code again, it make sense to me just to scale the output in P4ML?
Let's discuss at our next meeting what we should do.
Please double-check whether #84 makes this PR obsolete and if you agree, then please close it.
|
Dickey v. Florida
John D. Buchanan, Jr., Tallahassee, Fla., for petitioner.
George R. Georgieff, Tallahassee, Fla., for respondent.
Mr. Chief Justice BURGER delivered the opinion of the Court.
|
Bearing inner ring with integral mounting means
ABSTRACT
An inner ring assembly for a bearing includes a bearing annular body disposable about the shaft and having a bearing inner race and a plurality of slotted openings defining a plurality of arcuate mounting tabs, the slotted openings each having a curved inner end and each tab including a substantial recess to reduce stress concentration. An annular locking collar is disposed about and clamps the mounting tabs against the outer surface of the shaft to retain the inner ring. The collar is retained on the ring body by a retainer projection(s) extending outwardly from the mounting tabs and engaging with the collar or a retainer member projecting inwardly from the collar and engaging with one of the mounting tabs. The collar has a gap and a flat outer surface section spaced from the gap to increase the dynamic balance and the flexibility of the collar.
BACKGROUND OF THE INVENTION
The present invention relates to bearings, and more particularly to bearing inner rings for rolling element bearings.
Rolling element bearings basically include an inner ring mounted on a shaft or inner member, an outer ring disposed within a housing or outer member, and a plurality of rolling elements disposed between androtatably coupling the inner and outer rings. In general, the inner ring is mounted on the shaft by an interference or press fit, which requires relatively precise machining of the shaft outer surface for proper installation. However, in applications where it is desired to avoid such shaft machining, for example to reduce costs, the inner ring may be installed on the shaft by an integral mounting means, i.e., a mounting mechanism provided with the bearing. Typically, such integral mounting means include mounting fingers or tabs formed on the bearing inner ring and a collar for clamping the fingers/tabs onto the shaft outer surface.
SUMMARY OF THE INVENTION
In one aspect, the present invention is an inner ring assembly for a bearing, the bearing rotatably coupling a shaft with an outer member,the shaft being rotatable about a central axis. The inner ring assembly comprises a bearing annular body disposable about the shaft and having a centerline, opposing first and second axial ends, an outercircumferential surface, and an annular groove extending radiallyinwardly from the outer surface and providing a bearing inner race. A plurality of slotted openings extend axially inwardly from the first axial end and are spaced circumferentially about the centerline so as to define a plurality of arcuate mounting tabs. Each mounting tab has an inner end integral with a remainder of the annular body and an opposing,free outer end. An annular locking collar is disposed about the plurality of mounting tabs and is configured to clamp the tabs against the outer surface of the shaft so as to retain the inner ring radiallyand axially with respect to the shaft central axis. The collar is retained on the ring annular body when the inner ring is separate fromthe shaft by a retainer projection extending radially outwardly from the outer end of one of the mounting tabs and engaging with the collar and/or a retainer member movably coupled with and projecting radiallyinwardly from the collar and engaging with one of the mounting tabs.
In another aspect, the present invention is again an inner ring assembly for a bearing, the bearing rotatably coupling a shaft with an outer member, the shaft being rotatable about a central axis. The inner ringassembly comprises an annular body disposable about the shaft and having a centerline, opposing first and second axial ends, an outercircumferential surface and an annular groove extending inwardly fromthe outer surface and providing a bearing inner race. A plurality of slotted openings extend axially inwardly from the first axial end andare spaced circumferentially about the centerline so as to define a plurality of arcuate mounting tabs. Each mounting tab has an inner end integral with a remainder of the annular body and an opposing, free outer end. A locking collar includes an annular body disposed about the plurality of mounting tabs, the annular body having an innercircumferential surface with an inside diameter, an outercircumferential surface and a gap defining first and second spaced apartcircumferential ends. A threaded rod extends through the first and second circumferential ends such that rotation of the rod in a first angular direction displaces the first and second ends generally toward each other to reduce the body inside diameter and compress the plurality of mounting tabs into engagement with the shaft. The body outercircumferential surface has a flat surface section with a center spaced about one hundred eighty degrees (180°) about the centerline from the gap so as to increase the dynamic balance of the collar about the shaft central axis.
In a further aspect, the present invention is once again an inner ringassembly for a bearing, the bearing rotatably coupling a shaft with anouter member, the shaft being rotatable about a central axis. The innerring assembly comprises an annular body disposable about the shaft and having a centerline, opposing first and second axial ends, an outercircumferential surface, an annular groove extending inwardly from the outer surface and providing a bearing inner race. A plurality of slotted openings extend axially inwardly from the first axial end and are spacedcircumferentially about the centerline so as to define a plurality ofarcuate mounting tabs, each slotted opening being partially bounded by a curved inner end surface. Each mounting tab has an inner axial end integral with a remainder of the annular body, a free, outer axial end and an outer circumferential surface. The outer circumferential surface of each tab has a radiused section at the tab inner end, a cylindrical section extending axially inwardly from the tab outer end and an angled section extending between the radiused surface section and the cylindrical surface section and defining a recess. Further, an annularlocking collar is disposed about the plurality of mounting tabs and is configured to clamp the tabs against the outer surface of the shaft soas to retain the inner ring radially and axially with respect to the shaft central axis.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
The foregoing summary, as well as the detailed description of the preferred embodiments of the present invention, will be better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings,which are diagrammatic, embodiments that are presently preferred. It should be understood, however, that the present invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:
FIG. 1 is a perspective view of a bearing including an inner ringassembly according to the present invention;
FIG. 2 is a broken-away, upper axial cross-sectional view of a bearing with the present inner ring assembly, shown installed on a shaft and within an outer member;
FIG. 3 is an enlarged, broken-away view of a portion of FIG. 2 ;
FIG. 4 is a perspective view of the inner ring assembly;
FIG. 5 is a front plan view of the inner ring assembly;
FIG. 6 is perspective view of a bearing annular body of the inner ringassembly;
FIG. 7 is an axial cross-sectional view of the bearing annular body;
FIG. 8 is a perspective view of a locking collar of the inner ringassembly;
FIG. 9 is a partially broken-away front plan view of the locking collar;
FIG. 10 is an enlarged, broken-away view of an upper portion of FIG. 9 ;
FIG. 11 is a broken-away, axial cross-sectional view of a lower portion of the locking collar, showing a first construction retainer;
FIG. 12 is a broken-away, axial cross-sectional view of a lower portion of the locking collar, showing a second construction retainer;
FIG. 13 is broken-away, axial cross-sectional view of the bearingannular body, showing a first construction slotted opening;
FIG. 14 is broken-away, axial cross-sectional view of the bearingannular body, showing a second construction slotted opening;
FIG. 15 is an enlarged, broken-away axial view of a mounting tab; and
FIG. 16 is another enlarged, broken-away axial view of a mounting tab.
DETAILED DESCRIPTION OF THE INVENTION
Certain terminology is used in the following description for convenience only and is not limiting. The words “inner”, “inwardly” and “outer”,“outwardly” refer to directions toward and away from, respectively, a designated centerline or a geometric center of an element being described, the particular meaning being readily apparent from the context of the description. Further, as used herein, the words“connected” and “coupled” are each intended to include direct connections between two members without any other members interposedtherebetween and indirect connections between members in which one or more other members are interposed therebetween. The terminology includes the words specifically mentioned above, derivatives thereof, and words of similar import.
Referring now to the drawings in detail, wherein like numbers are usedto indicate like elements throughout, there is shown in FIGS. 1-16 an inner ring assembly 10 for a bearing 1, which preferably includes anouter ring 2 disposed about the inner ring 10 and a plurality of rolling elements 3 disposed between the inner ring assembly 10 and the outer ring 2 as shown in FIG. 2 . The bearing 1 rotatably couples a shaft 4with an outer member 5, such as a housing, the shaft 4 being rotatableabout a central axis A_(C). The inner ring assembly 10 basically comprises a bearing annular body 12 disposable about the shaft 4 and anannular locking collar 14 disposable about a portion of the annular body12 and configured to retain the body 12 radially and axially on the shaft 4. With such an integral mounting structure, the bearing innerring assembly 10 is readily mountable upon the shaft 4 without requiring precision machining of the shaft outer surface 4 a.
More specifically, the annular body 12 has a centerline 13, opposing first and second axial ends 12 a, 12 b, an inner circumferential surface16 defining a central bore 17 for receiving the shaft 4 and an opposing outer circumferential surface 18. An annular groove 20 extends inwardlyfrom the outer surface 18 and provides a bearing inner race 22 for receiving the rolling elements 3. A plurality of slotted openings 24extend axially inwardly from the first axial end 12 a of the annularbody 12 and are spaced circumferentially about the centerline 13 so as to define a plurality of arcuate mounting tabs 26. Each mounting tab 26has an inner end 26 a integral with a remainder of the annular body 12and an opposing, free outer end 26 b at the body first axial end 12 a.
Further, the annular locking collar 14 is disposed about the plurality of mounting tabs 26 and is configured to clamp the tabs 26 against the outer surface 4 a of the shaft 4, as depicted in FIGS. 2 and 3 . Such clamping of the mounting tabs 26 retains the inner ring annular body 12radially and axially with respect to the shaft central axis A_(C). The locking collar 14 preferably includes an annular body 30 having a centerline 31, first and second axial ends 30 a, 30 b, respectively, an inner circumferential surface 32 with an inside diameter ID_(C) and anouter circumferential surface 34. The collar annular body 30 has a gapG_(C) defining first and second spaced apart circumferential ends 36 a,36 b, respectively, i.e., the gap G_(C) extends both axially between thefirst and second axial ends 30 a, 30 b and radially between the inner and outer circumferential surfaces 32, 34 to form the circumferentiallyspaced or “circumferential” ends 36 a, 36 b. Preferably, the annularbody 30 has an inside diameter ID_(C) in an unbended state, i.e., prior to clamping on the tabs 26, being sized such that the collar 14 is assembled about the plurality of mounting tabs 26 with a “line to line fit”, as is well known in engineering tolerancing, for reasons discussed below.
Furthermore, a threaded rod 38 extends through the first and secondcircumferential ends 36 a, 36 b and the collar 14 is configured suchthat rotation of the rod “closes” the gap G_(C) and clamps the collar 14about the mounting tabs 26, i.e., with a clamping force F_(C) (FIG. 3 ).Specifically, a threaded opening 40 is formed in the firstcircumferential end 36 a and a through hole 42 is formed in the secondcircumferential end 36 b, the opening 40 and the hole 42 being generally aligned and extending generally tangentially with respect to the collar centerline 31, as best shown in FIG. 10 . The threaded rod 38 extends through the through-hole 42 and into the threaded opening 40 and has ahead 39 that bears against a shoulder surface 43 surrounding the hole42. With this structure, rotation of the rod 38 in a first angular direction A₁ (FIG. 4 ) displaces the first and second ends 36 a, 36 b ofthe annular body 36 generally toward each other, which reduces the sizeof the body inside diameter ID_(C) (FIG. 9 ). Such reduction of thecollar body inside diameter ID_(C) causes the collar 14 to compress or clamp the plurality of mounting tabs 26 into engagement with the shaft4, as indicated in FIG. 3 . Further, the threaded opening 40 and the through hole 42 are arranged such that torque applied to rotate the rod38 in the first direction A₁ tends to bias a lower portion of the collarannular body 30 inwardly toward a center C_(B) of the annular body 12and against a lower portion of a radial stop surface 81 of the body 12,which facilitates installation of the inner ring assembly 10 on the shaft 4.
With the basic structure being described above, the present inner ringassembly 10 has a number of improvements over previously known innerring assemblies, such as follows. The locking ring assembly 10 is provided with at least one, and preferably two, structural features for retaining the locking collar 14 on the inner ring body 12 when the innerring assembly 10 is separate from the shaft 4, i.e., during transport and prior to assembly. Also, the locking collar 14 is formed so as to more evenly distribute the mass of the collar body 30 about the centerline 31 and thereby optimize dynamic balance of the inner ringassembly 10, and to also increase the clamping force exerted on the mounting tabs 26. Further, the annular body 12 of the ring assembly 10is formed to reduce stress concentration, particularly by improvements in the structure of the mounting tabs 26. These improvements and others of the present inner ring assembly 10 are explained in greater detail below.
Referring to FIGS. 3-6 and 11-12 , as mentioned above, the inner ringassembly 10 preferably has two structural features for retaining the locking collar 14 disposed about the inner ring body 30 when the innerring assembly 10 is separate from the shaft 4, i.e., when the ringassembly 10 is in an unmounted or “dismounted” state. First, at leas tone and preferably all of the mounting tabs 26 each has a projection 50extending radially outwardly from the outer axial end 26 b of each tab26. Each projection 50 is disposable against or engageable with the locking collar 14 to retain the collar 14 on the inner ring assembly 10.More specifically, each retainer projection 50 is sized to permit thecollar 14 to displace axially over the plurality of projections 50during installation of the collar 14 on the inner ring body 12, unless the projections 50 are formed after installation of the collar 14 aboutthe annular body 12, as discussed below. That is, each projection 50 hasa limited radial height or extent such that, with slight inward bending of the mounting tabs 26 and angling or cocking of the collar body 30,the inner surface 32 of the collar 14 is able to pass over all of the projections 50 to become disposed about the plurality of mounting tabs26.
At the same time, each projection 50 is also sized to engage with thefirst or outer axial end 30 a of the collar annular body 30 to retain the locking collar 14 on the ring annular body 12. In other words, the projections 50 have a sufficient radial length/height to collectively retain the locking collar 14 from being axially displaced off of the mounting tabs 26 once installed thereabout. However, the radial height/length of each projection 50 is preferably lesser than the radial height of a chamfer 30 e formed on the inner end 30 b of the collarannular body 30 to enable the collar 14 to deflect the mounting tabs 26radially inwardly during assembly of the collar 14. Further, each projection 50 may be pre-formed as a forged or machined projection or may be formed after assembly of the collar 14 onto the mounting tabs 26,such as by staking or otherwise disrupting a portion of the material ofeach tab 26. Preferably, each projection 50 is generallypyramidal-shaped and located generally centrally on each mounting tab outer end 26 b, as best shown in FIG. 5 . Alternatively, each projection50 may be provided by an arcuate radial lip 51 formed at the outer end26 a of each mounting tab 26, as depicted in FIG. 3 . However, the retainer projections 50 may have any other appropriate shape or the inner ring assembly 10 may be formed without any retainer projections,such that the locking collar 14 is retained solely by a movable retainer member 56, as follows.
Referring to FIGS. 11-12 , the inner ring assembly 10 may additionally or alternatively include a retainer member 56 movably coupled with and projecting radially inwardly from the locking collar 14. The retainer member 56 is engaged or engageable with one of the mounting tabs 26,preferably with a recess 58 of one of the mounting tabs 26, to thereby retain the locking collar 14 disposed about the ring annular body 12.More specifically, each one of the mounting tabs 26 of the inner ringannular body 12 has an outer surface 27 with a recess 58, as described in detail below, and the retainer member 56 extends radially inwardlyfrom the inner circumferential surface 32 of the collar body 30. The retainer member 56 has an inner radial end 56 a disposable within the recess 58 of one of the mounting tabs 26 to retain the locking collar 14on the ring annular body 12.
Preferably, the locking collar 14 has a radial passage 60 with an opening 62 on the collar inner circumferential surface 32, which may bea blind hole 64, as shown in FIG. 11 , or a through hole 66 as depicted in FIG. 12 . The retainer member 56 is disposed within the passage 60and extends through the passage opening 62. Further, a spring 68 is disposed within the passage 60 and biases the retainer member 56radially inwardly toward the one mounting tab 26, i.e., the mounting tab26 which is located so as to extend beneath the passage 60.
The retainer member 56 is preferably a sphere or “ball” 57 having a radially inner portion 57 a disposed externally of the collar 14 and within the mounting tab recess 58. The spring 64 is compressed betweenthe ball 57 and either an inner end 64 a of the blind hole 64 or a threaded rod 67 enclosing the through hole 66. Although preferably formed as a ball 57, the retainer member 56 may be formed in any other appropriate manner, such as for example, as a stepped pin (not shown)slidably disposed within the passage 60. Furthermore, the locking collar14 may alternatively be formed without any movable retainer member and may instead be retained on the inner ring body 12 solely by the projections 50 on the mounting tabs 26.
Referring now to FIGS. 9 and 10 , as described above, the locking member14 is preferably formed with the annular body 30 having an adjustable gap G_(C), the threaded opening 40 and the through hole 42. To provide the shoulder surface 43 and space for the rod head 39, a counterborehole 44 is also formed adjacent to the through hole 42 and a partial“lead in” opening 46 is formed adjacent to the threaded opening 40during drilling of the opening 40 prior to tapping the threads thereof.As such, the gap G_(C), the threaded opening 40 and the holes 42, 44, 46each reduce the mass or weight of the collar body 30 in a section of the body 30 generally centered about the gap G_(C), which is not compensated for by the mass of the threaded rod 38. As such, the center of mass (not indicated) of the locking collar 14 is offset from the centerline 31 ofthe collar body 30, and therefore from the shaft central axis A_(C).Thus, the inner ring assembly 10 is dynamically imbalanced during rotation of the shaft 4, which may result in vibration or excess stresses or strains within portions of the inner ring assembly 10.
Therefore, to improve the dynamic characteristics of the present innerring assembly 10, the annular body 30 of the locking collar 14 is preferably formed having a flat surface section 70 in the body outercircumferential surface 34. Such a flat surface section 70 is formed by removal of a circular segment from a solid annular body 30 and has a center C_(F) and a length L_(F). between opposing ends 70 a, 70 b, as indicated in FIG. 9 . The center C_(F) of the flat surface section 70 iss paced about one hundred eighty degrees (180°) from the collar gapG_(C), so as to be located to offset the material losses or mass reduction in region of the gap G_(C). Further, the length L_(F) of the flat surface 70 is selected so as to remove a sufficient amount of material from the annular body 30 to offset the material removed in the region of the gap G_(C) so that the center of mass (not indicated) ofthe body 30 with the flat surface 70 is generally located on the centerline 31. As such, the flat 70 functions to increase the dynamic balance the locking collar 14 about the shaft central axis A_(C).
Furthermore, by forming the annular body 30 of the collar 14 with the flat surface section 70, the flexibility of the locking collar 14 is increased during compression of the mounting tabs 26. Specifically,providing the flat surface section 70 forms two arcuate portions 30 c,30 d of the collar annular body 30 which each extend between one end 70a, 70 b, respectively, of the flat section 70 and a separate one of thecircumferential ends 36 a, 36 b, respectively, of the body 30. Thesearcuate portions 30 c, 30 d of the annular body 30 tend to pivot aboutthe ends 70 a, 70 b of the flat section 70 and toward the collar centerline 31 when the threaded rod 38 displaces the circumferentialends 36 a, 36 b toward each other, which increases the clamping forceF_(C) exerted by the annular body 30 on the mounting tabs 26. Also, dueto the line to line fit between the inner circumferential surface 32 ofthe collar 14 and the outer surfaces 27 of the mounting tabs 26, the amount of rotation of the threaded rod 38 necessary to clamp the mounting tabs 26 to the shaft 4 is reduced and the total amount of clamping force F_(C) exerted on the tabs 26 is potentially increased.
Referring to FIGS. 3 and 13-16 , as mentioned above, the bearing annularbody 12 of the inner ring assembly 10, and particularly the mounting tabs 26 thereof, are preferably formed so as to reduce stress concentration and therefore fracturing or other forms of failure of the assembly 10. First, each one of the slotted openings 24 in the annularbody 12 is preferably partially bounded by a curved inner end surface72, which are each adjacent to the bendable inner ends 26 a of two mounting tabs 26. Specifically, each slotted opening 24 is defined by facing first and second side surfaces 74, 76, each side surface 74, 76extending axially inwardly from the annular body first axial end 12 a,and the curved end surface 72 extends between and connects the inner ends 74 a, 76 a of the first and second side surfaces 74, 76. Typically,such slotted openings have a “flat” end surface which extends perpendicular to the side surfaces and creates corners, which lead to a concentration of stress during bending of the adjacent tabs. Preferably,the curved end surfaces 72 are partially circular as shown in FIGS. 13and 14 , and may extend circumferentially wider than the spacing betweenthe side surfaces 74, 76, as depicted in FIG. 14 . However, each curved end surface 72 may have any other appropriate shape, such as partially elliptical, etc.
Next, each one of the mounting tabs 26 is preferably formed having anouter circumferential surface 27 with a radiused section 80 at the tab inner end 26 a, a cylindrical section 82 extending axially inwardly fromthe tab outer end 26 b and an angled section 84 extending between theradiused section 80 and the cylindrical section 82. The radiused section80 and the angled section 82 define the tab recess 58 for receiving thecollar retainer member 56, as described above, the recess 58 having an innermost point PI that is offset radially inwardly from the cylindrical section 84 by an offset distance d_(O) (FIG. 16 ) as discussed below.With this mounting tab structure, the inner surface 32 of the locking collar 14 is disposed against and about the cylindrical surfaces 82 ofall of the mounting tabs 26, with the second, inner end 30 b of thecollar body 30 preferably being disposed against a radial stop surface81 of the annular body 12 formed radially outwardly of the recessed surface section 80, as shown in FIG. 3 .
Thus, the material reduction created by forming the radiused and angled sections 80, 84, respectively, increases the flexibility of the mounting tabs 26. As such, each mounting tab 26 is radially bendable at theradiused section 80 with respect to the remainder of the ring annularbody 12 generally in the manner of a cantilever beam, thereby enabling the mounting tabs 26 to deflect inwardly during clamping by the locking collar 14. To further increase the flexibility of the mounting tabs 26,each tab cylindrical section 82 has an outside diameter OD_(T) that is lesser than the outside diameter OD_(B) of the remainder of the ringannular body 12, as shown in FIG. 16 .
To reduce stress concentration at the inner end 26 a of each mounting tab 26, the radiused section 80 is preferably formed having a substantial radius R_(RS) that extends between the remainder of the bearing annular body 12 and the angled section without any joints or disruptions which could concentrate stresses. Preferably, the radiusR_(RS) is at least about half of the offset distance d_(O) of the recess58, and most preferably about equal to the offset distance d_(O), as depicted in FIG. 16 . Further, the transition between the angled surface section 84 and the cylindrical surface section 82 eliminates a sharp edge or shoulder between the recess 58 and the tab surface 82 receiving clamping force F_(C) from the locking collar 14. Therefore, with both the substantial radius R_(RS) of the radiused section 80 and an angled surface section 84 which transitions to the cylindrical surface section82 without any sharp edges, the stress concentrations within each mounting tab 26 are generally eliminated or at least significantly reduced.
Representative, non-limiting examples of the present invention were described above in detail with reference to the attached drawings. This detailed description is merely intended to teach a person of skill inthe art further details for practicing preferred aspects of the present teachings and is not intended to limit the scope of the invention.
Moreover, combinations of features and steps disclosed in the above detailed description may not be necessary to practice the invention inthe broadest sense, and are instead taught merely to particularly describe representative examples of the invention. Furthermore, various features of the above-described representative examples, as well as the various independent and dependent claims below, may be combined in ways that are not specifically and explicitly enumerated in order to provide additional useful embodiments of the present teachings.
All features disclosed in the description and/or the claims are intended to be disclosed separately and independently from each other for the purpose of original written disclosure, as well as for the purpose of restricting the claimed subject matter, independent of the compositions of the features in the embodiments and/or the claims. In addition, all value ranges or indications of groups of entities are intended to disclose every possible intermediate value or intermediate entity forthe purpose of original written disclosure, as well as for the purpose of restricting the claimed subject matter. The invention is not restricted to the above-described embodiments, and may be varied withinthe scope of the following claims.
We claim:
1. An inner ring assembly for a bearing, the bearing rotatablycoupling a shaft with an outer member, the shaft being rotatable about a central axis, the inner ring assembly comprising: a ring annular body disposable about the shaft and having a centerline, opposing first and second axial ends, an outer circumferential surface, an annular groove extending radially inwardly from the outer surface and providing a bearing inner race, and a plurality of slotted openings extendingaxially inwardly from the first axial end and spaced circumferentiallyabout the centerline so as to define a plurality of arcuate mounting tabs, each mounting tab having an inner end integral with a remainder ofthe annular body and an opposing, free outer end; and an annular locking collar disposed about the plurality of mounting tabs and configured toc lamp the tabs against the outer surface of the shaft so as to retain the inner ring radially and axially with respect to the shaft central axis, the collar being retained on the ring annular body when the innerring is separate from the shaft by at least one of a retainer projection extending radially outwardly from the outer end of one of the mounting tabs and engaging with the collar and a retainer member movably coupled with and projecting radially inwardly from the collar and engaging with one of the mounting tabs.
2. The inner ring assembly as recited in claim1 wherein: each one of the mounting tabs of the ring annular body has anouter surface with a recess; and the locking collar has an innercircumferential surface and the retainer member extends radiallyinwardly from the collar inner circumferential surface, the retainer member having an inner radial end disposable within the recess of one ofthe mounting tabs to retain the collar on the annular body.
3. The innerring assembly as recited in claim 2 wherein the locking collar has a radial passage with an opening on the inner circumferential surface, the retainer member being disposed within the passage and extending throughthe passage opening, and a spring disposed within the passage andbiasing the member radially inwardly toward the one mounting tab.
4. The inner ring assembly as recited in claim 1 wherein each one of the mounting tabs has the retainer projection extending radially outwardlyfrom the tab outer axial end and the retainer projection is sized to permit the collar to displace axially over the projection during installation of the collar on the inner ring body and sized to engage with an axial end of the collar to retain the collar on the inner ring.5. The inner ring assembly as recited in claim 1 wherein each one of the mounting tabs has an outer circumferential surface with a radiusedsection at the tab inner end, a cylindrical section extending axiallyinwardly from the tab outer end and an angled section extending betweenthe surface radiused section and the surface cylindrical section, theradiused section and the angled section defining a recess, each mounting tab being generally radially bendable at the radiused section with respect to the remainder of the ring annular body.
6. The inner ringassembly as recited in claim 5 wherein an innermost point of the recess is offset radially inwardly from the cylindrical section by an offset distance and the radiused section has a radius of at least half of the offset distance.
7. The inner ring assembly as recited in claim 1wherein each slotted opening of the inner ring body has opposing, first and second side surfaces, each side surface extending axially between anouter end at the annular body outer end and an inner end, and a curved end surface extending between the inner ends of the first and second side surfaces.
8. The inner ring assembly as recited in claim 1 wherein the locking collar includes an annular body with a gap defining first and second spaced apart circumferential ends, a threaded opening formed in the first circumferential end, a through hole formed in the secondcircumferential end and a threaded rod extending through the through-hole and into the threaded opening such that rotation of the rodin a first angular direction displaces the annular body first and second ends generally toward each other to reduce the annular body inside diameter and compress the plurality of mounting tabs into engagement with the shaft.
9. The inner ring assembly as recited in claim 8 wherein the annular body of the locking collar has an outer circumferentialsurface with a flat surface section, the flat surface section having a center spaced about one hundred eighty degrees from the gap so as to increase the dynamic balance the collar about the shaft central axis.10. An inner ring assembly for a bearing, the bearing assembly rotatablycoupling a shaft with an outer member, the shaft being rotatable about a central axis, the inner ring assembly comprising: a ring annular body disposable about the shaft and having a centerline, opposing first and second axial ends, an outer circumferential surface, an annular groove extending inwardly from the outer surface and providing a bearing inner race, and a plurality of slotted openings extending axially inwardlyfrom the first axial end and spaced circumferentially about the centerline so as to define a plurality of arcuate mounting tabs, each mounting tab having an inner end integral with a remainder of theannular body and an opposing, free outer end; and a locking collar including an annular body disposed about the plurality of mounting tabs,the annular body having an inner circumferential surface with an inside diameter, an outer circumferential surface, a gap defining spaced apart first and second circumferential ends, and a threaded rod extending through the first and second circumferential ends such that rotation ofthe threaded rod in a first angular direction displaces the first and second circumferential ends generally toward each other to reduce the body inside diameter and compress the plurality of mounting tabs into engagement with the shaft, the body outer circumferential surface having a flat surface section with a center spaced about one hundred eighty degrees (180°) about the centerline from the gap so as to increase the dynamic balance of the collar about the shaft central axis and increase the flexibility of the annular body during compression of the mounting tabs.
11. The inner ring assembly as recited in claim 10 wherein a threaded opening is formed in the first circumferential end of thecollar annular body, a through hole is formed in the secondcircumferential end of the collar annular body and the threaded rod extends through the through-hole and into the threaded opening, the threaded opening being oriented such that torque applied to rotate the rod in the first angular direction biases the locking collar axiallytoward the center of the ring annular body.
12. The inner ring assembly as recited in claim 10 wherein the collar is retained on the ringannular body when the inner ring is separate from the shaft by at leas tone of a retainer projection extending radially outwardly from the outer end of one of the mounting tabs and engaging with the collar and a retainer member movably coupled with and projecting radially inwardlyfrom the collar and engaging with one of the mounting tabs.
13. The inner ring assembly as recited in claim 12 wherein at least one of: each one of the mounting tabs of the ring annular body has an outer surface with a recess, the locking collar has an inner circumferential surface and the retainer member extends radially inwardly from the collar innercircumferential surface, the retainer member having an inner radial end disposable within the recess of one of the mounting tabs to retain thecollar on the annular body; and each one of the mounting tabs has the retainer projection extending radially outwardly from the tab outer axial end and each retainer projection is sized to permit the collar todisplace axially over the projection during installation of the collar on the inner ring body and sized to engage with an axial end of thecollar to retain the collar on the inner ring.
14. The inner ringassembly as recited in claim 10 wherein each one of the mounting tabs has an outer circumferential surface with a radiused section at the tab inner end, a cylindrical section extending axially inwardly from the tab outer end and an angled section extending between the surface radiusedsection and the surface cylindrical section, the radiused section andthe angled section defining a recess, each mounting tab being generallyradially bendable at the radiused section with respect to the remainder of the ring annular body.
15. The inner ring assembly as recited in claim 10 wherein the annular body of the collar has an inside diameter in an unbended state being sized such that the collar is assembled aboutthe plurality of mounting tabs with a line to line fit.
16. An innerring assembly for a bearing assembly, the bearing rotatably coupling a shaft with an outer member, the shaft being rotatable about a central axis, the inner ring assembly comprising: an annular body disposable about the shaft and having a centerline, opposing first and second axial ends, an outer circumferential surface, an annular groove extendinginwardly from the outer surface and providing a bearing inner race, anda plurality of slotted openings extending axially inwardly from thefirst axial end and spaced circumferentially about the centerline so as to define a plurality of arcuate mounting tabs, each slotted opening being partially bounded by a curved inner end surface and each mounting tab having an inner axial end integral with a remainder of the annularbody, a free, outer axial end and an outer circumferential surface, the outer surface of each tab having a radiused section at the tab inner end, a cylindrical section extending axially inwardly from the tab outer end and an angled section extending between the radiused section and the cylindrical section and defining a recess; and an annular locking collar disposed about the plurality of mounting tabs and configured to clamp the tabs against the outer surface of the shaft so as to retain the inner ring radially and axially with respect to the shaft central axis.17. The inner ring assembly as recited in claim 16 wherein the curved surface section of each slotted opening is partially circular.
18. The inner ring assembly as recited in claim 16 wherein the locking collar has an inner circumferential surface and at least one retainer, the retainer extending radially inwardly from the collar inner surface and having an end portion disposable within the recessed section of one ofthe mounting tabs to retain the collar on the annular body.
19. The inner ring assembly as recited in claim 16 wherein at least one of: each one of the plurality of mounting tabs has a retainer projection extending radially outwardly from a center of the tab outer axial end and being sized to enable the collar to displace axially over the projection to install the collar on the inner ring body and to engage with an outer axial end of the collar to retain the collar on the innerring; and the locking collar further includes a retainer member movablycoupled with and projecting radially inwardly from the collar and engaging with one of the mounting tabs.
20. The inner ring assembly as recited in claim 16 wherein the locking collar includes an annular body disposed about the plurality of mounting tabs, the annular body having an inner circumferential surface with an inside diameter, an outercircumferential surface, a gap defining first and second spaced apartcircumferential ends, and a threaded rod extending through the first and second circumferential ends such that rotation of the rod in a first angular direction displaces the first and second ends generally toward each other to reduce the annular body inside diameter and compress the plurality of mounting tabs into engagement with the shaft, the annularbody outer circumferential surface having a flat surface section with a center spaced about one hundred eighty degrees (180°) about the centerline from the gap so as to increase the dynamic balance of thecollar about the shaft central axis.
|
Page:Imperialdictiona03eadi Brandeis Vol3b.pdf/447
TRI 1746 he went to Dresden, where he held a court appointment. Three years later he accepted a professorship in the university of Wittenberg, which he retained until his death in May, 1782. Triller was a laborious commentator on the ancients. A great part of his life was employed on an edition of Hippocrates, of which he only published a specimen. His principal original work was on pleurisy, Frankfort, 1740. He wrote Latin poems on medicine, and was also a cultivator of German poetry. He was also the author of a number of treatises on medical antiquities. A complete list of his works is given in the Biographic Médicale. It occupies two pages.—F. C. W. TRIMMER,, author of a number of popular books for the young, was born at Ipswich on the 6th of January, 1741. Her father was Mr. Joshua Kirby, author of Dr. Brooke Taylor's Method of Perspective Made Easy, and of The Perspective of Architecture. He subsequently removed to London on becoming tutor in perspective to George III., then prince of Wales; and from the year 1759 lived at Kew, having been appointed clerk of the works at the palace at that place. It was while residing here that Miss Kirby became acquainted with Mr. Trimmer, to whom she was married at the age of twenty-one. For the next twelve years she was wholly occupied with her domestic duties, her literary labours not having commenced till about the year 1780. It was, we are told, the example of Mrs. Barbauld that first led her to write books. Her first publication was a small volume, entitled, an "Easy Introduction to the Knowledge of Nature." It was followed by her "Sacred History, Selected from the Scriptures, with Annotations and Reflections adapted to the Comprehension of Young Persons," 1782-84; "The Economy of Charity," addressed to ladies, 1786, and republished with additions and alterations in 1801; "The Family Magazine," from which were afterwards published in a collected form, a seines of "Instructive Tales;" Illustrations of the Old and New Testaments, and of the Histories of Rome and England, said to have been suggested by the Adele et Theodore of Madame de Genlis; the "Guardian of Education;" "A Comparative View of the New Plan of Education," &c., 1806. Her last publication was a volume of "Family Sermons," selected and abridged from the most eminent divines. Mrs. Trimmer died suddenly, while sitting in her study chair, on the 15th of December, 1810. In 1814 was published an Account of the Life and Writings of Mrs. Trimmer, 2 vols., 8vo. TRINCAVELLI, TRINCAVELLA, or TRINCAVELA, , a physician of great classical acquirements, was born at Venice in 1496. He studied at Padua and Bologna. At the latter university he acquired such a mastery over the Greek language and literature, that his assistance in the elucidation of difficult passages was occasionally sought by the professors. At the end of seven years he returned to Padua, where he graduated, and then settled at Venice. Here he succeeded Sebastian Foscarini in the chair of philosophy, and obtained a lucrative practice. It was at this period that he published the works of several Greek authors from original MSS., which had previously been known only by imperfect Latin translations. These were, Themistii Orationes, 1534, folio; Joannes Grammaticus Philoponus, 1534, folio; Epicteti Enchiridion cum Arriani Comment., 1535, 8vo; Hesiod, 1536, 4to. He was intrusted by the Venetian government with the treatment of an epidemic which had broken out in the island of Murano, and his success was so marked that on his return he was received with a sort of ovation. In 1551 he was induced to leave Venice for Padua, where he succeeded J. B. Montanus in the chair of medicine. This change was made at a considerable pecuniary loss, but the senate increased his annual stipend from nine hundred and fifty to sixteen hundred crowns in consideration of the sacrifice he had made. He died at Venice in 1568. Trincavelli has the merit of being one of the first scholars who introduced the writings of the Greek medical authors into the Italian schools of medicine. Previously they had been chiefly known through the medicine of the Arabian writers. His medical works (Opera Omnia) were published at Lyons in 1586; at Venice in 1599. His original treatises are now only of antiquarian interest; but he published commentaries on various parts of the writings of Galen, Avicenna, and Hippocrates. He also edited Stobæus. In practice he is said to have adhered principally to the Arabian doctrines.—F. C. W. TRINIUS,, an eminent German naturalist, was born at Eisleben on 7th March, 1778, and died at St. Petersburg on 12th March, 1844. He devoted attention early to botany, and more particularly to grasses, on which he published several valuable works. The chief of these are—"Fundamenta Agrostographiæ," and "Species Graminum." The latter is in three volumes folio, and is illustrated by plates. He resided long in St. Petersburg, and was a member of the Academy. He was director of the botanical museum, which was enriched by him by the addition of five thousand species of grasses. He was admired for his varied accomplishments, and for his depth of intellect. He was also a man of amiable disposition and agreeable manners.—J. H. B. * TRIQUETI,, Baron de, an eminent French sculptor, was born at Conflans (Loiret) in 1802. He was a pupil of the painter Hersent, but he studied sculpture as well as painting, and at the Exposition of 1831 sent contributions in each art. The success of his group of "The Death of Charles the Bold" and the award of the second prize in sculpture, decided him to adopt sculpture as his profession. Baron de Triqueti has produced a large number of works in marble and bronze in the various branches of sculpture: groups, statues, and rilievi of religious subjects for church decorations and monuments; classical subjects; historical, both native and foreign, as "Genevieve de Brabant," and "Sir Thomas More before his Execution;" numerous portrait-statues, and busts; fountains, vases, &c. He has a high reputation in France, and he has received several commissions from England. He has occasionally contributed to the exhibitions of our Royal Academy, his latest contribution being, in 1862, a bronze group of "Dante and Virgil." Baron de Triqueti received the first prize of sculpture in 1839, and the cross of the legion of honour in 1842.—J. T—e. TRISSINO,, poet; born of noble parentage at Vicenza, 8th July, 1478; died in Rome, December, 1550. He has left an epic poem, "L'Italia liberata dai Goti," constructed on the Homeric model; "Sofonisba," a tragedy of classical character; "La Poetica," a treatise on the poetic art; and other works. He also proposed certain additions to the Italian alphabet, somewhat in the phonetic style; and has been reckoned the originator of versi sciolti (blank verse).—C. G. R. TRISTAN DA CUNHA, a Portuguese navigator, who sailed from Lisbon in 1506 with a squadron of fifteen vessels, intended to cruize in the Red Sea, and discovered the three islands which bear his name, off the Cape of Good Hope. He explored a portion of Madagascar, and took possession of the island of Socotra. Leaving his second in command, Alfonso d'Albuquerque, to cruize in the Red Sea, Da Cunha proceeded to Cochin, and embarked in an expedition against Calicut, which was so far successful that he returned to Portugal with five richly-laden ships. He was appointed ambassador to Leo X. in 1515, and appears to have died about 1536. An account of his expedition was compiled by De Barros, and published by order of the king, and a translation was published at Leyden in 1706.—F. M. W. TRITHEMIUS,, a learned Benedictine, was born in 1462 at Tritenheim, in the diocese of Treves, and was educated at Treves and Heidelberg. He was made abbot of Spanheim, in the diocese of Mentz, in 1483, and died in 1516. He wrote a considerable number of works, amongst which may be mentioned those "On the Illustrious Ecclesiastical Writers;" "On the Illustrious Men of Germany;" and "On the Illustrious Men of the Benedictine Order." <section end="447H" /> <section begin="447I" />TRIVET,, a learned English dominican friar, the son of Sir Thomas Trivet, one of the justices in Eyre in the reign of Henry III., was born in Norfolk about 1258, and was educated at a dominican convent in London, and at the universities of Oxford and Paris. On his return to England he was elected prior of the religious house in which his early years were passed, and continued to fill that post up to the time of his death, which took place in 1328. Trivet was author of several works, including commentaries on the Holy Scriptures and on St. Augustine's writings; on the Problems of Aristotle, the Metamorphoses of Ovid, the Tragedies of Seneca, the works of Böethius, Livy, and Juvenal; and some scientific treatises, the MSS. of which are still extant in the libraries of Oxford and Cambridge. The work by which Trivet is now best remembered, is a history of England about the period in which he himself flourished, entitled "Annales Sex Regum Angliæ." It was published by Anthony Hall at Oxford in 1719.—F. <section end="447I" /> <section begin="447Zcontin" />TRIVULZIO: a patrician family of Milan, prolific of noteworthy members:— (1447) with several of his brothers opposed the accession of Francesco Sforza to the <section end="447Zcontin" />
|
/*
* Type.cpp
*
* Created on: Nov 23, 2013
* Author: leili
*/
#include "Type.h"
namespace swift {
namespace code {
Type::Type(std::vector<std::string> scope, std::string name,
std::vector<Type> typeArgs, bool refTag, bool ptrTag, bool constTag) :
scope(scope), name(name), typeArgs(typeArgs), refTag(refTag), ptrTag(ptrTag), constTag(constTag) {
}
Type::Type(std::vector<std::string> scope, std::string name, Type typeArg,
bool refTag, bool ptrTag, bool constTag) :
Type(scope, name, std::vector<Type>( { typeArg }), refTag, ptrTag, constTag) {
}
Type::Type(const std::string name, bool refTag, bool ptrTag, bool constTag) :
Type(std::vector<std::string>(), name, std::vector<Type>(), refTag, ptrTag, constTag) {
}
Type::Type(std::vector<std::string> scope, std::string name, bool refTag, bool ptrTag, bool constTag) :
Type(scope, name, std::vector<Type>(), refTag, ptrTag, constTag) {
}
bool Type::hasScope() const {
return scope.size() > 0;
}
Type::Type(std::string name, std::vector<Type> typeArgs, bool refTag, bool ptrTag, bool constTag) :
Type(std::vector<std::string>(), name, typeArgs, refTag, ptrTag, constTag) {
}
Type::Type(Type baseType, std::vector<Type> typeArgs, bool refTag, bool ptrTag, bool constTag) :
Type(baseType.scope, baseType.name, typeArgs, refTag, ptrTag, constTag) {
}
Type::~Type() {
}
const std::string& Type::getName() const {
return name;
}
void Type::setRef(bool refTag) {
this->refTag = refTag;
}
bool Type::isRef() const {
return refTag;
}
void Type::setPtr(bool ptrTag) {
this->ptrTag = ptrTag;
}
bool Type::isPtr() const {
return ptrTag;
}
void Type::setConst(bool consTag) {
this->constTag = consTag;
}
bool Type::isConst() const {
return constTag;
}
std::vector<Type> & Type::getTypeArgs() {
return typeArgs;
}
std::vector<std::string>& Type::getScope() {
return scope;
}
// For Printer
void Type::print(printer::Printer* prt) {
prt->print(this);
}
} /* namespace code */
} /* namespace swift */
|
Portable insulating receptacles
ABSTRACT
The portable thermos receptacle has a receptacle main body containing an inner shell, an outer shell and a heat-insulating section defined between the inner shell and the outer shell, and a cover removably applied to an opening of the receptacle main body. The thermos receptacle has on the outer shell non-slip means over a zone covering both a center of gravity when the receptacle is full and a center of gravity when the receptacle is empty. The portable. thermos receptacle has a cylindrical shape which reduces toward the top or bottom. The non-slip means is a recess, ridge or corrugated portion which is formed integrally with the outer shell or a synthetic resin non-slip member attached to the outer shell.
This is a division of app ln Ser. No. 09/64,568 filed Mar. 8, 1999.
TECHNICAL FIELD
The present invention relates to a portable thermos receptacle.
BACKGROUND ART
Portable thermos receptacles each have a receptacle main body provided with a heat-insulating section defined between an inner shell and an outer shell, and a cover removably applied to an opening of the receptacle main body. Such thermos receptacles are roughly divided into two types, i.e. those with handles and those without handles. Generally, many of large-capacity thermos receptacles, which have large barrel diameters, are of the type with handles considering handle ability, for example, when the receptacle is carried and when the content in the receptacle is poured out.
Meanwhile, thermos receptacles having relatively small capacities are frequently of the type with no handles for convenience' sake, because they can be formed to have diameters such that the receptacles can be gripped with hands by the barrels. Further, such relatively small-capacity thermos receptacles in many cases have smooth barrel surfaces with no protrusion or recess due to difficulty in molding and the like, and also they are formed to have a cylindrical shape which reduces from the bottom toward the top or from the middle part of the barrel toward the top or bottom.
Accordingly, these thermos receptacles involve problems in that the receptacle is likely to slip when it is held with the hand by the barrel to pour the content of the receptacle out of it; and that, if the capacity of the receptacle is to be increased slightly, the height of the receptacle is increased rather than the barrel diameter, so that the center of gravity shifts greatly between the position when the receptacle is full and the position when the receptacle is empty to make it difficult to handle the receptacle unless the barrel of the receptacle is gripped at an appropriate position depending on the center of gravity in each occasion.
SUMMARY OF THE INVENTION
It is an objective of the present invention to provide a portable thermos receptacle which hardly slips even if it is held with the hand by the barrel and which can be handled easily even if the center of gravity shifts greatly.
The portable thermos receptacle according to the present invention has a receptacle main body containing an inner shell, an outer shell and a heat-insulating section defined between the inner shell and the outer shell; and a cover removably applied to an opening of the receptacle main-body; the outer shell having non-slip means over a zone covering both a center of gravity when the thermos receptacle is full and a center of gravity when the thermos receptacle is empty.
Accordingly, the gripping position when the thermos receptacle is carried or when the content of the receptacle is poured out or drunk can be clarified by the presence of the non-slip means, and the thermos receptacle can be gripped always at the center of gravity, facilitating handling of the receptacle.
The non-slip means is suitably used in a cylindrical thermos receptacle which reduces gradually toward the top or bottom. Further, the non-slip means is a recess, ridge or corrugated portion which is formed on the outer shell or a synthetic resin non-slip member attached to the outer shell. This non-slip member has ribs or protrusions on the surface.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a partial cross-sectional view of the portable thermos receptacle according to a first embodiment of the present invention;
FIG. 2 is a partial cross-sectional view of the portable thermos receptacle according to a second embodiment of the present invention;
FIG. 3 is a cross-sectional view showing the upper half of the portable thermos receptacle according to a third embodiment of the present invention;
FIG. 4 is a partial cross-sectional view showing of the portable thermos receptacle according to a fourth embodiment of the present invention;
FIG. 5 is a partial cross-sectional view showing the upper half of the portable thermos receptacle according to a fifth embodiment of the present invention;
FIG. 6 is a partial cross-sectional view showing the upper half of the portable thermos receptacle according to a sixth embodiment of the present invention; and
FIG. 7 is a partial cross-sectional view showing the upper half of the portable thermos receptacle according to a seventh embodiment of the present invention.
EMBODIMENTS OF THE INVENTION
The embodiments of the present invention will be described more specifically referring to the drawings respectively. It should be noted that like or same parts in these embodiments are affixed with the same reference numbers as used in the first embodiment, and description of them will be omitted or simplified.
FIG. 1 shows the first embodiment of the present invention. A thermos receptacle 1 is provided with a receptacle main body 2 having a heat-insulating structure and a cover 3 serving also as a cup removably applied to an opening of the receptacle main body 2. The receptacle main body 2 is formed by joining a metallic or resin closed-bottom inner shell 4 and a metallic or resin closed-bottom outer shell 5 at their upper end openings, and a heat-insulating section 6 having a vacuum heat-insulating structure is defined between the shell 4 and the shell 5. Further, a bottom part 7 is attached to the bottom of the outer shell 5.
A non-slip means 8 is formed on the outer circumference of the outer shell 5 over the zone covering both the center of gravity G1 when the thermos receptacle 1 is full and the center of gravity G2 when the thermos receptacle 1 is empty. The non-slip means 8 in this embodiment is an annular recess 81 formed by allowing the zone covering the centers of gravity G1 and G2 to recede from the upper and lower portions.
The outer shell has a side wall and a bottom wall and the inner shell has a side wall and a bottom wall, the side wall of the outer shell facing the side wall of the inner shell, the side wall of the inner shell extending above and below the annular recess. The receptacle has cylindrical shape which reduces gradually substantially linearly substantially from the non-slip means toward the top and which reduces gradually substantially linearly substantially from the non-slip means toward the bottom.
FIG. 2 shows a second embodiment of the present invention. The thermos receptacle 1 in this embodiment has as the non-slip part 8 an annular ridge 82, in place of the annular recess 81, formed by expanding the zone covering the centers of gravity G1 and G2 compared with the upper and lower portions.
FIG. 3 shows a third embodiment of the present invention. The cover 3 of the thermos receptacle 1 in this embodiment has on its top plate 3 a a closable drinking spout 11 protruding therefrom and a negative pressure relief valve 12. The drinking spout 11 contains a cylindrical drinking spout main body 13 having a channel 13 a and rising from one side of the top plate 3 a; a drinking spout portion 14 which is fitted on the drinking spout main body 13 to be shiftable along it in the axial direction so as to open and close the channel 13 a; and a drinking spout cap 15 which can be removably applied to the drinking spout portion 14.
The drinking spout main body 13 has a columnar guide 13 b formed at the center of the upper end and also has a stopping rim 13 c protruding along the periphery and to prevent the drinking spout portion 14 from slipping off the drinking spout main body 13. The drinking spout portion 14 has, in its cylindrical body 14 a, a through hole 14 c, formed at the center of its top plate 14 b, to which the guide 13 b is inserted; an annular ridge 14 d formed on the inner circumference of the cylindrical body 14 a at the middle part; and an engaging portion 14 e, with which the drinking spout cap 15 is engaged, formed on the outer upper circumference of the cylindrical body 14 a. The drinking spout cap 15 has a cap portion 15 a to be applied to the drinking spout portion 14, a retaining ring 15 b to be attached to the proximal portion of the drinking spout main body 13 and a retaining belt 15 c which connects the cap portion 15 a with the retaining ring 15 b and can be bent into a U shape. The cap portion 15 a has an engaging portion 15 d to be engaged with the engaging portion 14 e of the drinking spout portion 14 and a flange 15 e, which catches fingers when the cap portion 15 a is pulled off, formed along the inner upper circumference and along the outer upper circumference, respectively.
On the other side of the top plate 3 a of the cover 3, is formed a slit-like air vent 16 for preventing reduction in the internal pressure of the receptacle main body 2 from occurring, and the negative pressure relief valve 12 is located in the air vent 16. The negative pressure relief valve 12 has a valve stem 12 a inserted to the air vent 16, a valve element 12 b located on the lower end of the valve stem 12 a and a stopping end portion 12 c formed on the upper end of the valve stem 12 a. The valve element 12 b attached to the inner side of the top plate 3 a flexes when the internal pressure of the receptacle main body 2 is reduced to open the air vent 16, and closes the air vent 16 when the internal pressure of the receptacle main body 2 is returned to atmospheric pressure or when the pressure of the water in the receptacle main body 2 is exerted to the valve element 12 b.
An annular corrugated portion 83 consisting of a plurality of ribs is formed as the non-slip means 8 on the outer circumference of the outer shell 5 over the zone covering the centers of gravity G1 and G2. The corrugated portion 83 formed as the non-slip means 8 may be replaced with a plurality of protrusions.
In the thermos receptacle 1 having the constitution as described above, in the state where the drinking spout cap 15 is applied to the drinking spout portion 14 of the drinking spout 11 as shown in FIG. 3, the through hole 14 c and the channel 13 a are closed, and also the air vent 16 is closed by the valve element 12 b.
When one holds the thermos receptacle 1 by the non-slip means 8 and pulls up the flange 15 e with his or her hand or mouth, the drinking spout portion 14 is pulled up together with the drinking spout cap 15 to ascend until the annular ridge 14 d is engaged with the stopping rim 13 c. Then, the engaging portion 15 d rides over the engaging portion 14 e, and thus the drinking spout cap 15 is released from the drinking spout portion 14 to open the through hole 14 c and the channel 13 a.
If one holds the thermos receptacle 1 tilted such that the drinking spout 11 may locate on the lower side and sucks the water with his or her mouth applied to the drinking spout portion 14, the internal pressure of the thermos receptacle 1 is reduced, and the valve element 12 b of the negative pressure relief valve 12 flexes to open the air vent 16 and allow the outside air to flow through it into the thermos receptacle 1. Thus, the internal pressure of the thermos receptacle 1 is prevented from being reduced, and the water in the thermos receptacle 1 can be drunk through the through hole 14 c via the channel 13 a.
In this embodiment, since the procedures of opening and closing the drinking spout 11, tilting the thermos receptacle 1, etc. are carried out with the receptacle 1 being held with the hand by the non-slip means 8 formed to cover both the center of gravity G1 when the receptacle 1 is full and the center of gravity G2 when the receptacle 1 is empty, the thermos receptacle 1 can be gripped securely to facilitate the procedures of tilting etc.
FIG. 4 shows a fourth embodiment of the present invention which is carried out in a thermos receptacle 1 having the same drinking spout structure as in the third embodiment. The outer shell 5 is provided on the outer circumference with a cylindrical non-slip band 84 made of a synthetic resin, as the non-slip means 8, over the zone covering both the center of gravity G1 when the receptacle 1 is full and the center of gravity G2 when the receptacle 1 is empty. This non-slip member 84 is preferably made of an elastic material such as elastomer resin materials and silicone resin materials and can be attached to the outer shell 5 utilizing elasticity of such materials. Otherwise, a leather non-slip member may be bonded to such a zone.
FIG. 5 shows a fifth embodiment of the present invention, in which the present invention is carried out in a thermos receptacle 1 having the same cover structure as in the first embodiment. The thermos receptacle 1 has on the outer circumference of the outer shell a pair of annular ridges 5 a and 5 b molded integrally with the outer shell 5 at the upper and lower extremities of the zone covering both the center of gravity G1 when the receptacle 1 is full and the center of gravity G2 when the receptacle 1 is empty, and a non-slip member 85 having on the surface a plurality of annular ribs 85 a is interposed as the nonslip means 8 between these annular ridges 5 a and 5 b.
FIG. 6 shows a sixth embodiment of the present invention. In this embodiment, the present invention is carried out in a thermos receptacle 1 having a cover 3 of the same drinking spout structure as in the third embodiment. An annular recess 5 c is formed on the outer circumference of the outer shell 5 integrally over the zone covering both the center of gravity G1 when the receptacle 1 is full and the center of gravity G2 when the receptacle 2 is empty, and the same non-slip member 85 as in the fifth embodiment is fitted as the non-slip means 8 in the recess 5 c.
FIG. 7 shows a seventh embodiment of the present invention, in which the present invention is carried out in a thermos receptacle 1 having a cover 3 of the same drinking spout structure as in the third embodiment, and a non-slip member 86 having on the surface a plurality of protrusions 86 a is interposed as the non-slip means 8 between a pair of annular ridges 5 a and 5 b formed in the same as in the fifth embodiment.
According to the above constitutions, the gripping position can be clarified when the thermos receptacle is carried or when the content of the receptacle is poured out or drunk, and the thermos receptacle can be gripped at the center of gravity, facilitating handling of the receptacle. Further, the ribs or protrusions formed as the non-slip means exert higher effect of preventing slipping of the thermos receptacle.
It should be noted that it is of course possible to apply each of the non-slip means employed in the above embodiments to the other embodiments. Further, while the thermos receptacles 1 in the respective embodiments are formed to have cylindrical shapes which reduce gradually from the middle of the barrel toward the top, they may be of cylindrical shapes which reduce gradually from the bottom to the top or from the middle part of the barrel toward the bottom. In addition, while the receptacle main bodies 2 explained in the respective embodiments were of the vacuum heat-insulating structure, they may be of other heat-insulating structures, for example, a heat-insulating structure sealed with a low-thermal conductivity gas and a heat-insulating structure employing a heat insulating material such as urethane foam and the like.
What is claimed is:
1. A portable insulating receptacle comprising: a receptacle main body containing an inner shell, an outer shell, and a heat-insulating section defined between the inner shell and the outer shell; and a cover removably applied to an opening of the receptacle main body; the outer shell having a side wall and a bottom wall and the inner shell having a side wall and a bottom wall, the side wall of the outer shell facing the side wall of the inner shell; the outer shell having non-slip means extending over a zone covering both a center of gravity when the insulating receptacle is full and a center of gravity when the insulating receptacle is empty and located away from a top and a bottom of the receptacle, wherein the non-slip means is an un corrugated annular recess formed integrally with the outer shell, the side wall of the inner shell extending above and below the annular recess, having cyclindrical shape which reduces gradually substantially from the non-slip means toward the top and which reduces gradually substantially from the non-slip means towards the bottom.
2. The portable insulating receptacle according to claim 1, wherein the non-slip member has a plain surface.
|
/**
* Copyright 2016 Ryan Lau
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
*
* You may obtain a copy of the License at
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.isaacphysics.labs.chemistry.checker;
import java.util.HashMap;
/**
* Class for regular isotopes, i.e. single atom with subscripted and superscripted numbers on the left.
* Created by Ryan on 17/06/2016.
*/
public final class Isotope extends Nuclear {
/**
* Maps elements to their corresponding atomic number.
*/
private static HashMap<String, Integer> periodicTable;
/**
* Saved atom count.
*/
private HashMap<String, Fraction> savedAtomCount;
static {
periodicTable = new HashMap<>();
String[] elemList =
{"H", "He", "Li", "Be", "B", "C", "N", "O", "F", "Ne", "Na", "Mg", "Al", "Si", "P", "S", "Cl",
"Ar", "K", "Ca", "Sc", "Ti", "V", "Cr", "Mn", "Fe", "Co", "Ni", "Cu", "Zn", "Ga", "Ge", "As",
"Se", "Br", "Kr", "Rb", "Sr", "Y", "Zr", "Nb", "Mo", "Tc", "Ru", "Rh", "Pd", "Ag", "Cd", "In",
"Sn", "Sb", "Te", "I", "Xe", "Cs", "Ba", "La", "Ce", "Pr", "Nd", "Pm", "Sm", "Eu", "Gd", "Tb",
"Dy", "Ho", "Er", "Tm", "Yb", "Lu", "Hf", "Ta", "W", "Re", "Os", "Ir", "Pt", "Au", "Hg", "Tl",
"Pb", "Bi", "Po", "At", "Rn", "Fr", "Ra", "Ac", "Th", "Pa", "U", "Np", "Pu", "Am", "Cm", "Bk",
"Cf", "Es", "Fm", "Md", "No", "Lr", "Rf", "Db", "Sg", "Bh", "Hs", "Mt", "Ds", "Rg", "Cn", "Uut",
"Fl", "Uup", "Lv", "Uus", "Uuo"};
for (int i = 0; i < elemList.length; i++) {
periodicTable.put(elemList[i], i + 1);
}
}
/**
* Mass number of isotope.
*/
private Integer mass,
/**
* Atomic number of isotope.
*/
atom;
/**
* Atom/charged atom associated with isotope.
*/
private Formula formula;
/**
* Constructor method of Isotope.
* @param mass Mass number of isotope.
* @param atom Atomic number of isotope.
* @param f Atom/charged atom associated with the isotope.
*/
public Isotope(final Integer mass, final Integer atom, final Formula f) {
super();
this.mass = mass;
this.atom = atom;
this.formula = f;
}
@Override
public Integer getMassNumber() {
return mass;
}
@Override
public Integer getAtomicNumber() {
return atom;
}
@Override
public Fraction getCharge() {
return formula.getCharge();
}
@Override
public HashMap<String, Fraction> getAtomCount() {
if (savedAtomCount == null) {
savedAtomCount = formula.getAtomCount();
}
return savedAtomCount;
}
@Override
public boolean equals(final Object o) {
if (o instanceof Isotope) {
Isotope i = (Isotope) o;
return (this.mass.equals(i.mass))
&& (this.atom.equals(i.atom))
&& (this.formula.equals(i.formula));
}
return false;
}
@Override
public String toString() {
return "{}^{" + mass.toString() + "}_{" + atom.toString() + "}" + formula.toString();
}
@Override
public String getDotId() {
return "isotope_" + getdotId();
}
@Override
public String getDotCode() {
return "\t" + getDotId() + " [label=\"{‍‍‍‍Isotope‌|\\n"
+ getDotString()
+ "\\n\\n|‍‍‍atomic #‌: " + atom
+ "\\n|‍‍‍mass #‌: " + mass
+ "\\n|‍‍‍related atom‌}\",color=\"#944cbe\"];\n"
+ "\t" + getDotId() + ":s -> " + formula.getDotId() + ":n;\n"
+ formula.getDotCode();
}
@Override
public String getDotString() {
return "‍‍" + mass + "‌"
+ "‍" + atom + "‌"
+ formula.getDotString();
}
@Override
public int hashCode() {
return toString().hashCode();
}
@Override
public boolean isValidAtomicNumber() {
Molecule at;
if (formula instanceof Ion) {
at = ((Ion) formula).getMolecule();
} else {
at = (Element) formula;
}
return periodicTable.containsKey(at.toString())
&& periodicTable.get(at.toString()).equals(atom) && (mass >= atom);
}
}
|
What does "Resetting the connection" mean? System.Data.SqlClient.SqlException (0x80131904)
I know this is a bit vague, but I'm not being able to pinpoint the issue.
When I run the a bit of code against a local database it runs fine. When I use a remote database I get an error.
It occurs midway of the program execution. The DBup upgrade runs, and then a manual query fails with this exception:
System.Data.SqlClient.SqlException (0x80131904): Resetting the connection results in a different state than the initial login. The login fails.
Login failed for user 'sa'.
I'm creating SqlConnection manually using new SqlConnection() and I'm also using DbUp
I'm not sure what I can be doing wrong. Nor where to start debugging this.
The ConnectionString does not change and I'm always using sa to connect to the database.
A good question to start is What does "Resetting the connection" mean? How am I doing it?
See Entity Framework seed -> SqlException: Resetting the connection results in a different state than the initial login. The login fails.. Does that solve your problem?
If a database is attached to a server never use the AttachDB (localdb) property in the connection string (remove). The server owns the mdf database file and doesn't allow users to access the file directly. You must connect to the database through the server and instance. To debug, I use SQL Server Management Studio. SSMS login window will show server and instance name which should be used in the c# connection string. The login window also shows Window Credental which in connection string is equivalent to Integrated Security = true and uses the users (or group) windows credential.
@Igor the solution there is to use plain ado.net, which I'm aready doing.
@jdweng I'm not using the (localdb) it's simply an SQLServer instance running on localhost
For a connection to work the local machine and remote machine has to have same credentials. Usually I will make the database credentials a Window User Group and then put users into the group. The Group has to be assigned on both local and remote machines. A company usually has Group Policy setup which can be used for the database credentials.
@jdweng i'ts 2 completely diferent servers, with diferent credentials. Completely diferent connectionStrings. It's just that when I use the local server the error does not happen
Use same serve/instance as shown in the SSMS login window. Window should show Window Credential. Then add to connection string Integrated Security = true and remove the username/password from connection string.
I'm not using integrated security in any of them. It's not even enabled
Just to clarify, the exception occurs midway of the execution. Some querys execute sucessfully and then one does not
Integrated security = true just means you are using the user login credentials which in SSMS is shown as Windows Credential.
The same queries should be tested in SSMS which gives better error messages. I suspect some of your tables have different credentials and SSMS will indicate these errors so you can fix.
how can i check if a table has diferent credentials? Why would that happen only remotely?
Another piece of information is that I'm always using the sa user
I'm always using the sa user this is a very bad habit that exposes you to hacking. Never use that account in application code. As for what's wrong - you have to provide information in the question itself. SQL Account authentication obviously works otherwise thousands of developers would have noticed 23 years ago.
@pitermarx post your code, the connection string (without the password), the line that throws and the full exception string, not just the message part. You can easily get that with Exception.ToString() or by clicking on the Copy Details link in the exception popup. The full text includes any inner exceptions and the call stack that led to the exception
@pitermarx as for the duplicate, it says to use a different connection. EF uses ADO.NET underneath, so using the ADO.NET classes alone wouldn't fix the problem.
I encounter the same issue when using "ALTER LOGIN [sa] WITH DEFAULT_LANGUAGE = us_english" : the command works but the subsequent Sql command raises this same exception. Maybe because an important data has been altered, Login in my case, Database is your case
After a couple of hours of trial and error I got to a minimal piece of code that reproduces the error
string dbName = "TESTDB";
Run("master", $"CREATE DATABASE [{dbName}]");
Run(dbName, $"ALTER DATABASE [{dbName}] COLLATE Latin1_General_100_CI_AS");
Run(dbName, "PRINT 'HELLO'");
void Run(string catalog, string script)
{
var cnxStr = new SqlConnectionStringBuilder
{
DataSource = serverAndInstance,
UserID = user,
Password = password,
InitialCatalog = catalog
};
using var cn = new SqlConnection(cnxStr.ToString());
using var cm = cn.CreateCommand();
cn.Open();
cm.CommandText = script;
cm.ExecuteNonQuery();
}
The full stacktrace is
Unhandled Exception: System.Data.SqlClient.SqlException: Resetting the connection results in a different state than the initial login. The login fails.
Login failed for user 'user'.
Cannot continue the execution because the session is in the kill state.
A severe error occurred on the current command. The results, if any, should be discarded.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
...
If I change the first Run(dbName... to Run("master"... it runs fine.
So it's related to running ALTER DATABASE in the context of the same database
maybe a new question with this minimal example is best...
https://stackoverflow.com/questions/63726424/system-data-sqlclient-sqlexception-after-create-alter-print
It's not an answer to my question, but I worked around the issue by not disposing the SqlConnection but reusing it.
I still do not understand the problem
That's almost as bad as using sa. You're now accumulating locks on any tables you use, blocking other connections. You haven't posted any code or even the full exception so it's impossible to understand the problem
The one thing this shows though is that the code you use to create connections does something strange.
What do the two connection strings look like? What SQL Server editions and versions do you use? ADO.NET pools connections and reuses them. Each time you close/dispose a connection it's reset and put back in the pool. Connections are pooled by connection string and the Windows account if Windows Authentication is used. An error about resetting the connection suggests pooling got mixed up (unlikely, otherwise you'd see a lot of similar questions) or that something changed in the remote server. Different databases perhaps? Switch to single-user mode? A user-instance database?
@PanagiotisKanavos thanks for the comments. I did not post the code because it's a big codebase and I'm not sure what is causing the issue. The code to create the connection is as simple as new SqlConnection(connectionString); and then the Open()
@pitermax the relevant code is only a couple of lines. Again, if a simple connection string caused such problems a lot of people would have noticed. Neither SQL Server nor ADO.NET are broken
On the other hand, using sa is broken any way you look at it. That's why it's disabled by default too - even if you use SQL Accounts it's better to use a new account with sysadmin rights than leaving the well-known sa account active
I'm not saying ADO.NET is broken. I'm trying to understand the problem.
I also had the idea that the connections were already polled.
Locally it's a SQL2016 express and remotely too.
The options you are giving are
Pooling got mixed up.
Something changed in the remote server.
Diferent databases. I'm doing multi-database queries both remotely and locally
Switch to single-user. Are you suggesting I change to single-user?
User-instance database. I'm not using this feature. Are you suggesting I enable it?
I'd suggest reading the possible duplicate again because you seem to be doing exactly the same thing - creating a new database. The duplicate uses EF migrations, you're using DbUp. Which means a connection to the same server could end up trying to log into different databases from one phase to the next.
@PanagiotisKanavos thanks for the help. I created a new question, with a code example and more focused questions
https://stackoverflow.com/questions/63726424/system-data-sqlclient-sqlexception-after-create-alter-print
|
Hi !! My name is Dipendra Bharati. I go by Dibs. I graduating this semester. I am taking 5 classes. I have been applying for internships and jobs. I plan on doing well in this class and learning a lot.
|
package com.testwithspring.master.testcontainers;
import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.testcontainers.containers.BrowserWebDriverContainer;
import static org.assertj.core.api.Assertions.assertThat;
/**
* This example demonstrates how we can run a Selenium WebDriver
* container with JUnit 5 by using a custom JUnit 5 extension.
*/
@ExtendWith(TestContainersExtension.class)
@DisplayName("Run a Selenium WebDriver container")
class SeleniumContainerExtensionTest {
private static BrowserWebDriverContainer chrome = new BrowserWebDriverContainer()
.withDesiredCapabilities(DesiredCapabilities.chrome());
@Test
@DisplayName("Should return the correct title of the course's website")
void shouldReturnCorrectTitleOfCoursesWebsite() {
RemoteWebDriver driver = chrome.getWebDriver();
driver.get("https://www.testwithspring.com");
String title = driver.getTitle();
assertThat(title).isEqualTo("Test With Spring Course — Save Time by Writing Less Test Code");
}
}
|
Panel seal and support structure for fiber optic cable
ABSTRACT
A tubular member having an O-ring seal on a shoulder is locked in a panel opening with a nut. An elastomeric sleeve is bonded to an extended sleeve portion of the tubular member. Two elastomeric mirror image inserts forming one or more fiber optic cable cavities are assembled around the cables and inserted into engagement with the elastomeric sleeve internal surface. A hose clamp compresses the elastomeric sleeve against the elastomeric elements, firmly clamping the elements and the cables in place.
The present invention relates to an interface structure between a panel and fiber optical cable passing through the panel.
Fiber optic cables include terminating connectors at the cable ends. The terminating connectors connect the cable to equipment which receive or transmit signals on the cable. These connectors tend to be relatively bulky and considerably larger than the diameter of the fiber optic cable.
A problem in installing such terminated cables in equipment housings occurs when it is desired to hermetically seal the housing from the ambient environment. It is usually necessary to install the terminated end of the cable through an opening in the housing wall. To pass the terminated end through the housing wall requires a relatively large opening, as compared to the cable diameter, to accommodate the connector and, therefore, would not provide a good seal between the cable and wall. In this case, disassembly of the connector from the cable is required. In some cases, however, the installation of a disassembled terminated end into the housing is not always possible; due to the relatively small space present in some housings which does not lend itself to easy reassembly of the terminating connector onto the cable end. In this latter instance the terminated end generally is required to be passed through the housing wall. Present designs and adaptors for coupling the fiber optic cable to the housing wall in such cases do not provide good sealing engagement between the cable and the housing wall or provide good strain relief for the cable.
A panel seal and support structure for a fiber optic cable passing through an opening in a panel, according to the present invention, comprises a tubular member having first and second ends. Means are coupled to the member for securing the member at the first end to the panel at the opening. An elastomeric sleeve is secured to the second end. First and second elastomeric elements are adapted to be closely received in the sleeve and abut along facing surfaces. The interface of the facing surfaces forms at least one aperture of a given dimension for closely receiving the cable. Clamp means are engaged with the sleeve and adapted to clamp the sleeve to the elements and tend to thereby reduce the size of the aperture. The resulting structure can provide a hermetic seal between the cable and the panel and also strain relief and support for the cable at the panel.
In the drawings:
FIG. 1 is an end view of the panel seal and support structure according to one embodiment of the present invention; and
FIG. 2 is a sectional view of the structure of FIG. 1 taken along lines 2--2.
In FIGS. 1 and 2, a pair of predetermined fiber optic cable assemblies 10 and 12 are shown supported by a panel seal and support structure 14 and passing through an opening 16 in a panel 18. Panel 18 is one wall of a housing (not shown) having an interior volume 19 which is desired to be sealed from the ambient environment 21.
Fiber optic cable assemblies 10 and 12 are terminated with terminations 20 and 22, respectively. The terminations 20 and 22 are conventional devices (which need not be described in detail herein) connected to the respective cables 24 and 26 of cable assemblies 10 and 12. The terminations 20 and 22 are considerably larger than the diameters of the respective cables 24 and 26. However, the terminations 20 and 22 are each sufficiently smaller than the diameter of the opening 16, which may be a circular hole, so that they may easily pass through the opening 16.
The support structure 14 includes a tubular member 28, a nut 30, attached to threads 32 on the external surface at one end of the member 28, an annular shoulder 34 approximately midway along the length of member 28, and a sleeve portion 36 on the end of member 28 opposite the threaded end. The threads 32 of the member 28 extend beyond the panel 18. Surface 37 at the midsection of member 28 is closely received by the opening 16 in panel 18. Annular O-ring groove 38 is in shoulder 34 and faces surface 35 of the panel 18. O-ring 40 is in groove 38. The O-ring 40 has a diameter sufficiently large so it protrudes beyond groove 38 and engages surface 35, sealing the interface between shoulder 34 and the panel 18 surface 35. The nut 30 threaded onto threads 32 of member 28 tightly clamps the panel surface 35 against the O-ring 40, locking and sealing member 28 to panel 18.
The internal diameter at surface 42 of member 28 is sufficiently larger than either of the terminations 20 and 22 of the cables 10 and 12 permitting those terminations to pass therethrough, for example, from left to right of the drawing.
An elastomeric sleeve 44, which may be rubber or a thermoplastic material, is closely received over and securely bonded to the outer surface of sleeve portion 36 of member 28. One bonding material may be cyanacrylate glue. The glue securely bonds the entire periphery of one end of the elastomeric sleeve 44 to the tubular member 28 portion 36 to form a hermetic seal therebetween. The sleeve 44 has a portion 46 which extends beyond the end of the member 28. The sleeve 44 is sufficiently flexible to readily expand or contract upon application of force, but is sufficiently high in strength to provide cable support and strain relief, as will be described below. Materials for such purposes are well known.
The fiber optic cable assemblies 10 and 12 are passed through the combined internal openings of the tubular member 28 and the elastomeric sleeve 44 into the interior housing cavity 19 containing equipment to which the terminations 20 and 22 are to be attached.
The cables 24 and 26 are securely fastened to the elastomeric sleeve 44 by two elastomeric inserts 50 and 52, FIG. 1, and a conventional hose clamp 64. Inserts 50 and 52 each comprise like mirror image semicircular cylindrical elastic elements having a flange 62 extending around the periphery of sleeve 44 at end 63. The inserts 50, 52 may be made of rubber, thermoplastic or other relatively stiff, compressible material. The inserts 50 and 52 each have facing elongated channel-like recesses 54", 56" and 54', 56', respectively, which together form circular cylindrical openings 54 and 56 for receiving the respective cables 24 and 26. One-half of the openings 54 and 56 are formed by the semicircular cylindrical recesses 54', 56' in the insert 52 and by like mirror image recesses 54", 56" in the insert 50. The inserts 50 and 52, when joined at the interface 58 therebetween, form a circular cylindrical plug-like member having two circular cylindrical conduits or openings 54 and 56. The mating interface 58 between the facing surfaces of the two inserts 50 and 52 may be planar. While two openings 54 and 56 are shown for the two corresponding cables 24 and 26, more of fewer openings may be provided in accordance with a given implementation.
The elastomeric inserts 50 and 52 are assembled by aligning the insert recesses 54', 54" and 56', 56" over the respective cables 24 and 26. The inserts are then held in abutting facing relation outside the extended end of sleeve 44. Then the elements, with the cables 24, 26 clamped manually therebetween, are slid in the direction 60, FIG. 2, into the internal cavity of the elastomeric sleeve 44 until the end flanges 62 of elements 50 and 52 abut the extended edge of the elastomeric sleeve 44, as shown. The inserts 50 and 52 together form a circular cylinder which is closely received within or are in interference fit with the internal diameter of the elastomeric sleeve 44. The inserts 50 and 52 are easily attached to the cables 24 and 26 since they are separate pieces and are placed in facing mirror image fashion over the cables 24 and 26 outside the elastomeric sleeve 44 and then slid along the cables until the elements and cables of sleeve 44 are engaged as shown in FIG. 2. The sleeve 44 may be stretched slightly during the insertion of inserts 50, 52 thereto.
The hose clamp 64 is placed over the outer surface of the elastomeric sleeve 44 in an area surrounding the inserts 50 and 52 and tightened, compressing somewhat the elastomeric sleeve 44 an amount suffficient to reduce the diameter of the combined inserts 50 and 52. This action forms a hermetic seal between elements 50, 52 and sleeve 44 and reduces the diameter of the openings 54 and 56 so that they engage the cables 24 and 26 hermetically sealing the cables to the elements 50, 52. Tightening the hose clamp 64 firmly clamps the cables 24 and 26 to elements 50, 52 with relatively high friction engagement. The inserts 50 and 52 are thus compressably attached to the cables. This compression induces friction forces sufficient to provide strain relief between the panel seal and support structure 14 and the cables 24, 26. That is, tensile stresses on the cables 24 and 26, which are external to the panel 18 and sleeve 44, are absorbed by the seal and support structure 14. This action prevents transmittance of such stresses to the terminations 20 and 22, preventing inadvertent tearing loose of the terminations by such stress.
The cable assemblies 10 and 12 may be easily removed by loosening the hose clamp 64 and grasping the flanges 62 of the elements 50, 52, sliding the elements 50, 52 in the direction opposite direction 60 until free of sleeve 44 and thereby enabling the elements to be separated, freeing the cables.
The panel seal and support structure 14 may be made in a variety of diameters corresponding to different size openings 16 in a panel 18. These different sized structures 14 may accommodate cables 24 and 26 of different diameters. The resulting structure provides a hermetic seal between the ambient environment 21 and the interior volume 19 to be sealed. The terminations 20 and 22 readily pass through the internal opening of the elastomeric sleeve 44 and the tubular member 28 to permit ease of assembly of the cable assemblies to equipment in close quarters, for example, a small housing of which panel 18 is part. This eliminates the need to disassemble the terminations 20 and 22 from the cables 24 and 26. Although the cable assemblies are securely fastened to the panel 18, they are readily released and disassembled from panel 18 without disturbing the terminations 20, 22.
What is claimed is:
1. A panel seal and support structure for a fiber optic cable passing through an opening in said panel comprising:a tubular member having first and second ends; means for securing said first end of the tubular member to said panel at said opening; an elastomeric sleeve secured to said second end; first and second elastomeric elements abutting along mating facing surfaces and closely received in said sleeve, the interface of said surfaces forming at least one aperture of a given dimension for closely receiving said cable; and clamp means engaged with said sleeve for clamping said sleeve to said elements and compressing the elements to friction ally engage the received cable.
2. The structure of claim 1 wherein said means for securing includes means for hermetically sealing said tubular member to said panel.
3. The structure of claim 1 wherein said sleeve is bonded to said second end to form a hermetic seal thereto.
4. The structure of claim 1 wherein said first and second elastomeric elements form a plurality of cable receiving apertures at said interface.
5. A panel seal and support structure for a fiber optic cable passing through an opening in said panel comprising:a hollow member having a threaded exterior surface at one end adapted to pass through said opening, and a cylindrical sleeve portion at a second end opposite the one end, said member having an annular portion between said ends of greater diameter than said threaded exterior surface forming a shoulder which is adapted to abut a surface of said panel when said threaded surface passes through said opening; an elastomeric sleeve secured to said sleeve portion of said member; first and second elastomeric members closely received within said elastomeric sleeve, said elastomeric members abutting along facing surfaces thereof, said facing surfaces forming at least one opening for closely receiving a portion of said fiber optic cable; and clamp means engaged with said elastomeric sleeve for resiliently clamping said sleeve against said elastomeric members and said elastomeric members against said received cable.
6. The structure of claim 5 wherein said elastomeric members form a cylindrical element, said element including a shoulder portion abutting an edge of said elastomeric sleeve.
7. The structure of claim 5 wherein said shoulder has an annular groove, said structure further including sealing means in and extending from said groove for sealing engagement with said panel surface.
8. The structure of claim 5 wherein said elastomeric sleeve is bonded to said sleeve portion of said hollow member to form a hermetic seal therebetween.
|
Why does the equation $x = 1$ represent a line in a 2-dimensional coordinate system?
I'm posting a question because I was curious about something while studying linear algebra.
As we all know, $x = 1$ is a point in a one-dimensional coordinate system. I understand this part.
But why does $x = 1$ represent a line in two dimensions?
Is it simply defined that way?
If anyone knows anything about this, please help.
It may seem trivial, but I feel really uncomfortable and think about it every day.
Thank you.
A point in 2d space has two coordinates. One of those coordinates is 1. The other coordinate can be anything. What does the collection of those points look like?
Saying the line is $x=1$ is an abuse of language. It makes more sense if you write $l={(x,y)\in\mathbb R^2: x=1}$. Then all points $(1,y)$ are in the set and you get a vertical line. Likewise, $s={x\in\mathbb R: x=1}$ only has one solution so it represents the single point $1$ on the number line.
Your problem probably comes from the fact that you don't really know what a two-dimensional coordinate system is and how a line in a two-dimensional coordinate system is mathematically defined.
It is linear algebra closely associated with elementary geometry.
First we define $$E=\mathbb R \times \mathbb R=\{(x,y): x\in \mathbb\ R,y\in \mathbb R \}$$
We multiply an element $\lambda$ of $\mathbb R$ by an element $(x,y)$ of E like this $$\lambda(x,y):=(\lambda x,\lambda y)$$
For example $$5(0,1)=(5\times 0,5\times 1)=(0,5)$$
We're adding two elements of $E$ like this $$(\color{green}1,0)+(\color{green}0,5):=(\color{green}{1+0},0+5)$$
You can think of an element of E as a point or a vector whichever makes the most sense to you.
Then, we define à line in $E$ by a part of $E$ of the form $$l=a+\mathbb R u$$
$\mathbb R u$ is called the direction of $l$.
Here, with $a=(1,0)$ and $u=(0,1)$, you obtain
$$l=(1,0)+\mathbb R (0,1)=\{(x,y)\in \mathbb R \times \mathbb R: \exists \lambda \in \mathbb R, (x,y)=(1,0)+\lambda (0,1)\}$$ $$=\color{cyan}{\{(1,\lambda): \lambda \in \mathbb R\}}$$
Note that you asked yourself a good question to study linear algebra further.
The graph is all the points $(x,y)$ such that $x=1$. There is no constraint on $y$, so we plot all the points that have $1$ as the first coordinate. This results in the graph you show.
Made community wiki because it is the same approach as @Xander Henderson's comment, which came in as I was writing this.
As we all know, $x = 1$ is a point in a one-dimensional coordinate system. I understand this part.
Is it though? What if I write $\{a\in\mathbb{R}\ |\ x=1\}$. Is that a point? No, in fact it doesn't even make much sense.
What I'm trying to say, is that the equation "$x=1$" requires a context, on its own it is meaningless. So
$$\{(x,y)\in\mathbb{R}^2\ |\ x=1\}$$
indeed is a line, because $x$ is fixed, and only $y$ varies. So for example $(1,0)$ belongs to it, so does $(1,5)$ and $(1,-\pi)$, but not $(0,0)$.
However in say 3d space
$$\{(x,y,z)\in\mathbb{R}^3\ |\ x=1\}$$
it won't be a line, it will be a plane. Since now $x$ is fixed and $y,z$ varies.
Context. It changes everything.
|
Hi.
Hello, how can I assist you?
I would like to book a ticket from ORD to DFW, can you please help me with that?
Sure, may I know the travelling dates?
The travel dates are from 05/14 to 05/16.
Do you have any connection limit?
I need a flight with 1 connection limit.
Is there any other requirements?
No.
May I know your name?
Larry Green here.
Sorry, no flights found with your chosen dates.
That's ok, thank you for your help.
Thank you for opting us.
|
glmnet (2.0-5)
8 users
Lasso and Elastic-Net Regularized Generalized Linear Models.
http://www.jstatsoft.org/v33/i01/.
http://cran.r-project.org/web/packages/glmnet
Extremely efficient procedures for fitting the entire lasso or elastic-net regularization path for linear regression, logistic and multinomial regression models, Poisson regression and the Cox model. Two recent additions are the multiple-response Gaussian, and the grouped multinomial. The algorithm uses cyclical coordinate descent in a path-wise fashion, as described in the paper linked to via the URL below.
Maintainer: Trevor Hastie
Author(s): Jerome Friedman, Trevor Hastie, Noah Simon, Rob Tibshirani
License: GPL-2
Uses: foreach, Matrix, lars, survival, knitr
Reverse depends: aBioMarVsuit, AdapEnetClass, anoint, bapred, bigdata, bigmatrix, BigTSP, BioMark, c060, cosso, covTest, DivMelt, DTRlearn, elasso, EstHer, fastVAR, FindIt, glmnetcr, glmvsd, Grace, hdlm, HiCfeat, huge, InvariantCausalPrediction, ipflasso, KsPlot, MESS, mht, MMS, MNS, MRCE, msr, netgsa, oblique.tree, pacose, parcor, PAS, polywog, pre, PRIMsrc, prototest, qut, refund, regsel, relaxnet, roccv, RSDA, RTextTools, RVtests, selectiveInference, SIMMS, SIS, SOIL, SparseLearner, sparsenet, TextRegression, widenet
Reverse suggests: BiodiversityR, broom, bWGR, caret, caretEnsemble, CompareCausalNetworks, EBglmnet, eclust, emil, fbRanks, FeatureHashing, FRESA.CAD, fscaret, ggfortify, grpreg, heuristica, LSAmitR, medflex, MESS, mlr, ModelGood, mplot, ordinalNet, plotmo, pmml, ppstat, pulsar, randomForestSRC, sAIC, simputation, simulator, SPreFuGED, sqlscore, stabs, STPGA, SuperLearner, text2vec, varbvs
Reverse enhances: coefplot, stabs
Released about 1 year ago.
28 previous versions
Ratings
Overall:
4.0/5 (5 votes)
Documentation:
3.0/5 (3 votes)
Log in to vote.
Reviews
Related packages: ahaz, CoxBoost, gbm, glmpath, ipred, mboost, pamr, party, penalized, rpart, LogicReg, randomForestSRC, ranger, rgp, RSNNS, rminer, bigRR, mlr, maptree, evtree(20 best matches, based on common tags.)
Search for glmnet on google, google scholar, r-help, r-devel.
Visit glmnet on R Graphical Manual.
|
Is there any effort getting this into fdroid already?
Inclusion policy: https://f-droid.org/en/docs/Inclusion_Policy/
Contributing: https://gitlab.com/fdroid/fdroiddata/blob/master/CONTRIBUTING.md
Not at the moment. We're relying on google services for the pushnotifications, so complying to the fdroid policy is a big effort.
If you want, you can create a PR for this.
I haven't looked into the source so creating a PR for this is a bit over my head currently. Perhaps you can take into account making the dependency on GSF optional. Signal has done so as well. They just have different demands hence Signal isn't in fdroid.
We currently do not have the capacity in our development team to make this major change.
|
delete specific value in column Realm Database
Can I delete a value from a column in realm database?
Like this in sqlite:
DELETE FROM table_name WHERE some_column=some_value;
I tried the RealmResults remove method but it's only taking a position or an object.
For example, I want to delete "A" in alphabet column from table.
You can query for the data that you want deleted and then call deleteAllFromRealm on the result. Like so
realm.beginTransaction();
realm.where(Foo.class).equalTo("fieldName", "value").findAll().deleteAllFromRealm();
realm.commitTransaction();
thanks
i think that will work,but i don't see deleteAllFromRealm.
i use 0.87.5 version
|
[RFC][Tracking Issue][AMP] Tracking Issue for Mixed Precision Pass
This issue tracks work on supporting mixed precision within TVM.
RFC: https://github.com/apache/tvm-rfcs/pull/6
[x] Write initial mixed precision pass (https://github.com/apache/tvm/pull/8069)
[x] Audit schedules for support of accumulation dtypes (should be fixed with https://github.com/apache/tvm/pull/8517)
[ ] Benchmark accuracy loss on select models
[ ] Extend support for CUDA backend (https://github.com/apache/tvm/issues/8294)
[ ] Extend support for Vulkan backend (https://github.com/apache/tvm/issues/8295)
[ ] Extend pass to support Algebraic Data Types in Relay
[ ] Ensure bfloat16 works with pass on select GPUs
Tasks which may help:
[ ] Get dedup extraneous casts pass completed and refactor existing pass (https://github.com/apache/tvm/pull/8081)
Benchmarking improvements from pass: https://docs.google.com/spreadsheets/d/12lgyfuHaRS-X4uG-1iQOV8oAuPpuVAbspcmkOSPRFHQ/edit?usp=sharing
cc @Lunderberg
cc @masahi
I've hit a nasty issue. On CPU targets, our sorting related ops are implemented in C++ https://github.com/apache/tvm/blob/main/src/runtime/contrib/sort/sort.cc#L436, and they don't support fp16. So ops like topk, argsort, nms etc do not work on fp16 + cpu target combination. We can add all of them to the NEVER list, but then that would introduce unnecessary cast for GPU targets because sorting on GPU is implemented in TIR so it doesn't have issues with fp16.
Maybe we need to add a specialized CPU sort for fp16 or rewrite CPU sort in TIR...
It looks like transformer like models have many softmax ops that introduce a lot of casting before / after them, like https://gist.github.com/masahi/0d7d96ae88722b616a906cec2054559e#file-transformer-txt-L137-L143
The fact that softmax and the following cast to fp16 are not fused surprised me. This is because the op pattern for softmax is kOpaque, https://github.com/apache/tvm/blob/66ac4705aae9bec92047920c8a9273693cd48c44/python/tvm/relay/op/nn/_nn.py#L42. The cast overheads are big if they are not fused, so we are leaving a lot of perf on the table.
@yzhliu Is there a reason softmax op pattern cannot be OUT_ELEMWISE_FUSABLE?
@AndrewZhaoLuo What is our goal wrt mixed_type accumulation? Assuming we do find cases where mixed accum is beneficial, how are we going to decide when to enable / disable it? Given that currently we can only choose one or the other per op, https://github.com/apache/tvm/blob/f4f525dab86af653636bce95ce3609288fbaa587/python/tvm/relay/transform/mixed_precision.py#L167-L168
Yeah the issue behind creating defaults is that we cannot create defaults that work best for every situation. This is especially true since whenever we want speed we trade accuracy which can sometimes become a problem.
For the defaults I envision that for most ops we don't accumulate to FP32. For some ops like the global pools and sums we might turn it on. Really the best way to determine the criteria is to do a lot of the work you've been doing in trying out different models in different applications and seeing what needs to be turned on and off.
That being said, this is really designed to be a tool which requires the user sometimes to go back and modify the default values provided to either get more speed if their model can afford it, or accuracy if they need it. It requires investigation and I don't think we can probably hit all cases well. A tutorial here would help (which is on my long list of TODOs).
Finally, while things are done on a per-op basis, the actual mixed precision function can look at some parts of the relay call like the attributes or the node or the input tensor sizes. Therefore we can be smart about the quantization (e.g. for global pooling, only accumulate in fp32 if the input to output reduction is large enough). Again, a tutorial or example would help flesh this out.
@AndrewZhaoLuo I briefly looked at bfloat16. While fp16 vs bf16 makes no difference for the conversion pass, it seems it is going to take a lot of effort to compile and run a bf16 model end to end, for at least two reasons:
The constant folding pass doesn't work on bfloat16 input
Numpy doesn't understand bfloat16, but some topi schedules (winograd conv) try to create a numpy array of type out_dype, which in this case bfloat16.
Since tensorcore can natively run bf16 workloads at the same rate as fp16, and bf16 on x86 servers are becoming a thing, it would be nice to have a good support for bf16 across the stack in the future.
|
facebook error when trying to "share" tab
i was following the tab tutorial here which seemed excellent until i uploaded to my server and i get the following error
API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.
here is my code
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>flash</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css" media="screen">
html, body { height:100%; background-color: #ffffff;}
body { margin:0; padding:0; overflow:hidden; }
#flashContent { width:100%; height:100%; }
</style>
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.6.1/jquery.min.js" type="text/javascript"></script>
</head>
<body>
<div id="fb-root"></div>
<script src="https://connect.facebook.net/en_US/all.js"></script>
<script>
FB.init({
appId : '132536290178355',
});
</script>
<script type="text/javascript">
$(document).ready(function(){
$('#share_button').click(function(e){
e.preventDefault();
FB.ui(
{
method: 'feed',
name: 'HyperArts Blog',
link: 'http://mytablink/',
picture: 'http://www.hyperarts.com/_img/TabPress-LOGO-Home.png',
caption: 'I love HyperArts tutorials',
description: 'The HyperArts Blog provides tutorials for all things Facebook',
message: ''
});
});
});
</script>
<img src = "<?=base_url()?>/imgs/share_button.png" id = "share_button">
(i extracted this from codeigniter view thats why am using base_url)
should i set something in the developer app? or set something in the syntax?
I have run into this problem a number of times - only on page tabs, this code works fine in canvas apps - I dont know the solution unfortunately but this is a workaround I use. Place this in a javascript function:
<?
$ch_title=urlencode($SHARE_TITLE);
$ch_url=urlencode($FACEBOOK_REDIRECT_URI);
$ch_summary=urlencode($share_text);
$ch_image=urlencode($FACEBOOK_APPLICATION_BASEURL.'images/hare-image.png');
?>
window.open('http://www.facebook.com/sharer.php?s=100&p[title]=<?php echo $ch_title;?>&p[summary]=<?php echo $ch_summary;?>&p[url]=<?php echo $ch_url; ?>&p[images][0]=<?php echo $ch_image;?>', 'sharer', 'toolbar=0,status=0,width=548,height=325');
This works fine with one annoying exception: its a javascript popup window. :/
But its the only way I've been able to find to share a URL from a page tab.
|
Property $x(t)\otimes \delta (t-t_0)=x(t_0)$
My professor said that:
$$x(t)\otimes \delta (t-t_0)=x(t_0)$$
How can I prove it? I tried to apply the definition of convolution $q(x)w(x)=\int_{-\infty}^{+\infty}{q(\tau)w(x-\tau)d\tau}$:
$$x(t)\otimes \delta (t-t_0)=\int_{-\infty}^{+\infty}{x(\tau)\delta (t-t_0-\tau)d\tau}$$
Then I applied the sifting property $\int_{-\infty}^{+\infty}{q(x)\delta(x-a)dx=q(a)}$:
$$x(t)\otimes \delta (t-t_0)=x(t_0+\tau)$$
What is wrong?
Thank you very much.
Note that the result you get cannot depend on the integration variable $\tau$ that you have integrated over. You probably picked the wrong "$a$": you should have taken $a = t-t_0$ not $a = t_0-\tau$.
Hello @Winther. What do you mean? I have $\int_{-\infty}^{+\infty}{x(\tau)\delta (t-t_0-\tau)d\tau}=x(t_0+\tau)$, this is the application of sifting property thus should be right.
$$\int_{-\infty}^{+\infty} x(\tau) , \delta (t-t_0-\tau) , d\tau = x(t_0-t)$$
Note that $\delta(-x) = \delta(x)$ so your integral (which is over $\tau$) is $\int_{-\infty}^\infty x(\tau) \delta(\tau - \color{red}{(t-t_0)}){\rm d}\tau$. Now use what you know about the $\delta$-function.
Thank you so much @Winther.
$\tau$ is your integration variable, so it should disappear in your result. And your convolution is not defined properly. I think what is meant is you look at the "functions"
$$
f(t) = x(t), \quad g(t) = \delta(t - t_{0})
$$
and then at the convolution $(f \otimes g)(t)$.
I would be surprised if the result was independent of $t$ as your professor said, since if we do not shift by $t_{0}$ we get
$$
(x \otimes \delta )(t) = \int_{\mathbb{R}} x(\tau) \delta(t - \tau) d \tau = x(t),
$$
by the definition of the $\delta$ distribution and its "symmetry" $\delta(-x) = \delta(x)$.
For the more general case we have
\begin{align*}
(f \otimes g)(t) &= \int_{\mathbb{R}} x(\tau) \delta ((t - \tau) - t_{0}) d \tau = \int_{\mathbb{R}} x(\tau) \delta ((t - t_{0}) - \tau) d \tau \\
&= \int_{\mathbb{R}} x(\tau) \delta (\tau- (t - t_{0})) d \tau= x(t - t_{0}).
\end{align*}
|
Tax treatment of Giving loan to a relative overseas - what forms to file
I have a relative overseas who is asking for a loan of $100k. I would like to know the tax implications and what paperwork needs to be filed when the loan is repaid back to me. Should I declare it as a gift? In what form do I declare? This says:
For those receiving financial gifts through an international money transfer, you won’t pay taxes, but you may be required to report the gift to the IRS. If the gift exceeds $100,000, you will need to fill out an IRS Form 3520.
Do I need to make any declaration when I transfer the money out? Or is the declaration made when the funds are repaid?
Do I have to file Form 709 and pay gift taxes even though this is a loan?
Thanks.
You need to create a paper trail documenting that the $100K is a loan, with appropriate documentation such as a loan agreement, promissory note, interest rate being charged, loan repayment terms etc. You and the borrower should each have a fully executed copy of all this paperwork. You should also send the money via regular banking channels (including various money transfer services such as Transferwise or Xoom) and not through hawala channels.
With loans to relatives, and especially with relatives who need money in an emergency, these details can be left till after the immediate transfusion of cash has been made, and there can be sticking points such as you might not want to say you are charging interest (whether paid monthly or quarterly or annually or as a lump-sum along with the principal, as per the loan agreement) on a loan to immediate family members, but this can be handled by you gifting the interest to the borrower each year (and if you prefer, the borrower sending the money back you you as interest). Since the annual interest on $100K should be far less than the annual exemption for gift tax, no Form 709 need be filed. Be that as it may, the annual imputed interest due is taxable income to you for that year, and should be reported as interest income on each year's tax return. When the loan is paid off, you don't need to do any reporting; your bank will report that you received $100K or $100K+, and you have the paperwork to prove that it is merely repayment of a loan; it need not be reported on a tax return, and no tax is due.
Be aware that in some countries, repayment of such loans is allowed only in the currency of the foreign country and only into the lender's bank account in that country. Thus, if your relative is in such a country, you will need to establish such an account if you don't have it already, and you will bear the exchange rate risk. That US$100K might have become a loan of MN$300k, and be paid back as MN$300K, and when you bring the money back into the US, you might be getting back (say) only US$90K instead of the US$100K that you loaned because the exchange rate between US$ and MN$ changed in the interim.
so it looks like there are no IRS forms to file at all, but to keep things legit I should charge them a minimal interest rate and pay ordinary income tax on that? is that the TL;DR? the relative's home country is singapore fwiw.
No one gives a loan, because -- by definition -- loans are not gifts. Otherwise, they'd be gifts, not loans.
The interest that you earn on loans is income, and must be treated as such.
This should be a comment. Not an answer
@huyz sure it's an answer, since it says what to do with the interest on the loan.
|
<?php
namespace Oro\Bundle\UserBundle\Form\Handler;
use Doctrine\Common\Collections\ArrayCollection;
use Symfony\Component\Form\FormFactory;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\Form\FormInterface;
use Doctrine\Common\Persistence\ObjectManager;
use Pim\Bundle\UserBundle\Entity\UserInterface;
use Oro\Bundle\UserBundle\Form\Type\AclRoleType;
use Oro\Bundle\UserBundle\Entity\Role;
use Oro\Bundle\SecurityBundle\Acl\Persistence\AclManager;
use Oro\Bundle\SecurityBundle\Acl\Persistence\AclPrivilegeRepository;
class AclRoleHandler
{
/**
* @var Request
*/
protected $request;
/**
* @var FormFactory
*/
protected $formFactory;
/**
* @var FormInterface
*/
protected $form;
/**
* @var ObjectManager
*/
protected $manager;
/**
* @var AclManager
*/
protected $aclManager;
/**
* @var array
*/
protected $privilegeConfig;
/**
* @param FormFactory $formFactory
* @param array $privilegeConfig
*/
public function __construct(FormFactory $formFactory, array $privilegeConfig)
{
$this->formFactory = $formFactory;
$this->privilegeConfig = $privilegeConfig;
}
/**
* @param AclManager $aclManager
*/
public function setAclManager(AclManager $aclManager)
{
$this->aclManager = $aclManager;
}
/**
* @param ObjectManager $manager
*/
public function setEntityManager(ObjectManager $manager)
{
$this->manager = $manager;
}
/**
* @param Request $request
*/
public function setRequest(Request $request)
{
$this->request = $request;
}
/**
* Create form for role manipulation
*
* @param Role $role
* @return FormInterface
*/
public function createForm(Role $role)
{
foreach ($this->privilegeConfig as $configName => $config) {
$this->privilegeConfig[$configName]['permissions'] = $this->aclManager
->getPrivilegeRepository()->getPermissionNames($config['types']);
}
$this->form = $this->formFactory->create(
new ACLRoleType(
$this->privilegeConfig
),
$role
);
return $this->form;
}
/**
* Save role
*
* @param Role $role
* @return bool
*/
public function process(Role $role)
{
if (in_array($this->request->getMethod(), array('POST', 'PUT'))) {
$this->form->submit($this->request);
if ($this->form->isValid()) {
$appendUsers = $this->form->get('appendUsers')->getData();
$removeUsers = $this->form->get('removeUsers')->getData();
$role->setRole(strtoupper(trim(preg_replace('/[^\w\-]/i', '_', $role->getLabel()))));
$this->onSuccess($role, $appendUsers, $removeUsers);
$this->processPrivileges($role);
return true;
}
} else {
$this->setRolePrivileges($role);
}
return false;
}
/**
* Create form view for current form
*
* @return \Symfony\Component\Form\FormView
*/
public function createView()
{
return $this->form->createView();
}
/**
* @param Role $role
*/
protected function setRolePrivileges(Role $role)
{
/** @var ArrayCollection $privileges */
$privileges = $this->aclManager->getPrivilegeRepository()->getPrivileges($this->aclManager->getSid($role));
foreach ($this->privilegeConfig as $fieldName => $config) {
$sortedPrivileges = $this->filterPrivileges($privileges, $config['types']);
if (!$config['show_default']) {
foreach ($sortedPrivileges as $sortedPrivilege) {
if ($sortedPrivilege->getIdentity()->getName() == AclPrivilegeRepository::ROOT_PRIVILEGE_NAME) {
$sortedPrivileges->removeElement($sortedPrivilege);
continue;
}
}
}
$this->form->get($fieldName)->setData($sortedPrivileges);
}
}
/**
* @param Role $role
*/
protected function processPrivileges(Role $role)
{
$formPrivileges = array();
foreach ($this->privilegeConfig as $fieldName => $config) {
$privileges = $this->form->get($fieldName)->getData();
$formPrivileges = array_merge($formPrivileges, $privileges);
}
$this->aclManager->getPrivilegeRepository()->savePrivileges(
$this->aclManager->getSid($role),
new ArrayCollection($formPrivileges)
);
}
/**
* @param ArrayCollection $privileges
* @param array $rootIds
* @return ArrayCollection
*/
protected function filterPrivileges(ArrayCollection $privileges, array $rootIds)
{
return $privileges->filter(
function ($entry) use ($rootIds) {
return in_array($entry->getExtensionKey(), $rootIds);
}
);
}
/**
* "Success" form handler
*
* @param Role $entity
* @param UserInterface[] $appendUsers
* @param UserInterface[] $removeUsers
*/
protected function onSuccess(Role $entity, array $appendUsers, array $removeUsers)
{
$this->appendUsers($entity, $appendUsers);
$this->removeUsers($entity, $removeUsers);
$this->manager->persist($entity);
$this->manager->flush();
}
/**
* Append users to role
*
* @param Role $role
* @param UserInterface[] $users
*/
protected function appendUsers(Role $role, array $users)
{
/** @var $user UserInterface */
foreach ($users as $user) {
$user->addRole($role);
$this->manager->persist($user);
}
}
/**
* Remove users from role
*
* @param Role $role
* @param UserInterface[] $users
*/
protected function removeUsers(Role $role, array $users)
{
/** @var $user UserInterface */
foreach ($users as $user) {
$user->removeRole($role);
$this->manager->persist($user);
}
}
}
|
<IP_ADDRESS> wrote: By the way, when I think of shapeshifting, I have a difference from shapechanging. Shapechanging is you transform into something/someone, and have all their powers, but it doesn't change your DNA, and if a limb is cut off, it reverts to normal. Shapeshifting is you become what you transform into, down to DNA, but you keep your mind. Interesting ideas for abilities, but maybe too powerful.
|
Yellow Diamond's Pearl
"Yes, my diamond?"
- Pearl addressing
She is voiced by Deedee Magno-Hall, who also voices the Crystal Gems Pearl.
Appearance
Personality
Message Received
Season 2
* "Message Received" (debut)
Trivia
|
[02:24] <psuboy> Hi..I am installing straight xubuntu on an old windows xp machine with 20G Hard Drive. I want to delete all old partitions and create new ones...
[02:26] <psuboy> I selected manual partition...and want to create one for OS, and at least one for data...do I also need one for programs or will I use my OS partition for that
[02:26] <psuboy> any help is appreciated...
[02:27] <Guest62025> psuboy: with only 20G I would just let the install do the work...there isn't enough space there to have separate partitions for / and /home
[02:28] <psuboy> OK...so just do one partition for the whole deal...that is easier :-)...
[02:28] <psuboy> what about a 40G drive...
[02:28] <psuboy> I set up another machine...my first one with just one drive on that
[02:28] <psuboy> any thoughts?
[02:29] <Guest62025> psuboy: you will need a swap partition...but it should only be about 1.5 times ram, and the install will se tit up for you
[02:29] <Guest62025> psuboy: with a 40G I would make 15G for / and the rest for /home
[02:30] <psuboy> if I do advanced do I need to create my own swap also?
[02:30] <Guest62025> psuboy: although you could probably get away with 10G for /
[02:30] <psuboy> manual/ (advanced)
[02:30] <Guest62025> psuboy: yes...if you do manual you need to set aside something for swap
[02:30] <psuboy> do I call it /swap
[02:31] <psuboy> or does it need a specific name?
[02:31] <knome> psuboy, swap is not going to be formatted, it's a type of "filesystem"
[02:31] <Odin> psuboy: ...sorry...got dropped.
[02:31] <psuboy> ok...
[02:32] <psuboy> so I was asking about swap...knome is telling me that I do not need to format for swap ...I ma not sure I fully understand..is it going to b part of /
[02:33] <Guest48914> psuboy: no...swap is just a small section set aside...and it isn't formatted...it is just swap
[02:33] <Guest48914> psuboy: you mark it as swap and the install takes care of the rest.
[02:34] <th0r> finally...nickserv has it right <smile>
[02:34] <psuboy> is it part of the process after I name my partitions?
[02:35] <th0r> psuboy: yes and no...you don't ever access swap, it is used by the system. You don't format it, or write to it, and there isn't anything there for you to read either
[02:36] <th0r> psuboy: swap is used like an extension of ram on systems with small amounts of memory. When the memory starts to fill up, the system moves less used things onto the hard drive (swap) until they are needed.
[02:36] <psuboy> OK..So the install will just create it for me as part of it's process. I do not need to account for it? ie. it will be part of my 15G of space for Os
[02:37] <psuboy> yea...I know what it does...just not sure how to make sure I get it set up
[02:37] <th0r> psuboy: you will have to create three things...10g or so mounted at /, at least 1.5 times your memory size set aside for swap, and the rest will be available for /home
[02:37] <th0r> psuboy: you set it up just like any other partition...you will define the size, and then tell the install it is swap
[02:38] <th0r> psuboy: first, define /, then define swap, then whatever is left over can be used for /home
[02:38] <psuboy> ok..so i need to set up three.../ at 15G / at 1G and /home at 24G
[02:39] <th0r> psuboy: swap at 1G
[02:40] <th0r> psuboy: to give you some idea...I have tons of stuff installed and am using less than 7GB for /, so 10-15 should be plenty
[02:42] <psuboy> cool
[02:42] <psuboy> I set up a lamp server on an old desktop and it is working well...but I was thinking about redoing it and
[02:43] <psuboy> was wondering if it is worth it.I set up automatic partition on this machine..
[02:44] <th0r> psuboy: well, the main advantage to separating / and /home is that you can do a complete new install without losing any data or configs. In a server I am not sure how much that would b eworth
[02:56] <psuboy> I hear you thor...thanks for the help
[02:57] <psuboy> thank you to Odin/guest
[02:58] <th0r> psuboy: those were all me....nickserv didn't want to release my nick <smile>
[02:58] <psuboy> ok :-)
[02:59] <micahg> why does xubuntu recommend gnome-power-manager and not xfce4-power-manager?
[03:00] <micahg> *xubuntu-desktop
[03:43] <koko_> i have a problem, my i just installed xubuntu on my laptop, but i can't get a higher resolution that 800x600, can anyone provide a solution?
[03:53] <koko_> i have a problem, i just installed xubuntu on my laptop, but i can't get a higher screen resolution than 800x600, can anyone help?
[04:10] <Athan> Hello, I have an issue
[04:10] <Athan> I'm trying to install xubuntu x86 on my Dell Optiplex GX1
[04:10] <Athan> and whenever I try and go into the liveCD, It gives me a bug error
[04:10] <Athan> can anyone help me?
[04:56] <psuboy> anyone have some experience loading the correct video drivers?
[04:56] <maduser> the system should do it for you
[04:57] <psuboy> I loaded xubuntu...
[04:57] <maduser> you need download them through restricted drivers
[04:57] <psuboy> could not get it to view on screen unless I set it to basic vga
[04:57] <psuboy> hmmm...where I looked where restricted drivers are and did not see any
[04:58] <psuboy> said I am not using any...
[04:58] <maduser> what video card do have?
[04:58] <psuboy> intel 82830 cgc
[04:58] <psuboy> it is an inspiron 2600
[05:00] <maduser> use this http://ubuntuforums.org/archive/index.php/t-485171.html
[05:01] <maduser> larn how to backup and restore xorg.conf from the cli first before proceding
[05:01] <maduser> learn
[05:04] <psuboy> OK..
[05:04] <psuboy> it looks based on this that it did not help them much...
[05:05] <psuboy> I think I saw a few articles on line about editing the xorg.conf file with settings that people were very pleased with...
[05:06] <psuboy> I am a linux nubie...so sorry for basic questions..but if I edit this file don't I still need to load /install the proper driver
[05:06] <maduser> could copy one of those into your but, be ware if it dosn't work youll been in cli until you rstore a backup
[05:06] <maduser> i have done this before, but i know bash well
[05:06] <maduser> no
[05:07] <maduser> you also could look at this http://bbs.archlinux.org/viewtopic.php?id=61433
[05:46] <Murrlin> just wondering if there's a page about the system requirements (for installation, and general use, if seperate)?
[06:06] <sinjan> hi all
[06:51] <pteague> anybody know what package gstreamer-properties is in?
[06:59] <pteague> nm, found it :)
[08:03] <cdrew> hello
[08:03] <cdrew> and anyone help me with something?
[08:19] <jadez03> so i just got unreal tournament 2004 installed in xubuntu :D
[08:26] <Sacred_> :)
[11:07] <spuch1> i have a problem with thunar ,it can't list my local partitions in left pane as Nautilus does.can anyone help me?
[11:11] <knome> spuch1, with "local partitions" what do you exactly mean?
[11:30] <owen1> how to use console login instead of xdm/gdm/slim?
[11:31] <knome> owen1, one-time or for ever?
[11:46] <owen1> for ever
[11:46] <owen1> (until i'll change my mind(
[11:48] <knome> owen1, you can remove them (gdm/...) and you're left with a console login.
[11:49] <knome> owen1, you need to start the X session then by yourself, though.
[11:51] <SiDi> !update-rc.d
[11:51] <SiDi> owen1: check the man of update-rc.d
[11:54] <owen1> i'll take a look. thanks
[12:56] <psycho_oreos> anyone happen to have a weird issue with the mouse pointer not referring to the correct location? e.g. when trying to close a program, I have to select minimise to close, but to minimise I have to move more left of where the buttons are.. and trying to move the cursor at the end of the screen it seems to have some sort of barrier/limit
[12:58] <psycho_oreos> however if I move the mouse cursor to the edge on the left of the screen, the mouse cursor doesn't appear, so its not an issue with the monitor (when its LCD and I can easily set it to auto-adjust). however moving the mouse cursor to the edge on the right and before I can even get the mouse cursor there, there seems to be a block
[13:03] <psycho_oreos> nevermind, problem solved, I think its an issue with proprietary program, vmware workstation 6.5.2 running vista ultimate as guest
[13:41] <SiDi> probably a vista ultimate feature ~ </irony>
[15:54] <hrab> anyone around?
[15:54] <knome> o/
[15:54] <hrab> Howdy. Would this be the right place to ask about a grub2 question?
[15:58] <vidd> ask away
[15:59] <vidd> if we can answer we will
[16:01] <hrab> I seem to be pestering the #grub channel :) but sure, I installed grub2, it's in the stage where it chainloads to see if it works, on bootup it gives me error15 File could not be found.
[16:01] <hrab> it seems to be where it should be though.
[16:03] <SiDi> No idea.. :/
[16:03] <SiDi> I never managed to boot an OS with grub2
[16:03] <vidd> so you are getting the list of available os's but when you select one it fails?
[16:06] <Micro2GB> Hello is any one here?
[16:06] <vidd> yes
[16:07] <Micro2GB> I have a question about usage of a Xubuntu BackGround image on my website.
[16:08] <Micro2GB> I want to use Xubuntu-jmak-ws.png for the back drop on my website. but i dont want to infringe on Ubuntu.
[16:08] <Micro2GB> Do you think they would mind?
[16:09] <th0r> Micro2GB: I think you should contact the xubuntu team at the homepage about that one
[16:09] <vidd> im sure jmak wont mind if you give proper credit...but i would deffinantly ask
[16:09] <hrab> well I installed xubuntu with wubi, so I get the windows dual boot thing first, select -buntu, then it hits me with error:15 press any key yadda yadda.
[16:09] <hrab> from there I can go down and manually select xubuntu
[16:09] <Micro2GB> this all i could find to contact them, i will look agian thank you
[16:09] <knome> Micro2GB, i don't know what the license for joszefs artwork is, but i suppose that as long as it's not commercial, i think you can use it as you credit the original author
[16:10] <knome> Micro2GB, (joszef mak)
[16:12] <hrab> editing the menu.lst and "reminding" the chainloader entry which hd core.img lives on returns another can't find file error, and dumps me into grub recovery.
[16:54] <forces> !paste
[16:54] <forces> !pastebin
[16:58] <th0r> does anyone know if xubuntu 8.04 supports ext4?
[16:59] <vidd> th0r, i believe ext4 was introduced in 9.04
[16:59] <th0r> vidd: I am considering retrofitting to 8.04, but /home is ext4
[17:00] <vidd> th0r, i dont think you can
[17:01] <vidd> i dont believe the kenel for 8.04 supports ext4
[17:01] <th0r> vidd: was afraid of that. will just turn off the updates on jaunty and settle for this.
[17:01] <vidd> =]
[17:03] <th0r> vidd: yesterday's kernel 28-14 killed my internal wifi card...28-13 brought it back. 25 years into the game that shouldn't happen
[17:04] <vidd> and the wifi driver is....?
[17:04] <th0r> vidd: it is the broadcom driver....bcm4312 chipset
[17:04] <vidd> yeah
[17:05] <vidd> non-free firmware needed for that one?
[17:05] <th0r> vidd: no, believe it or not it worked out of the box from the livecd.
[17:06] <vidd> im asking cuzz i dont know
[17:06] <th0r> vidd: now the external card...an atheros ar5523...that one I had to bust a hump to get working
[17:06] <vidd> the bcm4306 is the pita card i have
[17:06] <vidd> and a kernel update kills it every time
[17:07] <th0r> vidd: well...I am going to freeze the laptop unless I find a good reason to update. I think I have about everything I need installed, and would prefer outdated stuff that works to updated stuff that doesn't
[17:07] <vidd> heh
[17:08] <th0r> heck...if I wanted the latest and greatest headaches I would be buying windows7
[17:08] <vidd> looks like ill be shopping around for a new distro myself
[17:08] <th0r> I have been thinking of either debian or suse. I think suse is more polished, but I like apt-get
[17:09] <vidd> i like apt-get too....but i need a distro that wont force-feed me bloat by default
[17:10] <th0r> yeah...xubuntu seemed like the answer, but too many times I have run into problems with updates
[17:10] <vidd> xubuntu USED to be the answer
[17:10] <th0r> and I don't especially like the parochial attitude that shows up in #ubuntu way too often
[17:11] <vidd> looks like from here on out, it will be ubuntu cli + SLiM, Openbox, and the bits and pieces i need
[17:12] <vidd> OH!, and install-recommends disabled
[17:12] <th0r> I have used suse previously and it is nice. I installed xfce at the initial install and it kept the size of the system down. They have a new boot process that seems interesting
[17:12] <th0r> vidd: I have been looking to see how I can turn off all the updates
[17:12] <vidd> th0r, i dont like that bootloader gui
[17:14] <th0r> vidd: there is always dsl <smile>
[17:16] <vidd> but i like b***hing here
[17:16] <vidd> =]
[17:22] <SiDi> Feel free to join #xubuntu-rant, guys
[17:23] <th0r> SiDi: a little slow today are we?
[17:28] <SiDi> btw, i suppose you reported the bug on kernel.org for your wifi chipset, th0r ?
[17:30] <th0r> no...but now that you mention it it would be a good idea.
[17:42] <pteague_work> i'm guessing xfce follows the free desktop standard considering several config files i've gone through & xfce panels works fine under icewm
[17:56] <Genelyk> it's bug ?? click rigth in thunar and freeze system bug or bad configuration ?
[17:57] <vidd> Genelyk, his system is not freezing....
[17:57] <Genelyk> uhm
[17:57] <vidd> he simply wants to preserve the existing versions of all his apps...like a snap-shot in time =]
[17:58] <Genelyk> not , freezing for 3 or 5 se , before normality
[17:58] <Genelyk> my version is 9.04 y.y
[17:58] <vidd> oh...your having an issue where your system is lagging when you rightclick in thunar?
[17:59] <Genelyk> yes
[18:00] <Genelyk> laggggggg
[18:18] <ron_o> Having some serious problems with my internet connection. Perhaps there's answers here.
[18:18] <ron_o> http://paste.ubuntu.com/219930/
[18:18] <ron_o> everything is in pastebin
[18:19] <ron_o> my connection usually drops out totally the more I do on the internet.
[18:22] <vidd> ron_o, i would set up your connection as follows:
[18:22] <vidd> cable to cable modem
[18:22] <vidd> cable modem to router
[18:22] <vidd> router to computer
[18:22] <vidd> see if that helps any
[18:23] <ron_o> vidd, why would that help?
[18:23] <ron_o> so I need a router between my modem and computer?
[18:23] <vidd> i would recommend it
[18:24] <ron_o> I just don't get the logic in putting something else between my computer and connex... seems like another place for a fault to lie.
[18:25] <vidd> ron_o, does your modem handle your connection or does the computer?
[18:26] <ron_o> modem.
[18:27] <ron_o> vidd, it's just that I'm kind of short on money. That's all. :/
[18:27] <vidd> heh...i understand
[18:27] <vidd> but there may be some "requires windows" setting in the modem
[18:28] <vidd> and setting up a router sometimes "fools" that setting
[18:28] <ron_o> ahh, I see.
[18:28] <ron_o> shit..
[18:28] <ron_o> pardon me.
[18:29] <ron_o> the thing is I did in fact have a Windows machine hooked up to the interenet connection and I still had a connex problem.
[18:29] <ron_o> :/
[18:29] <vidd> ok....
[18:29] <vidd> if the issue happens on windows too.....dont tell your ISP about your linux system
[18:29] <vidd> just have them troubleshoot for the windows box
[18:31] <ron_o> thanks.. I was just fixing a windows system for a friend is all. So I'm stuck with linux. I was talking to my ISP with Windows booted.
[18:31] <ron_o> thanks for the advice.
[18:32] <vidd> if the issue happens with windows as well as linux, then it is defanantly an ISP issue
[18:32] <vidd> id have them roll a truck to fix it
[18:32] <vidd> but you ask them to do that you best have a windows or mac box for the tech to access
[18:33] <ron_o> I see.. yah.
[18:33] <ron_o> I thought it might have been my splitters and all.
[18:33] <ron_o> I'll have to give them a call again.
[18:33] <vidd> it may very well be the splitters.....
[18:34] <ron_o> I removed them. I'm connex directly to my cable line to my modem, except for a few cable connectors...
[18:34] <vidd> but your cable company should have set up your modem for you
[18:34] <ron_o> it did vidd... it set it up years ago.
[18:35] <vidd> then there is most likely a rusted splitter on the outside wall
[18:35] <ron_o> but I'm out in the country and it's unlikely they give a crap about my issues.
[18:35] <ron_o> no, I disconnected the splitters for the moment.
[18:35] <ron_o> it's a direct connections.
[18:35] <vidd> there are still splitters....
[18:35] <ron_o> oh, coming to my house. Yes.
[18:36] <vidd> you may not have access to them....but they are most definantly there
[18:36] <ron_o> I see.
[18:36] <ron_o> you're probably right.
[18:36] * vidd works for an ISP
[18:37] <ron_o> before calling them I'll give it one more try and put the computer right next to the incoming line. I doubt it's my cable. I used RG6 and have crimp on connectors (but not the best kind)
[18:38] <vidd> ill bet you dollars to donuts it IS the cable line itself
[18:38] <vidd> you have cable tv as well (from the same company)?
[18:39] <ron_o> no.
[18:40] <vidd> I would have suggested plugging the cable modem into the jack with the best tv picture....
[18:41] <vidd> you have any nieghbors?
[18:42] <ron_o> but, you see, I am connected directly to the internet. I did have TV before, see?
[18:42] <ron_o> if I connect directly into the incoming line, there can be no better connex than that.
[18:43] <vidd> this is true
[18:44] <vidd> however....if your neighbor also has cable internet, and the installer messed up the line split on the pole....
[18:44] <ron_o> could be.
[18:44] <vidd> or someone illegally climbed the pole and is stealling cable tv....
[18:44] <ron_o> I don't want to bother them.
[18:44] <ron_o> I see. Killing my line.
[18:45] <vidd> exactly
[18:45] <ron_o> but the cables are underground.
[18:45] <vidd> ic...even worse
[18:45] <ron_o> the splitter is watertight.
[18:45] <ron_o> if working correctly.
[18:45] <ron_o> that's just it. The pipe into this area is only so big, so maybe that has something to do with it. Not like I have many options.
[18:46] <vidd> your a paying customer....you always have options =]
[18:47] <ron_o> I'll give them a call. Maybe set up a windows machine on another computer so they can't give me a hard time.
[18:47] <vidd> hehe
[18:48] <vidd> the other possibility is you ISP is throttling your connection
[18:48] <vidd> (ISP's that do that are evil)
[18:49] <ron_o> but that would mean killing my connex. Throttling, it wouldn't be so obvious.
[18:50] <ron_o> and in the middle of the night it would probably cease.
[18:50] <vidd> not nessissarily
[18:50] <Colonel_Panic> hey all
[18:50] <Colonel_Panic> I'm having a problem here
[18:50] <vidd> middle of the night is when you see the MOST throttling
[18:50] <vidd> Colonel_Panic, what issue?
[18:51] <ron_o> !ask
[18:51] <Colonel_Panic> I just rebooted and my applications and window menu are gone
[18:51] <Colonel_Panic> so, it appears, are my firefox user settings
[18:51] <Colonel_Panic> and when I opened IRC, it acted like it was the first time I'd ever run it
[18:51] <ron_o> add it the panel is all, unless I'm reading you wrong.
[18:52] <Colonel_Panic> the manels are gone too
[18:52] <Colonel_Panic> panels
[18:52] <ron_o> ahh, you lost your config files?
[18:52] <vidd> Colonel_Panic, did you delete any files b4 you rebooted?
[18:52] <Colonel_Panic> apparently so
[18:52] <Colonel_Panic> no I did not
[18:52] <vidd> did you run any updates?
[18:53] <Colonel_Panic> um... well I upgraded to 9.04 a few days ago
[18:53] <ron_o> any backup?
[18:53] <Colonel_Panic> but I rebooted after that and it worled fine
[18:53] <Colonel_Panic> I just rebooted again and this is what happened
[18:54] <vidd> Colonel_Panic, look in your /home directory....
[18:54] <Colonel_Panic> yes?
[18:54] <vidd> what users are there?
[18:55] <vidd> there should be a folder for each desktop user
[18:55] <Colonel_Panic> only the ones I created when I set up the OS
[18:55] <Colonel_Panic> yes there are
[18:55] <Colonel_Panic> and bin and lost+found
[18:55] <vidd> and which account are you in now?
[18:55] <Colonel_Panic> I'm on my own account
[18:56] <Colonel_Panic> one sec
[18:56] <Colonel_Panic> brb
[18:56] <Colonel_Panic> ok back
[18:56] <vidd> open up a terminal
[18:57] <Colonel_Panic> ok
[18:57] <Colonel_Panic> done
[18:57] <Colonel_Panic> already had one open
[18:57] <vidd> type "cd ~/Des[tab key]"
[18:58] <vidd> this will auto-fill /home/[user account]/Desktop
[18:58] <Colonel_Panic> yeah
[18:58] <Colonel_Panic> I know
[18:58] <vidd> does the user account auto-fill'd match the account you expect to be logged into?
[18:58] <Colonel_Panic> I'm in my own user directory
[18:58] <Colonel_Panic> yes
[18:58] <Colonel_Panic> I'm in my own home directory
[18:59] <vidd> do an ls -al
[18:59] <Colonel_Panic> ok
[18:59] <Colonel_Panic> one sec
[18:59] <vidd> bah! brb
[18:59] <Colonel_Panic> I shold mention that all my desktop icons are there as usual
[19:16] <vidd> sorry...
[19:16] <vidd> ok...in your list, you will see .conf
[19:17] <Colonel_Panic> in the Desktop dir?
[19:17] <Colonel_Panic> in my home dir, right?
[19:17] <vidd> no..in the /home/[user]
[19:17] <Colonel_Panic> cd ..
[19:17] <Colonel_Panic> oops
[19:18] <Colonel_Panic> wrong window
[19:18] <vidd> and its .config
[19:18] <vidd> that folder holds all your configuration files
[19:18] <vidd> hold up a sec....
[19:19] <vidd> do you have panels up?
[19:19] <Colonel_Panic> ok I'm there
[19:19] <Colonel_Panic> no panels
[19:20] <Colonel_Panic> I'm looking in my /home/<user>/.config directory
[19:20] <Colonel_Panic> what should I look for?
[19:20] <vidd> type xfce4-panel
[19:20] <vidd> do your panels come up like they were b4?
[19:21] <Colonel_Panic> yep. there they are!
[19:21] <Colonel_Panic> thans
[19:21] <Colonel_Panic> thanks
[19:21] <vidd> ok....so your issue was simply that your panels crashed
[19:22] <Colonel_Panic> I guess I need to go to #mozilla to get help with the firefox issue, right?
[19:22] <vidd> i recommend that you either clear out your session cache or save your session upon exit
[19:22] <vidd> well....
[19:23] <vidd> cd back to your home directory
[19:23] <Colonel_Panic> how do I clear out the sessions cache in xfce?
[19:23] <Colonel_Panic> I just switched from kde because I got tired of its bullshit
[19:24] <Colonel_Panic> too much extraneous crap that doesn't offer any better useability
[19:24] <Colonel_Panic> xfce is much nicer
[19:24] <vidd> go to .cache/sessions
[19:24] <Colonel_Panic> is that in my home?
[19:24] <vidd> delete everything there, and your saved sessions are gone
[19:24] <vidd> yes...
[19:25] <vidd> ~/.cache/sessions
[19:25] <Colonel_Panic> ok
[19:26] <Colonel_Panic> rm -rf
[19:26] <vidd> your thunderbird stuff SHOULD be saved in ~/.mozilla
[19:26] <Colonel_Panic> oops
[19:26] <Colonel_Panic> I mean rm *
[19:26] <Colonel_Panic> ok done
[19:27] <vidd> Colonel_Panic, both would have done the trick =]
[19:27] <vidd> and its your firefox stuff....not your thunderbird stuff in that folder =]
[19:27] <Colonel_Panic> so it's in ~/.mozilla/firefox ?
[19:28] <vidd> should be
[19:28] <Colonel_Panic> I see a profiles.ini
[19:28] <Colonel_Panic> I'd like to recover my bookmarks, history, etc.
[19:29] <vidd> there should be a folder in there
[19:29] <Colonel_Panic> gib74vv7.default?
[19:29] <vidd> yes
[19:29] <vidd> open that
[19:30] <Colonel_Panic> ok I'm seeing a bunch of stuff
[19:30] <vidd> you should see "bookmarks.bak" and "bookmarks.html
[19:30] <Colonel_Panic> ok
[19:30] <Colonel_Panic> there's a bookmarkbackups dir
[19:31] <vidd> im concerned with these 2 files i mentioned
[19:32] <vidd> check the dates modified for these 2 files
[19:44] <Colonel_Panic> the most recent one was modified today, the second most recent was modified yesterday
[19:49] <vidd> and yesterday the stuff worked fine?
[20:18] <tumii66> Can someone explain me how to change Xfce4 to Gnome (Xubuntu -> Ubuntu)?
[20:18] <tumii66> without reinstalling
[20:19] <vidd> !purexfce
[20:19] <tumii66> I have installed Xubuntu, I want to change the desktop to gnome, hmm
[20:19] <tumii66> !puregnome
[20:20] <vidd> tumii66, do the above in reverse
[20:20] <tumii66> hmm
[20:20] <tumii66> Oh thanks
[20:22] <vidd> is this the correct way to burn an image: dd of=/var/dwlds/disk.iso if=/dev/cdwr
[20:32] <princedugan> in which chat should I ask for VisualboyAdvance (ubuntu version) issues?
[20:35] <TheSheep> they are called channels, and you can ask here :)
[20:35] <TheSheep> you can also ask on #ubuntu if you don't get answer here
[20:38] <princedugan> the controls preferences in gvba respond to the keyboard but not my USB gamepad. my gamepad works fine for other apps, including SDL apps
[20:39] <princedugan> I investigated entering the gamepad control numbers directly into the config file, but can't find that information
[20:39] <TheSheep> gvba?
[20:39] <TheSheep> xev can give you that information
[20:40] <TheSheep> just open a terminal, type xev, a small window will open showing you all X events
[20:40] <princedugan> gvba= Visualboy Advanced GTK interface
[20:41] <TheSheep> princedugan: it's a separate project, isn't it?
[20:46] <princedugan> I didn't think gamepads were X related (is all HID handled by X?). I certainly didn't modify my Xorg directly to recognize my gamepad, should I? xev doesn't respond to my gamepad either. I don't know if vba and gvba are separate, but when I installed vba , gvba was also installed.
[20:48] <TheSheep> princedugan: I think they are independent animals
[20:48] <TheSheep> princedugan: that's why gvba might not be aware of them
[20:48] <TheSheep> princedugan: it's a gtk app, not sdl
[20:49] <TheSheep> princedugan: and to be honest, I find it several times slower than plain visualboyadvance
[20:51] <princedugan> oh, gtk does not recognize gamepads or just this gtk app (gvba)?
[20:55] <TheSheep> as far as I know gtk has no libraries for joystick support of its own, but there are external libraries
[20:55] <TheSheep> chances are that the authors didn't think about it and only used keyboard, though
[20:56] <TheSheep> I can't really tell, the package should contain the address of their project website, maybe they have a bugtracker or some other means of contact
[20:59] <TheSheep> princedugan: looks like you are not the first one http://ubuntuforums.org/showthread.php?t=1036715
[21:02] <TheSheep> princedugan: http://sourceforge.net/tracker/index.php?func=detail&aid=1378820&group_id=63889&atid=505529
[21:17] <xerox1> hi, i am using devilspie to determine a desk for an application; problem: if mutt is in desk 1 and firefox in desk 2 and i tell mutt to open a link firefox moves to desk 1 (with the new tab); how to fix that?
[21:33] <TheSheep> xerox1: let me find you a link
[21:37] <TheSheep> xerox1: http://wiki.sheep.art.pl/w/Firefox%20and%20XFCE4
[21:40] <SiDi> There's a GUI way to change it too
[21:41] <TheSheep> in new xfce
[21:44] <xerox1> thx guys, i tried this...no reaction at the moment; trying to restart display manager...perhaps it takes effect afterwards
[21:50] <xerox1> TheSheep, sorry but it doesn't seem to work: tried switch and none; if i get i right, switch should do the trick
[21:51] <TheSheep> xerox1: yeah, it works for me
[21:51] <TheSheep> xerox1: xfce 4.6 keeps config in different place though
[21:52] <xerox1> okay, then let me look for the new location
[22:17] <xerox1> TheSheep, now it is possible to change this property by using the gui (settings-editor or something like that could be the correct translation)
[22:17] <xerox1> section general provides the option to change the value
[23:57] <KittyKatt> [AmsG] brb...
|
Make sub nav bar aware of react-router-dom
Make sub nav bar aware of react-router-dom
Add a border to the sub nav bar
Add a pages in the CRA example
@mfrachet I just saw something on the main nav
haha, you're right! I'll update the main nav on another PR, thanks for the catch 🤣
I think we need a z-index on the condensed menu icon and the avatar is not centered vertically.
I've made the fixes @HichamELBSI
|
Board Thread:Animal Jam Talk/@comment-37305333-20190822161026/@comment-37305333-20190917142804
Aa I don't know a name, but she is really cute!
|
import { __awaiter } from "tslib";
import { green, yellow } from 'chalk';
import { writeFileSync } from 'fs';
// minimist is being used by the NG cli and a couple of other tools
import * as minimist from 'minimist';
import { join } from 'path';
import { inc } from 'semver';
import { makeHash } from './makeHash';
import { publishPackage } from './publishPackage';
import { folder, getPublishableProjects, readJson } from './utils';
// process cmd line options
const argv = minimist(process.argv.slice(2));
/** getting cmd line options */
const dryRun = !!!argv.doActualPublish;
const publish_major = !!argv.major;
const publish_minor = !!argv.minor;
const releaseType = publish_minor ? 'minor' : publish_major ? 'major' : 'patch';
/** always release all version on minor or major releases */
const all = releaseType === 'patch' ? !!argv.all : true;
if (dryRun) {
console.log(`doing a dry run for a ${releaseType}, no changes will be made to do an actual release add the ${yellow('--doActualPublish')} cmd line option\n`);
}
(() => __awaiter(void 0, void 0, void 0, function* () {
const currentVersions = yield getPublishableProjects();
const dataFileName = join(folder, './tools', 'releaseChecksums.release.json');
const oldData = (readJson(dataFileName) || []);
const needRelease = currentVersions.reduce((needRelease, data) => {
const old = oldData.find((row) => row && row.name === data.name);
if (all || old === undefined || old.hash !== data.hash) {
return needRelease.concat(data);
}
else {
console.log(`Package ${data.name} is upto date, and won't be released`);
}
return needRelease;
}, []);
yield Promise.all(needRelease.map((pkg) => __awaiter(void 0, void 0, void 0, function* () {
const newVersion = inc(pkg.version, releaseType);
const originalPackage = readJson(join(folder, pkg.root, 'package.json'));
const distPackage = readJson(join(folder, pkg.dist, 'package.json'));
console.log(`Making a release for ${green(pkg.name)}, from version ${yellow(pkg.version)} to ${green(newVersion)}`);
if (originalPackage === undefined || distPackage === undefined) {
console.log(`Couldn't find package.json for ${pkg.name}. Aborting run`);
process.exit(15);
}
originalPackage.version = newVersion;
distPackage.version = newVersion;
pkg.version = newVersion;
if (!dryRun) {
writeFileSync(join(folder, pkg.root, 'package.json'), JSON.stringify(originalPackage, undefined, 2));
writeFileSync(join(folder, pkg.dist, 'package.json'), JSON.stringify(distPackage, undefined, 2));
}
yield publishPackage('latest', Object.assign(Object.assign({}, pkg), { version: newVersion }), dryRun);
})));
/** update the hashes with the currently released versions */
const releasedHashes = yield Promise.all(currentVersions.map((v) => __awaiter(void 0, void 0, void 0, function* () {
const { hash } = yield makeHash(join(folder, './', v.dist));
return Object.assign(Object.assign({}, v), { hash });
})));
if (!dryRun) {
writeFileSync(dataFileName, JSON.stringify(releasedHashes, undefined, 2));
}
else {
// console.log(`updated ${dataFileName} will be:`)
// console.log(JSON.stringify(releasedHashes, undefined, 2))
}
}))();
//# sourceMappingURL=deployReleasets.js.map
|
<?php
namespace ipl\Html;
use Exception;
use InvalidArgumentException;
use function ipl\Stdlib\get_php_type;
/**
* {@link sprintf()}-like formatted HTML string supporting lazy rendering of {@link ValidHtml} element arguments
*
* # Example Usage
* ```
* $info = new FormattedString(
* 'Follow the %s for more information on %s',
* [
* new Link('doc/html', 'HTML documentation'),
* Html::tag('strong', 'HTML elements')
* ]
* );
* ```
*/
class FormattedString implements ValidHtml
{
/** @var ValidHtml[] */
protected $args = [];
/** @var ValidHtml */
protected $format;
/**
* Create a new {@link sprintf()}-like formatted HTML string
*
* @param string $format
* @param iterable $args
*
* @throws InvalidArgumentException If arguments given but not iterable
*/
public function __construct($format, $args = null)
{
$this->format = Html::wantHtml($format);
if ($args !== null) {
if (! is_iterable($args)) {
throw new InvalidArgumentException(sprintf(
'%s expects parameter two to be iterable, got %s instead',
__METHOD__,
get_php_type($args)
));
}
foreach ($args as $key => $val) {
if (! is_scalar($val) || (is_string($val) && ! is_numeric($val))) {
$val = Html::wantHtml($val);
}
$this->args[$key] = $val;
}
}
}
/**
* Create a new {@link sprintf()}-like formatted HTML string
*
* @param string $format
* @param mixed ...$args
*
* @return static
*/
public static function create($format, ...$args)
{
return new static($format, $args);
}
/**
* Render text to HTML when treated like a string
*
* Calls {@link render()} internally in order to render the text to HTML.
* Exceptions will be automatically caught and returned as HTML string as well using {@link Error::render()}.
*
* @return string
*/
public function __toString()
{
try {
return $this->render();
} catch (Exception $e) {
return Error::render($e);
}
}
public function render()
{
return vsprintf(
$this->format->render(),
$this->args
);
}
}
|
Java Spring Webservices SOAP Authentication
I am using java spring webservice to send soap requests to a server. However I get an error from the server saying
The security context token is expired or is not valid
So then I added authentication to the SOAP headers, resulting in request xml something like this:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<Security xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<UsernameToken>
<Username>XXXXXXXX</Username>
<Password>XXXXXXXX</Password>
</UsernameToken>
</Security>
</env:Header>
<env:Body>
The body is in the correct format here
</env:Body>
</env:Envelope>
But I still get that error. From what I understand, the client sends authentication credentials to the server, the server sends back requestToken which is used to keep connection alive between client and server and then client using the token received from the server can make any other API calls such as login, buy, sell (or whatever mentioned in API)
Am I right in this assumption? If yes, how can this be implemented using Java Spring WebServices. Do I need to generate fields on client side like BinarySecret and package that under RequestSecurityContext?
For adding the SOAP headers, I wrote a class which implements WebServiceMessageCallback and overrides doWithMessage method and writes headers in that for username and password (i.e security)
Any help would be appreciated! Thank You!
So after 2 days of finding out, I was able to figure out the solution!
1) Generate the classes from wsdl using CXF wsdl2java
2) Make sure in the pom file, you point to the correct wsdlLocation
3) Get the stub from the service class generated and inject username and password provided and then it should work. Something like this:
final YourService service = new YourService();
final YourStub stub = service.getService();
final Map ctx = ((BindingProvider)stub).getRequestContext();
ctx.put("ws-security.username", userName);
ctx.put("ws-security.password", password);
stub.callYourMethod();
PS: Please make sure you have the right libraries, I just used cxf-bundle and nothing else from cxf and it worked! Earlier it was not working as I had individually included libraries from cxf.
|
export class IdMap {
constructor(idStringify, idParse) {
this._map = new Map();
this._idStringify = idStringify || JSON.stringify;
this._idParse = idParse || JSON.parse;
}
// Some of these methods are designed to match methods on OrderedDict, since
// (eg) ObserveMultiplex and _CachingChangeObserver use them interchangeably.
// (Conceivably, this should be replaced with "UnorderedDict" with a specific
// set of methods that overlap between the two.)
get(id) {
const key = this._idStringify(id);
return this._map.get(key);
}
set(id, value) {
const key = this._idStringify(id);
this._map.set(key, value);
}
remove(id) {
const key = this._idStringify(id);
this._map.delete(key);
}
has(id) {
const key = this._idStringify(id);
return this._map.has(key);
}
empty() {
return this._map.size === 0;
}
clear() {
this._map.clear();
}
// Iterates over the items in the map. Return `false` to break the loop.
forEach(iterator) {
// don't use _.each, because we can't break out of it.
for (let [key, value] of this._map){
const breakIfFalse = iterator.call(
null,
value,
this._idParse(key)
);
if (breakIfFalse === false) {
return;
}
}
}
size() {
return this._map.size;
}
setDefault(id, def) {
const key = this._idStringify(id);
if (this._map.has(key)) {
return this._map.get(key);
}
this._map.set(key, def);
return def;
}
// Assumes that values are EJSON-cloneable, and that we don't need to clone
// IDs (ie, that nobody is going to mutate an ObjectId).
clone() {
const clone = new IdMap(this._idStringify, this._idParse);
// copy directly to avoid stringify/parse overhead
this._map.forEach(function(value, key){
clone._map.set(key, EJSON.clone(value));
});
return clone;
}
}
|
Solaris
Solaris is a country from Xenogears. It is the main antagonistic force throughout the game.
It appears northeast of Aquvy and southwest of Ignas. It is hidden from view by 3 gates located on the surface, located near Nisan, under the Ethos Headquarters and in the Sargasso.
History
Leadership
Class Structure
The population of Solaris is made up of 3 core classes:
Organizations
In the present day various organizations are used including the following:
Lore
* Solaris is named after the Stanislaw Lem novel of the same name.
|
Portal:Sharks/Did you know/12
* ... that the draughtsboard shark has been known to bark like a dog?
|
How does the model.resize_token_embeddings() function refactor the embeddings for newly added tokens in the tokenizer?
I am new to Natural Language Processing and currently working on machine translation using ALMA-7B model from Hugging Face. I wanted to create custom tokenizer based on the tokens that I have in my Word2Vec Embeddings and I also have their corresponding Embeddings (weights) with me. I am adding the tokens to tokenizers using following code:
alma_tokenizer.add_tokens(word_chunks)
Where alma_tokenizer is the Tokenizer for ALMA-7B model and word_chunks is a list of words I want to add. I want to update the model with its corresponding word embeddings as well, in the model and I was suggested to use resize_token_embeddings() function of AutoModelForCausalLM. When used it actually created new embeddings for the tokens I had added and I confirmed it as well. But my question is how are these embeddings created? Are they created randomly (as they are not a tensor of zeroes)? Can I insert my embeddings instead of the embeddings created by them?
Any kind of help will be appreciated!
embeddings=model.resize_token_embeddings(len(tokenizer))
transformers.modeling_utils.PreTrainedModel.resize_token_embeddings (https://github.com/huggingface/transformers/blob/38611086d293ea4a5809bcd7fadd8081d55cb74e/src/transformers/modeling_utils.py#L1855C14-L1855C27).
_get_resized_embeddings is finally called and Model._init_weights will be used to initialize new embedding. Than new_embeddings.weight.data[:n, :] = old_embeddings.weight.data[:n, :] will make sure the old token embedding remains the same.
As far as I know ALMA shares same architecture as Llama. Below is the _init_weight function in transformers.models.llama.modeling_llama:
def _init_weights(self, module):
std = self.config.initializer_range
if isinstance(module, nn.Linear):
module.weight.data.normal_(mean=0.0, std=std)
if module.bias is not None:
module.bias.data.zero_()
elif isinstance(module, nn.Embedding):
module.weight.data.normal_(mean=0.0, std=std)
if module.padding_idx is not None:
module.weight.data[module.padding_idx].zero_()
For ALMA, new token embedding will be initialized with normal distribution of mean=0 and var=std (which defined in model config)
Of course you can insert your embeddings.
Method 1 rewrite model._init_weights
def _my_init_weights(self, module):
std = self.config.initializer_range
if isinstance(module, nn.Linear):
module.weight.data.normal_(mean=0.0, std=std)
if module.bias is not None:
module.bias.data.zero_()
elif isinstance(module, nn.Embedding):
# replace following line with you embedding initialization here
module.weight.data.normal_(mean=0.0, std=std)
if module.padding_idx is not None:
module.weight.data[module.padding_idx].zero_()
Method 2 do it manually
my_embedding = nn.Embedding(...)
# do your initialize
alma_model.model.embed_tokens = my_embedding
If you do it manually, Don't forget to resize lm_head either. You may need to update parameters in model.config as well
Thanks for your detailed reply. There was one more doubt. Can you tell me what parameters in model.config I should check out if I am changing the length of tensors in model embeddings. ALMA has embedding tensors of 4096, but I am truncating them to 200 (to reduce the size of the model I am using).
vocab_size, or there will be mismatch between embedding shape and vocab_size in config file
Usually resize change vocab size dim instead of hidden state dim. Changing hidden state dim will cause error.
|
Thread:Collisions/@comment-24726562-20150626144837/@comment-26084724-20150627160252
http://i.imgur.com/irj1T1U.png
Your comic assembled
|
<?php
namespace Imperium\Http\Controllers\Admin;
use Illuminate\Http\Request;
use Imperium\Models\Category;
use Imperium\Http\Controllers\Controller;
class CategoriesController extends Controller {
/**
* Display a listing of the resource.
*
* @return Response
*/
public function index(Request $request)
{
$categories = Category::all();
$params = [
'title' => trans('categories.list'),
'categories' => $categories,
];
// If it's an API request
if ($request->wantsJson()) {
return response()->json(['success'=> true, 'message'=> $categories]);
}
return view('admin.categories.index')->with($params);
}
/**
* Show the form for creating a new resource.
*
* @return Response
*/
public function create()
{
$params = [
'title' => trans('categories.add')
];
return view('admin.categories.create')->with($params);
}
/**
* Store a newly created resource in storage.
*
* @return Response
*/
public function store(Request $request)
{
$this->validate($request, [
'name' => 'required|unique:categories',
'description' => 'required'
]);
if ($request->wantsJson()) {
if($validator->fails())
return response()->json(['success'=> false, 'error'=> $validator->errors()->all()]);
}
//create the new role
$cat = new Category();
$cat->name = $request->input('name');
$cat->description = $request->input('description');
$cat->save();
if ($request->wantsJson())
return response()->json(['success'=> true, 'message'=> trans('categories.created', ['name' => $category->name])]);
return redirect()->route('categories.index')->with('success', trans('categories.created', ['name' => $category->name]));
}
/**
* Display the specified resource.
*
* @param int $id
* @return Response
*/
public function show($id)
{
try
{
$category = Category::findOrFail($id);
return response()->json(['success'=> true, 'message'=> $category]);
}
catch (ModelNotFoundException $ex)
{
if ($ex instanceof ModelNotFoundException)
{
return response()->json(['success'=> false, 'message'=> trans('categories.notFound')]);
}
}
}
/**
* Show the form for editing the specified resource.
*
* @param int $id
* @return Response
*/
public function edit($id)
{
try
{
$category = Category::findOrFail($id);
$params = [
'title' => trans('categories.edit'),
'category' => $category,
];
return view('admin.categories.edit')->with($params);
}
catch (ModelNotFoundException $ex)
{
if ($ex instanceof ModelNotFoundException)
{
return redirect()->route('categories.index')->with('error', trans('categories.notFound'));
}
}
}
/**
* Update the specified resource in storage.
*
* @param \Illuminate\Http\Request $request
* @param int $id
* @return Response
*/
public function update(Request $request, $id)
{
try
{
$this->validate($request, [
'name' => 'required|unique:categories,name,'.$id,
'description' => 'required',
]);
$category = Category::findOrFail($id);
$category->name = $request->input('name');
$category->description = $request->input('description');
$category->save();
return redirect()->route('categories.index')->with('success', trans('categories.updated', ['name' => $category->name]));
}
catch (ModelNotFoundException $ex)
{
if ($ex instanceof ModelNotFoundException)
{
return redirect()->route('categories.index')->with('error', trans('categories.notFound'));
}
}
}
/**
* Remove the specified resource from storage.
*
* @param int $id
* @return Response
*/
public function destroy(Request $request, $id)
{
try
{
$category = Category::findOrFail($id);
$category->delete();
if ($request->wantsJson()) {
return response()->json(['success'=> true, 'error'=> trans('categories.deleted', ['name' => $category->name])]);
}
return redirect()->route('categories.index')->with('success', trans('categories.deleted', ['name' => $category->name]));
}
catch (ModelNotFoundException $ex)
{
if ($ex instanceof ModelNotFoundException)
{
if ($request->wantsJson()) {
return response()->json(['success'=> false, 'error'=> trans('categories.notFound')]);
}
return redirect()->route('categories.index')->with('error', trans('categories.notFound'));
}
}
}
}
|
Compressed Vice/Playing With
* Basic Trope: A flaw is introduced very suddenly and exaggerated for effect.
* Justified:
* Can't Get Away with Nuthin' for a Very Special Episode
* The need for Character Development in a show that has little in the way of continuity.
* Parodied: Bob has his first cigarette and instantly dies of cancer.
* Lampshaded: "Bob, weren't you going on just last week about how bad smoking is for you?"
* Averted:
* Bob doesn't smoke in-series.
* Discussed: "So...Bob's dying of emphysema 30 minutes after his first cigarette?"
* Played For Laughs: The vice is something small, like drinking out of the milk carton.
Back to Compressed Vice. Just don't squish it too hard.
|
Stakeholder management
Stakeholder management (also project stakeholder management) is a critical component in the successful delivery of any project, programme or activity. A stakeholder is any individual, group or organization that can affect, be affected by, or perceive itself to be affected by a programme.
The process
Project stakeholder management is considered as a continuous process, specifically a four-step process of identifying stakeholders, determining their influence, developing a communication management plan and influencing stakeholders through engagement. Within the field of marketing, it is believed that customers are one of the most important stakeholders for managing a business's long-term value, with a firm's major objective being the management of customer satisfaction.
History
The origin of stakeholder engagement can be traced back to the 1930s. In 1963, the Stanford Research Institute first defined the concept of stakeholder. In 1984, Edward Freeman’s book Strategic Management: A Stakeholder Approach was published. It brought to existence a complete body of knowledge surrounding the ethical management of stakeholders. Soon thereafter, computers were used to facilitate the organizations' engagement with communities and stakeholder analysis. Seven "principles of stakeholder management" are linked with the work of the Clarkson Centre for Business Ethics at the University of Toronto's Rotman School of Management, developed at four conferences held between 1993 and 1998.
The concept of stakeholder management has also been criticised, for example by John Argenti in 1996, who described the concept as "utterly discredited". The Strategic Planning Society's magazine, Strategy, subsequently hosted a debate on Argenti's views. Thomas argues that the established discourse regarding stakeholder management, although it is presented as supportive of stakeholders' interests, is "at best ambiguous, and at worst dishonest and manipulative".
Berman, Wicks, Kotha and Jones distinguish between two primary models of stakeholder management in business, an "instrumental" approach, according to which business managers engage with their stakeholders in order to maximise long term financial outcomes, and a "normative" approach, which identifies a stakeholder commitment as a moral obligation adopted by businesses, also referred to as an "intrinsic stakeholder commitment". Donaldson and Preston's academic work developed the normative approach, but while Berman et al. find empirical support for the financial benefits of effective stakeholder management, they have not identified any empirical basis for the normative model.
Organizational stakeholders
It is well acknowledged that any given organization will have multiple stakeholders including, but not limited to, customers, shareholders, employees, suppliers, and so forth. One of the Clarkson Centre's seven principles notes that managers "should acknowledge the potential conflicts between their own role as a corporate stakeholders, and the legal and moral responsibilities they hold to act for the interests of all stakeholders".
Stakeholder prioritization
Stakeholders may be mapped out on a power-interest map or grid, and classified by their power and interest. Other stakeholder mapping tools are available. For example, an employer is likely to have high power and influence over an employee's projects and high interest, whereas family members may have high interest, but are unlikely to have power over them.
Position on the grid may show actions:
* High power, interested people: these are the people you must fully engage and make the greatest efforts to satisfy.
* High power, less interested people: put enough work in with these people to keep them satisfied, but not so much that they become bored with your message.
* Low power, interested people: keep these people adequately informed, and talk to them to ensure that no major issues are arising. These people can often be very helpful with the detail of your project.
* Low power, less interested people: again, monitor these people, but do not bore them with excessive communication.
Stakeholder engagement
Stakeholder management creates positive relationships with stakeholders through the appropriate management of their expectations and agreed objectives. Stakeholder management is a process and control that must be planned and guided by underlying principles. Stakeholder management within businesses, organizations, or projects prepares a strategy using information (or intelligence) gathered during the following common processes. Stakeholder engagement emphasizes that corporations should take into account the effects of their actions and decision-making on their diverse stakeholders. In addition, in the stakeholder engagement, corporations should take into consideration the rights and expectations of their different supporters.
Some organizations use stakeholder engagement software to analyze their stakeholders, to create communication and engagement plans, to log information about the interactions they have with communities and to ensure compliance with regulations.
Aims of stakeholder engagement include:
* Communicate: to ensure intended message is understood and the desired response achieved.
* Consult, early and often, to obtain useful information and ideas, ask questions.
* Remember, they are human: be empathetic, operate with an awareness of human feelings.
* Plan it: time investment, and careful planning for how time is used, have a significant payoff.
* Relationship: engender trust with the stakeholders.
* Simple but not easy: show you care, and listen to the stakeholders.
* Managing risk: stakeholders can be treated as risks and opportunities that have probabilities and impact.
* Compromise across a set of stakeholders' diverging priorities.
* Understand what is success: explore the value of the project to the stakeholder.
* Take responsibility: project governance is the key to project success
|
10. A communication apparatus, comprising: one or more processors; and at least one memory, wherein the at least one memory stores instructions, and when executing the instructions stored in the memory, the one or more processors executes operations comprising: sending resource indication information with S bits to a terminal device; and sending data on the data channel, or receiving data on the data channel, wherein the resource indication information indicates frequency domain resources of a data channel, S is a positive integer, a most significant bit (MSB) in the S bits indicates whether a resource block set belongs to the frequency domain resources of the data channel, the resource block set consists of at least one resource block starting from a start resource block of a bandwidth part (BWP), a quantity of the at least one resource block is n, and n is less than or equal to m, m is a resource block group (RBG) size cor responding to a bandwidth of the BWP, y2 is equal to a quantity of resource blocks offset from a start resource block of a common index area to the start resource block of the BWP mod m, wherein when y2 is unequal to 0, n is less than m, and n is equal to m minus y2; when y2 is equal to 0, n is equal to m, the quantity of resource blocks offset from the start resource block of the common index area to the start resource block of the BWP is an integer multiple of m.
11. The apparatus according to claim 10, wherein the common index area comprises one or more bandwidth parts (BWPs).
12. The apparatus according to claim 10, wherein a second most significant bit in the S bits indicates whether m consecutive resource blocks belong to the frequency domain resources of the data channel, the m consecutive resource blocks are adjacent to the at least one resource block indicated by the MSB in the S bits, and S is greater than
1. 13. The apparatus according to claim 10, wherein S is equal to ┌(X2−n)/m┐+1, ┌┐ indicates rounding-up, and X2 is a quantity of resource blocks in the BWP.
14. The apparatus according to claim 10, wherein the resource indication information is a bitmap.
15. The apparatus according to claim 10, wherein the RBG size m is equal to 2, 4, or
8. 16. The apparatus according to claim 10, wherein the frequency domain resources of the data channel are a plurality of resource blocks.
17. The apparatus according to claim 10, wherein there is an offset from the start resource block of the common index area to a frequency domain reference point.
18. The apparatus according to claim 17, wherein the frequency domain reference point is a resource block with a minimum index included in a synchronization signal/physical broadcast channel block (SS/PBCH Block) of a primary serving cell (P cell).
19. A non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause a network device to perform operations comprising: sending resource indication information with S bits to a terminal device; and sending data on the data channel, or receiving data on the data channel, wherein the resource indication information indicates frequency domain resources of a data channel, S is a positive integer, a most significant bit (MSB) in the S bits indicates whether a resource block set belongs to the frequency domain resources of the data channel, the resource block set consists of at least one resource block starting from a start resource block of a bandwidth part (BWP), a quantity of the at least one resource block is n, and n is less than or equal to m, m is a resource block group (RBG) size cor responding to a bandwidth of the BWP, y2 is equal to a quantity of resource blocks offset from a start resource block of a common index area to the start resource block of the BWP mod m, wherein when y2 is unequal to 0, n is less than m, and n is equal to m minus y2; when y2 is equal to 0, n is equal to m, the quantity of resource blocks offset from the start resource block of the common index area to the start resource block of the BWP is an integer multiple of m.
20. The non-transitory computer-readable storage medium according to claim 19, wherein the common index area comprises one or more bandwidth parts (BWPs).
21. The non-transitory computer-readable storage medium according to claim 19, wherein a second most significant bit in the S bits indicates whether m consecutive resource blocks belong to the frequency domain resources of the data channel, the m consecutive resource blocks are adjacent to the at least one resource block indicated by the MSB in the S bits, and S is greater than
1. 22. The non-transitory computer-readable storage medium according to claim 19, wherein S is equal to ┌(X2−n)/m┐+1, ┌┐ indicates rounding-up, and X2 is a quantity of resource blocks in the BWP.
23. The non-transitory computer-readable storage medium according to claim 19, wherein the resource indication information is a bitmap.
24. The non-transitory computer-readable storage medium according to claim 19, wherein the RBG size m is equal to 2, 4, or
8. 25. The non-transitory computer-readable storage medium according to claim 19, wherein the frequency domain resources of the data channel are a plurality of resource blocks.
26. The apparatus according to claim 19, wherein there is an offset from the start resource block of the common index area to a frequency domain reference point.
27. The apparatus according to claim 26, wherein the frequency domain reference point is a resource block with a minimum index included in a synchronization signal/physical broadcast channel block (SS/PBCH Block) of a primary serving cell (P cell).
|
Physics documentation: mention servers when mentioning RIDs
Also mention RIDs in the top description of servers.
Also fix some mistakes in affected lines. For example, bodies and areas have (collision) shapes with a transform, so it is incorrect/incomplete to refer to these as Shape2D's, which are resources without a transform.
I think Mickeon brought up good points, I think I agree with those. What do you think @rburing?
|
Talk:Bugs/@comment-5116140-20120720153545
Temporary Working Solution for "Expansion Timer Bug" aka the "Sisyphean Bug"
"This note has also been posted under Expansions since it involves both expansion and bugs."
I can't help think of the punishment of the mythical Sisyphus everytime my timer resets.
Good luck fellow villagers, ID: TinyRobinEgg
|
Lens barrel and imaging device
ABSTRACT
A lens barrel includes a movable device to adjust an optical system, an operation section, and a display section. The operation section has a coupling section to be coupled with the movable device to control movement of the movable device. The display section is disposed in line with the operation section in a direction around an optical axis of the lens barrel to overlap with the operation section in a direction of the optical axis. The display section includes a display body that is movable in displaying a state of the optical system adjusted by the movable device. The display body of the display section is disposed to overlap the coupling section of the operation section in a radial direction of the lens barrel.
CROSS-REFERENCE TO RELATED APPLICATIONS
This patent application is based on and claims priority pursuant to 35 U.S.C. § 119(a) to Japanese Patent Application No. 2017-046858, filed on Mar. 13, 2017, in the Japan Patent Office, the entire disclosure of which is hereby incorporated by reference herein.
BACKGROUND Technical Field
Embodiments of the present disclosure relate to a lens barrel and an imaging device including the lens barrel.
Background Art
A lens barrel, such as an interchangeable lens used for, e.g., an auto-focus single lens reflex camera, is known that includes an automatic focus adjusting device and a manual focus adjusting device, either one of which is used to adjust focus of the lens barrel. Such a lens barrel includes an operation member for switching between automatic focus (AF) and manual focus (MF). With the operation member, a user switches between AF and MF. In addition, the lens barrel is often provided with a distance scale for the user to check the in-focus position.
SUMMARY
In an aspect of this disclosure, there is provided an improved lens barrel includes a movable device to adjust an optical system, an operation section, and a display section. The operation section has a coupling section to be coupled with the movable device to control movement of the movable device. The display section is disposed in line with the operation section in a direction around an optical axis of the lens barrel to overlap with the operation section in a direction of the optical axis. The display section includes a display body that is movable in displaying a state of the optical system adjusted by the movable device. The display body of the display section is disposed to overlap the coupling section of the operation section in a radial direction of the lens barrel.
In another aspect of this disclosure, there is provided an improved imaging device including the above-described lens barrel.
In even another aspect of this disclosure, there is provided an improved lens barrel including a movable device to perform a focus adjustment of an optical system, a switch, and a display section. The switch switches between an automatic focus adjustment mode and a manual focus adjustment mode, with the movable device. The display section is disposed to overlap the switch in a direction of an optical axis of the lens barrel and overlap the switch in a part in a radial direction of the lens barrel. The display section displays a state of the optical system adjusted by the movable device.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1A is a top view of a lens barrel according to an embodiment of the present disclosure, used in an imaging device;
FIG. 1B is a left side view of the lens barrel of FIG. 1A;
FIG. 2 is a longitudinal sectional view of a lens barrel according to a first embodiment along the optical axis direction of the lens barrel;
FIG. 3 is another longitudinal cross-sectional view of the lens barrel according to the first embodiment;
FIG. 4A is a longitudinal cross-sectional view of a release device and a differential device, which are in contact with each other;
FIG. 4B is a longitudinal sectional view of the release device and the differential device, which are separated from each other;
FIG. 5 is an external perspective view of an output ring;
FIGS. 6A and 6B are cross-sectional views taken along line A-A of the lens barrel in FIG. 3 focused at infinity and the close end, respectively;
FIG. 7 is a partially-exploded perspective view of the release device;
FIGS. 8A and 8B are illustrations of an operation of the release device;
FIG. 9A is a longitudinal cross-sectional view of a lens barrel according to a second embodiment with a release device in contact with a differential device;
FIG. 9B is a longitudinal sectional view of the lens barrel according to the second embodiment with the release device separated from the differential device;
FIG. 10 is a partially-exploded perspective view of the release device according to the second embodiment;
FIG. 11A is a longitudinal cross-sectional view of a lens barrel according to a third embodiment with a release device in contact with a differential device; and
FIG. 11B is a longitudinal sectional view of the lens barrel according to the third embodiment with the release device separated from the differential device.
DETAILED DESCRIPTION
In describing embodiments illustrated in the drawings, specific terminology is employed for the sake of clarity. However, the disclosure of this patent specification is not intended to be limited to the specific terminology so selected and it is to be understood that each specific element includes all technical equivalents that have the same function, operate in a similar manner, and achieve similar results.
Although the embodiments are described with technical limitations with reference to the attached drawings, such description is not intended to limit the scope of the disclosure and all of the components or elements described in the embodiments of this disclosure are not necessarily indispensable.
The present disclosure is not limited to the following embodiments, and the constituent elements of the embodiments includes those which can be easily conceived by those skilled in the art, substantially the same ones, and those in the following embodiments include those which can be easily conceived by those skilled in the art, substantially the same, and within equivalent ranges. Furthermore, various omissions, substitutions, changes and combinations of constituent elements can be made without departing from the gist of the following embodiments.
In a type of lens barrel that includes an operation member used to switch between automatic focus (AF) and manual focus (MF), and a distance scale for checking the in-focus position, the operation member and the distance scale are arranged on the circumferential surface of the lens barrel side by side along the optical axis direction, which increases the length of the lens barrel in the optical axis direction. To avoid such an increase, a configuration according to a comparative example is proposed that includes the operation member and the distance scale arranged side by side in the circumferential direction, that is, these are positioned to overlap with each other in the optical axis direction of the lens barrel. In a lens barrel according to a comparative example, the distance scale and the operation member are disposed to overlap with each other in the optical axis direction of the lens barrel.
One of the examples of the operation member for switching between AF and MF is an electrical switch. As another example of the operation member, a code plate and a brush are used for switching between AF and MF. In this case, a switch member, a code plate and a brush are disposed inside the lens barrel of the operation member, which occupies a predetermined area in the direction around the optical axis. In view of the above, the present inventor has studied a configuration that employs the operation member used to directly move and control a movable member disposed inside of the lens barrel. This configuration, however, increases the area occupied by relevant members of the operation member.
In the configuration according to the comparative example, the distance scale is provided on an annular member that rotates in an operation of focusing the focusing operation, and rotates together with the annular member by a predetermined angle around the optical axis of the lens barrel during the focusing operation. Thus, in the lens barrel according to the comparative example having the distance scale and the operation member disposed overlapping with each other in the optical axis direction, the distance scale and the switch member or the like of the operation member might interfere with each other. Particularly, the operation member, which includes a portion to couple with the movable member, studied by the present inventor is more likely to increase in size as a whole. This configuration further increases the probability of the interference between the distance scale and the operation member. In order to avoid such an interference, the operation member is preferably spaced apart from the operation member in the direction around the optical axis. In this case, however, the operation member has to be arranged on the lower side of the lens barrel. This arrangement leads to a deterioration in the operability of the operation member.
In the comparative example, an auto-focus (AF)-manual focus (MF) switch operation member is disposed at a stepped place, so that the operation member and a ring member for rotating overlap with each other in the optical-axis direction, but do not overlap in the radial direction (that is, these members are radially shifted from each other), so as to avoid the interference between the operation member and a ring member configured to rotate. This configuration according to the comparative example, however, increases the outer-diameter size of the lens barrel, which hampers the reduction in size of the lens barrel.
In view of the above, the present inventor has conceived of a compact lens barrel with a reduced length in the optical-axis direction and the diameter direction, which increases the design flexibility of the arrangement position of the operation member to thereby enhance the operability of the operation member, and an imaging device including the lens barrel as described below.
First Embodiment
FIGS. 1A and 1B are illustrations of a lens barrel 1 according to a first embodiment of the present disclosure attached to a camera body 2. FIG. 1A is a top view of the lens barrel 1, and FIG. 1B is a left side view of the lens barrel 1. In the front side of the lens barrel 1 (on the side of an object, the same applies hereinafter), a focus operation ring 73 is disposed on the circumferential surface of the lens barrel 1. The focus operation ring 73 enables manual focusing by the user's turning operation. A zoom operation ring 63 is disposed on the rear side (the image-plane side, the same applies hereinafter) on the circumferential surface of the lens barrel 1, and the user rotates the lens barrel 1 to change the focal length of the lens barrel 1.
On the left side surface of the lens barrel 1 as illustrated in FIG. 1B, a release switch 85 is disposed at an intermediate position of the lens barrel 1 in the direction of the optical axis of the lens barrel 1 (hereinafter, referred to simply as the optical-axis direction or the direction of the optical axis), that is, between the focus operation ring 73 and the zoom operation ring 63. The release switch 85 is described in detail later. The user's sliding the release switch 85 along the circumferential surface of the lens barrel 1 switches the manual focus (manual focus adjustment (MF)) mode of the focus operation ring 73 between an enabled state and a disabled state (released state). The release switch 85 serves as an operation section. When the manual focus mode is set to the released state, the manual focus adjustment of the focus operation ring 73 is disabled.
On the upper side surface of the lens barrel 1 as illustrated in FIG. 1A, a distance window 41 as a distance indication section (or simply referred to as a display section) is provided at a position adjacent to the release switch 85 in the circumferential direction. The user visually recognizes the distance indication through the distance window 41, so as to check the focusing distance that is a distance to the object of the lens barrel 1. The distance window 41 includes a distance display body 42 to be described later. The distance window 41 is disposed at a position that coincides with or partially overlaps the position of the release switch 85 in the direction of the optical axis. Such an arrangement of the distance window 41 that overlaps the release switch 85 in the direction of the optical axis achieves a reduction in the dimension of the lens barrel 1 in the direction of the optical axis, as compared to the configuration in which the distance window 41 does not overlap the release switch 85 in the direction of the optical axis.
FIGS. 2 and 3 are longitudinal cross-sectional views of the lens barrel 1. FIG. 2 is a longitudinal cross-sectional view of the lens barrel 1 taken at a radial position that includes the release switch 85. FIG. 3 is a partial cross-sectional view of the lens barrel 1 taken at a position that includes the distance window 41. As illustrated in FIG. 2, the interior of the lens barrel 1 includes a first lens group L1, a second lens group L2, a third group lens L3, a fourth group lens L4, and a fifth group lens L5 arranged from the left side of FIG. 2, that is, from the object side of the lens barrel 1. The first lens group L1 to the fifth lens group L5 move in the direction of the optical axis of the lens barrel 1 to change the focal length of the lens barrel 1 when the zoom operation ring 63 is rotated. The second lens group L2 is configured as a focus lens for moving in the direction of the optical axis in zooming and focus adjustment.
A focus motor 3 is disposed near the image-plane side in the lens barrel 1. The rotation of the focus motor 3 is controlled by, for example, an automatic focus control device mounted in the camera body 2. The focus motor 3 when rotating moves the second group lens L2 in the optical-axis direction to perform automatic focus adjustment. The focus motor 3 constitutes a part of an actuator for automatic focus adjustment according to an embodiment of the present disclosure. In the present embodiment, a direct current (DC) motor is employed as the focus motor 3. However, no limitation is intended herein. The focus motor 3 is a brushless DC motor, a stepping motor, or an ultrasonic motor.
In the interior of the lens barrel 1, an automatic focus adjustment device 4 configured to be driven by the focus motor 3, a manual focus adjustment device 5 configured to be driven by the focus operation ring 73, and a differential device 6 that coordinates the automatic focus adjustment device 4 with the manual focus adjustment device 5. The differential device 6 allows the automatic focus adjustment device 4 to perform the automatic focus adjustment on the second lens group L2 during the rotation of the focus motor 3. Further, the differential device 6 allows the manual focus adjustment device 5 to perform the manual focus adjustment on the second lens group L2 during the manual operation of the focus operation ring 73. The releasing switch 85 attached to the differential device 6 intermittently connects (coordinates) the manual focus adjustment device 5 with the differential device 6. When the differential device 6 is disconnected with the manual focus adjustment device 5, i.e., the manual focus adjustment is set to the released status, the manual focus adjustment of the focus operation ring 73 is disabled.
The lens barrel 1 includes a first stationary ring 91 provided with a lens mount 90. The first stationary ring 91 is joined with a second stationary ring 92 and a third stationary ring 93 disposed on the inner-diameter side of the second stationary ring 92. The focus operation ring 73 and the zoom operation ring 63 are supported by the second stationary ring 92 and the third stationary ring 93, respectively.
The second stationary ring 93 has two openings penetrating through the second stationary ring 92 in the radial direction that are disposed at certain positions in the direction of the optical axis, on the left side surface and the upper side surface arranged side by side in the circumferential direction. As illustrated in FIG. 2, the release switch 85 is attached to one of the two openings. As illustrated in FIG. 3, the distance window 41 is attached to the other opening. The distance window 41 includes a waterproof and dustproof transparent plate 41 a provided with, for example, an index for the user to check the distance indication. The transparent plate 41 a is buried and fixed in a recess on the outer circumferential surface of the second stationary ring 92.
A rear support ring 53 is joined with the second stationary ring 92 at the inner diameter position of the second stationary ring 92, and a front support ring 50 is joined with the second stationary ring on the object side of the lens barrel 1. A second support ring 57 is coupled to a section where the front support ring 50 and the rear support ring 53 are joined together.
At the inner diameter position of the rear support ring 53, a straight ring 32 and a zoom cam ring 31 are concentrically arranged toward the inner diameter direction. At the inner diameter position of the zoom cam ring 31, a third group lens frame 21 holding the third group lens L3, a focus cam ring 12, and a second group lens frame 11 holding the second group lens L2 are concentrically arranged. A first group lens frame 15 is disposed at an inner diameter position on the object side of the zoom cam ring 31, and a fourth group lens frame 16 and a fifth group lens frame 17 are disposed at an inner diameter position on the image-plane side of the zoom cam ring 31.
The zoom cam ring 31 is provided with a cam groove 31 a penetrating through the inner and outer diameters of the zoom cam ring 31. The straight ring 32 is provided with a longitudinal groove 32 a extending in the optical-axis direction, and a roller (referred to also as cam follower) 21 a provided on the outer periphery of the third group lens frame 21 is slidably fit into the cam groove 31 a and the longitudinal groove 32 a. Further, a roller 15 a provided on the first group lens frame 15 is fit into a cam groove 31 b and a longitudinal groove 32 b provided in the zoom cam ring 31 and the straight ring 32. Similarly, a roller 16 a provided on the fourth group lens frame 16 is fit into a groove 31 c and a longitudinal groove 32 c. Further, a roller 17 a provided on a fifth group lens frame 17 is fit into a longitudinal groove 16 b provided in the fourth group lens frame 16.
Such a configuration allows the first group lens frame 15 and the third group lens frame 21 to move in the optical-axis direction with a rotation of the zoom cam ring 31 by the manual operation of the zoom operation ring 63, thereby moving the first group lens L1 and the third group lens L3. Further, with the rotation of the zoom cam ring 31, the first group lens frame 15, the fourth group lens frame 16, and the fifth group lens frame 17 move in the direction of the optical axis. With the rotation of these elements, the second group lens frame 11 also moves in the direction of the optical axis. As a result, the first group lens L1 through the fifth group lens L5 move, which changes the focal length of the lens barrel 1.
A circumferential groove 21 b is provided on the inner peripheral surface of the third group lens frame 21. Between the circumferential groove 21 b and the focus cam ring 12, a plurality of spheres 14 is circumferentially disposed in the circumferential groove 21 b. This enables rotatably holding the focus cam ring 12 therein. The focus cam ring 12 has a cam groove 12 a penetrating through the inner and outer diameters thereof. The third group lens frame 21 is provided with a longitudinal groove 21 c extending in the optical axis direction. In addition, a roller 11 a provided on the outer periphery of the second group lens frame 11 penetrating through the cam groove 12 a is fit into the longitudinal groove 21 c. This arrangement restricts the rotation direction of the second group lens frame 11 to the direction of the optical axis.
A focus lever 13 extending to the image-plane side in the optical-axis direction is fixed to the focus cam ring 12 with a screw. The focus lever 13 rotates upon receiving the output of the differential device 6, thereby rotating the focus cam ring 12 together with the focus lever 13 while advancing and retracting in the direction of the optical axis together with the focus cam ring 12.
FIG. 4A is a longitudinal sectional view of an area including the differential device 6, which is a part of the lens barrel 1 in FIG. 2. The differential device 6 is disposed in an area between the second stationary ring 92 and the straight ring 32 in the radial direction and in an area between the focus operation ring 73 and the focus motor 3 in FIG. 2 in the direction of the optical axis. The differential device 6 is constituted by a planetary device. That is, the differential device 6 has a configuration including a first solar vehicle and a second solar vehicle, a plurality of planets, and a planetary carrier supporting these planets.
An output ring 51 is disposed on the outer-diameter side of the rear support ring 53. A groove 53 a that extends in the circumferential direction is provided on the outer circumferential surface of the rear support ring 53, and a plurality of spheres 54 arranged in the circumferential direction is disposed in the groove 53 a between the outer circumferential surface of the rear support ring 53 and the output ring 51. With this arrangement, the output ring 51 does not move in the optical axis direction with respect to the rear support ring 53, and is rotatably held around the optical axis.
FIG. 5 is an external perspective view of the output ring 51. An output lever 52 that extends in the direction of the optical axis is fixed to the output ring 51 with a screw, and has the leading end slidably fit with the focus lever 13. In this slide-fit configuration, the leading end of the output lever 52 is maintained integral with the focus lever 13 in the direction of rotation of the output ring 51, and the output lever 52 and the focus lever 13 slide over each other in the direction of the optical axis. In such a configuration, the rotation of the output ring 51 rotates the output lever 52, thereby rotating the focus lever 13, which further rotates the focus cam ring 12 that is integral with the focus lever 13. As described above, the rotation of the focus cam ring 12 advances or retracts the second group lens frame 11 in the direction of the optical axis to perform focus adjustment.
Three rotating shafts 51 a extending in the outer-diameter direction are equally spaced on the outer-circumferential surface of the output ring 51 in the circumferential direction. A planetary roller 55 is loosely fit to each rotation shaft 51 a. Each of two of the three rotating shafts 51 a includes a cover 56 screwed to the output ring 51, which prevents the planetary roller 55 from coming out.
An arcuate distance display body 42 is screwed in an area in the circumferential direction that includes the remaining rotation shaft 51 a and planetary roller 55. In the distance display body 42, a part of the inner edge in the circumferential direction is recessed in the outer-diameter direction, and screwed so as to serve also as the cover of the other rotation shaft 51 a other than the above-described two rotating shafts 51 a, which prevents the planetary roller 55 from coming out.
The distance display body 42 is formed in an arc shape having a substantially T-shaped cross section in the radial direction. The distance display body 42 has a lower edge 42 a attached to the circumferential surface of the output ring 51 so that the circumferential surface 42 b is formed to have an arcuate surface. Thus, the distance display body 42 radially projects from the circumferential surface of the output ring 51 in the outer-diameter direction by substantially the length of the lower edge 42 a. The distance display body 42 is disposed within the space in the radial direction between the output ring 51 and the second stationary ring 92. FIG. 6A is a cross-sectional view of the lens barrel 1 taken along the line A-A in FIG. 3. The distance display body 42 is attached with a display plate 43 circularly curved on the circumferential surface 42 b. The display plate 43 has a distance display body indicating the focal distance printed on the display plate 43, or a printed distance indication attached to the display plate 43. The distance indication of the display plate 43 is disposed facing the inner-diameter side of the distance window 41, which allows the user to visually recognize the distance indication from the outside of the lens barrel 1, through the transparent plate 41 a as described above.
The circumferential length of each of the distance display body 42 and the display plate 43 is set to the length of the arc, the center angle of which is substantially equal to a rotation angle, at which the output ring 51 rotates between the infinite end and the closest end in focus adjustment. When the output ring 51 rotates in the lens barrel 1 and the distance display body 42 rotates together with the output ring 51, the distance display body 42 rotates within an area that ranges from the upper side surface to the right-side surface as viewed from the object side of the lens barrel 1. In this case, the distance display body 42 is configured not to move to the area in which at least the release switch 85 is disposed.
As illustrated in FIG. 4A, the lens barrel 1 includes a drive gear ring 61 and a drive ring 71 to sandwich the above-mentioned three planetary rollers 55 in the optical-axis direction. A second wave washer 62 is disposed between the drive gear ring 61 on the image-plane side and the third stationary ring 93 in the optical-axis direction. The second wave washer 62 biases the drive gear ring 61 toward the object side, which presses a slide face 61 a on the object side of the drive gear ring 61 against the circumferential surface on the image-plane side of the planetary roller 55.
The lens barrel 1 further includes an internal gear 61 b on image-plane-side end of the drive gear ring 61. The internal gear 61 b is coupled to the focus motor 3 via a gear device. This configuration allows the drive gear ring 61 to rotate with the rotation of the focus motor 3. With the rotation of the drive gear ring 61, the planetary roller 55 pressed against by the drive gear ring 61 rotates, thereby rotating the output ring 51, thus rotating the focus cam ring 12, resulting in focus adjustment of the second group lens L2. Hence, the drive gear ring 61 constitutes a part of the above-described automatic focus adjustment device 4. Further, the drive gear ring 61 also constitutes one input section of the differential device 6.
The drive ring 71 contacting the planetary roller 55 on the object side of the planetary roller 55 has a slide face 71 a on the image-plane-side edge that is opposed to the planetary roller 55 in the optical-axis direction. In addition, a first wave washer 72 is disposed between a stepped surface, which is provided in the middle of the drive ring 71, and the front support ring 50 in the direction of the optical axis. The first wave washer 72 biases the drive ring 71 toward the image-plane side in the optical-axis direction, which presses the slide face 71 a against the object-side circumferential surface of the planetary roller 55.
A plurality of rollers 71 b is arranged on the object-side outer circumference of the drive ring 71 in the circumferential direction of the drive ring 71, each roller 71 b rising in the outer-radial direction. Further, each roller 71 b is slidably fit into each of the plurality of longitudinal grooves 73 a provided on the inner-circumferential surface of the focus operation ring 73 in the direction of the optical axis. This arrangement allows the drive ring 71 to move relative to the focus operation ring 73 along the direction of the optical axis. In addition, with the rollers 71 b slidably fit into the longitudinal grooves 73 a, the user's operation to rotate the focus operation ring 73 allows rotating the drive ring 71. When the slide face 71 a is pressed against the planetary roller 55, the rotation of the drive ring 71 rotates the planetary roller 55, thereby rotating the output ring 51, thus rotating the focus cam ring 12, resulting in the focus adjustment of the second group lens L2. Hence, the drive ring 71 constitutes a part of the manual focus adjustment device 5. Further, the drive ring 71 also constitutes another input section of the differential device 6.
The following describes the operation of the differential device 6. In FIG. 4A, when the focus motor 3 is driven during the automatic focus adjustment, the drive gear ring 61 rotates and the drive force is transmitted to the planetary rollers 55 pressed against the slide face 61 a. Accordingly, the planetary roller 55 rotates around the rotation shaft 51 a of the output ring 51. At this time, the drive ring 71 on the object side is stationary without rotating due to the friction torque generated between the drive ring 71 and the first wave washer 72. Thus, the planetary roller 55 rotates around the rotation shaft 51 a while the output ring 51 rotates around the optical axis. At this time, the output ring 51 rotates by a rotation amount of substantially half of that of the drive gear ring 61.
When the user operates the focus operation ring 73, the drive ring 71 rotates and the drive force is transmitted to the planetary roller 55 pressed against by the slide face 71 a. Accordingly, the planetary roller 55 rotates around the rotation shaft 51 a of the output ring 51. At this time, the drive gear ring 61 on the image-plane side is stationary without rotating due to the friction torque generated between the drive gear ring 61 and the second wave washer 62. Thus, the planetary roller 55 rotates around the rotation shaft 51 a while the output ring 51 rotates around the optical axis.
In the differential device 6, the following relations are satisfied: rT1 is smaller than T2 rT1; T2 rT1 is smaller than T3T3; T3T3 is smaller than T2 aT2; and T2 aT2 is smaller than T3 a where the rotational torque of the output ring 51 to move the second group lens L2 in the optical-axis direction is T1, the drive torque of the drive ring 71 rotated during the manual focus adjustment is T2, The drive torque of the drive gear ring 61 rotated during the focus adjustment is T3, the friction torque generated between the drive ring 71 and the first wave washer 72 is T2 a, the friction torque generated between the drive gear ring 61 and the second wave washer 62 is T3 a, and the speed reduction ratio of the differential device 6 is r.
The operation torque when the user operates the focus operation ring 73 depends on the static friction torque and dynamic friction torque generated between the drive ring 71 and the first wave washer 72. Preferably, the operation torque is not too heavy, not too light and moderate torque. A differential device according to a comparative example includes only one pressing member that gives friction torque. The pressing member in the comparative example corresponds to the second wave washer 62 according to the present embodiment of the present disclosure. Particularly when a vibration wave motor is employed as the actuator of the automatic focus adjusting device, the biasing force of a pressing member for biasing toward the planetary roller of the differential device is determined depending on the biasing force to allow the vibration wave motor to stably operate. This is because, a pressurizer for biasing toward a rotor serves also as the pressing member. In the differential device according to the comparative example, there is no degree of freedom in determining the biasing force of the pressing member, and adjusting the operation torque of the operation ring to an appropriate level has been difficult.
In the first embodiment, the drive ring 71 and the drive gear ring 61 are biased by the first wave washer 72 and the second wave washer 62, respectively, which allows adjusting the biasing forces independently. Within the range that satisfies the relations of T1, T2, T3, T2 a, and T3 a, setting the biasing force of, for example, the first wave washer 72 to be low allows reducing the operation torque of the focus operation ring 73.
As described above, the rotation of the output ring 51 rotates the output lever 52 integrated with the output ring 51, thereby rotating the focus lever 13, which further rotates the focus cam ring 12 that is integral with the focus lever 13. Such a rotation of the focus cam ring 12 advances or retracts the second group lens frame 11 to perform the focus adjustment. In such a state illustrated in FIG. 4A, both the automatic focus adjustment and the manual focus adjustment are enabled. Accordingly, when the user operates the focus operation ring 73 in focus adjustment by the automatic focus adjustment, the differential device 6 rotates the output ring 51.
A description is given of a release device 8 for preventing the movement of the differential device 6 by the operation of the focus operation ring 73 during the automatic focus adjustment. FIG. 7 is a partially exploded perspective view of the releasing device 8. The drive ring 71 includes the release member 81 at the outer diameter position of the drive ring 71. The drive ring 71 further includes a release switch ring 82 on the image-plane side and a presser ring 84 on the object side in the direction of the optical axis, between which the release member 81 is disposed. Note that the release switch ring 82 is disposed at the position along the optical axis to encircle the output ring 51.
The release switch ring 82 is rotatably held at the inner-diameter position of the second stationary ring 92. A plurality of (six release cams in the present embodiment) release cams 82 a is formed in the circumferential direction on the surface of the release switch ring 82 that faces the release member 81, that is, the object-side surface of the release switch ring 82 in the axial direction. The release switch ring 82 includes an engagement key 82 b extending rearward (to the image-plane side). The release switch ring 82 is engaged with an engagement groove 86 a of a release switch attachment member 86 that supports the release switch 85. With this configuration, the release switch ring 82 is coupled to the release switch 85, and rotates around the optical axis in response to the user's operation of the release switch 85 in the circumferential direction.
The release member 81 is provided with three straight keys 81 a, each being oriented in the optical-axis direction in the circumferential direction on the outer circumferential surface of the release member 81. Each straight key 81 a is slidably fit into a longitudinal groove 92 a on the inner-circumferential surface of the second stationary ring 92. This arrangement restricts the rotation of the release member 81 around the optical axis in the interior of the second stationary ring 92 while holding the release member 81 to be capable of moving straight. The release member 81 is provided with an engagement projection 81 b opposed to the release cam 82 a of the release switch ring 82 in the optical-axis direction. Further, the release member 81 includes a rib 8 over the object-side surface in the optical-axis direction, the rib 8 facing the stepped surface oriented to the image-plane side along the optical-axis direction on the drive ring 71.
The presser ring 84 is fixed to the front-side part of the second stationary ring 92 with, for example, a screw. A plurality of (six compression coil springs in the embodiment) compression coil springs 83 is disposed between the presser ring 84 and the release member 81 in the circumferential direction, which provides a spring force to bias the release member 81 toward the image-plane side in the optical-axis direction. This biasing of the release member 81 causes the engagement projection 81 b of the release member 81 to contact the release cam 82 a of the release switch ring 82, thereby pressing the release switch ring 82. The release switch ring 82 is held between the release member 81 and a plurality of presser ribs 92 b provided on the inner-circumferential surface of the second stationary ring 92.
The release switch attachment member 86 is formed to be a curved plate, and includes a conductive brush 87 and a plate spring 88 attached thereto. The conductive brush 87 and the plate spring 88 are disposed within the plate thickness of the release switch attachment member 86 as viewed in the radial direction of the lens barrel 1. The conductive brush 87 is brought into electrical contact with a flexible printed circuit board disposed in the lens barrel 1, to detect the rotational position of the release switch 85. Further, the plate spring 88 is configured to transmits, to the user having operated the release switch 85, the switching behavior of the release switch 85. The plate spring 88 has a bent-tip section 88 a that moves along the inner-circumferential surface of the second stationary ring 92, and slides to fit into valleys 92 c and 92 d formed in the inner-circumferential surface of the second stationary ring 92. This provides the switching behavior as a click feeling to the user. An engagement groove 86 a surrounded by a U-shaped projecting wall that projects in the radial direction is formed in a part of the inner surface of the release switch attachment member 86. The engagement key 82 b of the release switch ring 82 is engaged with the engagement groove 86 a. This configuration couples the release switch 85 with the release switch ring 82.
A description is given of the operation of the release device 8 with reference to FIGS. 7, 8A, and 8B. FIG. 7 is a schematic illustration of the release device 8 virtually viewed from above the lens barrel 1. FIGS. 8A and 8B corresponds to FIGS. 4A and 4B, respectively.
When the release member 81 is slide d upward in the lens barrel 1 by the user's operation of the release switch 85 as illustrated in FIG. 8A, the bent-tip section 88 a of the plate spring 88 is engaged with the valley 92 c formed on the inner-circumferential surface of the second stationary ring 92. In this state, the manual focus adjustment is enabled. At this time, the conductive brush 87 is capable of detecting the operation position.
In other words, as illustrated in FIG. 8A, when the release switch 85 is operated by the user to a position that enables the manual focus adjustment, the release switch ring 82 is rotated to a position at which the release cam 82 a do not contact the engagement projection 81 b. Accordingly, the release member 81 is moved to the image-plane side by the biasing force of the compression coil spring 83, and the rib 81 c of the release member 81 is separated from the stepped surface of the drive ring 71. Thus, the slide face 71 a of the drive ring 71 is pressed against the planetary roller 55 by the biasing force of the first wave washer 71 as illustrated in FIG. 4A. The user's operation of the focus operation ring 73 rotates the output ring 51, which enables the manual focus adjustment.
To cancel the state of the manual focus adjustment mode, the user operates the release switch 85 to slide in the clockwise direction, that is, downward in the lens barrel 1 from the state as illustrated in FIG. 6A, so that the bent-tip section 88 a of the plate spring 88 reaches the position of the valley 92 d. As illustrated in FIG. 8B, when the release switch 85 is operated by the user to a position that cancels the manual focus adjustment mode, the release switch ring 82 is rotated to a position at which the release cam 82 a contacts the engagement projection 81 b. Accordingly, the release member 81 is moved to the object side by the biasing force of the compression coil spring 83, and the rib 81 c of the release member 81 contacts the stepped surface of the drive ring 71. As a result, the drive ring 71 is moved to the object side against the biasing force of the first wave washer 71, and the slide face 71 a of the drive ring 71 is separated from the planetary roller 55. In this state, the output ring 51 does not rotate even with the user's operation of the focus operation ring 73, which disables the manual focus adjustment.
When the conductive brush 87 detects that the release switch 85 has been operated to reach the cancel position, the power supply to the focus motor 3 is cut off in a control circuit so as to prohibit focus adjustment by the automatic focus adjustment.
In the first embodiment, the user's operation of the release switch 85 in the circumferential direction of the lens barrel 1 enables operating the focus operation ring 73 or release this state. This configuration increases the operability of the release switch 85 during the imaging while stably holding the imaging device I during the operation, as compared to the case in which the release switch 85 is operated along the direction of the optical axis.
To release the manual focus adjustment mode in the first embodiment, the configuration is provided that the release member 81 pushes the drive ring 71 to release the coupling of the drive ring 71 with the planetary roller 55. This configuration enables releasing the manual focus adjustment mode at any position regardless of the rotational position of the ring 73 while preventing the misalignment of the focal position due to the small rotation of the focus operation ring 73. Further, such a configuration reliably prevents the misalignment of the focal position because there is no loose fit with play caused by component tolerance.
In releasing the manual focus adjustment mode according to the first embodiment, the drive ring 71 is moved to the object side, which compresses the first wave washer 72 further, so that the elastic restoring force of the first wave washer 72 increases. Accordingly, the rotation torque for operating the focus operation ring 73 increases, which facilitates a user's intuitive perceiving of the release of the manual focus adjustment mode.
When the manual focus adjustment mode is released, the planetary roller 55 of the output ring 51 is pressed against the slide face 61 a of the drive gear ring 61 for automatic focus adjustment. This arrangement prevents an improper rotation of the output ring 51 even when vibrations or the like are applied to the lens barrel 1 at the time of the release. Thus, the misalignment of the focal position is reliably prevented.
As described above, the user's operation of the release switch 85 rotates the release switch ring 82, which moves the release member 81 in the direction of the optical axis, thus releasing the connection of the manual focus adjustment device 5 in the differential device 6. Accordingly, the release switch 85 and the release switch attachment member 86 supporting the release switch 85 constitute an operation section that operates the release device 8 for controlling the connection and release in the differential device 6, that is, a switch that switches the released state. That is, the release switch 85 serves as the operation section to control movable devices of the lens barrel 1 that includes the release switch attachment member 86, the conductive brush 87 and the plate spring 88 attached to the release switch 85, the release device 8, and the differential device 6 to be controlled with the release device 8.
As can be seen from FIG. 1A, the release switch 85 of the operation section is disposed on the circumferential surface of the second stationary ring 92. Similarly, the distance window 41 as the distance display section is also disposed on the circumferential surface of the second stationary ring 92. In particular, the release switch 85 is disposed at a position close to the distance window 41 and on the left-side surface of the lens barrel 1 at which the user can easily operate the release switch 85. Further, as can be seen from FIG. 6A, the release switch attachment member 86 of the operation section is provided with a coupling section at which the release switch attachment member 86 is coupled with a the circumferential-directional part of the release switch ring 82. That is, the coupling section is the engagement groove 86 a that engages with the engagement key 82 b. The engagement groove 86 a is disposed within a space in the radial direction between the outer-circumferential surface of the output ring 51 of the differential device 6 and the inner-circumferential surface of the second stationary ring 92. Within the space, the distance display body 42 of the distance display section and the display plate 43 are also arranged.
That is, the engagement groove 86 a as the coupling section of the operation section coupled with the release device 8 and the distance display body 42 of the distance display section overlap with each other in the radial direction of the lens barrel 1. In other words, the distance display section including the distance display body 42 and the coupling section (the engagement groove 86 a) of the release switch attachment member 86 of the operation section (the release switch 85) that is mechanically coupled with the release device 8 as a part of the movable device in the interior of the lens barrel 1 are disposed to overlap with each other in the radial direction. Other elements other than the coupling section in the release switch attachment member 86 are disposed away from the distance display body 42 in the radial direction, that is, disposed on the outer-diameter side of the distance display body 42.
With such a configuration of the operation section (the release switch 85), when the lens barrel 1 is focused on infinity, the output ring 51 rotates by a maximum amount in the clockwise direction, and the display plate 43 indicating the infinity on the distance display body 42 is visually recognized by the user through the distance window 41, as illustrated in FIG. 6A. At this time, the clockwise-directional end of the distance display body 42 overlaps a part of the release switch attachment member 86 in the circumferential direction, and is not moved to the position of the coupling section (the engagement groove 86 a), which prevents the interference between the distance display body 42 and the release switch attachment member 86.
FIG. 6B is a sectional view of the lens barrel 1 that is focused at the close end. In this case, the output ring 51 rotates by a maximum amount in the counterclockwise direction, and the distance display body 42 indicating the close distance is visually recognized by the user through the distance window 41. At this time, the distance display body 42 is moved in a direction away from the release switch attachment member 86, which prevents the interference between the distance display body 42 and the release switch attachment member 86. In this case, one planetary roller 55, which moves toward the release switch 85 in the clockwise direction, does not reach the release switch attachment member 86. In the configuration according to the first embodiment, even when the output ring 51 is rotated to perform focusing of the lens barrel 1 from infinity to the close end, the output ring 51, the distance display body 42 and the planetary rollers 55 mounted on the output ring 51 do not interfere with the release switch attachment member 86.
In this configuration, the distance display section and the operation section (the release switch 85) are disposed on the circumferential surface of the lens barrel 1 to overlap with each other along the direction of the optical axis, which allows a reduction in the length of the lens barrel 1 in the direction of the optical axis. Further, in this configuration, the distance display body 42 of the distance display section and the coupling section (the engagement groove 86 a) of the release switch attachment member S6 are disposed to overlap with each other in the radial direction of the lens barrel 1. This arrangement prevents the interference between the distance display body 42 and the release switch attachment member 86 even with a predetermined amount of rotation (movement) of the distance display body 42 while providing the release switch 85 disposed close to the distance window 41, thus increasing the operability of the release switch 85, as compared to the case in which the distance display body 42 overlaps with the release switch attachment member 86 as a whole in the radial direction of the lens barrel 1. Even with the movement of the distance display body 42, a thin area other than the area of the coupling section (the engagement groove 86 a) of the release switch attachment member 86 merely comes to overlap the distance display body 42 in the circumferential direction, thereby preventing an increase in the outer diameter dimension of the lens barrel 1. This configuration achieves a compact lens barrel with an operation member having an increased operability while providing a compact imaging device, such as a camera, with such a lens barrel.
The present disclosure is applied to any lens barrel that includes a distance display section and an operation section for operating movable members disposed within the lens barrel. Accordingly, the present disclosure is applicable to lens barrels according to a second embodiment and a third embodiment as described below.
Second Embodiment
FIG. 9A is a cross-sectional view of a release switch ring member 82A according to a second embodiment formed by the release switch ring 82 integrated with the release member 81 according to the first embodiment. Parts equivalent to those in the first embodiment are denoted by the same reference numerals, and redundant description is omitted. FIG. 10 is a perspective view of the release switch ring member 82A. In the second embodiment, as illustrated in FIG. 10, the release switch ring member 82A includes a tapered release cam 82 a provided on the image-plane side surface of the release switch ring member 82A. The second stationary ring 92 has the surface directed to the direction of the optical axis including an engagement projection 92 b that faces the release cam 82 a in the direction of the optical axis. The release cam 82 a comes to engage with or gets released from the engagement projection 92 b with changes in rotational position of the release switch ring member 82A. The release switch ring member 82A is mounted at the inner-radial position of the second stationary ring 92 to be capable of slightly moving in the direction of the optical axis. Further, the release switch ring member 82A is biased toward the image-plane side by the compression coil spring 83 disposed between the release switch ring member 82A and the presser ring 84. In some embodiments, the compression coil spring 83 is a third wave washer. With such a configuration, the release cam 82 a is biased toward a direction to contact the engagement projection 92 b.
In the second embodiment, when the release switch 85 is operated in the circumferential direction, as illustrated in FIG. 9A, the release switch ring member 82A rotates in the circumferential direction, which causes the release cam 82 a to contact the engagement projection 92 b or not to contact the engagement projection 92 b. When the release cam 82 a does not contact the engagement projection 92 b, the biasing force of the compression coil spring 83 moves the release switch ring member 82A to the image-plane side of the imaging device I. That is, the release switch ring member 82A is at the position on the image-plane side when the release cam 82 a is not contact with the engagement projection 92 b. Further, the first wave washer 72 presses the drive ring 71 toward the image-plane side of the imaging device I, thereby pressing the slide face 71 a of the drive ring 71 against the planetary roller 55. In this state, the user's operation of the focus operation ring 73 rotates the output ring 51, thus allowing the manual focus adjustment.
By contrast, when the release cam 82 a contacts the engagement projection 92 b in accordance with the operation of the release switch 85, as illustrated in FIG. 9B, the release switch ring member 82A moves toward the object side of the imaging device I, against the biasing force of the compression coil spring 83, thereby moving the drive ring 71 to the object side. As a result, the slide face 71 a of the drive ring 71 is separated from the planetary rollers 55, and thus the manual focus adjustment mode is set to the released state. Thus, even with the user's operation of the focus operation ring 73, the output ring 51 does not rotate and the manual focus adjustment is disabled.
In the second embodiment, using one release switch ring member 82A enables connecting and disconnecting the drive ring 71 with the differential device 6 by moving the drive ring 71 along the direction of the optical axis. This configuration reduces the number of elements in the lens barrel 1, thus advantageously reducing the size of the lens barrel 1. In the configuration according to the second embodiment, similarly to the first embodiment, the operation section including the release switch is provided to overlap the distance display section including the distance window and the distance display body in the direction of the optical axis and in the radial direction. This arrangement achieves a reduction in size of the lens barrel.
Third Embodiment
FIG. 11A is a cross-sectional view of the release switch ring 82 and the release member 81 according to a third embodiment in which these are configured in a cam groove structure. Parts equivalent to those in the first embodiment are denoted by the same reference numerals, and redundant description is omitted. In the third embodiment, the release switch ring 82 is formed in a cylindrical shape and a cam groove 82 c is provided on the circumferential surface of the release switch ring 82. The release member 81 is disposed on the inner-diameter side of the release switch ring 82, and a roller 81 d engaging with the cam groove 82 c is disposed in a part of the release switch ring 82. Further, an auxiliary drive ring 71A is coupled with the drive ring 71 in the optical-axis direction, with a screw. A part of the release member 81 is sandwiched between the drive ring 71 and the auxiliary drive ring 71A in the optical-axis direction. The slide face 71 a on the image-plane side of the drive ring 71 is disposed facing the planetary roller 55, and the auxiliary drive ring 71A is engaged with the focus operation ring 73. Note that the first wave washer 72 in the first embodiment is not included in the lens barrel 1 according to the third embodiment.
In Embodiment 3, operating the release switch 85 to rotate the release switch ring 82 moves the release member 81 toward the image-plane side in the optical-axis direction, which is caused by the sliding of the cam groove 82 c and the roller 81 d as illustrated in FIG. 11A. As a result, the drive ring 71 and the auxiliary drive ring 71A that sandwich the release member 81 also move toward the image-plane side. Thus, by suitably designing the shape of the cam groove 82 c, when the release switch 85 is operated to a position where manual focus adjustment is enabled, the drive ring 71 moves toward the image-plane side and the slide face 71 a comes into contact with the planetary roller 55, thus enabling the manual focus adjustment with the focus operation ring 73.
When the release switch 85 is operated to a position to release the manual focus adjustment mode, as illustrated in FIG. 11B, the release member 81 is moved toward the object side by the sliding of the cam groove 82 c and the roller 81 d accompanying the rotation of the release switch ring 82. At the same time, the drive ring 71 and the auxiliary drive ring 71A move toward the object side, together with release member 81. As a result, the slide face 71 a of the drive ring 71 is separated from the planetary roller 55, and manual focus adjustment by the focus operation ring 73 is disabled. At this time, the second wave washer 62 moves the drive gear ring 61 to the object side. In the configuration according to the third embodiment, the groove 53 a and the ball 54 of the rear support ring 53 as in the first and second embodiments are not included. Accordingly, the output ring 51 moves to the object side of the lens barrel 1 with the movement of drive gear ring 61, and the end face 51 a on the object side of the output ring 51 contacts the second support ring 57, which restricts the movement of the output ring 51, thus keeping the drive ring 71 away from the planetary roller 55.
In the configuration according to the third embodiment, similarly to the first embodiment, the operation section including the release switch is provided to overlap the display section including the distance window and the distance display body in the direction of the optical axis and in the radial direction. This arrangement achieves a reduction in size of the lens barrel.
The operation section in the present disclosure is not limited to the release switch according to the first embodiment through the third embodiment, and may be any section for switching the inner device of the lens barrel. Therefore, any movable member configured to be moved by the operation section is not limited to the members according to the first embodiment through the third embodiment. Further, the display section in the present disclosure is not limited to the distance display section for indicating the focal distance as described in the first embodiment, and may be a focal-distance display section for indicating zooming data (lens focal length) or a F-number display section for indicating f numbers of lenses.
The present disclosure is not limited to the lens barrel such as the interchangeable lens described above, and may be applied to a lens barrel integrated with the camera body. Further, the present disclosure is not limited to the lens barrel of the camera for shooting a still image, and may be applied to a lens barrel of a camera for moving image shooting or to a lens barrel for a digital imaging device. Further, the embodiments of the present disclosure include the lens barrel as an interchangeable lens, an imaging device as a camera integrated with the body of the device, an imaging device for moving image shooting.
Numerous additional modifications and variations are possible in light of the above teachings. It is therefore to be understood that, within the scope of the above teachings, the present disclosure may be practiced otherwise than as specifically described herein. With some embodiments having thus been described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the scope of the present disclosure and appended claims, and all such modifications are intended to be included within the scope of the present disclosure and appended claims.
What is claimed is:
1. A lens barrel, comprising: a movable device to adjust an optical system, the movable device including a ring that is rotatable around an optical axis in the lens barrel; an operation section having a coupling section to be coupled with the movable device to control movement of the movable device; and a display section disposed in line with the operation section in a direction around the optical axis of the lens barrel to overlap with the operation section in a direction of the optical axis, the display section including a display body that is movable in displaying a state of the optical system adjusted by the movable device, wherein the display body of the display section is disposed to overlap the coupling section of the operation section in a radial direction of the lens barrel, and wherein the display body of the display section radially projects from an outer-circumferential surface of the ring.
2. An imaging device comprising the lens barrel according to claim
1. 3. The lens barrel according to claim 1, wherein the coupling section of the operation section is disposed radially outside the outer-circumferential surface of the ring, and wherein the coupling section of the operation section is disposed in an area in a circumferential direction of the ring, and the display body does not move to the area when the ring rotates.
4. The lens barrel according to claim 1, wherein the movable device is configured to adjust a focal position of the optical system, wherein the display section is a distance display section to display the focal position of the optical system, and wherein the display body is a distance scale body provided with a distance indication.
5. The lens barrel according to claim 4, wherein the movable device further includes a differential device that includes a first input of a manual focus adjustment device and a second input of an automatic focus adjustment device of the optical system, wherein the ring is an output ring of the differential device, and wherein the operation section is a release switch to release a connected state of the manual focus adjustment device.
6. The lens barrel according to claim 5, wherein the output ring supports a planetary roller in at least a part of the output ring in the circumferential direction, and wherein the operation section is disposed in an area to which the planetary roller does not move when the output ring rotates.
7. The lens barrel according to claim 5, further comprising: a stationary ring having a first opening and a second opening, wherein in the first opening, the display section includes a distance window to enable visually recognizing a distance indication provided on a circumferential surface of the display body, and wherein in the second opening, the release switch is disposed.
8. A lens barrel, comprising: a movable device to adjust an optical system; an operation section having a coupling section to be coupled with the movable device to control movement of the movable device; and a display section disposed in line with the operation section in a direction around an optical axis of the lens barrel to overlap with the operation section in a direction of the optical axis, the display section including a display body that is movable in displaying a state of the optical system adjusted by the movable device, wherein the display body of the display section is disposed to overlap the coupling section of the operation section in a radial direction of the lens barrel, wherein the movable device includes a ring that is rotatable around the optical axis in the lens barrel, wherein the display body of the display section is disposed on an outer-circumferential surface of the ring, and the coupling section of the operation section is disposed radially outside the outer-circumferential surface of the ring.
9. The lens barrel according to claim 8, wherein the coupling section of the operation section is disposed in an area in a circumferential direction of the ring, and the display body does not move to the area when the ring rotates.
10. The lens barrel according to claim 8, wherein the movable device is configured to adjust a focal position of the optical system, wherein the display section is a distance display section to display the focal position of the optical system, and wherein the display body is a distance scale body provided with a distance indication.
11. The lens barrel according to claim 10, wherein the movable device further includes a differential device that includes a first input of a manual focus adjustment device and a second input of an automatic focus adjustment device of the optical system, wherein the ring is an output ring of the differential device, and wherein the operation section is a release switch to release a connected state of the manual focus adjustment device.
12. The lens barrel according to claim 11, wherein the output ring supports a planetary roller in at least a part of the output ring in the circumferential direction, and wherein the operation section is disposed in an area to which the planetary roller does not move when the output ring rotates.
13. The lens barrel according to claim 11, further comprising: a stationary ring having a first opening and a second opening, wherein in the first opening, the display section includes a distance window to enable visually recognizing a distance indication provided on a circumferential surface of the display body, and wherein in the second opening, the release switch is disposed.
14. A lens barrel, comprising: a movable device to perform a focus adjustment of an optical system, the movable device including a ring that is rotatable around an optical axis in the lens barrel; a switch to switch between an automatic focus adjustment mode and a manual focus adjustment mode, with the movable device; and a display section disposed to overlap the switch in a direction of an optical axis of the lens barrel and overlap the switch in a part in a radial direction of the lens barrel, the display section to display a state of the optical system adjusted by the movable device, wherein the display body of the display section radially projects from an outer-circumferential surface of the ring.
15. An imaging device comprising the lens barrel according to claim
14.
|
js concatenates an integer value to an integer array element instead of adding them together
Following is a js function where I am trying to add the amt input from user, to pmt_arry[month] and pmt_arry[13] integer array elements. But, instead of adding the numeric value of amt input, js simply concatenates it as string. I don't understand how js thinks. I am including the console output as well further below. As can be seen in the output, the two payments of 225 each should be added to pmt_arry[11] and pmt[13] to make them 450 each but js simply concatenates them as 225225 and 225225. Please help.
function updCurryrPmtData(username, month, amt, callback) {
con.query('SELECT * FROM havuzs_sakinleri WHERE isim = ?', [username], function(err, rows) {
if (err) // If error in updating the database, display error message.
throw err;
rows.forEach((row)=> {
pmt_arry = [0, row.ay1_odemesi, row.ay2_odemesi, row.ay3_odemesi, row.ay4_odemesi,
row.ay5_odemesi, row.ay6_odemesi, row.ay7_odemesi, row.ay8_odemesi, row.ay9_odemesi,
row.ay10_odemesi, row.ay11_odemesi, row.ay12_odemesi, row.toplam_odenen_tl];
pmt_arry = pmt_arry.map(Number);
console.log('pmt_arry before: ', pmt_arry);
pmt_arry[month] = pmt_arry[month] + amt;
pmt_arry[13] = pmt_arry[13] + amt;
console.log('pmt_arry after: ', pmt_arry);
calcTotPayable(username, function(response) {
var totpayable_curryr = response - amt;
console.log('totpayable_curryr: ', totpayable_curryr );
var sql = "UPDATE havuzs_sakinleri SET ay1_odemesi = ?, ay2_odemesi = ?, ay3_odemesi = ?, ay4_odemesi = ?, " +
"ay5_odemesi = ?, ay6_odemesi = ?, ay7_odemesi = ?, ay8_odemesi = ?, ay9_odemesi = ?, ay10_odemesi = ?, " +
"ay11_odemesi = ?, ay12_odemesi = ?, toplam_odenen_tl = ?, aidat_bakiye = ? WHERE isim = ? ";
con.query(sql, [pmt_arry[1], pmt_arry[2], pmt_arry[3], pmt_arry[4], pmt_arry[5], pmt_arry[6], pmt_arry[7],
pmt_arry[8], pmt_arry[9], pmt_arry[10], pmt_arry[11], pmt_arry[12], pmt_arry[13], totpayable_curryr,
username], function(err, res) {
if (err) // If error in updating the database, display error message.
{ throw err;
status_message=('Aylik aidat güncellenirken sorun oluştu.');
}
else // If update is successful, display a message.
status_message = ("Bu site sakininin aylık ödemeleri güncellendi!");
return callback(status_message);
});
});
});
});
};
Following is the console output before and after the addition.
Just to be sure try and convert amt into Number before adding it.
amt is already an integer. Nonetheless, I have tried converting it by 'amt = amt.map(Number);'. But, node.js doesn't like it, it says 'TypeError: amt.map is not a function'.
I think amt is not an array that is why you can't use map(). Try and do amt = Number(amt).
I am a beginner but your level of js must be much more advanced. It works. I will add this to my important js tips-notes. Much appreciated, thanks.
|
Fraxinus pallisiae
Fraxinus pallisiae is a species of flowering plant belonging to the family Oleaceae.
Its native range is Southeastern Europe to Moldova, Caucasus.
|
When Ant-Man fights Falcon, does he change size through his own choice?
When Ant-Man fought Falcon, Ant-Man became big again several times during the fight. One such instance is when Falcon punches Ant-Man. What caused Ant-Man to become big? Is it something the suit does, or something deliberate from Ant-Man's choosing or something else?
Reference:
Ant-Man was such an unfortunate movie, I don't know even if I want to see it in MCU.
At 1:15 it looks like Falcon tries to stomp him and he stays small, but at 1:28 Falcon punches him and Ant-Man becomes big.
@apollo: boooo. It’s fun! Paul Rudd is charming!
Falcon also does some weird double punch/wing clap thing at 1:47 that causes Ant-Man to become big again.
@PaulD.Waite Boo to you! I like Paul Rudd. I just didn't like the movie.
Here's a better question. When Ant-Man was fighting the Falcon, was he disappointed they couldn't get a bigger star to do a cameo?
@VenomFangs: Since the movie doesn't seem to explicitly note whether it's intentional, what can I do to improve my answer for you?
The punch you reference at 1:28, I'm pretty sure that Ant-Man was trying to do the "size change punch" like he did at 0:58, but Falcon anticipated him. At 1:47, there's something weird going on, but it looks to me that Falcon was trying to generate wind to blow the tiny Ant-Man, so Ant-Man grew again so as to use his increased mass / surface area to slow himself (really, shouldn't he have maintained conservation of velocity like he does on his punches, though?).
So yes, it looks like he's consciously choosing to change his size as a strategic measure.
Increasing surface area for 1:47 makes sense. I watched 0:58 several times and he shrinks then jumps up and punches, as he's still small after the punch. So 1:28 still doesn't make sense to me.
The one at 1;47 looks like the Falcon got lucky and hit him in such a way that it made the suit make him big again, perhaps a glancing blow on the wrist?
@Richard, I thought the same thing but going slow through 1:28 (pause play pause play...), it looks like he's starting to get big before the impact of the punch and the result is the punch landing on his chest. I'm not sure if being big has any advantage to taking the punch, as being small with the density seems like it might be better? But that leads me to the question about how he's blown away so easily if he really does have the density/mass... and how he can ride on the bee's back. I'm left with more questions instead of figuring out the answer :)
There's been some speculation as to whether they kept the original Ant-Man's "same density when shrunk" or The Atom's "manipulate size and mass" to allow for more tricks involving hitting someone c.f. this discussion at http://scifi.stackexchange.com/a/93231/23243
@VenomFangs - Pfft. This whole 'let's go to the Avengers HQ to pick up the Macguffin" sequence was tacked on at the last minute and lacks any coherence.
|
Category:Flora of Western Canada
This category includes the Flora of Western Canada, in North America. It includes flora taxa that are native to Western Canada. Taxa of the lowest rank are always included. Higher taxa are included only if endemic. For the purposes of this category, "Western Canada" is defined in accordance with the World Geographical Scheme for Recording Plant Distributions. That is, the geographic region is defined by the political boundaries of its constituents:
* Alberta
* British Columbia
* Manitoba
* Saskatchewan
|
Microsoft KB Archive/36025
COBOL Version 2.x RUNCOB /P Switch Not Supported in 3.0
PSS ID Number: Q36025 Article last modified on 04-20-1993
2.00 2.10 2.20 3.00 | 3.00 MS-DOS | OS/2
Additional reference words: 2.00 2.10 2.20 3.00 Copyright Microsoft Corporation 1993.
|
Thread:Noobyrblx011/@comment-32769624-20191106173745
Hi, I'm an admin for the community. Welcome and thank you for your edit to Beehive!
Enjoy your time at !
|
arm_cortex-a9_vfpv3
The ARM® Cortex®-A9 processor is a popular general purpose choice for low-power or thermally constrained, cost-sensitive 32-bit devices.
The Cortex-A9 processor is proven in a wide range of devices and is one of ARM's most widely deployed and mature applications processors. Cortex-A9 processor offers an overall performance enhancement over 25% higher than Cortex-A8 per core, plus the ability to implement multi-core designs that further scale the performance increase.
The Cortex-A9 implements the widely supported ARMv7-A architecture with an efficient microarchitecture:
• High-efficiency, dual-issue superscalar, out-of-order, dynamic length pipeline (8 – 11 stages)
• Highly configurable L1 caches, and optional NEON and Floating-point extensions
• Available as a Single processor configuration, or a scalable multi-core configuration with up to 4 coherent cores
For the most high-end 32-bit devices, Cortex-A17 delivers more performance and efficiency in a similar footprint than it’s predecessor, the Cortex-A9. They are based of a similar pipeline, with Cortex-A17 extending the capabilities in single thread performance and adding big.LITTLE support and virtualization that were not in the original Cortex-A9 offering.
source
This architecture is for cortex a9 processors with VFPUv3
Package architectureTargetSubtarget BrandModelVersion
arm_cortex-a9_vfpv3mvebucortexa9BuffaloLS421DE
arm_cortex-a9_vfpv3tegragenericCompuLabTrimSlice
arm_cortex-a9_vfpv3mvebucortexa9CteraC200V2
arm_cortex-a9_vfpv3mvebucortexa9GlobalscaleMirabox
arm_cortex-a9_vfpv3mvebucortexa9KobolHelios4
arm_cortex-a9_vfpv3mvebucortexa9LinksysWRT1200ACv1 (caiman), v2 (caiman)
arm_cortex-a9_vfpv3mvebucortexa9LinksysWRT32Xv1 (venom)
arm_cortex-a9_vfpv3mvebucortexa9LinksysWRT1900ACv1 (mamba)
arm_cortex-a9_vfpv3mvebucortexa9LinksysWRT1900ACv2 (cobra)
arm_cortex-a9_vfpv3mvebucortexa9LinksysWRT1900ACSv1 (shelby), v2 (shelby)
arm_cortex-a9_vfpv3mvebucortexa9LinksysWRT3200ACMv1 (rango)
arm_cortex-a9_vfpv3mvebucortexa9MarvellRD-A370-A1
arm_cortex-a9_vfpv3mvebugenericMarvellDB-A380-DDR3-AP
arm_cortex-a9_vfpv3mvebucortexa9MarvellArmada A385 DB AP
arm_cortex-a9_vfpv3mvebucortexa9MarvellArmada A370 DB
arm_cortex-a9_vfpv3mvebugenericMarvellRD-MV784MP-GP
arm_cortex-a9_vfpv3mvebucortexa9PlatHomeOpenBlocks AX3-4
arm_cortex-a9_vfpv3mvebucortexa9SolidRunClearFog Base
arm_cortex-a9_vfpv3mvebucortexa9SolidRunClearFog Prov2.1
arm_cortex-a9_vfpv3mvebucortexa9Turris CZ.NICOmniaCZ11NIC13, CZ11NIC20, CZ11NIC23
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
• Last modified: 2018/08/16 17:44
• by tmomas
|
Fix weld3 build by using newer arquillian-weld, weld 3.1.9.Final, geronimo fix for HV 6, build from 8 to 17
weld3 build is broken currently when running this profile - mvn clean install -PWeld3. Fixed it by updating arquillian. To error on side of caution, only fixed for weld 3. Also bumped weld to 3.1.9.Final. Build tested as passing using jdk 8.
Adding onto this PR the following
Add missing relativePath so that parent looks to .m2 cache instead of build space
Correct geronimo 2.0 spec as required level for hibernate validator 6.0 which was breaking on newer jdks
Add opens to tests for jdk through 17 support
Add jakarta.el for jdk through 17 support
Correct memory usage on tests since jdk 8
Hi @hazendaz ! Thanks a lot for these really cool fixes!
I picked them separately, sometimes squashed em and added minor changes. I think I grabbed all except the one I commented on (jakarta-el api) where I did not find why it should be necessary. Gonna close this PR now, but please ping us if you think we missed something!
Thanks again and looking forward to further contributions!
|
#pragma once
#include <glad\glad.h>
#include <string>
#include <vector>
#include <unordered_map>
#include <glm\vec3.hpp>
#include <glm\gtc\quaternion.hpp>
class GlLoader {
public:
struct MeshContext {
GLuint arrayObject = 0;
GLuint vertexBuffer = 0;
GLuint indexBuffer = 0;
uint32_t indexCount = 0;
};
struct TextureContext {
GLuint textureBuffer = 0;
};
struct ProgramContext {
GLuint program = 0;
};
struct MeshHierarchy {
struct Node {
bool hasMesh = false;
uint32_t parentNodeIndex = 0;
uint32_t meshContextIndex = 0;
glm::vec3 position;
glm::quat rotation;
glm::vec3 scale = { 1, 1, 1 };
std::string name;
};
std::vector<MeshContext> meshContexts;
std::vector<Node> nodes;
};
struct AttributeInfo {
uint32_t positionAttrLoc = 0;
uint32_t normalAttrLoc = 1;
uint32_t texcoordAttrLoc = 2;
//uint32_t tangentAttrLoc = 3;
//uint32_t bitangentAttrLoc = 4;
//uint32_t colourAttrLoc = 5;
//uint32_t boneWeightsAttrLoc = 6;
//uint32_t boneIndexesAttrLoc = 7;
};
private:
const AttributeInfo _attributeInfo;
std::unordered_map<std::string, GLuint> _loadedShaders;
std::unordered_map<std::string, ProgramContext> _loadedPrograms;
std::unordered_map<std::string, TextureContext> _loadedTextures;
std::unordered_map<std::string, MeshHierarchy> _loadedMeshes;
public:
GlLoader(AttributeInfo attributeInfo);
const ProgramContext* loadProgram(const std::string& vertexFile, const std::string& fragmentFile, bool reload = false);
const TextureContext* loadTexture(const std::string& textureFile, bool reload = false);
const MeshHierarchy* loadMesh(const std::string& meshFile, bool reload = false);
};
|
#calss header
class _CAMOUFLAGE():
def __init__(self,):
self.name = "CAMOUFLAGE"
self.definitions = [u'the use of leaves, branches, paints, and clothes for hiding soldiers or military equipment so that they cannot be seen against their surroundings: ', u'the way that the colour or shape of an animal or plant appears to mix with its natural environment to prevent it from being seen by attackers: ', u'something that is meant to hide something, or behaviour that is intended to hide the truth: ']
self.parents = []
self.childen = []
self.properties = []
self.jsondata = {}
self.specie = 'nouns'
def run(self, obj1 = [], obj2 = []):
return self.jsondata
|
Revert "[null-safety] enable null assertions for framework tests"
Reverts flutter/flutter#64071
New test failures:
1:53 +891 ~12 -1: /b/s/w/ir/k/flutter/packages/flutter/test/rendering/simple_semantics_test.dart: only send semantics update if semantics have changed [E]
'package:flutter/src/semantics/semantics.dart': Failed assertion: line 0: 'value != null': is not true.
dart:core _AssertionError._throwNewNullAssertion
package:flutter/src/semantics/semantics.dart SemanticsConfiguration.explicitChildNodes=
package:flutter/src/rendering/proxy_box.dart 4527:12 RenderSemanticsAnnotations.describeSemanticsConfiguration
test/rendering/simple_semantics_test.dart 69:11 TestRender.describeSemanticsConfiguration
package:flutter/src/rendering/object.dart 2524:7 RenderObject._semanticsConfiguration
package:flutter/src/rendering/object.dart 1429:34 RenderObject.attach
package:flutter/src/rendering/object.dart 3021:11 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/foundation/node.dart 132:13 AbstractNode.adoptChild
package:flutter/src/rendering/object.dart 1290:11 RenderObject.adoptChild
package:flutter/src/rendering/object.dart 3016:7 RenderObjectWithChildMixin.child=
test/rendering/rendering_tester.dart 170:23 layout
test/rendering/simple_semantics_test.dart 31:5 main.<fn>
01:55 +897 ~12 -2: /b/s/w/ir/k/flutter/packages/flutter/test/rendering/reattach_test.dart: objects can be detached and re-attached: layout [E]
'package:flutter/src/semantics/semantics.dart': Failed assertion: line 0: 'value != null': is not true.
dart:core _AssertionError._throwNewNullAssertion
package:flutter/src/semantics/semantics.dart SemanticsConfiguration.explicitChildNodes=
package:flutter/src/rendering/proxy_box.dart 4527:12 RenderSemanticsAnnotations.describeSemanticsConfiguration
package:flutter/src/rendering/object.dart 2524:7 RenderObject._semanticsConfiguration
package:flutter/src/rendering/object.dart 1429:34 RenderObject.attach
package:flutter/src/rendering/object.dart 3021:11 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/custom_paint.dart 494:11 RenderCustomPaint.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/rendering/object.dart 3023:14 RenderObjectWithChildMixin.attach
package:flutter/src/foundation/node.dart 132:13 AbstractNode.adoptChild
package:flutter/src/rendering/object.dart 1290:11 RenderObject.adoptChild
package:flutter/src/rendering/object.dart 3016:7 RenderObjectWithChildMixin.child=
test/rendering/rendering_tester.dart 170:23 layout
https://api.cirrus-ci.com/v1/task/6444243294093312/logs/main.log
Also seen on LUCI.
Merging to green the build.
|
folkland
Etymology
From. Equivalent to.
Noun
* 1) Land held in villeinage, being distributed among the folk, or people, at the pleasure of the lord of the manor, and taken back at his discretion.
|
Talk:Clans & Alliances/@comment-25515075-20141130070107
Plz do edit Black ops sector 207 and change it to
Name: Black ops
sector : 146
with new badge
|
module RailsCoreExtensions
module ActionViewExtensions
def textilize(content)
super(h(content)).html_safe
end
# Generates a tooltip with given text
# text is textilized before display
def tooltip(hover_element_id, text, title='')
content = "<div style='width: 25em'>#{textilize(text)}</div>"
"<script>" +
"new Tip('#{hover_element_id}', '#{escape_javascript(content)}',"+
"{title : '#{escape_javascript title}', className: 'silver_smaller_div',"+
"showOn: 'mouseover', hideOn: { event: 'mouseout' }, fixed: false});"+
"</script>"
end
def boolean_select_tag(name, *args)
options = args.extract_options!
options ||= {}
yes_no_opts = [%w[Yes 1], %w[No 0]]
option_tags = options_for_select(yes_no_opts, options[:selected])
select_tag name, option_tags, options.except(:selected)
end
end
end
|
Thread:<IP_ADDRESS>/@comment-22439-20140129142919
Hi, welcome to ! Thanks for your edit to the Veronique Van den Bossche page.
Please leave me a message if I can help with anything!
|
When does a cached Big Query job expire?
I am currently using bigquery and whenever a query is run, the job is cached in memory and subsequent pages can be fetched from the cached table. So, is there a fixed expiration date for the cached tables? What factors does the job data persistence depend on? I am trying to see if the job still exists if I come back after a week or a month.
Directly from the docs (if you Google "App Engine BigQuery Caching") :
Results are cached for approximately 24 hours and cache lifetimes are extended when a query returns a cached result.
So basically, as long as you get your cached result once every 24 hours, cache should stay indefinitely.
Thanks. I was looking on the bigquery jobs page and couldn't find anything re the caching.
|
Talk:Carlos María Morales
External links modified
Hello fellow Wikipedians,
I have just added archive links to 1 one external link on Carlos María Morales. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
* Added archive https://web.archive.org/20071102105508/http://www.tenfieldigital.com.uy:80/servlet/hprfchsj?0,2,2%2F43%2F,1,3056 to http://www.tenfieldigital.com.uy/servlet/hprfchsj?0,2,2%2F43%2F,1,3056
Cheers.—cyberbot II Talk to my owner :Online 22:13, 26 January 2016 (UTC)
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.