text
stringlengths 0
128k
|
|---|
Joseph Constantine Carpue
Works:
* 1801 Description of the Muscles of the Human Body
* 1819 History of the High Operation for the Stone, by Inscision above the Pubis
External Reference:
* A Short Biography, Joseph Carpue
Joseph Constantine Carpue
|
import Controller from '@ember/controller';
export default Controller.extend({
loadMore() {
const model = this.get('model');
model.set('query.filter', reference => reference.orderBy('name').limit(5));
model.update();
},
});
|
package com.zj.wheelview.model;
/**
* Created by Administrator on 2016/4/21.
*/
public class PhotoInfo {
public String imgPath;//原始图路径
public String thumbImgPath;//缩略图路径
public boolean isSelected = false;
public String getImgPath() {
return imgPath;
}
public void setImgPath(String imgPath) {
this.imgPath = imgPath;
}
public boolean isSelected() {
return isSelected;
}
public void setSelected(boolean selected) {
isSelected = selected;
}
public String getThumbImgPath() {
return thumbImgPath;
}
public void setThumbImgPath(String thumbImgPath) {
this.thumbImgPath = thumbImgPath;
}
}
|
package peermanager
import (
"context"
"sync"
logging "gx/ipfs/QmbkT7eMTyXfpeyB3ZMxxcxg7XH8t6uXp49jqzz4HB7BGF/go-log"
bsmsg "gx/ipfs/QmcSPuzpSbVLU6UHU4e5PwZpm4fHbCn5SbNR5ZNL6Mj63G/go-bitswap/message"
wantlist "gx/ipfs/QmcSPuzpSbVLU6UHU4e5PwZpm4fHbCn5SbNR5ZNL6Mj63G/go-bitswap/wantlist"
peer "gx/ipfs/QmYVXrKrKHDC9FobgmcmshCDyWwdrfwfanNQN4oxJ9Fk3h/go-libp2p-peer"
)
var log = logging.Logger("bitswap")
var (
metricsBuckets = []float64{1 << 6, 1 << 10, 1 << 14, 1 << 18, 1<<18 + 15, 1 << 22}
)
// PeerQueue provides a queer of messages to be sent for a single peer.
type PeerQueue interface {
AddMessage(entries []bsmsg.Entry, ses uint64)
Startup()
AddWantlist(initialWants *wantlist.SessionTrackedWantlist)
Shutdown()
}
// PeerQueueFactory provides a function that will create a PeerQueue.
type PeerQueueFactory func(ctx context.Context, p peer.ID) PeerQueue
type peerMessage interface {
handle(pm *PeerManager)
}
type peerQueueInstance struct {
refcnt int
pq PeerQueue
}
// PeerManager manages a pool of peers and sends messages to peers in the pool.
type PeerManager struct {
// peerQueues -- interact through internal utility functions get/set/remove/iterate
peerQueues map[peer.ID]*peerQueueInstance
peerQueuesLk sync.RWMutex
createPeerQueue PeerQueueFactory
ctx context.Context
}
// New creates a new PeerManager, given a context and a peerQueueFactory.
func New(ctx context.Context, createPeerQueue PeerQueueFactory) *PeerManager {
return &PeerManager{
peerQueues: make(map[peer.ID]*peerQueueInstance),
createPeerQueue: createPeerQueue,
ctx: ctx,
}
}
// ConnectedPeers returns a list of peers this PeerManager is managing.
func (pm *PeerManager) ConnectedPeers() []peer.ID {
pm.peerQueuesLk.RLock()
defer pm.peerQueuesLk.RUnlock()
peers := make([]peer.ID, 0, len(pm.peerQueues))
for p := range pm.peerQueues {
peers = append(peers, p)
}
return peers
}
// Connected is called to add a new peer to the pool, and send it an initial set
// of wants.
func (pm *PeerManager) Connected(p peer.ID, initialWants *wantlist.SessionTrackedWantlist) {
pm.peerQueuesLk.Lock()
pq := pm.getOrCreate(p)
if pq.refcnt == 0 {
pq.pq.AddWantlist(initialWants)
}
pq.refcnt++
pm.peerQueuesLk.Unlock()
}
// Disconnected is called to remove a peer from the pool.
func (pm *PeerManager) Disconnected(p peer.ID) {
pm.peerQueuesLk.Lock()
pq, ok := pm.peerQueues[p]
if !ok {
pm.peerQueuesLk.Unlock()
return
}
pq.refcnt--
if pq.refcnt > 0 {
pm.peerQueuesLk.Unlock()
return
}
delete(pm.peerQueues, p)
pm.peerQueuesLk.Unlock()
pq.pq.Shutdown()
}
// SendMessage is called to send a message to all or some peers in the pool;
// if targets is nil, it sends to all.
func (pm *PeerManager) SendMessage(entries []bsmsg.Entry, targets []peer.ID, from uint64) {
if len(targets) == 0 {
pm.peerQueuesLk.RLock()
for _, p := range pm.peerQueues {
p.pq.AddMessage(entries, from)
}
pm.peerQueuesLk.RUnlock()
} else {
for _, t := range targets {
pm.peerQueuesLk.Lock()
pqi := pm.getOrCreate(t)
pm.peerQueuesLk.Unlock()
pqi.pq.AddMessage(entries, from)
}
}
}
func (pm *PeerManager) getOrCreate(p peer.ID) *peerQueueInstance {
pqi, ok := pm.peerQueues[p]
if !ok {
pq := pm.createPeerQueue(pm.ctx, p)
pq.Startup()
pqi = &peerQueueInstance{0, pq}
pm.peerQueues[p] = pqi
}
return pqi
}
|
International waste
International waste is any organic waste product that is deemed unsafe to be released into the environment or standard municipal solid waste stream that has originated from an external country, and sometimes territory. Such waste must be treated before it can be disposed of in the municipal solid waste stream to prevent sickness and environmental damage. If not managed properly, regulated garbage can have detrimental impacts on agriculture, livestock, and crops.
United States
The United States requires that all international waste must be sterilized through incineration or an autoclave. The rules and regulations for international waste and regulated garbage are determined by USDA's APHIS and US Customs and Border Protection. Regulated garbage includes international waste, which is defined as any organic material that originates outside of the United States, with the exception of Canada. Typically, such waste is not permitted for import into the United States, but exceptions for ships and airplanes landing in US ports can be made. Regulations must be followed for any company handling IW, such as recording when garbage was received and subsequently destroyed. Waste being transported to a treatment facility must avoid all rural areas, and if it must travel through a rural area, it must be ensured that the garbage is stored in a secure leak proof fashion, using approved agents for cleaning spills, and filing paperwork when waste needs to be transported between states.
Canada
Unlike the United States, Canada does not make an exception for international waste entering from the United States. Rules and restrictions are managed by Canadian Food Inspection Agency (CFIA) and the Canada Border Services Agency (CBSA). Regulations require that this type of waste must be placed in an orange bag. Along with autoclaving and incineration, Canada also allows international waste to be buried in a landfill, however the landfill must be approved the waste must be buried. The landfill must be 0.5 km from any livestock, precautions must be taken to prevent animals from entering, and the waste must be buried under 1.8 km of non-international waste.
United Kingdom
Known as "international catering waste" in the United Kingdom, specific regulations must be followed. This waste must be stored in "covered", "leak-proof", and "clearly labelled 'Category 1 – for disposal only'". Similar to Canada, disposing of the waste in a deep authorized landfill is acceptable. Additionally, along with incineration and autoclaving, processing the waste into biodiesel is acceptable.
Criticism
Strict regulations in Canada have made it difficult to establish an international marine terminal in Cape Breton, Nova Scotia. International waste from Marine terminals needed to be disposed of, and the only approves sites were both located in Dartmouth, on the other side of the province, meaning that the cost of disposal would be too high to allow foreign ships to enter the terminal.
|
Namespaces
Variants
Actions
Agatha
From Wowpedia
Jump to: navigation, search
Agatha
Gender Female
Race Val'kyr (Humanoid)
Reaction Alliance Horde
Location Tirisfal Glades and Silverpine Forest
Status Deceased
Agatha is a val'kyr in service to the Dark Lady.
Contents
History
Notable appearances
Location Level Health
Deathknell 10 11,880
Silverpine Forest 15 19,680
Edge of Night
This section concerns content exclusive to the Warcraft novels or short stories.
Agatha was present when Sylvanas Windrunner almost committed suicide. Annhylde the Caller and Agatha tried to stop her. Agatha, being the youngest of the battlemaidens in life and the most impatient in her undeath, tried to convince her by reminding her of the Forsaken, though Sylvanas did not care.
Cataclysm
This section concerns content exclusive to Cataclysm.
Agatha is the first person new Forsaken players meet, as she is the one that raises them back into the world of the "living".
She is present for the meeting between Garrosh and Sylvanas, where Sylvanas reveals that the val'kyr have joined the Forsaken. Agatha then resurrects the nearby fallen corpses as Forsaken, much to the disgust of Garrosh and High Warlord Cromush.
Agatha later helps the player by taking them to Fenris Isle and aids the player in fleeing when the refugees from Hillsbrad become Worgen. Agatha later appears in Sepulcher and The Forsaken Front where she aids in the resurrection of Lord Godfrey and his lieutenants.
When Lord Godfrey betrays and kills Sylvanas, Agatha and her fellow val'kyr Arthura and Daschla sacrifice themselves to resurrect the Dark Lady.
Trivia
The names of the three val'kyr may be a reference to the three precogs in Minority Report named Agatha, Arthur, and Dashiell. In the movie, Agatha is the strongest of the three and most featured, similar to her Val'kyr counterpart.
Quotes
• Life is meaningless. It is in the afterlife that we are truly tested.
• I long for the frozen wastes of Northrend.
• Do you feel it, <name>? The darkness surrounds us.
• The warmth of this place sickens me.
• Through me the Banshee Queen sees all...
• Different master, same insatiable thirst for power.
Patch changes
External links
|
User talk:<IP_ADDRESS>
Welcome, <IP_ADDRESS>!
* Questions? Need help? Don't know what to do? Just post a message on my talk page!
* Follow our policies, to make sure that all of us get along harmoniously.
* Sign in every time you edit, so that we can recognize you.
* Read the Blog Policy before making blogs.
I'm really happy to have you here, and look forward to working with you! Have fun!
Greetings,Vidmas7er (talk) 15:34, August 28, 2016 (UTC)
|
#pragma once
#define ME_INLINE __forceinline
#include <crtdbg.h>
typedef void (*FreeMethod)();
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// <summary>
// The Delegate Class definition.
// based on: https://blog.molecular-matters.com/2011/09/19/generic-type-safe-delegates-and-events-in-c/
// </summary>
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
class Delegate
{
private:
void* _instance; // instance if class pointer
void (*_member)(void*); // member function.
public:
typedef void* InstancePtr;
typedef void (*InternalFunction)(InstancePtr);
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// <summary>
// turns a free function into our internal function stub
// </summary>
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
template <void (*Function)()>
static ME_INLINE void FunctionStub(InstancePtr)
{
// we don't need the instance pointer because we're dealing with free functions
return (Function)();
}
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// <summary>
// turns a member function into our internal function stub
// </summary>
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
template <class C, void (C::* Function)()>
static ME_INLINE void ClassMethodStub(InstancePtr instance)
{
// cast the instance pointer back into the original class instance
return (static_cast<C*>(instance)->*Function)();
}
public:
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// <summary>
// Simple constructor.
// </summary>
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Delegate(void) : _instance(nullptr), _member(nullptr)
{
}
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// <summary>
// Binds a free function
// usage: Delegate delegate; delegate.Bind<&FreeFunction>(); delegate.Invoke();
// </summary>
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
template <void (*Function)()>
void Bind(void)
{
_instance = nullptr;
_member = &FunctionStub<Function>;
}
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// <summary>
// Binds a class method
// usage: Class c; Delegate delegate; delegate.Bind<Class, &Class::MemberFunction>(&c); delegate.Invoke();
// </summary>
// <param name="instance"> The class instance.</param>
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
template <class C, void (C::* Function)()>
void Bind(C* instance)
{
_instance = instance;
_member = &ClassMethodStub<C, Function>;
}
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// <summary>
// Invoke and execute the delegate.
// </summary>
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
void Invoke() const
{
_ASSERT_EXPR(_member != nullptr, "Cannot invoke unbound delegate. Call Bind() first.");
_member(_instance);
}
};
|
644 THE LYMPHATICS.
they are provided on their course with several elongated glands, to which the lymphatic radicles that arise from the cervical portion of the trachea and oesophagus pass. On arriving near the entrance to the chest, they aro lost in the prepectoral glaiuls. Some of them, however, traverse these without dividing, and directly enter, on the left, the thoracic duct, and on the right, the great lymphatic vein. It has been even possible for us to inject the latter vessel by one of these canals exposed on the right side.
3. Submaxillary or Subglossal Glands.
They represent a fusiform mass situated at the bottom of the inter maxillary space, in the receding angle comprised between the digastricus on the one side, and the mylo-hyoideus and subscapulo-hyoideus muscles on the other, above and near to the external maxillary artery. The lymphatics of the tongue, cheeks, lips, nostrils, and nasal cavities join these glands. Their efferents reach the pharyngeal or guttural glands.
4. Prescapular Glands.
By their union they form a species of chain, at least twelve inches in length, placed on the course of the ascending branch of the inferior cervical artery, beneath the internal face of the levator humeri muscle, and descend ing close by the fixed insertion of the sterno-maxillaris muscle.
5. Brachial Glands.
Situated beneath the anterior limb, within the arm, these vessels are divided into two groups : one placed near the ulnar articulation, within the inferior extremity of the humerus ; the other disposed in a discoid mass behind the brachial vessels, near the common insertion of the adductor muscle of the arm and the great dorsal muscle.
The first group receives the vessels from the foot and the fore-arm, which accompany the superficial veins, or pass with the deep arteries and veins into the muscular interstices. It sends nine or ten flexuous branches to the second group, into which open directly the lymphatics of the arm and shoulder, and from which emerge a certain number of effereuts that pass, in company with the axillary vessels, to the prepectoral glands.
ARTICLE III. GREAT LYMPHATIC VEIN.
The second large receptive trunk of the lymphatic vessels, this great vein (the ductus lymphaticus dexter) leaves the prepectoral glands of the right side, and therefore becomes the general confluent of the lymphatics from the right anterior limb, the right axillary and superficial costal regions, as well as the right half of the head, neck, and diaphragm.
This trunk is only from three-fourths of an inch to two inches in length. " It usually opens at the junction of the jugulars, at the side of the canal, by an orifice furnished with a double semilunar valve. Sometimes one or two of the branches which concur to form it describe circumvolutions around the corresponding brachial trunks or some of its divisions, before joining the others. Lastly, it is not rare to see this lymphatic trunk anastomose
|
Skip to main content
ORIGINAL RESEARCH article
Front. Microbiol., 13 September 2017
Sec. Microbial Symbioses
Volume 8 - 2017 | https://doi.org/10.3389/fmicb.2017.01751
Estimating Herd Immunity to Amphibian Chytridiomycosis in Madagascar Based on the Defensive Function of Amphibian Skin Bacteria
• 1Zoologisches Institut, Technische Universität Braunschweig, Braunschweig, Germany
• 2Department of Biology, James Madison University, Harrisonburg, VA, United States
• 3Ecology and Evolutionary Biology, University of Michigan, Ann Arbor, MI, United States
• 4Department of Biology, University of Massachusetts Boston, Boston, MA, United States
• 5Department of Animal Biology, University of Antananarivo, Antananarivo, Madagascar
• 6Laboratoire National de Diagnostic Vétérinaire, Antananarivo, Madagascar
• 7Unit for Environmental Sciences and Management, North-West University, Potchefstroom, South Africa
• 8Illinois Natural History Survey University of Illinois at Urbana-Champaign, Champaign, IL, United States
For decades, Amphibians have been globally threatened by the still expanding infectious disease, chytridiomycosis. Madagascar is an amphibian biodiversity hotspot where Batrachochytrium dendrobatidis (Bd) has only recently been detected. While no Bd-associated population declines have been reported, the risk of declines is high when invasive virulent lineages become involved. Cutaneous bacteria contribute to host innate immunity by providing defense against pathogens for numerous animals, including amphibians. Little is known, however, about the cutaneous bacterial residents of Malagasy amphibians and the functional capacity they have against Bd. We cultured 3179 skin bacterial isolates from over 90 frog species across Madagascar, identified them via Sanger sequencing of approximately 700 bp of the 16S rRNA gene, and characterized their functional capacity against Bd. A subset of isolates was also tested against multiple Bd genotypes. In addition, we applied the concept of herd immunity to estimate Bd-associated risk for amphibian communities across Madagascar based on bacterial antifungal activity. We found that multiple bacterial isolates (39% of all isolates) cultured from the skin of Malagasy frogs were able to inhibit Bd. Mean inhibition was weakly correlated with bacterial phylogeny, and certain taxonomic groups appear to have a high proportion of inhibitory isolates, such as the Enterobacteriaceae, Pseudomonadaceae, and Xanthamonadaceae (84, 80, and 75% respectively). Functional capacity of bacteria against Bd varied among Bd genotypes; however, there were some bacteria that showed broad spectrum inhibition against all tested Bd genotypes, suggesting that these bacteria would be good candidates for probiotic therapies. We estimated Bd-associated risk for sampled amphibian communities based on the concept of herd immunity. Multiple amphibian communities, including those in the amphibian diversity hotspots, Andasibe and Ranomafana, were estimated to be below the 80% herd immunity threshold, suggesting they may be at higher risk to chytridiomycosis if a lethal Bd genotype emerges in Madagascar. While this predictive approach rests on multiple assumptions, and incorporates only one component of hosts' defense against Bd, their culturable cutaneous bacterial defense, it can serve as a foundation for continued research on Bd-associated risk for the endemic frogs of Madagascar.
Introduction
Host-associated symbiotic bacterial communities mediate protection against pathogens in multiple hosts, including plants (Haas and Défago, 2005), corals (Krediet et al., 2013), insects (Cafaro et al., 2011), bats (Hoyt et al., 2015), humans (Sanchez et al., 2016), and amphibians (Bletz et al., 2013; Walke and Belden, 2016). Next generation sequencing technologies have rapidly advanced our understanding of community composition and structure of host microbiotas; however, understanding the function of these communities requires alternative technologies and can be complicated. Culture-based studies can be of great value for determining microbial function. Understanding the functional capacity of culture isolates may help identify phylogenetic patterns of function and thus help to further elucidate how community composition is linked to function.
Bacteria can provide protection against the cutaneous chytrid fungus, Batrachochytrium dendrobatidis (Bd), which can cause the lethal disease, chytridiomycosis (Berger et al., 1998; Stuart et al., 2004; Lips et al., 2006; Cheng et al., 2011). Resident cutaneous microbes work together with the host's innate immune system to provide a first line of defense against invading pathogens, such as Bd (Becker and Harris, 2010). Bacterial symbionts isolated from amphibian skin can inhibit Bd growth through the production of anti-fungal compounds (Harris et al., 2006; Brucker et al., 2008a,b; Flechas et al., 2012; Woodhams et al., 2015); however, inhibitory strength of bacterial metabolites can differ among Bd genotypes (Antwis et al., 2015). Furthermore, the addition of particular bacterial species, such as Janthinobacterium lividum, to the skin of amphibians can increase host survival by reducing the burden of chytridiomycosis (Harris et al., 2009a,b; Vredenburg et al., 2011; Kueneman et al., 2016).
In a study of amphibians from the western USA, population persistence through the emergence of Bd has been linked to the proportion of amphibians with Bd-inhibitory bacteria residing on their skin (Lam et al., 2010). Lam et al. (2010) propose that a mechanism analogous to herd immunity may, in part, explain variation in population persistence when Bd emerges. This concept states that when a given percentage of the population is immunized or protected against a communicable disease, the disease will die out and the population will persist. This critical threshold is a function of an intrinsic property of the pathogen—its reproductive rate (R0). For several amphibian populations and communities, a herd immunity threshold of 80% appears to be a consistent cut-off, below which populations crash when the pathogen emerges, and above which populations persist in coexistence with Bd (Woodhams et al., 2007; Lam et al., 2010; Figure S1). Interestingly, for many human diseases, the herd immunity threshold percentage is also around 80% (Anderson and May, 1985; Fine, 1993; Gonçalves, 2008; Fine et al., 2011). From this, a hypothetical model can be derived for further testing: if 80% of amphibian individuals maintain at least one strongly Bd-inhibitory bacterium on their skin, the population may persist and coexist with Bd.
Madagascar is a hotspot for biodiversity conservation, home to more than 400 frog species, most of which are found nowhere else in the world (Vieites et al., 2009; Perl et al., 2014). Ecological niche modeling suggests that the eastern rainforest of Madagascar is highly suitable for Bd (Lötters et al., 2011) and it has a higher amphibian species richness compared to the more arid west (Brown et al., 2016). Until recently, Madagascar was considered naïve to Bd, but this pathogen has recently been detected in samples from multiple locations across Madagascar (Vredenburg et al., 2012; Weldon et al., 2013; Bletz et al., 2015). The lineage of Bd that is present in Madagascar has not yet been characterized, nor is its virulence known. The potential risk of Bd-associated declines is presumed high; however, there is essentially nothing known about the resident bacteria on Madagascar frogs and the role they may have in the hosts' defense against Bd. Probiotic therapies have been proposed as a possible disease mitigation strategy for combating chytridiomycosis (Bletz et al., 2013; Walke and Belden, 2016; Woodhams et al., 2016); therefore, culturing and characterizing the function of microbes from amphibian skin works toward a possible mitigation strategy against Bd.
We collected samples from over 500 Malagasy frogs from 14 locations, and cultured, sequenced, and characterized the Bd-inhibiting functional capacity of over 3,000 bacterial isolates in order to address the following questions: (1) Are bacteria residing on Madagascar frogs able to inhibit Bd?, (2) What is the phylogenetic distribution of cultured isolates and does Bd-inhibitory function correlate with bacterial phylogeny?, and (3) How does functional capacity of bacteria against Bd vary among different Bd genotypes? In addition, we use these functional data to estimate Bd-associated risk of amphibian communities based on their bacterial defense following the model proposed in Lam et al. (2010). Thus, we ask the questions, (4) Are certain amphibian communities in Madagascar likely to be at risk of developing chytridiomycosis based on their bacterial defense? and (5) Are particular host genera likely to be at risk of developing chytridiomycosis based on their bacterial defense? While bacterial defense makes up only one component of a host's defense against Bd, this approach can provide a step toward understanding Bd-associated risk for the endemic frogs of Madagascar.
Methods
Field Sampling
Field sampling took place during three field visits: 14 August–12 September 2013, 4 January–9 February 2014, and 5 November–15 December 2014. In total, 540 culturable skin microbe samples were collected from 14 localities and 93 different host species (Figure 1).
FIGURE 1
Figure 1. Sampling locations and sample sizes across Madagascar throughout the sampling period. Mitsinjo Breeding center is located in Andasibe (no additional point has been added for this location on the map). Parenthetical “JF” indicates sampling occurred in January–February 2014, and “ND” indicates sampling occurring in November–December 2014. The base map was obtained from www.worldofmaps.net. No permission is required from the copyright holders for the reproduction of this image. Points on the map were generated using Google Earth Pro and afterwards edited on Adobe Illustrator CS6 (Adobe, 2012).
Amphibians were captured during day and night surveys with clean nitrile gloves and were placed in sterile Whirl-Pak® bags (Nasco, Fort Atkinson, WI, USA). For skin microbe sampling, individuals were removed from the bag with a clean pair of nitrile gloves and were rinsed with 50 ml of filter- or UV-sterilized water. After rinsing, individuals were swabbed with 10 strokes on the ventral abdomen, 5 strokes on each ventral thigh, and 5 strokes on each foot using sterile rayon swabs (MW113, Medical Wire Equipment & Co. Ltd., Corsham, UK). Swabs were stored in microcentrifuge tubes containing 100–200 ul of Tryptic-Soy-Yeast-Extract + 20% Glycerol (TSYE+G) and were transported on ice (~4–10°C) until transfer to a −20°C freezer. Frogs were immediately released at the location of capture after sampling. This study was approved by the Institutional Animal Care and Use Committee of James Madison University (protocol #A01-15), and necessary research and access permits were obtained from the Malagasy Direction Générale des Forêts (DGF) and Madagascar National Parks for all sampling.
Bacterial Culturing
Samples were thawed, gently vortexed, and 25 μl of the TSYE+G storage solution was plated on 1% tryptone agar. While using only one culture medium may limit the diversity of bacteria cultured, the one used represents a general low nutrient medium that supports a wide variety of microorganisms, and was used, in part, because it is also a standard one used for culturing Bd. Plates were incubated at 21°C for 2 weeks, and were checked every 3 days for morphologically distinct bacterial colonies. For each sample, each morphologically distinct colony was isolated into pure culture, and subsequently was cryopreserved in TSYE+G solution for later Bd-growth inhibition testing and 16S rRNA sequencing.
Bd-Growth Inhibition Assays
A Bd isolate from the Global Pandemic Lineage (GPL), JEL 423, was used to characterize function of all bacterial isolates. In addition, a subset of 77 isolates (all from Isalo, Madagascar) were tested against a panel of Bd isolates, including four GPL isolates from different regions of the world (USA, Panama, Africa, and Australia), as well as one isolate endemic to Brazil, one isolate endemic to Switzerland, and one isolate endemic to Korea (Table 1). Bacterial cell-free supernatant (CFS) obtained from a single liquid culture of each isolate was used for testing against all Bd genotypes. Each isolate was tested for its functional capacity against Bd using the 96-well assay method described in Bell et al. (2013) and Becker et al. (2015). Briefly, Bd zoospores were collected by flooding 3–5 day-old plate cultures with 1% tryptone, allowing zoospores to be released from mature sporangia into the tryptone media. Bd zoospores (2 × 106) were grown in the presence of the CFS of each bacterial isolate in triplicate. Bacterial CFS was obtained by filtering a liquid culture grown in co-culture with Bd for 3 days on a shaker (250 rpm), through a 0.22 um filter. The following controls were included with each assay in triplicate: (1) positive control–1% tryptone + Bd zoospores; (2) nutrient-depleted control–sterile water + Bd zoospores; (3) heat-killed control–heat-killed Bd zoospores + 1% tryptone; and (4) negative control–1% tryptone only. Assay plates were incubated at 21°C, and growth was measured as optical density (OD) at 492 nm on a spectrophotometer on days 0, 3, and 7.
TABLE 1
Table 1. Genotypes of Bd used for growth-inhibition assays.
Bacterial Sequencing and Identification
DNA was extracted from bacterial isolates using one of three methods: (1) PrepMan Ultra (ThermoFisher Scientific, Waltham, MA, USA), (2) Chelex (Bio-rad, Hercules, CA, USA), or (3) MoBio UltraClean Microbial DNA isolation kit (MoBio, Carlsbad, CA, USA). The PrepMan protocol was as follows: suspend bacterial cells in 100 μl of PrepMan Ultra solution; vortex and incubate for 10 min at 100°C; centrifuge for 3 min at max speed; transfer supernatant to clean tube. The Chelex protocol was as follows: suspend bacterial cells in 100 μl of 5% Chelex solution; vortex and incubate for 20 min at 99°C; centrifuge for 2 min at max speed; transfer supernatant to clean tube. For MoBio extractions, the manufacturer's protocol was followed. Different methods were used to maximize cost efficiency and to extract troublesome bacterial cells.
Polymerase Chain Reactions (PCR) were used with the bacterial primers 27F and 907R to amplify part of the bacterial 16S rRNA gene from the extracted DNA of each bacterial isolate. Amplification was verified using gel electrophoresis, and each isolate was sequenced either using an in-house capillary sequencer (ABI 3130xl) or was sent for sequencing to LGC Genomics in Berlin, Germany. Sequencing produced approximately 500–800 bp for each bacterial isolate. Sequences were cleaned and a preliminary alignment was completed in order to trim to approximately equal lengths (~500–600 bp) in CodonCode Aligner. Trimmed sequences were then aligned with PyNAST in QIIME, and a phylogenetic tree was built using fasttree (Price et al., 2010). The resulting tree was visualized using the Interactive Tree of Life tool (Letunic and Bork, 2007). Taxonomy was assigned to each bacterial isolate with the Ribosomal Database Project Classifier using QIIME (Wang et al., 2007; Caporaso et al., 2010). Sequences were deposited in GenBank (accession numbers GenBank MF523799–MF526895).
Data Analysis
For each tested bacterial CFS, the proportional Bd growth was determined by dividing the slope (OD/Time) of Bd growth in the presence of a given bacterial CFS by the slope of Bd growth in the nutrient-depleted control. Using the nutrient depleted control represents the effect of bacterially-secreted metabolites on Bd growth while accounting for the potential effect on growth due to additional nutrients in the culture medium added into the positive control (Bell et al., 2013). This value was subtracted from 1 to obtain a proportional inhibition score for each isolate. Triplicates of each tested bacterial isolate were averaged to obtain a mean inhibition score.
Mantel correlations were used to test the phylogenetic independence of mean inhibition scores. More specifically, distance matrices of the patristic distances between bacterial isolates were compared to distances derived from mean inhibition scores of each isolate. Using the inferred phylogenetic tree, patristic distances between bacterial isolates were calculated with the ape and adephylo packages in R (Paradis et al., 2004; Jombart et al., 2010; R Core Team, 2016). Euclidean distances between mean inhibition scores were calculated in QIIME with the distance_matrix_from_mapping.py script. Mean inhibition was compared across bacterial orders using Kruskal-Wallis tests because the data could not be normalized. Two-way analysis of variance (ANOVA) was used to compare bacterial inhibition of Bd across Bd genotypes. Bd genotype and bacterial isolate ID were the main factors.
To apply the herd immunity model proposed in Lam et al. (2010), the following steps were taken. First, bacterial isolates exhibiting inhibition scores greater than 0.8 (i.e., reduced Bd growth by 80%) were considered “inhibitory.” This threshold was chosen because it represents a strong reduction in Bd growth, and similar thresholds have been used in other studies (e.g., Becker et al., 2015); note that this value is not related to the threshold in the herd immunity concept associated with the R0, which coincidentally is also 80% (see below). Second, each individual amphibian was classified as protected or not-protected based on the existence of at least one Bd-inhibitory isolate cultured from its skin. Next, the proportion of “protected” individuals was determined (1) for each sampled amphibian community (i.e., location) with more than 10 individuals sampled, and (2) for each host genera at two high diversity sites, Andasibe and Ranomafana (that is, the proportion of protected individuals was calculated considering all individuals within a given genus at the particular site). We estimated herd immunity from both the “community” and “host genera” perspective to address it from two scales: (1) a larger scale community framework, and (2) a finer scale examining specific host taxonomic groups within locations. Both frameworks were implemented because they carry different inherent assumptions. For example, variation in protection at the genus or species level could affect community level protection dynamics. For our estimates, we applied the hypothesis of an 80% herd immunity threshold, i.e., we considered a group of amphibians as protected by herd immunity if 80% of the individuals had at least one strongly Bd-inhibitory bacterium on their skin. It is important to note that community level investigations make assumptions about potential pathogen transmission dynamics in that they assume contact would be equally likely within or across species (i.e., spatial and contact homogeneity). While contact rates within a species are undoubtedly higher than across species, interspecies or inter-genera contact can be expected to occur frequently given the high spatial overlap and sympatry of amphibians in hyper-diverse locations (i.e. multiple species inhabit small microhabitat areas at relatively high densities). During breeding season when amphibian species congregate at water bodies inter-species contact could be even more probable. In this context, a community level framework can be seen as valid and informative.
Results
From the 540 sampled individuals, 3179 bacterial isolates were cultured and were successfully tested in Bd-growth inhibition assays. On average, 7.5 bacterial morphotypes were collected per frog. The cultured isolates were predominantly from the phylum Actinobacteria (57.3%) followed by Proteobacteria (27.1%, [Alpha-59.3%, Gamma-31.2%, Beta-9.4%]), Firmicutes (9.6%), and Bacteriodetes (5.2%) (Figure 2). Inhibitory isolates (reducing Bd growth by 80% or more) were identified in all four bacterial phyla represented in the data as well as in all the represented bacterial families (Figure S2).
FIGURE 2
Figure 2. Phylogenetic and taxonomic distribution of cultured isolates. (A) Phylogenetic tree of cultured isolates based on DNA sequences of the 16S rRNA gene (~500–600 bp in length). (B) Number of cultured isolates within each family of each phylum. Color coding corresponds to bacterial phyla.
Mean inhibition was weakly correlated with bacterial phylogeny (Mantel test- R = 0.04 p = 0.01). Furthermore, mean inhibition varied significantly across bacterial orders (KW chi-squared = 438.2, df = 16, p-value < 0.001, Figure 3). The orders Caulobacterales, Burkholderiales, Enterobacteriales, Pseudomonadales, Xanthamonadales, and Flavobacteriales consistently exhibited stronger inhibition than the other represented bacterial orders (Figure 3, Table 1). Mean inhibition also varied significantly at the family level (KW chi-squared = 675.2, df = 56, p-value < 0.001). In some bacterial families, the majority of the isolates were classified as inhibitory, including Caulobacteraceae (102/140), Weeksellaceae (60/83), Enterobacteriaceae (47/57), Pseudomonadaceae (18/24), and Xanthamondaceae (80/100), while other families had only a few inhibitory isolates, including Rhizobiaceae (7/39), Methylobacteriaceae, (4/70) and Staphylococcaceae (6/75) (Figure S2).
FIGURE 3
Figure 3. Mean Bd inhibition for bacterial isolates within each dominant order. Each black point represents the mean inhibition of a given bacterial isolate, and the red bars represent the mean inhibition score for each order. On the horizontal axis: 1 equals complete inhibition of Bd growth; 0 equals no inhibition; values less than 0 indicate facilitation of Bd growth. Color bars beside each order name correspond to bacterial phyla in Figure 2.
Testing of a subset of 77 bacterial isolates cultured from two frog species in Isalo (Mantella expectata: n = 57, Scaphiophyrne gottlebei: n = 20) showed that inhibition across Bd genotypes was not consistent (Table 2). Bacterial inhibition of Bd varied significantly among Bd genotypes [ANOVA–F(6, 76) = 15.46, p < 0.001, Table S1).
TABLE 2
Table 2. Mean Bd inhibition (1 = 100% inhibition of Bd growth) across multiple genotypes of Bd for the 57 bacterial isolates cultured from Mantella expectata. Isolates from Scaphiophyrne gottlebei are not shown.
We determined the proportion of protected individuals within each amphibian community (i.e., each sampled locations) and within each host genus at Andasibe and Ranomafana by defining an individual as “protected” if at least one of its cultured isolates was classified as inhibitory. Proportion of protected individuals differed across locations, ranging from 57 to 100%. Locations predicted to be unprotected included Farankaraina, Ambohitantely, Andasibe, Torotorofotsy, Antoetra, and Ranomafana-Vatoharanana, while Nosy Mangabe, Maroantsetra, Ankaratra, Ambatolampy, Ranomafana-Vohiparara, and Isalo were predicted to be protected (Figure 4). Proportion of protected individuals also varied among host genera at both selected sites. In Ranomafana, our predictions suggest that Boophis, Mantidactylus, and Platypelis fall below the herd immunity threshold, while Gephyromantis meets this threshold. In Andasibe, Boophis, Mantidactylus, Spinomantis, and Heterixalus fell below the herd immunity threshold, while the genera Aglyptodactylus, Blommersia, and Ptychadena surpassed this threshold (Figure 5).
FIGURE 4
Figure 4. Proportion of “protected” individuals across amphibian communities in Madagascar. Black coloring denotes location that meet or surpass the herd immunity threshold of 80% (i.e., predicted to be protected), and white coloring denotes locations that are below this threshold (i.e. predicted to be at risk). Dotted line represents the herd immunity threshold (80%). Map on the right shows the distribution of “protected” and “unprotected” locations across Madagascar. The base map was obtained from www.worldofmaps.net. No permission is required from the copyright holders for the reproduction of this image. Points on the map were generated using Google Earth Pro and afterwards edited on Adobe Illustrator CS6 (Adobe, 2012).
FIGURE 5
Figure 5. Proportion of “protected” individuals across host genera at two hyperdiverse sites in Madagascar. Black coloring denotes genera that meet or surpass the herd immunity threshold of 80% (i.e., predicted to be protected), and white coloring denotes genera that are below this threshold (i.e., predicted to be at risk). Dotted line represents the herd immunity threshold (80%).
Discussion
Phylogenetic and Taxonomic Distribution of Bd-Inhibitory Function
Bd inhibition by bacterial isolates derived from the skin of Malagasy amphibians was widespread across the bacterial phylogenetic tree, but mean inhibition was weakly correlated with bacterial phylogeny, suggesting that anti-Bd function may be at least in part phylogenetically conserved. This finding differs from that of a Panamanian frog skin bacteria study where inhibition was not correlated with bacterial phylogeny (Becker et al., 2015). The correlation herein was rather weak (Mantel R statistic = 0.04, but p-value of 0.01); therefore, bacterial phylogeny is likely not the main driver of inhibitory function against Bd, which could be associated with the highly flexible genomes of bacteria (Fuhrman, 2009). Bacterial genes can be readily transferred via horizontal gene transfer (Smillie et al., 2011). In fact, different bacterial species have been observed to transfer genes encoding for antifungal compounds (Ravel et al., 2000). Different bacterial taxa are also known to produce the same anti-fungal compounds, and this is even the case for known Bd-inhibitory compounds. For example, 2,4 DAPG is produced by both Pseudomonas (Pseudomonadaceae) and Lysobacter (Xanthamonadaceae), and violacein is produced by multiple taxa spanning across different bacterial genera including Janthinobacterium, Collimonas, Duganella, Pseudoalteromonas, and Microbulbifer (Brucker et al., 2008b; Choi et al., 2015).
Inhibitory taxa were found within all major bacterial orders and families which mirrors the findings of other studies (Harris et al., 2006; Woodhams et al., 2007; Flechas et al., 2012; Becker et al., 2015). Despite the fact that Bd inhibition was documented across nearly all taxonomic groups, certain bacterial groups appear to be composed of mainly inhibitory isolates [e.g., Caulobacteraceae (72%), Weeksellaceae (73%), Enterobacteriaceae (82%), Pseudomonadaceae (80%), and Xanthamondaceae (80%)] which might be responsible for the weak phylogenetic effect found in our overall data set. Many of these groups have been identified to have high proportions of inhibitory isolates in other amphibian studies as well (Becker et al., 2015). Pseudomonads, in particular, are well-documented in other systems including plants, crustaceans, fish, and bats as having pathogen-inhibiting effects (Spanggaard et al., 2001; Ramette et al., 2003, 2011; Balcázar et al., 2007; Kim et al., 2007; Cheng et al., 2016). Additionally, it is important to note that in vitro assays do not directly indicate in vivo function; other biotic and abiotic factors can influence the functional behavior of bacteria on amphibian skin.
Estimating Bd-Associated Risk based on Bacterial Defense
The functional characterization of the resident bacteria's ability to inhibit Bd was used to estimate the potential risk or susceptibility to Bd-associated declines in the context of the herd-immunity model proposed by Lam et al. (2010). This model is based on results from the Rana muscosa/sierrae system in the USA and from consideration of the concept of herd immunity in other systems. A population found co-existing with Bd had 80% of individuals with at least one Bd-inhibitory isolate, and a population below this 80% threshold was declining once Bd emerged in the population (Woodhams et al., 2007). In addition, a naïve population that met the 80% threshold did not go extinct while other naïve populations in this region went extinct (Lam et al., 2010). Several additional studies support this model (Figure S1).
While predictions within this framework provide an integrative look at how protection provided by bacteria varies across amphibian taxa and locations in Madagascar, it is important to note the following limitations of the model: (i) only the culturable community is considered, (i) bacterial interactions (antagonistic or synergistic) are not considered, (iii) the bacterial function assessment is based on high density in vitro testing (i.e., the hypothesis of antifungal activity does not take the in vivo density of a specific bacterium into account), and (iv) predictions are based on one GPL Bd isolate only. In general, dominant bacteria associated to the amphibian skin can be cultured with common techniques (Walke et al., 2015). To further support this within our study system, a comparison with data from Illumina-based sequencing of bacterial 16S amplicons from the skin of Malagasy amphibians (Bletz et al., 2017) suggests that a relatively high proportion of the dominant community members are represented among the cultured isolates [75% of top 80 illumina OTUs were present in the cultured isolates (Bletz, personal observation)]. Nevertheless, because additional (uncultured) members of the community might also inhibit Bd, our assessment of the number of protected individuals is conservative, and more individuals than estimated may have at least one Bd-inhibiting bacterium on their skin.
Our predictions based on the herd immunity model suggest that risk of developing chytridiomycosis varies across the landscape in Madagascar. Amphibian communities at some locations appear protected (above 80%), while others fall below this herd-immunity threshold. Locations predicted to be unprotected included Farankaraina, Ambohitantely, Andasibe, Torotorofotsy, Antoetra, and Ranomafana-Vatoharanana, while Nosy Mangabe, Maroantsetra, Ankaratra, Ambatolampy, Ranomafana-Vohiparara, and Isalo appear to be protected. There is no clear biogeographical or ecological pattern in the protected vs. unprotected categories; both contain localities from low-, mid-, and high-elevations, from eastern humid regions, and from drier regions of the central plateau (Brown et al., 2016). However, the fact that locations like Andasibe, Torotorofotsy, and Ranomafana-Vatoharanana are predicted to be at risk is particularly concerning considering these are all hyperdiverse mid-high elevation rainforest sites also predicted by ecological niche modeling to be highly suitable for Bd (Lötters et al., 2011). These sites are ecologically similar to places in Central America where drastic populations declines have occurred (La Marca et al., 2005; Lips et al., 2006). In addition, locations, such as Ambohitantely and Antoetra, are home to critically endangered species (Anodonthyla vallani and Mantella cowani, respectively) that have restricted distributions. It is important to note that our community predictions are based of variable numbers of species within the sampled locations and protection may vary non-randomly across host species or genera (see below); thus, these results should be taken as a preliminary look and continued research is needed to investigation complex community–infection dynamics that may occur in diverse amphibian assemblages.
Proportions of protected individuals also differed across host genera in Andasibe and Ranomafana, suggesting that Bd-associated risk would not be equal across amphibian hosts. Our predictions suggest that Boophis, Mantidactylus, Platypelis, Spinomantis, and Heterixalus, may be more at risk, at least at the sampled locations, while the genera Aglyptodactylus, Blommersia, Guibemantis, Gephyromantis, and Ptychadena are predicted to be protected. Interestingly, all of the potentially protected species, except Gephyromantis, are pond-breeding species, whereas the majority of Boophis and Mantidactylus, as well as all Spinomantis, are stream breeders. In general, stream-breeding amphibians are considered more susceptible to chytridiomycosis (Stuart et al., 2004). We hypothesize that genera such as Aglyptodactylus, Blommersia, Guibemantis, and Ptychadena (e.g., the pond breeders) might be protected against this disease by two mechanisms: (1) due to a high-proportion of individuals possessing Bd-inhibiting cutaneous bacteria, and (2) due to their microhabitat preferences, which include periodic stays in or near warm, stagnant water bodies that do not provide suitable conditions for survival of Bd (Kriger and Hero, 2007; Forrest and Schlaepfer, 2011). In addition, Aglyptodactylus and Ptychadena, and partly Blommersia and Gephyromantis, are ground-dwelling frogs, and perhaps their association with terrestrial habitats increases the abundance of transient and established fungal-inhibiting bacteria on their skin, as soil is known to be a species-rich and functionally diverse environment (Torsvik and Øvreås, 2002).
Toward Probiotics for Malagasy Amphibians
Probiotic therapies have been proposed as a possible disease mitigation strategy for combating chytridiomycosis (Bletz et al., 2013; Walke and Belden, 2016; Woodhams et al., 2016). To establish such therapies, culturing and characterizing function of microbes from amphibian skin is an important first step. One of the main objectives of this research was to evaluate the functional capacity of bacteria isolated from Madagascar frogs against Bd, and to determine whether Bd-inhibitory taxa are present. Indeed, inhibitory bacterial taxa were cultured: 39% (1241 isolates) of the cultured isolates inhibited Bd by at least 80%, and 26% (829 isolates) inhibited Bd by at least 90%. These strongly inhibitory taxa can all serve as potential probiotic candidates for Madagascar's frogs if a lethal Bd genotype arrives in Madagascar. Bd-inhibition was found herein and in other studies (Antwis et al., 2015) to vary across Bd genotypes; that is, not all bacteria could consistently inhibit a panel of Bd genotypes, which has important implications for development of probiotic disease mitigation strategies. Ideal probiotics will be bacterial isolates that do demonstrate broad spectrum Bd-inhibitory function; that is, they have high inhibition scores (>80%) across Bd variants, and have a low standard deviation across replicates (Figure 6). While function across Bd genotypes varied for the bacterial isolates tested, there were some bacterial isolates with broad-spectrum Bd-inhibitory function, such as a Chryseobacterium trutae, a Elizabethkingia miricola, a Pedobacter nutrimenti, and a Delftia acidovorans (Table S2).
FIGURE 6
Figure 6. Selecting bacterial isolates with functional consistency across Bd genotypes. Scatterplot displays mean inhibition vs. standard deviation of inhibition across Bd genotypes. The ideal probiotic candidates will be those with strong inhibitory function and low standard deviation. Points are colored from gray to black to illustrate increasing potential effectiveness as a probiotic.
These results serve as a basis for continued development of probiotic disease mitigation strategies for the frogs of Madagascar by providing a bank of potential probiotics. In addition, they provide an initial estimate of Bd-associated risk across Madagascar, which can facilitate prioritization of locations and host genera that appear to be more at risk. It is important to acknowledge that bacterial defense is only one component of a host's defense against Bd; therefore, our predictive approach must be taken as preliminary hypothesis, and as a stimulus for future research on Bd-associated risk for the frogs of Madagascar. Continued research on host protection (bacterial and host-produced defenses) against disease is needed to improve our understanding of disease risk across the landscape in Madagascar and help inform integrative conservation management planning. Future research should continue along the probiotic selection steps outlined in Bletz et al. (2013) by working toward identifying which Bd-inhibitory taxa can colonize and persist on frog hosts. Bioaugmentation as a mitigation tool requires a deeper understanding of bacterial community assembly and stability in the context of the amphibian host community and their skin secretions (Garner et al., 2016), which will be an important part of future research. Before probiotics can be widely implemented as a long-term management strategy for wild amphibian populations broader aspects including the potential risk probiotics pose to ecosystems and public health must been assessed (Woodhams et al., 2016). However, provided that candidate bacteria meet the necessary criteria, bioaugmentation could be far more cost-effective, ethical and less controversial than the current alternative treatment, namely chemicals (Garner et al., 2016). Continued probiotic research will bring us one step closer to an integrative probiotic approach for mitigating possible Bd-associated declines in Madagascar.
Author Contributions
MB and RH designed project with significant input from FR, CW, DE, and MV. MB, FR, AR, CW, DE and RH conducted sampling. MB, JM, and AR performed laboratory work. MB completed data analysis and wrote the paper. All authors contributed to revision of the manuscript and have approved the final manuscript.
Conflict of Interest Statement
The authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.
Acknowledgments
We are grateful to the Malagasy authorities for issuing research and export permits for this research. We are indebted to numerous local guides and field assistants that help during field work. We thank Kelsey Savage and Tiffany Bridges for help with laboratory culturing and growth assays. This study was supported by a grant from the Mohamed bin Zayed Conservation Fund to MB and RH, a grant from the Amphibian Survival Alliance to MB, RH, and MV, a grant from Chester Zoo to MB and RH, a scholarship of the German Academic Exchange Service (DAAD) to MB, and a grant from the Deutsche Forschungsgemeinschaft (DFG) to MV (VE247/9-1).
Supplementary Material
The Supplementary Material for this article can be found online at: https://www.frontiersin.org/article/10.3389/fmicb.2017.01751/full#supplementary-material
References
Anderson, R. M., and May, R. M. (1985). Vaccination and herd immunity to infectious diseases. Nature 318, 323–329. doi: 10.1038/318323a0
PubMed Abstract | CrossRef Full Text | Google Scholar
Antwis, R. E., Preziosi, R. F., Harrison, X. A., and Garner, T. W. (2015). Amphibian symbiotic bacteria do not show universal ability to inhibit growth of the global pandemic lineage of Batrachochytrium dendrobatidis. Appl. Environ. Microbiol. 81, 3706–3711. doi: 10.1128/AEM.00010-15
PubMed Abstract | CrossRef Full Text | Google Scholar
Balcázar, J. L., Rojas-Luna, T., and Cunningham, D. P. (2007). Effect of the addition of four potential probiotic strains on the survival of pacific white shrimp (Litopenaeus vannamei) following immersion challenge with Vibrio parahaemolyticus. J. Invertebr. Pathol. 96, 147–150. doi: 10.1016/j.jip.2007.04.008
PubMed Abstract | CrossRef Full Text | Google Scholar
Becker, M. H., and Harris, R. N. (2010). Cutaneous bacteria of the redback salamander prevent morbidity associated with a lethal disease. PLoS ONE 5:e10957. doi: 10.1371/journal.pone.0010957
PubMed Abstract | CrossRef Full Text | Google Scholar
Becker, M. H., Walke, J. B., Murrill, L., Woodhams, D. C., Reinert, L. K., Rollins-Smith, L. A., et al. (2015). Phylogenetic distribution of symbiotic bacteria from Panamanian amphibians that inhibit growth of the lethal fungal pathogen Batrachochytrium dendrobatidis. Mol. Ecol. 24, 1628–1641. doi: 10.1111/mec.13135
PubMed Abstract | CrossRef Full Text | Google Scholar
Bell, S. C., Alford, R. A., Garland, S., Padilla, G., and Thomas, A. D. (2013). Screening bacterial metabolites for inhibitory effects against Batrachochytrium dendrobatidis using a spectrophotometric assay. Dis. Aquat. Organ. 103, 77–85. doi: 10.3354/dao02560
PubMed Abstract | CrossRef Full Text | Google Scholar
Berger, L., Speare, R., Daszak, P., Green, D. E., Cunningham, A. A., Goggin, C. L., et al. (1998). Chytridiomycosis causes amphibian mortality associated with population declines in the rain forests of Australia and Central America. Proc. Natl. Acad. Sci. U.S.A. 95, 9031–9036. doi: 10.1073/pnas.95.15.9031
PubMed Abstract | CrossRef Full Text | Google Scholar
Bletz, M. C., Archer, H., Harris, R. N., McKenzie, V., Rabemananjara, F. C. E., Rakotoarison, A., et al. (2017). Host ecology rather than host phylogeny drives amphibian skin microbial community structure in the biodiversity hotspot of Madagascar. Front. Microbiol. 8:1530. doi: 10.3389/fmicb.2017.01530
PubMed Abstract | CrossRef Full Text | Google Scholar
Bletz, M. C., Loudon, A. H., Becker, M. H., Bell, S. C., Woodhams, D. C., Minbiole, K. P. C., et al. (2013). Mitigating amphibian chytridiomycosis with bioaugmentation: characteristics of effective probiotics and strategies for their selection and use. Ecol. Lett. 16, 807–820. doi: 10.1111/ele.12099
PubMed Abstract | CrossRef Full Text | Google Scholar
Bletz, M. C., Rosa, G. M., Crottini, E. A., Andreone, F., Schmeller, D. S., Rabibisoa, N. H. C., et al. (2015). Widespread presence of the pathogenic fungus Batrachochytrium dendrobatidis in wild amphibian communities in Madagascar. Sci. Rep. 5:8633. doi: 10.1038/srep08633
PubMed Abstract | CrossRef Full Text | Google Scholar
Brown, J. L., Sillero, N., Glaw, F., Bora, P., Vieites, D. R., and Vences, M. (2016). Spatial biodiversity patterns of Madagascar's amphibians and reptiles. PLoS ONE 11:e144076. doi: 10.1371/journal.pone.0144076
PubMed Abstract | CrossRef Full Text | Google Scholar
Brucker, R. M., Baylor, C. M., Walters, R. L., Lauer, A., Harris, R. N., and Minbiole, K. P. C. (2008a). The identification of 2,4-diacetylphloroglucinol as an antifungal metabolite produced by cutaneous bacteria of the salamander Plethodon cinereus. J. Chem. Ecol. 34, 39–43. doi: 10.1007/s10886-007-9352-8
PubMed Abstract | CrossRef Full Text | Google Scholar
Brucker, R. M., Harris, R. N., Schwantes, C. R., Gallaher, T. N., Flaherty, D. C., Lam, B. A., et al. (2008b). Amphibian chemical defense: antifungal metabolites of the microsymbiont Janthinobacterium lividum on the salamander Plethodon cinereus. J. Chem. Ecol. 34, 1422–1429. doi: 10.1007/s10886-008-9555-7
PubMed Abstract | CrossRef Full Text | Google Scholar
Cafaro, M. J., Poulsen, M., Little, A. E. F., Price, S. L., Gerardo, N. M., Wong, B., et al. (2011). Specificity in the symbiotic association between fungus-growing ants and protective Pseudonocardia bacteria. Proc. Biol. Sci. 278, 1814–1822. doi: 10.1098/rspb.2010.2118
PubMed Abstract | CrossRef Full Text | Google Scholar
Caporaso, J. G., Kuczynski, J., Stombaugh, J., Bittinger, K., Bushman, F. D., and Costello, E. K. (2010). QIIME allows analysis of high-throughput community sequencing data. Nat. Methods 7, 335–336. doi: 10.1038/nmeth.f.303
PubMed Abstract | CrossRef Full Text | Google Scholar
Cheng, T. L., Mayberry, H., McGuire, L. P., Hoyt, J. R., Langwig, K. E., Nguyen, H., et al. (2016). Efficacy of a probiotic bacterium to treat bats affected by the disease white-nose syndrome. J. Appl. Ecol. 54, 701–708. doi: 10.1111/1365-2664.12757
CrossRef Full Text | Google Scholar
Cheng, T. L., Rovito, S. M., Wake, D. B., and Vredenburg, V. T. (2011). Coincident mass extirpation of Neotropical amphibians with the emergence of the infectious fungal pathogen Batrachochytrium dendrobatidis. Proc. Natl. Acad. Sci. U.S.A. 108, 9502–9507. doi: 10.1073/pnas.1105538108
PubMed Abstract | CrossRef Full Text | Google Scholar
Choi, S. Y., Yoon, K., Lee, J. I., and Mitchell, R. J. (2015). Violacein: properties and production of a versatile bacterial pigment. Biomed. Res. Int. 2015, 1–8. doi: 10.1155/2015/465056
PubMed Abstract | CrossRef Full Text | Google Scholar
Fine, P. E. (1993). Herd immunity: history, theory, practice. Epidemiol. Rev. 15, 265–302. doi: 10.1093/oxfordjournals.epirev.a036121
PubMed Abstract | CrossRef Full Text | Google Scholar
Fine, P., Eames, K., and Heymann, D. L. (2011). “Herd immunity”: a rough guide. Clin. Infect. Dis. 52, 911–916. doi: 10.1093/cid/cir007
PubMed Abstract | CrossRef Full Text | Google Scholar
Flechas, S. V., Sarmiento, C., Cardenas, M. E., Medina, E. M., Restrepo, S., and Amezquita, A. (2012). Surviving chytridiomycosis: differential anti-Batrachochytrium dendrobatidis activity in bacterial isolates from three lowland species of Atelopus. PLoS ONE 7:e44832. doi: 10.1371/journal.pone.0044832
PubMed Abstract | CrossRef Full Text | Google Scholar
Forrest, M. J., and Schlaepfer, M. A. (2011). Nothing a hot bath won't cure: Infection rates of amphibian chytrid fungus correlate negatively with water temperature under natural field settings. PLoS ONE 6:e28444. doi: 10.1371/journal.pone.0028444
PubMed Abstract | CrossRef Full Text | Google Scholar
Fuhrman, J. A. (2009). Microbial community structure and its functional implications. Nature 459, 193–199. doi: 10.1038/nature08058
PubMed Abstract | CrossRef Full Text | Google Scholar
Garner, T. W. J., Schmidt, B. R., Martel, A., Pasmans, F., Muths, E., Cunningham, A. A., et al. (2016). Mitigating amphibian chytridiomycoses in nature. Philos. Trans. R. Soc. Lond. B Biol. Sci. 371:1709. doi: 10.1098/rstb.2016.0207
PubMed Abstract | CrossRef Full Text | Google Scholar
Gonçalves, G. (2008). Herd immunity: recent uses in vaccine assessment. Expert Rev. Vaccines 7, 1493–1506. doi: 10.1586/147605<IP_ADDRESS>3
PubMed Abstract | CrossRef Full Text | Google Scholar
Haas, D., and Défago, G. (2005). Biological control of soil-borne pathogens by fluorescent pseudomonads. Nat. Rev. Microbiol. 3, 307–319. doi: 10.1038/nrmicro1129
PubMed Abstract | CrossRef Full Text | Google Scholar
Harris, R. N., Brucker, R. M., Walke, J. B., Becker, M. H., Schwantes, C. R., Flaherty, D. C., et al. (2009a). Skin microbes on frogs prevent morbidity and mortality caused by a lethal skin fungus. ISME J. 3, 818–824. doi: 10.1038/ismej.2009.27
PubMed Abstract | CrossRef Full Text | Google Scholar
Harris, R. N., James, T. Y., Lauer, A., Simon, M. A., and Patel, A. (2006). Amphibian pathogen Batrachochytrium dendrobatidis is inhibited by the cutaneous bacteria of amphibian species. Ecohealth 3, 53–56. doi: 10.1007/s10393-005-0009-1
CrossRef Full Text | Google Scholar
Harris, R. N., Lauer, A., Simon, M. A., Banning, J. L., and Alford, R. A. (2009b). Addition of antifungal skin bacteria to salamanders ameliorates the effects of chytridiomycosis. Dis. Aquat. Organ. 83, 11–16. doi: 10.3354/dao02004
PubMed Abstract | CrossRef Full Text | Google Scholar
Hoyt, J. R., Cheng, T. L., Langwig, K. E., Hee, M. M., and Frick, W. F. (2015). Bacteria isolated from bats inhibit the growth of Pseudogymnoascus destructans, the causative agent of white-nose syndrome. PLoS ONE 10:e0121329. doi: 10.1371/journal.pone.0121329
PubMed Abstract | CrossRef Full Text | Google Scholar
Jombart, T., Balloux, F., and Dray, S. (2010). Adephylo: new tools for investigating the phylogenetic signal in biological traits. Bioinformatics 26, 1907–1909. doi: 10.1093/bioinformatics/btq292
PubMed Abstract | CrossRef Full Text | Google Scholar
Kim, J., Kim, B., and Lee, C. (2007). Alga-lytic activity of Pseudomonas fluorescens against the red tide causing marine alga Heterosigma akashiwo (Raphidophyceae). Biol. Control 41, 296–303. doi: 10.1016/j.biocontrol.2007.02.010
CrossRef Full Text | Google Scholar
Krediet, C. J., Ritchie, K. B., Paul, V. J., and Teplitski, M. (2013). Coral-associated micro-organisms and their roles in promoting coral health and thwarting diseases. Proc. Biol. Sci. 280:20122328. doi: 10.1098/rspb.2012.2328
PubMed Abstract | CrossRef Full Text | Google Scholar
Kriger, K. M., and Hero, J. M. (2007). The chytrid fungus Batrachochytrium dendrobatidis is non-randomly distributed across amphibian breeding habitats. Divers. Distrib. 13, 781–788. doi: 10.1111/j.1472-4642.2007.00394.x
CrossRef Full Text | Google Scholar
Kueneman, J. G., Woodhams, D. C., Harris, R., Archer, H. M., Knight, R., McKenzie, V. J., et al. (2016). Probiotic treatment restores protection against lethal fungal infection lost during amphibian captivity. Proc. R. Soc. 283.1839:20161553. doi: 10.1098/rspb.2016.1553
CrossRef Full Text | Google Scholar
La Marca, E., Lips, K. R., Lötters, S., Puschendorf, R., Ibáñez, R., Rueda-Almonacid, J. V., et al. (2005). Catastrophic population declines and extinctions in Neotropical harlequin frogs (Bufonidae: Atelopus). Biotropica 37, 190–201. doi: 10.1111/j.1744-7429.2005.00026.x
CrossRef Full Text | Google Scholar
Lam, B. A., Walke, J. B., Vredenburg, V. T., and Harris, R. N. (2010). Proportion of individuals with anti-Batrachochytrium dendrobatidis skin bacteria is associated with population persistence in the frog Rana muscosa. Biol. Conserv. 143, 529–531. doi: 10.1016/j.biocon.2009.11.015
CrossRef Full Text | Google Scholar
Letunic, I., and Bork, P. (2007). Interactive Tree Of Life (iTOL): an online tool for phylogenetic tree display and annotation. Bioinformatics 23, 127–128. doi: 10.1093/bioinformatics/btl529
PubMed Abstract | CrossRef Full Text | Google Scholar
Lips, K. R., Brem, F., Brenes, R., Reeve, J. D., Alford, R. A., Voyles, J., et al. (2006). Emerging infectious disease and the loss of biodiversity in a Neotropical amphibian community. Proc. Natl. Acad. Sci. U.S.A. 103, 3165–3170. doi: 10.1073/pnas.0506889103
PubMed Abstract | CrossRef Full Text | Google Scholar
Lötters, S., Rödder, D., Kielgast, J., and Glaw, F. (2011). “Hotspots, conservation, and diseases: Madagascar's megadiverse amphibians and the potential impact of chytridiomycosis,” in Biodiversity Hotspots, eds F. E. Zachos and J. C. Habel (Berlin; Heidelberg: Springer), 255–274.
Paradis, E., Claude, J., and Strimmer, K. (2004). APE: analyses of phylogenetic and evolution in R language. Bioinformatics 20, 289–290. doi: 10.1093/bioinformatics/btg412
CrossRef Full Text | Google Scholar
Perl, R. G. B., Nagy, Z. T., Sonet, G., Glaw, F., Wollenberg, K. C., and Vences, M. (2014). DNA barcoding Madagascar's amphibian fauna. Amphibia Reptilia 35, 197–206. doi: 10.1163/15685381-00002942
CrossRef Full Text | Google Scholar
Price, M. N., Dehal, P. S., and Arkin, A. P. (2010). FastTree 2—approximately maximum-likelihood trees for large alignments. PLoS ONE 5:e9490. doi: 10.1371/journal.pone.0009490
PubMed Abstract | CrossRef Full Text | Google Scholar
R Core Team (2016). R: A Language and Environment for Statistical Computing. Vienna. Available online at: http://www.r-project.org/
Ramette, A., Frapolli, M., Saux, M. F. L., Gruffaz, C., Meyer, J. M., Défago, G., et al. (2011). Pseudomonas protegens sp. nov., widespread plant-protecting bacteria producing the biocontrol compounds 2,4-diacetylphloroglucinol and pyoluteorin. Syst. Appl. Microbiol. 34, 180–188. doi: 10.1016/j.syapm.2010.10.005
PubMed Abstract | CrossRef Full Text | Google Scholar
Ramette, A., Moënne-Loccoz, Y., and Défago, G. (2003). Prevalence of fluorescent pseudomonads producing antifungal phloroglucinols and/or hydrogen cyanide in soils naturally suppressive or conducive to tobacco black root rot. FEMS Microbiol. Ecol. 44, 35–43. doi: 10.1111/j.1574-6941.2003.tb01088.x
CrossRef Full Text | Google Scholar
Ravel, J., Wellington, E. M. H., and Hill, R. T. (2000). Interspecific transfer of Streptomyces giant linear plasmids in sterile amended soil microcosms. Appl. Environ. Microbiol. 66, 529–534. doi: 10.1128/AEM.66.2.529-534.2000
PubMed Abstract | CrossRef Full Text | Google Scholar
Sanchez, B., Delgado, S., Blanco-Miguez, A., Lourenco, A., Gueimonde, M., and Margolles, A. (2016). Probiotics, gut microbiota, and their influence on host health and disease. Mol. Nutr. Food Res. 201600240, 1–15. doi: 10.1002/mnfr.201600240
CrossRef Full Text | Google Scholar
Smillie, C. S., Smith, M. B., Friedman, J., Cordero, O. X., David, L. A., and Alm, E. J. (2011). Ecology drives a global network of gene exchange connecting the human microbiome. Nature 480, 241–244. doi: 10.1038/nature10571
PubMed Abstract | CrossRef Full Text | Google Scholar
Spanggaard, B., Huber, I., Nielsen, J., Sick, E. B., Pipper, C. B., Martinussen, T., et al. (2001). The probiotic potential against vibriosis of the indigenous microflora of rainbow trout. Environ. Microbiol. 3, 755–765. doi: 10.1046/j.1462-2920.2001.00240.x
PubMed Abstract | CrossRef Full Text | Google Scholar
Stuart, S. N., Chanson, J. S., Cox, N. A., Young, B. E., Rodrigues, A. S. L., Fischman, D. L., et al. (2004). Status and trends of amphibian declines and extinctions worldwide. Science 306, 1783–1786. doi: 10.1126/science.1103538
PubMed Abstract | CrossRef Full Text | Google Scholar
Torsvik, V., and Øvreås, L. (2002). Microbial diversity and function in soil: from genes to ecosystems. Curr. Opin. Microbiol. 5, 240–245. doi: 10.1016/S1369-5274(02)00324-7
PubMed Abstract | CrossRef Full Text | Google Scholar
Vieites, D. R., Wollenberg, K. C., Andreone, F., Köhler, J., Glaw, F., and Vences, M. (2009). Vast underestimation of Madagascar's biodiversity evidenced by an integrative amphibian inventory. Proc. Natl. Acad. Sci. U.S.A. 106, 8267–8272. doi: 10.1073/pnas.0810821106
PubMed Abstract | CrossRef Full Text | Google Scholar
Vredenburg, V. T., Briggs, C. J., and Harris, R. N. (2011). “Host-pathogen dynamics of amphibian chytridiomycosis: the role of the skin microbiome in health and disease,” in Fungal Diseases: an Emerging Threat to Human, Animal, and Plant Health, eds L. Olson, E. Choffnes, D. Relman, and L. Pray (Washington, DC: National Academy Press), 342–355.
Google Scholar
Vredenburg, V. V. T., Preez, L., Raharivololoniaina, L., Vieites, D. R., Vences, M., and Weldon, C. (2012). A molecular survey across Madagascar does not yield positive records of the amphibian chytrid fungus Batrachochytrium dendrobatidis. Herpetol. Notes 5, 507–517. Available online at: http://www.herpetologynotes.seh-herpetology.org/Volume5_PDFs/Vredenburg_Herpetology_Notes_Volume5_pages507-517.pdf (Accessed March 22, 2014).
Google Scholar
Walke, J. B., and Belden, L. K. (2016). Harnessing the microbiome to prevent fungal infections: lessons from amphibians. PLoS Pathog. 12:e1005796. doi: 10.1371/journal.ppat.1005796
PubMed Abstract | CrossRef Full Text | Google Scholar
Walke, J. B., Becker, M. H., Hughey, M. C., Swartwout, M. C., Jensen, R. V., and Belden, L. K. (2015). Most of the dominant members of amphibian skin bacterial communities can be readily cultured. App. Environ. Microbiol. 81, 6589–6600. doi: 10.1128/AEM.01486-15
PubMed Abstract | CrossRef Full Text | Google Scholar
Wang, Q., Garrity, G. M., Tiedje, J. M., and Cole, J. R. (2007). Naive Bayesian classifier for rapid assignment of rRNA sequences into the new bacterial taxonomy. Appl. Environ. Microbiol. 73, 5261–5267. doi: 10.1128/AEM.00062-07
PubMed Abstract | CrossRef Full Text | Google Scholar
Weldon, C., Crottini, A., Bollen, A., Rabemananjara, F. C. E., Copsey, J., Garcia, G., et al. (2013). Pre-emptive national monitoring plan for detecting the amphibian chytrid fungus in Madagascar. Ecohealth 10, 234–240. doi: 10.1007/s10393-013-0869-8
PubMed Abstract | CrossRef Full Text | Google Scholar
Woodhams, D. C., Alford, R. A., Antwis, R. E., Archer, H. M., Becker, M. H., Belden, L. K., et al. (2015). Antifungual isolates database of amphibian skin-associated bacteria and function against emerging fungal pathogens. Ecology 96, 595. doi: 10.1890/14-1837.1
CrossRef Full Text | Google Scholar
Woodhams, D. C., Bletz, M. C., Kueneman, J., and McKenzie, V. (2016). Managing amphibian disease with skin microbiota. Trends Microbiol. 24, 161–164. doi: 10.1016/j.tim.2015.12.010
PubMed Abstract | CrossRef Full Text | Google Scholar
Woodhams, D. C., Vredenburg, V. T., Simon, M. A., Billheimer, D., Shakhtour, B., Shyr, Y., et al. (2007). Symbiotic bacteria contribute to innate immune defenses of the threatened mountain yellow-legged frog, Rana muscosa. Biol. Conserv. 138, 390–398. doi: 10.1016/j.biocon.2007.05.004
CrossRef Full Text | Google Scholar
Keywords: anti-Bd bacteria, chytridiomycosis, amphibians, skin bacteria, Batrachochytrium dendrobatidis
Citation: Bletz MC, Myers J, Woodhams DC, Rabemananjara FCE, Rakotonirina A, Weldon C, Edmonds D, Vences M and Harris RN (2017) Estimating Herd Immunity to Amphibian Chytridiomycosis in Madagascar Based on the Defensive Function of Amphibian Skin Bacteria. Front. Microbiol. 8:1751. doi: 10.3389/fmicb.2017.01751
Received: 07 June 2017; Accepted: 28 August 2017;
Published: 13 September 2017.
Edited by:
Sebastian Fraune, University of Kiel, Germany
Reviewed by:
Sébastien Duperron, Université Pierre et Marie Curie, France
Suzanne Lynn Ishaq, University of Oregon, United States
Copyright © 2017 Bletz, Myers, Woodhams, Rabemananjara, Rakotonirina, Weldon, Edmonds, Vences and Harris. This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) or licensor are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.
*Correspondence: Molly C. Bletz<EMAIL_ADDRESS>
Download
|
Decorations. — Halls are brightened for bird nights with 2-cent Perry pictures. They are best remembered if grouped in families, a study of which may be made from Reed's " Bird Guide." They may be tacked on cloth or jjaper.
Lists. — All members are encouraged to make yearly lists of all the birds they can identify. Lecturers try to use care lest in rivalry for long lists there is carelessness in identification. Daily lists are even more educational than yearly.
year or on bird night may be awarded at the grange fair in autumn.
Contests. — 1. The miniature pictures of Reed's, of which there are 80, are far more accurate for identifying than Perry's. These pictures are grouped around the hall with names covered. Members write the names of these, and those who make the best lists receive appropriate prizes, as a book, " Land Birds," a bird box or simply an Audubon leaflet.
2. Each member wears something to represent a bird. This is more certain to succeed if some one person will furnish every member with a paper with the name of some bird " jumbled," namely, the letters mis I^laced, these to be pinned on the shoulder. Then all go about examin ing the names, and those who get the best lists have little prizes.
May. May is the greatest of all months for song.
The secretary of the bird committee at New Salem will furnish in foi-mation and eon-espond with any one interested in birds. The chair man at Princeton is always ready to help in the work.
Bird Club Exhibits.
Since the successful work of the Meriden Bird Club at Meriden, ISTew Hampshire, has become widely known through the efforts of the manager, Ernest Harold Baynes, many clubs have been organized for the .protection of birds, and Massachu setts has been one of the foremost States in this movement. In 1914 the Brush Hill Bird Club of Milton, Massachusetts, was organized, and under the leadership of its president, Dr. Joel A. Goldthwait, and its energetic general manager. Dr. Harris J. Kennedy, planned a unique exhibit of materials and ap pliances for attracting and feeding birds. The scope of this exhibition was enlarged to include almost everything relating to
|
Page:The seven great hymns of the mediaeval church - 1902.djvu/149
Rh
ULL of beauty tood the mother
By the manger, blet o'er other,
Where her little one he lays:
For her inmot oul's elation,
In its fervid jubilation,
Thrills with ectay of praie.
Oh! what glad, what rapturous feeling
Filled that bleed mother, kneeling
By the Sole-Begotten One!
How, her heart with laughter bounding,
She beheld the work atounding,
Saw His birth, the glorious Son.
|
"use strict";
var util = require('./util');
var indexes = require('./indexes');
var Promise = require('bluebird');
var _ = require('lodash');
var uuid = require('node-uuid');
var Transaction = function(fdb, db, index){
this.fdb = fdb;
this.db = db;
this.index = index;
this.operations = [];
this.commited = false;
}
/**
Creates a document in the given keypath.
*/
Transaction.prototype.create = function(keyPath, args)
{
if(_.isString(keyPath)){
keyPath = [keyPath];
};
var id = args._id ? args._id : uuid.v1();
return this.put(keyPath.concat(id), _.extend({_id: id}, args)).then(function(){
return id;
});
}
/**
Updates a document in the given keypath.
*/
Transaction.prototype.put = function(keyPath, args)
{
var _this = this;
if(_.isString(keyPath)){
keyPath = [keyPath];
};
var defer = Promise.defer();
this.operations.push(function(tr){
var tuples = makeTuples(keyPath, args);
_.each(tuples, function(tuple){
var value = _.last(tuple);
var key = _.initial(tuple);
var packedKey = _this.fdb.tuple.pack(key);
var packedValue = util.packValue(_this.fdb, value);
tr.set(packedKey, packedValue);
//
// Check if we need to update the index
//
var indexKeyPath = _.initial(keyPath);
indexKeyPath = indexKeyPath.concat(_.last(key, key.length - keyPath.length))
if(indexes.checkIndex(_this.index, indexKeyPath)){
indexes.writeIndex(_this.fdb,
tr,
indexKeyPath,
_.last(keyPath),
value);
}
});
defer.resolve();
return defer.promise;
});
return defer.promise;
}
/**
Returns a promise with the object at the given keypath (if any)
*/
Transaction.prototype.get = function(keyPath, fields, opts)
{
var _this = this;
var fdb = this.fdb;
if(_.isString(keyPath)){
keyPath = [keyPath];
};
var promise = new Promise(function(resolve, reject){
_this.operations.push(function(tr){
var range = fdb.tuple.range(keyPath);
var iter = tr.getRange(range.begin, range.end, {
limit: opts ? opts.limit : undefined,
streamingMode: fdb.streamingMode.want_all
});
var result;
iter.forEachBatch(function(arr, cb){
var len = arr.length;
for(var i=0; i<len; i++){
var kv = arr[i];
var tuple = fdb.tuple.unpack(kv.key);
result = result ? result : _.isNumber(_.last(tuple)) ? [] : {};
tuple.push(util.unpackValue(fdb, kv.value));
fromTuple(result, tuple.slice(keyPath.length));
}
cb();
}, function(err) {
if(err){
reject(err);
}else{
resolve(_.isEmpty(result) ? undefined: result);
}
})
return promise;
});
});
return promise;
}
Transaction.prototype.remove = function(keyPath)
{
var _this = this;
if(_.isString(keyPath)){
keyPath = [keyPath];
};
this.operations.push(function(tr){
var range = _this.fdb.tuple.range(keyPath);
tr.clearRange(range.begin, range.end);
return Promise.resolve();
});
return this;
}
Transaction.prototype.find = function find(keyPath, where, fields, options){
//
// Check if we can use some indexes to accelerate this query.
//
keyPath = _.isArray(keyPath) ? keyPath : [keyPath];
var _this = this;
var tuples = makeTuples(keyPath, where);
var promises;
_.each(tuples, function(tuple){
if(indexes.checkIndex(_this.index, _.initial(tuple))){
promises = promises || [];
var defer = Promise.defer();
_this.operations.push(function(tr){
defer.resolve(indexes.readIndex(_this.fdb, tr, tuple));
return defer.promise;
});
promises.push(defer.promise);
}
});
if(promises){
return Promise.all(promises).then(function(docs){
// Merge all objects
docs = _.extend.apply(_, docs);
// Get all the objects
var ids = Object.keys(docs);
return Promise.all(_.map(ids, function(id){
return _this.get(keyPath.concat(id));
})).then(function(docs){
docs = _.filter(docs, where);
// Filter them & _.pick
return fields ? _.map(docs, function(doc){
return _.pick(doc, fields);
}) : docs;
});
});
}else{
return this.get(keyPath).then(function(docs){
docs = _.filter(docs, where);
// Filter them & _.pick
return fields ? _.map(docs, function(doc){
return _.pick(doc, fields);
}) : docs;
});
}
}
Transaction.prototype.processOperations = function(tr, index)
{
var _this = this;
var results = [];
var operations = this.operations;
var task, i = index || 0;
try{
while(task = operations[i]) {
results.push(task(tr, this.fdb));
i++;
}
}catch(err){
return Promise.reject(err);
}
return Promise.all(results).then(function(){
return new Promise(function(resolve, reject){
process.nextTick(function(){
if(operations[i]){
resolve(_this.processOperations(tr, i));
}else{
resolve();
}
});
});
});
}
Transaction.prototype.commit = function(){
var _this = this;
//
// We use superior bluebird promises instead of fdb built-in ones.
//
return new Promise(function(resolve, reject){
_this.db.doTransaction(function(tr, cb){
_this.processOperations(tr).then(function(result){
cb(null, result);
}, cb);
}, function(err, result){
if(err) return reject(err);
_this.commited = true;
resolve(result);
});
});
}
/**
Creates an array of tuples from a given object.
*/
function makeTuples(prefix, args){
var result = [];
traverseToTuple(result, prefix, args)
return result;
}
function traverseToTuple(result, arr, args){
if(!_.isObject(args)){
// Pack primitive
arr.push(args);
result.push(arr);
}else{
_.each(args, function(value, key){
traverseToTuple(result, arr.concat(key), value);
});
};
}
/**
Creates an object from an array of tuples
*/
function makeObject(tuples){
var result = {};
_.each(tuples, function(tuple){
fromTuple(result, tuple);
});
return result;
}
function fromTuple(obj, tuple){
var i, len = tuple.length-2;
for(i=0; i<len; i++){
if (_.isUndefined(obj[tuple[i]])){
if(_.isNumber(tuple[i+1])){
obj[tuple[i]] = [];
}else{
obj[tuple[i]] = {};
}
}
obj = obj[tuple[i]];
}
obj[tuple[i]] = tuple[i+1];
}
module.exports = Transaction;
|
package com.nhsbsa.model;
import com.nhsbsa.model.MonthName;
import com.nhsbsa.model.MonthNum;
import org.junit.Test;
import static org.junit.Assert.assertEquals;
/**
* Created by nataliehulse on 10/11/2016.
*/
public class MonthNameTest {
private final MonthName months = new MonthName();
@Test
public void MonthNoShouldReturnCorrectName() {
String monthName = months.getMonthNameFromNum(2);
assertEquals("Should be equal", monthName, "February");
}
@Test
public void IncorrectMonthNoShouldReturnNull() {
String monthName = months.getMonthNameFromNum(0);
assertEquals("Should be equal", monthName, null);
}
}
|
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. error for excel
i use windows 7 home basic 64-bit and microsoft excel starter 2010 and i want to read an excel file but when i debug my code, i take this error: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
my code is the followings:
protected void Page_Load(object sender, EventArgs e)
{
GridView1.DataSource=getirExcel();
GridView1.DataBind();
}
DataTable getirExcel()
{
string dosya_adres = @"C:\Users\Erdi\Downloads\DBE_BAKIM_FORMU.xlsx";
OleDbConnection baglanti = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" + dosya_adres + ";Extended Properties=Excel 12.0");
baglanti.Open();
string query = "select * from [Sheet1$A1:D20]";
OleDbDataAdapter oAdp = new OleDbDataAdapter(query, baglanti);
DataTable dt = new DataTable();
oAdp.Fill(dt);
return dt;
}
i have tried Microsoft.JET.OLEDB.4.0 but it does not work for 64-bit according to forums. do you know any alternative provider?
thanks in advance..
You need to install the database engine here: http://www.microsoft.com/en-us/download/details.aspx?id=13255
|
Mesalamine for the treatment of cancer
ABSTRACT
Methods of treating renal cancer, including renal cell carcinoma, using mesalamine are disclosed herein. Mesalamine can be administered as a monotherapy or as part of a comprehensive treatment program, which can also include administration with other anti-cancer drugs, surgical treatments or exposure to ionizing radiation.
CROSS REFERENCE TO RELATED APPLICATION
This application is a continuation of U.S. application Ser. No. 15/637,007, now U.S. Pat. No. 9,867,865, filed Jun. 29, 2017, which claims the benefit of Indian Application<PHONE_NUMBER>75, filed on Jun. 30, 2016, the contents of which are hereby incorporated in their entirety.
FIELD OF THE INVENTION
The invention is directed to the treatment of cancer, especially renal cell carcinoma, using mesalamine, optionally in combination with one or more additional cancer therapeutics.
BACKGROUND
Renal cell carcinoma (RCC, also known as hypernephroma) is a kidney cancer that originates in the lining of the proximal convoluted tubule, the very small tubes in the kidney that transport GF (glomerular filtrate) from the glomerulus to the descending limb of the nephron. RCC is the most common type of kidney cancer in adults, responsible for approximately 80% of cases. It is also known to be the most lethal of all the genitourinary tumors. Initial treatment is most commonly a radical or partial nephrectomy and remains the mainstay of curative treatment. Where the tumor is confined to the renal parenchyma, the five year survival rate is 60-70%, but this is lowered considerably once metastases have spread. It is relatively resistant to radiation therapy and chemotherapy, although some cases respond to immunotherapy.
Renal-cell carcinoma affects approximately 150,000 people worldwide each year, causing close to 78,000 deaths annually, and its incidence seems to be increasing. RCC is not a single entity, but rather comprises the class of tumors of renal epithelial origin. Extensive histological and molecular evaluation has resulted in the development of a consensus classification of different RCC subtypes: (i) conventional (clear-cell) renal cell carcinoma; (ii) papillary renal cell-carcinoma; (iii) chromophobe renal carcinoma; (iv) onco-cytoma; (v) collecting-duct carcinoma. Although most cases of RCC seem to occur sporadically, an inherited predisposition to renal cancer accounts for 1-4% of cases and could involve the same genes that cause sporadic renal cancer. Over the past two decades, studies of families with inherited RCC have laid the groundwork for the identification of seven hereditary renal cancer syndromes, and the predisposing genes for five of these have been identified. The surprisingly diverse nature of these genes implicates various mechanisms and biological pathways in RCC tumorigenesis.
RCC has been conventionally treated using surgery, radiation therapy, immunotherapy, and molecular-targeted therapy. Surgical resection remains the only known effective treatment for localized renal cell carcinoma, and it also is used for palliation in metastatic disease. Targeted therapy and immunomodulatory agents are considered standard of care in patients with metastatic disease.
Options for chemotherapy and endocrine-based approaches are limited, and no hormonal or chemotherapeutic regimen is accepted as a standard of care. Objective response rates with chemotherapy, either single-agent or combination, are usually lower than 15%. Therefore, various therapies have been evaluated.
The first agent, approved in late 2005, was sorafenib, after showing improvement in the second-line setting for progression-free survival (PFS) versus placebo. Shortly thereafter, sunitinib was approved following a large phase III trial that also demonstrated improvement in PFS versus interferon-α (INFα) in the first-line setting. The next agent approved was the mechanistic target of rapamycin (serine/threonine kinase) (mTOR) inhibitor, temsirolimus, which was evaluated as a first-line therapy against INFα in patients, most of whom had poor-risk disease. This trial demonstrated an improvement in overall survival (OS) in patients receiving temsirolimus. Combination of temsirolimus and INFα showed no advantages over the mTOR inhibitor alone. Meanwhile, everolimus was the second mTOR inhibitor approved after second-line therapy showed improvement in PFS versus placebo in a clinical trial. Pazopanib and axitinib are the two newer tyrosine kinase inhibitors and were recently approved for treatment of metastatic RCC. Patients taking pazopanib exhibited improved PFS versus those taking placebo both in the first-line setting and for cytokine-refractory disease. axitinib was studied against sorafenib as a second-line agent and demonstrated improved PFS, while patient preference studies with pazopanib suggested improved tolerability. Yet another class of drug, an anti-PD-1 checkpoint inhibitor named as nivolumab, has been approved for intravenous administration that unleashes the body's immune system so that it can reject the kidney cancer, however, the drug may cause the body to develop an immune reaction against its own tissues thereby leading to wide range of side effects that can be severe or life-threatening. With multiple approved agents available, further research is yet to define the ideal timing, sequencing, and patient profile for a given particular agent.
Although, studies have demonstrated the general tolerability of targeted agents, at most occasions, most patients with RCC inevitably develop resistance to targeted agents after a median of 5-11 months of treatment. Combinations of targeted agents are being evaluated, but toxicity is problematic. Several strategies have been tested to manage the drug resistance including: Adjusting the dose of the drug, combination therapy or switching to an alternative agent. Moreover alternative pathways are currently under investigation particularly targeting of RAF (Rapidly Accelerated Fibrosarcoma), MEK (Mitogen-activated protein/extracellular signal-regulated kinase), and the PI3K (Phosphatidylinositol 3-kinase)/AKT (a serine/threonine kinase also known as protein kinase B [PKB]) pathway.
Based on the information available, even though there have been some advancements in the treatment of renal cell carcinomas, the associated complications like the disease stage, the response rate and the accompanying side effects potentially reduce the patient compliance and poses issues which severely affect the progression-free survival (PFS) and/or the overall survival (OS) which is the ultimate treatment goal for a given therapy.
There remains a need for improved and additional methods of treating renal cell carcinoma. There remains a need for additional small-molecule therapeutics for the treatment of renal cancer.
SUMMARY
According to one aspect of the present invention, there is provided a method of treating renal cell carcinoma (RCC) comprising administration of 5-aminosalicylic acid derivatives like mesalamine.
According to another aspect of the present invention, there is provided a pharmaceutical composition comprising mesalamine with one or more pharmaceutically acceptable excipients for the treatment of renal cell carcinoma (RCC).
According to another aspect of the present invention, there is provided a method of treating renal cell carcinoma (RCC) by administration of mesalamine in combination with one or more additional cancer treatment regimens. The cancer treatment regimen can include administration of one or more additional therapeutic agents, exposure to ionizing radiation, and/or surgical interventions.
According to another aspect of the present invention, there is provided a use of mesalamine in combination with one or more therapeutic agents either simultaneously, sequentially, or separately for the treatment of renal cell carcinoma (RCC). In some instances, the therapeutic agent can include one or more chemotherapeutic drugs.
According to another aspect of the present invention, there are provided pharmaceutical compositions and kits including mesalamine and at least one other therapeutic agent.
The details of one or more embodiments are set forth in the descriptions below. Other features, objects, and advantages will be apparent from the description and from the claims.
BRIEF DESCRIPTION OF THE FIGURES
FIG. 1 depicts the relative IC₅₀ values (and the mean relative IC₅₀ value) for mesalamine across the human tumor models for renal cancer.
FIG. 2 depicts the absolute IC₅₀ values (and the mean absolute IC₅₀ value) for mesalamine across the human tumor models for renal cancer.
FIG. 3 depicts a concentration-effect curve exhibiting efficacy of mesalamine in human tumor models.
FIG. 4 includes a graphical representation of mean tumor volume across the animal group populations G1 (vehicle), G2 (sunitinib), and G3 (mesalamine).
FIG. 5 includes a graphical representation of mean tumor growth inhibition (in percentage value) across the animal group populations G1 (vehicle), G2 (sunitinib), and G3 (mesalamine).
FIG. 6 includes a graphical representation depicting change in body weights across the animal group population G1 (vehicle), G2 (sunitinib), and G3 (mesalamine).
DETAILED DESCRIPTION
Before the present methods and systems are disclosed and described, it is to be understood that the methods and systems are not limited to specific synthetic methods, specific components, or to particular compositions. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.
As used in the specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise. Ranges may be expressed herein as from “about” one particular value, and/or to “about” another particular value. When such a range is expressed, another embodiment includes
from the one particular value and/or to the other particular value. Similarly, when values are expressed as approximations, by use of the antecedent “about,” it will be understood that the particular value forms another embodiment. It will be further understood that the endpoints of each of the ranges are significant both in relation to the other endpoint, and independently of the other endpoint.
“Optional” or “optionally” means that the subsequently described event or circumstance may or may not occur, and that the description includes instances where said event or circumstance occurs and instances where it does not.
Throughout the description and claims of this specification, the word “comprise” and variations of the word, such as “comprising” and “comprises,” means “including but not limited to,” and is not intended to exclude, for example, other additives, components, integers or steps. “Exemplary” means “an example of” and is not intended to convey an indication of a preferred or ideal embodiment. “Such as” is not used in a restrictive sense, but for explanatory purposes.
Disclosed are components that can be used to perform the disclosed methods and systems. These and other components are disclosed herein, and it is understood that when combinations, subsets, interactions, groups, etc. of these components are disclosed that while specific reference of each various individual and collective combinations and permutation of these may not be explicitly disclosed, each is specifically contemplated and described herein, for all methods and systems. This applies to all aspects of this application including, but not limited to, steps in disclosed methods. Thus, if there are a variety of additional steps that can be performed it is understood that each of these additional steps can be performed with any specific embodiment or combination of embodiments of the disclosed methods.
Mesalamine is an officially adopted name for the compound 5-amino-2-hydroxybenzoic acid, or 5-aminosalicylic acid (5-ASA), and is in a class of medications called anti-inflammatory agents. Mesalamine has been approved for the treatment and management of inflammatory bowel disease, including ulcerative colitis and Crohn's disease. Mesalamine has the following chemical structure:
As used herein, term “mesalamine” (along with its synonyms mesalazine, 5-aminosalicylic acid and 5-ASA) is denoted in broad sense to include not only mesalamine per se but also its pharmaceutically acceptable derivatives. Suitable pharmaceutically acceptable derivatives include pharmaceutically acceptable salts, pharmaceutically acceptable solvates, pharmaceutically acceptable hydrates, pharmaceutically acceptable anhydrates, pharmaceutically acceptable enantiomers, pharmaceutically acceptable esters, pharmaceutically acceptable polymorphs, pharmaceutically acceptable prodrugs, pharmaceutically acceptable tautomers, pharmaceutically acceptable complexes etc.
Mesalamine may be formulated as a pharmaceutically acceptable salt. Pharmaceutically acceptable salts are salts that retain the desired biological activity of the parent compound and do not impart undesirable toxicological effects. Examples of such salts are acid addition salts formed with inorganic acids, for example, hydrochloric, hydrobromic, sulfuric, phosphoric, and nitric acids and the like; salts formed with organic acids such as acetic, oxalic, tartaric, succinic, maleic, fumaric, gluconic, citric, malic, methanesulfonic, ptoluenesulfonic, napthalenesulfonic, and polygalacturonic acids, and the like; salts formed from elemental anions such as chloride, bromide, and iodide; salts formed from metal hydroxides, for example, sodium hydroxide, potassium hydroxide, calcium hydroxide, lithium hydroxide, and magnesium hydroxide; salts formed from metal carbonates, for example, sodium carbonate, potassium carbonate, calcium carbonate, and magnesium carbonate; salts formed from metal bicarbonates, for example, sodium bicarbonate and potassium bicarbonate; salts formed from metal sulfates, for example, sodium sulfate and potassium sulfate; and salts formed from metal nitrates, for example, sodium nitrate and potassium nitrate. Pharmaceutically acceptable and non-pharmaceutically acceptable salts may be prepared using procedures well known in the art, for example, by reacting a sufficiently basic compound such as an amine with a suitable acid comprising a physiologically acceptable anion. Alkali metal (for example, sodium, potassium, or lithium) or alkaline earth metal (for example, calcium) salts of carboxylic acids can also be made.
Mesalamine may be formulated as pharmaceutically acceptable prodrugs. Prodrugs can substantially increase the bioavailability of the compounds, permitting more effective oral therapy. In some embodiments, the prodrug is a C₁-C₁₀ alkyl ester of the 1-carboxylic acid, which may or may not be substituted. A preferred substituent is carbonyl-oxy and alkyloxy-carbonyloxy. Exemplary esters include methyl, ethyl, 2-morpholinylethyl, pivaloyloxy-methyl ester, 1-(isopropyloxy-carbonyloxy)ethyl ester, and 1-(acetyloxy)ethyl ester. In some embodiments, the 5-amino group may be converted to a prodrug, for instance a phosphonate, phosphamide, aminomethylenes (—CH₂NR₂), methylene ethers (—CH₂OR) (in each case R is an alkyl group, e.g., a C₁-C₁₀ alkyl, which may or may not be substituted), and the like. In other embodiments, the prodrug is sulfasalazine.
According to the present invention there is provided a pharmaceutical composition comprising mesalamine with one or more pharmaceutically acceptable excipients for the treatment of renal cell carcinoma (RCC).
Mesalamine can be administered according to various dosing regimens. For instance, mesalamine can be administered once a day, twice a day, three times per day, or even more than three times a day. Mesalamine can be administered such that the total daily dose is at least 50 mg, at least 100 mg, at least 250 mg, at least 500 mg, at least 750 mg, at least 1,000 mg, at least 1,250 mg, at least 1,500 mg, at least 1,750 mg, or at least 2,000 mg. In some instances, the total daily dose can be from 5-5,000 mg, 10-5,000 mg, 25-5,000 mg, 50-5,000 mg, 100-5,000 mg, 200-2,500 mg, 500-2,500 mg, 10-2,500 mg, 50-2,500 mg, 100-2,500 mg, 100-2,000 mg, 250-2,000 mg or 500-2,000 mg. In other embodiments, mesalamine can be administered less than once daily, instance, once every two days, once every three days, once every five days, once every seven days, once every ten days, once every fourteen days, once every twenty-eight days or once every month. In some instances, mesalamine can be administered intermittently, for instance for a period of 1-10 days, followed by a period in which no mesalamine is administered (e.g., 1-10 days), followed by another period e.g., 1-10 days, in which mesalamine is administered. The on/off dosing schedule can be repeated as many times as necessary.
Preferably, mesalamine may be provided in the form of a pharmaceutical composition such as, but not limited to, solid unit dosage forms including tablets, capsules (filled with powders, pellets, beads, mini-tablets, pills, micro-pellets, small tablet units, multiple unit pellet systems (MUPS), disintegrating tablets, dispersible tablets, granules, and microspheres, multiparticulates), sachets (filled with powders, pellets, beads, mini-tablets, pills, micro-pellets, small tablet units, MUPS, disintegrating tablets, dispersible tablets, granules, and microspheres, multiparticulates), powders for reconstitution and sprinkles, however, other dosage forms such as controlled release formulations, lyophilized formulations, modified release formulations, delayed release formulations, extended release formulations, pulsatile release formulations, dual release formulations and the like may fall within the scope of the invention. Apart from this, it will be well acknowledged by person skilled in the art to have other forms of pharmaceutical compositions like liquid or semisolid dosage form (liquids, suspensions, solutions, dispersions, ointments, creams, emulsions, microemulsions, sprays, spot-on), injection/parenteral preparations, topical, inhalations, buccal, nasal etc. and which may be envisaged under the ambit of the invention.
Depending on the pathological stage, patient's age and other physiological parameters, size of the tumor, and the extent of invasion, the pharmaceutical composition comprising mesalamine may require specific dosage amounts and specific frequency of administrations. Preferably, on an average, the dose range that may be feasible for producing suitable anticancer effect may range from 25 mg to 3 gms depending on the above factors, and the route of administration adopted for administering the pharmaceutical composition. The dosing frequency that may be required for adherence to the therapy may be at least once, twice or thrice a day depending on the above mentioned factors and the route of administration adopted for administering the pharmaceutical composition.
It will further be well acknowledged by person skilled in the art that by specific treatment with mesalamine, various physicochemical properties could be improved such as solubility, better absorption, bioavailability, increased shelf life, etc. and wherein such specific treatment refers to one or more of micronization and nano sizing techniques which may achieve one or more of the benefits aimed hereinabove, and may also assist in dose reduction. For instance, mesalamine may be present in the form of nanoparticles which have an average particle size of less than 2,000 nm, less than 1,500 nm, less than 1,000 nm, less than 750 nm, less than 500 nm, or less than 250 nm.
Suitable pharmaceutically acceptable excipients may be used for formulating the dosage forms according to the present invention such as, but not limited to, surface stabilizers or surfactants, viscosity modifying agents, polymers including extended release polymers, stabilizers, disintegrants or super disintegrants, diluents, plasticizers, binders, glidants, lubricants, sweeteners, flavoring agents, anti-caking agents, opacifiers, anti-microbial agents, antifoaming agents, emulsifiers, buffering agents, coloring agents, carriers, fillers, anti-adherents, solvents, taste-masking agents, preservatives, antioxidants, texture enhancers, surface stabilizers, channeling agents, coating agents or combinations thereof.
The present inventors have discovered the mesalamine is surprisingly effective for the treatment of renal cell carcinoma. In certain embodiments, mesalamine can be used to treat conventional (clear-cell) renal cell carcinoma, papillary renal cell-carcinoma, chromophobe renal carcinoma, onco-cytoma, or collecting-duct carcinoma. Renal cell carcinoma can be classified in stages, according to the extent of disease progression. The TNM (tumor size/lymph node/metastasis) system includes the following stages of RCC:
Stage I: Tumor of a diameter of 7 cm (approx. 2¾ inches) or smaller, and limited to the kidney, with no lymph node involvement or metastases to distant organs.
Stage II: Tumor larger than 7.0 cm but still limited to the kidney, with no lymph node involvement or metastases to distant organs.
Stage III: Tumor of any size with involvement of a nearby lymph node but no metastases to distant organs. Tumor of this stage may be with or without spread to fatty tissue around the kidney, with or without spread into the large veins leading from the kidney to the heart; or Tumor with spread to fatty tissue around the kidney and/or spread into the large veins leading from the kidney to the heart, but without spread to any lymph nodes or other organs; or Tumor with spread to fatty tissue around the kidney and/or spread into the large veins leading from the kidney to the heart, but without spread to any lymph nodes or other organs.
Stage IV: Tumor that has spread directly through the fatty tissue and the fascia ligament-like tissue that surrounds the kidney; or involvement of more than one lymph node (near or distant from kidney); or distant metastases, such as in the lungs, bone, or brain.
Mesalamine can be used to treat Stage I RCC, Stage II RCC, Stage III RCC, or Stage IV RCC. In some embodiments, mesalamine can reduce tumor size, inhibit tumor growth, alleviate symptoms, delay progression, prolong survival, including, but not limited to disease free survival, prevent or delay RCC metastasis, reduce or eliminate preexisting RCC metastasis, and/or prevent recurrence of RCC. All of these effects fall within the general scope of treating RCC.
As used herein, the term “delay” refers to methods that reduce the probability of disease development/extent in a given time frame, when compared to otherwise similar methods that do not include the use of mesalamine. Probabilities can be established using clinical trials, but can also be determined using in vitro assays when correlations have been established. In some embodiments, mesalamine can inhibit renal cancer cell proliferation. For instance, at least about 10%, 20%, 30%, 40%, 60%, 70%, 80%, 90%, or 100% of cell proliferation is inhibited. In some embodiments, mesalamine can inhibit renal cancer metastasis. For instance, at least about 10%, 20%, 30%, 40%, 60%, 70%, 80%, 90%, or 100% of metastasis is inhibited.
According to the present invention, there is provided a method of alleviating or treating renal cell carcinoma (RCC) by administration of mesalamine in combination with one or more anti-cancer drugs either simultaneously, sequentially, or separately. In certain embodiments, mesalamine can be administered with:
(A) cytotoxic anti-neoplastic drugs such as nucleoside analogues, anti folates, antimetabolites, topoisomerase I inhibitor, anthracyclines, podophyllotoxins, taxanes, vinca alkaloids, alkylating agents, platinum compounds, proteasome inhibitors, nitrogen mustards & oestrogen analogue; and/or
(B) targeted anti-neoplastic drugs such as monoclonal antibodies, tyrosine kinase inhibitors, mTOR inhibitors, retinoids, immunomodulatory agents, histone deacetylase inhibitors, other kinase inhibitors.
In some embodiments, mesalamine may be administered (simultaneously, sequentially or separately) with one or more anti-cancer drugs. Such drugs include small molecule chemical agents and biological agents, including immunotherapies. Examplary anti-cancer drugs include Abiraterone acetate, Methotrexate, Paclitaxel Albumin-stabilized Nanoparticle, Brentuximab Vedotin, Ado-Trastuzumab Emtansine, Doxorubicin Hydrochloride, Afatinib Dimaleate, Everolimus, Netupitant, Palonosetron Hydrochloride, Imiquimod, Aldesleukin, Alectinib, Alemtuzumab, Melphalan Hydrochloride, Melphalan, Pemetrexed Disodium, Chlorambucil, Aminolevulinic acid, Anastrozole, Aprepitant, Pamidronate Disodium, Exemestane, Nelarabine, Arsenic Trioxide, Ofatumumab, Asparaginase Erwinia chrysanthemi, Atezolizumab, Bevacizumab, Axitinib, Azacitidine, Carmustine, Belinostat, Bendamustine hydrochloride, Bevacizumab, Bexarotene, Tositumomab, Bicalutamide, Bleomycin, Blinatumomab, Blinatumomab, Bortezomib, Bosutinib, Busulfan, Cabazitaxel, Cabozantinib, Alemtuzumab, Irinotecan hydrochloride, Capecitabine, Fluorouracil, Carboplatin, Carfilzomib, Bicalutamide, Lomustine, Ceritinib, Daunorubicin Hydrochloride, Cetuximab, Chlorambucil, Cyclophosphamide, Clofarabine, Cobimetinib, Dactinomycin, Cobimetinib, Crizotinib, Ifosfamide, Ramucirumab, Cytarabine, Dabrafenib, Dacarbazine, Decitabine, Daratumumab, Dasatinib, Daunorubicin hydrochloride, Decitabine, Efibrotide Sodium, Defibrotide sodium, Degarelix, Denileukin Diftitox, Denosumab, Dexamethasone, Dexrazoxane hydrochloride, Dinutuximab, Docetaxel, Doxorubicin Hydrochloride, Dacarbazine, Rasburicase, Epirubicin hydrochloride, Elotuzumab, Oxaliplatin, Eltrombopag ola mine, Aprepitant, Elotuzumab, Enzalutamide, Epirubicin Hydrochloride, Cetuximab, Eribulin Mesylate, Vismodegib, Erlotinib hydrochloride, Etoposide, Raloxifene hydrochloride, Melphalan hydrochloride, Toremifene, Panobinostat, Fulvestrant, Letrozole, Filgrastim, Fludarabine phosphate, Flutamide, Methotrexate, Pralatrexate, Recombinant HPV Quadrivalent Vaccine, Recombinant HPV Nonavalent vaccine, Obinutuzumab, Gefitinib, Gemcitabine hydrochloride, Gemtuzumab Ozogamicin, Afatinib Dimaleate, Imatinib Mesylate, Glucarpidase, Goserelin acetate, Eribulin mesylate, Trastuzumab, Topotecan hydrochloride, Palbociclib, Ibritumomab tiuxetan, Ibrutinib, Ponatinib hydrochloride, Idarubicin hydrochloride, Idelalisib, Imiquimod, Axitinib, Recombinant Interferon Alfa-2b, Tositumomab, Ipilimumab, Gefitinib, Romidepsin, Ixabepilone, Ixazomib Citrate, Ruxolitinib phosphate, Cabazitaxel, Ado-Trastuzumab Emtansine, Palifermin, Pembrolizumab, Lanreotide Acetate, Lapatinib ditosylate, Lenalidomide Lenvatinib mesylate, Leuprolide acetate, Olaparib, Vincristine Sulfate, Procarbazine hydrochloride, Mechlorethamine hydrochloride, Megestrol Acetate, Trametinib, Mercaptopurine, Temozolomide, Mitoxantrone hydrochloride, Plerixafor, Busulfan, Azacitidine, Gemtuzumab Ozogamicin, Vinorelbine tartrate, Necitumumab, Nelarabine, Sorafenib tosylate, Nilotinib, Ixazomib citrate, Nivolumab, Romiplostim, Obinutuzumab, Ofatumumab, Olaparib, Omacetaxine mepesuccinate, Pegaspargase, Ondansetron hydrochloride, Osimertinib, Panitumumab, Panobinostat, Peginterferon Alfa-2b, Pembrolizumab, Pertuzumab, Plerixafor, Pomalidomide, Ponatinib hydrochloride, Necitumumab, Pralatrexate, Procarbazine hydrochloride, Aldesleukin, Denosumab, Ramucirumab, Rasburicase, Regorafenib, Lenalidomide, Rituximab, Rolapitant hydrochloride, Romidepsin, Ruxolitinib phosphate, Siltuximab, Dasatinib, Sunitinib malate, Thalidomide, Dabrafenib, Osimertinib, Talimogene, Atezolizumab, Temsirolimus, Thalidomide, Dexrazoxane hydrochloride, Trabectedin, Trametinib, Trastuzumab, Lapatinib ditosylate, Dinutuximab, Vandetanib, Rolapitant hydrochloride, Bortezomib, Venetoclax, Crizotinib, Enzalutamide, Ipilimumab, Trabectedin, Ziv-Aflibercept, Idelalisib, Ceritinib.
Mesalamine can be administered with one or more chemotherapeutic agents either simultaneously, sequentially, or separately. In certain cases, mesalamine can be administered for a period of at least 1 week, at least 2 weeks, at least 4 week, at least 6 weeks, at least 8 week, or at least 10 weeks, prior to commencing treatment with additional agents. In some instances, mesalamine and the other agent can be administered intermittently, for instance a period of mesalamine administration, followed by a period in which the other agent to administered, followed by another period of mesalamine administration. The cycle can be repeated as many times as necessary.
In certain cases, the combination of mesalamine and additional agent will exhibit a greater than additive effect (i.e., a synergistic effect). In other instance, the use of mesalamine permits a reduced amount of the other agent to be administered, without a corresponding decrease in therapeutic efficiency.
In cases of combination therapy, it is possible that a unitary dosage form comprising both mesalamine and one or more additional anti-cancer drugs may be employed. In some instances, the combinations may be provided in form of kit preparation wherein mesalamine is present in an oral or parenteral composition and the additional anti-cancer drug therapy may be provided in an oral or parenteral composition. In one embodiment, the kit preparation may be provided in an all oral dosage form presentation wherein both the mesalamine and the additional anti-cancer drug are presented in an oral dosage form. In another embodiment, the kit preparation may be provided as an oral plus parenteral dosage form presentation wherein mesalamine is presented in an oral form and the additional anti-cancer drug is presented in a parenteral form. Alternatively, the kit preparation may be provided wherein mesalamine is presented in a parenteral form and the additional anti-cancer drug is presented in an oral dosage form.
In some instances, mesalamine can be used in combination with ionizing radiation and/or surgical interventions for the treatment of RCC. Mesalamine can be administered before, during, or after treatment with ionizing radiation or surgical intervention. In certain cases, mesalamine can be administered for a period of at least 1 week, at least 2 weeks, at least 4 week, at least 6 weeks, at least 8 week, or at least 10 weeks, prior to commencing treatment with ionizing radiation or surgery. Exemplary forms of radiation include x-rays, gamma rays, electron beams and proton beams. It has been found that administration of mesalamine permits a reduction in the total exposure of the patient to ionizing radiation, without a corresponding reduction in therapeutic efficiency. In certain instances, mesalamine can be administered both prior and subsequent to ionizing radiation and/or surgical interventions. For instance, mesalamine can be administered for a period of at least 1 week, at least 2 weeks, at least 4 week, at least 6 weeks, at least 8 week, or at least 10 weeks, following treatment with ionizing radiation or surgery.
EXAMPLES
The following examples are set forth below to illustrate the methods and results according to the disclosed subject matter. These examples are not intended to be inclusive of all aspects of the subject matter disclosed herein, but rather to illustrate representative methods, compositions, and results. These examples are not intended to exclude equivalents and variations of the present invention, which are apparent to one skilled in the art.
Efforts have been made to ensure accuracy with respect to numbers (e.g., amounts, temperature, etc.) but some errors and deviations should be accounted for. Unless indicated otherwise, parts are parts by weight, temperature is in ° C. or is at ambient temperature, and pressure is at or near atmospheric. There are numerous variations and combinations of reaction conditions, e.g., component concentrations, temperatures, pressures, and other reaction ranges and conditions that can be used to optimize the product purity and yield obtained from the described process. Only reasonable and routine experimentation will be required to optimize such process conditions.
Example 1
In the present study, mesalamine was characterized for their ability to inhibit anchorage independent growth and ex vivo colony formation of tumor cells in semi-solid medium. Mesalamine was tested against 10 human tumor xenograft-derived cell suspensions or tumor cell lines of renal cancer. Test concentrations ranged from 0.0698 mM to 3 mM.
Mesalamine inhibited colony formation in a concentration-dependent manner with a mean relative IC₅₀ value of 1,207 μM (1,263 αM). Bottom plateaus of the concentration-effect curves of responding tumor models were in the range from 0 to 18%, indicating clear inhibition of tumor colony growth in the selected test range.
Clonogenic Assay
Cultivation of Cell Lines
Cell lines were routinely passaged one or twice weekly. All cells were grown at 37° C. in a humidified atmosphere with 5% CO₂ in RPMI 1640 medium (Biochrom) supplemented with 10% (v/v) fetal calf serum and 0.1 mg/mL gentamicin. The percentage of viable cells was determined in a Neubauer-hemocytometer using trypan blue exclusion.
Preparation of Single Cell Suspensions from Human Tumor Xenografts
Tumor xenografts (patient-derived, as well as cell line-derived xenografts) were passaged as subcutaneous xenografts in NMRI nu/nu mice. At a tumor volume of 400-1000 mm³ tumor-bearing mice were sacrificed and tumors were collected under sterile conditions without delay according to the relevant Oncotest SOPs and the relevant animal welfare guidelines published by the FELASA and the GV-SOLAS. Tumors were mechanically disaggregated and subsequently incubated with an enzyme cocktail consisting of collagenase type IV (41 U/mL), DNase I (125 U/mL), hyaluronidase type III (100 U/mL), and disp ase II (1.0 U/mL) in RPMI 1640 medium (Life Technologies) at 37° C. for 60-120 minutes. Cells were passed through sieves of 100 μm and 40 μm mesh size (Cell Strainer, BD Falcon™), and washed with RPMI 1640 medium. The percentage of viable cells was determined in a Neubauer-hemocytometer using trypan blue exclusion. Aliquots of the cells were frozen down, and stored in liquid nitrogen. On each day of an experiment, a frozen aliquot of tumor cells was thawed and used for preparation of assay plates.
Clonogenic Assay Procedure
The clonogenic assay was carried out in a 96 well plate format using ultra low attachment plates. For each test, cells were prepared as described above and assay plates were prepared as follows: each test well contained a layer of semi-solid medium with tumor cells (50 μL) and a second layer of medium supernatant with or without test compound (100 μL). The cell layer consisted of 2.5·10³ to 1·10⁴ tumor cells per well, which were seeded in 50 μL/well cell culture medium (IMDM, supplemented with 20% (v/v) fetal calf serum, 0.01% (w/v) gentamicin, and 0.4% (w/v) agar). After 24 hours, the test compounds were added after serial dilution in cell culture medium, and left on the cells for the duration of the experiment (continuous exposure, 100 μl drug overlay). Every plate included six untreated control wells and drug-treated groups in duplicate at 9 concentrations. Cultures were incubated at 37° C. and 7.5% CO₂ in a humidified atmosphere for 8 to 13 days and monitored closely for colony growth using an inverted microscope. Within this period, ex vivo tumor growth led to the formation of colonies with a diameter of >50 μm. At the time of maximum colony formation, counts were performed with an automatic image analysis system (Cell Insight NXT, Thermo Scientific). 48 hours prior to evaluation, vital colonies were stained with a sterile aqueous solution of 2-(4-iodophenyl)-3-(4-nitrophenyl)-5-phenyltetrazolium chloride (1 mg/ml, 100 μl/well).
The ability of mesalamine to inhibit ex vivo colony formation of cells with the ability to grow anchorage-independently in semi-solid medium was examined in 10 tumor models of renal cancer.
Mesalamine inhibited colony formation in a concentration-dependent manner with a mean relative IC₅₀ value of 1,207 μM (1,263 μM).
In-Vivo Animal Efficacy Study
Objective
The objective of this study was to evaluate the in vivo anti-tumor efficacy of mesalamine alone and in combination with standard-of-care, sunitinib in xenograft model using Human renal cell carcinoma cell line (A498)
Methodology
Healthy 10 female athymic nude mice were recruited for the donor cell inoculation. Animals were subcutaneously injected at flank region with 10 million A498 cells suspended in 200 μl of media and matrigel. Animals were monitored for solid tumor growth. Once the tumor reaches ˜500 mm³, donor animals were humanely sacrificed and tumors were collected under aseptic condition. Tumors were fragmented in to ˜30 mg size.
After one week of acclimatization, female athymic nude mice were subcutaneously implanted with ˜30 mg tumor fragments using the device trocar. Animals were observed for tumor growth for next three weeks. Tumor bearing animals were selected from the experimental animals and grouped on basis of tumor size, into six groups containing 7 animals in each group.
Group G1 animals served as a vehicle control, which received 10 mL/kg, p.o. of 0.5% CMC in water; whereas Group 2 served as the standard, which received 20 mg/kg (Sub-therapeutic dose) of Sunitinib. Group 3 received mesalamine at 250 mg/kg.
Group Treatment Dose, Route & Regimen No. of Animals G1 Vehicle, 0.5% CMC 10 mL/kg, p.o. q.d.x21 7 G2 Sunitinib 20 mg/kg, p.o. q.d.x21 7 (Sub-therapeutic dose) G3 Mesalamine 250 mg/kg, p.o. q.d.x21 7
Tumor Measurement
The tumor sizes were measured weekly twice from the date of tumor appearance till the end of the experiment. Tumor size was measured by digital vernier caliper (MITUTOYO) by measuring length (L=longest axis) and width (W=shortest axis).
Tumor volume was calculated according to the formula L×W²/2 (Unit: mm³), where, L=length of tumor (mm) and W=width of tumor (mm). From the tumor volume data mean tumor volume and % tumor growth inhibition (% TGI) were determined. Mesalamine by itself shows anti-tumor efficacy, inhibiting tumor formation by more than 50% at the dose tested, and the anti-tumor efficacy of mesalamine is comparable to sunitinib. None of the treatment shows any significant change in body weights.
Mean Tumor Volume
G1, G2, Sunitinib G3, Mesalamine Vehicle control (20 mg/kg) (250 mg/kg) Days Mean SEM Mean SEM Mean SEM 1 147.56 20.68 145.40 29.19 145.26 29.30 6 331.93 79.52 174.90 37.07 161.68 26.47 9 463.77 110.07 261.95 66.94 250.41 63.08 13 617.07 146.04 340.62 93.64 301.82 103.16 16 961.26 226.49 448.05 121.72 501.10 160.99 20 1280.51 295.87 630.25 215.72 536.78 195.78
Mean Tumor Growth Inhibition
G1, Vehicle G2, Sunitinib G3, Mesalamine Days control (20 mg/kg) (250 mg/kg) 1 0 1.47 1.56 6 0 47.31 51.29 9 0 43.52 46.01 13 0 44.80 51.09 16 0 53.39 47.87 20 0 50.78 58.08
Example 2: Pharmaceutical Compositions
Manufacturing formula for a pharmaceutical composition envisaged under the present invention can be referred herein below:
Ingredients Qty/tab (mg) Dry Mix Mesalamine 400-1200 Anhydrous Lactose 55-165 Binder solution Povidone/Hypromellose/Hydroxy Propyl 22.5-67.50 Cellulose Isopropyl Alcohol q.s Purified water q.s Blending Sodium starch glycolate/Crospovidone/ 7.5-22.50 Croscarmellose Sodium Colloidal anhydrous silica 5-15 Purified talc 5-15 Lubrication Magnesium stearate/Stearic acid 5-15 Total 500-1500 Seal Coating:
Ingredients Qty/tab (mg) Hypromellose 5-15 Polyethylene Glycol 0.5-1.5 Isopropyl alcohol q.s Dichloromethane q.s Enteric Coating:
Ingredients Qty/tab (mg) Methacrylic acid copolymer (Eudragit 30-90 S100/Eudragit L 100) Purified Talc 7.50-22.50 Tri ethyl citrate 7.00-21.00 Isopropyl alcohol q.s Acetone q.s Film Coating:
Ingredients Qty/tab (mg) Opadry color composition 10-30.00 Purified Water q.s. Total 560-1680 mg
Manufacturing Process:
(I) Dry Mixing:
i) Ingredients 1 & 2 were sifted through specified sieves
ii) Presifted ingredients were loaded in suitable granulator and were mixed to form a dry mix
(II) Binder Preparation & Granulation:
iii) Povidone/Hypromellose/Hydroxy propyl Cellulose were dissolved in Isopropyl Alcohol & water under stirring, and the solution was stirred until a clear solution was obtained.
iv) Dry mix of step ii) above was granulated using the binder solution until proper consistency of the wet mass was obtained in the granulator.
(III) Drying & Milling:
v) The wet milled mass obtained at step iv was loaded in a dryer and the granules so obtained were dried
vi) The dried granules so obtained were sifted through specified sieves.
(IV) Blending:
viii) The above obtained granules were blended in octagonal suitable blender at suitable RPM with sodium starch glycolate/Crospovidone/sodium carboxy Methyl Cellulose/Croscarmellose Sodium, Colloidal Silicon dioxide and Purified Talc.
(V) Lubrication & Compression:
ix) The presifted magnesium stearate/stearic acid were loaded in octagonal blender and the blend was lubricated for suitable time followed by compression of the granules to form tablets.
(VI) Coating:
x) The compressed tablets obtained above were seal coated using Hypromellose and PEG solution followed by enteric coating of the seal coated tablets using Eudragit S 100/Eudragit L 100 solution along with Tri ethyl citrate, talc keeping appropriate in-process parameters, and finally, film coated the above enteric coated tablets with Opadry color solution.
Manufacturing Formula II:
Ingredients Qty/tab (mg) Granulation I Dry Mix Mesalamine 400-1200 Microcrystalline Cellulose (Avi cel PH 101) 3-9 Sodium starch glycolate/Crospovidone/ 2-6 Croscarmellose Sodium Sodium carboxy Methyl Cellulose 5-15 Bees Wax 5-15 Binder solution Purified water q.s Granulation II III. Dry Mix Mesalamine Granules 410-1230 Microcrystalline Cellulose (Avi cel PH 101) 10-30 Hpromellose/Hydroxy Propyl Cellulose 20-60 Colloidal anhydrous silica 2-6 sodium starch glycolate/Crospovidone/ 2-6 Croscarmellose Sodium Binder solution Povidone/Hypromellose/Hydroxy Propyl 3-9 Cellulose/sodium carboxy Methyl Cellulose Purified Water q.s. Lubrication Magnesium stearate/Stearic acid 3-9 Total 455-1365 Seal Coating:
Ingredients Qty/tab (mg) Hypromellose 5-15 Polyethylene Glycol 0.5-1.5 Isopropyl alcohol q.s Dichloromethane q.s Enteric coating:
Ingredients Qty/tab (mg) Methacrylic acid copolymer (Eudragit 25.0-75.0 S100/Eudragit L 100) Purified Talc 5.0-15.0 Tri ethyl citrate 3.5-10.5 Isopropyl alcohol q.s Acetone q.s
Film Coating:
Ingredients Qty/tab (mg) Opadry color composition 6.0-18.0 Purified Water q.s. Total 560-1680 mg
Manufacturing Process:
(I) Granulation I:
1) Dry Mixing:
i) Ingredients 1 to 5 were sifted through specified sieves and loaded in a suitable granulator. A dry mix was formed by mixing the presifted ingredients for 5 mins.
2) Binder Preparation & Granulation:—
i) The dry mix obtained above was granulated using Purified water as binder solution till proper consistency of wet mass was obtained in suitable granulator.
3) Drying:
i) The wet mass obtained above was sized & the granules so obtained were dried.
(II) Granulation II:
4) Sifting:
i) The ingredients 7 to 10 were sifted through specified mesh & loaded into suitable granulator.
ii) The dried granules obtained in 3) were then loaded into the granulator along with the materials obtained above in 4 i).
5) Binder Preparation & Granulation:—
i) Povidone/Hypromellose/Hydroxy propyl Cellulose/Sodium Carboxy Methyl Cellulose were dissolved in water under stirring, and were continuously stirred until a clear solution was obtained.
ii) The dry mix of step 4) was granulated using the above binder solution until proper consistency of wet mass was obtained
6) Drying & Milling:
i) The wet mass was sized & the granules were dried. The dried granules were sifted through suitable sieves.
7) Lubrication & Compression:
i) The presifted Magnesium Stearate/Stearic Acid were loaded in a suitable Blender & the granules were lubricated for suitable time followed by compression of the granules to form tablets
8) Coating:
i) The compressed tablets obtained above were seal coated using Hypromellose and PEG solution followed by enteric coating of the seal coated tablets using Eudragit S 100/Eudragit L 100 solution along with Tri ethyl citrate, talc keeping appropriate in-process parameters, and finally, film coated the above enteric coated tablets with Opadry color solution.
The compositions and methods of the appended claims are not limited in scope by the specific compositions and methods described herein, which are intended as illustrations of a few aspects of the claims and any compositions and methods that are functionally equivalent are intended to fall within the scope of the claims. Various modifications of the compositions and methods in addition to those shown and described herein are intended to fall within the scope of the appended claims. Further, while only certain representative compositions and method steps disclosed herein are specifically described, other combinations of the compositions and method steps also are intended to fall within the scope of the appended claims, even if not specifically recited. Thus, a combination of steps, elements, components, or constituents may be explicitly mentioned herein or less, however, other combinations of steps, elements, components, and constituents are included, even though not explicitly stated. The term “comprising” and variations thereof as used herein is used synonymously with the term “including” and variations thereof and are open, non-limiting terms. Although the terms “comprising” and “including” have been used herein to describe various embodiments, the terms “consisting essentially of” and “consisting of” can be used in place of “comprising” and “including” to provide for more specific embodiments of the invention and are also disclosed. Other than in the examples, or where otherwise noted, all numbers expressing quantities of ingredients, reaction conditions, and so forth used in the specification and claims are to be understood at the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, to be construed in light of the number of significant digits and ordinary rounding approaches.
What is claimed is:
1. A method for the treatment of renal cell carcinoma in a patient, the method comprising administering to said patient mesalamine, or a pharmaceutically acceptable salt or prodrug thereof, in an amount effective to treat renal cell carcinoma, and at least one additional anti-cancer agent.
2. The method according to claim 1, wherein the additional anti-cancer agent comprises a nucleoside analog, anti folate, antimetabolite, topoisomerase I inhibitor, anthracycline, podophyllotoxin, taxane, vinca alkaloid, alkylating agent, platinum compound, proteasome inhibitor, nitrogen mustard, oestrogen analogue, monoclonal antibody, tyrosine kinase inhibitor, mTOR inhibitor, retinoid, immunomodulatory agent, histone deacetylase inhibitor, or a combination thereof.
3. The method according to claim 1, wherein the additional anti-cancer agent comprises nelarabine, azacitidine, capecitabine, fluorouracil, cytarabine, decitabine, gemcitabine, or a combination thereof.
4. The method according to claim 1, wherein the additional anti-cancer agent comprises afatinib, alectinib, axitinib, bosutinib, cabozantinib, dasatinib, erlotinib, lapatinib, lenvatinib, sorafenib, nilotinib, osimertinib, ponatinib, crizotinib, gefitinib, cobimetinib, sunitinib, trametinib, vandetanib, ceritinib, idelalisib, ruxolitinib, everolimus, temsirolimus, or a combination thereof.
5. The method according to claim 1, wherein the additional anti-cancer agent comprises bortezomib, ixazomib, brentuximab, alemtuzumab, ofatumumab, bevacizumab, tositumomab, blinatumomab, cetuximab, ramucirumab, daratumumab, denosumab, dinutuximab, elotuzumab, obinutuzumab, gemtuzumab, trastuzumab, ibritumomab, ipilimumab, necitumumab, nivolumab, panitumumab, pembrolizumab, pertuzumab, rituximab, atezolizumab or a combination thereof.
6. The method according to claim 4, wherein the additional anti-cancer agent comprises sunitinib maleate.
7. The method according to claim 1, wherein the at least one additional agent is administered simultaneously with mesalamine.
8. The method according to claim 1, wherein the at least one additional agent is administered sequentially with mesalamine.
9. The method according to claim 1, wherein the at least one additional agent is administered separately from mesalamine.
10. A pharmaceutical composition comprising mesalamine, or a pharmaceutically acceptable salt or prodrug thereof, and at least one additional renal cell carcinoma therapeutic agent, wherein the additional anti-cancer agent comprises a nucleoside analog, anti folate, antimetabolites, topoisomerase I inhibitor, anthracyclines, podophyllotoxin, taxane, vinca alkaloid, alkylating agent, platinum compound, proteasome inhibitor, nitrogen mustard, oestrogen analogue, monoclonal antibody, tyrosine kinase inhibitor, mTOR inhibitor, retinoid, immunomodulatory agent, histone deacetylase inhibitor, other kinase inhibitor or combinations thereof.
11. The composition according to claim 10, wherein the additional anti-cancer agent comprises nelarabine, azacitidine, capecitabine, fluorouracil, cytarabine, decitabine, gemcitabine, or a combination thereof.
12. The composition according to claim 10, wherein the additional anti-cancer agent comprises afatinib, alectinib, axitinib, bosutinib, cabozantinib, dasatinib, erlotinib, lapatinib, lenvatinib, sorafenib, nilotinib, osimertinib, ponatinib, crizotinib, gefitinib, cobimetinib, sunitinib, trametinib, vandetanib, ceritinib, idelalisib, ruxolitinib, everolimus, temsirolimus, or a combination thereof.
13. The composition according to claim 10, wherein the additional anti-cancer agent comprises bortezomib, ixazomib, brentuximab, alemtuzumab, ofatumumab, bevacizumab, tositumomab, blinatumomab, cetuximab, ramucirumab, daratumumab, denosumab, dinutuximab, elotuzumab, obinutuzumab, gemtuzumab, trastuzumab, ibritumomab, ipilimumab, necitumumab, nivolumab, panitumumab, pembrolizumab, pertuzumab, rituximab, atezolizumab or a combination thereof.
14. The composition according to claim 12, wherein the additional anti-cancer agent comprises sunitinib maleate.
15. A kit comprising mesalamine, or a pharmaceutically acceptable salt or prodrug thereof, and at least one additional renal cell carcinoma therapeutic agent, wherein the additional anti-cancer agent comprises a nucleoside analog, anti folate, antimetabolites, topoisomerase I inhibitor, anthracyclines, podophyllotoxin, taxane, vinca alkaloid, alkylating agent, platinum compound, proteasome inhibitor, nitrogen mustard, oestrogen analogue, monoclonal antibody, tyrosine kinase inhibitor, mTOR inhibitor, retinoid, immunomodulatory agent, histone deacetylase inhibitor, other kinase inhibitor or combinations thereof.
16. The kit according to claim 15, wherein the additional anti-cancer agent comprises nelarabine, azacitidine, capecitabine, fluorouracil, cytarabine, decitabine, gemcitabine, or a combination thereof.
17. The kit according to claim 15, wherein the additional anti-cancer agent comprises afatinib, alectinib, axitinib, bosutinib, cabozantinib, dasatinib, erlotinib, lapatinib, lenvatinib, sorafenib, nilotinib, osimertinib, ponatinib, crizotinib, gefitinib, cobimetinib, sunitinib, trametinib, vandetanib, ceritinib, idelalisib, ruxolitinib, everolimus, temsirolimus, or a combination thereof.
18. The kit according to claim 15, wherein the additional anti-cancer agent comprises bortezomib, ixazomib, brentuximab, alemtuzumab, ofatumumab, bevacizumab, tositumomab, blinatumomab, cetuximab, ramucirumab, daratumumab, denosumab, dinutuximab, elotuzumab, obinutuzumab, gemtuzumab, trastuzumab, ibritumomab, ipilimumab, necitumumab, nivolumab, panitumumab, pembrolizumab, pertuzumab, rituximab, atezolizumab or a combination thereof.
19. The kit according to claim 17, wherein the additional anti-cancer agent comprises sunitinib maleate.
20. The kit according to claim 15, wherein the mesalamine is provided in a pharmaceutical composition suitable for oral or parenteral administration.
|
Author:William Dennes Mahan
as McIntosh and Twyman
* Archko Volume
Works about Mahan
* "The Fraudulent Archko Volume" BYU Studies Quarterly: Vol. 15 : Iss. 1, Article 4. by Richard Lloyd Anderson
|
Talk:Aleksandar Đokić
External links modified
Hello fellow Wikipedians,
I have just modified one external link on Aleksandar Đokić. 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/20101104090733/http://www.srpskoblago.org/visual-arts/modern-serbian-architecture to http://www.srpskoblago.org/visual-arts/modern-serbian-architecture
Cheers.— InternetArchiveBot (Report bug) 12:03, 7 December 2017 (UTC)
|
Feature Request: Give options for truncating numeric amounts after 999, 9999, or 99999.
Issue description:
You open your grid and see objects totaling 600, 900, and 1.2k.
I like exact numbers. O_o
What you expected to happen:
An option in the config to make it so the number isn't truncated until 10k, or maybe even 100k. Four digits should easily fit and would be a huge boon. Five would be amazing, but might be a bit sqwoahsh'd. Obviously you don't have to implement this change, and I'll continue loving you and this mod forever and ever, but maybe I'll love it just a teensy bit more. ^_^
Version (make sure you are on the latest version before reporting):
Minecraft: 1.12.2
Refined Storage: 1.5.34
P.S.:
I would say treat the OCD
|
Talk:Ryougi Shiki (Saber)/@comment-4069714-20160225052338
* le sigh*
Just rolled 10 times and I got nothing...
Looks like I'm outta the game
|
# Custom Google Data Studio connector
[](https://circleci.com/gh/Bajena/spotify-gds-connector/tree/master)
[](https://codecov.io/gh/Bajena/spotify-gds-connector)
## Description
This repo contains code of a custom [Google Data Studio connector](https://developers.google.com/datastudio/connector/gallery/) for displaying stats about your recent plays in Spotify.
The connector uses [Spotify API](https://developer.spotify.com/documentation/web-api/reference/player/get-recently-played/) to fetch the tracks.
Unfortunately the API endpoint is currently limited to the recent 50 tracks.
## Preview
Here's how an example report looks like:
## More info
I described the whole development process in a few blog posts:
* Introduction - https://medium.com/@bajena3/building-a-custom-google-data-studio-connector-from-a-z-b4d711a5cf58
* Development environment setup and creating basic connector code - https://medium.com/@bajena3/building-a-custom-google-data-studio-connector-from-a-z-part-1-basic-setup-445a6d965d3f
* OAuth and calling Spotify API - https://medium.com/@bajena3/building-a-custom-google-data-studio-connector-from-a-z-part-2-oauth-calling-apis-caching-edb3e25b18e7
* Unit testing and linting the code - https://medium.com/@bajena3/building-a-custom-google-data-studio-connector-from-a-z-part-3-unit-tests-and-eslint-setup-16807675dc10
|
Thread:LordDrakostar/@comment-957747-20190321234259
* Check out Wiki Features to turn on some special features including our popular community Chat.
* Customize your community’s color and style by visiting the Theme Designer.
* Stop by Community Central to check out the staff blog, and ask questions on our community forum.
Have fun!
|
Thread:Hyper-the-developer/@comment-24825392-20160729191407/@comment-24825392-20160729193702
Thanks for adding the templates to the articles. They look great now :)
|
dynamic sampled query in oracle db trace
i've got a huge Oracle Trace file. The application, wich produced this file, runned 1 hour and 15 minutes.
In this Tracefile i found 4 Selects with together a little bit over a hour runtime.
The problem is these selects are sampled by the Optimizer.
SELECT /* OPT_DYN_SAMP */ /*+ ALL_ROWS IGNORE_WHERE_CLAUSE
NO_PARALLEL(SAMPLESUB) opt_param('parallel_execution_enabled', 'false')
NO_PARALLEL_INDEX(SAMPLESUB) NO_SQL_TUNE */ NVL(SUM(C1),:"SYS_B_00"),
NVL(SUM(C2),:"SYS_B_01")
FROM
(SELECT /*+ IGNORE_WHERE_CLAUSE NO_PARALLEL("LST_G") FULL("LST_G")
NO_PARALLEL_INDEX("LST_G") */ :"SYS_B_02" AS C1, CASE WHEN
"LST_G"."SENDUNG_TIX"=:"SYS_B_03" AND "LST_G"."LST_K"=:"SYS_B_04" AND
"LST_G"."LST_ART"=:"SYS_B_05" AND "LST_G"."FAK_TIX"=(-:"SYS_B_06") THEN
:"SYS_B_07" ELSE :"SYS_B_08" END AS C2 FROM "TMS1033"."LST_G" SAMPLE BLOCK
(:"SYS_B_09" , :"SYS_B_10") SEED (:"SYS_B_11") "LST_G") SAMPLESUB
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 56076 3.93 4.21 0 0 0 0
Execute 56076 1.98 1.80 0 0 0 0
Fetch 56076 1127.54 1122.77<PHONE_NUMBER>4 0 56076
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 168228 1133.45 1128.79<PHONE_NUMBER>4 0 56076
This is one of the four, they look nearly the same. I think i found the original Statements and these are executed from a Uniface-Service. I have no idea how Uniface works, i am only the db guy.
The problem is that i have no Idea why the Optimizer rebuild this statement. The original one don't use the dynamic_sample hint. Also i found these, i think so, original Statments additionally in the trace file .
select count(*)
from
lst_g where sendung_tix =<PHONE_NUMBER>0396 and lst_k = 'E' and lst_art = 'G'
and fak_tix = -4
Thats why i am not sure what these sampled Statements are. Any idea?
Thanks a lot.
Dynamic sampling is turned on for that query. Either
The query uses the /*+ DYNAMIC_SAMPLING */ hint
The code issues an alter session set optimizer_dynamic_sampling= command
optimizer_dynamic_sampling is set in the database spfile.
For example
alter session set OPTIMIZER_DYNAMIC_SAMPLING = 2;
Then issue a query against a big table with a very selective (but not exact) condition that can use an index.
select * from mtl_system_items /* biiig table */
where organization_id = 92
and segment1 LIKE 'DY_' /* very selective condition with index */
Run it and you get data back quickly. But then,
alter session set OPTIMIZER_DYNAMIC_SAMPLING = 10;
and re-run the same SELECT and it's out to lunch, sampling every block in the table.
Thanks for the explanation
I believe these are queries used by Statistics Gathering jobs for updating statistics on database objects. Please check if any stats gathering / update jobs were running at the time when the trace file got generated.
In your case, from the SQL posted it seems statistics was being gathered on "TMS1033"."LST_G". The same will be the case with the other 3 SQLs you found out.
Hope this helps.
Sorry, I hate to down vote, but this isn't right. These queries are not from DBMS_STATS. They're from the optimizer performing dynamic sampling. You can tell by (A) the OPT_DYN_SAMP comment in the query and (B) by the fact that the query has a WHERE clause on specific columns in the table. DBMS_STATS would sample from all the rows (no where clause, just a sample size).
|
Blends of fluoroplastics with polyetherketoneketone
ABSTRACT
Compositions of melt-flowable fluoroplastic and poly(ether ketone ketone) are provided, wherein the either the fluoroplastic or the poly(ether ketone ketone) is the matrix polymer and the other polymer is the dispersed phase, to provide improved properties to the matrix polymer.
This application claims the benefit of provisional application Ser. No. 60/053749, filed Jul. 25, 1997.
FIELD OF THE INVENTION
This invention relates to blends of fluoroplastics and polyetherketoneketone having improved properties.
BACKGROUND OF THE INVENTION
Fluoroplastics which are fabricable by melt flow at temperatures above their melting points have a wide range of utilities because of their chemical inertness and high melting temperature. These utilities could be broadened if such properties as room temperature toughness, high temperature physical properties such as heat distortion temperature and/or permeability could be improved. The use of additives in the fluoroplastic in an attempt to achieve such improvement suffers from one or more problems of incompatibility with the fluoroplastic, resulting in deterioration of desired properties, and difficulty in uniformly incorporating the additive into the fluoroplastic.
SUMMARY OF THE INVENTION
It has been found that incorporation of varying amounts of polyetherketoneketone, commonly known as PEKK, into melt-flowable fluoroplastics imparts surprising improvements in properties to the fluoroplastic. Another aspect of the present invention is the incorporation of the fluoroplastic into the PEKK to cause surprising improvement in properties of the PEKK. In this aspect, the fluoroplastic is dispersed in PEKK as the matrix instead of the PEKK being dispersed in the fluoroplastic as in the first-mentioned embodiment. Thus, the present invention is a composition comprising 5 to 95 wt % melt-flowable fluoroplastic and complement ally, to total 100 wt %, 95 to 5 wt % PEKK.
DETAILED DESCRIPTION OF THE INVENTION
In one embodiment of the present invention, the melt-flowability of the fluoroplastic enables it to be fabricated by melt extrusion, including injection molding. As such, the fluoroplastic can have a melt flow rate (MFR) in the range of 1 to 100 g/10 min determined in accordance with ASTM D-1238 at the temperature which is standard for the fluoroplastic. The fluoroplastic is non-elastomeric, i.e. the stress-strain curve for the fluoroplastic exhibits a yield point, and upon further stretching of the fluoroplastic, there is little recovery of strain (stretch), e.g. less than 20%, upon release of the stretching force. Examples of melt-fabricable fluoroplastics include the group of well known fluoropolymers comprising tetrafluoroethylene (TFE) copolymers, particularly the copolymers of TFE with one or more comonomers selected from perfluoroolefins having 3-8 carbon atoms, preferably hexafluoropropylene (HFP), and perfluoro(alkyl vinyl ether) (PAVE) with alkyl groups having 1-5 carbon atoms, preferably 1-3 carbon atoms, most preferably 2-3 carbon atoms. Such copolymers have sufficient concentration of comonomer to reduce the melting temperature of the copolymer significantly below that of TFE homopolymer. Preferred melt-fabricable fluoroplastics include TFE/HFP (typically referred to as FEP), TFE/PAVE (typically referred to as PFA), and TFE/HFP/PAVE. The aforesaid TFE copolymers can also contain minor amounts of units derived from other comonomers, including polar-functional monomers that introduce polar groups along the polymer chain, usually at the end of pendant side groups, when copolymerized into the polymer. Fluoroplastics other than the perfluorinated copolymers mentioned above can also be used, such as copolymers of TFE or chlorotrifluoroethylene (CTFE) with ethylene, and TFE/HFP/vinylidene fluoride copolymer (THV). The processing of the fluoroplastic at temperature above its melting point indicates that the fluoroplastic has crystallinity. The fluoroplastic used in the present invention may also be amorphous, however, in which case, the processing of the fluoroplastic is at a high temperature that the PEKK will be flowable as though molten during the processing.
In another embodiment of the present invention, a portion of the melt-fabricable fluoroplastic is replaced by polytetrafluoroethylene (PTFE) micropowder. PTFE micropowder is a tetrafluoroethylene homopolymer or modified homopolymer which has a considerably lower molecular weight than the normal high melt viscosity PTFE, which enables the micropowder by itself to be melt flowable, having a melt flow rate within the range described for the melt-fabricable fluoroplastics. The high molecular weight of the normal PTFE is characterized by a molecular weight (Mn) of at least 2,000,000 and a melt viscosity of at least 10⁸ Pa.s at 380° C., this melt viscosity being so high that the PTFE does not flow in the molten state, requiring special non-melt-fabrication techniques, including paste extrusion for the fine powder type of PTFE and compression molding for the granular type of PTFE. In contrast, the molecular weight (Mn) of PTFE micropowder will usually be within the range of 50,000 to 700,000, and the melt viscosity of the micropowder will be 50 to 1×10⁵ Pa•s as measured at 372° C. in accordance with the procedure of ASTM D-1239-52T, modified as disclosed in U.S. Pat. No. 4,380,618. Preferably the melt viscosity of the PTFE micropowder is 100 to 1×10⁴ Pa•s at 372° C. PTFE micropowder is described further in Kirk-Othmer, The Encyclopedia of Chemical Technology, 4^(th) Ed., pub. by John Wiley & Sons (1994) on pp 637-639 of Vol. 11, and in the article H. -J Hendriock, “PTFE Micro powders”, Kunstoffe German Plastics, 76, pp. 920-926 (1986). These publications describe the micropowder as being obtained by polymerization or by irradiation degradation of the high molecular weight (high melt viscosity) PTFE. Polymerization directly to the micropowder is disclosed for example in PCT WO 95/23829, wherein the micropowder is referred to as low melt viscosity PTFE. Although the PTFE micropowder is melt flowable, it is not melt fabricable by itself because the resultant product has no practical strength due to the low molecular weight of the PTFE micropowder. Thus, the beading obtained in the melt flow rate test from which the melt viscosity is determined is brittle such that it breaks upon the slightest flexure.
When a portion of the melt-fabricable fluoroplastic is replaced by PTFE micropwder, at least 10% by weight of the total fluoroplastic will be the melt-fabricable fluoroplastic, preferably at least 20 wt %, the remainder being the PTFE micropowder. Surprisingly, the PTFE micropowder imparts increased strength to articles molded from the fluoroplastic/PEKK blend, even though the PTFE micropowder has no strength by itself as described above.
The PEKK component is a copolymer of diphenyl ether and benzene dicarboxylic acid halides, preferably terephthalyl (T) or isophthaloyl (I) halides, usually chlorides, and mixtures thereof, such as disclosed in U.S. Pat. Nos. 3,062,205, 3,441,538, 3,442,857, 3,516,966, 4,704,448, and 4,816,556, preferably having an inherent viscosity of at least 0.4 measured on a 0.5 wt % solution in concentrated sulfuric acid at 30° C. The PEKK generally has a melting point of at least 300° C. Typically, the PEKK contains both T and I units in a ratio of 90:10 to 30:70, and more typically 80:20 to 60:40. As the proportion of T units decrease and I units increase, the crystallinity of the PEKK diminishes, until at 60:40, the PEKK crystallizes so slowly that it resembles an amorphous polymer, except that it will exhibit a melting point.
With respect to the combination of fluoroplastic and PEKK forming compositions of the present invention, in a general sense, the preferred composition has at least 25 wt % of the melt-flowable fluoroplastic. For specific results, the proportion of the fluoroplastic will vary. One of the improvements which a relatively small amount of PEKK imparts to the fluoroplastic is improved cut-through resistance which is especially valuable in the use of fluoroplastic for insulation coating or jacketing of insulated wire. In this embodiment, the PEKK content of the composition will be 5 to 25 wt %, preferably 10 to 20 wt %. While the PEKK is incompatible with the fluoroplastic as indicated by the PEKK being present as discrete particles (domains) dispersed in the fluoroplastic matrix forming the insulation or jacketing, the electrical properties and tensile elongation of the insulation and jacketing does not suffer.
Another improvement which a relatively small amount of PEKK imparts to the fluoroplastic is improved high temperature resistance to distortion under load. This is especially valuable for applications in which the fluoroplastic forms a structural member, such as baskets for carrying articles through exposure to chemical processing at high temperatures. Unfortunately, fluoroplastics tend to creep and distort at temperatures as low as 60 to 100° C. PEKK imparts much greater resistance to creep and distortion at elevated temperatures than would be expected from the amount of PEKK used. This greater resistance to creep and distortion can be measured as increased heat distortion temperature in accordance with ASTM D648 using 264 psi (1816 MPa) load. Dispersion of PEKK in fluoroplastic can provide blends which have heat distortion temperatures (HDT) greater than 100° C., and even greater than 140° C., enabling the fluoroplastic to have a higher service temperature, without detracting from the chemical inertness of the fluoroplastic. In this embodiment, the PEKK content of the composition can be 5 to 30 wt %, preferably 10 to 30 wt %, and more preferably 15 to 25 wt %.
In still another embodiment, at higher PEKK content for the composition, e.g. 40 to 50 wt %, wherein the PEKK is still the dispersed phase in the fluoroplastic composition, the resultant composition exhibits remarkable creep resistance, i.e. resistance to cold flow. Instead of de laminating as might be expected, the composition has physical integrity, so as to be useful in structural applications providing the improved performance of dimensional integrity. This embodiment is demonstrated is especially valuable in pipe lining.
In still another embodiment, wherein the PEKK is the matrix polymer component of the composition, the incorporation of dispersed fluoroplastic therein provides for improved impermeability to organic fluid and improved toughness. Fluoroplastic by itself has high impermeability to such hydrocarbon fluids as fuel as compared to the relatively high permeability of PEKK to such fluid. Dispersion of a relatively small amount of the fluoroplastic, e.g. 5 to 30 wt %, greatly improves the impermeability of the PEKK (the resultant blend) to such fluid and improves the toughness of the PEKK as well. Thus, co extruded tubing of a fluoroplastic inner layer and a layer of the blend (dispersion of the fluoroplastic in the PEKK) of the present invention is highly useful in applications for transporting such hydrocarbon fluid as fuel both on board motorized vehicles and in stationary applications.
The fluoroplastic and PEKK components can be melt blended as part of the extrusion process or can be premixed, followed by melt blending at temperature at which both resins are molten. Generally, the melt blending temperature will be at least 300° C. Under this condition, the PEKK or the fluoroplastic, as the case may be, becomes uniformly dispersed as fine particles (domains) in the component which becomes the matrix. The resultant extrudate can be the final molded article, such as in the case of an injection molded article or an extruded tube, sheet or coating, or can be chopped into molding granules for subsequent melt processing into the article desired.
The compositions of the present invention can contain other ingredients such as pigments for coloring the composition or fillers, such as mica, glass, carbon, or aramid, in fibrous or other particulate form. The PEKK aids in dispersing the filler in the fluoroplastic matrix. When filler is present, the amount present will be 0.5 to 30 wt % based on the combined weight of PEKK, fluoroplastic and filler.
EXAMPLES
The general procedure for melt blending to form blends of the present invention as described in the following Examples was as follows: The fluoroplastic and PEKK were fed in the proportions desired to a twin-screw extruder equipped with high shear screws for melt blending under vaccuum to remove any gas that may be generated. The maximum extruder temperature is reported in the Examples. The resulting melt blend was extruded as strands, cooled and chopped up into pellets for injection and compression molding at temperatures of 330 to 370° C. for testing. The melt flow rates (MFR) disclosed in the Examples are typical for the respective fluoropolymers as indicated in the commercial product literature. The PEKK used in the Examples is made by the process disclosed in U.S. Pat. No. 4,816,556 (Gay et al.)
Example 1
In this experiment, the fluoroplastic was TEFLON® PFA fluoropolymer resin grade 350 (MFR 2 g/10 min at 372° C.) and the PEKK contained T and I units in a 80/20 ratio. The extruder temperature used was 360° C. Blends containing 5 to 30 wt % of the fluoroplastic dispersed in the PEKK matrix were made and tested for high temperature distortion (test previously described) and tensile modulus, with the results shown in the following tables:
TABLE 1 HDT Wt % PFA Wt % PEKK HDT - ° C. 100 0 61.5 95 5 70.1 90 10 81.0 80 20 132.0 70 30 151.0 0 100 162.0
These results show that only a relatively small proportion of the PEKK dispersant in the fluoroplastic has a much greater effect on increasing HDT than would be expected. For example, only 30 wt % of the PEKK was needed to raise the HDT almost 90% of the difference in HDT between pure PFA and pure PEKK.
TABLE 2 Tensile Modulus (D638) Wt % PFA Wt % PEKK Tensile Mod.- ksi* (MPa) 100 0 40 (276) 95 5 49.1 (339) 90 10 93 (642) 80 20 193 (1332) 70 30 247 (1704) 0 100 530 (3657) *1 ksi = 1000 psi
This table shows that the tensile modulus of PFA is quite low as compared to PEKK, but that with only 30 wt % of the blend being PEKK, more than 50% of the difference between these moduli is gained by the 70/30 blend. Additional blends were made in which the PEKK content was increased from 30 wt % to 95 wt % in approximately 10 wt % increments.
Similar results are obtained when resin grade 340 PFA (MFR 13 g/10 min at 372° C.) is substituted for the 350 resin grade PFA.
Example 2
Blends were made in which the PEKK contained T and I units in a 60/40 ratio was the PFA was the 340 grade. In these experiments the PEKK contained about 10 wt % of TiO₂ filler, based on the weight of the PEKK plus filler, and the PEKK/filler blend constituted 70 to 80 wt % of the total composition. The temperature of the twin screw extruder was 370° C. The 80 wt % composition was tested for tensile modulus, which was 471 ksi (3250 MPa) as compared to 495 ksi (3416 MPa) for the PEKK composition by itself and 64 ksi (442 MPa) for the PFA by itself. The incorporation of the PFA into the PEKK resulted in an unexpectedly small reduction in the tensile modulus of the PEKK composition, while imparting improved chemical resistance to the overall composition.
Blends similarly made, but containing 40 wt % of the PFA, also exhibited an unexpectedly high tensile modulus of 441 ksi (3043 MPa).
Example 3
This experiment repeated the experiments of Example 2 except that the PFA formed the blend matrix, by constituting 60 to 80 wt % of the total composition. The twin screw extruder temperature was 370° C. Blends containing 60 and 80 wt % of the PFA, thereby forming the matrix of the blend, exhibited unexpectedly high tensile moduli of 296 ksi (2042 MPa) and 222 ksi (1532 MPa), respectively. Articles made from these blends exhibit much greater strength that articles made solely from the PFA resin and chemical resistance approaching that of the pure PFA resin.
Example 4
This experiment was similar to the experiment of Example 2 except that the composition of the melt blend was 60 wt % of the PEKK, 5 wt % TiO₂, and 35 wt % of the PFA. Similarly higher than expected tensile modulus (318 ksi, 2194 MPa) was obtained.
Example 5
The PEKK composition of Example 2 was used and the fluoroplastic was TFE/HFP copolymer (TEFLON® FEP fluoropolymer resin grade 100, MFR 7 g/10 min at 372°). Blends containing 5 to 30 wt % of this fluoroplastic and 95 to 70 wt % of the PEKK were prepared using a twin screw extruder operating at 370° C. The tensile modulus of the FEP by itself is 50 ksi (345 MPa). The tensile moduli of the blends having 5, 10 and 20 wt % of the FEP were determined and all were greater than 436 ksi (3008 MPa) obtained for the 20 wt % blend, which is unexpectedly high.
Blends similarly made but containing 60, 80, and 90 wt % of the FEP, thereby forming the matrix of the blend, exhibited unexpectedly high tensile moduli of 310 ksi (2139 MPa), 185 ksi (1277 MPa), and 141 ksi (973 MPa), respectively.
Example 6
A blend of 80 wt % TEFZEL® ETFE fluoropolymer grade 280 (MFR 4 g/10 min at 297° C.) and 20 wt % of the PEKK used in Example 1 was prepared in the twin screw extruder at a temperature of 370° C. and tested for tensile modulus. The TEFZEL fluoroplastic by itself exhibited a tensile modulus of 186 ksi (1283 MPa), and the blend exhibited a tensile modulus of 263 ksi (1815 MPa), which is greater than the increase that would have been expected from the tensile modulus of the PEKK. A similar result was obtained when the PEKK of Example 2 was used; the 80/20 blend exhibited a tensile modulus of 260 ksi (1794 MPa).
Example 7
This Example shows the unexpectedly high tensile modulus of blends of fluoroplastic and PEKK when the fluoroplastic is a combination of melt-fabricable and melt-flowable, not melt-fabricable fluoroplastics. The PEKK used was that of Example 1, tensile modulus of 530 ksi, the melt-fabricable fluoroplastic was TEFLON® PFA fluoropolymer grade 440 HP (MFR 13 g/10 min at 372°) exhibiting a tensile modulus of 80 ksi (552 MPa), and the melt flowable, not melt-fabricable fluoroplastic (PTFE micropowder) was ZONYL® fluoroadditive grade MP 1600 (MFR 17 g/10 min at 372° C.) exhibiting no tensile strength (zero tensile modulus), because the tensile test bars break upon clamping in the tensile testing machine. The results are shown in Table 3.
TABLE 3 Tensile Modulus Tensile Modulus Wt % PFA Wt % MP1600 Wt % PEKK ksi MPa 5 50 45 360 2484 10 50 40 350 2415 20 50 30 340 2346 30 50 20 260 1794 40 50 10 180 1242
Table 3 shows that even only a small proportion of PEKK doubles the tensile modulus of the PFA considered by itself, and that the MP 1600 fluoroadditive which has no tensile modulus, does not detract from the tensile strengthening of the blend. Surprisingly, the MP1600 fluoroadditive, which has no tensile strength, can constitute a substantial proportion of the blend with PEKK, wherein the blend has high tensile modulus. This provides a utility for the MP 1600 fluoroadditive in molded articles, in contrast to prior utilities for this fluoropolymers as a particulate solid lubricant in liquid media or as a component in a supported coating composition. The PTFE micropowder also imparts improved chemical resistance and lubricity to the blend.
Example 8
This Example shows the improved creep resistance (reduced creep) of blends of the present invention. The fluoropolymer used was the PFA of Example 1 and the PEKK used was that of Example 1. The creep of test specimens of the blends was measured by DMA (Dynamic Mechanical Analyzer) at 100° C. using a 500 g load. The creep is the increase in length of the specimen as a percent of the original length (% elongation)
% Elongation Wt % PFA Wt % PEKK Initial (10,000 hours) 100 — 1.83 3.04 — 100 0.11 0.16 95 5 1.48 2.39 90 10 0.97 1.51 80 20 0.55 0.81 70 30 0.37 0.77
Table 3 shows that as little as 5 wt % PEKK reduces the initial elongation by 19% and the long term elongation (creep) by 21%. The presence of 20 wt % PEKK in the blend decreases creep by almost 400%.
What is claimed is:
1. Composition comprising 5 to 95 wt % non-elastomeric melt-flowable fluoroplastic having crystallinity and complement ally to total 100 wt %, 95 to 5 wt % polyetherketoneketone.
2. The composition of claim 1 wherein said polyetherketoneketone is dispersed in a matrix of said fluoroplastic.
3. The composition of claim 1 wherein said fluoroplastic is dispersed in a matrix of said polyetherketoneketone.
4. The composition of claim 1 and additionally containing filler.
5. The composition of claim 1 wherein the amount of said polyetherketoneketone present is 5 to 30 wt %.
6. The composition of claim 1 wherein the amount of said polyetherketoneketone present is 40 to 50 wt %.
7. The composition of claim 1 wherein the amount of said fluoroplastic present is 5 to 30 wt %.
8. The composition of claim 1 wherein said fluoroplastic is melt fabricable fluoroplastic.
9. The composition of claim 1 wherein said fluoroplastic comprises at least 10 wt % of melt-fabricable fluoroplastic, the remainder to total 100 wt % of said fluoroplastic being polytetrafluoroethylene micropowder.
10. Process comprising coextruding a composite tubing having an inner layer of melt fabricable fluoroplastic and an outer layer of the composition of claim
1.
|
Board Thread:Roleplaying/@comment-29559990-20141219013143/@comment-11457306-20141226161344
(Are we doing a flashback conversation? Kasa was done. She found out what she wanted to know.)
|
[1pt] Add item class properties
All Item class properties visible in the diagram should be defined and set up in the constructor method. Exception: properties for the 1-to-many relationships should NOT be set in the constructor method. Instead, they should have a custom setter method created.
Closing the issue as the task has been completed in Pull Request No. 27
|
import {
REQUEST_DIGEST,
REQUEST_DIGEST_ERROR,
RECEIVE_DIGEST
} from '../constants/digest';
/**
* @param path
* @returns {{type: string, payload: {path: *}}}
*/
export function requestDigest(path) {
return {
type: REQUEST_DIGEST,
payload: {path}
};
}
/**
* @param digest
* @returns {{type: string, payload: {digest: *}}}
*/
export function receiveDigest(digest) {
return {
type: RECEIVE_DIGEST,
payload: {digest}
};
}
/**
* @returns {{type: string}}
*/
export function errorDigest() {
return {
type: REQUEST_DIGEST_ERROR
};
}
|
/**
* 请求登录
* author: freezestudio
* date: 2018-8-1
* ver: 1.0
*/
import { PackBodyStruct, from_string, to_string } from "../core/htmix";
export interface IWebSubSignIn {
id_card: string;
password: string;
}
export class WebSignIn implements PackBodyStruct{
constructor(private signin?:IWebSubSignIn){
}
init(view: ArrayBuffer): void {
if(this.signin){
const card_view = from_string(this.signin.id_card);
const pwd_view = from_string(this.signin.password);
const idcard_pointer = new Int8Array(view,0,18);
const pwd_pointer = new Int8Array(view,18,16);
idcard_pointer.set(card_view);
pwd_pointer.set(pwd_view);
}
}
from(view: ArrayBuffer): void {
if(!this.signin){
this.signin = {
id_card:to_string(view,0,18),
password:to_string(view,18,16)
}
}
}
length(): number {
return 18 + 16;
}
}
|
WOMERSLEY—MICROTROMBIDIINAE OF AUSTRALIA AND NEW GUINEA 341 curved ventrally to give the more or less helmet-like form of the genus Holcotrombidiwm. The smaller setae are as featured by Berlese, with a number of branching granular lobes. Berlese (fig. 82 D-E) shows the specialized comb-like or serrate setae found on segments III onwards of the legs. These are the same on the specimens from Ceylon and measure 35, long (Berlese does not give the length).
Fig. 30. Holcotrombidium ef. dentipile (Canest). Specimen from Ceylon, A, Crista and eyes (X 375); B, palp (X 375); C, front tarsus and metatarsus (X 200); D, larger dorsal seta (X 860); E, smaller dorsal seta (x 860) ; F, leg seta (x 860). The crista is linear, 200p long, with a posterior sensillary area, and with SB 30p. apart; the sensillae are filamentous. The palpi are stout, as figured by Berlese, with strong apical tibial claw, strong accessory claw and two indistinct pectines on tibia, and on the external side of tibia with 3 strong long spine-like setae. Berlese states and figures only one such seta but the number of these external spines in some species (e.g. of the genus Camerotrombidium) appears to be variable, and consequently while referring the Ceylon material to dentipile it should perhaps be considered as a variety. The palpal tarsus is stout, elongate and overreaches tip of tibial claw. The eyes are 2 on each side, prominent and subsessile,
|
Board Thread:General Discussion/@comment-2221250-20140822020300/@comment-1587581-20140822031444
Back when I had Krinkinko he'd turn Super only on rare occasions.
|
Page:The Emperor Marcus Antoninus - His Conversation with Himself.djvu/293
Rh own Nature self-sufficient, and must create her wants before she can feel them. This priviledge makes her Impregnable, and above Restraint; unless the Teazes, and puts Fetters upon her self.
XVII. What is Happiness but wise Thinking, or a Mind rightly dispos'd ? Why then does Fancy break in and disturb the Scene? Be gone! I'le have nothing to do with the Impostures of Imagination! However since they have Custom to plead in their Excuse, let them withdraw, and I'le forgive them.
XVIII. Is any one afraid of Dissolution and Change ? I would gladly know what can be done without it ? If the Course of Nature, and the method of the Universe, won't reconcile us to the Expectation, we are somewhat unreasonable. Pray must not your Wood be turn'd into a Coal, before your Bath can be ready for you? Must not your Meat be changed in your Stomack to make it fit to Nourish you ? Indeed what part of Life or Convenience can go forward without Alteration? Now in all likelyhood a Revolution in your Carcass, and Condition, may be as serviceable to the World in general, as those Alterations abovementiond are to you. Rh
|
from collections import defaultdict
import cv2
from functools import partial
import json
from multiprocessing import Pool
import os
import re
categories = ['ancient_artillery', 'bandit_archer', 'bandit_guard', 'black_imp', 'cave_bear', 'city_archer', 'city_guard', 'cultist', 'deep_terror', 'earth_demon', 'flame_demon', 'forest_imp', 'frost_demon', 'giant_viper', 'harrower_infester', 'hound', 'inox_archer', 'inox_guard', 'inox_shaman', 'living_bones', 'living_corpse', 'living_spirit', 'lurker', 'night_demon', 'ooze', 'savvas_icestorm', 'savvas_lavaflow', 'spitting_drake', 'stone_golem', 'sun_demon', 'vermling_scout', 'vermling_shaman', 'vicious_drake', 'wind_demon']
is_crowd = 0
MASK_REGEX = r"image_\d+_mask_\d+_(.*)\.png"
def get_mask_contours(image_id, image_masks, debug=False):
image_id_filter = image_id + "_"
image_masks = [x for x in image_masks if image_id_filter in x[1]]
result = []
if debug:
print("{}: {}".format(image_id, image_masks))
mask_id = 0
for (dirpath, filename) in image_masks:
mask = cv2.imread(os.path.join(dirpath, filename))
name = re.match(MASK_REGEX, filename)[1]
gray = cv2.cvtColor(mask, cv2.COLOR_BGR2GRAY)
ret, thresh = cv2.threshold(gray, 200, 255, cv2.THRESH_BINARY)
contours, _ = cv2.findContours(thresh, cv2.RETR_TREE, cv2.CHAIN_APPROX_SIMPLE)
contour = sorted(contours, key=lambda x: -cv2.contourArea(x))[0]
result.append((name, contour))
if debug:
cv2.drawContours(mask, contours, -1, (0, 255, 0), thickness=1)
cv2.drawContours(mask, [contour], -1, (0, 0, 255), thickness=2)
cv2.imshow("{}: {} - {}".format(image_id, mask_id, name), mask)
mask_id += 1
if debug:
print([x[0] for x in result])
cv2.waitKey(0)
cv2.destroyAllWindows()
return result
def create_sub_mask_annotation(sub_mask, image_id, category_id, annotation_id, is_crowd):
segmentations = [cv2.approxPolyDP(sub_mask, 1, True)]
bbox = cv2.boundingRect(segmentations[0])
return {
'segmentation': [s.ravel().tolist() for s in segmentations],
'iscrowd': is_crowd,
'image_id': image_id,
'category_id': category_id,
'id': annotation_id,
'bbox': tuple(bbox),
'area': cv2.contourArea(sub_mask)
}
def process_image(image, image_masks):
dirpath, filename = image
image_id = filename.replace(".png", "")
try:
sub_masks = get_mask_contours(image_id, image_masks)
except IndexError:
print("Error processing image: " + image_id)
return None
annotations = []
annotation_id = 1
for (name, sub_mask) in sub_masks:
category_id = categories.index(name) + 1
annotation = create_sub_mask_annotation(
sub_mask,
image_id,
category_id,
image_id + "_" + str(annotation_id),
is_crowd
)
annotations.append(annotation)
annotation_id += 1
return {
'annotations': annotations,
'image': {
'id': image_id,
# 'file_name': os.path.join(dirpath, image_id).replace("masks", "images") + ".png"
'file_name': image_id + ".png"
}
}
if __name__ == "__main__":
mask_directory = r"E:\Generated\masks"
masks = []
for (dirpath, dirnames, filenames) in os.walk(mask_directory):
for filename in filenames:
if 'mask' not in filename:
continue
masks.append((dirpath, filename))
image_directory = r"E:\Generated\images"
image_names = []
for (dirpath, dirnames, filenames) in os.walk(image_directory):
if "val" in dirpath:
print("Skipping val directory")
continue
for filename in filenames:
image_names.append((dirpath, filename))
processed_images = []
"""
for idx in range(10):
processed_images.append(process_image(image_names[idx], masks))
"""
with Pool(5) as pool:
processed_images.extend(pool.map(partial(process_image, image_masks=masks), image_names))
annotations = []
images = []
all_monsters_found = defaultdict(lambda: 0)
for el in processed_images:
if el is None:
continue
images.append(el["image"])
annotations.extend(el["annotations"])
for annotation in el["annotations"]:
all_monsters_found[categories[annotation["category_id"] - 1]] += 1
print("")
print("")
print("{} successful images".format(len(images)))
print("\n\n== Monsters found: {} ==".format(len(list(all_monsters_found.keys()))))
for key, value in all_monsters_found.items():
print(" - {}: {}".format(key, value))
coco = {
'categories': [
{
'id': idx + 1,
'name': cat,
'supercategory': None
}
for idx, cat in enumerate(categories)
],
'images': images,
'annotations': annotations
}
with open(r"E:\Generated\annotations.json", "w") as file:
json.dump(coco, file)
|
President Obama signed into law legislation crafted by Rep. Maxine Waters (D-CA) that should provide further debt cancellation for Haiti. The law “directs the Secretary of the Treasury to instruct the U.S. Executive Directors at the World Bank, the International Monetary Fund (IMF)” to
1. cancel immediately and completely all debt owed by Haiti to these institutions;
2. suspend Haiti’s debt service payments to the institutions until the debt is canceled completely; and
3. provide additional assistance to Haiti in the form of grants so that Haiti does not accumulate additional debt.
...and also push for “the cancellation of all remaining bilateral, multilateral, and private creditor debt owed by Haiti” and to secure grants, instead of loans, from multilateral lenders for Haiti through January 2015.
The bill should expedite debt cancellation by – among others - the IMF, which has yet to cancel Haiti’s debt, despite various statements by IMF Managing Director, Dominique Strauss-Kahn, regarding a “Marshall Plan for Haiti.”
The IMF offered Haiti a $114 million loan following January’s devastating earthquake. After this received much criticism in the media, the IMF announced that Haiti would not have to pay any interest on the loan, and would not have to start paying back the principle for 5.5 years.
Most recently, Strauss-Kahn told the UN donors’ conference that the Fund will present a proposal for total cancellation of Haiti’s debt to the IMF Executive Board. Considering that the U.S. Treasury continues to wield an effective veto over the IMF, Strauss-Kahn’s proposal should pass easily now that Congress is pressing Geithner to publicly push for it.
Meanwhile, members of Congress say they are closer to passing another Haiti-focused bill, one that would be aimed at boosting U.S. imports of apparel from Haiti. A bipartisan deal will probably bring the bill, which would extend existing trade preferences for garments made in Haiti through September 2020, to a vote in the near future. A Real News Network interview today with Haitian labor organizer Didier Dominique, of Batay Ouvriye, examines working conditions in garment factories in Haiti’s Export Processing Zones, where Didier says workers make $3.00/day and often “cannot leave” their jobs because they become indebted to their employers.
Site Maintenance
"The CEPR website currently takes longer to load than usual. We hope to have this and other issues addressed shortly. While this much needed site maintenance is taking place, our content is still available so please continue to slooowwwly surf the pages of our site. Thank you for your patience."
|
Board Thread:Roleplaying/@comment-25828117-20191223012920/@comment-25828117-20191224021810
"No! Don't be daft." Nemicus said crossing his arms.
"They kill men. That's their whole schtick." He grinned.
|
Talk:Handmaid's Ladle/@comment-1855630-20140417051146/@comment-24756074-20140503074947
But mundane will reduce scaling from other stats and will cut base damage in half.
|
Thread:Octopushy/@comment-27628339-20151011144429/@comment-25610519-20151011150916
What ceiling? :P
Yeah, I'm sitting outside as of right now XD
|
Target Books/1973
Target Books was the main publishing imprint of Doctor Who titles from 1973 until the early 1990’s.
Reprints and Other Title Covers
None
Publishing History
May
* Doctor Who and the Daleks Writer: David Whitaker Cover Artist: Chris Archilleos
* Doctor Who and the Zarbi Writer: Bill Strutton Cover Artist: Chris Archilleos
* Doctor Who and the Crusaders Writer: David Whitaker Cover Artist: Chris Archilleos
Publishing Notes
* to be added
Other Reference Sources
* Personal Collection
* Doctor Who Magazine
* Howe’s Celestial Toybox
* Collectors guides
* The Target Book by David Howe release date 2007
|
Board Thread:Off-Topic Fun/@comment-5679696-20141215164611/@comment-25926288-20151110043508
Camelot was once a desert, but that could have been all of the EF, but it's not neatly defined.
Map of Arthuir's castle was revealed! Not much though.
|
User blog:Damac1214/Mob of the Dead Development Interview
Interview
'''Why Alcatraz? What other locations did you consider in pre-production?'''
'''With Mob of the Dead, you lay out the plan right at the start. Why the added transparency?'''
Was there anything throughout the production of Mob of the Dead that really stood out for you?
Uprising
In case you haven't heard, Uprising is also now available on Playstation 3 and PC for 15 dollars.
|
#! /usr/bin/env python3
# Copyright (c) Facebook, Inc. and its affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.
r"""
Abstract base module for all botorch posteriors.
"""
from abc import ABC, abstractmethod, abstractproperty
from typing import Optional
import torch
from torch import Tensor
class Posterior(ABC):
r"""Abstract base class for botorch posteriors."""
@abstractproperty
def device(self) -> torch.device:
r"""The torch device of the posterior."""
pass # pragma: no cover
@abstractproperty
def dtype(self) -> torch.dtype:
r"""The torch dtype of the posterior."""
pass # pragma: no cover
@abstractproperty
def event_shape(self) -> torch.Size:
r"""The event shape (i.e. the shape of a single sample)."""
pass # pragma: no cover
@property
def mean(self) -> Tensor:
r"""The mean of the posterior as a `(b) x n x m`-dim Tensor."""
raise NotImplementedError(
f"Property `mean` not implemented for {self.__class__.__name__}"
)
@property
def variance(self) -> Tensor:
r"""The variance of the posterior as a `(b) x n x m`-dim Tensor."""
raise NotImplementedError(
f"Property `variance` not implemented for {self.__class__.__name__}"
)
@abstractmethod
def rsample(
self,
sample_shape: Optional[torch.Size] = None,
base_samples: Optional[Tensor] = None,
) -> Tensor:
r"""Sample from the posterior (with gradients).
Args:
sample_shape: A `torch.Size` object specifying the sample shape. To
draw `n` samples, set to `torch.Size([n])`. To draw `b` batches
of `n` samples each, set to `torch.Size([b, n])`.
base_samples: An (optional) Tensor of `N(0, I)` base samples of
appropriate dimension, typically obtained from a `Sampler`.
This is used for deterministic optimization.
Returns:
A `sample_shape x event`-dim Tensor of samples from the posterior.
"""
pass # pragma: no cover
def sample(
self,
sample_shape: Optional[torch.Size] = None,
base_samples: Optional[Tensor] = None,
) -> Tensor:
r"""Sample from the posterior (without gradients).
This is a simple wrapper calling `rsample` using `with torch.no_grad()`.
Args:
sample_shape: A `torch.Size` object specifying the sample shape. To
draw `n` samples, set to `torch.Size([n])`. To draw `b` batches
of `n` samples each, set to `torch.Size([b, n])`.
base_samples: An (optional) Tensor of `N(0, I)` base samples of
appropriate dimension, typically obtained from a `Sampler` object.
This is used for deterministic optimization.
Returns:
A `sample_shape x event_shape`-dim Tensor of samples from the posterior.
"""
with torch.no_grad():
return self.rsample(sample_shape=sample_shape, base_samples=base_samples)
|
from __future__ import annotations
import sys
from datetime import datetime, timedelta
from django.utils.timezone import now
if sys.version_info >= (3, 9):
from zoneinfo import ZoneInfo
else:
from backports.zoneinfo import ZoneInfo
class Unit(object):
def __init__(self, name: str, nsecs: int):
self.name = name
self.plural = name + "s"
self.nsecs = nsecs
SECOND = Unit("second", 1)
MINUTE = Unit("minute", 60)
HOUR = Unit("hour", MINUTE.nsecs * 60)
DAY = Unit("day", HOUR.nsecs * 24)
WEEK = Unit("week", DAY.nsecs * 7)
def format_duration(duration: timedelta) -> str:
remaining_seconds = int(duration.total_seconds())
result = []
for unit in (WEEK, DAY, HOUR, MINUTE):
if unit == WEEK and remaining_seconds % unit.nsecs != 0:
# Say "8 days" instead of "1 week 1 day"
continue
v, remaining_seconds = divmod(remaining_seconds, unit.nsecs)
if v == 1:
result.append("1 %s" % unit.name)
elif v > 1:
result.append("%d %s" % (v, unit.plural))
return " ".join(result)
def format_hms(duration: timedelta) -> str:
total_seconds = duration.total_seconds()
if 0.01 <= total_seconds < 1:
return "%.2f sec" % total_seconds
total_seconds = int(total_seconds)
result = []
mins, secs = divmod(total_seconds, 60)
h, mins = divmod(mins, 60)
if h:
result.append("%d h" % h)
if h or mins:
result.append("%d min" % mins)
result.append("%s sec" % secs)
return " ".join(result)
def format_approx_duration(duration: timedelta) -> str:
v = duration.total_seconds()
for unit in (DAY, HOUR, MINUTE, SECOND):
if v >= unit.nsecs:
vv = v // unit.nsecs
if vv == 1:
return f"1 {unit.name}"
else:
return f"{vv} {unit.plural}"
return ""
def month_boundaries(months: int, tzstr: str) -> list[datetime]:
tz = ZoneInfo(tzstr)
result: list[datetime] = []
now_value = now().astimezone(tz)
y, m = now_value.year, now_value.month
for x in range(0, months):
result.insert(0, datetime(y, m, 1, tzinfo=tz))
m -= 1
if m == 0:
m = 12
y = y - 1
return result
def week_boundaries(weeks: int, tzstr: str) -> list[datetime]:
tz = ZoneInfo(tzstr)
result: list[datetime] = []
today = now().astimezone(tz).date()
needle = today - timedelta(days=today.weekday())
for x in range(0, weeks):
result.insert(0, datetime(needle.year, needle.month, needle.day, tzinfo=tz))
needle -= timedelta(days=7)
return result
|
#ifndef StaticWaveFileSource_H_INCLUDED
#define StaticWaveFileSource_H_INCLUDED
#include "ISoundSource.h"
#include <Threading.h>
#include <functional>
//! A sound source for wave files loaded into memory
//! Currently only pcm wave files with 8 or 16 bit mono or stereo are supported
class StaticWaveFileSource : public ISoundSource{
private:
//read only:
uint8_t* buffer;
uint32_t bufferSize;
ISoundSource::PCMFormat format;
uint32_t sampleRate;
uint32_t bytesPerFrame;
bool good;
//exchange:
Mutex m;
bool loop;
bool ready;
int32_t offsetToSet;//-1 if no change
//thread only:
uint32_t offset;
uint32_t dataOffset;
bool deleteMemoryOnDestruct;
void parseBuffer();
public:
//! loads the wave file from a given path
StaticWaveFileSource(SoundManager* soundmgr, const char* path);
//! loads the wave file using a loader function, the loader function must return true on success and read the file into a new buffer (first param) and fills the buffer size (second param)
StaticWaveFileSource(SoundManager* soundmgr, const std::function<bool(char*&, uint32_t&)>& loadFunction);
//! uses an externally provided buffer containing the whole wave file
StaticWaveFileSource(SoundManager* soundmgr, uint8_t* buffer, uint32_t bufferSize, bool useForeignMemory = true, bool deleteMemoryOnDestruct = true);
~StaticWaveFileSource();
void setLoop(bool loop);
//! true if wave file good and can be parsed
bool isGood() const;
ISoundSource::PCMFormat getPCMFormat() const;
uint32_t getSampleRate() const;
uint32_t fillNextBytes(uint8_t* buffer, uint32_t bufferSize);
bool isPlayingOrReady();
void seek(float position);
};
#endif
|
[8338] Concatenate integer and fraction parts from fixed_Name1 into a single bit string
[8339] Concatenate integer and fraction parts from fixed_Name2 into a single bit string
[8340] True if the first bit string is less than the second
[8341] Return result
[8342] COMP 4.4 Fixed LTE(fixed_Name1,fixed_Name2)
[8343] Description
[8344] Returns true if fixed_Name1 is less than or equal to fixed_Name2. Inputs fixed_Name1 Fixed-point number of any type or width fixed_Name2 Fixed-point number of the same type and width
[8345] Output
[8346] Single bit wide unsigned integer value with 0 as false and 1 as true
[8347] Detailed Description
[8348] Concatenate integer and fraction parts from fixed_Name1 into a single bit string
[8349] Concatenate integer and fraction parts from fixed_Name2 into a single bit string
[8350] True if the first bit string is less than or equal to the second
[8351] Return result
[8352] COMP 4.5 Fixed GT(fixed_Name1,fixed_Name2)
[8353] Description
[8354] Returns true if fixed_Name1 is greater than fixed_Name2. Inputs fixed_Name1 Fixed-point number of any type or width fixed_Name2 Fixed-point number of the same type and width
[8355] Output
[8356] Single bit wide unsigned integer value with 0 as false and 1 as true
[8357] Detailed Description
[8358] Return the result of Fixed LT(fixed_Name2,fixed_Name1)
[8359] COMP 4.6 Fixed GTE(fixed_Name1,fixed_Name2)
[8360] Description
[8361] Returns true if fixed_Name1 is greater than or equal to fixed_Name2. Inputs fixed_Name1 Fixed-point number of any type or width fixed_Name2 Fixed-point number of the same type and width
[8362] Output
[8363] Single bit wide unsigned integer value with 0 as false and 1 as true
[8364] Detailed Description
[8365] Return the result of Fixed LTE(fixed_Name2,fixed_Name1)
[8366] Bitwise Logical Operators
[8367] The macros in this section rely on Handel-C's type and width checking.
[8368] COMP 5.1 Fixed Not(fixed_Name)
[8369] Description
[8370] Returns bitwise not. Inputs fixed_Name Fixed-point number of any type or width
[8371] Output
[8372] Fixed-point number of same type and width as fixed_Name
[8373] Detailed Description
[8374] Concatenate integer and fraction parts from fixed_Name into a single bit string
[8375] Find the bitwise not of the bit string
[8376] Split result into integer and fraction parts of same type and width as fixed_Name
[8377] Return as struct
[8378] COMP 5.2 Fixed And(fixed_Name1,fixed_Name2)
[8379] Description
[8380] Returns bitwise and. Inputs fixed_Name1 Fixed-point number of any type or width fixed_Name2 Fixed-point number of the same type and width
[8381] Output
[8382] Fixed-point number of same type and width as fixed_Name1
[8383] Detailed Description
[8384] Concatenate integer and fraction parts from fixed_Name1 into a single bit string
[8385] Concatenate integer and fraction parts from fixed_Name2 into a single bit string
[8386] Find the bitwise and of the bit strings
[8387] Split result into integer and fraction parts of same type and width as fixed_Name1
[8388] Return as struct
[8389] COMP 5.3 Fixed Or(fixed_Name1,fixed_Name2)
[8390] Description
[8391] Returns bitwise or. Inputs fixed_Name1 Fixed-point number of any type or width fixed_Name2 Fixed-point number of the same type and width
[8392] Output
[8393] Fixed-point number of same type and width as fixed_Name1
[8394] Detailed Description
[8395] Concatenate integer and fraction parts from fixed_Name1 into a single bit string
[8396] Concatenate integer and fraction parts from fixed_Name2 into a single bit string
[8397] Find the bitwise or of the bit strings
[8398] Split result into integer and fraction parts of same type and width as fixed_Name1
[8399] Return as struct
[8400] COMP 5.4 Fixed Xor(fixed_Name1,fixed_Name2)
[8401] Description
[8402] Returns bitwise xor. Inputs fixed_Name1 Fixed-point number of any type or width fixed_Name2 Fixed-point number of the same type and width
[8403] Output
[8404] Fixed-point number of same type and width as fixed_Name1
[8405] Detailed Description
[8406] Concatenate integer and fraction parts from fixed_Name1 into a single bit string
[8407] Concatenate integer and fraction parts from fixed_Name2 into a single bit string
[8408] Find the bitwise xor of the bit strings
[8409] Split result into integer and fraction parts of same type and width as fixed_Name1
[8410] Return as struct
[8411] Conversion Operators
[8412] COMP 6.1 FixedIntWidth(fixed_Name)
[8413] Description
[8414] Returns the width of the integer part of fixed_Name as a compile time constant. Inputs fixed_Name1 Fixed-point number of any type or width
[8415] Output
[8416] Compile time constant integer
[8417] Detailed Description
[8418] Return the width of the integer part of fixed_Name
[8419] COMP 6.2 FixedFracWidth(fixed_Name)
[8420] Description
[8421] Returns the width of the fraction part of fixed_Name as a compile time constant. Inputs fixed_Name1 Fixed-point number of any type or width
[8422] Output
[8423] Compile time constant integer
[8424] Detailed Description
[8425] Return the width of the fraction part of fixed_Name
[8426] COMP 6.3 Fixed Literal(isSigned, intWidth,fracWidth, intBits,fracBits)
[8427] Description
[8428] Returns a signed fixed-point number if isSigned is true and an unsigned fixed-point number if isSigned is false. This number has an integer part intBits of width intWidth and a fraction part fracBits of width frac Width. Inputs isSigned Compile time constant to indicate the type of fixed-point structure. FIXED_ISSIGNED represents signed and FIXED_ISUNSIGNED unsigned intWidth Compile time constant integer to set width of integer part fracWidth Compile time constant integer to set width of fraction part intBits Value to set integer part fracBits Value to set fraction part
[8429] Output
[8430] Signed or unsigned fixed-point number with widths and values specified
[8431] Detailed Description
[8432] Selects signed or unsigned type to cast structure using isSigned
[8433] Return a fixed-point number with an integer part of width intWidth and value intBits, and a fraction part of width frac Width and value fracBits
[8434] COMP 6.4 FixedTolnt(fixed_Name)
[8435] Description
[8436] Returns the integer part of the fixed point number with the same type and width. Inputs fixed_Name Fixed point number of any type or width
[8437] Output
[8438] Integer of same type and width as the integer part of the number is stored in the fixed point structure
[8439] Detailed Description
[8440] Return the integer part of the fixed point number
[8441] COMP 6.5 FixedToBool (fixed_Name)
[8442] Description
[8443] Returns a single bit wide unsigned int value which is 0 for false if the operand equals 0 and 1 for true otherwise. Inputs fixed_Name Fixed-point number of any type or width
[8444] Output
[8445] Single bit wide unsigned integer value with 0 as false and 1 as true
[8446] Detailed Description
[8447] Return 1 if the fixed and the fraction parts of fixed_Name are both not equal to zero and 0 otherwise
[8448] COMP 6.6 FixedToBits(fixed_Name)
[8449] Description
[8450] Returns the integer and fraction bits of fixed_Name concatenated together. Inputs fixed_Name Fixed-point number of any type or width
[8451] Output
[8452] Integer of same type as the fixed-point structure and with width intWidth+fracWidth
[8453] Detailed Description
[8454] Return the integer part and the fraction part of the fixed-point number concatenated together
[8455] COMP 6.7 FixedCastSigned(isSigned, intWidth, fracWidth, fixed_Name)
[8456] Description
[8457] Casts any signed fixed-point number to the type and widths specified. Inputs isSigned Compile time constant to indicate the type of fixed-point structure. FIXED_ISSIGNED represents signed and FIXED_ISUNSIGNED unsigned intWidth Width to cast the integer part of the number to fracWidth Width to cast the fraction part of the number to fixed_Name Fixed-point number of signed type and any width
[8458] Output
[8459] Fixed-point number of the type specified
[8460] Detailed Description
[8461] Adjust the integer part of fixed_Name to a width of intWidth by either taking the intWidth least significant bits or sign extending.
[8462] Adjust the fraction part of fixed_Name to a width of fracWidth by either taking the fracWidth most significant bits or adding bits with value zero in after the number.
[8463] If isSigned is true then cast the integer and fraction parts of the floating point number as signed
[8464] If isSigned is false then cast the integer and fraction parts of the floating point number as unsigned
[8465] Return the result as a struct
[8466] COMP 6.8 FixedCastUnsigned(isSigned, intWidth, fracWidth, fixed_Name)
[8467] Description
[8468] Casts any unsigned fixed-point number to the type and widths specified. Inputs isSigned Compile time constant to indicate the type of fixed-point structure. FIXED_ISSIGNED represents signed and FIXED_ISUNSIGNED unsigned intWidth Width to cast the integer part of the number to fracWidth Width to cast the fraction part of the number to fixed_Name Fixed-point number of unsigned type and any width
[8469] Output
[8470] Fixed-point number of the type specified
[8471] Detailed Description
[8472] Adjust the integer part of fixed_Name to a width of intWidth by either taking the intWidth least significant bits or adding bits with value zero in front of the number.
[8473] Adjust the fraction part of fixed_Name to a width of fracWidth by either taking the fracWidth most significant bits or adding bits with value zero in after the number.
[8474] If isSigned is true then cast the integer and fraction parts of the floating point number as signed
[8475] If isSigned is false then cast the integer and fraction parts of the floating point number as unsigned
[8476] Return the result as a struct
[8477] Verification
[8478] This section documents all of the tests necessary to verify that each macro functions correctly. It is important that the macros match their definitions in the subsections above. All of the macros available to the user can be tested for results and errors using black box testing.
[8479] Runtime tests:
[8480] The type performed are:
[8481] Positive (P)
[8482] Negative (N)
[8483] Volume and Stress (V&S)
[8484] Comparison (C)
[8485] Demonstration (D)
[8486] The tests are performed only on 8 and 32 bit numbers apart from when it seems appropriate to use other widths also to fully test the macro, such as for FixedIntWidth. The tests are performed on signed and unsigned numbers apart from when this is not possible because the macro is only designed for one type. Generally the tests are aimed at:
[8487] Zero values (P, V&S, C, D)
[8488] Midrange values (P, V&S, C, D)
[8489] Overflow values (N, V&S, C, D)
[8490] The results expected for the comparison tests have been calculated using the Microsoft Calculator.
[8491] Error tests:
[8492] These are tests which may produce non-severe errors from the compiler. They should be either standard Handel-C error messages directed at the functions used or assert errors defined in the library. Generally the tests performed may be:
[8493] inputting an integer into where there should be a fixed-point structure
[8494] inputting a signed fixed-point structures where there should be an unsigned fixed-point structure and vice versa
[8495] inputting two fixed-point structures of different types or width in the same macro
[8496] inputting an integer of incorrect width
[8497] inputting variables when a constant is required
[8498] assigning fixed-point result to a fixed-point structure of incorrect type or width
[8499] assigning integer result to a int of incorrect type or width
[8500] Performance tests:
[8501] All of the macros take just one clock cycle to run. In the case of the arithmetic operators, the number of SLICEs and maximum speed may be calculated to compare with the appropriate Handel-C operator.
WAVEFORM ANALSIS
[8502] Trace/Pattern Window
[8503]FIG. 93 illustrates a Trace and Pattern window 9300. In the Trace and Pattern window, the top half 9302 of the window shows the trace or pattern details. The bottom half 9304 of the window shows the values and positions of marks that have been set on the trace or pattern. The marks are referred to as cursors and represented by colored triangles.
[8504] In an illustrative embodiment, the current trace is out-lined with a green dashed line. The current cursor has a red underline. Right-clicking the trace waveform or the current value pane calls up a menu of possible display formats for that pane. Multiple traces or patterns in a single window, but they all use the same cursors, the same number of points and the same clock period.
[8505] Zooming
[8506] A user may zoom in and out of the active Trace or Pattern window using the zoom icons or the Zoom options from the View menu.
[8507] Set Advance Step Dialog
[8508] The Set Advance Step dialog (Capture>Set Advance Step) specifies the time in nanoseconds to advance all simulations by.
[8509] Capture menu
[8510] Several items of a capture menu according to an embodiment of the present invention include the following set forth in Table 23. TABLE 23 Run (F5) Start reading traces from simulations and sending patterns to simulations. Pause Temporarily stop sending traces to simulations and reading patterns from simulations. This may also suspend all connected simulations. Stop (Shift+F5) Stop reading traces from simulations and sending patterns to simulations. Simulations may continue running after Waveform Analyzer has stopped. Advance (Ctrl+F11) Advance all simulations by the specified interval. Set Advance Step Specify the interval by which to advance simulations when ‘Advance’ is selected. Opens Set Advance Step dialog.
[8511] Define Symbols Dialog Box
[8512] The Define symbols dialog box consists of a set of radio buttons which allow selection of how values are represented:
[8513] Binary
[8514] Octal
[8515] Decimal
[8516] Hexadecimal numbers
[8517] ASCII characters
[8518] User defined strings: The user may supply the filename of a file which associates symbols with values for the trace being defined. Each line of this file should contain a number (in binary, octal, decimal or hexadecimal, using the Handel-C syntax) followed by a symbol. The symbol should be separated from the number using a whitespace. Any values which may appear in the Trace and which do not have symbols associated with them may be represented using the ‘?’ character. For example, if the trace is of width 3, is unsigned, and the user defined symbol file contains the following:
[8519] 0b001 A
[8520] 0b111 D
[8521] 0b110 C
[8522] 0b101 B the values 1,5,6 and 7 may be represented as A,B,C and D respectively. The values 0,2,3 and 4 may all be represented as question marks.
[8523] Edit Menu
[8524] Items in the Edit Menu include those set forth in Table 24. TABLE 24 Find (Ctrl+F) Search for a specified sequence of data words in the selected trace or patten. The user is prompted for a PGL statement describing the sequence of words to search for, the search direction, and whether to scroll to the sequence if it is found. Searching starts at the position of the selected cursor. If there is no cursor, searching starts at the beginning of the selected trace or pattern. If the sequence is found, the selected cursor is positioned at the start of the sequence. If there is no cursor, a cursor is created at the start of the sequence. Copy (Ctrl+C) Copy the selected portion of the selected trace or pattern to the clipboard. Paste (Ctrl+V) Paste the contents of the clipboard into the selected portion of the selected pattern. Save Selection Save the selected portion of the selected trace or As . . . pattern to a file. The user is prompted for a filename and, if the file is a VCD file, a reference name to use for the signal in the VCD file.
[8525] File Menu
[8526] Items in the Edit Menu include those set forth in Table 25. TABLE 25 Open a new The user is prompted for the type of window, a filename trace or for the window and the clock period and number of pattern dialog. points for the window. The clock period and the number New (Ctrl+N) of points that the user specifies may be used for all traces or patterns in the window. Open (Ctrl+O) Open an existing trace or pattern file. Close Close the active trace or pattern window. Save (Ctrl+S) Save the active trace or pattern window. Save As Save the active trace or pattern window with a different name. Save All Save all open trace and pattern windows. New Project Create a new project. Open Project Open an existing project. Close Project Close the current project. Save Project Save the current project. Print Print the active trace or pattern window. Print Setup Setup the printer details. Print Preview Preview the active trace or pattern window. Recent Files A list of recently used trace or pattern files. Recent Projects A list of recently used projects. Exit Close all windows and exit the application.
[8527] New Window Dialog
[8528] The New window dialog box (File>New) defines the default clock period and the number of points in the window. Elements include those set forth in Table 26. TABLE 26 Untitled box Enter the window name Default clock Enter the default clock period in nanoseconds period Default No. Enter the number of points recorded in the window points Filename and File where the window details are stored (use the location browse button to choose a directory
[8529] Pattern menu
[8530] Items in the Edit Menu include those set forth in Table 27. TABLE 27 New Pattern Create a new pattern in the active pattern window. Edit Pattern Edit the selected pattern in the active pattern window. Delete Pattern Remove the selected pattern from the active pattern window.
[8531] Pattern Properties Dialog Box
[8532] The fields in the Pattern properties dialog box include those set forth in Table 28. TABLE 28 Name Name to use for the pattern. The name is displayed in a box on the left of the Pattern window. The name may be a C-style identifier. Width Width of the data in the pattern in bits. Type Whether the pattern represents signed or unsigned data. Points Number of points in the pattern. This value was entered when the Pattern Window was created. It cannot be edited. Clock Period Rate at which data is read into the pattern. This value was entered when the Pattern window was created. It cannot be edited. Source The source for the pattern may be either a file or a script. Supported file formats are ASCII and VCD. The box to the right of the radio buttons is used to enter a script if the ‘Script’ radio button is checked, or a file name if the ‘File’ radio button is checked. Variable If the source is a VCD file, this box should be used to enter the reference name of the variable in the VCD file that may be used as the source for this pattern. Destination Expression of the form ‘Terminal-Name(width)’ as for the DK1Connect plugin Trigger Transmission of a pattern can be triggered by the occurrence of a specified sequence of words in any trace. This box is used to specify which sequences of words and which trace triggering should occur on If this box is empty, no trigger is used and all further trigger options are grayed out. Delay Specifies the trigger delay. For patterns, this may be positive. A delay of x means that transmission begins x time units after a trigger sequence occurs. No Choose the trigger mode. trigger/Single/ No trigger, triggering is disabled. Auto Single, a pattern is transmitted once after a trigger sequence occurs. Auto, a pattern is transmitted after every occurrence of a trigger sequence. Pause on If this checkbox is ticked, capturing may Trigger automatically get paused after a trigger sequence has occurred and a pattern has been transmitted. Interpolated This set of radio buttons is used to choose the Waveform/ display format for the pattern. Stepped Waveform/ Numeric Symbolic Define Select how values are represented Symbols (gives dialog)
[8533] Grouping Windows into Projects
[8534] Trace Windows and Pattern Windows can be grouped together into projects. Only one project may be open at a time. The user may create a project if he or she wants to use a Pattern Generation Language Script file.
[8535] Creating a Project
[8536] Open Waveform Analyzer and select New Project from the File menu. A dialog box appears asking the user to select a file name for the new project. Project filenames have an ‘.APJ’ extension.
[8537] Script Menu
[8538] The script menu includes the following item: Edit Script... Edit the PGL script for the current project.
[8539] Trace Dialog
[8540] Fields in the Trace properties dialog box (Trace>New Trace) include the following set forth in Table 29. TABLE 29 Field Function Name Name to use for the trace. This name may be displayed in a box on the left of the Trace window. The name can also be used as part of a trigger specification for this or any other trace. The name may be a C-style identifier. Width Width of the data in the trace in bits. Type Whether the trace represents signed or unsigned data. Points Number of points in the trace. This value was entered when the Trace window was created. It cannot be edited. Clock Period Rate at which data is read into the trace. This value was entered when the Trace window was created. It cannot be edited. Expression Port(s) the trace is connected to. The expression may be of the form ‘Terminal-Name(width)’ (as for the DK1Connect plugin) or a Handel-C expression with expressions of the form ‘Terminal-Name(width)’ in place of variables. Dump File Enter a filename to capture the trace to a file. Two file formats are supported: ASCII files and Verilog Value Change Dump files. If the filename ends in ‘.VCD’, ‘.DMP’ or ‘.DUMP’ a Value Change Dump file may be produced otherwise an ASCII file may be produced. The Browse button may be used to select a filename. If no filename is entered, no dump file may be produced. Variable If the dump file is a Verilog Value Change Dump file, enter the name which may be used as the reference name of the signal in the VCD file. Trigger Specifies which sequences of words triggering should occur on If this box is empty, no trigger is used and all further trigger options are grayed out. Delay Specifies the trigger delay. This may be positive or negative. If a positive delay x is used, capturing begins x time units after a trigger sequence occurs. If a negative delay is used, capturing begins x time units before a trigger sequence occurs. No trigger/ Select trigger mode. Single/Auto No trigger, triggering is disabled. Single, a trace is captured once after a trigger sequence occurs. Auto, a trace is captured after every occurrence of a trigger sequence. Pause on If this checkbox is ticked, capturing may automatically Trigger get paused after a trigger sequence has occurred and a trace has been captured. Interpolated Select display format for trace. Waveform/ Stepped Waveform/ Numeric Symbolic Define Select how values are represented Symbols (gives dialog)
[8541] Trace Menu
[8542] Fields in the trace menu include those set forth in Table 30. TABLE 30 New Trace Create a new trace in the active Trace window. Edit Trace Edit the selected trace in the active Trace window. Delete Trace Remove the selected trace from the active Trace window.
[8543] View Menu
[8544] Items available from the view menu include those set forth in Table 31. TABLE 31 Toolbar Toggle the toolbar on/off. Status Bar Toggle the Status Bar on/off. Zoom Max Zoom in to the maximum extent at the centre of the active trace or pattern window. Zoom In Zoom in at the centre of the active trace or pattern window. Zoom Out Zoom out from the centre of the active trace or pattern window. Zoom Min Zoom out to the maximum extent from the centre of the active trace or pattern window. Zoom on Cursor Zoom in on the selected cursor in the active trace or pattern window. Jump to Cursor Scroll to the selected cursor in the active trace or pattern window. New Cursor Create a new cursor in the centre of the active trace or pattern window. Delete Cursor Delete the selected cursor from the active trace or pattern window.
[8545] Toolbar Icons
[8546]FIG. 94 illustrates several toolbar icons 9400 and their functions 9402.
[8547] Window Menu
[8548] Items in the window menu include those set forth in Table 32. TABLE 32 Cascade Cascade all open windows. Tile Tile all open window. Arrange Icons Automatically arrange all minimized trace and pattern windows.
[8549] Analyzer Interface
[8550] The waveform analyzer interface consists of:
[8551] menu bar
[8552] tool bar
[8553] workspace area
[8554] any trace or pattern windows open
[8555] log output window: used by the program to report errors to the user.
[8556] The user may group trace or pattern windows together in a project. Projects contain a number of trace or pattern windows (those open when during the last save of the project) and any scripts written in the project.
[8557] Menus
[8558] File Menu
[8559] New windows dialog (File>New)
[8560] Edit Menu
[8561] View Menu
[8562] Trace Menu
[8563] Trace dialog
[8564] Pattern Menu
[8565] Pattern properties dialog
[8566] Define symbols dialog
[8567] Script Menu
[8568] Capture Menu
[8569] Window Menu
[8570] Help Menu
[8571] Pattern Generation Language
[8572] The Waveforn Analyzer uses Pattern Generation Language (PGL) as a scripting language to generate patterns. PGL has a similar expressive power to regular expressions, but uses a C-like syntax.
[8573] The PGL can be used to trigger on a sequence of data and search for a sequence of data in a trace or pattern.
[8574] When executed, a PGL program generates a sequence of values. When used for triggering or searching, a program in PGL may match any sequence which it could generate, such as:
[8575] PGL statements
[8576] PGL functions
[8577] Wild-card matching
[8578] Pattern Generation Language syntax
[8579] Using the Waveform Analyzer
[8580] The Waveform Analyzer connects to ports in Handel-C simulations. It displays outputs from Handel-C simulations as waveforms (traces). Thus a user can generate inputs to Handel-C simulations and display them as waveforms (patterns). The user can also manipulate the simulated inputs and outputs in the same way that input and output signals from a real piece of hardware can be manipulated with a waveform analyzer. A partial list of manners in which the waveform analyzer can be used follows.
[8581] Connecting traces to output ports in Handel-C simulations
[8582] Connecting patterns to input ports in Handel-C simulations
[8583] Connecting the Waveform Analyzer to ports connected to another simulation using the DK1Share plugin (connecting in parallel)
[8584] Measuring the differences between values and times in traces or patterns using cursor marks.
[8585] Creating patterns by writing scripts using a Pattern Generation Language, or by copying existing traces or patterns into a pattern window. Patterns can also be read from a file.
[8586] Specifying triggers in the Pattern Generation Language
[8587] Capturing traces or generate patterns when a specified trigger appears in a trace
[8588] Finding a specified pattern in a trace or pattern window
[8589] Functions in PGL
[8590] PGL allows a user to define and call functions which can take parameters. Only functions in an open project can be defined. The functions are stored in the script.pg1 file associated with that project. The user may edit this file outside the Waveform Analyzer.
[8591] Defining Functions
[8592] To define functions, the project where the functions are to be used is opened. The ‘Edit Script’ icon on the toolbar is selected. Alternatively, Edit Script from the Script menu can be selected: the file script.pg 1 is opened in Notepad . This file resides in the same directory as the project file.
EXAMPLE
[8593] The following example defines two functions, one called rising_edge and the other called rectangular_wave.
[8594] rising_edge( )
[8595] {0;1;} rising_edge() {0;1;} rectangular_wave(hiv al,hi count,lo val,lo count,cycles) { loop (cycles) { loop(hi count) hiv al; loop(lo count) lo val; } }
[8596] The rectangular_wave function can be called with a statement like the following:
[8597] rectangular_wave(1,5,0,5 ,10);
[8598] Wild-Card Matching in Triggering or Searching
[8599] When a PGL program is used for triggering or searching, it may contain a ‘?’ character in any place where a number or variable could go. This character stands for ‘any value’. For example the compound statement {1;?;1;}would match against any 3 word sequence starting and ending with a 1.
[8600] If ‘?’ is used as an actual parameter in a function call, when the function is called, the formal parameter which corresponds to the ‘?’ has no value assigned to it.
[8601] If a variable is encountered which has no value assigned to it, it gets assigned a value according to the values encountered during matching.
[8602] Context-sensitive matches can be carried out in this way. For example, if a function is defined as follows:
[8603] count_fives(a)
[8604] {a; loop(a) 5;}
[8605] and called using the statement ‘count_fives(?);’, it may match any sequence consisting of a number, followed by that number of fives (including the sequence ‘0’). This feature should be used carefully, since it is possible to use it write functions which take a very long time to match.
[8606] PGL Statements
[8607] The pattern generation language consists of one or more statements terminated by semi-colons. Statements can include numbers, identifiers and wild-cards. A PGL statement may be one of the following:
[8608] Expression Statement
[8609] For example:
[8610] 1;
[8611] When an expression statement is executed, it generates the value of the expression.
[8612] An expression statement used for matching may also be of the form:
[8613] !1;
[8614] This statement may match any value except 1.
[8615] Compound Statement
[8616] For example: {0;1;}
[8617] The statements enclosed in the curly brackets get executed sequentially.
[8618] Loop Statement
[8619] For example: loop(3) {0;1;}
[8620] The body of this loop may get executed 3 times.
[8621] Conditional Statement
[8622] For example:
[8623] if(a==1) {0;1;} else {1;0;}
[8624] Here, the statements which get executed depend upon the value of the variable a.
[8625] A user can build Boolean tests using the following operators to use for the condition in a conditional statement: == != ! || &&
[8626] Switch Statement
[8627] For example:
[8628] switch(a) switch(a) { case 1: 0; 1; break; default: 1; 0; break; }
[8629] This switch statement achieves the same thing as the if-else statement described above.
[8630] Assert Statement
[8631] For example:
[8632] assert(a !=0);
[8633] This kind of statement can be used when matching to place constraints on matched variables.
[8634] Wild-Card Matching in PGL
[8635] If a PGL program is used for triggering or searching, a ‘?’ character can be used in any place where a number or variable could go. This character stands for ‘any value’. For example the compound statement {1;?;1;}would match against any 3 word sequence starting and ending with a 1.
[8636] If ‘?’ is used as an actual parameter in a function call, when the function is called, the formal parameter which corresponds to the ‘?’ has no value assigned to it. If a variable is encountered which has no value assigned to it, it gets assigned a value according to the values encountered during matching.Context-sensitive matches can be carried out in this way. For example, a function defined as follows:
[8637] count_fives(a)
[8638] {a; loop(a) 5;}
[8639] If this is called using the statement ‘count_fives(?);’, it may match any sequence consisting of a number, followed by that number of fives. (Including the sequence ‘0’). This feature should be used carefully, since it is possible to use it write functions which take a very long time to match.
[8640] It is an error to use the ‘?’ expression, expression statements starting with ‘!’ and assert statements in PGL programs which are used to generate patterns.
[8641] Connecting in Parallel
[8642] If it is desired to connect the Waveform Analyzer to ports that are connected to another simulation, this may be done using the DK1Share.dll. interface bus_out() seg7_output(unsigned 7 output1 = encode_out) with {extlib=“DK1Share.d11”, extinst=“ \ Share={extlib=<7segment.d11>, extinst=<A>, extfunc=<PlugInSet>} \ Share={extlib=<DK1Connect.d11>, extinst=<SS(7)>, extfunc=<DK1ConnectGetSet>} \ ”, extfunc=“DK1ShareGetSet” };
EXAMPLE
[8643] This example uses DK1Share.dll to share the output port seg7_output.output1 between the 7-segment display (connected to terminal A) and DK1Connect (connected to terminal SS(7) ). A user can then trace the output going to the 7-segment display by using SS(7) as the expression in the Trace properties window
[8644] Finding a Sequence of Data in a Trace or Pattern
[8645] To find a sequence of data, the window that contains the trace or pattern to be searched is activated. If there are multiple traces or patterns in the window, the desired trace or pattern is selected. The Edit>Find menu item is selected. A PGL statement or function is entered in the ‘Find what:’ box in the Find dialog.
[8646] Generating Patterns
[8647] Generating a pattern from an Existing Trace or Pattern
[8648] Data is copied from a trace or pattern into the clipboard, and then the contents of the clipboard are pasted into a pattern. A region of a trace or pattern is selected, such as by dragging the mouse pointer over the region to select it. The region is copied to the clipboard by selecting Copy from the Edit menu or with the Copy icon on the toolbar. A pattern window is activated and either a region to paste over or a cursor is selected. Paste is selected from the Edit menu or the Paste icon on the toolbar is clicked on.
[8649] If a region has been selected, the clipboard contents are pasted into the selected pattern starting at the beginning of the selected region. If a cursor was selected, the clipboard contents are pasted into the window starting at the selected cursor location.
[8650] Generating a Pattern from a PGL Statement:
[8651] Script is selected as the pattern source in the Pattern Properties dialog. The PGL statement or function call is entered in the box to the right of the button.
[8652] Generating a Pattern from a File:
[8653] File is selected as the pattern source in the Pattern Properties dialog. The filename is entered in the box to the right of the button. The Browse button is used to browse for a file.
[8654] Pattern Generation Limitations
[8655] It is an error to use the ‘?’ expression, expression statements starting with ‘!’ and assert statements in PGL programs which are used to generate patterns.
[8656] Complex Pattern-Generation
[8657] More complex patterns may require using a separate Handel-C program to perform pattern generation.
[8658] Measuring Time and Value Differences in Windows
[8659] The user can measure the time between two events and the difference in the value of a signal at two different times by placing marks in Trace and Pattern Windows. These marks are represented by colored triangles and may be referred to as cursors. One cursor is always selected.
[8660] The cursor triangles are placed in the time pane of the trace or pattern window. If there is more than one cursor in the time pane, the time pane displays the differences in time between cursors. The bottom-centre pane displays the absolute position in time of all cursors. The differences in values between the cursors are displayed in the bottom-left pane.
[8661] If multiple traces or patterns are displayed in a window, the values given are those of the selected trace or pattern.
[8662] Creating Cursors
[8663] Click on the New cursor icon on the toolbar or select New Cursor from the View menu. The cursor may be added to the center of the time pane of the active trace or pattern window.
[8664] Moving Cursors
[8665] Drag the cursor across the time pane
[8666] Selecting Cursors
[8667] Double-click a cursor. A red bar may appear beneath it to show that it is selected. By default, the first cursor created is the selected cursor. Only one cursor can be selected at a time.
[8668] Deleting Cursors
[8669] Select the cursor to be deleted. Click the Delete Cursor icon on the toolbar or select Delete Cursor from the View menu.
[8670] Connecting a Pattern to a Port
[8671] To connect a pattern to a port, the following steps are performed:
[8672] 1. write and compile Handel-C code to connect a Handel-C port to a terminal using the DK1Connect and the DK1Sync plugins.
[8673] 2. set up a pattern window in the analyzer generating a signal to the named terminal.
[8674] 3. simulate the Handel-C code and start transmitting the pattern
[8675] Writing the Handel-C Program
[8676] To write a program in Handel-C, open Handel-C, create a new project and enter the following program: set clock = external “P1” with {extlib = “DK1Sync.d11”, extinst = “50”, extfunc = “DK1SyncGetSet”}; interface bus_in(unsigned 1 in) ib1 () with {extlib = “DK1Connect.d11”, extinst = “t(1)”, extfunc = “DK1ConnectGetSet”}; unsigned 5 count = 0; void main(void) { while(!count[4] || !count[2]) { if (ib1.in == 0) { delay; if (ib1.in == 1) count++; } else delay; } }
[8677] }
[8678] Note: this program uses the DK1Connect plugin to connect the port ib1.in to the terminal t(1). The program may only terminate when it has detected 20 rising edges from the port ib1.in.
[8679] Set Up a Pattern Window
[8680] To set up a pattern window, the following general steps are performed:
[8681] 1. Open Waveform Analyzer.
[8682] 2. In Waveform Analyzer, select New from the File menu and create a new pattern with a filename, with 40 as the number of points and 50 as the clock period.
[8683] 3. An empty Pattern window appears. Select New Pattern from the Pattern menu or from the toolbar and enter the following properties in the dialog box. Note Table 33. TABLE 33 Name: test pattern Width: 1 Type: Unsigned Source: Select Script radio button. Enter loop(20) {0; 1;} in the box. Variable: Grayed out. Destination: t(1) Trigger: Leave box blank. Other settings should be grayed out. Delay: Grayed out with 0 as default Display: Check Stepped Waveform radio button 4. Click OK.
[8684] Start Transmission
[8685] To start the transmission, tun the Handel-C simulation. Start transmission by clicking the Run icon on the toolbar, or by selecting Run from the Capture menu. The Handel-C program should terminate shortly after transmission is started. To stop capturing click on the stop icon on the toolbar or select Stop from the Capture menu.
[8686] Starting the Waveform Analyzer
[8687] To start the Waveform Analyzer:
[8688] Select Start>Programs>DK1 Design Suite>Waveform Analyzer or,
[8689] Double-click the icon for the analyzer.exe file in the DK1\Bin directory.
[8690] Connecting a Simulation to a Trace
[8691] To connect a simulation to a trace:
[8692] 1. write and compile Handel-C code to connect a Handel-C port to a terminal using the DK1Connect and the DK1Sync plugins.
[8693] 2. set up a trace window in the analyzer which reads the signal from the named terminal.
[8694] 3. simulate the Handel-C code and start capturing
[8695] Sample Handel-C Program
[8696] set clock =external “P1”
[8697] with {extlib =“DK1Sync.dll”, extinst =“50”, extfunc =“DK1SyncGetSet”};
[8698] unsigned 3 x =0;
[8699] interface bus_out( ) ob1(unsigned 3 out =x)
[8700] with {extlib =“DK1Connect.dll”, extinst =“t(3)”, extfunc =“DK1ConnectGetSet”}; set clock = external “P1” with {extlib = “DK1Sync.d11”, extinst = “50”, extfunc = “DK1SyncGetSet”}; unsigned 3 x = 0; interface bus_out() ob1 (unsigned 3 out = x) with {extlib = “DK1Connect.d11”, extinst = “t(3)”, extfunc = “DK1ConnectGetSet”}; void main(void) { while(1) x++; }
[8701] Note: this program uses the DK1 Connect plugin to connect the port ob1.out to the terminal t(3 ). Compile the program but do not run it.
[8702] Set Up a Trace Window
[8703] To set up a trace window, open Waveform Analyzer. In Waveform Analyzer, select New from the File menu and create a new trace. Select the browse button to specify a filename and location. Set Default Clock Period to 50 and Default No. points to 40.
[8704] An empty Trace window should appear. Select New Trace from the Trace menu or from the toolbar and enter the following properties in the dialog box. Note Table 34. TABLE 34 Name: test trace Width: 3 Type: Unsigned Expression: t(3) Dump File: Leave blank Variable: Grayed out Trigger: Leave box blank. Other settings should be grayed out. Delay: Grayed out with 0 as default Display: Check the Stepped Waveform radio button. Click OK.
[8705] Start Capturing
[8706] Start capturing by clicking the Run icon on the toolbar, or by selecting Run from the Capture menu. A red dashed line should appear jumping around all over the place). This line marks the current position in the trace. Run the Handel-C simulation. To stop capturing click on the stop button on the toolbar or select Stop from the Capture menu. The Handel-C simulation is stopped.
[8707] Using the Pattern Generation Language
[8708] The Pattern Generation Language (PGL) can be used to:
[8709] Generate patterns that are fed into a port
[8710] Identify a sequence of data in a trace to use as a trigger. The trigger can be used to start recording the trace or to start generating a pattern. If a trigger associated with a trace or pattern has been defined, it may be re-used as a trigger for other traces or patterns.
[8711] Find a sequence of data in a trace or a pattern
[8712] Entering PGL Statements
[8713] PGL is entered as a single PGL statement in the properties dialog for a trace or pattern. The PGL statement may be a compound statement or a function call. PGL functions may be written in the script.pg1 file associated with a project.
[8714] Complex Pattern-Matching and Pattern-Generation
[8715] A separate Handel-C program can be written to perform pattern generation or pattern matching. For triggering, a trigger signal can be output from this Handel-C program to Waveform Analyzer, and then a simple PGL statement can be used to trigger on this signal.
[8716] Using Triggers
[8717] A sequence of data to be used as a trigger can be specified. Alternatively, an existing specification canbe used.
[8718] When the trigger sequence occurs, the following are enabled:
[8719] Start capturing a trace before, at or after the specified trigger
[8720] Start generating a pattern at or after the specified trigger
[8721] Stop capturing a trace or generating a pattern.
[8722] To Specify a Trigger:
[8723] Open the Pattern or Trace Properties dialog. Enter trace name: in the Trigger box followed by a PGL statement. trace name is the name of a pre-defined trace (Note that it may be followed by a colon). The PGL statement may be matched against the named trace. For example:
[8724] b : {0;1;}
[8725] would cause the pattern to be generated on a rising edge of trace b. The appropriate radio button is selected. Radio buttons include those set forth in Table 35. TABLE 35 No trigger: No triggering Single: Transmit or capture the first time the trigger is received Auto: Transmit or capture each time the trigger is received.
[8726] To re-use a specified trigger, ″name is entered in the Trigger box, where name is the name of the trace or pattern that uses a trigger. Note that name may be preceded by a double-quote. For example:
[8727] ″trace1
[8728] would cause the trace or pattern whose details are being entered to use the same trigger as the trace named trace1. The appropriate radio button is selected. Note Table 36. TABLE 36 No trigger: No triggering Single: Transmit or capture the first time the trigger is received Auto: Transmit or capture each time the trigger is received.
[8729] To Specify the Delay Between the Trigger and the Action
[8730] Specify a trigger and enter the number of time units in the Delay box on the Properties dialog. The delay is in the time units for that window. Delays can be positive or negative for a trace, (negative delays capture before the trigger, positive after) and positive or zero for a pattern.
[8731] To Pause on Trigger
[8732] Specify a trigger and check the Pause box.
[8733] File Formats
[8734] A preferred embodiment of the Waveform Analyzer supports two different file formats for storing waveform data. These can include, for example ASCII files, where data elements are written in ASCII and separated by whitespace; and Value Change Dump (VCD) files. This file format is specified in the IEEE 1364 standard.
[8735] A VCD file can contain any number of variables. If several traces are dumped to the same VCD file, simply enter the same VCD filename in the ‘Dump File’ box for every trace which should be written to that file. The ‘Variable’ box in the Trace dialog is used to enter a reference name which may be used in the VCD file for the signal.
[8736] When reading a pattern from a VCD file, the ‘Variable’ box in the Pattern dialog is used to enter the reference name of the variable in the VCD file which needs to be read. The file extension of a Dump File or Pattern source file determines the file format. If the extension is ‘.VCD’, ‘.DMP’ or ‘.DUMP’ the file is a Value Change Dump file, otherwise it is an ASCII file.
[8737] Pattern Generation Language Syntax
[8738] The following are syntax statements used during programming: subprogram_def : := identifier ( [parameter-list] ) compound-statement parameter-list : := identifier | identifier , parameter-list statements : := statement | statement statements statement : := subprogram_call | compound-statement | loop-statement | if-statement | if-else-statement | switch-statement | break-statement | expression-statement | assert-statement subprogram_call : := identifier ( [expression-parameter-list] ) ; expression-parameter-list : := expression | expression , expression-parameter-list compound-statement : := { statements } loop-statement : := loop ( expression ) statement | loop forever statement if-statement : := if ( boolean-expression ) statement if-else-statement : := if ( boolean-expression ) statement else statement switch-statement : := switch ( expression ) { case-list [default : statements] } case-list : := case | case case-list case : := case number : statements break-statement : := break ; expression-statement : := expression ; | ! expression ; assert-statement : := assert ( boolean-expression ) ; boolean-expression : := expression == expression | expression != expression | expression | boolean-expression && boolean-expression | boolean-expression | | boolean-expression | ! boolean-expression | ( boolean-expression ) (here, && has higher precedence than | | and both are left associative) expression : := ? | number | identifier
[8739] Numbers may be binary, octal, decimal or hexadecimal integers, and use the same syntax as Handel-C. (i.e. 0b . . . for binary numbers, 0 . . . for octal numbers, 0x . . . for hex numbers, all other numbers are treated as decimals).
[8740] Identifiers are C-style identifiers.
[8741] Time Units
[8742] Time units are not explicitly defined in Waveform Analyzer. Any Handel-C simulation to which the Waveform Analyzer is connected should use the DK1Sync plugin with the clock period for the simulation specified in an extinst string. When the clock period is entered for a trace or pattern window, the sample rate for the trace or patterns are determined in the window relative to the clock period specified for the Handel-C simulation. If the clock period for the trace or pattern is the same as the clock period specified in the extinst string in the Handel-C program, the trace or pattern may be sampled on every cycle of the Handel-C program. If the clock period for the trace or pattern is twice the clock period specified in the extinst string in the Handel-C program, the trace or pattern may be sampled on every other cycle of the Handel-C program and so on. It is a matter of convenience to make the clock periods correspond to the clock periods that may be used in the target hardware. Preferably, the VCD file reader/writer used by Waveform Analyzer assumes that the time units used are nanoseconds.
[8743] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
What is claimed is:
1. A method for using a dynamic object in a programming language, comprising the steps of: (a) defining an object with an associated first value and second value; (b) using the first value in association with the object during a predetermined clock cycle; and (c) using the second value in association with the object before or after the predetermined clock cycle.
2. A method as recited in claim 1, wherein the object is used to split up an expression into sub-expressions.
3. A method as recited in claim 2, wherein the sub-expressions are reused.
4. A method as recited in claim 1, wherein the first value is assigned to and read from the object during the predetermined clock cycle.
5. A method as recited in claim 1, wherein the programming language is adapted for programming a gate array.
6. A method as recited in claim 1, wherein the programming language includes Handel-C.
7. A computer program product for using a dynamic object in a programming language, comprising: (a) computer code for defining an object with an associated first value and second value; (b) computer code for using the first value in association with the object during a predetermined clock cycle; and (c) computer code for using the second value in association with the object before or after the predetermined clock cycle.
8. A computer program product as recited in claim 7, wherein the object is used to split up an expression into sub-expressions.
9. A computer program product as recited in claim 8, wherein the sub-expressions are reused.
10. A computer program product as recited in claim 7, wherein the first value is assigned to and read from the object during the predetermined clock cycle.
11. A computer program product as recited in claim 7, wherein the programming language is adapted for programming a gate array.
12. A computer program product as recited in claim 7, wherein the programming language includes Handel-C.
13. A system for using a dynamic object in a programming language, comprising: (a) logic for defining an object with an associated first value and second value; (b) logic for using the first value in association with the object during a predetermined clock cycle; and (c) logic for using the second value in association with the object before or after the predetermined clock cycle.
14. A system as recited in claim 13, wherein the object is used to split up an expression into sub-expressions.
15. A system as recited in claim 14, wherein the sub-expressions are reused.
16. A system as recited in claim 13, wherein the first value is assigned to and read from the object during the predetermined clock cycle.
17. A system as recited in claim 13, wherein the programming language is adapted for programming a gate array.
18. A system as recited in claim 13, wherein the programming language includes Handel-C.
|
User:PlatinumLink
Welcome to my User Page!
Activity: I am most active from around 4:30pm to 10:00pm
Level: Level 16
Current Gear:
Barnsquids: I am awaiting a Barnsquid! (Hopefully!)
Favorite Weapon[s]:
|
<?php
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;
class CreateClassesTable extends Migration
{
/**
* Run the migrations.
*
* @return void
*/
public function up()
{
Schema::create('klasses', function (Blueprint $table) {
$table->id();
$table->foreignId('user_id')->constrained()->onDelete('cascade');
$table->string('section');
$table->string('subject_code');
$table->string('subject_description');
$table->dateTime('end_date');
$table->timestamps();
});
}
/**
* Reverse the migrations.
*
* @return void
*/
public function down()
{
Schema::dropIfExists('klasses');
}
}
|
Set up basic landing page
Modify the dashboard for items specific to the user, and their decks.
Ideas:
Show high level list of decks in categories of MTG format (Standard, Legacy, EDH...)
The shell is here: https://github.com/sleeveup/sleeveup-app/issues, but content needs to be fleshed out.
|
Is there any way to tell if an SD card has been used?
I ordered a “new” micro SD card from Amazon Marketplace. However, it was sent in a small cheap plastic bag instead of the original package. I put it into my PC and found it to be empty but formatted.
Do SD cards normally come formatted out of the box? Does that mean it was already used? If not, is there any method to tell if it was used?
I don’t really mind as long as it works properly, but I don’t think it is OK to list something as “new” in Amazon although if it isn’t.
Did you buy it from Amazon itself or from one of their (many) “associates”? If you bought it from an associate, then it is effectively no different than buying from someone on eBay (a lot of Chinese sellers on eBay will ship the item without its packaging so that they can offer free shipping). In that case, it could be in any condition, though of course the description should be accurate. If you bought it from Amazon itself, then you may consider exchanging it.
Memory cards and flash drives do usually come formated as FAT32. That said, if you have not written to it yet, you could use a hex-editor like HxD to open the drive and examine it at a low level to see if there is any residual data on it (simply deleting or quick-formatting does not remove the actual data). Of course even then, the drive being filled with 0’s does not really disprove it’s previous use (by a user, obviously the factor will have “used” it during manufacture).
The best way to check a memory card or flash-drive for previous use is to closely examine the pins to see if there is evidence of it having been inserted. Obviously you can only do this before inserting it yourself.
(Whenever I buy something online, used or not, I have someone grab the camera and record a video of me opening the package for the first time and examining it, so that I have proof should I need it.)
The most likely case if it's an associate is that it's new but counterfeit. I'm not sure how that falls under your "I don’t really mind as long as it works properly" scale, but I would not be pleased.
Unless it’s a terrific counterfeit, then it would probably be easy to tell by looking for small markings and such (fakes usually don’t bother with extra work). Whether or not it is reliable depends on whether it had free shipping or not and what the associate’s feedback ratings are.
The counterfeit cards are usually modified to report more capacity than they actually have. You need a program like H2testw to make sure this is not the case.
Who said anything about counterfeits? The OP was just asking if there is a way to tell if it is used or not. I didn’t realize that tin-foil hats had come back in fashion.
@H2testw: Thanks for the tip, I will check that!
@smackfu: this is also a good point. The micro SD card is already tiny and I don't think I can tell if it's fake without using a magnifier. But the seller is in Switzerland (they don't usually tolerate such things in Europe) and it has 100% five stars from 61 buyers. So I don't think it would sell counterfeits. I was only concerned if it could be used. Thanks for all answers BTW.
@Synetech: I know what the OP was asking, but my experience is that any card not bought directly from Amazon is very likely to be counterfeit (like any card you buy on eBay). It is advisable to check the card as soon as possible so you can pursue some resolution with your payment processor.
Don't be too concerned about the packaging. Many products sold in bulk or as OEM or as budget level forgo any fancy packaging as part of lowering the price of the product. This is especially true of electronics and computer products. It should not usually be considered relevant to whether or not a product is new (although sometimes it is an obvious sign).
I think file recovery software can help you to find out if used or not. Run the recovery software and see if any erased files exist. The manufaturer may wish to comment if you contact them directly
Most SD cards do come pre-formatted. Assuming there was a previous user, if they only did a quick format, then the file table was wiped but not that actual data, meaning that just about any forensic toolkit (e.g. Encase or FTK) will be able to tell you if there's anything there. However, if they did a full format, then there is no publicly known method for determining whether there was previously data there or not.
Though I appreciate it's not a clear answer to your question (on www.seagate.com you can download a free file recovery utility that will show you things you wouldn't believe exist on all your drives - then, if you wanted to retrieve the data, you have to buy a license but chances are you will want to clean rather than retrieve the corruption).
For cleaning / wiping a SD card, I've been reliably led to believe the official formatting utility available for free on www.sdcard.org > Downloads (Windows and Mac only) is the best utility. You'll want to select the "long" format / overwrite option, of course.
I think common-sense suggests your gut instinct is correct, in this instance. I'm not sure what the comment about OEM packaging is referencing. I've bought many products packaged for OEM, and whilst the packaging lacks the 'frills'...it's still going to be packaged.
|
Minecraft Dungeons:Twin Bow
"The Twin Bow is the champion of the hero who finds themselves outnumbered and alone."
- In-game description
Obtaining
* Missions
* (Adventure)
* (DLC)
* (DLC)
* (DLC)
* (DLC)
* Merchants
* Ancients
Usage
Properties
* X ranged damage
* Shoots two enemies at once ( tier I)
Stats
* Multiplier: 1-2.5
* Quiver: 80
Others
de:MCD:Zwillingsbogen zh:MCD:双子弓
|
using UnityEngine;
using System.Collections.Generic;
using BansheeGz.BGSpline.Curve;
using UnityEditor;
namespace BansheeGz.BGSpline.Editor
{
public class BGSceneViewOverlayPointInsert : BGSceneViewOverlayPointAdd
{
private const float DistanceToleranceSquared = .008f;
private static readonly float DistanceTolerance = Mathf.Sqrt(DistanceToleranceSquared) * 2;
private static readonly Color32 PointersColor = Color.red;
private static readonly List<int> SectionIndexes = new List<int>();
private Vector3 intersectPosition;
private float splineIntersectionDistance;
private int pointIndex;
public BGSceneViewOverlayPointInsert(BGSceneViewOverlay overlay) : base(overlay)
{
}
protected override bool VisualizingSections
{
get { return false; }
}
protected override bool ShowingDistance
{
get { return false; }
}
public override string Name
{
get { return "Insert Point"; }
}
protected override BGCurvePoint CreatePointForPreview(Vector3 position, BGCurve curve, out float toLast, out float toFirst, BGCurveSettings settings)
{
toLast = toFirst = 0;
return CreatePoint(curve, settings);
}
protected override void AddPoint(BGCurve curve, Vector3 intersectionPosition, BGCurveSettings settings)
{
BGCurveEditor.AddPoint(curve, CreatePoint(curve, settings), pointIndex + 1);
}
private BGCurvePoint CreatePoint(BGCurve curve, BGCurveSettings settings)
{
var math = overlay.Editor.Editor.Math;
var from = curve[pointIndex];
var to = pointIndex == curve.PointsCount -1 ? curve[0] : curve[pointIndex + 1];
var ratio = (splineIntersectionDistance - math[pointIndex].DistanceFromStartToOrigin)/math[pointIndex].Distance;
var tangent = BGEditorUtility.CalculateTangent(@from, to, ratio);
var point = BGNewPointPositionManager.CreatePointBetween(curve, @from, to, settings.Sections, settings.ControlType, intersectPosition, tangent);
return point;
}
protected override void Animate(BGTransition.SwayTransition swayTransition, Vector3 point, float distanceToCamera, Plane plane)
{
var verts = GetVertsByPlaneAndDistance(new Vector3(swayTransition.Value, swayTransition.Value, swayTransition.Value), point, distanceToCamera, plane);
var size = swayTransition.Value*ScalePreviewPoint*distanceToCamera/5;
BGEditorUtility.SwapHandlesColor(PointersColor, () =>
{
foreach (var position in verts)
{
#if UNITY_5_6_OR_NEWER
Handles.ConeHandleCap(0, position, Quaternion.LookRotation(point - position), size, EventType.Repaint);
#else
Handles.ConeCap(0, position, Quaternion.LookRotation(point - position), size);
#endif
}
});
}
protected override void Cast(Event @event, Ray ray, out Vector3 position, out string error, out Plane plane)
{
position = intersectPosition;
error = null;
plane = new Plane(ray.direction.normalized, position);
}
protected override bool Comply(Event currentEvent)
{
//comply is called at the very beginning, so we calculate required data here
return CalculateIntersection(HandleUtility.GUIPointToWorldRay(currentEvent.mousePosition));
}
private bool CalculateIntersection(Ray ray)
{
splineIntersectionDistance = -1;
var curve = overlay.Editor.Curve;
var pointsCount = curve.PointsCount;
if (pointsCount < 2) return false;
var math = overlay.Editor.Editor.Math;
// bbox intersection check
SectionIndexes.Clear();
for (var i = 0; i < math.SectionsCount; i++)
{
var bbox = math.GetBoundingBox(i, math[i]);
var bboxExtents = bbox.extents;
if (bboxExtents.x < DistanceTolerance) bbox.extents = new Vector3(DistanceTolerance, bbox.extents.y, bbox.extents.z);
if (bboxExtents.y < DistanceTolerance) bbox.extents = new Vector3(bbox.extents.x, DistanceTolerance, bbox.extents.z);
if (bboxExtents.z < DistanceTolerance) bbox.extents = new Vector3(bbox.extents.x, bbox.extents.y, DistanceTolerance);
if (bbox.IntersectRay(ray)) SectionIndexes.Add(i);
}
if (SectionIndexes.Count == 0) return false;
// line to line distance
var minDistanceSqrt = float.MaxValue;
foreach (var sectionIndex in SectionIndexes)
{
var section = math[sectionIndex];
var points = section.Points;
var sectionPointsCount = section.PointsCount;
for (var j = 0; j < sectionPointsCount - 1; j++)
{
var from = points[j];
var to = points[j + 1];
Vector3 point1, point2;
var toFrom = (to.Position - @from.Position);
//closest points on 2 lines
if (!ClosestPointsOnTwoLines(out point1, out point2, @from.Position, toFrom.normalized, ray.origin, ray.direction)) continue;
//ensure the point lay on the segment of the line
if (PointOnWhichSideOfLineSegment(@from.Position, to.Position, ProjectPointOnLine(@from.Position, toFrom.normalized, point1)) != 0) continue;
var sqrtDistance = Vector3.SqrMagnitude(point2 - point1);
if (sqrtDistance > DistanceToleranceSquared || sqrtDistance > minDistanceSqrt) continue;
minDistanceSqrt = sqrtDistance;
splineIntersectionDistance = @from.DistanceToSectionStart + section.DistanceFromStartToOrigin + Vector3.Distance(@from.Position, point1);
intersectPosition = point1;
pointIndex = sectionIndex;
}
}
SectionIndexes.Clear();
return splineIntersectionDistance >= 0;
}
// the original code: http://wiki.unity3d.com/index.php/3d_Math_functions
//Two non-parallel lines which may or may not touch each other have a point on each line which are closest
//to each other. This function finds those two points. If the lines are not parallel, the function
//outputs true, otherwise false.
private static bool ClosestPointsOnTwoLines(out Vector3 closestPointLine1, out Vector3 closestPointLine2, Vector3 linePoint1, Vector3 lineVec1, Vector3 linePoint2, Vector3 lineVec2)
{
closestPointLine1 = Vector3.zero;
closestPointLine2 = Vector3.zero;
// float a = Vector3.Dot(lineVec1, lineVec1);
float b = Vector3.Dot(lineVec1, lineVec2);
// float e = Vector3.Dot(lineVec2, lineVec2);
float d = 1 - b*b;
//lines are not parallel
if (d != 0.0f)
{
Vector3 r = linePoint1 - linePoint2;
float c = Vector3.Dot(lineVec1, r);
float f = Vector3.Dot(lineVec2, r);
float s = (b*f - c)/d;
float t = (f - c*b)/d;
closestPointLine1 = linePoint1 + lineVec1*s;
closestPointLine2 = linePoint2 + lineVec2*t;
return true;
}
return false;
}
//This function returns a point which is a projection from a point to a line.
//The line is regarded infinite. If the line is finite, use ProjectPointOnLineSegment() instead.
public static Vector3 ProjectPointOnLine(Vector3 linePoint, Vector3 lineVec, Vector3 point)
{
//get vector from point on line to point in space
Vector3 linePointToPoint = point - linePoint;
float t = Vector3.Dot(linePointToPoint, lineVec);
return linePoint + lineVec*t;
}
//This function finds out on which side of a line segment the point is located.
//The point is assumed to be on a line created by linePoint1 and linePoint2. If the point is not on
//the line segment, project it on the line using ProjectPointOnLine() first.
//Returns 0 if point is on the line segment.
//Returns 1 if point is outside of the line segment and located on the side of linePoint1.
//Returns 2 if point is outside of the line segment and located on the side of linePoint2.
public static int PointOnWhichSideOfLineSegment(Vector3 linePoint1, Vector3 linePoint2, Vector3 point)
{
Vector3 lineVec = linePoint2 - linePoint1;
Vector3 pointVec = point - linePoint1;
float dot = Vector3.Dot(pointVec, lineVec);
//point is on side of linePoint2, compared to linePoint1
if (dot > 0)
{
//point is on the line segment
if (pointVec.magnitude <= lineVec.magnitude)
{
return 0;
}
//point is not on the line segment and it is on the side of linePoint2
return 2;
}
//Point is not on side of linePoint2, compared to linePoint1.
//Point is not on the line segment and it is on the side of linePoint1.
return 1;
}
}
}
|
Next Article in Journal
Synthesis, Characterization and Performance Evaluation of Burmese Grape (Baccaurea ramiflora) Seed Biochar for Sustainable Wastewater Treatment
Previous Article in Journal
On Sources of Damping in Water-Hammer
Order Article Reprints
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article
Unveiling Distribution, Hydrogeochemical Behavior and Environmental Risk of Chromium in Tannery Wastewater
1
Institute of Soil and Environmental Sciences, University of Agriculture Faisalabad, Faisalabad 38040, Pakistan
2
Soil and Environmental Biotechnology Division, National Institute for Biotechnology and Genetic Engineering (NIBGE), Faisalabad 38000, Pakistan
3
Department of Zoology, College of Science, King Saud University, Riyadh 11451, Saudi Arabia
4
Department of Agronomy, University of Agriculture Faisalabad, Faisalabad 38040, Pakistan
5
Department of Environmental Sciences, COMSATS University Islamabad, Vehari Campus, Vehari 61100, Pakistan
6
Fodder Research Sub-Station, Ayub Agricultural Research Institute, Faisalabad 38000, Pakistan
7
Centre for Planetary Health and Food Security, Griffith University, Nathan Campus, Brisbane, QLD 4110, Australia
8
Department of Agriculture and Fisheries, Mareeba, QLD 4880, Australia
9
Biochar Engineering Technology Research Center of Guangdong Province, School of Environmental and Chemical Engineering, Foshan University, Foshan 528000, China
*
Author to whom correspondence should be addressed.
Water 2023, 15(3), 391; https://doi.org/10.3390/w15030391
Received: 20 October 2022 / Revised: 1 January 2023 / Accepted: 12 January 2023 / Published: 18 January 2023
(This article belongs to the Section Water Quality and Contamination)
Abstract
:
Chromium (Cr)-contaminated tannery wastewater is a major environmental concern, especially in developing countries, such as Pakistan, due to its use for crop irrigation, resulting in food-chain contamination and health issues. In this study, we explored the distribution, speciation, hydrogeochemical behavior and environmental risks of Cr in tannery wastewater collected from various tanneries of Kasur district in Punjab, Pakistan. Tannery wastewater samples were taken during the summer (TWW-summer; n = 82) and winter (TWW-winter; n = 82) seasons. The results showed that high Cr concentration was observed in TWW-winter (mean: 49 ± 32 mg L−1) compared to TWW-summer (mean: 15 ± 21 mg L−1). In TWW-summer and TWW-winter samples, the Cr concentration exceeded the National Environmental Quality Standard (1 mg L−1), with the total Cr ranging from 2.8 to 125 mg L−1. Hexavalent Cr (Cr(VI)) and trivalent Cr (Cr(III)) concentrations spanned 2.7 to 2.9 and 12.4 to 46 mg L−1, respectively. The Piper plot showed that hydrogeochemistry of wastewater was dominated by Ca-Mg-SO4 and Ca-Mg-Cl type water, and geochemical modeling indicated that the presence of Cr-iron (Fe)-bearing mineral phases—notably, FeCr2O4, MgCr2O4 and Cr(OH)3) may control the fate of Cr in the tannery wastewater. Environmental risk assessment modeling categorized the tannery wastewater as the ‘worst quality’, which is not fit for use in crop irrigation without treatment. This study highlights that immediate monitoring, remediation and mitigation strategies are required to reduce the risk of Cr exposure from tannery wastewater in many areas of Pakistan.
1. Introduction
Rapid industrialization and urbanization have drastically enhanced the production of wastewater containing various contaminants, including the potentially toxic elements (PTEs) [1,2,3,4], such as chromium (Cr), mercury (Hg), nickel (Ni), lead (Pb), zinc (Zn), copper (Cu), iron (Fe) and cadmium (Cd). These PTEs can cause severe environmental and human health issues, thus, becoming a major concern globally [5,6,7]. Among various PTEs, Cr is a highly toxic and carcinogenic metal and is used in different industries, including textile, Cr plating, refractories and particularly in the leather tanning industry [8].
Given the toxic and mobile nature of Cr, the maximum permissible limit of total Cr in wastewater has been set at 0.05 mg L−1 by the World Health Organization (WHO). The International Agency for Research on Cancer (IARC) has classified hexavalent Cr (Cr(VI)) as a Group-I human carcinogen [9]. Crop irrigation with wastewater containing PTEs is a common practice in developing countries, such as Pakistan, because it also has important nutrients, such as nitrogen and phosphorus [10,11,12,13].
Chromium-induced environmental and health hazards depend on its speciation and bioavailability. The most common Cr species are trivalent Cr (Cr(III)) and Cr(VI), which exist in water and soil environments [14]. The oxidation and reduction of Cr in water depend on the pH, redox potential (Eh) and presence of redox coupling agents, such as ferrous iron (Fe(II)), sulfide (S2−) and organic carbon. The Fe(II) and S2− may reduce Cr(VI) into Cr(III), while Cr(III) oxidizes into Cr(VI) by oxidizing agents, such as manganese oxide (MnO2), hydrogen per oxide (H2O2) and dissolved oxygen (DO) [15,16].
Previous research has examined the fate of Cr by examining the oxidation and reduction of Cr-bearing minerals or precipitation/dissolution of Cr under varying redox potential and pH. The dissolution/precipitation of Fe-bearing minerals, such as pyrite (FeS2), mackinawite (FeS1−x), hematite (Fe2O3), goethite and magnetite (Fe3O4), present in wastewater and in subsurface systems may control the hydrogeochemical behavior and fate of Cr in tannery wastewater [17,18,19].
Previous research has been conducted to determine water quality attributes and Cr concentration in tannery wastewater, although it has not been directed to examine the hydrogeochemistry and fate of Cr in tannery wastewater [20,21,22,23,24,25]. Afzal, Shabir, Iqbal, Mustafa, Khan and Khalid [26] determined the aquatic chemistry of groundwater in Punjab, Pakistan and reported a high concentration of Cr (0.82–2.25 mg L−1), which was possibly due to the discharge of Cr-contaminated wastewater from the surrounding leather tanning industry in the area. Joyia, Ashraf, Shafiq, Anwar, Nisa, Khaliq and Malik [27] reported a high concentration (72 mg L−1) of Cr in tannery wastewater produced from various tannery industries of Harappa in Punjab, Pakistan. Most of the earlier research assessed the hydrogeochemistry of groundwater mainly contaminated with arsenic and fluoride and not wastewater, employing analytical and multivariate statistical tools.
While poorly understood, we investigated Cr distribution, speciation and assessed Cr-mediated environmental risk, using geochemical and multivariate tools to determine the fate of Cr in tannery wastewater. Moreover, the (hydro)geochemical behavior of Cr in wastewater was examined in the summer (TWW-summer) and winter (TWW-winter) seasons.
2. Materials and Methods
2.1. Description of the Study Area
Tannery wastewater samples (n = 82 in summer and winter each) were collected from Kasur in Punjab, Pakistan (Figure S1, Supplementary Information). Leather tanning has a long-standing tradition in Kasur district (Table S1, Supplementary Information) of Punjab, which is known as the biggest tannery industrial city in Pakistan [28]. The climate is comparatively cold in winter but hot in summer. In the months of May and June, the mean temperature may rise to 44 °C. The average annual rain of Kasur is 500 mm [29].
In Kasur, leather tanning is the most important industry where more than 300 active individual tanning industrial units are located. As a result of tanning activities, about 150 t solid waste and 13,000 m3 of Cr-contaminated tannery wastewater are discharged on a daily basis to main water bodies and land, thus, contaminating the environment in the area and causing serious health hazards to humans and animals [30].
2.2. Tannery Wastewater Sampling
Tannery wastewater sampling points were selected considering their spatial distribution in different tanneries to represent major tannery areas with potential Cr-contamination in TWW-summer and TWW-winter samples. Wastewater was taken from 21 different tanneries during summer and winter seasons. Wastewater samples were collected in two replicates from each tannery wastewater site. The water samples were taken at a high loading rate during both seasons, although examining the impact of the loading rate was beyond the scope of the current study.
A total of 82 samples were taken in summer and 82 in winter from 21 different tanneries. In the summer season, tannery wastewater samples were collected in May 2018 and in winter season samples were collected in January 2019. Wastewater samples (250 mL each) were collected in clean plastic bottles and analyzed for the total Cr, iron (Fe), manganese (Mn), chemical oxygen demand (COD), biological oxygen demand (BOD), cations and anions.
Tannery wastewater was divided in two sets: (i) acidified with concentrated nitric acid (HNO3) to bring the pH < 2 and used for Cr and major elemental analysis, and (ii) non-acidified to determine ions and other wastewater quality attributes. All the tannery wastewater samples were stored in a refrigerator at <4 °C prior to various physicochemical analyses.
During the collection of wastewater samples, various chemical and physical parameters, such as the pH, electrical conductivity (EC), redox potential (Eh), total dissolved solids (TDS) and dissolved oxygen (DO), were measured at the sampling time. The Eh, pH EC, TDS and DO of tannery wastewater samples were determined using a portable redox meter (Model 8424, Hanna, USA), pH meter (ST 300, Ohaus-USA), DO meter (model ST300, OHAUS, USA) and EC/TDS meter (Model 3100, OHAUS, USA), respectively.
The total Cr in wastewater was determined using a flame atomic absorption spectrometer (FAAS; Thermo-AA®, Solar Series, USA) at a 357.9 nm wavelength. The Cr(VI) in wastewater was determined using the 1,5-diphenylcarbazide (DPC) method at 540 nm using an UV-Visible Spectrophotometer (Lambda 25, Perkin Elmer, AA solar-series, USA) (APHA 2005). The concentration of Cr(III) was calculated by taking the difference between the total Cr and Cr(VI) in wastewater.
The Mn and Fe concentrations were analyzed using a FAAS. Concentrations of calcium (Ca), potassium (K) and sodium (Na) in the tannery wastewater were determined using a flame photometer (BWB Model BWB-XP, 5 Channel Flame Photometer, England). The analytical wavelengths of 589.0 nm (Na), 422.7 nm (Ca) and 766.5 nm (K) were used for analysis of these elements. The Ca and Mg hardness were determined using the standard titration method as described [31].
The sulfate (SO4) in wastewater was determined following the barium sulfate (BaSO4) precipitation method. A 1 N solution of barium chloride (BaCl2) was prepared and added into wastewater samples and then allowed to precipitate SO4–S as BaSO4 following the method described elsewhere [32]. The concentrations of carbonate (CO32−), bicarbonate (HCO3) and chloride (Cl) were determined according to the method described by Estefan et al. (2013). The concentration of COD and BOD in tannery wastewater was analyzed according to the standard methods described by Saritha, Chockalingam and BIST [33].
2.3. Environmental Risk Assessment of Chromium-Bearing Wastewater
The comprehensive contamination index (CCI) and single-factor evaluation index (SFEI) were used to measure the wastewater quality and potential risk. The SFEI used to examine the contribution of every single water attribute to water contamination and CCI was used to assess the contributions of all the measured parameters in wastewater.
For this purpose, the National Environmental Quality Standards [34] of Pakistan were used to calculate the surface water quality attributes; and the United States Environmental Protection Agency and WHO standards were used to calculate the SFEI and CCI values [35].
The SFEI and CCI were computed by using Equations (1) and (2), respectively.
SFEI = Mi / Si
CCI = 1 / n i = 1 n Mi / Si
where Mi is the measured concentration of each parameter, Si is the corresponding maximum/environmental quality standard of surface water, and n is the total number of parameters.
The computed results by SFEI were interpreted as SFEI value < 1, the water quality meets the standards. If SFEI value > 1, the water quality exceeded the surface water quality standards. Based on the CCI value, the water quality was classified into five categories: (i) CCI is 0–0.20 (clean water), (ii) CCI is 0.21–0.40 (sub-clean), (iii) CCI is 0.41–1.00 (slightly contaminated), (iv) CCI is 1.0–2.00 (medium contamination) and (v) CCI is >2.01, highly contaminated. The heavy metal evaluation index (HEI) was used to determine the overall water quality concerning metal contamination.
The HEI was computed using Equation (3):
HEI = i = 1 n Hc / Hmax
where Hc is the measured value, and Hmax is the maximum permissible limit of each trace metal.
Based on the computed value of HEI, there are three levels of contamination: (i) HEI > 20, high contamination, (ii) HEI 10–20, medium contamination and (iii) HEI < 10, low contamination [35].
2.4. Quality Control and Analytical Precision
Quality assurance and quality control protocol was followed to ensure data reliability and analytical accuracy. After every 10 samples, a reference sample with a known total Cr or Cr(VI) concentration was run on the FAAS or UV-visible spectrophotometer, respectively, to check the analytical precision and accuracy. The chemicals used in this research were of analytical grade. All the glassware and plastic ware were soaked in diluted HNO3 for 24 h and then washed with deionized water twice before use for analytical work.
2.5. Geochemical Modeling for Saturation Index
The saturation index (SI) values were calculated using geochemical modeling software, PHREEQC [36]. These values were used to estimate the equilibrium conditions of various mineral phases controlling the geochemistry of tannery wastewater. Based on the SI values, mineral-like phases/salts intensity can be classified into three categories: (i) SI > 0, oversaturated/precipitation, (ii) SI < 0, unsaturated/dissolution and SI = 0, equilibrium [37,38]. Geochemist Workbench software (version 9.0.8) was employed to make a Eh–pH stability diagram using the Cr and other relevant parameters data to predict Cr speciation in tannery wastewater and assess its fate in the environment.
2.6. Multivariate Analysis
The statistical analysis was performed using Excel 2016. Principle components analysis (PCA) and Pearson correlation were performed using the Minitab software®. The study area map to show the sampling sites was developed using ArcMap software version 10.4.1. The Piper plot and Durov diagram to show the wastewater type and (hydro)geochemistry were made using the Geochemist Workbench.
3. Results and Discussion
3.1. Distribution of Chromium and Speciation in Wastewater
Figure 1a shows the average concentration of Cr in tannery wastewater from summer and winter seasons collected from 21 tannery sites (hereafter referred as tannery wastewater summer (TWW-summer) and tannery wastewater winter (TWW-winter)) in the industrial zone of Kasur. A high Cr concentration was observed in TWW-winter (3.9–125 mg L−1) compared to TWW-summer (2.8–94.6 mg L−1) samples (Table 1). All the wastewater samples from summer and winter seasons exceeded the Cr concentration above the permissible limits set by the National Environmental Quality Standards (NEQS; 1 mg L−1) and WHO (0.05 mg L−1) (WHO, 1999) (Table 2) as well as the USEPA safe limit of 2.0 mg L−1 for Cr (USEPA, 2012) (Table 2) (USEPA, 2012).
Tannery wastewater samples, which were taken from the main channels receiving wastewater from all the tanneries, showed the highest Cr concentration in both TWW-winter and TWW-summer samples (up to 72 and 44 mg L−1, respectively). Among all the tanneries, tannery 2 had the highest Cr concentration (39 mg L−1) in TWW-summer and tannery 20 had the maximum Cr concentration (125 mg L−1) in the TWW-winter samples. The tannery 1 and tannery 13 samples showed the lowest Cr concentrations (2.8 and 4.0 mg L−1) in summer and winter seasons, respectively (Table 1).
These data concur with previous studies where researchers investigated the Cr concentration in wastewater collected from different areas of Punjab, Pakistan [39,40,41]. Parveen, Ashfaq, Ali, Qadri and Zeb [42] reported that the Cr concentration in tannery wastewater ranged from 15 to 186 mg L−1 in the Karachi district of Sindh, Pakistan. The authors revealed that the Cr concentration in all the tannery wastewater samples was above the NEQS safe limit of 1 mg L−1 in wastewater.
Recently, Ashraf, Naveed, Afzal, Seleiman, Al-Suhaibani, Zahir, Mustafa, Refay, Alhammad, Ashraf, Alotaibi and Abdella [43] reported that the Cr concentration in tannery wastewater was above the threshold limit with an average Cr concentration of 134 mg L−1. The results from the current study demonstrated that greater Cr concentration was found in TWW-winter compared to TWW-summer samples, which may be due to more tanning processing in the winter season or due to inefficient tanning processes. Khalid, Rizvi, Yousaf, Khan, Noman, Aqeel, Latif and Rafique [44] revealed that tannery wastewater had a high Cr concentration (up to 1.45 mg L−1) that exceeded the safe limits of NEQS (1 mg L−1) in the city of Sialkot in Punjab, Pakistan. Our data indicated that the wastewater from all the tanneries collected in summer and winter seasons did not meet the legal requirements of discharge to drain or sewer without Cr treatment.
3.2. Chromium Speciation in Wastewater
Chromium speciation data of the tannery wastewater showed that the percentage distribution of Cr(III) ranged from 40% to 90% and from 2% to 98% of total Cr in the TWW-summer and TWW-winter samples, respectively (Figure 1b,c). The percentage distribution of Cr(VI) ranged from 1% to 70% and 1% to 35% in the TWW- summer and TWW-winter season samples, respectively.
The percentage abundance of Cr(III) and Cr(VI) was in the order of TW-winter > TW-summer (Table 1; Figure S2, Supplementary Information). In this study, Cr(III) was the dominant Cr species in tannery wastewater of Kasur in both seasons (Figure S2, Supplementary Information). This indicates that reducing conditions prevail in the tannery wastewater, which is also agreement with the presence of a negative redox potential (Eh) (TWW-summer: −3.4 ± 66; TWW-winter: −20.7 ± 99).
Neelam, Alamgir and Kanwal [45] reported that the basic pH of wastewater might induce Cr(VI) transformation to Cr(III), which settles down in the surface as oxides and in sludge. The results from the current study revealed that high concentration of Cr(III) in wastewater may make precipitates with Fe and settle down in bottom sediments or remain in tannery wastewater residues [46]. The presence of Cr(VI) in wastewater indicated that Cr(III)-compounds released from tanning processes could possibly be oxidized into Cr(VI) by oxidizing agents, such as manganese oxide (MnO2) and dissolved oxygen [15,16].
3.3. Tannery Wastewater Attributes
In both seasons, tannery wastewater samples showed slightly acidic to alkaline pH (TWW-summer pH: 6.0–8.8 and TWW-winter pH: 6.0–8.1), which were within the permissible limit set by WHO and NEQS (pH 6–10 and 6–9, respectively) (Table 2). The EC of tannery wastewater ranged from 2.0 to 24.4 mS cm−1 (mean: 8.7 mS cm−1) in TWW-summer and from 8.5 to 21.8 mS cm−1 (mean: 14.5 mS cm−1) in TWW-winter samples, which were significantly greater than the USEPA’s permissible limit (1.0 mS cm−1). The results showed that the TWW-summer and TWW-winter samples had high concentrations of cations, such as Ca (96 and 97 mg L−1, respectively) Mg (477 and 509 mg L−1), Na (324 and 345 mg L−1) and K (151.7 and 184.6 mg L−1). Among various cations, the Na concentration of 46% (TWW-summer) and 84% (TWW-winter) samples exceeded the safe limit of NEQS (Table 2).
The data demonstrated that the tannery wastewater of the study area was dominated by major cations and anions in the following order of percentage abundance: Mg > Na > K > Ca and Cl > HCO3 > SO4 > CO3 (Table 1). These results concur with other researchers, who reported acidic to basic pH and EC of tannery wastewater in various industrial zones of Pakistan and other countries [14,45,47,48]. An alkaline pH of tannery wastewater may be because of high anions and cations concentration which are possibly produced from different tannery industrial processes [49].
The manganese concentration was higher than the permissible limit set by NEQS (1.5 mg L−1) in tannery industry wastewater samples of TWW-summer and TWW-winter season, with about 80% summer and 100% of winter samples. The iron concentration ranged from 3.6 to 21 and from 4.5 to 29 mg L−1, respectively, in the summer and winter seasons samples, which was above the permissible limit of 2.0 mg L−1 set by NEQS. The COD values ranged from 1660 to 8330 and from 471 to 9286 mg L−1. The BOD concentration spanned 885 to 4374 and 235 to 4693 mg L−1, respectively, in TWW-summer and TWW-winter samples, respectively, thus, exceeding the WHO safe limits in all the wastewater samples (Table 2).
The results showed that the wastewater had low Eh and DO concentrations, which indicated reduced aqueous conditions. Due to the elevated concentration of dissolved organic contaminants or organic matter, microbes consume huge oxygen and enhance the level of BOD, which produces anaerobic conditions causing toxic greenhouse gas formation [50,51]. The results concur with the previous findings where researchers showed high BOD levels and low DO in tannery wastewater [52].
Afzal, Rehman, Shabir, Tahseen, Ijaz, Hashmat and Brix [53] reported high concentrations of COD because of a high number of organic compounds, which are not degraded by the microbes. Due to reduced conditions, microbes, Fe- and sulfur-bearing minerals reduced the Cr(VI) species into Cr(III), which might make precipitates, such as Cr2O3, CrPO4 and Cr(OH)3 or isomorphic substitution for Fe(III) in oxides, such as goethite [54]. At pH > 4, Cr (III) can adsorb on Fe oxide mineral surfaces (Fe3O4 and Fe2O3) or make complex through the chelation of organic matter [55,56].
3.4. Multivariate Analysis of Various Attributes in Tannery Wastewater
The chemical nature of the water was determined by plotting the major anions and cations concentrations on a Piper plot [57,58] (Figure 2).
It is important to examine the hydrogeochemistry of the water based on the abundance of the selected cations and anions [59]. There are two types of triangles—one is for cations, and the other is for anions. In addition, chemical nature of wastewater was also examined by plotting the TDS concentration on a Durov diagram. The Durov diagram shows that all the wastewater samples had a TDS less than 10 g L−1 with Cl and HCO3 as the major anions (Figure S3, Supplementary Information).
The Piper plot shows the ionic supremacy of Mg over Na, K and Ca and of Cl over SO4 and HCO3 pointing to a Ca-Mg-Cl-SO4 wastewater type (Figure 2a,b). During the summer and winter seasons, the major dominant wastewater type was Ca-Mg-SO4 (non-carbonates hardness (secondary salinity) exceed 50%), mixed Ca-Mg-Cl (no cation-anion pairs exceed 50%) and Na-Cl (salinity). Other main dominant wastewater types were mixtures of SO4-Cl, Cl-SO4-HCO3 and Na-K-Mg. These findings may reflect the highly saline type of tannery wastewater [60] as high concentrations of Ca, Mg, Na, Cl and SO4 were present in the samples.
The Durvo and Piper plots specify the variability of the chemical composition in wastewater contributed by local geochemical conditions, mineral–water interaction, dissolution of minerals and use of salts in tannery industries [61,62]. The Piper plot demonstrates that alkaline ions (Mg and Ca) were not higher than the alkalis (Na and K) but strong acid anions (Cl and SO4) exceeded week acids (HCO3 and CO3). Ghazaryan and Chen [59] reported the same type of water with high concentration of strong acid anions and cations. In the current study, high levels of EC with elevated COD and BOD, as well as an abundance of Cr(III) were an indication of the reduced aqueous environment in wastewater and as such may support Cr(VI) reduction by redox sensitive agents.
In this study, the Pearson correlation matrix shows a correlation between Cr and other attributes in wastewater of TWW-summer and TWW-winter samples. In TWW-summer, a positive and significant correlation was found between EC-TDS (r = 0.99), HCO3-Cl (r = 0.75), Ca-Mg (r = 0.61), Mg-CrT (r = 0.69), Na-K (r = 0.79), CrT-Cr(III) (0.99), Cr(III)-Cr(VI) (r = 0.90) and SO4-Eo (r = 0.63) (Table S2, Supplementary Information). In TWW-winter, a significant and positive correlation was found between EC-TDS (r = 0.81), CO3-CrT (r = 0.55), TH-Mg (r = 0.95), Na-K (r = 0.62), CrT-Cr(III) (r = 0.99) and Cr(VI)-Cr(III) (r = 0.45) (Table S3, Supplementary Information).
Inter-elemental relationships in wastewater provide the information on pathways and sources of various variables in hydro-geoenvironments. A significant positive correlation was found between the total Cr and Cr(III), indicating the main source of Cr in tannery wastewater was Cr(III)-containing mineral phases. The pH has a positive correlation with Cr indicating that Cr speciation and the precipitation/dissolution depends on pH [62].
3.5. Principal Component Analysis
Five main principal components (PCs) (PC-1, PC-2, PC-3, PC-4 and PC-5) affecting the wastewater quality showed 70% and 57% variance of the data in the TWW-summer and TWW-winter samples, respectively (Table S4, Supplementary Information). The bold values in Table S4 of the Supplementary Information correspond to each variable that may control the hydrogeochemistry of the tannery wastewater. In the PC-1 of TWW-summer and TWW-winter samples (27% and 18%), Na, K, EC, TDS, total Cr, Cr(III) and EC, Na, K, TH, total Cr and Cr(III), respectively, were major contributing factors. In each PCA loading and score plot, the total Cr and its species were clustered together (Figure 3; Figures S4 and S5, Supplementary Information). Thus, these attributes showed co-variance revealing an inter-correlation, and they may vary together in the tannery industry wastewater.
The PC-1, PC-2 and PC-3 may suggest the presence of possible sources and minerals of cation, anions and Cr, which may be associated with the dissolution of Na/Cl, Ca/Mg, Cr-minerals or other mineral phases in wastewater (Table S4, Supplementary Information). It could be inferred from the PC-4 that the high Cr(VI) concentration may be due to conversion of Cr(III) to Cr(VI) because of MnO and DO [56]. In wastewater, Cr(VI) may be present in the form of minerals in association with various cations released from tanneries [63].
3.6. Saturation Indices for Estimating Possible Mineral-Phases
The SI values from the geochemical speciation modelling of tannery wastewater samples are shown in Table S5, Supplementary Information. PHREEQC data revealed that the wastewater conditions were mainly under saturated for CO3 containing minerals-phases, such as calcite [(CaCO3) (summer: −0.25; winter: −0.35)], aragonite, [(CaCO3) (summer: −0.36; winter: −0.46)] and gypsum [(CaSO4:2H2O) (summer: −1.25; winter: −0.59)]. This indicates that CO3 minerals are unlikely to precipitate as indicated by the negative SI values [57].
In contrast, the positive SI values were obtained for Fe-bearing phases, such as Fe(II)-chromite (FeCr2O4), ferrihydrite, goethite, hematite (Fe2O3), magnetite (Fe3O4), Mg-ferrite (MgFe2O4) and siderite (FeCO3) (Table S5, Supplementary Information). This shows that Fe oxides and other Fe-bearing minerals could possibly control Cr speciation in tannery wastewater. Immobilization of Cr(III) may occur through the precipitation of Cr(OH)3 or through the precipitation of mixed Fe(III)-Cr(III) (oxy)hydroxides [46].
The SI values for other Cr mineral phases were observed, such as FeCr2O4 (summer: 16.01; winter: 16.57)], MgCr2O4 (summer: 5.66; winter: 6.36)], Cr(OH)3) (summer: 3.50; winter: 4.07)] and Cr2O3 (summer: 8.9; winter: 10.04)], with higher SI values in winter season wastewater compared to the summer season. This shows that, in summer season, there is a comparatively higher use and discharge of water in the leather tanning process than in the winter season, which may lead to greater solubility of ions in the winter season water. The results indicate that mainly Cr(III) compounds have been used in tannery wastewater for tanning purposes [8].
3.7. Geochemical Speciation and Eh–pH Relationship of Chromium-Contaminated Tannery Wastewater
The Eh–pH stability diagram illustrates various chemical forms of Cr that could be present within the specified Eh and pH range in wastewater (Figure 4). In this study, the Eh–pH diagram explained the stable and soluble forms of Cr in tannery wastewater. Trivalent Cr was present in a wide pH and Eh range, while Cr(VI) exists in a specific pH and Eh range. Above the pH 3.5, Cr(III) hydrolysis in Cr-tannery wastewater system may produce Cr(III) as Cr2O3 and CrO2 species. It is evident from the Eh–pH stability data that Cr fate is mainly controlled by Fe(III) oxides (i.e., magnetite, hematite and Mg-rich ferrite) and in the form of Fe(III)-Cr(III)-oxide precipitates in wastewater in both seasons.
3.8. Environmental Risk Assessment of Tannery Wastewater
A single-factor evaluation index and CCI were used to identify the main attributes contributing to the contamination and to evaluate the overall status of water contamination [64] (Table 3). In tannery wastewater, the SFEI was above >1, and the CCI values of tannery wastewater exceeded the contamination standard category (Class V). The tannery wastewater was contaminated in the study area mainly due to anthropogenic processes related to leather tanning, causing enrichment with Cr, organic contaminants and other metals. Based on the quality classification [65], the CCI values were higher in all the wastewater samples, and its quality fell in Category V, i.e., ‘heavily contaminated’ [66].
The HEI (summer: 23.3; winter 60.4) showed that tannery wastewater is highly contaminated with metals, especially with Cr produced from tannery industries in the study area. The HEI values of our study was lower than the reported values (up to 83) for contaminated water of Egypt [67]. Mekuria, Kassegne and Asfaw [35] reported that 60% of contaminated wastewater was within the low contamination class (HEI < 10), which may be because of low metal load in these sites. The major inputs of heavy metals include domestic wastes, tannery industries and agrochemicals. The results showed a warning situation of environmental risk from tannery wastewater for both seasons.
The highest SFEI, CCI and HEI values were recorded in the winter samples, which agrees with high load of BOD, COD, salinity and Cr inputs from different processes of tanneries. Future research is warranted on sustainable treatment of tannery wastewater using a low-cost and eco-friendly technology, such as floating treatment or constructed wetlands considering high values of risk parameters (SFEI, CCI and HEI).
4. Conclusions
This study shows that tannery wastewater had high concentrations of Cr, Fe and other ions (Cl, CO32−, HCO3 and SO42−), as well as COD and BOD. All the tannery wastewater samples from the summer and winter seasons exceeded the Cr concentration above the permissible limits set by NEQS, USEPA and WHO. The chromium concentration in TWW-summer was lower compared to the TWW-winter samples (15 and 49 mg L−1).
The Piper plot showed the ionic supremacy of Mg over Na, K and Ca and of Cl over SO4 and HCO3 pointing to a Ca-Mg-Cl-SO4 wastewater type. These findings may reflect the highly saline type of tannery wastewater in the summer and winter seasons.
The PCA results were also supported by hydro-geochemical modelling data that showed that Cr association with Fe oxide phases might have a potential role in the adsorption and dissolution of Cr in tannery wastewater systems. According to the CCI and HEI values, the overall tannery wastewater quality is poor and not suitable for reuse without proper treatment.
Future research should be directed to develop and implement a suitable and eco-friendly remediation strategy to treat Cr-contaminated tannery industry wastewater, such as constructed wetlands technology. It is imperative to precisely understand Cr hydrogeochemistry in wastewater, which provides base knowledge to determine the fate of Cr in wastewater and potential threats to the ecosystem.
Supplementary Materials
The following supporting information can be downloaded at: https://www.mdpi.com/article/10.3390/w15030391/s1, Figure S1: Location map of study area showing the TWW-summer and TWW-winter sampling sites in Kasur, Punjab, Pakistan; Figure S2: Scatter plot showing the percentage speciation of total Cr in wastewater samples collected in summer (TWW-summer) and winter (TWW-winter) seasons from Kasur, Punjab, Pakistan; Figure S3: Durov plot showing the tannery industry wastewater chemistry with pH and TDS in (A) summer (TWW-summer) and (B) winter (TWW-winter) samples, collected from Kasur, Pun-jab, Pakistan; Figure S4: Score plot showing the Cr distribution in tannery industry wastewater samples collected in (A) summer (TWW-summer) and (B) winter (TWW-winter) from Kasur, Punjab, Paki-stan; Figure S5: Scree plot of PC-I and PC-II of the various tannery industry wastewater attributes and Cr determined in wastewater of different tannery industries (A: summer (TWW-summer); B: winter (TWW-winter)) in Punjab, Pakistan; Table S1 Location coordinates of wastewater samples collected in summer (TWW-summer) and winter (TWW-winter) seasons from Kasur, Punjab, Pakistan; Table S2 Pearson correlation matrix of various attributes of tannery wastewater samples collected in summer (TWW-summer) season from Kasur, Punjab, Pakistan; Table S3 Pearson correlation matrix of various attributes of tannery industry wastewater samples collected in winter (TWW-winter) season from Kasur, Pun-jab, Pakistan; Table S4 Principal component analysis of Cr and various other wastewater quality parameters for tannery wastewater samples collected in two different sea-sons from Kasur, Punjab, Pakistan; Table S5 Saturation indices of different mineral phases calculated by geochemical modeling using water attributes of tannery wastewater.
Author Contributions
F.Y. collected wastewater samples and prepared the initial draft. I.B., N.K.N., M.A. and M.S. conceptualized the idea, provided resources, read, edited and improved the paper. K.H., F.A.-M., Q.S., F.A. and H.W. read, edited and improved the paper. All authors have read and agreed to the published version of the manuscript.
Funding
Higher Education Commission (Project Nos. 6425/Punjab/NRPU/R&D/HEC/2016 and 6396/Punjab/NRPU/R&D/HEC/2016), Pakistan. COMSTEQ-TWAS research grant 2018 (18–268 RG/EAS/AS_C) and Researchers Supporting Project No. RSP-2021/24.
Institutional Review Board Statement
Not applicable.
Informed Consent Statement
Not applicable.
Data Availability Statement
All data are provided in paper.
Acknowledgments
The authors are thankful to Higher Education Commission (Project Nos. 6425/Punjab/NRPU/R&D/HEC/2016 and 6396/Punjab/NRPU/R&D/HEC/2016), Pakistan for providing financial support. I.B. acknowledges the support from COMSTEQ-TWAS research grant 2018 (18–268 RG/EAS/AS_C). The authors are grateful to the Researchers Supporting Project No. RSP-2021/24, King Saud University, Riyadh, Saudi Arabia.
Conflicts of Interest
The authors declare no conflict of interest.
References
1. Laxmi, V.; Kaushik, G. Toxicity of Hexavalent Chromium in Environment, Health Threats, and Its Bioremediation and Detoxification from Tannery Wastewater for Environmental Safety. In Bioremediation of Industrial Waste for Environmental Safety: Volume I: Industrial Waste and Its Management; Saxena, G., Bharagava, R., Eds.; Springer: Singapore, 2020; pp. 223–243. [Google Scholar]
2. Yahya, M.D.; Obayomi, K.S.; Abdulkadir, M.B.; Iyaka, Y.A.; Olugbenga, A.G. Characterization of cobalt ferrite-supported activated carbon for removal of chromium and lead ions from tannery wastewater via adsorption equilibrium. Water Sci. Eng. 2020, 13, 202–213. [Google Scholar] [CrossRef]
3. Liang, T.; Li, L.; Zhu, C.; Liu, X.; Li, H.; Su, Q.; Ye, J.; Geng, B.; Tian, Y.; Sardar, M.F.; et al. Adsorption of As(V) by the Novel and Efficient Adsorbent Cerium-Manganese Modified Biochar. Water 2020, 12, 2720. [Google Scholar] [CrossRef]
4. Hasan, I.M.U.; Javed, H.; Hussain, M.M.; Shakoor, M.B.; Bibi, I.; Shahid, M.; Farwa; Xu, N.; Wei, Q.; Qiao, J.; et al. Biochar/nano-zerovalent zinc-based materials for arsenic removal from contaminated water. Int. J. Phytoremediation 2022, 2022, 2140778. [Google Scholar] [CrossRef]
5. Khan, M.U.; Malik, R.N.; Muhammad, S. Human health risk from Heavy metal via food crops consumption with wastewater irrigation practices in Pakistan. Chemosphere 2013, 93, 2230–2238. [Google Scholar] [CrossRef] [PubMed]
6. Czikkely, M.; Neubauer, E.; Fekete, I.; Ymeri, P.; Fogarassy, C. Review of Heavy Metal Adsorption Processes by Several Organic Matters from Wastewaters. Water 2018, 10, 1377. [Google Scholar] [CrossRef][Green Version]
7. Sardar, M.; Ahmad, H.; Zıa-Ur-Rehman, M. Absorption of foliar-applied lead (Pb) in rice (Oryza sativa L.): A hydroponic experiment. Fresenius Env. Bull 2018, 27, 6634–6639. [Google Scholar]
8. Younas, F.; Niazi, N.K.; Bibi, I.; Afzal, M.; Hussain, K.; Shahid, M.; Aslam, Z.; Bashir, S.; Hussain, M.M.; Bundschuh, J. Constructed wetlands as a sustainable technology for wastewater treatment with emphasis on chromium-rich tannery wastewater. J. Hazard. Mater. 2021, 422, 126926. [Google Scholar] [CrossRef]
9. Kazakis, N.; Kantiranis, N.; Kalaitzidou, K.; Kaprara, E.; Mitrakas, M.; Frei, R.; Vargemezis, G.; Tsourlos, P.; Zouboulis, A.; Filippidis, A. Origin of hexavalent chromium in groundwater: The example of Sarigkiol Basin, Northern Greece. Sci. Total. Environ. 2017, 593-594, 552–566. [Google Scholar] [CrossRef]
10. Khalid, S.; Shahid, M.; Dumat, C.; Niazi, N.K.; Bibi, I.; Bakhat, H.F.S.G.; Abbas, G.; Murtaza, B.; Javeed, H.M.R. Influence of groundwater and wastewater irrigation on lead accumulation in soil and vegetables: Implications for health risk assessment and phytoremediation. Int. J. Phytoremediation 2017, 19, 1037–1046. [Google Scholar] [CrossRef]
11. Khalid, S.; Shahid, M.; Natasha; Bibi, I.; Sarwar, T.; Shah, A.H.; Niazi, N.K. A Review of Environmental Contamination and Health Risk Assessment of Wastewater Use for Crop Irrigation with a Focus on Low and High-Income Countries. Int. J. Environ. Res. Public Heal. 2018, 15, 895. [Google Scholar] [CrossRef][Green Version]
12. Natasha; Bibi, I.; Niazi, N.K.; Shahid, M.; Ali, F.; Hasan, I.M.U.; Rahman, M.M.; Younas, F.; Hussain, M.M.; Mehmood, T.; et al. Distribution and ecological risk assessment of trace elements in the paddy soil-rice ecosystem of Punjab, Pakistan. Environ. Pollut. 2022, 307, 119492. [Google Scholar] [CrossRef] [PubMed]
13. Ali, A.; Hussain, M.M.; Niazi, N.K.; Younas, F.; Farooqi, Z.U.R.; Zeeshan, N.; Javed, M.T.; Shahid, M.; Bibi, I. A Comparison of Technologies for Remediation of Arsenic-Bearing Water: The Significance of Constructed Wetlands. In Global Arsenic Hazard: Ecotoxicology and Remediation; Niazi, N., Bibi, I., Aftab, T., Eds.; Springer International Publishing: Cham, Switzerland, 2022; pp. 223–245. [Google Scholar] [CrossRef]
14. Homa, D.; Haile, E.; Washe, A.P. Determination of Spatial Chromium Contamination of the Environment around Industrial Zones. Int. J. Anal. Chem. 2016, 2016, 7214932. [Google Scholar] [CrossRef] [PubMed][Green Version]
15. Apollaro, C.; Fuoco, I.; Brozzo, G.; De Rosa, R. Release and fate of Cr(VI) in the ophiolitic aquifers of Italy: The role of Fe(III) as a potential oxidant of Cr(III) supported by reaction path modelling. Sci. Total. Environ. 2019, 660, 1459–1471. [Google Scholar] [CrossRef] [PubMed]
16. Vasileiou, E.; Papazotos, P.; Dimitrakopoulos, D.; Perraki, M. Expounding the origin of chromium in groundwater of the Sarigkiol basin, Western Macedonia, Greece: A cohesive statistical approach and hydrochemical study. Environ. Monit. Assess. 2019, 191, 509. [Google Scholar] [CrossRef] [PubMed]
17. Ma, H.; Li, X.; Zhu, C.; Chen, F.; Yang, Y.; Chen, X. Liberation and recovery of Cr from real tannery sludge by ultrasound-assisted supercritical water oxidation treatment. J. Clean. Prod. 2020, 267. [Google Scholar] [CrossRef]
18. Guo, S.-S.; Xu, Y.-H.; Yang, J.-Y. Simulating the migration and species distribution of Cr and inorganic ions from tanneries in the vadose zone. J. Environ. Manag. 2021, 288, 112441. [Google Scholar] [CrossRef]
19. Izbicki, J.A.; Ball, J.W.; Bullen, T.D.; Sutley, S.J. Chromium, chromium isotopes and selected trace elements, western Mojave Desert, USA. Appl. Geochem. 2008, 23, 1325–1352. [Google Scholar] [CrossRef]
20. Khan, M.; Ahad, S. Analysis Of Kasur Tannery Pre Treated Wastewater For Its Metal Toxicity. J. Appl. Chem. 2015, 4, 572–577. [Google Scholar]
21. Zaheer, I.; Ali, S.; Saleem, M.; Imran, M.; Alnusairi, G.; Alharbi, B.; Riaz, M.; Abbas, Z.; Rizwan, M.; Soliman, M. Role of iron–lysine on morpho-physiological traits and combating chromium toxicity in rapeseed (Brassica napus L.) plants irrigated with different levels of tannery wastewater. Plant Physiol. Biochem. 2020, 155, 70–84. [Google Scholar] [CrossRef]
22. Zaheer, I.E.; Ali, S.; Rizwan, M.; Bareen, F.-E.; Abbas, Z.; Bukhari, S.A.H.; Wijaya, L.; Alyemeni, M.N.; Ahmad, P. Zinc-lysine prevents chromium-induced morphological, photosynthetic, and oxidative alterations in spinach irrigated with tannery wastewater. Environ. Sci. Pollut. Res. 2019, 26, 28951–28961. [Google Scholar] [CrossRef]
23. Ashraf, S.; Naveed, M.; Afzal, M.; Seleiman, M.F.; Al-Suhaibani, N.A.; Zahir, Z.A.; Mustafa, A.; Refay, Y.; Alhammad, B.A.; Ashraf, S.; et al. Unveiling the Potential of Novel Macrophytes for the Treatment of Tannery Effluent in Vertical Flow Pilot Constructed Wetlands. Water 2020, 12, 549. [Google Scholar] [CrossRef]
24. Younas, F.; Bibi, I.; Afzal, M.; Niazi, N.K.; Aslam, Z. Elucidating the Potential of Vertical Flow-Constructed Wetlands Vegetated with Different Wetland Plant Species for the Remediation of Chromium-Contaminated Water. Sustainability 2022, 14, 5230. [Google Scholar] [CrossRef]
25. Shah, S.W.A.; Rehman, M.U.; Hayat, A.; Tahseen, R.; Bajwa, S.; Islam, E.; Naqvi, S.N.H.; Shabir, G.; Iqbal, S.; Afzal, M.; et al. Enhanced Degradation of Ciprofloxacin in Floating Treatment Wetlands Augmented with Bacterial Cells Immobilized on Iron Oxide Nanoparticles. Sustainability 2022, 14, 14997. [Google Scholar] [CrossRef]
26. Afzal, M.; Shabir, G.; Iqbal, S.; Mustafa, T.; Khan, Q.M.; Khalid, Z.M. Assessment of Heavy Metal Contamination in Soil and Groundwater at Leather Industrial Area of Kasur, Pakistan. CLEAN Soil, Air, Water 2013, 42, 1133–1139. [Google Scholar] [CrossRef]
27. Joyia, F.A.; Ashraf, M.Y.; Shafiq, F.; Anwar, S.; Nisa, Z.-U.; Khaliq, B.; Malik, A. Phytotoxic effects of varying concentrations of leather tannery effluents on cotton and brinjal. Agric. Water Manag. 2020, 246, 106707. [Google Scholar] [CrossRef]
28. Abbas, M.; Rahman, M.A.U.; Safdar, A. Detection of Heavy Metals Concentration Due to Leather Tanning Industry and Prevalent Disease Pattern in Kasur, Pakistan. Environ. Urban. ASIA 2012, 3, 375–384. [Google Scholar] [CrossRef]
29. Andleeb, S.; Mahmood, T.; Khalid, A.; Akrim, F.; Fatima, H. Hexavalent chromium induces testicular dysfunction in small Indian mongoose (Herpestes javanicus) inhabiting tanneries area of Kasur District, Pakistan. Ecotoxicol. Environ. Saf. 2018, 148, 1001–1009. [Google Scholar] [CrossRef]
30. Bozlur Rahman, M. Design and Fabrication of Column Filtration Reactor for the Removal of Dissolved Dyes from Tannery Wastewater. Master’s Thesis, Bangladesh University of Engineering and Technology, Dhaka, Bangladesh, 2004. [Google Scholar]
31. Spellman, F. Water & Wastewater Infrastructure: Energy Efficiency and Sustainability; Crc Press: Boca Raton, FL, USA, 2013. [Google Scholar]
32. Ryan, J.; Estefan, G.; Rashid, A. Soil and Plant Analysis Laboratory Manual; ICARDA: Beirut, Liban, 2001. [Google Scholar]
33. Saritha, B.; Chockalingam, M.; Bist, B. Evaluation and Characterization of Tannery Wastewater. Int. J. Pure Appl. Math. 2018, 119, 8479–8487. [Google Scholar]
34. NEQS. The Gazette of Pakistan, Extraordinary, Islamabad; Part II, Statutory Notification (SRO); Government of Pakistan, Envi-ronmental and Urban Affairs Division (Pakistan Environmental Protection Agency): Islamabad, Pakistan, 1999.
35. Mekuria, D.M.; Kassegne, A.B.; Asfaw, S.L. Assessing pollution profiles along Little Akaki River receiving municipal and industrial wastewaters, Central Ethiopia: Implications for environmental and public health safety. Heliyon 2021, 7, e07526. [Google Scholar] [CrossRef]
36. Bibi, I.; Singh, B.; Silvester, E. Dissolution of illite in saline–acidic solutions at 25 °C. Geochim. Cosmochim. Acta 2011, 75, 3237–3249. [Google Scholar] [CrossRef]
37. Dotro, G.; Larsen, D.; Palazolo, P. Preliminary Evaluation of Biological and Physical–Chemical Chromium Removal Mechanisms in Gravel Media Used in Constructed Wetlands. Water, Air, Soil Pollut. 2010, 215, 507–515. [Google Scholar] [CrossRef]
38. Shakoor, M.B.; Bibi, I.; Niazi, N.K.; Shahid, M.; Nawaz, M.F.; Farooqi, A.; Naidu, R.; Rahman, M.M.; Murtaza, G.; Lüttge, A. The evaluation of arsenic contamination potential, speciation and hydrogeochemical behaviour in aquifers of Punjab, Pakistan. Chemosphere 2018, 199, 737–746. [Google Scholar] [CrossRef]
39. Bhalli, J.A.; Khan, Q.M. Pollution Level Analysis in Tannery Effluents Collected From Three Different Cities of Punjab, Pakistan. Pak. J. Biol. Sci. 2006, 9, 418–421. [Google Scholar] [CrossRef][Green Version]
40. Shakir, L.; Ejaz, S.; Ashraf, M.; Ahmad, N.; Javeed, A. Characterization of tannery effluent wastewater by proton-induced X-ray emission (PIXE) analysis to investigate their role in water pollution. Environ. Sci. Pollut. Res. 2011, 19, 492–501. [Google Scholar] [CrossRef] [PubMed]
41. Shafiq, M.; Shaukat, T.; Nazir, A.; Bareen, F.-E. Modeling of Cr contamination in the agricultural lands of three villages near the leather industry in Kasur, Pakistan, using statistical and GIS techniques. Environ. Monit. Assess. 2017, 189, 1–18. [Google Scholar] [CrossRef]
42. Parveen, R.; Ashfaq, M.; Qureshi, J.; Ali, S.M.M.; Qadri, M. Estimation of Chromium in Effluents from Tanneries of Korangi Industrial Area. Pak. J. Chem. 2013, 3, 29–33. [Google Scholar] [CrossRef]
43. Hadad, H.; Maine, M.A.; Bonetto, C. Macrophyte growth in a pilot-scale constructed wetland for industrial wastewater treatment. Chemosphere 2006, 63, 1744–1753. [Google Scholar] [CrossRef]
44. Khalid, N.; Rizvi, Z.F.; Yousaf, N.; Khan, S.M.; Noman, A.; Aqeel, M.; Latif, K.; Rafique, A. Rising Metals Concentration in the Environment: A Response to Effluents of Leather Industries in Sialkot. Bull. Environ. Contam. Toxicol. 2021, 106, 493–500. [Google Scholar] [CrossRef]
45. Neelam, A.; Alamgir, A.; Kanwal, H. Determination of chromium in the tannery wastewater, Korangi, Karachi. Int. J. Environ. Sci. Nat. Resour. 2018, 15, 122–125. [Google Scholar] [CrossRef]
46. Bibi, I.; Niazi, N.K.; Choppala, G.; Burton, E. Chromium(VI) removal by siderite (FeCO3) in anoxic aqueous solutions: An X-ray absorption spectroscopy investigation. Sci. Total. Environ. 2018, 640–641, 1424–1431. [Google Scholar] [CrossRef]
47. Chowdhury, M.; Mostafa, G.; Biswas, T.K.; Mandal, A.; Saha, A.K. Characterization of the Effluents from Leather Processing Industries. Environ. Process. 2015, 2, 173–187. [Google Scholar] [CrossRef][Green Version]
48. Ashraf, S.; Naveed, M.; Afzal, M.; Ashraf, S.; Ahmad, S.R.; Rehman, K.; Zahir, Z.A.; Núñez-Delgado, A. Evaluation of Toxicity on Ctenopharyngodon idella Due to Tannery Effluent Remediated by Constructed Wetland Technology. Processes 2020, 8, 612. [Google Scholar] [CrossRef]
49. Nur-E-Alam, M.; Mia, M.; Ahmad, F.; Rahman, M. An overview of chromium removal techniques from tannery effluent. Appl. Water Sci. 2020, 10, 205. [Google Scholar] [CrossRef]
50. Mwinyihija, M.; Meharg, A.; Dawson, J.; Strachan, N.J.; Killham, K. An Ecotoxicological Approach to Assessing the Impact of Tanning Industry Effluent on River Health. Arch. Environ. Contam. Toxicol. 2006, 50, 316–324. [Google Scholar] [CrossRef] [PubMed]
51. Sardar, M.F.; Zhu, C.; Geng, B.; Huang, Y.; Abbasi, B.; Zhang, Z.; Song, T.; Li, H. Enhanced control of sulfonamide resistance genes and host bacteria during thermophilic aerobic composting of cow manure. Environ. Pollut. 2021, 275, 116587. [Google Scholar] [CrossRef] [PubMed]
52. Aregu, M.B.; Asfaw, S.L.; Khan, M.M. Developing horizontal subsurface flow constructed wetland using pumice and Chrysopogon zizanioides for tannery wastewater treatment. Environ. Syst. Res. 2021, 10, 1–13. [Google Scholar] [CrossRef]
53. Afzal, M.; Rehman, K.; Shabir, G.; Tahseen, R.; Ijaz, A.; Hashmat, A.J.; Brix, H. Large-scale remediation of oil-contaminated water using floating treatment wetlands. NPJ Clean Water 2019, 2, 3. [Google Scholar] [CrossRef][Green Version]
54. Li, Y.; Cundy, A.B.; Feng, J.; Fu, H.; Wang, X.; Liu, Y. Remediation of hexavalent chromium contamination in chromite ore processing residue by sodium dithionite and sodium phosphate addition and its mechanism. J. Environ. Manag. 2017, 192, 100–106. [Google Scholar] [CrossRef][Green Version]
55. Liang, J.; Huang, X.; Yan, J.; Li, Y.; Zhao, Z.; Liu, Y.; Ye, J.; Wei, Y. A review of the formation of Cr(VI) via Cr(III) oxidation in soils and groundwater. Sci. Total. Environ. 2021, 774, 145762. [Google Scholar] [CrossRef]
56. Dai, R.; Liu, J.; Yu, C.; Sun, R.; Lan, Y.; Mao, J.-D. A comparative study of oxidation of Cr(III) in aqueous ions, complex ions and insoluble compounds by manganese-bearing mineral (birnessite). Chemosphere 2009, 76, 536–541. [Google Scholar] [CrossRef]
57. Li, P.; Wu, J.; Qian, H. Assessment of groundwater quality for irrigation purposes and identification of hydrogeochemical evolution mechanisms in Pengyang County, China. Environ. Earth Sci. 2012, 69, 2211–2225. [Google Scholar] [CrossRef]
58. Natasha; Bibi, I.; Shahid, M.; Niazi, N.K.; Younas, F.; Naqvi, S.R.; Shaheen, S.M.; Imran, M.; Wang, H.; Hussaini, K.M.; et al. Hydrogeochemical and health risk evaluation of arsenic in shallow and deep aquifers along the different floodplains of Punjab, Pakistan. J. Hazard. Mater. 2020, 402, 124074. [Google Scholar] [CrossRef] [PubMed]
59. Ghazaryan, K.; Chen, Y. Hydrochemical assessment of surface water for irrigation purposes and its influence on soil salinity in Tikanlik oasis, China. Environ. Earth Sci. 2016, 75, 383. [Google Scholar] [CrossRef]
60. Kumar, P.S. Evolution of groundwater chemistry in and around Vaniyambadi Industrial Area: Differentiating the natural and anthropogenic sources of contamination. Geochemistry 2014, 74, 641–651. [Google Scholar] [CrossRef]
61. Kanagaraj, G.; Elango, L. Chromium and fluoride contamination in groundwater around leather tanning industries in southern India: Implications from stable isotopic ratio δ53Cr/δ52Cr, geochemical and geostatistical modelling. Chemosphere 2019, 220, 943–953. [Google Scholar] [CrossRef]
62. Shahid, M.; Shamshad, S.; Rafiq, M.; Khalid, S.; Bibi, I.; Niazi, N.K.; Dumat, C.; Rashid, M.I. Chromium speciation, bioavailability, uptake, toxicity and detoxification in soil-plant system: A review. Chemosphere 2017, 178, 513–533. [Google Scholar] [CrossRef]
63. Unceta, N.; Séby, F.; Malherbe, J.; Donard, O.F.X. Chromium speciation in solid matrices and regulation: A review. Anal. Bioanal. Chem. 2010, 397, 1097–1111. [Google Scholar] [CrossRef]
64. Mishra, S.; Lai, K.; Singh, V. Optimality and duality for minimax fractional programming with support function under (C,α,ρ,d)-convexity. J. Comput. Appl. Math. 2015, 274, 1–10. [Google Scholar] [CrossRef]
65. Son, C.T.; Giang, N.T.H.; Thao, T.P.; Nui, N.H.; Lam, N.T.; Cong, V.H. Assessment of Cau River water quality assessment using a combination of water quality and pollution indices. J. Water Supply Res. Technol. 2020, 69, 160–172. [Google Scholar] [CrossRef]
66. Matta, G.; Kumar, A.; Nayak, A.; Kumar, P.; Kumar, A.; Tiwari, A.K. Water Quality and Planktonic Composition of River Henwal (India) Using Comprehensive Pollution Index and Biotic-Indices. Trans. Indian Natl. Acad. Eng. 2020, 5, 541–553. [Google Scholar] [CrossRef]
67. Goher, M.E.; Hassan, A.M.; Abdel-Moniem, I.A.; Fahmy, A.H.; El-Sayed, S.M. Evaluation of surface water quality and heavy metal indices of Ismailia Canal, Nile River, Egypt. Egypt. J. Aquat. Res. 2014, 40, 225–233. [Google Scholar] [CrossRef]
Figure 1. Box plot showing the quartiles and mean of the measured (a) chromium (total Cr), (b) trivalent Cr ((Cr(III)) and (c) hexavalent Cr ((Cr(VI)) values from the tannery industry wastewater samples collected from various tannery industries sites in summer and winter seasons from Punjab, Pakistan.
Figure 1. Box plot showing the quartiles and mean of the measured (a) chromium (total Cr), (b) trivalent Cr ((Cr(III)) and (c) hexavalent Cr ((Cr(VI)) values from the tannery industry wastewater samples collected from various tannery industries sites in summer and winter seasons from Punjab, Pakistan.
Figure 2. Piper plot showing the tannery industry wastewater chemistry of (a) summer (TWW-summer) and (b) winter (TWW-winter) season samples, collected from Kasur in Punjab, Pakistan.
Figure 2. Piper plot showing the tannery industry wastewater chemistry of (a) summer (TWW-summer) and (b) winter (TWW-winter) season samples, collected from Kasur in Punjab, Pakistan.
Figure 3. Loading plot of chromium (Cr) concentration and other physicochemical tannery industry wastewater parameters from Kasur, Punjab, Pakistan. (A) TWW-summer. (B) TWW-winter.
Figure 3. Loading plot of chromium (Cr) concentration and other physicochemical tannery industry wastewater parameters from Kasur, Punjab, Pakistan. (A) TWW-summer. (B) TWW-winter.
Figure 4. Eh-pH diagram for Cr-contaminated tannery wastewater collected in summer (a) Cr with other wastewater parameters and (b) Fe with other wastewater parameters); and winter (c) Cr with other wastewater parameters and (d) Fe with other wastewater parameters).
Figure 4. Eh-pH diagram for Cr-contaminated tannery wastewater collected in summer (a) Cr with other wastewater parameters and (b) Fe with other wastewater parameters); and winter (c) Cr with other wastewater parameters and (d) Fe with other wastewater parameters).
Table 1. Physico-chemical parameters of tannery wastewater collected in summer (TWW-summer) and winter (TWW-winter) seasons from the tannery industry area of Kasur, Punjab, Pakistan.
Table 1. Physico-chemical parameters of tannery wastewater collected in summer (TWW-summer) and winter (TWW-winter) seasons from the tannery industry area of Kasur, Punjab, Pakistan.
TWW-Summer Sampling: n = 82 TWW-Winter Sampling: n = 82
ParametersMeanMedianRangeS.D (±)MeanMedianRangeS.D (±)
pH<IP_ADDRESS>–8.80.9<IP_ADDRESS>–8.10.7
EC (mS/cm)<IP_ADDRESS>–24.46.2214.513.88.5–21.83.1
TDS (g/L)<IP_ADDRESS>–<IP_ADDRESS>.05.0–11.92.7
DO (mg/L)<IP_ADDRESS>–6.40.8<IP_ADDRESS>–6.40.8
Eh (mv)−3.4−20.3−74.5–19866.0−20.7−19.0−304–18099.1
Ca (mg/L)96.169.548.1–22053.297.584.248.1–21940.4
Mg (mg/L)477.3462.3257.7–1161165.1509.1483.1358–774112.4
Total hardness (mg/L)573.2531.7350.0–1380202.2606.7566.6433.3–993.3129.4
Na (mg/L)324.3295.9147.0–564.5127.5345.7351.0117–643122.1
K (mg/L)151.7129.462.9–28355.2184.6163.091.3–35463.6
CO3 (mg/L)512.8518.2192.0–750190.9622.1640.0260–870157.3
HCO3 (mg/L)3119.93105.92199–4270523.13301.73233.02623–4209491.0
Cl (mg/L)4136.64263.02408–5431773.54542.84431.63147–5739551.1
SO4 (mg/L)1033.2686.5446–4097881.11294.0922.5425–5161938.9
COD (mg/L)3340.42583.3471–92862654.73509.02324.0356–93973124.9
BOD (mg/L)1712.21416.6235–46931346.51954.01273.7178–54001758.7
Fe (mg/L)12.812.03.6–21.04.715.314.44.5–29.05.5
Mn (mg/L)<IP_ADDRESS>–<IP_ADDRESS>.32.1–11.62.1
Total Cr (mg/L)<IP_ADDRESS>–94.621.149.343.63.9–12532.2
Cr(VI) (mg/L)<IP_ADDRESS>–<IP_ADDRESS>.21.0–7.21.8
Cr(III) (mg/L)<IP_ADDRESS>–<IP_ADDRESS>8.82.5–12231.4
Note(s): TDS: total dissolved solids; DO: dissolved oxygen; Eh: redox potential; Ca: calcium; Mg: magnesium; Na: sodium; K: potassium; CO3: carbonates; HCO3: bicarbonates; Cl: chloride; SO4: sulfate; COD: chemical oxygen demand; BOD: biochemical oxygen demand; Fe: iron; Mn: manganese; Cr: chromium; Cr(VI): hexavalent Cr; and Cr(III): trivalent Cr. S.D ( ± ) indicates the standard deviation.
Table 2. Chromium concentration and maximum permissible limits for Cr and other wastewater quality parameters set by NEQS, WHO and USEPA.
Table 2. Chromium concentration and maximum permissible limits for Cr and other wastewater quality parameters set by NEQS, WHO and USEPA.
ParametersTWW-SummerNEQS Safe Limit% Number of
Samples >NEQS Limit
WHOUSEPATWW-
Winter
% Number of
Samples >NEQS Limit
pH7.36–1006–96–97.00
EC (mS/cm)8.7NG--1.014.5-
TDS (mg/L)420035003021005007600100
DO (mg/L)5.16–9.5---5.2-
Eh (mV)−3.4NG---−20-
Ca (mg/L)96NG---97-
Mg (mg/L)477NG- 509-
Total hardness (mg/L)573NG---606-
Na (mg/L)32425046--34584
K (mg/L)151NG---184-
CO3 (mg/L)512NG---622-
HCO3 (mg/L)3119NG---3301-
Cl (mg/L)41361000100--4542100
SO4 (mg/L)1033NG---1294-
COD (mg/L)33401501002505003509100
BOD (mg/L)171280100303001954100
Fe (mg/L)12.82.0100-5.015.3100
Mn (mg/L)2.81.580--5.3100
Total Cr (mg/L)15.01.01000.051.049100
Cr(VI) (mg/L)2.70.25100--2.9100
Cr(III) (mg/L)12.40.75100--46100
Note(s): TDS: total dissolved solids; DO: dissolved oxygen; Eh: redox potential; Ca: calcium; Mg: magnesium; Na: sodium; K: potassium; CO3: carbonates; HCO3: bicarbonates; Cl: chloride; SO4: sulfate; COD: chemical oxygen demand; BOD: biochemical oxygen demand; Fe: iron; Mn: manganese; Cr: chromium; Cr(VI): hexavalent Cr; Cr(III): trivalent Cr; NEQS: National Environmental Quality Standards of Pakistan; WHO: World Health Organization; and USEPA: United State of Environmental Protection Agency.
Table 3. Single-factor evaluation index (SFEI), CCI and HEI index of tannery wastewater collected from Kasur, Punjab Pakistan.
Table 3. Single-factor evaluation index (SFEI), CCI and HEI index of tannery wastewater collected from Kasur, Punjab Pakistan.
TWW-Summer
(n = 82)
TWW-Winter
(n = 82)
Single Factor Risk Category
ParametersSFEISFEI
TDS1.22.1SFEI > 1: Water is contaminated
Na1.31.4
Cl4.14.5
COD2223
BOD2124
Fe6.47.6
Mn1.93.5
Total Cr1549
Cr(VI)1011
Cr(III)1661
Total99189
CCI918
Tannery wastewater quality classVV
HEI2360
Chromium risk categoryHigh contaminationHigh contamination
Note(s): NG: Not given; TDS: total dissolved solids; Na: sodium; COD: chemical oxygen demand; BOD: biochemical oxygen demand; Fe: iron; Mn: manganese; Cr: chromium; Cr(VI): hexavalent Cr; Cr(III): trivalent Cr; SFEI: single-factor evaluation index; CCI: comprehensive water contamination index; and HEI: heavy metals index.
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content.
Share and Cite
MDPI and ACS Style
Younas, F.; Bibi, I.; Afzal, M.; Al-Misned, F.; Niazi, N.K.; Hussain, K.; Shahid, M.; Shakil, Q.; Ali, F.; Wang, H. Unveiling Distribution, Hydrogeochemical Behavior and Environmental Risk of Chromium in Tannery Wastewater. Water 2023, 15, 391. https://doi.org/10.3390/w15030391
AMA Style
Younas F, Bibi I, Afzal M, Al-Misned F, Niazi NK, Hussain K, Shahid M, Shakil Q, Ali F, Wang H. Unveiling Distribution, Hydrogeochemical Behavior and Environmental Risk of Chromium in Tannery Wastewater. Water. 2023; 15(3):391. https://doi.org/10.3390/w15030391
Chicago/Turabian Style
Younas, Fazila, Irshad Bibi, Muhammad Afzal, Fahad Al-Misned, Nabeel Khan Niazi, Khalid Hussain, Muhammad Shahid, Qamar Shakil, Fawad Ali, and Hailong Wang. 2023. "Unveiling Distribution, Hydrogeochemical Behavior and Environmental Risk of Chromium in Tannery Wastewater" Water 15, no. 3: 391. https://doi.org/10.3390/w15030391
Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.
Article Metrics
Back to TopTop
|
package <missing>;
public class GlobalMembers
{
public static int t = 1;
public static int Main()
{
int num = new int(int,int,int);
int n;
int k;
int num_mon;
int tot;
n = Integer.parseInt(ConsoleInput.readToWhiteSpace(true));
k = Integer.parseInt(ConsoleInput.readToWhiteSpace(true));
num_mon = n;
tot = num(n, k, num_mon);
System.out.print(tot);
System.out.print("\n");
return 0;
}
public static int num(int n,int k,int num_mon)
{
int tot;
if (num_mon == 0)
{
return t;
}
else
{
while (true)
{
tot = n * num(n, k, num_mon - 1) / (n - 1) + k;
if (num(n, k, num_mon - 1) % (n - 1) == 0)
{
return tot;
break;
}
else
{
t++;
}
}
}
}
}
|
# Lexus-GS450H-Inverter-Controller
Opensource controller for the Lexus GS450H Hybrid inverter and gearbox.
<br>
Controls the inverter using it's own OEM logic board. No modification required.
<br>
Connects to the gearbox and controls oil pump, gear shifting and temperature monitoring.
<br>
Only requires throttle and brake inputs from the vehicle but also has CAN capabilty for communicating with modern vehicles.
<br>
Big thanks to Tom Darby for figuring out the control protocol.
<br>
Thread on the openinverter.org forum : <br>
https://openinverter.org/forum/viewtopic.php?f=14&t=205
<br>
PCB files in Designspark PCB 8.1 format.
<br>
Copyright 2019 D.Maguire and T.Darby
<br>
<br>
29/09/19 : Initial commit.PCB design in progress.
<br>
<br>
27/10/19 : First successful test of the prototype running on the bench : https://youtu.be/F5XM6blwMlw
<br>
24/11/19 : Uploaded V3 software with reverse function. When IN1 is low motors run forward. when IN1 is pulled to +12v MG2 reverses.
21/01/2020 : Due to popular demand and a return to a no risk no reward culture, I have released the V2 design including the JLCPCB files so you can all take an arrow in back for me if I screwed up the design. In case anyone for some weird reason would like to support me why not buy a board from the EVBMW webshop : https://www.evbmw.com/index.php/evbmw-webshop
17/02/20 : WiFi interface files uploaded. Designed to run on the Olimex ESP8266 WiFi Module : <br>
https://www.olimex.com/Products/IoT/ESP8266/MOD-WIFI-ESP8266/open-source-hardware
<br>
|
Jeffrey MARCUS, Individually and On Behalf of All Others Similarly Situated v. BMW OF NORTH AMERICA, LLC; Bridgestone Americas Tire Operations, LLC, f/k/a Bridgestone Firestone North American Tire, LLC; Bridgestone Corporation Bridgestone Americas Tire Operations, LLC, f/k/a Bridgestone Firestone North American Tire, LLC; Bridgestone Corporation, Appellants (No. 11-1192) BMW of North America, LLC, Appellant (No. 11-1193).
Nos. 11-1192, 11-1193.
United States Court of Appeals, Third Circuit.
Argued Sept. 20, 2011.
Opinion filed Aug. 7, 2012.
Hugh R. Whiting, Esq., [Argued], Dustin B. Rawlin, Esq., Jones Day, Cleveland, OH, Counsel for Appellant, Bridgestone Corporation.
Susan T. Dwyer, Esq., Herrick Feinstein LLP, New York, NY, Ronald J. Levine, Esq., David R. King, Esq., Herrick Feinstein LLP, Princeton, NJ, Counsel for Appellant, Bridgestone Americas Tire Operations, LLC.
Rosemary J. Bruno, Esq., Christopher J. Dalton, Esq., [Argued], Buchanan Ingersoll & Rooney, Newark, NJ, Counsel for Appellant, BMW of North America, LLC.
Karin E. Fisch, Esq., [Argued], Orin Kurtz, Esq., Abbe, Spanier, Rodd & Abrams LLP, New York, NY, Alan E. Sash, Esq., Steven J. Hyman, Esq., McLaughlin & Stern, LLP, New York, NY, Counsel for Appellee, Jeffrey Marcus.
Before: AMBRO, CHAGARES, and ALDISERT, Circuit Judges.
OPINION OF THE COURT
AMBRO, Circuit Judge.
Table of Contents
I. Factual and Procedural Background..........................................588
II. Jurisdiction and Standard of Review..........................................590
III. Preliminary Matters........................................................590
A. The Class Definition and the Claims to be Given Class Treatment............591
B. Ascertainability........................................................592
IV.Rule 23(a).................................................................H94
A. Numerosity ........................................... ÜT ZD ^
B. Commonality.......................................... C7I to -q
C. Typicality............................................ CR zo -q
V. Rule 23(b)(3): Predominance.................................600
A. The Common Law Claims...............................600
1. Common Proof of Susceptibility to Road Hazard Damage......604
2. Common Proof of Proximate Causation...............603
B. The New Jersey Consumer Fraud Act Claim .............605
VI. Conclusion............................................... 05 I — *■ do
This class action involves run-flat tires (“RFTs”). As their name suggests, they can “run” while “flat.” Even if an RFT suffers a total and abrupt loss of air pressure from a puncture or other road damage, the vehicle it is on remains stable and can continue driving for 50 to 150 miles at a speed of up to 50 miles per hour.
Jeffrey Marcus leased a BMW convertible equipped with four Bridgestone RFTs. Unfortunately, he experienced four “flat” tires during his three-year lease. In each case, the RFT worked as intended. Even though the tire lost air pressure, Marcus was able to drive his car to a BMW dealer to have the tire replaced. Unsatisfied nonetheless, Marcus sued Bridgestone Corporation, Bridgestone Americas Tire Operations, LLC (“BATO”) (together “Bridgestone”), and BMW of North America, LLC (“BMW”), asserting consumer fraud, breach of warranty, and breach of contract claims. Among other things, he claims that Bridgestone RFTs are “defective” because they: (1) are “highly susceptible to flats, punctures and bubbles, and ... fail at a significantly higher rate than radial tires or other run-flat tires;” (2) cannot be repaired, only replaced, “in the event of a small puncture;” and (3) are “exorbitantly priced.” J.A. 91, 100, 102. He also claims RFT-equipped BMWs cannot be retrofitted to operate with conventional, non-run-flat tires, and that “many service stations do not sell” Bridgestone RFTs, making them difficult to replace. J.A. 91, 92. He faults BMW and Bridge-stone for failing to disclose these “defects.”
The District Court certified Marcus’s suit under Federal Rule of Civil Procedure 23(b)(3) as an opt-out class action brought on behalf of all purchasers and lessees of certain model-year BMWs equipped with Bridgestone RFTs sold or leased in New Jersey with tires that “have gone flat and been replaced.” For the reasons that follow, we part from the District Court. Among other problems, on the record before us, Marcus’s claims do not satisfy the numerosity and predominance requirements. We thus vacate the District Court’s certification order and remand for proceedings consistent with this opinion.
I. Factual and Procedural Background
In July 2007, Jeffrey Marcus (a New York resident) leased a 2007 BMW 328ci from an authorized BMW dealership in Ramsey, New Jersey. The convertible first caught his eye at another dealership in South Hampton, New York. He saw the car on the showroom floor and, interest piqued, picked up a brochure. Aside from visiting the dealership, picking up the brochure, and riding in a friend’s 328ci as a passenger, Marcus claims he “absolutely [did] not” do any other research on BMW vehicles or RFTs before leasing his car. J.A. 875.
As noted, Marcus suffered four “flat” tires during his three-year lease. Each time he experienced a flat, he drove his car to a BMW dealership in New York and had the tire replaced. BMW then billed Marcus between $350 to $390 for parts, labor, fees, and taxes. See J.A. 407-11. After his first flat, Marcus purchased a road-hazard warranty for about $400, which covered at least some of the replacement costs for flat tires two through four. See J.A. 880.
Marcus’s first two flat tires were not available for inspection in this lawsuit. Dealer records show that a nail punctured the first tire and the second was replaced due to a “blown out bubble.” J.A. 407-08. Marcus’s third, tire was replaced because he ran over a chunk of metal “the size of a finger,” according to his own expert, and his fourth because he ran over another sharp object that tore and gouged the tire and damaged the sidewall. J.A. 300. The parties’ experts agree that the third and fourth tires could not have been repaired, and that any tire (run-flat or conventional) would have been damaged, if not destroyed, under the circumstances. See J.A. 300, 414-15. They also agree on two other, more general propositions: (1) a tire can “go flat” or fail for a wide variety of reasons and not be a “defective” tire; and (2) to determine properly and accurately the cause of any particular tire failure, a careful and thorough examination of that tire is necessary. See J.A. 305, 399, 1476-77.
The parties dispute what Marcus knew about RFTs and RFT-equipped BMWs before leasing his car and, more importantly, what other purchasers and lessees could have known. To “provide a market and consumer perspective” on RFTs and BMWs, BMW presented the expert report and testimony of William Pettit. See J.A. 1761-76. He concluded that “[a]n abundance of [RFT] information exists in the public domain extolling the safety and convenience benefits and discussing potential downsides.” J.A. 1769. He pointed to BMW and Bridgestone documents (e.g., their press releases and marketing brochures), as well as information from the public domain (e.g., articles in publications like Consumer Reports, BusinessWeek, The Wall Street Journal, and The New York Times).
To take but a few examples, BMW boasts in its brochures that “should you get a flat, you can still travel up to 150 miles at 50 mph, thanks to [the 2007 BMW 3 Series Convertible’s] standard run-flat tires,” J.A. 329, “so you can drive off a busy highway, out of a dangerous area, or just continue on your journey on a rainy night,” J.A. 1108. In several other places, its brochures mention that the car comes equipped with RFTs and that, “[d]ue to low-profile tires, wheels, tires and suspension parts are more susceptible to road hazard and consequential damages.” J.A. 366, 374, 377, 380. A warning about road hazard susceptibility also appears in Bridgestone’s tire warranty — “low aspect ratio tires, with reduced sidewall height, may be more susceptible to damage from potholes, road hazards, and other objects such as curbs” — as well as in BMW press releases from July 2006 and March 2007. See J.A. 577, 579, 580, 993, 1449. In addition, the BMW Owner’s Manual for the 328i warns drivers that, “[fjor safety reasons, BMW recommends that damaged Run-Flat Tires be replaced rather than repaired.” J.A. 1558. BMW’s “Approved Tires” brochure similarly advises consumers that “[w]hile some tire manufacturers will allow tire repairs, BMW only recommends replacement of damaged tires.” J.A. 1092. BMW and Bridgestone also highlight information from the public domain. An April 2006 Business Week article says, “Run-flat tires aren’t cheap. Four Bridgestone Blizzak Run-Flats cost about $1,200, compared with perhaps $500 to $800 for comparable conventional tires.” J.A. 762. Sounding a similar note, an article from the June 2007 Consumer Reports mentions that some RFT owners have complained about “limited replacement choices” and “high replacement costs.” J.A. 961. However, this report concludes that “[d]espite the disadvantages and inconveniences of run-flat tires for many, Consumer Reports believes that the safety benefits can outweigh the downsides.” Id.
Marcus disputes BMW’s and Bridge-stone’s openness about RFTs, the information available in the public domain, and whether this information is sufficient to provide consumers with notice about the downsides of Bridgestone RFTs. He offers internal BMW and Bridgestone documents — such as emails, research reports and marketing surveys — to show that the defendants were aware that many other consumers were as displeased with RFTs as he was.
After his second flat tire, Marcus sued BMW and Bridgestone. In his Amended Class Action Complaint, he asserts claims against BMW and Bridgestone: (1) on behalf of a nationwide class, for breach of implied warranty in violation of the Magnuson Moss Warranty Act (“MMWA”); and (2) on behalf of a New Jersey subclass for (a) consumer fraud in violation of the New Jersey Consumer Fraud Act (“NJCFA”), (b) breach of implied warranty, (c) breach of contract, and (d) breach of the implied covenant of good faith and fair dealing. He also asserts a claim on behalf of the New Jersey sub-class for breach of express warranty against BMW.
The District Court denied Marcus’s motion for class certification with respect to the nationwide class, but granted the motion with respect to the New Jersey subclass. See Marcus v. BMW of N. Am., LLC, No. 08-5859(KSH), 2010 WL 4853308 (D.N.J. Nov. 19, 2010). The Court did not provide a definition of the class it certified, though it cross-referenced the docket entry for Marcus’s amended notice of motion for class certification. That notice sought certification of a
New Jersey state subclass consisting of [any] and [a]ll current and former owners and lessees of 2006, 2007, 2008, and 2009 BMW vehicles equipped with run-flat tires manufactured by Bridgestone and/or BATO and sold or leased in [New Jersey] whose Tires have gone flat and been replaced (excluded from the Class and the Sub-Class are Defendants, as well as Defendants’ affiliates, employees, officers and directors, including franchised dealers, and any person who has experienced physical injury as a result of the defects at issue in this litigation) ....
J.A. 198.
II. Jurisdiction and Standard of Review
The District Court had jurisdiction under 28 U.S.C. § 1332(d). Having granted BMW’s and Bridgestone’s petitions for leave to appeal under Federal Rule of Civil Procedure 23(f), we have appellate jurisdiction under 28 U.S.C. § 1292(e).
‘We review a class certification order for abuse of discretion, which occurs if the district court’s decision rests upon a clearly erroneous finding of fact, an errant conclusion of law or an improper application of law to fact.” In re Hydrogen Peroxide Antitrust Litig., 552 F.3d 305, 312 (3d Cir.2009) (quotation marks omitted). “[Wjhether an incorrect legal standard has been used is an issue of law to be reviewed de novo.” Id.
III. Preliminary Matters
“The class action is an exception to the usual rule that litigation is conducted by and on behalf of the individual named parties only.” Wal-Mart Stores v. Dukes, — U.S. -, 131 S.Ct. 2541, 2550, 180 L.Ed.2d 374 (2011) (quotation marks omitted). To invoke this exception, every putative class action must satisfy the four requirements of Rule 23(a) and the requirements of either Rule 23(b)(1), (2), or (3). See Fed.R.Civ.P. 23(a)-(b). To satisfy Rule 23(a),
(1) the class must be “so numerous that joinder of all members is impracticable” (numerosity); (2) there must be “questions of law or fact common to the class” (commonality); (3) “the claims or defenses of the representative parties” must be “typical of the claims or defenses of the class” (typicality); and (4) the named plaintiffs must “fairly and adequately protect the interests of the class” (adequacy of representation, or simply adequacy).
In re Cmty. Bank of N. Va., 622 F.3d 275, 291 (3d Cir.2010) (quoting Fed. R.Civ.P. 23). Rule 23(b)(3), the basis for certification here, “requires that (i) common questions of law or fact predominate (predominance), and (ii) the class action is the superior method for adjudication (superiority).” Id.
“[T]he requirements set out in Rule 23 are not mere pleading rules.” Hydrogen Peroxide, 552 F.3d at 316; see also Dukes, 131 S.Ct. at 2551. The party seeking certification bears the burden of establishing each element of Rule 23 by a preponderance of the evidence. See Hydrogen Peroxide, 552 F.3d at 307. Echoing the Supreme Court, we have repeatedly “emphasize[d] that ‘[ajctual, not presumed!,] conformance’ with Rule 23 requirements is essential.” Id. at 326 (quoting Newton v. Merrill Lynch, Pierce, Fenner & Smith, Inc., 259 F.3d 154, 167 (3d Cir.2001) (quoting Gen. Tel. Co. of the Sw. v. Falcon, 457 U.S. 147, 160, 102 S.Ct. 2364, 72 L.Ed.2d 740 (1982))).
To determine whether there is actual conformance with Rule 23, a district court must conduct a “rigorous analysis” of the evidence and arguments put forth. Id. at 316 (quoting Falcon, 457 U.S. at 161, 102 S.Ct. 2364). When doing so, the court cannot be bashful. It “must resolve all factual or legal disputes relevant to class certification, even if they overlap with the merits—including disputes touching on elements of the cause of action.” Id. at 307. Rule 23 gives no license to shy away from making factual findings that are necessary to determine whether the Rule’s requirements have been met.
Before considering Rule 23(a) and Rule 23(b)(3), we address two preliminary matters: (1) whether the District Court clearly defined the parameters of the class and the claims to be given class treatment, as required by Rule 23(c)(1)(B); and (2) whether the class must be (and, if so, is in fact) objectively ascertainable.
A. The Class Definition and the Claims to be Given Class Treatment
“An order that certifies a class action must define the class and the class claims, issues, or defenses.... ” Fed. R.Civ.P. 23(c)(1)(B). Specifically, “the text of the order or an incorporated opinion must include (1) a readily discernible, clear, and precise statement of the parameters defining the class or classes to be certified, and (2) a readily discernible, clear, and complete list of the claims, issues or defenses to be treated on a class basis.” Wachtel v. Guardian Life Ins. Co., 453 F.3d 179, 187 (3d Cir.2006). Clearly delineating the contours of the class along with the issues, claims, and defenses to be given class treatment serves several important purposes, such as providing the parties with clarity and assisting class members in understanding their rights and making informed opt-out decisions. Id.
The definition of the class certified here is not clear and precise. Rather than set out its own definition, the District Court noted in its certification order that “[certification of the New Jersey sub-class is granted [D.E. 144],” cross-referencing the docket entry for Marcus’s amended notice of motion for class certification. That notice sought certification of a
New Jersey state subclass consisting of [any] and [a]ll current and former owners and lessees of 2006, 2007, 2008, and 2009 BMW vehicles equipped with run-flat tires manufactured by Bridgestone and/or BATO and sold or leased in the United States whose Tires have gone flat and been replaced (excluded from the Class and the Sub-Class are Defendants, as well as Defendants’ affiliates, employees, officers and directors, including franchised dealers, and any person who has experienced physical injury as a result of the defects at issue in this litigation)....
J.A. 198. Although Marcus’s notice of motion defines the New Jersey subclass in terms of vehicles “sold or leased in the United States,” the Court mentions in its accompanying opinion that the subclass is “limited to those who bought or leased their cars in New Jersey.” Marcus, 2010 WL 4853308, at *1.
Even with this correction, however, the parameters of Marcus’s class definition are far from clear. As written, the definition seems to include not only (1) owners and lessees who bought or leased a new or used BMW from a New Jersey BMW dealership, but also (2) subsequent owners and lessees who bought or leased a used BMW in New Jersey from anyone, not just BMW dealers, and even (3) subsequent owners and lessees who bought or leased a used BMW anywhere in the country from anyone whose BMW was initially bought or leased in New Jersey. When confronted with this ambiguity at oral argument, Marcus’s counsel clarified that the “intent” was to include only owners and lessees of new BMWs purchased or leased in New Jersey from BMW dealerships with original-equipment Bridgestone RFTs. See Oral Arg. Tr. 20:19-:24. Even if the District Court shared counsel’s understanding of the class definition, counsel’s post hoc clarification is no substitute for a “readily discernible, clear, and precise statement of the parameters defining the class ... to be certified” in either the certification order or accompanying opinion. Wachtel, 453 F.3d at 187.
In addition, the certification order does not define the claims, issues, or defenses to be treated on a class basis at all. The District Court’s opinion does address Marcus’s claims and the issues presented, but we cannot find “a readily discernible, clear, and complete list.” Id.; see also id. at 189 (noting that an opinion that forces us to “comb the entirety of its text” and “cobble together the various statements” in search of “isolated statements that may add up to a partial list of class claims, issues, or defenses falls short of the readily discernible and complete list of class claims, issues, or defenses required by the Rule”).
Rule 23(c)(1)(B) requires more, and thus a remand. If Marcus continues to attempt to certify a class, he needs to provide the Court with a more clearly defined class and set of claims, issues, or defenses to be given class treatment.
B. Ascertainability
Many courts and commentators have recognized that an essential prerequisite of a class action, at least with respect to actions under Rule 23(b)(3), is that the class must be currently and readily ascertainable based on objective criteria. See, e.g., John v. Nat. Sec. Fire & Cas. Co., 501 F.3d 443, 445 (5th Cir.2007); In re Initial Pub. Offerings Sec. Litig., 471 F.3d 24, 30 (2d Cir.2006); Crosby v. Social Sec. Admin. of the U.S., 796 F.2d 576, 580 (1st Cir.1986); see also Chiang v. Veneman, 385 F.3d 256, 271 (3d Cir.2004) (holding that “defining a class by reference to those who ‘believe’ they were discriminated against undermines the validity of the class by introducing a subjective criterion into what should be an objective evaluation”), abrog. on other grounds by Hydrogen Peroxide, 552 F.3d at 318 n. 18; Johnson v. Geico Cas. Co., 673 F.Supp.2d 255, 268 (D.Del.2009); Agostino v. Quest Diagnostics, Inc., 256 F.R.D. 437, 478 (D.N.J. Feb. 11, 2009); 1 William B. Rubenstein et ah, Newberg on Class Actions, § 3:2-3:3 (5th ed.); 7A Charles Alan Wright et al., Federal Practice and Procedure § 1760 (3d ed. 2005). If class members are impossible to identify without extensive and individualized fact-finding or “mini-trials,” then a class action is inappropriate. Some courts have held that where nothing in company databases shows or-could show whether individuals should be included in the proposed class, the class definition fails. See Clavell v. Midland Funding LLC, No. 10-3593, 2011 WL 2462046, at *4 (E.D.Pa. June 21, 2011); Sadler v. Midland Credit Mgmt., Inc., No. 06-C-5045, 2008 WL 2692274, at *5 (N.D.Ill. July 3, 2008); In re Wal-Mart Stores, Inc. Wage & Hour Litig., No. C 06-2069 SBA, 2008 WL 413749, at *8 (N.D.Cal. Feb. 13, 2008); Deitz v. Comcast Corp., No. C 06-06352 WHA, 2007 WL 2015440, at *8 (N.D.Cal. July 11, 2007).
The ascertainability requirement serves several important objectives. First, it eliminates “serious administrative burdens that are incongruous with the efficiencies expected in a class action” by insisting on the easy identification of class members. Sanneman v. Chrysler Corp., 191 F.R.D. 441, 446 (E.D.Pa. Mar. 2, 2000). Second, it protects absent class members by facilitating the “best notice practicable” under Rule 23(c)(2) in a Rule 23(b)(3) action. See Manual for Complex Litigation, § 21.222 (4th ed. 2004). Third, it protects defendants by ensuring that those persons who will be bound by the final judgment are clearly identifiable. See Xavier v. Philip Morris USA, Inc., 787 F.Supp.2d 1075, 1089 (N.D.Cal.2011) (“Ascertainability is needed for properly enforcing the preclusive effect of final judgment. The class definition must be clear in its applicability so that it will be clear later on whose rights are merged into the judgment, that is, who gets the benefit of any relief and who gets the burden of any loss. If the definition is not clear in its applicability, then satellite litigation will be invited over who was in the class in the first place.”); 1 William B. Rubenstein et ah, Newberg on Class Actions, § 3:1 (5th ed.).
The proposed class raises serious ascertainability issues. In its briefs, BMW claims that it “may be able to identify current and former original owners and lessees of BMW vehicles factory-equipped with Bridgestone RFTS which were initially purchased or leased from New Jersey dealerships.” BMW Br. at 38 (emphasis in original); see also BMW Reply Br. 8. At oral argument, BMW’s counsel was even less optimistic. He suggested that BMW could not know which of the vehicles that fit the class definition had Bridgestone RFTs because “[tjhey’re made in Germany by a different company,” and BMW does not have a “parts manifest.” See Oral Arg. Tr. 16:3-16:8. To complicate matters further, not every car that comes onto a dealership lot with Bridgestone RFTs necessarily leaves the lot with the same tires. According to BMW, dealers might change the tires at a customer’s request. In any event, says BMW, even if the proper cars with the proper tires could be identified, defendants’ records would not indicate whether all potential class members’ Bridgestone RFTs “have gone flat and been replaced,” as the class definition requires, because the class is not limited to those persons who took their vehicles to BMW dealers to have their tires replaced.
If Marcus attempts to certify a class on remand, the District Court — adjusting the class definition as needed— must resolve the critical issue of whether the defendants’ records can ascertain class members and, if not, whether there is a reliable, administratively feasible alternative. We caution, however, against approving a method that would amount to no more than ascertaining by potential class members’ say so. For example, simply having potential class members submit affidavits that their Bridgestone RFTs have gone flat and been replaced may not be “proper or just.” See Xavier, 787 F.Supp.2d at 1089-90 (rejecting plaintiffs’ aseertainability proposal to have potential class members submit affidavits about their smoking histories). BMW and Bridgestone will be able to cross-examine Marcus at trial about whether and why his tires “have gone flat and been replaced.” Forcing BMW and Bridgestone to accept as true absent persons’ declarations that they are members of the class, without further indicia of reliability, would have serious due process implications.
IV. Rule 23(a)
A. Numerosity
Rule 23(a)(1), which requires that a class be “so numerous that joinder of all members is impracticable,” promotes three core objectives. First, it ensures judicial economy. It does so by freeing federal courts from the onerous rule of compulsory joinder inherited from the English Courts of Chancery and the law of equity. See 1 Rubenstein, supra, § 1:12. Courts no longer have to conduct a single, administratively burdensome action with all interested parties compelled to join and be present. Id. The impracticability of joinder, or numerosity, requirement also promotes judicial economy by sparing courts the burden of having to decide numerous, sufficiently similar individual actions seriatim. Id. at § 3:11. As for its second objective, Rule 23(a)(1) creates greater access to judicial relief, particularly for those persons with claims that would be uneconomical to litigate individually. See Phillips Petroleum Co. v. Shutts, 472 U.S. 797, 809, 105 S.Ct. 2965, 86 L.Ed.2d 628 (1985). Finally, the rule prevents putative class representatives and their counsel, when joinder can be easily accomplished, from unnecessarily depriving members of a small class of their right to a day in court to adjudicate their own claims. 7A Charles Alan Wright et al, Federal Practice and Procedure § 1762 (Sd ed. 2005).
There is no minimum number of members needed for a suit to proceed as a class action. See Stewart v. Abraham, 275 F.3d 220, 226-27 (3d Cir.2001). We have observed, however, that “generally if the named plaintiff demonstrates that the potential number of plaintiffs exceeds 40, the first prong of Rule 23(a) has been met.” Id. Nonetheless, Rule 23(a)(1) “requires examination of the specific facts of each case.” Gen. Tel. Co. of the N.W. v. EEOC, 446 U.S. 318, 330, 100 S.Ct. 1698, 64 L.Ed.2d 319 (1980). Critically, numerosity — like all Rule 23 requirements — must be proven by a preponderance of the evidence. See Hydrogen Peroxide, 552 F.3d at 307.
When a plaintiff attempts to certify both a nationwide class and a state-specific subclass, as Marcus did here, evidence that is sufficient to establish numerosity with respect to the nationwide class is not necessarily sufficient to establish numerosity with respect to the state-specific subclass. The Court of Appeals for the Eleventh Circuit’s decision in Vega v. T-Mobile USA, Inc. is particularly instructive on this point. 564 F.3d 1256, 1266-68 (11th Cir.2009). There, the Court reversed a finding of numerosity concerning a proposed class of all T-Mobile employees in Florida who received commissions for the sale of cellphone plans. It held that the plaintiff could not simply rely on the nationwide presence of T-Mobile to satisfy the numerosity requirement without Florida-specific evidence:
Vega has not cited, and we cannot locate in the record, any evidence whatsoever (or even an allegation) of the number of retail sales associates T-Mobile employed during the class period in Florida who would comprise the membership of the class, as certified by the district court.
Yes, T-Mobile is a large company, with many retail outlets, and, as such, it might be tempting to assume that the number of retail sales associates the company employed in Florida during the relevant period can overcome the generally low hurdle presented by Rule 23(a)(1). However, a plaintiff still bears the burden of establishing every element of Rule 23, and a district court’s factual findings must find support in the evidence before it. In this case, the district court’s inference of numerosity for a Florida-only class without the aid of a shred of Florida-only evidence was an exercise in sheer speculation.
Id. at 1267 (emphasis added) (citations and footnotes omitted).
Like Vega, Marcus offered sufficient company-wide evidence to the District Court to support a finding of numerosity for a nationwide class. According to BMW, it sold or leased 740,102 vehicles equipped with RFTs nationwide during the class period. But not all those vehicles came with Bridgestone RFTs. The group includes cars with RFTs from seven different manufacturers — Goodyear, Pirelli, Michelin, Dunlop, Continental, Uniroyal, and Bridgestone. With respect to these 740,102 vehicles, BMW recorded and produced 582 unique customer contacts from consumers across the nation who called BMW to complain about their RFTs. Of those 582 customers, 196 specifically identified their RFTs as Bridgestone RFTs. Marcus submitted 29 of the 582 complaints as evidence of the proposed nationwide class’s numerosity. In addition, he submitted records, obtained from various companies offering road hazard products, showing thousands of claims made for road hazard damage on 2006-2009 BMW vehicles. He even provided loss-ratio data (the ratio of dollars received in premiums to dollars paid out in claims) for one warranty company’s contracts covering BMWs. Piled on top of that were internal BMW emails about customer complaints regarding Bridgestone RFTs.
But after digging through this supposed mountain of evidence, we can only speculate as to how many 2006-2009 BMWs were purchased or leased in New Jersey with Bridgestone RFTs that have gone flat and been replaced. To begin, we can only guess as to how many 2006-2009 BMWs were purchased or leased in New Jersey regardless of tire brand. That information is not in the record. There is also no evidence of how many of the 740,-102 vehicles bought and leased nationwide had Bridgestone RFTs. No evidence shows that BMW purchased tires from its seven RFT-suppliers in roughly equal proportions or even if Bridgestone was among its larger or smaller suppliers. As noted, Marcus submitted 29 of the 582 nationwide complaints as evidence of numerosity. The complaints, however, do not indicate in any readily apparent way whether the complaining customers purchased or leased their vehicles in New Jersey. Four complaining customers did list New Jersey addresses. See J.A. 1612,1632,1634,1636. But only two of these four customers referred to Bridgestone RFTs specifically, and one of them apparently accepted $500 in “Lifestyle Gifts” as a settlement from BMW. See J.A. 1634, 1636-43. And, like Marcus, they could have crossed state lines to purchase or lease their cars. Not to pile on, but Marcus has not pointed us to any evidence in the record — not in the customer complaints, the road hazard warranty claims, the loss-ratio data, or the internal BMW emails — that identifies another purchaser or lessee of a 2006-2009 BMW that was sold or leased in New Jersey and equipped with Bridgestone RFTs that have gone flat and been replaced. In short, he has offered proof of only one potential class member: himself.
Nonetheless, the District Court found that the New Jersey class met the numerosity requirement because “it is common sense that there will be more members of the class than the number of consumers who complained — probably significantly more,” and “common sense indicates that there will be at least 40.” Marcus, 2010 WL 4853308, at *3. That may be a bet worth making, but it cannot support a finding of numerosity sufficient for Rule 23(a)(1).
As we explained in Hydrogen Peroxide, a district court must make a factual determination, based on the preponderance of the evidence, that Rule 23’s requirements have been met. See 552 F.3d at 307. Mere speculation is insufficient. See 7A Wright, supra, § 1762 (collecting cases); Roe v. Town of Highland, 909 F.2d 1097, 1100 n. 4 (7th Cir.1990) (“The party supporting the class cannot rely on conclusory allegations that joinder is impractical or on speculation as to the size of the class in order to prove numerosity.”) (quotation marks omitted). Of course, Rule 23(a)(1) does not require a plaintiff to offer direct evidence of the exact number and identities of the class members. But in the absence of direct evidence, a plaintiff must show sufficient circumstantial evidence specific to the products, problems, parties, and geographic areas actually covered by the class definition to allow a district court to make a factual finding. Only then may the court rely on “common sense” to forgo precise calculations and exact numbers. See In re Prudential Ins. Co. of Am. Sales Practices Litig., 962 F.Supp. 450, 468, 510 (D.N.J.1997), aff'd 148 F.3d 283 (3d Cir. 1998) (finding numerosity requirement satisfied without pinpointing an exact number because the evidence suggested a class of over 8,000,000 policyholders and “[c]ommon sense suggested] that it would be at best extremely inconvenient to join all class members”); cf. Lloyd v. City of Phila., 121 F.R.D. 246, 249 (E.D.Pa. Aug. 22, 1988) (refusing to certify a class when, despite plaintiffs “mere speculation” that the class could exceed 10,000 employees, the evidence demonstrated that only the four plaintiffs met the class definition).
Given the complete lack of evidence specific to BMWs purchased or leased in New Jersey with Bridgestone RFTs that have gone flat and been replaced, the District Court’s numerosity ruling crossed the line separating inference and speculation. BMW is a large company that sells and leases many cars throughout the country, many with RFTs. But the Court did not certify a nationwide class of BMW owners and lessees with any brand of RFTs. It certified a New Jersey class of owners and lessees with Bridgestone RFTs that have gone flat and been replaced. It is tempting to assume that the New Jersey class meets the numerosity requirement based on the defendant companies’ nationwide presence. But the only fact with respect to numerosity proven by a preponderance of the evidence is that Marcus himself is a member of the proposed class. “[I]f there are no members of the class other than the named representatives, then Rule 23(a)(1) obviously has not been satisfied.” 7A Wright, supra, § 1762. And “we are not prepared to read the numerosity requirement out of the class action rule,” as we have no authority to do so. Gurmankin v. Costanzo, 626 F.2d 1132, 1135 (3d Cir. 1980). Accordingly, we hold that the District Court abused its discretion by finding the numerosity requirement to be satisfied with respect to the New Jersey class.
B. Commonality
Rule 23(a)(2)’s commonality requirement “does not require identical claims or facts among class member[s].” Chiang v. Veneman, 385 F.3d 256, 265 (3d Cir.2004), abrog. on other grounds by Hydrogen Peroxide, 552 F.3d at 318 n. 18. “For purposes of Rule 23(a)(2), even a single common question will do.” Dukes, 131 S.Ct. at 2556 (quotation marks and alterations omitted); see also In re Schering Plough Corp. ERISA Litig., 589 F.3d 585, 597 (3d Cir.2009).
Marcus seeks to offer evidence about, among other things, whether Bridgestone RFTs are “defective,” whether the defendants had a duty to disclose those defects, and whether the defendants did in fact fail to disclose those defects. These issues of fact and law (or some subset of them) apply to each of Marcus’s causes of actions against each of the defendants, and are issues common to all class members. Accordingly, the District Court did not abuse its discretion in finding the commonality requirement to be satisfied.
C. Typicality
The concepts of typicality and commonality are closely related and often tend to merge. See Baby Neal v. Casey, 43 F.3d 48, 56 (3d Cir.1994). “Both serve as guideposts for determining whether under the particular circumstances maintenance of a class action is economical and whether the named plaintiffs claim and the class claims are so interrelated that the interests of the class members will be fairly and adequately protected in their absence.” Falcon, 457 U.S. at 158 n. 13, 102 S.Ct. 2364. Typicality, however, derives its independent legal significance from its ability to “screen out class actions in which the legal or factual position of the representatives is markedly different from that of other members of the class even though common issues of law or fact are present.” 7A Wright, supra, § 1764.
To determine whether a plaintiff is markedly different from the class as a whole, we consider the attributes of the plaintiff, the class as a whole, and the similarity between the plaintiff and the class. See Schering Plough, 589 F.3d at 597. This comparative analysis addresses
three distinct, though related, concerns: (1) the claims of the class representative must be generally the same as those of the class in terms of both (a) the legal theory advanced and (b) the factual circumstances underlying that theory; (2) the class representative must not be subject to a defense that is both inapplicable to many members of the class and likely to become a major focus of the litigation; and (3) the interests and incentives of the representative must be sufficiently aligned with those of the class.
Id. at 599. If a plaintiffs claim arises from the same event, practice or course of conduct that gives rises to the claims of the class members, factual differences will not render that claim atypical if it is based on the same legal theory as the claims of the class. Hoxworth v. Blinder, Robinson & Co., 980 F.2d 912, 923 (3d Cir.1992).
The District Court found that Marcus is typical of the class, because “[w]hat is crucial to the typicality analysis here is that Marcus and the class members purportedly suffered harm from the same alleged course of conduct: the defendants failed to disclose defects in their products, misrepresented or omitted important information about the products, and made promises about the products that were not true.” Marcus, 2010 WL 4853308, at *6. BMW and Bridgestone argue that the Court erred in its finding for three reasons. First, Marcus performed very little research before leasing his car, whereas the average BMW purchaser or lessee performs significant research prior to purchase or lease. Second, Marcus leased only one model BMW with one kind of Bridgestone RFT, yet he seeks to represent a class composed of people with other model-year BMWs and Bridgestone tire types. According to Bridgestone, Marcus’s claims potentially cover 49 different tire designs of varying specifications, including size, load rating, and model type. Third, New York law — not New Jersey law — applies to Marcus’s claims and, as a result, Marcus is subject to unique defenses that do not apply to all members of the proposed class. We see no abuse of discretion behind any of these arguments.
First, even if there are marked differences in the amounts of research class members performed, these differences by themselves do not render Marcus’s claims atypical. As discussed below, if a class member knew about the alleged “defects” prior to purchase or lease, then that knowledge could break the proximate cause link between the alleged defect and any damages suffered. Determining whether a class member had such knowledge requires an individualized inquiry. That creates a predominance problem. If Marcus knew of the defects prior to his lease, then he would risk having the causal link between the defendants’ conduct and his damages broken. If that were so, he would be unable to represent fairly the interests of class members who did not have such knowledge. That would create a typicality problem. But Marcus may be in a better position than other potential class members because he did not do significant research before leasing his car. That fact may distinguish him from other class members, but it does not prejudice his ability to protect absent class members’ interests fairly and adequately.
The fact that Marcus leased only one model BMW with one kind of Bridgestone RFT also does not pose a typicality problem. When a class includes purchasers of a variety of different products, a named plaintiff that purchases only one type of product satisfies the typicality requirement if the alleged misrepresentations or omissions apply uniformly across the different product types. See, e.g., Wiener v. Dannon Co., 255 F.R.D. 658, 666-67 (C.D.Cal. Jan. 30, 2009); Gonzalez v. Proctor & Gamble Co., 247 F.R.D. 616, 621-22 (S.D.Cal. Sept. 12, 2007); Lewis Tree Serv. Inc. v. Lucent Techs. Inc., 211 F.R.D. 228, 232-34 (S.D.N.Y. Nov. 20, 2002); Kaczmarek v. Int’ Bus. Machs. Corp., 186 F.R.D. 307, 313 (S.D.N.Y. May 12, 1999). The parties agree that different tire models and sizes, and different vehicles, have different performance characteristics, compositions, designs, purposes, and uses. But Marcus alleges that the problems with Bridgestone RFTs — that they are highly susceptible to road hazard damage, unrepairable, expensive, difficult to purchase, and that a vehicle cannot be converted for use of conventional tires — are uniform and apply to all 2006-2009 BMW vehicles equipped with Bridgestone RFTs.
As we discuss below with respect to predominance, the District Court did not abuse its discretion when finding that a defect making Bridgestone RFTs highly susceptible to road hazard damage will show itself in a substantially similar way across the various tire models and sizes at issue here. Nor is there any indication that BMW’s and Bridgestone’s representations differed significantly depending on the model-year BMW or specification of Bridgestone RFT. Therefore, the fact that Marcus leased only one model BMW with one kind of Bridgestone RFT does not pose a typicality problem.
Finally, “[i]t is well-established that a proposed class representative is not ‘typical’ under Rule 23(a)(3) if ‘the representative is subject to a unique defense that is likely to become a major focus of the litigation.’ ” Schering Plough, 589 F.3d at 598 (quoting Beck v. Maximus, Inc., 457 F.3d 291, 301 (3d Cir.2006)). “Other courts of appeals emphasize, as do we, the challenge presented by a defense unique to a class representative — the representative’s interests might not be aligned with those of the class, and the representative might devote time and effort to the defense at the expense of issues that are common and controlling for the class.” Beck, 457 F.3d at 297. Here, BMW and Bridgestone argue that New York law, not New Jersey law, applies to Marcus’s claims and, along with it, certain unique defenses. For example, they claim that New York law, unlike New Jersey law, requires privity of contract in order to pursue a claim for breach of implied warranty. Compare Arthur Jaffee Assocs. v. Bilsco Auto Serv. Inc., 89 A.D.2d 785, 785, 453 N.Y.S.2d 501 (App. Div.1982), aff'd 58 N.Y.2d 993, 461 N.Y.S.2d 1007, 448 N.E.2d 792, 792 (1983), with Paramount Aviation Corp. v. Agusta, 288 F.3d 67, 73-76 (3d Cir.2002) (applying New Jersey law).
The defendants presented this argument to the District Court, but it did not respond to it. The Court did conduct a choice-of-law analysis with respect to the class members’ MMWA claims when considering issues of predominance. It did not, however, conduct a choice-of-law analysis with respect to Marcus’s consumer fraud or common law claims when considering issues of typicality, specifically whether Marcus’s claims are subject to unique defenses that are likely to become a major focus of the litigation. But even if New York, rather than New Jersey, law applies to Marcus’s claims, BMW and Bridgestone have failed to demonstrate how any defenses unique to Marcus’s claims will become a major focus of the litigation. On remand, the parties and the District Court may find that the contours of the litigation have changed significantly and what will or will not likely be a major focus of the litigation will have to be assessed. We leave this to the District Court to address when and if the issue should arise.
V. Rule 23(b)(3): Predominance
Under Rule 23(b)(3), “questions of law or fact common to class members [must] predominate over any questions affecting only individual members.” This predominance requirement “tests whether proposed classes are sufficiently cohesive to warrant adjudication by representation.” Amchem Prods., Inc. v. Windsor, 521 U.S. 591, 623, 117 S.Ct. 2231, 138 L.Ed.2d 689 (1997). To assess predominance, a court at the certification stage must examine each element of a legal claim “through the prism” of Rule 23(b)(3). In re DVI, Inc. Sec. Litig., 639 F.3d 623, 630 (3d Cir.2011). A plaintiff must “demonstrate that the element of [the legal claim] is capable of proof at trial through evidence that is common to the class rather than individual to its members.” Hydrogen Peroxide, 552 F.3d at 311. “Because the nature of the evidence that will suffice to resolve a question determines whether the question is common or individual, a district court must formulate some prediction as to how specific issues will play out in order to determine whether common or individual issues predominate in a given case.” Id. (quotation marks omitted).
Marcus asserts four claims on behalf of the New Jersey class against BMW and Bridgestone: (1) violations of the NJCFA; (2) breach of the implied warranty of merchantability; (3) breach of contract; and (4) breach of the implied covenant of good faith and fair dealing. He also asserts a claim for breach of express warranty against BMW. We consider the elements of these claims through the prism of the predominance requirement to determine whether they are capable of proof with common, class-wide evidence.
A. The Common Law Claims
The essence of each of Marcus’s common law claims (at least for purposes of our predominance analysis) is that he purchased a defective product that caused him damage. In his complaint, Marcus alleges that Bridgestone RFTs (and, in turn, the BMW vehicles that they equip) are defective for several reasons: (1) Bridgestone RFTs pop or sustain bubbles from use under normal driving conditions, making them more susceptible to road hazard damage than conventional tires and other brands of RFTs; (2) they cannot be repaired in the event of even a small puncture; and (3) they are extremely expensive to replace. In addition, he alleges that his BMW vehicle is defective because it cannot be reconfigured to operate with conventional tires.
The District Court found that Marcus could prove these alleged defects at trial with common, class-wide evidence. BMW and Bridgestone contest the Court’s finding with respect to the first alleged defect. They also argue that issues of proximate causation — ie., determining why each class member’s tires “have gone and been replaced” — will require individualized inquiries that will predominate over any common ones.
1. Common Proof of Susceptibility to Road Hazard Damage
According to BMW and Bridgestone, Marcus has failed to identify any partieular defect that supposedly makes Bridge-stone RFTs more susceptible to road hazard damage than other tires. In addition, they claim that any defect — should one exist at all — will not be evident uniformly across all tires, regardless of size or other specifications, included in the class definition. They argue that the District Court erred by accepting without question Marcus’s expert testimony on these points without considering their own.
In In re Hydrogen Peroxide Antitrust Litigation, we clarified a district court’s duty when confronted with competing expert testimony about a plaintiffs ability to prove a claim through evidence that is common to the class. 552 F.3d at 307, 322-24. We held that “the court’s obligation to consider all relevant evidence and arguments [on a motion for class certification] extends to expert testimony, whether offered by a party seeking class certification or by a party opposing it.” Id. at 307. We explained that “[e]xpert opinion with respect to class certification, like any matter relevant to a Rule 23 requirement, calls for rigorous analysis.” Id. at 323. Therefore, “[wjeighing conflicting expert testimony at the certification stage is not only permissible[, but] it may be integral to the rigorous analysis Rule 23 demands,” especially when a party opposing certification offers its own competing expert opinion. Id. We further assured district courts that “[r]igorous analysis need not be hampered by a concern for avoiding credibility issues.” Id. at 324. In that case, we ruled that the district court abused its discretion because it appeared to have assumed that it was barred from weighing one expert opinion against another for the purpose of determining whether the requirements of Rule 23 had been met, specifically whether the plaintiffs claims were susceptible to common proof. Id. at 322.
Like the District Court in Hydrogen Peroxide, the District Court here was confronted with conflicting expert testimony about whether the plaintiff could prove its claim with common proof. On the one hand, Marcus’s tire expert, Charles Gold, opined on the similarity of Bridgestone RFTs. After “a detailed analysis of the thousands of pages of specifications produced,” he found that “all Bridgestone run-flat tires relevant to this action, despite variations due to size, are substantially similar in construction.” J.A. 1978-79. He concluded that “a proven defect arising from construction would manifest itself in all relevant tires.” J.A. 1979. In addition, Gold suggests in his expert report that not only would all Bridgestone RFTs have a similar defect, but in fact they all do have a particular defect. He explains that the major difference between RFTs and conventional tires is the inclusion of extra components added to the sidewall and assemblies of RFTs, allowing RFTs to be operated at zero, or near zero, inflation pressure. J.A. 1978. “Unfortunately,” he adds, these same components stiffen the tire during regular inflated use and “[t]he extra stiffness [in RFTs] can make the tire more susceptible to road hazard damages during normal use.” J.A. 1978-1979.
BMW and Bridgestone counter by highlighting that Gold recanted his “extra stiffness” opinion during his deposition. He admitted he had no published testing, studies or scientific data to support his opinion. J.A. 2031-32. In fact, Gold admitted that he “cannot offer an opinion, to a reasonable degree of engineering certainty, that Bridgestone RFTs are more susceptible to road-hazard damage during normal use.” J.A. 2074-75. When Bridgestone and BMW moved to exclude Gold’s opinion, Marcus too seems to have changed course with respect to the “stiffness” theory. Rather than rely on that theory, he argued (and still argues now) that Bridgestone RFTs are more susceptible to road hazard damage because they are “low aspect ratio” tires and that proof of this “defect” is found in the defendants’ own documents, not in any expert report. Marcus Br. 27-28; J.A. 2138.
Despite this apparent retreat from Gold’s “stiffness” theory, the District Court found that Marcus “has offered evidence that because run-flat tires are, universally, substantially stiffer than conventional tires, they are therefore more susceptible to road hazard damage. Such evidence makes it likely that common issues of proof will establish the class members’ claims.” Marcus, 2010 WL 4853308, at *13. Ultimately, however, whether Bridgestone RFTs are more susceptible to road hazard damage than other tires — due to their “extra stiffness,” their low aspect ratio, or anything else— is not the issue before us. Our inquiry is limited to whether the District Court abused its discretion when finding that, should a defect exist at all in Bridgestone RFTs that makes them more susceptible to road hazard damage, Marcus will be capable of proving that defect at trial through evidence that is common to the class rather than individual to its members. See Hydrogen Peroxide, 552 F.3d at 311.
On this point, the Court discussed and apparently credited Gold’s similarity opinion. Marcus, 2010 WL 4853308, at *4, *5 (noting that Marcus “will also offer Gold’s expert testimony that all Bridgestone run-flat tires, regardless of model, are substantially similar” and that “Gold’s expert testimony opines that all of Bridgestone’s run-flat tires are substantially similar, irrespective of model”). Bridgestone offered its own expert evidence (reports and deposition testimony from its experts, Brian Queiser and James Gardner) that the different tires and sizes in the class are not substantially similar given the differences in design, components and materials in different tires specified as standard and optional equipment for different BMW vehicles. J.A. 399; 401-06; 413-15; 424-26; 452-53. The District Court did not explicitly discuss these expert opinions, which challenge the similarity opinion of Marcus’s expert.
Although we would prefer a more explicit discussion and comparison of Bridgestone’s competing expert testimony from the District Court to aid our appellate review, we cannot conclude that the Court abused its discretion in violation of Hydrogen Peroxide. Unlike the District Court’s opinion in Hydrogen Peroxide, nothing in the District Court’s opinion in our case suggests that it assumed it was barred from weighing the credibility of the expert opinions. Instead, it appears that the Court — consistent with Hydrogen Peroxide — simply found Gold’s opinion about the similarity of Bridgestone RFTs to be more persuasive than the opinions put forth by Bridgestone. This was not an abuse of discretion.
2. Common Proof of Proximate Causation
Having found that Marcus could show a common, class-wide defect, the District Court then found he could show, without resort to individual proofs, that this defect caused the class members’ damages. Considering the damages that Marcus alleges, we believe the District Court’s causation finding was an abuse of discretion.
Recall that Marcus defines the class in terms of certain owners and lessees of BMW vehicles with Bridgestone RFTs that “have gone flat and been replaced.” He claims that “[a]ll class members were damaged when their tires suffered a flat and they were forced to pay for a new Tire or when they purchased road hazard coverage to insulate them from financial hardship due to cost of the Tires.” Pi’s Am. Br. in Support of Class Cert. (J.A. 1255). Accordingly, he asserts that “[e]ach Class member’s damages can be measured by the cost of a replacement Tire. For Class members who purchased road hazard coverage, the damages will be the greater of either the cost of replacement Tires or the cost of road hazard coverage.” Id. at 1253-54.
But these damages allegations beg the question of what caused class members’ tires to go flat and need replacement. Causation is pivotal to each of Marcus’s claims. See, e.g., N.J. Stat. Ann. § 12A:2-314 cmt. 13 (discussing how, in an action based on breach of warranty, “it is of course necessary to show ... that the breach of warranty was the proximate cause of the loss sustained,” and that “an affirmative showing by the seller that the loss resulted from some action or event following his own delivery of the goods can operate as a defense”). Here the District Court should have addressed an undisputed, fundamental point: any tire can “go flat” for myriad reasons. See J.A. 307-308, 448. Even “defective” tires can go flat for reasons completely unrelated to their defects. Critically, to determine why a particular class member’s Bridgestone RFT has “gone flat and been replaced” requires an individual examination of that class member’s tire. See J.A. 305, 399, 1476-77. These individual inquiries are incompatible with Rule 23(b)(3)’s predominance requirement.
In another RFT case brought against BMW and Goodyear involving nearly identical allegations as those Marcus makes here, Judge Holwell of the United States District Court for Southern District of New York denied class certification and aptly explained why individual issues of causation create irremediable predominance problems:
Even if the plaintiffs were to show that the Goodyear RFTs suffered from a common defect, they would still need to demonstrate that this defect caused each class member’s RFT to puncture. But tires can puncture for any number of reasons, and not all of these reasons will relate to the defect. As defendants properly note, RFTs can go flat for reasons that would also cause a standard radial tire to go flat, for example, if the driver ran over a nail, tire shredding device, or large pothole, or if a vandal slashed the tire.... [P]laintiff would have to demonstrate in each individual case that the tire punctured for reasons reláted to the defect, rather than for a reason that would cause any tire to fail.
Oscar v. BMW of N. Am., LLC, 274 F.R.D. 498, 511 (S.D.N.Y. June 7, 2011) (“Oscar I”). Other federal courts have also recognized that suits alleging defects “involving motor vehicles often involve complicated issues of individual causation that predominate over common questions regarding the existence of a defect.” Id. at 510 (collecting cases); see also Chin v. Chrysler Corp., 182 F.R.D. 448, 455 (D.N.J. Sept. 11, 1998) (refusing to certify a class of purchasers and lessee of vehicles with allegedly defective anti-lock brake systems because, among other things, “[e]ven where the alleged defect has manifested itself, individual issues of actual cause must be adjudicated”).
Marcus’s own experience illustrates the problem. Of the two tires he presented for inspection in this lawsuit, one went “flat” and was replaced because he ran over a jagged chunk of metal and the other because he ran over a sharp object that tore and gouged the tire and damaged the sidewall. See J.A. 300, 400, 409-10. The experts agree that the two tires could not have been repaired and that any tire (run-flat or conventional) would also have been damaged under the circumstances. See J.A. 309-10, 400, 412, 414, 426. In other words, it is undisputed that even if Marcus could prove that Bridgestone RFTs suffer from common, class-wide defects, those defects did not cause the damage he suffered for these two tires: the need to replace them. In this sense, Marcus is no different than a class member who, seconds after buying his car, pulls off the dealership lot and runs over a bed of nails, as neither can claim a “defect” caused his tires to go flat and need replacement. Because Marcus’s common law claims require an individualized inquiry into why any particular consumer’s Bridgestone RFTs went flat and had to be replaced, the District Court abused its discretion in finding that the claims satisfy the predominance requirement.
B. The New Jersey Consumer Fraud Act Claims
Next, we turn to the District Court’s certification of Marcus’s NJCFA claims. At the outset, it is important to disentangle two fundamental questions that are at the core of the District Court’s analysis but that can be conflated: (1) Under New Jersey law, what must a plaintiff prove to succeed on an NJCFA claim and what evidence can a defendant put forth to rebut and defeat that claim?; and (2) When a plaintiff seeks to certify an NJCFA claim for class treatment under Rule 23(b)(3), when might common questions of fact fail to predominate over individual ones?
We begin with examining the elements of a NJCFA claim. The NJCFA prohibits certain deceptive commercial behavior that it calls “unlawful practice^].”
The act, use or employment by any person of any unconscionable commercial practice, deception, fraud, false pretense, false promise, misrepresentation, or the knowing, concealment, suppression, or omission of any material fact with intent that others rely upon such concealment, suppression or omission, in connection with the sale or advertisement of any merchandise or real estate, or with the subsequent performance of such person as aforesaid, whether or not any person has in fact been misled, deceived or damaged thereby, is declared to be an unlawful practice....
N.J. Stat. Ann. § 56:8-2. The Attorney General of New Jersey may take action under the NJCFA to address an “unlawful practice” and, in doing so, “does not have to prove that the victim of the fraudulent conduct had ‘in fact been misled, deceived or damaged thereby....’” Meshinsky v. Nichols Yacht Sales, Inc., 110 N.J. 464, 541 A.2d 1063, 1067 (1988).
A private plaintiff, however, must do more than prove an “unlawful practice.” Another section of the NJCFA provides that
[a]ny person who suffers any ascertainable loss of moneys or property, real or personal, as a result of the use or employment by another person of any method, act, or practice declared unlawful under this act or the act hereby amended and supplemented may bring an action or assert a counterclaim therefor in any court of competent jurisdiction.
N.J. Stat. Ann. § 56:8-19 (emphases added). So, “[w]hile the Attorney General does not have to prove that the victim was damaged by the unlawful conduct, a private plaintiff must show that he or she suffered an ‘ascertainable loss ... as a result of the unlawful conduct.” Meshinsky, 541 A.2d at 1067.
An “ascertainable loss” is “either an out-of-pocket loss or a demonstration of loss in value” that is “quantifiable or measurable.” Thiedemann v. Mercedes-Benz U.S.A., LLC, 183 N.J. 234, 872 A.2d 783, 792-93 (2005). Put differently, a plaintiff is not required to show monetary loss, but only that he purchased something and received “less than what was promised.” Union Ink Co., Inc. v. AT&T Corp., 352 N.J.Super. 617, 801 A.2d 361, 379 (N.J.Super.Ct.App.Div.2002); see also In re Mercedes-Benz Tele Aid Contract Litig., 257 F.R.D. 46, 73 (D.N.J. Apr. 24, 2009) (“[T]he sum of each class member’s loss is the amount necessary to fulfill his or her expectation of a functioning [product].)”.
Importantly, unlike common law fraud, the NJCFA does not require proof of reliance. See Gennari v. Weichert Co. Realtors, 148 N.J. 582, 691 A.2d 350, 366 (1997). That is, it does not require proof that a consumer would not have purchased a product absent the alleged unlawful practice or even proof that the unlawful practice played a substantial part in his or her decisionmaking. Cf. Restatement (Second) of Torts § 546. Nonetheless, “the CFA requires a consumer to prove that [his or her] loss is attributable to the conduct that the CFA seeks to punish by including a limitation expressed as a causal link.” Bosland v. Wamock Dodge, Inc., 197 N.J. 543, 964 A.2d 741, 748 (2009); see also Meshinsky, 541 A.2d at 1067 (“[A] plaintiff must establish ‘the extent of any ascertainable loss, particularly proximate to a misrepresentation or unlawful act of the defendant condemned by the [Act].’ ”) (quoting Ramanadham v. N.J. Mfrs. Co., 188 N.J.Super. 30, 455 A.2d 1134, 1136 (N.J.Super.Ct.App.Div.1982)). In other words, the alleged unlawful praetice must be a proximate cause of the plaintiffs ascertainable loss.
Here, Marcus argues that BMW and Bridgestone “violated the NJCFA by failing to disclose salient facts about the Tires that would be material to the average consumer who is not knowledgeable about tires.” Marcus Br. at 21. Specifically, he asserts that they failed to disclose the alleged “defects” previously discussed (i.e., susceptibility to damage, repairability, exorbitant price, etc.). He claims that, as a result of BMW’s and Bridgestone’s wrongdoing, he suffered two forms of ascertainable loss: (a) he spent money to replace his tires that went flat, and (b) he leased a product that was worth less than what he expected. See J.A. 101, 103 (alleging ascertainable loss as “monies spent to replace the Tires and/or in diminution in value”).
To the extent Marcus relies on the cost of replacing his tire as his ascertainable loss, his claims cannot meet the predominance requirement for the reasons related to causation discussed above. See Oscar I, 274 F.R.D. at 513 (“[Determining whether each tire failed as a result of the allegedly concealed defect or as a result of unrelated issues, e.g., potholes or reckless driving habits, will devolve into numerous mini-trials.”). The District Court’s NJCFA analysis, however, seems to have proceeded on the assumption that class members’ ascertainable losses would be the value of the product they expected to purchase minus the value of the product they actually purchased. The Court noted that, with respect to ascertainable loss, “[t]he relevant issue ... is whether the class members got less than what they expected.” Marcus, 2010 WL 4853308, at *11. Hence unlike his common law claims, Marcus’s NJCFA claims proceed on the theory that class members suffered a loss the instant they purchased or leased their cars, not when their tires went flat. Compare J.A. 101, 103 (alleging with respect to NJCFA claims ascertainable loss as “monies spent to replace the Tires and/or in diminution in value”), with Pi’s Am. Br. in Support of Class Cert. (J.A. 1255) (arguing with respect to the common law claims that “[a]ll class members were damaged when their tires suffered a flat and they were forced to pay for a new Tire or when they purchased road hazard coverage to insulate them from financial hardship due to cost of the Tires”).
In response, BMW and Bridgestone point out that a person cannot succeed on an NJCFA claim against them if that person knew about the alleged “defects,” yet decided to purchase or lease a BMW anyway. In such a case, under the NJCFA any alleged unlawful practice by the defendants would not have been the proximate cause of the knowledgeable consumer’s ascertainable loss. Turning to the requirements of Rule 23, they then point out that what a particular class member knew about Bridgestone RFTs before purchase or lease would require an individualized inquiry, making Marcus’s NJCFA claims not susceptible to proof with common, class-wide evidence.
The District Court concluded that a “presumption of causation” should apply to Marcus’s NJCFA claims, and therefore that common issues of fact would predominate. See Marcus, 2010 WL 4853308, at *12. According to the Court, a causal relationship between an alleged unlawful practice and a consumer’s ascertainable loss may be presumed under the NJCFA when a defendant is alleged to have omitted (rather than affirmatively misrepresented) material information in written representations and when a defendant’s marketing statements do not differ from one consumer to another. Id. If the Court is correct, then Marcus would be able to prove his NJCFA claims with nothing more than evidence of BMW’s and Bridge-stone’s “unlawful practices” (thus common issues of fact would predominate).
To justify this conclusion, both New Jersey law and Rule 23 require factual findings that the District Court did not make. What a consumer knew about Bridgestone RFTs prior to purchasing or leasing his or her car is highly relevant to whether that consumer can succeed on an NJCFA claim. The District Court correctly noted that “[t]he relevant issue ... is whether the class members got less than what they expected.” Marcus, 2010 WL 4853308, at *11. But what a class member “expected” of Bridgestone RFTs and BMWs depends on what information, if any, about the alleged defects was available during the class period and whether that class member knew about it. If a consumer did know about the “defects” but, despite that knowledge, still decided to purchase or lease a BMW at the same price anyway — because, for example, he or she decided that the other safety and convenience benefits RFTs and BMWs offer outweigh the costs of their defects — then the consumer would not have received something less than expected. If the evidenee indicates that this could be true for a significant number of class members, then common questions of fact will not predominate. Instead, individual issues about what each class member expected when purchasing or leasing his or her car would swamp the inquiry, making the NJCFA claims inappropriate for class treatment. Because, as we explain below, the District Court made its “presumption of causation” ruling without making key factual findings that the NJCFA and Rule 23 require, it is an “errant conclusion of law” and an abuse of discretion. Hydrogen Peroxide, 552 F.3d at 312.
The Supreme Court of New Jersey has addressed when a “presumption of causation” may apply to NJCFA claims in two cases: International Union of Operating Engineers Local No. 68 Welfare Fund v. Merck & Co., 192 N.J. 372, 929 A.2d 1076 (2007), and Lee v. Carter-Reed Co., LLC, 203 N.J. 496, 4 A.3d 561 (2010). Both cases arose in the context of class actions brought under the New Jersey rule that, like Rule 23(b)(3), requires a finding of predominance. See N.J. Ct. R. 4:32-1(b)(3). Although we must follow a state’s highest court when interpreting state law, see III. Nat’l Ins. Co. v. Wyndham Worldwide Operations, Inc., 653 F.3d 225, 231 (3d Cir.2011), we decide the legal standards that Rule 23 requires as a matter of federal law. See Hydrogen Peroxide, 552 F.3d at 312. Given this confluence of state and federal law, we take pains to isolate what the NJCFA requires and what Rule 23 requires in this ease.
International Union involved a putative NJCFA class action against Merck, the manufacturer and marketer of the pain medication Vioxx. The class consisted of “third-party payors,” such as corporate health insurers and union benefit organizations, who administer health benefit plans and make payments to pharmaceutical companies for medications prescribed to their members. Int’l Union, 929 A.2d at 1080. The plaintiff alleged that Merck fraudulently marketed Vioxx as safer and more effective than similar medications, and thereby caused class members to afford Vioxx preferred status in their “formularies,” the approved listings of drugs third-party payors have authorized for purchase. Id. at 1080-81.
Merck argued that class certification was inappropriate because class members differed greatly in how their formularies dealt with Vioxx, especially as new information about the drug became available. Id. at 1081. Initially, some third-party payors gave Vioxx preferred status and assigned it to a low co-payment tier. Others put it in a non-preferred tier with high co-payments. Critically, Merck offered evidence that third-party payors, when they eventually learned of the supposedly fraudulent misrepresentations and omissions, did not react uniformly. Id. Merck’s expert testified that decisionmakers for third-party payors “responded to ongoing releases of information about Vioxx in different ways, with some altering its placement in their formularies.” Id. Merck asserted that
the essence of the claims must be that each class member was injured individually when it decided, based on defendant’s allegedly fraudulent conduct, to include Vioxx in its formulary and, more to the point, when it paid for the drug purchased by plan members in its home state.... [Bjecause each class member made that evaluation at different times and based on different criteria and because each reacted differently with regard to formulary placement even after the facts that allegedly prove the fraud became known, there are overwhelmingly individual, rather than common, questions of law and fact.
Id. at 1087 (emphasis added).
The Supreme Court of New Jersey agreed with Merck that certification of a NJCFA class is not proper when class members do not react to misrepresentations or omissions in a sufficiently similar manner.
Plaintiff does not suggest that each of these proposed class members, receiving the same information from defendant, reacted in a uniform or even similar manner. Rather, the record speaks loudly in its demonstration that each third-party payor ... made individualized decisions concerning the benefits that would be available to its members for whom Vioxx was prescribed. The evidence about separately created formularies, different types of tier systems, and individualized requirements for approval or reimbursement imposed on various plans’ members and, to some extent, their prescribing physicians, are significant. That evidence convinces us that the commonality of defendant’s behavior is but a small piece of the required proofs. Standing alone, that evidence suggests that the common fact questions surrounding what defendant knew and what it did would not predominate.
Id. (emphasis added).
As a matter of substantive New Jersey law, International Union instructs that when a plaintiff knows the truth behind a fraudulent misrepresentation or omission, that plaintiff may not succeed under the NJCFA. Merck presented evidence that some third-party payors knew about “the facts that allegedly prove the fraud” but did not alter the placement of Vioxx in their formularies. Id. at 1087. Even if other class members did not know that Vioxx was not a safer and more effective pain medication than other available products, the evidence “spoke loudly” that third-party payors reacted very differently to the available information. So from the class action perspective, the case also makes clear that “the commonality of [the] defendant’s behavior is but a small piece of the required proofs” if class members do not react to defendants’ conduct in a sufficiently “uniform or even similar manner.” Id.
Three years later, New Jersey’s Supreme Court decided Lee v. Carter-Reed Company, L.L. C, which the Court described as “fully in line” with International Union. Lee, 4 A.3d at 577. In Lee, a plaintiff sought to certify a class of purchasers of Relacore, a dietary supplement the defendants marketed as a weight-reduction product with the additional benefits of lessening anxiety and elevating mood. Id. at 566. According to the plaintiff, the defendants misrepresented the benefits of Relacore in their advertising and promotions. Id. The Court held that the plaintiffs NJCFA claims satisfied the predominance requirement. Id. at 579-80. It noted that “[i]f the entire marketing scheme was based on fictional benefits that Relacore offered, then whether the class member enjoyed good or impaired health or took other medications would hardly matter.” Id. at 580. The Court continued that “[w]hen all the representations about the product are baseless, a trier of fact may infer the causal relationship between the unlawful practice — the multiple deceptions — and the ascertainable losses, the purchases of the worthless product.” Id.
Not surprisingly, the Lee Court gave no indication that there was evidence of any class members who could have known that Relacore was a “worthless product” but decided to purchase it anyway. Such purchasers would not have been able to succeed on their NJCFA claims under New Jersey law. Turning to the predominance requirement, the Lee Court noted that, “[i]n contrast to this case, International Union involved a proposed class of diverse entities, which the plaintiff did not suggest ‘reacted in a uniform or even similar manner’ to the same information broadcast by Merck.” Id. at 582 (quoting Int’l Union, 929 A.2d at 1076).
Read together, International Union and Lee convince us that, before applying a “presumption of causation” to an NJCFA claim, a court must consider not only the defendants’ course of conduct, but also that of the plaintiffs. Specifically, it must consider whether plaintiffs could have known the truth underlying the defendant’s fraud. See McNair v. Synapse Grp., Inc., No. 06-5072(JLL), 2009 WL 1873582, at *10 (D.N.J. June 29, 2009) (“Thus, to establish causation under the NJCFA the New Jersey Supreme Court [in International Union ] looked not only to the defendant’s conduct but also to the class members’ conduct....”).
Although not binding on us, we also find the Supreme Court of New Jersey’s predominance rulings to be instructive. In the class action context, if the truth behind alleged defects is knowable and if evidence suggests that class members did not react to information about the product they purchased or leased in a sufficiently similar manner such that common issues of fact would predominate, then certification is improper. See Demmick v. Cellco P’ship, No. 06-2163(JLL), 2010 WL 3636216, at *16 (D.N.J. Sept. 8, 2010) (“[A]lleging a uniform course of conduct by itself is not sufficient to satisfy the predominance element for the causation element of a NJCFA claim.”).
Relying heavily on the Appellate Division of the New Jersey Superior Court’s decision in Varacallo v. Massachusetts Mutual Life Insurance, 332 N.J.Super. 31, 752 A.2d 807 (N.J.Super.Ct.App.Div.2000), Marcus argues nonetheless that we need not consider class members’ conduct here. In Varacallo, however, the record did not indicate that the facts underlying the alleged fraud were knowable to class members or, even if they were, that a sufficient number of class members would have purchased the product anyway.
The case involved a putative class of New Jersey residents who purchased so-called “vanishing premium” whole life insurance policies. Id. at 808. A “vanishing premium” policy allows insureds to pay premiums out-of-pocket for a limited number of years only, until such time as dividends can completely fund the purchased plan. Id. Plaintiffs claimed that Mass Mutual violated the NJCFA by intentionally inflating its advertised dividend rates and then concealing a plan to reduce dividends to insupportable levels. They contended that this information was not revealed to agents who used Mass Mutual’s prepared illustrations in selling the policies. Id. Mass Mutual countered that class certification would be improper because individual issues of causation would predominate over common issues of law and fact.
The Court held that if the plaintiffs established the core issue of liability, then they would be entitled to a “presumption of reliance and/or causation.” Id. at 818. It explained:
It is inconceivable to us, considering the assumption that Mass Mutual’s liability is premised on a knowing omission of material information, that discovery will reveal more than a very small number of policyholders who would have purchased an N-Pay Policy, rather than a competitor’s policy, if the Mass Mutual literature stated that the illustrated dividends “probably will,” rather than “may,” decrease and that the payout period “probably will,” rather than “may,” be longer than projected. Plaintiffs are required to prove only that defendant’s conduct was a cause of damages. They need not prove that Mass Mutual’s conduct was the sole cause of loss..... It may be that some extraordinary sales agent could overcome such negative information[,] thereby becoming the superceding cause of a policyholder’s loss, but we think it a small possibility.
Id. at 816-17. In short, unlike in International Union, there was no evidence that class members could have known the truth behind the defendant’s representations and it was “inconceivable” that “more than a very small number” would have purchased their policies despite knowing the risks that defendants allegedly concealed.
In this case, the District Court should not have focused exclusively on BMW’s and Bridgestone’s conduct, and should have made factual findings critical to the predominance analysis. Before certifying a class, the Court needed to have found (among other things) either (1) that the alleged defects were not knowable to a significant number of potential class members before they purchased or leased their BMW's, or (2) that, even if the defects were knowable, that class members were nonetheless relatively uniform in their decisionmaking, which would indicate that, at most, only an insignificant number of class members actually knew of the alleged defects and purchased or leased their cars at the price they did anyway. These findings cannot be side-stepped. They are necessary to determine whether the predominance requirement is met in this case. See Hydrogen Peroxide, 552 F.3d at 316-18. If class members could have known of the alleged defects and the evidence shows that they do not react to information about the cars and tires they purchased or leased in a sufficiently uniform manner, then individual questions related to causation will predominate. See In re Ford Motor Co. E-350 Van Prods. Liab. Litig. (No. II), No. 03-4558, 2012 WL 379944, at *14-*15 (D.N.J. Feb. 6, 2012) (denying certification because evidence showed that significant information about the alleged defects was in the public domain and, as a result, class members who knew “the E-350 van to have significant handling problems will have a difficult time proving causation, and in doing so, they would not rely on common proof’).
Marcus disputes that the drawbacks of the tires were knowable to class members before purchase. He claims that “[defendants have not produced any evidence showing that that information [about the drawbacks] was or could have been communicated to some class members prior to purchase.” Marcus Br. at 36. The defendants have, however, shown significant evidence that the allegedly omitted information was available to class members from various sources. See, e.g., J.A. 462-554; 940-948, 961-1108; 2308-2310, 2313. The District Court did not explicitly address this issue, however, and it should be the first Court to do so.
Furthermore, the District Court may find that class members did not react uniformly when presented with information about the cars they purchased or leased. The evidence might suggest that a significant number of class members could have known of the alleged “defects,” but decided to purchase or lease their cars at the same price anyway. This may be so because other class members may consider the features of Bridgestone RFTs and BMWs that Marcus styles as “defects” to be simply trade-offs. Some purchasers or lessees may have found that the significant safety and convenience benefits RFTs offer in the event of a “flat” tire outweighed their downsides. See, e.g., J.A. 961 (“Despite the disadvantages and inconveniences of run-fiat tires for many, Consumer Reports believes that the safety benefits can outweigh the downsides.”). Others may simply have had the means to purchase or lease the luxury car of their choice and brush off how “exorbitantly” expensive it is to replace their tires and how frequently they must do that. “For some consumers, the RFTs may have been an important factor; for others, not at all; for others, somewhere in between____” Oscar II, 2012 WL 2359964, at *4. If, on remand, the evidence shows that no more than very few class members could have known of the alleged “defects” and — for reasons either related or unrelated to RFTs — would have still purchased or leased their cars at the same price despite that knowledge, then perhaps Marcus’s NJCFA claims may be suitable for class treatment. If not, then individual proof would be needed to determine whether a particular class member broke the causal link between defect and ascertainable loss by purchasing or leasing a car despite knowing of the alleged defects.
That would distinguish this case from Lee and Varacallo. Lee involved a “worthless product” for which “all representations ... [were] baseless.” 4 A.3d at 580. There was no reason for the Lee Court to believe that a significant number of class members would, despite knowing that the product was worthless, purchase Relacore anyway. Similarly, in Varacallo it was “inconceivable” that “more than a very small number” of plaintiffs would purchase a vanishing premium insurance policy despite knowing that the promised dividend rates were inflated, making that knowledge a “superceding cause of a policyholder’s loss.” 752 A.2d at 816-17. Here, if the evidence shows on remand that the “defects” were knowable and that more than a very small number of class members would have purchased or leased their cars despite knowing of those defects, then Jeffrey Marcus is destined to meet the same fate on his RFT claims as Gerald Oscar met on his. See Oscar I, 274 F.R.D. 498; Oscar II, 2012 WL 2359964.
VI. Conclusion
With this context, we vacate the District Court’s certification order and remand for proceedings consistent with this opinion.
. As noted in our introduction, RFTs do not go "flat” in the conventional sense. When discussing RFTs, we use the term "flat” to mean a tire that has suffered a loss of air pressure and been replaced.
. As a practical matter, the certification decision is typically a game-changer, often the whole ballgame, for plaintiffs and plaintiffs’ counsel. See Newton, 259 F.3d at 167 ("[D]enying or granting class certification is often the defining moment in class actions (for it may sound the 'death knell' of the litigation on the part of plaintiffs, or create unwarranted pressure to settle nonmeritorious claims on the part of defendants) .... ”). Appropriately, attentiveness to “the potential for unwarranted settlement pressure” coincides with a court's obligation to conduct a “rigorous analysis” of whether a plaintiff has demonstrated actual conformance with Rule 23. Hydrogen Peroxide, 552 F.3d at 310.
. The class definition and aseertainability problems spill into the predominance inquiry as well. According to BMW and Bridgestone, the District Court could not have properly conducted a choice-of-law analysis because the class definition includes "unidentified persons from jurisdictions unknown.” See BMW Br. at 45; see also BMW Reply Br. at 19 ("[T]he nebulous class definition ... makes the choice-of-law analysis difficult if not impossible.”). If the District Court finds on remand an ascertainable class, and clarifies its definition accordingly, then the defendants can renew their choice-of-law arguments as they relate to predominance. We note, however, that predominance is not defeated merely because different states’ laws apply to different class members’ claims. See Sullivan v. DB Invs., Inc., 667 F.3d 273, 301-02 (3d Cir.2011) (en banc). In this regard, "Rule 23(b)(3) requires merely that common issues predominate, not that all issues be common to the class.” Id. (quoting Smilow v. Sw. Bell Mobile Sys., Inc., 323 F.3d 32, 39 (1st Cir. 2003) (emphasis added)).
. BMW and Bridgestone do not challenge the District Court's finding that Marcus is an adequate representative of the class.
. Whether Marcus has alleged actionable “defects” or simply trade-offs that a consumer should consider in the purchase or lease calculus was the not the question before the District Court at the certification stage nor is it the one before us now. So while BMW argues that it had no duty to provide purchasers and lessees with a part-by-part price list for each of its vehicles and warn them about Bridgestone RFTs being "exorbitantly priced,” we cannot consider that argument at this stage of the litigation.
. Neither BMW nor Bridgestone challenge on appeal the District Court's findings that a class action is the superior method for adjudication.
. Like the District Court, we refer to Marcus's breach of warranty, breach of contract, and breach of the implied covenant of good faith and fair dealing claims as his “common law” claims, even though the breach of implied warranty claims now derive from New Jersey statutes. See N.J. Stat. Ann. § 12A:2-314.
."To state a claim for breach of the implied warranty of merchantability ..., a plaintiff must allege (1) that a merchant sold goods, (2) which were not 'merchantable' at the time of sale, (3) injury and damages to the plaintiff or its property, (4) which were was caused proximately and in fact by the defective nature of the goods, and (5) notice to the seller of injury.” In re Ford Motor Co. E-350 Van Prods. Liab. Litig. (No. II), No. 03-4558(HAA), 2008 WL 4126264, at *19 (D.N.J. Sept. 2, 2008). A claim for breach of express warranty similarly requires proof of proximate cause. See Collins v. Uniroyal, Inc., 64 N.J. 260, 315 A.2d 16, 20 n. 4 (1974) ("[P]roximate cause and damages.... are, of course, necessary for a breach of express warranty verdict.”); Prashker v. Beech Aircraft Corp., 258 F.2d 602, 607 (3d Cir.1958) (“The measure of damages for a breach of warranty is, under New Jersey law, the loss directly and naturally resulting in the ordinary course of events from such breach ”) (emphases added). To state a claim for breach of contract, a plaintiff must “[1] show that the parties entered into a valid contract, [2] that the defendant failed to perform his obligations under the contract and [3] that the plaintiff sustained damages as a result.” Murphy v. Implicito, 392 N.J.Super. 245, 920 A.2d 678, 689 (N.J.Super.Ct.App.Div.2007) (quotation marks omitted). Marcus's implied covenant of good faith and fair dealing claims also hinge on his purchasing a defective product that caused him damage. See Amended Class Action Complaint (J.A. 109-110) ("BMW breached those implied covenants by selling or leasing to Plaintiff and members of the Sub-Class Vehicles that were not fit for ordinary use, and that were equipped with Tires that were inherently defective when BMW knew, or should have known, that the Tires were defective .... As a direct and proximate result of BMW's breach of its implied covenants, Plaintiffs and Class members have been damaged.”); see id. at 111-12 (making similar allegations against Bridgestone).
. Because BMW and Bridgestone do not challenge the District Court's findings that, with respect to Marcus's common claims, the other alleged defects are capable of common proof, we need not consider them.
. An aspect ratio is, roughly speaking, the relationship between the height and width of a tire. A tire with a low aspect ratio, sometimes referred to as a low profile tire, is short and squatty and generally provides for better handling. J.A. 421. Bridgestone argues that a low aspect ratio is not a defect. It is simply a design trade-off that allows for better handling at the cost of a softer ride, among other things. Bridgestone Reply Br. 8-10. To repeat, see supra note 5, whether Marcus has alleged actionable "defects” or non-actionable design trade-offs is not before us.
. After Judge Holwell denied Oscar’s motion for class certification, Judge Engelmayer denied Oscar’s second motion for class certification based on causation and predominance problems. See Oscar v. BMW of N. Am., LLC, No. 09 Civ. 11 (PAE), 2012 WL 2359964 (S.D.N.Y. June 19, 2012) ("Oscar II").
. At times, Marcus erroneously suggests that the lower standard of proof applicable to actions by the Attorney General applies to his claims as well. See Marcus Br. at 22-23 (“Even if ... class members had differing levels of knowledge, such an inquiry is irrelevant under the NJCFA because Defendants may be liable under the NJCFA 'whether or not any person has in fact been misled, deceived or damaged’ by their deception.”) (quoting N.J. Stat. Ann. § 56:8-2).
. We do not consider whether Marcus's damages allegations raise another set of predominance problems on which we may soon receive relevant guidance from the Supreme Court. See Comcast Corp. v. Behrend, No. 11-864, - U.S. -, - S.Ct. -, - L.Ed.2d -, 2012 WL 113090 (June 25, 2012) (granting certiorari on the question of ”[w]hether a district court may certify a class action without resolving whether the plaintiff class has introduced admissible evidence, including expert testimony, to show that the case is susceptible to awarding damages on a class-wide basis”).
|
Magnetism booster assembly
ABSTRACT
A magnetism booster assembly including a sleeve having a first face, a second face, and an outer periphery surface extending between the first face and the second face. The sleeve defines a central bore extending from the first face to the second face. The sleeve also defines a pocket spaced apart from the central bore and having an opening in the first face. The magnetism booster assembly also includes a magnet positioned within the pocket.
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims priority to U.S. Provisional Patent Application No. 62/701,204, filed Jul. 20, 2018, the entire contents of which are incorporated herein by reference.
BACKGROUND
The present invention relates to a magnetism booster assembly.
Power tools and hand tools alike are used to rotate and fasten screw sand other fasteners. A driver bit used to fasten fasteners typically includes a shaft with a tip that contacts a head of the fastener. In some constructions, the tip may be magnetic to help maintain engagement with the head. Likewise, some screwdrivers may include tips that are magnetic to help maintain engagement with fasteners. However, magnetic tips are often not strong enough to fully retain the fastener.
SUMMARY
In one embodiment, the invention provides a magnetism booster assembly including a sleeve having a first face, a second face, and an outer periphery surface extending between the first face and the second face.The sleeve defines a central bore extending from the first face to the second face. The sleeve also defines a pocket spaced apart from the central bore and having an opening in the first face. The magnetism booster assembly also includes a magnet positioned within the pocket.
In another embodiment, the invention provides a magnetism boosterassembly including a sleeve with a first face, a second face, and an outer periphery surface that extends between the first and second faces.The sleeve defines a central bore that extends from the first face tothe second face. The central bore defines a center axis and includes an inside surface. The sleeve further includes a rib that extends from the inside surface towards the center axis. The rib is configured to engage a shaft of a tool. The magnetism booster assembly also includes a magnet supported by the sleeve.
In another embodiment, the invention provides a magnetism boosterassembly including a flexible sleeve with a first face, a second face,and an outer periphery surface extending between the first face and the second face. The flexible sleeve defines a central bore extending between the first face and the second face. The magnetism boosterassembly also includes a first magnet supported by the flexible sleeve and spaced apart from the central bore and a second magnet supported bythe flexible sleeve and spaced apart from the central bore. The second magnet is positioned on a diametrically opposite side of the central bore from the first magnet.
Other aspects of the invention will become apparent by consideration ofthe detailed description and accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a perspective view of a magnetism booster assembly.
FIG. 2 is a front end view of the magnetism booster assembly of FIG. 1.
FIG. 3 is a rear end view of the magnetism booster assembly of FIG. 1.
FIG. 4 is an exploded view of the magnetism booster assembly of FIG. 1.
FIG. 5 is a side view of the magnetism booster assembly of FIG. 1.
FIG. 6 is a cross-sectional view of the magnetism booster assembly taken along section line A-A of FIG. 5.
FIG. 7 is a detailed view of section B-B of the magnetism boosterassembly of FIG. 6
FIG. 8 is a cross-sectional view of the magnetism booster assembly taken along section line C-C of FIG. 5.
DETAILED DESCRIPTION
Before any embodiments of the invention are explained in detail, it isto be understood that the invention is not limited in its application tothe details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings.The invention is capable of other embodiments and of being practiced or of being carried out in various ways.
FIGS. 1-8 illustrate a magnetism booster assembly 10. The illustrated magnetism booster assembly 10 can be selectively coupled to a shaft of atool, such as a driver bit or a screwdriver, to increase the magnetism of a tip of the tool for engaging a fastener (e.g., screw, bolt, nail,or the like) with the tip. In other embodiments, the magnetism boosterassembly 10 may be used with other types of power tools or hand tools to boost the magnetism of the tools.
With reference to FIGS. 1-4, the magnetism booster assembly 10 includes a sleeve 14, a first magnet 18, and a second magnet 22. Although the illustrated assembly 10 includes two magnets 18, 22, in other embodiments, the assembly 10 may include only one magnet. Alternatively,the assembly 10 may include three or more magnets.
Now referencing FIG. 1, the sleeve 14 is generally circular and includes a first or front face 26, a second or rear face 30 (FIG. 3) opposite the front face 26, an upper ridge 34, a lower ridge 38, and an outer periphery surface 42. The upper ridge 34, the lower ridge 38, and the outer periphery surface 42 extend between the front face 26 and the rear face 30. The outer periphery surface 42 is tapered from the front face26 to the rear face 30 to define gripping portions 44 (FIG. 5). In otherwords, an outer dimension of the sleeve 14 gradually decreases from the front face 26 then abruptly increases near the rear face 30 to form projections 45. The gripping portions 44 with the projections 45 assista user in removal and installation of the magnetism booster 10 on atool. The sleeve 14 has a length L (FIG. 5) measured between the front face 26 and the rear face 30. In the illustrated embodiment, the length L is approximately 22 mm. In other embodiments, the length L may be greater than or less than 22 mm. In further embodiments, the length L may be within a range between 16 mm and 28 mm.
The sleeve 14 defines a centrally located bore 46 that extends from the front face 26 to the rear face 30. The bore 46 defines a center axis 50of the sleeve 14 that extends from the front face 26 to the rear face30. The bore 46 is configured to receive a shaft of a tool. The sleeve14 also defines a pair of pockets (e.g., a first or upper pocket 54 anda second or lower pocket 58). The pockets 54, 58 are spaced apart fromthe bore 46 on diametrically opposite sides of the center axis 50. The pockets 54, 58 retain the first and second magnets 18, 22, respectively.The illustrated pockets 54, 58 have a generally rectangular cross-section. In the illustrated embodiment, the sleeve 14 includes two pockets 54, 58 that retain two magnets 18, 22 (one magnet in each pocket). In other embodiments, the sleeve 14 may include more than or less than two pockets to retain more than or less than two magnets. Thefirst and second pockets 54, 58 both include an opening 62 on the front face 26 that allows access to the interior of the pockets 54, 58.
With reference to FIG. 6, the openings 62 are smaller than the pockets54, 58. In the illustrated embodiment, the openings 62 are approximately1 mm smaller in a width direction and a length direction compared to a corresponding length and a corresponding width of the pockets 54, 58. As such, the openings 62 define a lip or shoulder 66 that helps retain the magnets 18, 22 within the pockets 54, 58. The pockets 54, 58 are also defined by a back surface 70 of the sleeve 14 that acts as a stop forthe magnets 18, 22. Apertures 72 extend through the back surface 72 tothe rear face 30 of the sleeve 14 in each of the pockets 54, 58. Theapertures 72 allow air to escape while the magnets 18, 22 are being inserted into the pockets 54, 58. The apertures 72 also facilitate removing the magnets 18, 22 from the pockets 54, 58 by allowing a relatively thin object (e.g., a nail) to be inserted through theapertures 72 to push the magnets 18, 22). As shown, the length of the magnets 18, 22 in a direction parallel to the center axis 50 is smaller than the length of the pockets 54, 58 in a direction parallel to the center axis 50. As such, magnets of different lengths may be retained inside the pockets 54, 58. In other embodiments, the length of the magnets 18, 22 may be the same as the length of the pockets 54, 58.
With continued reference to FIG. 6, the sleeve 14 includes two ribs 82,86 extending into the central bore 46. The ribs 82, 86 extendcircumferentially around an inside surface 78 that defines the bore 46toward the center axis 50. The first rib 82 is positioned adjacent the front face 26 of the sleeve 14, and the second rib 86 is positioned adjacent the rear face 30 of the sleeve 14. Moving on to FIG. 7, each rib 82, 86 extends from the inside surface 78 approximately 2 mm and hasa width W that is approximately 1 mm. In other embodiments, the ribs 82,86 may extend further than or less than 2 mm from the inside surface 78.In further embodiments, the ribs 82, 86 may extend within a range between 1 mm and 3 mm from the inside surface 78. Similarly, the ribs82, 86 may have a width W that is greater than or less than 1 mm or within a range from 0.5 mm to 2 mm. The ribs 82, 86 engage the shaft ofa tool to help retain the sleeve 14 on the shaft. The ribs 82, 86 also accommodate a variety of driver sizes (e.g., widths, diameters, etc.)and shapes (e.g., cylindrical, hexagonal, oblong, etc.) of tool shafts.
In the illustrated embodiment, the sleeve 14 is made of a silicone material. For example, the sleeve 14 may be made of a silicon material having a hardness on the Shore A scale between durometer 50 and 60. The silicone is flexible and durable and allows the inside surfaces of the pockets 54, 58 to conform to the shapes of the magnets 18, 22 to help retain the magnets 18, 22 inside the pockets 54, 58. For example, the silicone allows the openings 62 to deflect and expand to receive the magnets 18, 22. Similarly, the silicone allows the central bore 46 andthe ribs 82, 86 to conform to different sized and shaped tool shafts to retain the sleeve 14 on the tool. In other embodiments, sleeve 14 may be made of a material having hardness greater than or less than durometer50-60. In further embodiments, the sleeve 14 may be made from a different material (e.g., rubber, elastomeric material, plastic, etc.).
With reference to FIG. 4, the magnets 18, 22 are permanent magnets witha north pole side 90 and a south pole side 94. In other embodiments, the magnets 18, 22 may be ferromagnetic elements that magnetically couple toa magnetic field created by a corresponding permanent magnet. The magnets 18, 22 have a generally rectangular cross-sectional shape,corresponding to the cross-sectional shape of the pockets 54, 58. The magnets 18, 22 are inserted into their respective pocket 54, 58 in a direction parallel to the center axis 50. The first magnet 18 is positioned in the upper pocket 54 with the north pole side 90 facing down, and the second magnet 22 is positioned in the lower pocket 58 withthe north pole side 90 facing up. In other words, the magnets 18, 22 are positioned inside the pockets 54, 58 respectively with the north pole sides 90 facing each other. Alternatively, the magnets 18, 22 may be placed inside the pockets 54, 58, respectively, with the south pole sides 94 facing each other. With the north pole 90 sides facing eachother, a strong magnetic field is created between the two magnets 18,22. Specifically, a strong magnetic field is created equidistance fromthe magnets 18, 22 within the central bore 46. The magnetic field is amplified on the shaft of a tool within the bore 46 to magnetize the shaft and increase engagement between the tip of the shaft and a fastener.
Providing a magnetism booster assembly 10 on a tool advantageouslyboosts the magnetic coupling between the tip of the tool and a fastener.With the magnetism booster assembly 10, fasteners are less likely to beuncoupled or misaligned from the tip of a shaft while being driven into a workpiece or while being transported to the workpiece. For example, auser can place the fastener on the shaft and lift towards the ceiling or wall without worrying about the fastener falling to the ground. Inaddition, the magnetism booster assembly 10 allows for fasteners to be pulled out of bores of a workpiece easier.
Various features and advantages of the invention are set forth in thefollowing claims.
What is claimed is:
1. A magnetism booster assembly comprising: a sleeve having a first face, a second face, and an outer periphery surface extending between the first face and the second face, the sleeve define sa central bore extending from the first face to the second face, the sleeve also defines a pocket spaced apart from the central bore and having an opening in the first face; and a magnet positioned within the pocket; wherein the pocket is partially defined by a back surface of the sleeve that acts as a stop for the magnet, and wherein the sleeve further defines an aperture in communication with the pocket and adjacent the back surface.
2. The magnetism booster assembly of claim 1,wherein the sleeve is made of a flexible silicone material.
3. The magnetism booster assembly of claim 1, wherein the sleeve includes a rib extending into the central bore, and wherein the rib is configured to engage a shaft of a tool.
4. The magnetism booster assembly of claim 1,wherein the pocket is a first pocket and the magnet is a first magnet,wherein the sleeve further defines a second pocket spaced apart from the central bore and the first pocket, wherein the second pocket has an opening in the first face, and further comprising a second magnet positioned within the second pocket.
5. The magnetism booster assembly of claim 4, wherein the first pocket and the second pocket are positioned on diametrically opposite sides of the central bore.
6. The magnetism booster assembly of claim 1, wherein the sleeve has a length defined between the first and second faces between 16 mm and 28 mm. 7.The magnetism booster assembly of claim 1, wherein the sleeve is generally circular.
8. The magnetism booster assembly of claim 1,wherein the pocket has a generally rectangular cross-section.
9. The magnetism booster assembly of claim 1, wherein the opening defines a lip that helps retain the magnet within the pocket.
10. The magnetism booster assembly of claim 1, wherein the central bore defines a center axis, and wherein the magnet is inserted into the pocket of the sleeve in a direction parallel to the center axis.
11. The magnetism boosterassembly of claim 1, wherein the aperture extends through the second face into the pocket.
12. A magnetism booster assembly comprising: a sleeve including a first face, a second face, and an outer periphery surface extending between the first and second faces, the sleeve define sa central bore extending from the first face to the second face, the central bore defines a center axis and includes an inside surface, the sleeve further includes a rib extending from the inside surface towards the center axis, the rib is configured to engage a shaft of a tool; anda magnet supported by the sleeve; wherein the rib extendscircumferentially around the inside surface of the central bore.
13. The magnetism booster assembly of claim 12, wherein the rib is a first rib positioned adjacent the first face of the sleeve, and wherein the sleeve further includes a second rib extending from the inside surface towards the center axis, the second rib is positioned adjacent the second face of the sleeve.
14. The magnetism booster assembly of claim 12, wherein the rib extends from the inside surface towards the center axis within arange between approximately 1 mm and 3 mm.
15. The magnetism boosterassembly of claim 14, wherein the rib has a width that is approximately1 mm.
16. The magnetism booster assembly of claim 12, wherein the rib is flexible to accommodate a variety of tool shaft sizes and shapes.
17. A magnetism booster assembly comprising: a flexible sleeve including a first face, a second face, and an outer periphery surface extending between the first face and the second face, the flexible sleeve define sa central bore extending between the first face and the second face; a first magnet supported by the flexible sleeve and spaced apart from the central bore; and a second magnet supported by the flexible sleeve and spaced apart from the central bore, the second magnet is positioned on adiametrically opposite side of the central bore as the first magnet;wherein each magnet is received in a corresponding pocket of the flexible sleeve, wherein each pocket has an opening through which the corresponding magnet is received and allowing access to an interior ofthe pocket, and wherein each opening has a width that is less than a width of the interior of the corresponding pocket.
18. The magnetism booster assembly of claim 17, wherein the flexible sleeve is made of a silicone material.
19. The magnetism booster assembly of claim 18,wherein the silicone material has a hardness on the Shore A scale between durometer 50 and 60.
|
Page:Meditations of the Emperor Marcus Antoninus - Volume 1 - Farquharson 1944.pdf/48
already begun before the time of Suidas, as would indeed be probable on general grounds.
There is one other line of inquiry to be considered in reference to the transmission of the Meditations. This depends on the length of the known omissions in A. The commonest length is of sentences consisting of from 30 to 40 letters, say an average of 35 letters. Schenkl has compared this modulus with the length of lines in the papyrus of Hierocles and with that in some old codices. I presume that he means especially the length of line in some of the manuscripts which we know to have been transcribed for Arethas' library, the Bodleian Euclid, for example. Several of A's omissions, however, are of 23–5 letters in length, corresponding to the 24 (23) letters dropped by both P and A in Book v. 8. It is tempting to suppose that 23–5 was the length of line in an early stage of the text, since it is common in many papyrus rolls of the second century The fact, however, that the one omission common to A. and P (v. 8) is supplied from the X excerpts might be held to show that this oversight belongs to a later period of the transmission. We may perhaps safely use these two moduli in an estimate of a given conjectural emendation or supplement, like Gataker's in v. 16. To argue on the basis of either length to the original format of the Meditations is too hazardous, in view of the variety of lines even in early rolls, much more in the minuscule stage.
As to the sources of literal corruption in both P and A, and their presumed archetype, the ground here is familiar. The errors are such as are met with in the study of every Greek text, and are abundantly illustrated from the apparatus criticus of modern texts of Marcus. The fact that A rarely writes iota subscript proves that his original was of later date than the iota adscript period. P's occasional omission of iota (it is not always easy to read in the print) points in the same direction. More than one explanation might be suggested for the uncertainty about xl
|
Conveying a coal slurry with a single pipeline
ABSTRACT
This invention relates to the art of transporting coal with water through a pipeline. More particularly, it relates to a method which includes preparing a vehicle comprising an aqueous slurry of an inorganic finely divided water insoluble solid carrier such as magnetite, coal ash, coal of a selected size or various clays. Coal in particulate form is then suspended in the vehicle. The insoluble solid carrier must be finely divided as compared to the particulate coal to ensure that the two can be separated by screening or hydraulic sizing. In this connection, the solid carrier should all be finer than 100 microns while the particulate coal should all be larger than 500 microns. After the slurry is formed, it is then pumped through a pipeline to a location many miles away where, after being separated from the vehicle, the coal is utilized and the coal-free vehicle is collected. This operation is continued for a period of several days at the end of which pumping of the slurry is discontinued and the pipeline is flushed with water. Upon completion of the flushing, the coal-free vehicle is pumped back through the pipeline to the point at which the coal slurry is prepared, the vehicle being reused. The water filling the pipeline is returned to the preparation point by the return of the vehicle. In this manner, it is possible to achieve transportation of the coal and reutilization of the vehicle with but a single pipeline.
Unite States Patent 1 Wasp [ March 6, 1973 Primary Examiner Richard E. Aegerter Assistant Examine rl-l. S. Lane Attorney Carl Hoppe et al.
ABSTRACT This invention relates to the art of transporting coal with water through a pipeline. More particularly, it relates to a method which includes preparing a vehicle comprising an aqueous slurry of an inorganic finely divided water insoluble solid carrier such as magnetite, coal ash, coal of a selected size or various clays. Coal in particulate form is then suspended in the vehicle. The insoluble solid carrier must be finely divided as compared to the particulate coal to ensure that the two can be separated by screening or hydraulic sizing. In this connection, the solid carrier should all be finer than l00 microns while the particulate coal should all be larger than 500 microns.
After the slurry is formed, it is then pumped through a pipeline to a location many miles away where, after being separated from the vehicle, the coal is utilized and the coal-free vehicle is collected. This operation is continued for a period of several days at the end of which pumping of the slurry is discontinued and the pipeline is flushed with water. Upon completion of the flushing, the coal-free vehicle is pumped back through the pipeline to the point at which the coal slurry is prepared, the vehicle being reused. The water filling the pipeline is returned to the preparation point by the return of the vehicle. In this manner, it is possible to achieve transportation of the coal and reutilization of the vehicle with but a single pipeline.
5 Claims, 2 Drawing Figures BLEED l/4"x0 COAL FROM 7 WATER CRUSHING a WASHING PLANT VEHIISEE I/4 1 l4 l4 MESH SCREEN TANK MESH /\//6 Ila l 7 i MINus 37 I4 MESH TANK 3 PUMP STATION PATH-mum W5 3,719,397
SHEET 10F 2 l/4"x0 COAL FROM 12 7 WATER CRUSHING a WASHING PLANT I7 353%: l/4"xl4 l4 MESH SCREEN TANK I MESH 9 L MINUS L 37 I4 MESH K; TANK Q a READY 2/ 1 WATER v sl gmv 22 23 24 STORAGE wAsTE 6 PIPELINE FLUSH L g-g O i l 0@ 26 4? 70 PIPELINE 50 MI.
MINUS l4 MESH l/4"xl4 64,27 1
MESH I/zemEsn SCREEN H OLDI NS 133 TANK DEWATERING Nn Nus l4 'CENTRIFUGE MESCI' l/4"x l4 COAL GOA 46 w vEmcLE VEHICLE DEWATERING COAL STORAGE RETURN TANK CENTRIFUGE PUMP STATION INVENTOR. 'ward J. Wasp y;- K v PATENTEDHAR 61w 3.719.397
SHEET 2 [)F 2 l/4"x o coAL 7 FROM CRUSHING PLANT 52 i F1 SLURRY 56 5 PUMP STATION 56 w -i If[ E] 67 J59 BLEED VEHICLE a5 READY SE fi s To WASTE STORAGE SLURRY 57 (SUPERFINES) TA PIPELINE 50 MILES VEHICLE REMOVAL g CENTR'FUGE 4 DEWATERED coAL T0 1k 7 I I USERS STOCKPILE 69x4..- BLOCK 2 VALVES 63 r VEHICLE STORAGE VEHICLE RETURN PUMP STATION .zg- Z INVENTOR. Eda/4rd Wasp .4 r TOP/V5 Y CONVEYING A COAL SLURRY WITH A SINGLE PIPELINE BACKGROUND OF THE INVENTION It has been proposed heretofore to transport coal through a pipeline utilizing a vehicle to maintain the coal in suspension as a slurry. In this case, however, the slurry was separated into a coal component and a vehicle component at the point of use of the coal, the vehil cle being returned continuously through a separate pipeline. This requires the capital investment in two pipelines.
SUMMARY OF THE INVENTION BRIEF DESCRIPTION OF THE DRAWINGS In the drawings,
FIGS. 1 and 2 are schematic flow sheets showing the operation of the present invention, while FIGS. 3 and 4 are fragmentary flow sheets showing variations based on the flowsheet of FIG. 2.
DESCRIPTION OF THE PREFERRED EMBODIMENT Referring to FIG. 1, a fine dense material in water suspension is fed from tank 7 by pump 8 through line 9 to a slurry tank 11. Coal from a crushing plant is fed through line 12 to screen 16. The screen is sprayed with water from line 17, the coarse coal (usually /4 inch X14 mesh) being fed into tank 11 while the fines are passed through line 18 into tank 19 where the minus 14 mesh coal is maintained in slurry form. The coal in suspension in the vehicle in tank 11 is fed through valve 21 to line 22 and then through a series of pumps, generally indicated at 23, and thence through valve 24 into the main pipeline 26. The pipeline is, say, 50 miles in length and extends to a point of use for the coal. The coal in suspension in the vehicle is passed through valve 27 and thence over screen 31 which serves to separate the coal from the vehicle, the latter passing into a vehicle tank 32 where it is collected. The screen size is selected to separate the coal and the vehicle; in one installation a 28 mesh screen was used. The coal from the screen 31 is passed through line 33 into a water separation device 34 such as a centrifuge to remove the water from the coal. The coal is then passed through line 36 to storage. The effluent from the water separation device 34 is sent to the vehicle tank 32 through line 35.
This operation is continued for several days on a definite program, say from Monday through Friday. At the end of this time, valve 21 is closed and valve 37 from tank 19 is open to permit the minus 14 mesh slurry to pass from tank 19 into line 22 for transportation through line 26. When the minus 14 mesh slurry arrives at the point of use, valve 27 is closed and valve 38 is open to permit the minus 14 mesh slurry to pass through a holding tank 39 and thence through line 44 I to a water separation device 42 such as a centrifuge which removes the water, the minus 14 mesh coal being sent to storage. The effluent from the dewatering device 42 is sent through line 45 to thickener 50 from which the thickened solids are withdrawn through line 55 to be returned to vehicle tank 32. The flow of fines is continued for, say, half of Saturday.
When transmission of the minus 14 mesh material has been completed, valve 37 is closed and valve is open to permit water to flow into pumps 23 from the pipeline fresh water supply line 65 from water storage tanks (not shown). Transmission of the water is continued until the line 26 is flushed and the water reaches valve 27. When this occurs, valves 24 and 27 are closed and valves 43 and are opened. Pumps 46 are then operated to return the vehicle from the vehicle tank 32 through valve 43 and line 26. The pumping of the vehicle forces the water to return through line 26 and to permit its exit to the water storage tanks (not shown). When the water has been eliminated from line 26, valve 60 is opened and valve 75 is closed and the flow of the vehicle to tank 7 occurs through line 47 for, say, half of Saturday and all of Sunday. The vehicle is returned through line 26 and through line 47 to the vehicle storage tank 7 for reuse in the preparation of additional )4 inch X0 mesh coal slurry.
Referring to FIG. 2, coal graded so that it is all finer than /4 inch is provided from a crushing plant through line 51 to a slurry makeup tank 52. The latter is supplied with a vehicle from tank 53 which is made up of superfine fine coal. Because it is so fine, the solid material provides a very large surface area and it is this which one needs to increase the viscosity of the slurry. The vehicle is passed through line 54 by pump 56 into tank 52 to make up the slurry. The slurry is then passed through a pumping station 57 and through valve 58 into a pipeline 59 which extends to the point of use. There the slurry is passed through the valve 61 to a device 62 such as a centrifuge which serves to separate the coal from the vehicle. The vehicle discharged from the device 62 is removed through line 63 into the storage tank 64 where it is held for several days until the desired amount of dewatered coal has been sent to the users stockpile through line 66. When this has been achieved, the line 59 is flushed with the vehicle from tank 53, valves 55 and 60 being closed and valve 65 being opened to permit the vehicle to flow through line 75 to pumping station 57. When the line has been flushed free of the coarse coal, valves 58 and 61 are closed and valves 67 and 69 are opened so that the vehicle from tank 64 can be sent through line 71 by pumps 72 from the tank 64. The vehicle flows through line 59 and line 73 to the vehicle tank 53 where it is collected for reuse. b
There is an inherent advantage in having a vehicle in which the solid is fine coal. One of the problems with a recycling scheme is the inevitable contamination of the vehicle with minor amounts of coarse coal breaking down and destroying the effectiveness of the vehicle. In FIGS. 3 and 4, I have shown two concepts enabling this difficulty to be eliminated when fine coal provides the solid in the vehicle. Basically each involves the use of a grinding step to reduce the size of the inevitable minor amounts of such coal. This enables one to maintain a vehicle which contains a solid which is finely divided enough to have a high surface area and hence a relatively high viscosity for its concentration. Thus, in FIG. 3 I have shown the effluent from the centrifuge 62 as being discharged through line 63 into a thickener 82. The thickened effluent from the thickener is passed through line 83 and pump 84 through line 86 into a ball mill 87. Depending upon the concentration of the material issuing from the ball mill, water may be added from line 88 to line 89 which leads to the pumps 72.
In the flowsheet shown in FIG. 4, the effluent from the water separation device 62 is passed through line 63 into a liquid cyclone separator 91. The overhead fine product from the cyclone is sent through line 92 into a thickener 93 from which the concentrated fine product is sent through line 94 to line 89 and hence to pump 72. The coarse underflow from the cyclone is sent through line 96 into ball mill 97 and from thence through line 98 to line 89. In this way the coarse coal can be ground to such a size that it provides the necessary high surface area.
I claim:
1. A method of transporting coal from a coal slurry preparation site through a main pipeline to a point of use comprising preparing at such site a slurry of coarse comminuted coal in a vehicle comprising water and a water insoluble solid carrier in finely divided form,
I pumping said slurry through said pipeline to said point of use whereat the coarse comminuted coal and the vehicle are separated and are separately collected, discontinuing pumping of the slurry through said pipeline, pumping the coarse coal-free vehicle through the pipeline from the point of use of the coal to the slurry preparation site, and storing said vehicle at said site for further transportation of coarse coal.
2. The method of claim 1 wherein the comminuted coal is separated into a coarse fraction and a fines fraction and each fraction is thereafter formed into a separate slurry which is pumped separately through the pipeline to the point of use.
3. The method of claim 2 wherein following pumping of both fractions the pipeline is flushed with water following which the collected coarse coal free vehicle is pumped to the site forcing the water in the pipeline ahead of it.
4. The method of claim 1 wherein the carrier is superfine coal and the slurry is separated at the point of use into a coarse coal fraction free of water and a fines fraction which is ground and thickened to provide a superfine coal fraction which is thereafter returned to the slurry preparation site.
5. The method of claim 1 wherein the carrier is superfine coal and wherein, following pumping of the slurry, the pipeline is flushed with the vehicle until this fills the pipeline whereupon the vehicle is returned to slurry preparation site.
1. A method of transporting coal from a coal slurry preparation site through a main pipeline to a point of use comprising preparing at such site a slurry of coarse comminuted coal in a vehicle comprising water and a water insoluble solid carrier in finely divided form, pumping said slurry through said pipeline to said point of use whereat the coarse comminuted coal and the vehicle are separated and are separately collected, discontinuing pumping of the slurry through said pipeline, pumping the coarse coal-free vehicle through the pipeline from the point of use of the coal to the slurry preparation site, and storing said vehicle at said site for further transportation of coarse coal.
2. The method of claim 1 wherein the comminuted coal is separated into a coarse fraction and a fines fraction and each fraction is thereafter formed into a separate slurry which is pumped separately through the pipeline to the point of use.
3. The method of claim 2 wherein following pumping of both fractions the pipeline is flushed with water following which the collected coarse coal free vehicle is pumped to the site forcing the water in the pipeline ahead of it.
4. The method of claim 1 wherein the carrier is superfine coal and the slurry is separated at the point of use into a coarse coal fraction free of water and a fines fraction which is ground and thickened to provide a superfine coal fraction which is thereafter returned to the slurry preparation site.
|
ui.header('ui.dataframe')
ui.text('Display a pandas dataframe as a table.')
ui.subheader('Signature')
ui.code('ui.dataframe(data)')
ui.subheader('Parameters')
ui.table({
'name': ['data'],
'type': ['pandas.Dataframe'],
'default': [''],
'': ['the data to display'],
})
# ui.subheader('Returns')
# ui.table({})
ui.subheader('Example')
ui.code("""import pandas as pd
import numpy as np
df = pd.DataFrame(
np.random.randn(50, 20),
columns=('col %d' % i for i in range(20)))
ui.dataframe(df)""")
ui.subheader('Result')
def render_example():
import pandas as pd
import numpy as np
df = pd.DataFrame(
np.random.randn(50, 20),
columns=('col %d' % i for i in range(20)))
ui.dataframe(df)
render_example()
|
const path = require('path');
const cdogsService = require('./cdogsService');
const dataService = require('../services/dataService');
const transformService = require('../services/transformService');
const templateJson = require('../assets/silviculture-ipc-template-b.json');
module.exports = {
generate: async ipcPlanId => {
const docx = path.join(__dirname, '..', 'assets', 'silviculture-ipc-template-j.docx');
let templateId = await cdogsService.getHash(docx);
const templateResult = await cdogsService.getTemplate(templateId);
if (templateResult.status !== 200) {
const uploadResult = await cdogsService.uploadTemplate(docx);
templateId = uploadResult.data;
}
// ok, have the template... get the data and create the document...
const ipcPlan = await dataService.getIPCPlan(ipcPlanId);
const ipcPlanData = transformService.modelToAPI.ipcPlanToPost(ipcPlan);
const body = { ...templateJson };
body.data = { ...ipcPlanData };
return await cdogsService.templateRender(templateId, body);
}
};
|
can any Handler post to mainThread using Lopper.getMainLooper()
Lets say i am in another thread that i created and in android i do the following:
//this is called from another thread (not mainTread)
new Handler(Lopper.getMainLooper()).post(new Runnable() {
@Override
public void run() {
mAdapter.notifyDataSetChanged();
}
});
am i to understand that the handler here is associated with the thread but since i'm using the mainThreads looper that it will send the runnable to the mainThreads message queue for processing ? and if thats true that any handler on any thread can accept another threads looper to post to it ? is that correct ?
Or is it that "new Handler(Lopper.getMainLopper())" makes this a mainThread handler ?
Yes, you've got it right.
One thread can have only one unique Looper and can have many unique Handlers associated with it.
A Handler gets implicitly associated with the thread that instantiates it via thread’s Looper. Also you are allowed to tie your Handler with any thread simply by passing its Looper in constructor.
I would recommend to take a glance at this article to grasp the better understanding of this issue.
try this ...replace Looper.getMainLooper() with context.getMainLooper().This should work .
new Handler(context.getMainLooper()).post(new Runnable() {
@Override
public void run() {
mAdapter.notifyDataSetChanged();
}
});
my question is actually theoretical. i wanted to know if any handler can speak to any thread simply by having its looper.
if you can access looper then why not ?looper maintains the process queue in the thread .
|
[bulk] Validation: Absolute Links
Docs Build status updates of commit ba69d49:
:white_check_mark: Validation status: passed
File
Status
Preview URL
Details
Skype/UCMA/using-an-instantmessagingflowtemplate.md
:bulb:Suggestion
Details
Skype/UCMA/visual-ivr-sample.md
:bulb:Suggestion
Details
Skype/UCMA/voicexml-browser.md
:bulb:Suggestion
Details
Skype/UCMA/voicexml-support-in-ucma-5-0.md
:bulb:Suggestion
Details
Skype/UCMA/voicexmlsample-quickstart.md
:bulb:Suggestion
Details
Skype/UCMA/what-is-ucma-5-0.md
:bulb:Suggestion
Details
Skype/UCMA/using-an-instantmessagingflowtemplate.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform.instantmessagingsettings?view=ucma-api. Otherwise, remove the view parameter.
Line 15, Column 235: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate?view=ucma-api. Otherwise, remove the view parameter.
Line 17, Column 92: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow?view=ucma-api. Otherwise, remove the view parameter.
Line 21, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 22, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 32, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor' will be broken in isolated environments. Replace with a relative link.
Line 32, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor. Otherwise, remove the view parameter.
Line 37, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFormat_' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFormat_. Otherwise, remove the view parameter.
Line 42, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate_' will be broken in isolated environments. Replace with a relative link.
Line 42, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate_. Otherwise, remove the view parameter.
Line 47, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.composingtimeoutvalue?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 47, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.composingtimeoutvalue?view=ucma-api. Otherwise, remove the view parameter.
Line 53, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.messageconsumptionmode?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 53, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.messageconsumptionmode?view=ucma-api. Otherwise, remove the view parameter.
Line 55, Column 509: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessageconsumptionmode?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 55, Column 509: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessageconsumptionmode?view=ucma-api. Otherwise, remove the view parameter.
Line 59, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.supportedformats?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 59, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.supportedformats?view=ucma-api. Otherwise, remove the view parameter.
Line 65, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.toastformatsupport?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 65, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.toastformatsupport?view=ucma-api. Otherwise, remove the view parameter.
Line 66, Column 87: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.capabilitysupport?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 66, Column 87: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.capabilitysupport?view=ucma-api. Otherwise, remove the view parameter.
Line 70, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.waitingfordeliverynotificationdisabled?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 70, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.waitingfordeliverynotificationdisabled?view=ucma-api. Otherwise, remove the view parameter.
Line 71, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendinstantmessage?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 71, Column 76: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendinstantmessage?view=ucma-api. Otherwise, remove the view parameter.
Line 78, Column 55: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessageconsumptionmode?view=ucma-api. Otherwise, remove the view parameter.
Line 82, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 83, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 106, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.supportedformats?view=ucma-api. Otherwise, remove the view parameter.
Line 108, Column 430: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.messagereceived?view=ucma-api. Otherwise, remove the view parameter.
Line 108, Column 613: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendsuccessdeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 108, Column 809: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendfailuredeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 110, Column 38: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.deliverynotificationreceived?view=ucma-api. Otherwise, remove the view parameter.
Line 110, Column 361: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendfailuredeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 110, Column 517: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendsuccessdeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 112, Column 51: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendinstantmessage?view=ucma-api#overloads. Otherwise, remove the view parameter.
Skype/UCMA/visual-ivr-sample.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Skype/UCMA/voicexml-browser.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml.browser?view=ucma-voice. Otherwise, remove the view parameter.
Skype/UCMA/voicexml-support-in-ucma-5-0.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 29, Column 3: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration?view=ucma-api-5.0. Otherwise, remove the view parameter.
Line 30, Column 3: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/Microsoft.Rtc.Collaboration.AudioVideo.VoiceXml?view=ucma-voice. Otherwise, remove the view parameter.
Skype/UCMA/voicexmlsample-quickstart.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 21, Column 166: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideocall?view=ucma-api. Otherwise, remove the view parameter.
Line 23, Column 34: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform?view=ucma-api. Otherwise, remove the view parameter.
Line 25, Column 19: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml.browser?view=ucma-voice. Otherwise, remove the view parameter.
Skype/UCMA/what-is-ucma-5-0.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 25, Column 118: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration?view=ucma-api. Otherwise, remove the view parameter.
Line 29, Column 130: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml?view=ucma-voice' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 130: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml?view=ucma-voice. Otherwise, remove the view parameter.
Line 31, Column 128: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.signaling?view=ucma-api. Otherwise, remove the view parameter.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel
@v-emilypr Hi Emily, is this PR still a work in progress or is it abandoned?
Docs Build status updates of commit 3a1a66d:
:white_check_mark: Validation status: passed
File
Status
Preview URL
Details
Skype/UCMA/using-an-instantmessagingflowtemplate.md
:bulb:Suggestion
Details
Skype/UCMA/visual-ivr-sample.md
:bulb:Suggestion
Details
Skype/UCMA/voicexml-browser.md
:bulb:Suggestion
Details
Skype/UCMA/voicexml-support-in-ucma-5-0.md
:bulb:Suggestion
Details
Skype/UCMA/voicexmlsample-quickstart.md
:bulb:Suggestion
Details
Skype/UCMA/what-is-ucma-5-0.md
:bulb:Suggestion
Details
Skype/UCMA/using-an-instantmessagingflowtemplate.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform.instantmessagingsettings?view=ucma-api. Otherwise, remove the view parameter.
Line 15, Column 235: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate?view=ucma-api. Otherwise, remove the view parameter.
Line 17, Column 92: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow?view=ucma-api. Otherwise, remove the view parameter.
Line 32, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor' will be broken in isolated environments. Replace with a relative link.
Line 32, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor. Otherwise, remove the view parameter.
Line 37, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFormat_' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFormat_. Otherwise, remove the view parameter.
Line 42, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate_' will be broken in isolated environments. Replace with a relative link.
Line 42, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.-ctor?view=ucma-api#Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate__ctor_Microsoft_Rtc_Collaboration_InstantMessagingFlowTemplate_. Otherwise, remove the view parameter.
Line 47, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.composingtimeoutvalue?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 47, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.composingtimeoutvalue?view=ucma-api. Otherwise, remove the view parameter.
Line 53, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.messageconsumptionmode?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 53, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.messageconsumptionmode?view=ucma-api. Otherwise, remove the view parameter.
Line 55, Column 509: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessageconsumptionmode?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 55, Column 509: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessageconsumptionmode?view=ucma-api. Otherwise, remove the view parameter.
Line 59, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.supportedformats?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 59, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.supportedformats?view=ucma-api. Otherwise, remove the view parameter.
Line 65, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.toastformatsupport?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 65, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.toastformatsupport?view=ucma-api. Otherwise, remove the view parameter.
Line 66, Column 87: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.capabilitysupport?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 66, Column 87: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.capabilitysupport?view=ucma-api. Otherwise, remove the view parameter.
Line 70, Column 17: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.waitingfordeliverynotificationdisabled?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 70, Column 17: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.waitingfordeliverynotificationdisabled?view=ucma-api. Otherwise, remove the view parameter.
Line 71, Column 76: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendinstantmessage?view=ucma-api' will be broken in isolated environments. Replace with a relative link.
Line 71, Column 76: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendinstantmessage?view=ucma-api. Otherwise, remove the view parameter.
Line 78, Column 55: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessageconsumptionmode?view=ucma-api. Otherwise, remove the view parameter.
Line 106, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflowtemplate.supportedformats?view=ucma-api. Otherwise, remove the view parameter.
Line 108, Column 430: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.messagereceived?view=ucma-api. Otherwise, remove the view parameter.
Line 108, Column 613: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendsuccessdeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 108, Column 809: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendfailuredeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 110, Column 38: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.deliverynotificationreceived?view=ucma-api. Otherwise, remove the view parameter.
Line 110, Column 361: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendfailuredeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 110, Column 517: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendsuccessdeliverynotification?view=ucma-api. Otherwise, remove the view parameter.
Line 112, Column 51: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.instantmessagingflow.beginsendinstantmessage?view=ucma-api#overloads. Otherwise, remove the view parameter.
Skype/UCMA/visual-ivr-sample.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Skype/UCMA/voicexml-browser.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml.browser?view=ucma-voice. Otherwise, remove the view parameter.
Skype/UCMA/voicexml-support-in-ucma-5-0.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 29, Column 3: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration?view=ucma-api-5.0. Otherwise, remove the view parameter.
Line 30, Column 3: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/Microsoft.Rtc.Collaboration.AudioVideo.VoiceXml?view=ucma-voice. Otherwise, remove the view parameter.
Skype/UCMA/voicexmlsample-quickstart.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 21, Column 166: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideocall?view=ucma-api. Otherwise, remove the view parameter.
Line 23, Column 34: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform?view=ucma-api. Otherwise, remove the view parameter.
Line 25, Column 19: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml.browser?view=ucma-voice. Otherwise, remove the view parameter.
Skype/UCMA/what-is-ucma-5-0.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 25, Column 118: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration?view=ucma-api. Otherwise, remove the view parameter.
Line 29, Column 130: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml?view=ucma-voice' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 130: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rtc.collaboration.audiovideo.voicexml?view=ucma-voice. Otherwise, remove the view parameter.
Line 31, Column 128: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.signaling?view=ucma-api. Otherwise, remove the view parameter.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel
Docs Build status updates of commit 7b7bc43:
:white_check_mark: Validation status: passed
File
Status
Preview URL
Details
Skype/UCMA/voicexml-browser.md
:bulb:Suggestion
Details
Skype/UCMA/using-an-instantmessagingflowtemplate.md
:white_check_mark:Succeeded
Skype/UCMA/visual-ivr-sample.md
:white_check_mark:Succeeded
Skype/UCMA/voicexml-support-in-ucma-5-0.md
:white_check_mark:Succeeded
Skype/UCMA/voicexmlsample-quickstart.md
:white_check_mark:Succeeded
Skype/UCMA/what-is-ucma-5-0.md
:white_check_mark:Succeeded
Skype/UCMA/voicexml-browser.md
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel
|
DDO information project/Spot and Search/21
Level 21 quests
=== Suspected Requirements ===
Spot Requirements:
* Casual
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
* Normal
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
* Hard
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
* Elite
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
Search Requirements
* Casual
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
* Normal
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
* Hard
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
* Elite
* Guaranteed to find everything recorded: ?
* Suspected requirement to find everything: ?
The Lords of Dust
Traps&Locks
Traps
The Prisoner (Vault of Night, Part 2)
Trap & Lock DCs
Traps
Spies in the House
(Heroic)
Trap & Lock DCs
Traps
Secret doors
|
human sort list fix https://github.com/PCMDI/click/issues/10
Pull Request Test Coverage Report for Build 994
14 of 15 (93.33%) changed or added relevant lines in 1 file are covered.
16 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.3%) to 75.492%
Changes Missing Coverage
Covered Lines
Changed/Added Lines
%
pcmdi_metrics/io/base.py
14
15
93.33%
Files with Coverage Reduction
New Missed Lines
%
tests/basepmpdriver.py
1
90.63%
tests/basepmp.py
15
55.32%
Totals
Change from base Build 981:
-0.3%
Covered Lines:
3145
Relevant Lines:
4166
💛 - Coveralls
|
Purchasers pay or allow for transportation on Bulbs and Roots by the 1,000, also on Vegetable Seeds by the § peck, peck and bushel; Farm Seeds, Grain, Grass and Clover Seeds, Tools, Implements, Requisites, Fertilizers and Insecticides.
|
How to deserialize json list, error: Invalid conversion from runtime type List<ANY> to List<or_leadsJSON>
I an trying to deserialize a Json string to use in my callout but get the error
Invalid conversion from runtime type List<ANY> to List<or_guestsJSON>
Callout
HttpResponse response = http.send(request);
if (response.getStatusCode() == 200) {
List<or_leadsJSON> input = (List<or_leadsJSON>)JSON.deserializeUntyped(response.getBody());
}
Class object
public class or_leadsJSON{
class cls_0 {
public String city; //Irvine
public String state; //California
}
class cls_agency {
public String uid; //0000-0000-0000-0000-0000
public String name; //Responseev
}
class cls_property {
public String uid; //0000-0000-0000-0000-0000
public boolean isActive;
public String currencyRep; //USD
}
class cls_photos {
public String url; //https://www.orbirental.com/img/uploader/view_0.jpg
public String description; //my house
}
class cls_stayDetails {
public String departureDate; //2017-02-25 11:00:00.0
public String arrivalDate; //2017-02-24 15:00:00.0
public String extraNotes; //Some notes
}
public static or_leadsJSON parse(String json){
String jsonReplace = json.replace('"currency":', '"currencyRep":');
return (or_leadsJSON) System.JSON.deserialize(jsonReplace, or_leadsJSON.class);
}
}
Change this:
List<or_guestsJSON> input = (List<or_guestsJSON>) JSON.deserializeUntyped(
response.getBody()
);
to this:
List<or_guestsJSON> input = (List<or_guestsJSON>) JSON.deserialize(
response.getBody(),
List<or_guestsJSON>.class
);
so that the parser has the type information it needs to create the correct type which in this case is a list.
(For arrays deserializeUntyped always creates the most generic collection type of List<Object>. You can still work with that, but you need additional code to convert to the correct type of list so better to use deserialize when possible.)
I have edited my question with leads instead of guests. When I debug this I get : input(or_leadsJSON:[], or_leadsJSON:[], or_leadsJSON:[], or_leadsJSON:[], or_leadsJSON:[], or_leadsJSON:[], or_leadsJSON:[], or_leadsJSON:[])
@Thomas Not to sure what you mean here. Bottom line is that if the JSON has a fixed structure use deserialize with an explicit type (class).
In this case isnt my or_leadsJSON empty or how do I get cls_stayDetails arrivalDate?
@Thomas Best you add a sample of the JSON that fails to the question. Your class or_leadsJSON is entirely missing any properties which would give you the result you see. If you are trying to support multiple formats in one piece of code, you will need to use deserializeUntyped and handle the differences using explicit map-access code.
if you know a structure of JSON and already have created wrapper to store deserialized result - use deserialize method with type as second param of method
or_guestsJSON input = JSON.deserialize(jsonReplace, or_leadsJSON.class);
you already have parse method, as JSON2Apex generates it as well (looks like you used this tool)
if (response.getStatusCode() == 200) {
or_guestsJSON input = or_guestsJSON.parse(response.getBody());
}
|
Is the demo broken?
The demo looks broken because the footer is just below the fold, is this correct?
No, that's just a result of me not having any sort of reset or normalization on the page. The body element. It has a top and bottom padding in some browsers that pushes everything a bit further down the page.
It doesn't look like a reset issue (although that might help) because the footer is hidden by the same amount as it's height..
View source, find the style section in the head, and add:
* {
margin: 0;
padding: 0;
}
Issue fixed. I use this on TONS of projects, always with a reset or normalize, and it works as expected.
|
Probability - Variance of the square of a random variable
I was looking at the problem under the link below (did not want to post the same problem twice) and I got confused by one of the comments.
We have a random variable $X$ and then we have $C$ = $10$ + $20X$ + $4X^2$.
The first comment under says that $C$ = $10$ + $20X$ + $4X^2$ does not imply that $Var(C)$ = $400Var(X)$ + $16Var(X^2)$.
I am wondering what I am missing here since I did it the same way.
Varience of $Y^2$ given Variance of $Y$
|
<?php
namespace common\logic\entities\system;
use Yii;
use yii\db\ActiveRecord;
use yii\behaviors\TimestampBehavior;
class Logs extends ActiveRecord
{
public static function tableName(){
return '{{logs}}';
}
public function behaviors()
{
return [
[
'class' => TimestampBehavior::className(),
'attributes' => [
ActiveRecord::EVENT_BEFORE_INSERT => ['created_at']
],
],
];
}
public function rules()
{
return [
['text', 'string'],
['file', 'string', 'max' => 255],
['level', 'integer'],
['created_at', 'safe']
];
}
public function attributeLabels()
{
return [
'text' => 'Текст',
'file' => 'Файл',
'level' => 'Рівень',
'created_at' => 'Створено в'
];
}
public static function add($text, $file, $level)
{
$logs = new self();
$logs->text = $text;
$logs->file = $file;
$logs->level = $level;
if (!$logs->save()) {
throw new \RuntimeException('Error save logs.');
}
}
}
|
Adds 'Using your own Azure AD identity' to docs. Closes #1496
Closes #1496
Coverage remained the same at 100.0% when pulling 54cdbde7b2c83881c8d4897f47518bf521284748 on garrytrinder:using-own-identity into 80deeb124a2457c5da6df610e1de582152b47a3e on pnp:dev.
Merged manually. Thanks! 👍
|
Testing a Log statement output in Golang
Hi I want to check that the output of a Log.error() is valid, I have this following code here
func logError(param bool)
bool {
if (param == true)
log.Error(fmt.Sprintf("I need to somehow tst, that the output here is correct"))
return param;
}
I am not allowed to modify my existing code, I just want to ensure that whatever is printed by the console by my logError function, is what I expect it to be.
Is this possible without modifying my existing code, thank you.
The answer depends on which log library you are using.
Apologies, I have just added my Log library.
The Log library I am using is https://github.com/sirupsen/logrus
With logrus, you can capture the output of the logger in a test:
oldOut:=log.StandardLogger().Out // Save current log target
buf:=bytes.Buffer{}
log.SetOutput(&buf)
logError(true)
// Here, buf.String() should give you the log msg
log.SetOutput(oldOut) // Restore log target
|
Rio Hot Carnival
Go Back to Main Page | Go Back to Special Character Teams
Rio Hot Carnival Members
Go Back to Main Page | Go Back to Special Character Teams
|
The copyright line for this article was changed on 14 November 2017 after original online publication.
**Funding agencies**: The Parkinsonism Incidence in North‐East Scotland (PINE) study was supported by Parkinson\'s UK (Grants G‐0502, G‐0914, G‐1302), the Scottish Chief Scientist Office (CAF 12/05), the British Medical Association (BMA) Doris Hillier award, RS Macdonald Trust, the Bupa Foundation, National Health Service (NHS) Grampian endowments, NHS R&D, and SPRING. The ParkWest study was supported by the Research Council of Norway (Grant 177966), the Western Norway Regional Health Authority (Grants 911218 and 911949), and the Norwegian Parkinson\'s Disease Association.
**Relevant conflicts of interests/financial disclosures**: A.D.M. received funding support from the Chief Scientist Office of the Scottish Government, Parkinson\'s UK, NHS Grampian Endowments, the Wellcome Trust, and the University of Aberdeen. O.‐B.T. and J.P.L. have received funding from the Research Council of Norway, the Western Norway Regional Health Authority, and the Norwegian Parkinson\'s Disease Association. C.E.C. has received research funding from Parkinson\'s UK, the Chief Scientist Office of the Scottish Government, the BMA Doris Hillier award, RS Macdonald Trust, the BUPA Foundation, NHS Grampian endowments, NHS R&D, and SPRING. I.D. reports no disclosures.
Parkinson\'s disease (PD) is a progressive disabling disorder with higher mortality, disability, and dementia than in controls.[1](#mds27177-bib-0001){ref-type="ref"}, [2](#mds27177-bib-0002){ref-type="ref"} Being able to predict outcome has many benefits, including individualized risk prediction with improved information for patients, stratifying or personalizing treatments according to prognosis, improving design of clinical trials (eg, selection of participants, stratifying randomisation, or adjustment for covariates), and adjusting for case‐mix when comparing different cohorts.[3](#mds27177-bib-0003){ref-type="ref"}, [4](#mds27177-bib-0004){ref-type="ref"} It is important that appropriate methods are used to develop prognostic models, including a representative patient sample and adequate external validation to demonstrate that the model can be used in settings other than those in which it was developed.[3](#mds27177-bib-0003){ref-type="ref"}, [4](#mds27177-bib-0004){ref-type="ref"}
Only one externally validated prognostic model has been published for use in PD, but it is limited to predictions at a single timepoint (at 5 years) and uses a single composite outcome.[5](#mds27177-bib-0005){ref-type="ref"} No prognostic models have been published for specific outcomes in PD. We therefore aimed to (1) develop prognostic models for predicting 3 important outcomes over time in PD, that is, mortality, dependency (needing help with basic activities of daily living such as walking, dressing, toileting), and the composite outcome of "death or dependency" (which may be a useful simple clinical measure of disease progression)[6](#mds27177-bib-0006){ref-type="ref"} and (2) to validate these models in an international cohort. We have previously published data on individual predictors of dependency and "death or dependency" in PD,[7](#mds27177-bib-0007){ref-type="ref"} but this paper extends this work significantly by combining prognostic factors to develop and validate predictive models for these outcomes and mortality.
Materials and Methods {#mds27177-sec-0002}
We developed the prognostic models in the Parkinsonism Incidence in North‐East Scotland (PINE) study and performed external validation in the ParkWest study in prospective, population‐based incident cohorts of PD (ie, which attempted to recruit and follow‐up all new PD cases in the specified time period and area).
PINE Study (Development Cohort) {#mds27177-sec-0003}
The PINE study was recruited during the following 2 incidence periods: an 18‐month pilot phase in area with population of 148,600 beginning November 2002 and the 36‐month main study phase in population of 317,357 people beginning April 2006.[8](#mds27177-bib-0008){ref-type="ref"}, [9](#mds27177-bib-0009){ref-type="ref"}, [10](#mds27177-bib-0010){ref-type="ref"} Patients were recruited using multiple, overlapping strategies for case ascertainment, including writing to general practitioners and hospital specialists asking them to refer suspected cases, hand‐searching neurology/geriatrics referral letters, and electronic searching of general practice and hospital discharge databases. All those referred or identified through the searches and who did not have a previous diagnosis of a parkinsonian disorder were invited to be assessed by a neurologist with a special interest in movement disorders (or supervised trainee). Those with parkinsonism (defined as 2 or more of rest tremor, bradykinesia, rigidity, or unexplained postural instability) were invited to consent to long‐term annual follow‐up. Consenting patients were reviewed annually with a range of clinical assessments. Only those diagnosed with idiopathic PD (guided by the UK PD Society Brain Bank criteria)[11](#mds27177-bib-0011){ref-type="ref"} were included in this analysis.
ParkWest Study (Validation Cohort) {#mds27177-sec-0004}
The ParkWest study sought to recruit all new PD cases over 22 months from November 1, 2004, in 4 Norwegian counties comprising a population of 1,052,075.[12](#mds27177-bib-0012){ref-type="ref"} Similar to the PINE study, multiple, overlapping strategies were used for case ascertainment, including hand‐searching referral letters, notification of general practitioners and relevant hospital specialists asking them to refer suspected cases, and electronic searching of hospital databases and general practitioners\' electronic medical records systems. All new cases were invited to consent to follow‐up with twice‐yearly assessment, including a range of clinical assessments. PD diagnoses were made using the UK PD Society Brain Bank criteria[11](#mds27177-bib-0011){ref-type="ref"} and the Gelb criteria.[13](#mds27177-bib-0013){ref-type="ref"}
Both studies were approved by appropriate ethics committees (Multi‐centre Research Ethics Committee for Scotland, Edinburgh, UK, University of Bergen, Bergen, Norway) and were conducted with the informed consent of the patients involved.
### Outcome Definition {#mds27177-sec-0005}
Data on mortality were derived from notifications by relatives/general practitioners plus surveillance by the UK national death registers in the PINE study. Functional dependency was measured by the Schwab & England scale[14](#mds27177-bib-0014){ref-type="ref"} at follow‐up visits and defined using a cut‐off of \< 80% (80% = completely independent in most chores; 70% = not completely independent). The word *chores* was consistently interpreted as basic activities of daily living (walking, personal hygiene, dressing, toileting, feeding) by both study teams. The Schwab & England scale has been partly validated for use in PD as a measure of activities of daily living,[15](#mds27177-bib-0015){ref-type="ref"}, [16](#mds27177-bib-0016){ref-type="ref"}, [17](#mds27177-bib-0017){ref-type="ref"}, [18](#mds27177-bib-0018){ref-type="ref"} but its validity as a dichotomous measure of dependency/independency has not been established. Nevertheless, it does have face validity for this purpose.
### Predictor Variables {#mds27177-sec-0006}
We selected potential baseline predictors (ie, measured at diagnosis) to include in the model based on previously reported associations,[1](#mds27177-bib-0001){ref-type="ref"}, [19](#mds27177-bib-0019){ref-type="ref"} a previous analysis of the measures of motor impairment with best predictive value in the PINE study (in which measures of axial severity were better predictors of long‐term outcomes than other measures of motor function, including the postural‐instability‐gait‐difficulties/tremor‐dominant classification),[20](#mds27177-bib-0020){ref-type="ref"} and clinical knowledge. We limited the number of candidate predictors to avoid overfitting.[21](#mds27177-bib-0021){ref-type="ref"} We included age in the models irrespective of statistical significance because, on the basis of previous studies and clinical knowledge, it strongly predicts many outcomes in PD. The other candidate baseline variables were selected using a backward stepwise selection process (see Model Development): sex, pack years of smoking history, Charlson comorbidity score,[22](#mds27177-bib-0022){ref-type="ref"} severity of bradykinesia (sum of bradykinesia items from UPDRS \[part III\] motor score), severity of axial features (sum of speech, facial expression, face tremor, neck rigidity, arising from chair, posture, gait, and postural instability items from the UPDRS \[part III\] motor score), mini‐mental state examination (MMSE) score, and Hoehn & Yahr stage. We previously compared the Charlson comorbidity score with 2 other scales and found it was more reliable and had better predictive validity.[23](#mds27177-bib-0023){ref-type="ref"} There were no missing data for predictor variables in either study. Treatment‐related variables were not included to allow the models to be used at time of diagnosis (ie, before treatment initiation) and in trials of de novo treatment in PD.
### Model Development {#mds27177-sec-0007}
We developed 3 models to predict time to all‐cause mortality, time to dependency, and time to "death or dependency." We used Weibull proportional hazards parametric survival modelling to allow direct estimation of the baseline hazard function (the hazard function when centred covariates are set to 0), for ease of out‐of‐sample prediction and for straightforward validation. We investigated other parametric distributions of the baseline hazard, but none provided better fit adjusted for complexity (assessed by the Bayesian information criterion). Univariable analysis was performed with each candidate predictor in turn, and then those variables with association with the outcome of interest (*P* \< .2) were included in a backward stepwise regression model. A probability cut‐off of .1 was used for removal of variables from the model (other than age). We checked whether the proportional odds or probit scale fitted better than the proportional hazards scale, but they did not. Functional form was tested by assessing whether a 2‐power fractional polynomial (ie, nonlinear terms) provided better fit.[24](#mds27177-bib-0024){ref-type="ref"} The influence of individual observations on the models was assessed by calculating the likelihood displacement.[25](#mds27177-bib-0025){ref-type="ref"} Because the effect of baseline Charlson score on mortality varied with time from the baseline assessment, an interaction between Charlson score and 2 discrete periods of time was added to the model (with approximately equal numbers of deaths in each time period), resulting in significantly improved fit (*P* = .001). The significance of interactions between age and other variables in the model were assessed, but other interactions were not tested because of limited power. Shrinkage was not applied during prognostic modelling development as the shrinkage factors were all \>0.85.[26](#mds27177-bib-0026){ref-type="ref"}
For the dependency model, patients who were dependent at time of diagnosis were excluded and patients who died or were lost to follow‐up prior to becoming dependent were censored at the time they were last seen. We assumed that censoring because of death was independent of dependency because most deaths in those who were not previously known to be dependent were not a result of PD and therefore unlikely to be related to dependency. Patients remaining alive and independent were censored at the time of their last visit (or up until January 19, 2015 for surviving patients in the PINE study). Two patients were excluded from the development of the mortality model and 1 from the dependency model because of unusual outlying values together with high influence on the model.
### Model Validation {#mds27177-sec-0008}
We assessed validation by measuring discrimination (the ability of a model to distinguish different risks between individuals) and calibration (the degree of agreement between observed event probability and predicted event probability in groups of patients defined by the prognostic index \[*xβ*\]). Discrimination was measured using the C‐statistic, the proportion of all possible pairs of observations in the dataset correctly ranked in terms of risk.[27](#mds27177-bib-0027){ref-type="ref"} Calibration was assessed by plotting observed versus predicted survival probabilities in 4 quantiles of predicted risk derived from the models (ie, the prognostic index \[*xβ*\]). First, apparent discrimination and calibration was assessed, that is, the direct performance of the models in the PINE dataset in which they were created. Second, (so‐called) optimism‐adjusted estimates of discrimination in the PINE dataset were assessed using 500 bootstrapped samples for each model.[3](#mds27177-bib-0003){ref-type="ref"}, [28](#mds27177-bib-0028){ref-type="ref"} Third, the models developed in the PINE study were externally validated by measuring their discrimination and assessing their calibration in the ParkWest study.[3](#mds27177-bib-0003){ref-type="ref"}, [28](#mds27177-bib-0028){ref-type="ref"}
### Model Recalibration {#mds27177-sec-0009}
The models were recalibrated to account for a different baseline risk in the ParkWest study.[29](#mds27177-bib-0029){ref-type="ref"} This was done by iterating the constant and shape parameter of the model so that the curve of mean predicted survival probabilities for all patients in the ParkWest study was a close fit to the observed Kaplan‐Meier survival probabilities (leaving the other parameter estimates unchanged). The calibration plots were repeated using the new constant and shape parameter to derive the predicted values.
All statistical analyses were performed with Stata version 12.1 (StataCorp LP, College Station, Texas). Appropriate reporting guidelines have been followed.[30](#mds27177-bib-0030){ref-type="ref"}
Supplementary Figure 1 shows recruitment to the PINE and ParkWest studies. Consent to follow‐up was higher in the PINE study than in the ParkWest study (94% vs 81%). A total of 198 patients with PD in PINE and 192 patients with PD in ParkWest were included in the analyses of mortality. Of the patients, 22 (11%) were excluded from analyses of dependency in the PINE study and 30 in the ParkWest study because they were already dependent at baseline (16%). The patients in the PINE study were older (mean age at diagnosis 72.5 vs 67.9), had shorter median symptoms duration at baseline assessment (13 vs 20 months), higher smoking history, slightly higher disease impairment and disease stage, and more comorbidities (Table [1](#mds27177-tbl-0001){ref-type="table-wrap"}). Follow‐up data were available for between 6 and 12 years from diagnosis in the PINE study and between 6 and 8 years from diagnosis in the ParkWest study.
::: {#mds27177-tbl-0001 .table-wrap}
Baseline variable PINE, N = 198 ParkWest, N = 192
-------------------------------------------- --------------- -------------------
Mean age in years at diagnosis (SD) 72.5 (10.4) 67.9 (9.3)
Number male (%) 119 (60) 117 (61)
Median symptom duration in months (IQR) 13 (9‐24) 20.0 (13.6‐36.8)
Mean H&Y stage (SD) 2.3 (0.8) 1.9 (0.6)
Mean UPDRS motor score (SD) 25.1 (11.6) 23.5 (11.2)
Mean MMSE (SD) 28.1 (2.3) 27.8 (2.5)
Median Charlson score (IQR) 1 (0‐2) 0 (0‐1)
Median pack years of smoking history (IQR) 0 (0‐15) 8 (3‐20)
IQR, interquartile range; PINE, Parkinsonism Incidence in North‐East Scotland; SD, standard deviation.
Mortality was higher in the PINE study than in the ParkWest study (see Fig. [1](#mds27177-fig-0001){ref-type="fig"}A). We developed 2 models predicting mortality, with and without the Charlson comorbidity index, to enable use in settings where comorbidity data is not available. Age, sex, and severity of axial features were included in both models (Table [2](#mds27177-tbl-0002){ref-type="table-wrap"}). The model increased mortality with increasing comorbidity burden in the first 4 years of follow‐up and a nonsignificant decrease in mortality with increasing baseline Charlson score after 4 years follow‐up. Apparent discrimination and calibration were very good (C‐statistics 0.75 and 0.73 for model with and without Charlson score, respectively; see calibration plot in Fig. [2](#mds27177-fig-0002){ref-type="fig"}A). Calibration plots for the model without Charlson score are not shown, but are almost identical. Both models discriminated better in the external cohort than internally (C‐statistics 0.76 and 0.78 for models with and without comorbidity burden). However, although the calibration plot in the ParkWest study showed good separation into groups according to prognostic risk, the model tended to overestimate risk of death except in the highest‐risk quantile (Fig. [2](#mds27177-fig-0002){ref-type="fig"}B). Using the recalibrated model, calibration was very good (Fig. [3](#mds27177-fig-0003){ref-type="fig"}A).
::: {#mds27177-fig-0001 .fig}
Plots of survival in the Parkinsonism Incidence in North‐East Scotland (PINE) and ParkWest studies. Plots of Kaplan‐Meier probability of (**A**) survival, (**B**) remaining independent (with deaths censored), and (**C**) remaining alive and independent. Colored bands represent 95% confidence bands for the Kaplan‐Meier survival probabilities. Vertical marks represent censored observations. \[Color figure can be viewed at [wileyonlinelibrary.com](http://wileyonlinelibrary.com)\]
::: {#mds27177-fig-0002 .fig}
Internal and external calibration plots. Plots of model calibration showing the observed and predicted probabilities of outcome in quantiles of predicted risk of survival in the Parkinsonism Incidence in North‐East Scotland (PINE) study (**A**) and in the ParkWest study (**B**), of remaining independent in the PINE study (**C**) and in the ParkWest study (**D**), and of remaining alive and independent in the PINE study (**E**) and in the ParkWest study (**F**). The dashed lines indicate the probabilities predicted by the model, and the solid lines indicate the Kaplan‐Meier survival function. \[Color figure can be viewed at [wileyonlinelibrary.com](http://wileyonlinelibrary.com)\]
::: {#mds27177-fig-0003 .fig}
Recalibrated model calibration plots. Plots of model calibration showing the observed and predicted probabilities of outcome in quantiles of predicted risk in the models recalibrated for the baseline risk in the ParkWest study: (**A**) survival, (**B**) dependency, and (**C**) death or dependency. The dashed lines indicate the probabilities predicted by the model and the solid lines indicate the Kaplan‐Meier survival function. \[Color figure can be viewed at [wileyonlinelibrary.com](http://wileyonlinelibrary.com)\]
::: {#mds27177-tbl-0002 .table-wrap}
C‐statistic (95% CI) -- model discrimination
------------------------------------------------------------------ ------------------------ ------------------ ---------------------------------------------- ------ ------------------
All‐cause mortality Age (10‐year increase) 2.02 (1.51‐2.71) 0.75 (0.70‐0.80) 0.73 0.76 (0.68‐0.85)
Male sex 1.78 (1.13‐2.82)
Axial severity (5‐point increase) 1.33 (1.08‐1.66)
Charlson score (effect in first 4 years of follow‐up) 1.31 (1.12‐1.52)
Charlson score (effect after first 4 years) 0.83 (0.63‐1.08)
Shape parameter 2.28 (1.90‐2.74)
Constant −2.66 (−3.09 to 2.23)
All‐cause mortality (alternative model excluding Charlson score) Age (10‐year increase) 2.12 (1.58‐2.84) 0.73 (0.68‐0.78) 0.71 0.78 (0.70‐0.86)
Male sex 1.85 (1.17‐2.91)
Axial severity (5‐point increase) 1.41 (1.13‐1.76)
Shape parameter 1.92 (1.61‐2.28)
Constant −2.38 (−2.77 to 2.00)
Functional dependency Age (10‐year increase) 2.15 (1.61‐2.86) 0.77 (0.72‐0.82) 0.74 0.68 (0.61‐0.75)
Smoking history (10‐pack‐year increase) 1.15 (1.05‐1.27)
Axial severity (5‐point increase) 1.74 (1.28‐2.35)
MMSE score 0.86 (0.77‐0.96)
Shape parameter 1.85 (1.56‐2.18)
Constant 1.15 (0.05‐28.1)
Death or dependency Age (10‐year increase) 1.91 (1.50‐2.44) 0.74 (0.69‐0.79) 0.73 0.68 (0.62‐0.75)
Smoking history (10‐pack‐year increase) 1.16 (1.07‐1.26)
Axial severity (5‐point increase) 1.56 (1.18‐2.05)
MMSE score 0.86 (0.78‐0.95)
Shape parameter 1.66 (1.43‐1.92)
Constant 1.89 (0.11‐32.8)
The probabilities of developing sustained dependency over time were higher in the PINE study than in the ParkWest study (Fig. [1](#mds27177-fig-0001){ref-type="fig"}B). Median time until dependency was 5.5 years in the PINE study, but was not reached in the ParkWest study. The model of dependency developed in PINE included age, smoking history, severity of axial features, and MMSE score (Table [2](#mds27177-tbl-0002){ref-type="table-wrap"}). This model had relatively high apparent discrimination (C‐statistic 0.77) and very good calibration (Fig. [2](#mds27177-fig-0002){ref-type="fig"}C). Discriminative performance was also very good in the validation cohort (C‐statistic 0.75), and although the calibration plots showed clear separation by prognostic risk, there was systematic overestimation of risk of dependency in the validation cohort (Fig. [2](#mds27177-fig-0002){ref-type="fig"}D). However, the recalibration plots show much better calibration (Fig. [3](#mds27177-fig-0003){ref-type="fig"}B).
Death or Dependency {#mds27177-sec-0013}
The risk of becoming "dead or dependent" was substantially higher in the PINE study than in the ParkWest study during most of the follow‐up period (see Fig. [1](#mds27177-fig-0001){ref-type="fig"}C). The model of "death or dependency" developed in PINE included the same variables as in the model of dependency (Table [2](#mds27177-tbl-0002){ref-type="table-wrap"}). This model had good apparent discrimination (C‐statistic 0.74) and very good calibration (Fig. [2](#mds27177-fig-0002){ref-type="fig"}E). The model discriminated slightly better in the ParkWest study (C‐statistic 0.76). The calibration plots showed clear separation by prognostic risk, but there was systematic overestimation of risk of "death or dependency" in the validation cohort (Fig. [2](#mds27177-fig-0002){ref-type="fig"}F). The recalibrated model showed much improved calibration (Fig. [3](#mds27177-fig-0003){ref-type="fig"}C).
For each model, assumptions were satisfied, linear form was appropriate for interval variables, and there was no evidence for interactions between age and other variables. Supplementary Appendix 1 contains a risk prediction calculator.
These 3 prognostic models combine clinical features at the time of diagnosis to predict important clinical outcomes in PD. They performed well in the PINE cohort and when tested in the ParkWest cohort, they had very good discrimination. Although there was good separation into prognostic groups, there was a systematic overestimation of risk in the patients in the ParkWest study. We developed recalibrated models that had good discrimination and calibration in the Norwegian cohort.
These models are novel. Although many previous studies have studied prognostic factors for mortality and dependency in PD,[1](#mds27177-bib-0001){ref-type="ref"}, [19](#mds27177-bib-0019){ref-type="ref"} and another study has developed, but not externally validated, a prognostic model for several outcomes including mortality,[31](#mds27177-bib-0031){ref-type="ref"} we are unaware of any externally validated prognostic model that can be used to calculate risk of specific outcomes in PD. One recent study has published a prognostic model developed in the Netherlands, and validated in England, which combined 3 variables (age, severity of axial features, and verbal fluency) to predict a composite outcome (postural instability, dementia, or death) at 5 years.[5](#mds27177-bib-0005){ref-type="ref"} Although this model discriminated well (C‐statistic 0.77 in the development cohort and 0.85 in the validation cohort) and calibrated well, its use is limited to predictions at a single timepoint and the components of the composite outcome are not equal in severity. Our models have the distinct advantages of predicting risk at multiple timepoints and of predicting specific outcomes.
We do not here discuss particular prognostic factors for dependency outcomes as we have done so previously.[7](#mds27177-bib-0007){ref-type="ref"} The finding that comorbidity was associated with mortality but not the dependency outcomes may be because many deaths, particularly early deaths, were related to comorbid disease, whereas most disability was related to PD itself. The interaction between comorbidity burden and time suggests that baseline comorbidity is more important for early mortality than for later mortality (given survival beyond year 4).
This study has 3 principal strengths. The first lies in the study designs, which both aimed to reduce selection bias by attempting to include all patients in the population with newly diagnosed PD. However, because PD is predominantly a disease of the elderly, there were relatively few young‐onset cases studied (8.5% \< 55 at diagnosis). Although we are unaware of evidence that the effects of the prognostic factors are modified by age, the models should be used cautiously in young‐onset patient groups until they have undergone further validation in these groups.
The second main strength is the international external validation of the models. The key threat to model validity is overfitting as the model may fit too closely the idiosyncrasies of the development dataset resulting in overoptimistic estimates of model performance.[3](#mds27177-bib-0003){ref-type="ref"} Demonstrating that the model discriminates well in another cohort provides direct evidence of its generalizability to other settings and utility for certain applications. The third strength is that the models were developed following recommendations for prognostic studies[4](#mds27177-bib-0004){ref-type="ref"} using appropriate statistical methods.
An important limitation of this study relates to sample size. Although with about 100 deaths in the development cohort about 10 predictors can be studied without excessive overfitting,[21](#mds27177-bib-0021){ref-type="ref"} this limited selection of candidate predictors and the investigation of potential interactions in the models. Therefore further work in larger studies or combining studies could result in better models for individualized risk prediction.
A second important limitation is poor calibration of the models in the external cohort, which is probably mainly attributable to the higher overall risk of mortality and dependency in the PINE study. This must be related to factors which were not included (and therefore adjusted for) in the models. Differences in mortality are most likely explained by differences in non‐PD‐related mortality as it is unlikely the pathogenesis of PD is fundamentally different between the 2 countries and the burden of the diseases that most commonly lead to death (cardiovascular disease, respiratory disease, and malignancy) is higher in the United Kingdom than in Norway,[32](#mds27177-bib-0032){ref-type="ref"} which is reflected in the higher mortality rates in the United Kingdom than in Norway.[33](#mds27177-bib-0033){ref-type="ref"} Although there are no comparative population data on dependency available, the comorbidity rate was higher in the PINE study than in the ParkWest study, which may have led to higher dependency risk in the PINE study. Other possible explanations for these differences include the older average age of PINE participants and the lower consent rate in the ParkWest cohort if frailer patients were less likely to consent.
Because we have demonstrated the external validity of these models in terms of discrimination, we anticipate that these models will have several uses as research tools that separate patients into groups according to prognostic risk. These include in clinical trials design (eg, selection of participants for inclusion based on baseline predicted prognosis, stratification of randomization, and adjustment of analyses), adjustment for confounding in observational studies, and adjustment for case‐mix (eg, in comparing cohorts from different studies, countries, hospitals).[3](#mds27177-bib-0003){ref-type="ref"} These models combine simple and easy‐to‐collect variables that can easily be gathered in the clinic or in a research context.
Similarly, these models could also be used in clinical practice for stratification of treatment according to prognostic risk. Although there is no definite indication for this at present, this may be useful if disease modifying treatments with potentially serious side effects become available for PD. For example, they could be used to select people with the worst prognosis to try such treatments. However, these models are only a starting point; before these models can be used for individualized or personalized medicine, we need (1) further validation; (2) improved prediction, for example, adding biomarkers such as genetic or imaging factors; (3) simple implementation for use in clinical practice; and (4) evaluation of benefit versus harm, ideally in randomized trials[34](#mds27177-bib-0034){ref-type="ref"}, [35](#mds27177-bib-0035){ref-type="ref"} because the use of models to guide treatments may cause harm as well as benefit (eg, from false negative or false positive predictions). It will be important to develop flexible dynamic models that use accumulating data over time (such as disease progression, motor or nonmotor complications) to predict later outcomes but clearly those data are not available at diagnosis, and therefore models that use baseline data only are relevant for use in early disease.
Although prognostic models that discriminate well can be useful for research purposes and for treatment stratification even if they do not calibrate well, individualized risk prediction requires better precision than these uses and must calibrate well in the settings in which they are used. Although the original models worked well in North‐East Scotland, it was necessary to recalibrate to the ParkWest population in Western Norway. Therefore, the models should be recalibrated before use for individualized risk prediction in other geographical areas. This can be easily done if estimates of survival rate or progression to dependency are available.
In conclusion, we have developed and validated prognostic models to predict important outcomes in PD that use predictors that can be easily measured in the clinic setting. We have demonstrated that these models have sufficient validity to be used in a research context, but that recalibration is required before use in other geographical areas for individualized risk prediction. Further work includes (1) developing more‐accurate models with individual‐patient data meta‐analyses of representative studies; (2) further validation in a young‐onset cohort; (3) further simplification for use in case‐mix correction (eg, to identify which components of the axial features variable need to be collected); (3) updating these models to include biomarker data, for example, genetic, imaging, or biochemical data; (4) updating baseline risk in the models in the future if, for example, disease‐modifying treatments are introduced, which would alter the natural history of the disease; and (5) evaluation of their use in clinical management of individual patients. The use of these models in randomized controlled trials to stratify randomization by baseline prognosis would allow further validation by comparing participants\' predicted and actual outcome.
Author Roles {#mds27177-sec-0016}
1\) Research project: A. Conception, B. Organization, C. Execution; 2) Statistical Analysis: A. Design, B. Execution, C. Review and Critique; 3) Manuscript: A. Writing of the first draft, B. Review and Critique.
A.D.M.: 1A, 1B, 1C, 2A, 2B, 3A, 3B
I.D.: 2C, 3B
O.‐B.T.: 1A, 1B, 1C, 3B
J.P.L.: 1A, 1B, 1C, 3B
C.E.C.: 1A, 1B, 1C, 2C, 3B
Financial disclosures for previous 12 months {#mds27177-sec-0017}
A.D.M. has received funding support from Parkinson\'s UK, NHS Grampian Endowments, the Wellcome Trust, the University of Aberdeen, and the Academy of Medical Sciences. O.‐B.T. has given lectures for several pharmaceutical companies and is on the editorial board of *Acta Neurologica Scandinavica*. J.P.L. was associate editor of the *Journal of Parkinson\'s Disease* 2012 to 2016 and has received research funding from the Western Norway Health Trust, project support, 2013 to 2018. C.E.C. has received research funding from Parkinson\'s UK and NHS Grampian Endowments. I.D. reports no disclosures.
Additional Supporting Information may be found in the online version of this article at the publisher\'s website
Supplementary Information 1
Click here for additional data file.
Supplementary Information 2
Click here for additional data file.
Supplementary Information 3
Click here for additional data file.
We would like to thank study participants, study personnel, and study funders.
|
#pragma once
#include "nucleotides.hpp"
#include <string>
#include <vector>
namespace bloom_params
{
/* 1 << 20 - 1 Megabyte
* 1 << 21 - 2 Megabyte
* 1 << 24 - 16 Megabyte
*/
constexpr static const double Fc = 16. / 2.08; // <- wanted false positive rate factor, false positive rate is F = (Fc * k)^-1
}
struct bloom_filter
{
// m - number of bits in the table (not bytes, we have vector<bool>!)
// k - number of hash functions to use
// optimal k is (m/n)ln 2, n is number of elements to be inserted
bloom_filter(std::size_t m, std::size_t k)
: k(k), table(m, false)
{ }
void add(const Nucleotides& text);
bool contains(const Nucleotides& text) const;
private:
std::size_t k;
std::vector<bool> table;
};
// based on Quingpeng et al. (2014)
struct counting_bloom_filter
{
// m - number of bits in the table
// k - number of hash functions to use
// optimal k is (m/n)ln 2, n is number of elements to be inserted
counting_bloom_filter(std::size_t m, std::size_t k)
: k(k), table(m, 0)
{ }
void add(const Nucleotides& text);
unsigned short count(const Nucleotides& text) const;
private:
std::size_t k;
std::vector<unsigned short> table;
};
|
Steel manufacture
ABSTRACT
A method for desulphurizing steel in heats over 1 metric ton in a container, such as a ladle furnace. The container is provided with a basic slag line and additionally with a lining which substantially prevents oxygen from leaking in through or from the lining. Basic slag-formers such as lime are added to the steel melt in the container in order to obtain highly basic slag and other desulphurizing agents such as misch metal may be added. The melt is well deo xi di zed by means of vacuum degassing or precipitation deo xidation, and subjected to vigorous stirring and heating during the process.
United States Patent [1 1 Carlsson et al.
[ STEEL MANUFACTURE [75] Inventors: Lars Erik Carlsson, Borlange; Nils Fredrik Grevillius; Lars Ivar Hell ner, both of Karlskoga, all of Sweden [73] Assignee z' Allman na Svenska Elektriska Aktiebolaget, Vasteras, Sweden 221 Filed: Feb. 20, 1973 211 Appl. No.: 333,476
Related U.S. Application Data [63] Continuation-impart of Ser, No. 305 ,681, Nov. 13, I972, abandoned, which is a continuation of Ser. No. 54,480, July 13. I970, abandoned.
[30] Foreign Application Priority Data July 15, I969 Sweden 9974/69 [52] U.S. Cl. 75/58; 75/49; 75/54; 75/55; 75/57 [51] lnt. Cl. CZIC 7/02; C2lC 7/06;C21C 7/lO 5] Dec. 9, 1975 Primary Examiner-Winston A. Douglas Assistant Examiner-Mark Bell [57] ABSTRACT A method for desulphurizing steel in heats over I metric ton in a container, such as a ladle furnace. The container is provided with a basic slag line and additionally with a lining which substantially prevents oxygen from leaking in through or from the lining. Basic slag-formers such as lime are added to the steel melt in the container in order to obtain highly basic slag and other desulphurizing agents such as misch metal may be added. The melt is well deo xi di zed by means of vacuum degassing or precipitation deo xidation. and subjected to vigorous stirring and heating during the process.
3 Claims, 1 Drawing Figure U.S. Patent Dec. 9, 1975 3,925,061
STEEL MANUFACTURE RELATED APPLICATIONS This application is a continuation-in-part of application Ser. No. 305,681 filed Nov. I3, 1972 which is in turn a streamlined continuation of application Ser. No. 54,480, filed July I3, 1970, both now abandoned.
BACKGROUND OF THE INVENTION l. Field of the. Invention The present invention relates to a method of manufacturing high-class steel in heats over 1 ton in a container, for example a ladle furnace.
2. The Prior Art High-grade steel must fulfil high standards of freedom from non-metallic inclusions and other impurities. This means, for instance, that the phosphorus, oxygen and sulphur contents of the steel must be low and the tapping and casting carried out correctly. The most usual method hitherto used of manufacturing highgrade steel is melting in electric arc furnaces by two slag methods. The tap to tap time is thus divided into two main periods: the first covering deo xidation and desulphurizing. The latter period, called the reducing period, might comprise 30% of the total tap to tap time. By virtue of modern degassing methods, principally the ASEA-SKF process developed in Sweden, a steel having very slight content of oxide inclusions can be manufactured without a reducing period in the melting furnace (ASEA Journal 39(l966):6-7, pages 87-95). In previously known degassing processes, however, the desulphurizing is negligible. With the method developed according to which desulphurization is effected simultaneously with the deo xidation, a considerable increase in production can be achieved and at the same time the steel manufactured in this way is of extremely high quality.
Desulphurizing according to the two-slag process in an electric arc furnace is a time-consuming and laborious method and it is therefore expensive. Neither is sufficiently low oxygen potential achieved with this method. The yield from the additives for desulphurizing is therefore unsatisfactory. Considerable efforts have been made to obtain a high-quality desulphurized steel on an industrial scale in containers outside the electric arc furnace. However, so far this has not been achieved, which is probably due principally to too short treating times without the possibility of heating, and to insufficient stirring. Desulphurizing on an experimental scale has been reported to produce very low contents using desulphurizing agents such as SiCa, AlCa and CaC for example.
SUMMARY OF THE INVENTION The invention aims at carrying out desulphurization in a container outside the arc furnace on an industrial scale. The advantages of the invention are that desulphurization can be carried out very cheaply and to extremely low percentages of sulphur and the capacity of the furnace is increased.
The method demands that certain practical problems, for instance concerning oxygen content, durability of the lining, oxygen leakage from the lining and bath surface and the contact between steel and desulphurizing agent must be solved. The invention is characterised in that lime and/or some other basic slag former is added to a steel melt in the container to ob- 2 tain highly basic slag; and other desulphurizing additives may be used, especially misch metal, the melt being well deo xi di zed and being subjected to vigorous stirring and heating during the process.
For practical reasons the desulphurizing process should be carried out in the same ladle furnace as is used for degassing the steel, but it may also be carried out in another container. The desulphurizing process is based on reaction with a molten slag phase, which must be highly basic, and additions of solid reaction agent, principally misch metal. Steel furnaces intended for operation under vacuum are usually lined with neutral brick which is, however, attacked by basic slags. Furnaces in which desulphurization is carried out according to conventional methods are usually lined basically. Such linings are sensitive to temperature fluctuations, which makes them unsuitable for use in containers and furnaces of the type intended.
The invention is particularly characterised by the fact that aluminum is added to keep the oxygen activity low; that the furnace wall, at least at the slag line, is formed of basic brick; and that the misch metal is introduced without contact with the molten slag at a point where the melt is on a downward part of the stirring path, so as to prevent to a great extent Contact between the misch metal and the molten slag.
A steel manufactured in this manner is of extremely high quality and its manufacture may be carried out on a large scale at low costs. The steel obtained can be cast continuously or in batches.
BRIEF DESCRIPTION OF THE DRAWING The drawing shows in cross-section a furnace of the type which may be used in carrying out the invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS The method according to the above may be used for example in a furnace of the type used for the ASEA- SKF process and which is shown in the drawing (see also application of Karlsson et al. Ser. No. 538,633, filed Mar. 30, I966, now abandoned). This is a ladle furnace with the ladle l1 and its lining 22. The basic slag line is shown at 21. The basic slag line is always manufactured from basic brick. The lining may otherwise be made in a high-value neutral brick containing A1 0 or in basic brick. In either event, the lining is such as or at least substantially to prevent leakage of oxygen from the lining into the melt.
A typical basic slag line may have the following composition:
96 97% MgO 0.7% sio, 0.3% M20; 0.2% mo, 03% 0,0, 1.4% CaO (Steetly MSB) In the rest of the lining, the composition may be:
21% sio,
2.6% Tio,
73% Alp,
0.2% CaO 0.2% MgO 0.3% alkali metal com positions.
3 Type Hogan as H W M (Harbison Walker) A steel melt may be tapped into such container or ladle which is provided with a lid having through electrodes, and the melt is thus heated to a certain temperature by means of electric arcs under the lid. In the meanwhile lime is added which melts and a basic and well reduced slag is formed. Stirring is carried out the whole time by electromagnetic multiphase stirrers. As shown in the drawing, this stirring has a vertical nature, that is, the melt moves in a pattern having upward and downward components. The container is then provided with a vacuum lid with evacuating means and degassing is carried out to reduce the percentage of oxygen and other noxious gases. When the desired degree of degassing has been achieved, the vacuum is removed and aluminum and then misch metal are added (for example, half the total amount of misch metal), the melt still being stirred and heated, for example for about minutes after which aluminium, if it is to be added, and part of the remaining quantity of misch metal are added while the melt is stirred and heated for another 15 minutes. Aluminum and the remainder of the misch metal are then added and the melt stirred for approximately the same length of time. The misch metal may be added in one step or in several, as in the example. If the process is used in a container without vacuum treatment, this is replaced by precipitation deo xi dization with a strong deo xidant, for example aluminum. The melt obtained in this way is of high quality with low sulphur and oxygen contents.
if the melt has a sufficiently high temperature when it is tapped into the container, the vacuum may be applied directly, after which the highly basic slag is produced and aluminum and misch metal are added during heating and stirring. The vacuum treatment is carried out until the desired low gas content is achieved.
The electro-magnetic stirring may be replaced by stirring by means of blowing in gas or mechanical stirring (mechanical stirrer or vibratory ladle) and the heating may also be carried out by some other means than with electric arcs.
The purpose of the stirring is to ensure that all parts of the melt will be reached by the degassing effect and to effect satisfactory contact between the desulphurizing slag and any added desulphurizer and the steel melt.
Leakage of oxygen from the lining to the melt is prevented by using a basic lining or high-value lining of neutral brick containing A1 0 At the slag line the lining should be basic to prevent it from being strongly attacked by the highly basic slag.
The desulphurizing process requires a well deo xi di zed steel. This is obtained in the ladle by means of vacuum treatment with a vacuum lid applied on the container or a vacuum tank surrounding the container and/or by the addition of a powerful deo xidant to the slag, for example aluminum, and stirring the melt by means of electro-magnetic low-frequency stirrers or by blowing in gas or by mechanical means.
During desulphurizing the melt should be covered by molten highly basic slag preferably prepared from lime, reduced with aluminum and possibly with the addition of fluxing agent. Fluospar may be added at the time of casting in order to prevent the slag from freezing. The lime should be well dried to prevent increased hydrogen content in the melt. The highly basic slag prevents disturbing leakage of oxygen from the bath surface and also has a partial desulphurizing effect. In many cases the desulphurizing obtained in this way is quite suffrcient.
The lime should be added in quantities of 0.2 2.0, suitably 0.3 1.5 per cent by weight, preferably 0.5 1.0 per cent by weight of the total charge weight. Misch metal is added for the desulphurizing process in quantities of up to l% of the charge weight, suitably up to 0.3%, preferably 0.l 0.2
Calcium may also be added for the desulphurizing process, preferably in the form of calcium alloys corre sponding to up to about 0.5 per cent by weight calcium of the charge weight, preferably 0.2 0.3%, or magnesium may be added for the same purpose, preferably in the form of magnesium alloys, added in the same quantities. Combinations of these (Ca, Mg) may also occur.
In experiments using a 50 ton charge weight for de sulphurizing in a vacuum ladle, the ladle was provided with a basic slag line and the conventional neutral lining otherwise. In all the experiments lime was added in quantities which are set out in the following.
After normal degassing under a vacuum lid (see ASEA Journal mentioned above), g Al/ton was added. In one charge (1) no other desulphurizing agent than lime was added to the melt, whereas in the other experiments (2-5) misch metal was also added in different quantities. The misch metal was added by immersing tins in the bath in three batches (see above), at intervals of about 15 minutes between the batches. The misch metal is thus introduced through the slag without contact therewith, in a portion of the stirring pattern where the melt is moving downwardly. Al is always added before the misch metal in order to keep the oxygen activity low. As mentioned, the quantity of aluminum added first was 100 g/ton and after that 50 g/ton on each occasion.
The following results were obtained for the five charges:
greatest when misch metal was added also (charges 25), but even with only the addition of lime (basic slag) satisfactory desulphurizing was obtained (1).
The following table shows the result of two heats manufactured without vacuum-degassing.
Heat Steel Quality Lime Misch metal Before In No. Tapping mould 6 SIS 1650 0.8 0.2 0.024 0.00l 7 Al Sl H ll 0.8 0.25 0.0l5 0.002
In experiments using about 1 ton charge weight without vacuum treatment, the following results were obtained. During the experiments the lower part of the container was neutrally lined and its upper part basi cai ly lined. During the experiments additions were made as shown below:
A highly basic slag is at the surface of the bath, in experiments 8 up to 1.0% of the charge weight.
The invention can be varied in many ways within the scope of the following claims.
We claim:
1. Method of desulphurizing deo xi di zed melts of steel in charges over 1 ton in a container, which container is provided with a lining which substantially prevents oxygen from leaking in from the lining, and which includes a basic slag line liner at the slag line which comprises adding to the molten steel at least one basic slag-former in the container in order to obtain a high basic molten slag, adding aluminum to the melt and adding misch metal directly into the melt as a desulphurizing agent without substantial contact with the slag and principally at a point of downward movement in the stirring pattern.
2. Method according to claim 1, in which said misch metal is added in a quantity of up to one per cent of the 2 charge weight.
3. Method as claimed in claim 1, in which a vacuum is maintained above the melt during the desulphurizing.
1. METHOD OF DESULPHURIZING DEOXIDIZED MELTS OF STEEL IN CHARGES OVER 1 TON IN A CONTAINER, WHICH CONTAINER IS PROVIDED WITH A LINING WHICH SUBSTANTIALLY PREVENTS OXYGEN FROM LEAKING IN FROM THE LINING, AND WHICH INCLUDES A BASIC SLAG LINE LINER AT THE SLAG LINE WHICH COMPRISES ADDINT TO THE MOLTEN STEEL AT LEAST ONE BASIC SLAT-FORMER IN THE CONTAINER IN ORDER TO OBTAIN A HIGH BASIC MOLTEN SLAG, ADDING ALUMINUM TO THE MELT AND ADDING MISCH METAL DIRECTLY INTO THE MELT AS A DESULPHURIZING AGENT WITHOUT SUBSTANTIAL CONTACT WITH THE SLAG AND PRINCIPALLY AT A POINT OF DOWNWARD MOVEMENT IN THE STIRRING PATTERN.
2. Method according to claim 1, in which said misch metal is added in a quantity of up to one per cent of the charge weight.
3. Method as claimed in claim 1, in which a vacuum is maintained above the melt during the desulphurizing.
|
*Administration of Barack H. Obama, 2010 *
**Proclamation 8541—Captive Nations Week, 2010 **
*July 16, 2010 *
*By the President of the United States of America *
*A Proclamation *
In 1959, President Eisenhower issued the first Captive Nations Proclamation in solidarity with those living without personal or political autonomy behind the Iron Curtain. Since that time, once-captive nations have broken free to establish civil liberties, open markets, and allow their people access to information. However, even as more nations have embraced self-governance and basic human rights, there remain regimes that use violence, threats, and isolation to suppress the aspirations of their people.
The Cold War is over, but its history holds lessons for us today. In the face of cynicism and stifled opportunity, the world saw daring individuals who held fast to the idea that the world can change and walls could come down. Their courageous struggles and ultimate success—and the enduring conviction of all who keep the light of freedom alive—remind us that human destiny will be what we make of it.
The journey towards worldwide freedom and democracy sought in 1959 remains unfinished. Today, we still observe the profound differences between governments that reflect the will of their people, and those that sustain power by force; between nations striving for equal justice and rule of law, and those that deny their citizens freedom of religion, expression, and peaceful assembly; and between states that are open and accountable, and those that restrict the flow of ideas and information. The United States has a special responsibility to bear witness to those whose voices are silenced, and to stand alongside those who yearn to exercise their universal human rights.
In partnership with like-minded governments, we must reinforce multilateral institutions and international partnerships that safeguard human rights and democratic values. We must empower embattled civil societies and help their people connect with one another and the global community through new technologies. And, with faith in the future, we must always stand with the courageous advocates, organizations, and ordinary citizens around the world who fearlessly fight for limitless opportunity and unfettered freedom.
The Congress, by Joint Resolution, approved July 17, 1959 (73 Stat. 212), has authorized and requested the President to issue a proclamation designating the third week of July of each year as "Captive Nations Week."
*Now, Therefore, I, Barack Obama,* President of the United States of America, do hereby proclaim July 18 through July 24, 2010, as Captive Nations Week. I call upon the people of the United States to reaffirm our deep commitment to all those working for human rights and dignity around the globe.
*In Witness Whereof,* I have hereunto set my hand this sixteenth day of July, in the year of our Lord two thousand ten, and of the Independence of the United States of America the two hundred and thirty-fifth.
BARACK OBAMA
[Filed with the Office of the Federal Register, 8:45 a.m., July 20, 2010]
NOTE: This proclamation was published in the *Federal Register* on July 21.
*Categories:* Proclamations : Captive Nations Week.
*Subjects:* Captive Nations Week.
*DCPD Number:* DCPD201000602.
|
package com.ruoyi.framework.jwt.service;
import cn.hutool.crypto.SecureUtil;
import com.auth0.jwt.JWT;
import com.auth0.jwt.JWTCreator;
import com.auth0.jwt.algorithms.Algorithm;
import com.ruoyi.framework.jwt.domain.Account;
import com.ruoyi.utils.AESUtil;
import org.springframework.stereotype.Service;
/**
* @Description $功能描述$
* @Author yufei
* @Date 2019-03-08 10:37
**/
@Service("TokenService")
public class TokenService {
/**
* 获得Token
* @param account
* @return
*/
public String getToken(Account account) {
String token="";
// token= JWT.create().withAudience(account.getId())// 将 id 保存到 token 里面
// .sign(Algorithm.HMAC256(account.getPassword()));// 以 password 作为 token 的密钥
//签名算法
Algorithm algorithm = Algorithm.HMAC256(account.getPassword());
//生成
JWTCreator.Builder builder = JWT.create();
builder.withAudience(AESUtil.Encrypt(account.getId()+ "_" + SecureUtil.simpleUUID(),""));
token = builder.sign(algorithm);
return token;
}
}
|
User blog:Rhonda the stalker fan!/An update on some things...
Vacation
I think that will interfere with The Summer Competition...so I have no idea what that will do...
Summer Competition
So sorry :(
Izzy and Friends
Collabs
Total Drama What The Heck?
This is a bit of me just going on, so if you want to skim, you can.
* More musical sequences will come. Next chapter will have one...
* Someone will have an awkward family reunion while on the show while they are still competing...
* In said adventure, a character met before will reappear...
* A squirrel will get a shotgun...
* Someone will finally admit their true feelings for someone else next chapter...
* The plane will have another crash...
Closing
But, I do want to say I love this wiki and that I feel like you are all really great people :) I really love you guys :P
|
CLI Build Fix
Web Platform Detection
When I try to build a Dart CLI with Flutter Stellar SDK, an error occurs, telling me that we can't use package:flutter/foundation.dart because there's no singleton exist in Dart (something like that, I forgot the exact error).
Because we only use the foundation.dart to access kIsWeb, I created two stub files, stub/non-web.dart and stub/web.dart, just to replace the web platform detection.
With the help of dart.library.html, we are able to detect the web platform without importing foundation.dart.
This is just my own workaround, if you have a better way, it would be better.
Dio Overrides
When I try to run the compiled Dart CLI inside Docker container, the call to Soroban server failed due to badCertificateCallback.
So I add the option for Dio overrides just in case someone need it later.
Hello @hasToDev, thank you for adding this PR.
|
import React from 'react';
import { StyleSheet, ScrollView } from 'react-native';
import { List } from 'react-native-paper';
import { connect } from 'react-redux';
import { listTips } from '../reducer';
class TipsList extends React.Component {
static navigationOptions = ({ navigation }) => {
return {
title: 'Astuces ' + navigation.getParam('otherParam')
};
};
componentDidMount() {
this.props.listTips();
}
constructor(props) {
super(props);
this.state = {};
}
tipsList() {
const { tips } = this.props;
const { navigation } = this.props;
const otherParam = navigation.getParam('otherParam');
return tips.filter((tip) => tip.category == otherParam).map((tip, index) => (
<List.Item
key={index}
right={(props) => <List.Icon {...props} icon="arrow-forward" />}
title={tip.name}
onPress={() =>
this.props.navigation.navigate('SingleTips', {
otherParam: tip.name
})}
/>
));
}
render() {
return (
<ScrollView style={styles.container}>
<List.Section>{this.tipsList()}</List.Section>
</ScrollView>
);
}
}
const styles = StyleSheet.create({
container: {
flex: 1
}
});
const mapStateToProps = (state) => {
let storedRepositories = state.tips.map((tip) => ({ key: tip.id, ...tip }));
return {
tips: storedRepositories
};
};
const mapDispatchToProps = {
listTips
};
export default connect(mapStateToProps, mapDispatchToProps)(TipsList);
// export default withTheme(TipsList);
|
Are you planning your vacation closer to winter or summer months?
Summer
Winter
During your ideal vacation, would you be more likely to spend time exploring a city or relaxing on the beach?
Exploring a city
Relaxing on the beach
When planning your vacation, are you considering a budget to get the most value out of your trip?
Or is money not an object for this trip?
Following strict budget
Money is no object
When you travel do you prefer to be an outsider and explore the lives of native people?
Or would you rather travel with a tourist group, surrounded by people like you?
I like to be the outsider
I prefer to be with people like me
Do you prefer to have fine dining options when you travel?
Or do you just need food to fuel your exploration?
Wine me and dine me!
Just the basics, I need fuel to explore!
Submit
Congratulations! You're going to Puerto Vallarta, Mexico!
Congratulations! You're going to San Francisco, California!
Congratulations! You're going to Paris, France!
sorry, but it's hard to relax on a beach in winter,try again
|
Synagodus, Cope, gen. nov.
The characters of this genus have been pointed out in the ana lytical key. They are evident^ as important as those which define the divisions which are regarded as genera by naturalists. It is not unlikely that the typical species has been heretofore esti mated as a variety of Canis familiaris, but it exhibits two tren chant generic dental charaeters not found in Canis, and three unique specific characters in the teeth, besides two characters of the cranium found in but one or two of the subspecies of Canis familiaris.
The generic characters alluded to are: (1) the absence of the second inferior tubercular molar, and (2) the absence of the in ternal tubercle of the inferior sectorial. The absence of the second inferior tubercular is evidently not one of those abnormal cases which occur in various species of Cam's from time to time; for the first tubercular molar is smaller than in any known species of Canis, and has but one root, a character which some persons might regard as being the third of the generic category. The premolars are 4 4, and of the usual form; the first in both jaws is one-rooted.
It is uncertain whether any species of this genus exists in the wild state. Should such not be the case, we can only predicate the former existence of such an one entirely different from the Canis familiaris, and which has given origin to the existing one below described.
Synagodus mansuetus, sp. nor.
Two crania represent this species in the Museum of the Academy of Natural Sciences. They agree in all essential particulars. The incisor and premolar teeth present no peculiarities (the latter are without marginal lobes), and the superior sectorial is normal. The first tubercular has less transverse extent than in the Canidse generally, and its median crest and inner cingulum are con founded, a character which I have not found in any of the other species accessible. Thus the crown of this tooth consists of an external pair of tubercles, a basin, and a stout inner marginal prominence. The second tuberculars are abnormally small in one
|
Eliminating the subtle whitespace handling difference between DateTimeFormat and Joda's DateTimeFormatter
We have some existing code like this:
DateFormat[] dateFormats = {
new SimpleDateFormat("EEE, d MMM yyyy HH:mm:ss Z", Locale.ENGLISH),
new SimpleDateFormat("d MMM yyyy HH:mm:ss Z", Locale.ENGLISH)
};
For thread safety reasons, I tried to convert it to use Joda Time's formatters, so:
DateTimeFormatter[] dateFormats = {
DateTimeFormat.forPattern("EEE, d MMM yyyy HH:mm:ss Z")
.withLocale(Locale.ENGLISH)
.withOffsetParsed(),
DateTimeFormat.forPattern("d MMM yyyy HH:mm:ss Z")
.withLocale(Locale.ENGLISH)
.withOffsetParsed()
};
However, it surprised me to find that existing test cases broke. In particular (at least the first line which causes the test to fail):
String dateString = "Wed, 1 Feb 2006 21:58:41 +0000";
DateFormat happily matches two or more spaces after the comma but DateTimeFormatter only matches the single space literally.
I could probably put in an additional format which allows for an additional space, but it is sort of awful to have to do that, so is there some way to customise a DateTimeFormatter to be more relaxed about whitespace?
I think it's much easier to process the input string before parsing
str = str.replaceAll(" +", " ");
It is awfully tempting.
I hate to like this answer +1
I think it will be useful for others saying that since Java 8 we can fix above issue by rewriting the pattern:
String pattern = "EEE,[ ][ ]d MMM yyyy HH:mm:ss Z"
This code matches 1 or 2 spaces after comma.
Why not just , [ ]d? That is, one space followed by an optional space.
I like this solution actually. I really have to get us off Joda Time but the migration path isn't entirely clear at the moment. At least for date/time parsing, though, it might be possible to write a wrapper which uses the java.time API but conforms to the Joda Time one.
|
Inline SVG in react 16
I have a SVG file that I want to use as an icon in my react component.
<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 409.6 405.76"><defs><style>.cls-1{fill:none;}.cls-2{clip-path:url(#clip-path);}</style><clipPath id="clip-path" transform="translate(-478 -181.08)"><rect class="cls-1" x="478" y="181" width="409.92" height="406.8"/></clipPath></defs><title>test</title><g class="cls-2"><path class="ofj" d="M682.8,396.06c50.72,0,91.84-48.13,91.84-107.49,0-82.33-41.12-107.49-91.84-107.49S591,206.24,591,288.57c0,59.36,41.12,107.49,91.84,107.49Zm0,0" transform="translate(-478 -181.08)"/><path d="M885.6,554.28,839.27,449.9a23.3,23.3,0,0,0-10.48-11.15l-71.91-37.43a4.66,4.66,0,0,0-4.93.41,113.41,113.41,0,0,1-138.3,0,4.67,4.67,0,0,0-4.94-.41l-71.9,37.43a23.24,23.24,0,0,0-10.47,11.15L480,554.28a23.16,23.16,0,0,0,21.18,32.56H864.42a23.17,23.17,0,0,0,21.18-32.56Zm0,0" transform="translate(-478 -181.08)"/></g></svg>
I want to be able to change the fill color dynamically. I've read that it's best to use SVG 'inline' and I tried to reference it with a <use> but it does not work (it's not showing...)
<svg className="icon-avator">
<use xlinkHref="./assets/avatar.svg" />
</svg>
How can I achieve this?
points to a fragment not an entire file. is for complete files.
React JSX can produce SVG, the same way it does with HTML. Write the SVG as the component's "markup", and use props to control the fill attribute (you can also change the style):
const Icon = ({ fill }) => (
<svg viewBox="0 0 409.6 405.76" fill={ fill }>
<path d="M682.8,396.06c50.72,0,91.84-48.13,91.84-107.49,0-82.33-41.12-107.49-91.84-107.49S591,206.24,591,288.57c0,59.36,41.12,107.49,91.84,107.49Zm0,0" transform="translate(-478 -181.08)"/>
<path d="M885.6,554.28,839.27,449.9a23.3,23.3,0,0,0-10.48-11.15l-71.91-37.43a4.66,4.66,0,0,0-4.93.41,113.41,113.41,0,0,1-138.3,0,4.67,4.67,0,0,0-4.94-.41l-71.9,37.43a23.24,23.24,0,0,0-10.47,11.15L480,554.28a23.16,23.16,0,0,0,21.18,32.56H864.42a23.17,23.17,0,0,0,21.18-32.56Zm0,0" transform="translate(-478 -181.08)"/>
</svg>
);
ReactDOM.render(
<Icon fill="red" />,
demo
);
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/15.1.0/react.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/15.1.0/react-dom.min.js"></script>
<div id="demo"></div>
Cool thanks :) Do you then know what's the best way to make the Icon component dynamic to be able to show different SVG markup? Maybe a trivial question, but my brain is dead right now!!
Each symbol can be a component, and you can have SymbolA, SymbolB, etc.. Now you can wrap them with a generic Icon component that selects the symbol according to a property.
To make it cleaner you could remove the <title> tag, take both <path>s out of <g> and delete it, remove fill from <path>s and set it inside <svg> :)
Instead of hard coding the svg markup, would it be possible to import or otherwise load the markup from a svg file?
@olefrank - you can always load the svg as an image. Another option is to use react-svg-loader - A loader for webpack, rollup, babel that loads svg as a React Component.
For people landing on this page, there is also a webpack loader which generates React components from SVG files. react-svg-loader
If you are using create-react-app, you might want to eject for now. But know this; there are discussions about integrating such a loader in CRA and it's on the 2.0.0 roadmap apparently
There is also a npm package that converts all svg elements to the correct JSX incase anyone else came here and stumbled with a similar problem.
https://www.npmjs.com/package/convert-svg-react
Another option is to not use an external source, so instead of doing
<use href="/path/to/icon.svg" />
create a sprite with symbols (e.g. with https://www.npmjs.com/package/svg-sprite) like that:
<svg ...>
// icon contents here, except `svg` tag became `symbol` tag
<symbol id="icon-id-inside-the-sprite" ...>
// ...
</symbol>
// may be add more icons
</svg>
inline it into your HTML somewhere and hide with display: none style, then use it like
<use href="#icon-id-inside-the-sprite" />
Now you should be able to target its inner classes from your outside CSS.
|
const router = require('express').Router()
const {Task} = require('../db/models')
module.exports = router
router.get('/', async (req, res, next) => {
try {
const tasks = await Task.findAll({})
res.json(tasks)
} catch (err) {
next(err)
}
})
router.get('/:id', async (req, res, next) => {
try {
const taskId = parseInt(req.params.id, 10)
const task = await Task.findOne({
where: {
id: taskId
}
})
res.json(task)
} catch (err) {
next(err)
}
})
|
Torque sensor
ABSTRACT
A torque sensor includes: a strain generation unit with an outer ring-shaped unit, an inner ring-shaped unit that shares a center with the outer ring-shaped unit; and a plurality of spoke units connecting the outer ring-shaped unit with the inner ring-shaped unit; an insulation layer provided on the strain generation body; a first resistor unit and a second resistor unit that are connected in series and that are provided on the insulation layer; and a first output terminal that is connected between the first resistor unit and the second resistor unit, wherein the first resistor unit includes a plurality of first gauge elements connected in series and are arranged in each of the plurality of the spoke units, and the second resistor unit includes a plurality of second gauge elements connected in series and are arranged in each of the plurality of the spoke units.
CROSS-REFERENCE TO RELATED APPLICATIONS
The present application is a continuation application of International Application No. PCT/JP2018/045259 filed on Dec. 10, 2018, which claims priority to Japanese Patent Application No. 2018-029140 filed on Feb. 21, 2018. The contents of these applications are incorporated herein by reference in their entirety.
TECHNICAL FIELD
The present invention relates to a torque sensor.
BACKGROUND ART
In recent years, a torque sensor with a disk-shaped strain generation body and strain gauges (gages) (strain sensors, distortion gauges, or, distortion sensors) is used in a joint part of a robot. In this type of a torque sensor, the strain generation body is arranged perpendicular to a rotation axis, a strain of the strain generation body according to a torque is detected by the strain gauges, and the torque applied to the strain generation body is detected.
PRIOR ART DOCUMENTS Patent Document [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2013-96735 SUMMARY OF THE INVENTION Technical Problem
In a conventional torque sensor, however, there is a problem in that, in a case where a load is applied to the strain generation body from a direction different from a rotational direction, a strain of the strain generation body due to a load is detected by the strain gauges and an error is generated in a detected torque.
The present invention has been made in view of the above problem, and an object of the present invention is to provide a torque sensor that is capable of accurately detecting a torque.
Solution to Problem
A torque sensor according to an embodiment of the present invention includes: a strain generation unit with an outer ring-shaped unit, an inner ring-shaped unit configured to share a center with the outer ring-shaped unit, and a plurality of spoke units connecting the outer ring-shaped unit with the inner ring-shaped unit; an insulation layer provided on the strain generation body, a first resistor unit and a second resistor unit that are connected in series and that are provided on the insulation layer; and a first output terminal that is connected between the first resistor unit and the second resistor unit, wherein the first resistor unit includes a plurality of first gauge elements connected in series and are arranged in each of the plurality of the spoke units, and the second resistor unit includes a plurality of second gauge elements connected in series and are arranged in each of the plurality of the spoke units.
Advantageous Effects of Invention
According to one or more embodiments of the present invention, it is possible to provide a torque sensor that can accurately detect a torque.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a plan view illustrating an example of a torque sensor.
FIG. 2 is an A-A line cross sectional view of the torque sensor illustrated in FIG. 1.
FIG. 3 is a drawing illustrating an example of a circuit structure of a torque sensor.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
In the following, one or more embodiments of the present invention will be described while making reference to the drawings. It should be noted that, in descriptions of the specification and the drawings of an embodiment of the present invention, the same reference numeral is given to an element that has substantially the same functional structure, and duplicated descriptions will be omitted.
A torque sensor 100 according to an embodiment of the present invention will be described by referring to FIGS. 1 to 3. The torque sensor 100 is a disk-shaped sensor that detects a torque. The torque sensor 100 is mounted perpendicular to a rotation axis in a joint part of a robot, etc.
FIG. 1 is a plan view illustrating an example of a torque sensor 100. FIG. 2 is an A-A line cross sectional view of the torque sensor 100 illustrated in FIG. 1. FIG. 3 is a drawing illustrating an example of a circuit structure of the torque sensor 100. In the following, for the sake of convenience, descriptions will be made by assuming up, down, left, and right in the figure as up, down, left, and right of the torque sensor 100, respectively.
The torque sensor 100 includes a strain generation body 1, a insulation layer 2, a first resistor unit R1, a second resistor unit R2, a third resistor unit R3, a fourth resistor unit R4, a first output terminal T1, a second output terminal T2, and a conversion circuit 3.
The strain generation body 1 is a disk-shaped member to which a torque is applied. The torque sensor 100 detects the torque applied to the strain generation body 1 by detecting a strain of the strain generation body 1 using a strain gauge. As illustrated in FIG. 1, the strain generation body 1 includes an outer ring-shaped unit 11, an inner ring-shaped unit 12, and a plurality of spoke units 13.
The outer ring-shaped unit 11 is a ring-shaped part located on the outside of the strain generation body 1. The outer ring-shaped unit 11 includes a plurality of openings 14. The openings 14 is used for fixing the outer ring-shaped unit 11, via a bolt, with a transmission member used for transmission of a drive force from a drive source, or with an operation body to which the drive force is transmitted through the strain generation body 1. In the following, the center of the outer ring-shaped unit 11 is referred to as a center C.
The inner ring-shaped unit 12 is a ring-shaped part located on the inside of the strain generation body 1. The inner ring-shaped unit 12 shares the center C with the outer ring-shaped unit 11 and has an outer diameter that is less than an inner diameter of the outer ring-shaped unit 11. The inner ring-shaped unit 12 includes a plurality of openings 15. The openings 14 is used for fixing the inner ring-shaped unit 12, via a bolt, with a transmission member used for transmission of a drive force from a drive source, or with an operation body to which the drive force is transmitted through the strain generation body 1. The outer ring-shaped unit 11 is fixed with the operation body in the case where the inner ring-shaped unit 12 is fixed with the transmission member, and the outer ring-shaped unit 11 is fixed with the transmission member in the case where the inner ring-shaped unit 12 is fixed with the operation body. Further, the inner ring-shaped unit 12 includes an extension unit 16.
The extension unit 16 is a part that extends from the inner ring-shaped unit 12 towards the outer ring-shaped unit 11. It is possible to easily secure a space for arranging circuit elements including the conversion circuit 3 by providing the extension unit 16. It should be noted that the inner ring-shaped unit 12 includes four extension units 16 that are arranged at the same interval in an example illustrated in FIG. 1. The arrangement and the number of the extension units 16 may be freely designed. Alternatively, the extension units 16 may be provided by extending from the outer ring-shaped unit 11 towards the inner ring-shaped unit 12.
The spoke units 13 are parts that connect the outer ring-shaped unit 11 with the inner ring-shaped unit 12, and a plurality of the spoke units are provided for maintaining the strength of the strain generation body 1. The spoke units 13 are parts with which a torque is transmitted between the outer ring-shaped unit 11 and the inner ring-shaped unit 12, and thus, the parts have a relatively greater strain with respect to the torque in the strain generation body 1. It should be noted that the body 1 includes four spoke units 13 that are arranged at the same interval (per 90 degrees) in an example illustrated in FIG. 1. The number and the arrange of the spoke units 13 are not limited to the above. However, it is preferable that the plurality of the spoke units 13 are arranged at a same interval as illustrated in an example in FIG. 1. According to the above, as described below, it is possible to arrange strain gauges at positions of point symmetry having the center C as a symmetry center.
The insulation layer 2 is an insulation layer provided on the strain generation body 1, and is arranged to cover at least the plurality of spoke units 13. The insulation layer 2 may be an oxide film, a nitride film, or a resin insulation film formed on the strain generation body 1, or may be an insulating printed circuit board fixed onto the strain generation body 1. The printed circuit board may be a flexible circuit board or a rigid circuit board. In either case, the entire surface of the insulation layer 2 is fixed to the strain generation body 1 to get strain in accordance with the strain of the strain generation body 1. Further, the strain generation body 1 may be formed by a printed circuit board. In this case, the strain generation body 1 serves a role of the insulation layer 2. It should be noted that it is preferable that the insulation layer 2 is arranged to cover at least a part of the outer ring-shaped unit 11 and at least a part of the inner ring-shaped unit 12 as illustrated in an example of FIG. 1. According to the above, an area of the insulation layer 2 increases, and thus, it is possible to increase the freedom of circuit design.
Here, a circuit structure formed on the insulation layer 2 will be described by referring to FIG. 3. FIG. 3 is a drawing illustrating an example of a circuit structure of the torque sensor 100. As illustrated in FIG. 3, on the insulation layer 2, a first resistor unit R1, a second resistor unit R2, a third resistor unit R3, a fourth resistor unit R4, a first output terminal T1, a second output terminal T2, and a conversion circuit 3 are provided.
One end of the first resistor unit R1 is connected to a power supply, and the other end of the first resistor unit R1 is connected to the first output terminal T1. One end of the second resistor unit R2 is connected to the first output terminal T1, and the other end of the second resistor unit R2 is connected to the ground. In other words, the first resistor unit R1 and the second resistor unit R2 are connected in series, and form a half bridge circuit. A voltage between the first resistor unit R1 and the second resistor unit R2 (a voltage obtained by dividing a power supply voltage Vdd by the first resistor unit R1 and the second resistor unit R2) is output from the first output terminal T1 as an output voltage V1. The first output terminal T1 is connected to the conversion circuit 3, and the output voltage V1 is input to the conversion circuit 3.
One end of the third resistor unit R3 is connected to the power supply, and the other end of the third resistor unit R3 is connected to the second output terminal T2. One end of the fourth resistor unit R4 is connected to the second output terminal T2, and the other end of the fourth resistor unit R4 is connected to the ground. In other words, the third resistor unit R3 and the fourth resistor unit R4 are connected in series, and form a half bridge circuit. A voltage between the third resistor unit R3 and the fourth resistor unit R4 (a voltage obtained by dividing the power supply voltage Vdd by the third resistor unit R3 and the fourth resistor unit R4) is output from a second output terminal T2 as an output voltage V2. The second output terminal T2 is connected to the conversion circuit 3, and the output voltage V2 is input to the conversion circuit 3.
As is understood from FIG. 3, the third resistor unit R3 and the fourth resistor unit R4 are connected in parallel with the first resistor unit R1 and the second resistor unit R2, and form a bridge circuit together with the first resistor unit R1 and the second resistor unit R2. Each of the first resistor unit R1, the second resistor unit R2, the third resistor unit R3, and the fourth resistor unit R4 includes a plurality of strain gauges. A resistor value of each of the first resistor unit R1, the second resistor unit R2, the third resistor unit R3, and the fourth resistor unit R4 is changed in accordance with a torque applied to the strain generation body 1. Therefore, the output voltage V1 is a voltage in accordance with resistor values of the first resistor unit R1 and the second resistor unit R2 that are changed in accordance with the torque. Similarly, the output voltage V2 is a voltage in accordance with resistor values of the third resistor unit R3 and the fourth resistor unit R4 that are changed in accordance with the torque. In other words, each of the output voltages V1 and V2 is a voltage in accordance with the torque.
The conversion circuit 3 is a circuit that detects a torque based on the output voltages V1 and V2. Specifically, the conversion circuit 3 converts a difference between the output voltages V1 and V2 into a torque by referring to a table prepared in advance. A case is assumed in an example of FIG. 3 in which the conversion circuit 3 is a single IC (Integrated Circuit). However, the conversion circuit 3 may be formed by a plurality of discrete parts. Further, in an example illustrated in FIG. 1, the inner ring-shaped unit 12 includes the extension units 16, and thus, the conversion circuit 3 can be easily arranged in the inner ring-shaped unit 12.
Next, structures of the first resistor unit R1, the second resistor unit R2, the third resistor unit R3, and the fourth resistor unit R4 will be described by referring to FIG. 1.
The first resistor unit R1 includes four first strain gauges r1 that are connected in series by using printed wiring (not shown in the figure). The first strain gauges r1 may be formed by printing a metal material on the insulation layer 2, or may be formed by attaching a metal foil on the insulation layer 2. Further, the first strain gauges r1 may be independent elements implemented in the insulation layer 2. In either case, the entire surface of the first strain gauges r1 is fixed to the strain generation body 1 to get strain in accordance with the strain of the insulation layer 2. According to the above structure, when load is applied to the strain generation body 1, the strain generation body 1 gets strain in accordance with the load, the insulation layer 2 gets strain together with the strain generation body 1, the first strain gauges r1 get strain together with the insulation layer 2, a resistor value of each of the first strain gauges r1 is changed in accordance with the strain, and a resistor value of the first resistor unit R1 is changed in accordance with the change of the resistor value of each of the first strain gauges r1. As a result, the output voltage V1 is changed in accordance with the load.
The plurality of the first strain gauges r1 are arranged in each of the plurality of the spoke units 13. In an example of FIG. 1, a single first strain gauge r1 is arranged in each of the spoke units 13. However, a plurality of first strain gauges r1 may be arranged in each of the spoke units 13. As described above, the spoke units 13 are parts having a relatively greater strain with respect to the torque in the strain generation body 1, and thus, by arranging the first strain gauges r1 in the spoke units 13, it is possible to cause the output voltage V1 to be relatively greatly changed with respect to the torque, and it is possible to accurately detect the torque.
Further, by arranging the first strain gauges r1 in each of the spoke units 13, it is possible to accurately detect the torque even in a case where the load is applied from a direction different from the rotational direction of the strain generation body 1. For example, in a case where a load is applied to the strain generation body 1 in a direction indicated by an arrow B in FIG. 1 (a direction different from the rotational direction), the first strain gauges r1 arranged in the spoke units 13 on the upper side of the strain generation body 1 are extended and the resistor value of the first strain gauges r1 increases, and the first strain gauges r1 arranged in the spoke units 13 on the lower side of the strain generation body 1 are contracted and the resistor value of the first strain gauges r1 decreases. In other words, changes of the resistor values of the first strain gauges r1 caused by the load in a direction indicated by an arrow B are canceled by each other. As a result, an effect to the resistor value of the first resistor unit R1 due to a load in a direction indicated by an arrow B is decreased and an output voltage V1 is output in accordance with the torque in the rotational direction, and thus, it is possible to accurately detect the torque based on the output voltage V1.
Further, it is preferable that the plurality of the first strain gauges r1 are arranged at a same interval. In an example of FIG. 1, four first strain gauges r1 are arranged at every 90 degrees. According to the above, changes of the resistor values of the first strain gauges r1 are uniformly canceled by each other regardless of the applied direction of the load. In order to realize this kind of arrangement of the first strain gauges r1, it is preferable that the spoke units 13 are arranged at a same interval.
Further, it is preferable that the plurality of the first strain gauges r1 are arranged on the same circumference centered on the center C. According to the above, it is possible to cause the effects to the plurality of the first strain gauges r1 due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy.
Further, it is preferable that the plurality of the first strain gauges r1 are arranged at positions of point symmetry having the center C as a symmetry center. In an example of FIG. 1, a first strain gauge r1 in upper left is arranged at a position of point symmetry with a first strain gauge r1 in lower right, and a first strain gauge r1 in upper right is arranged at a position of point symmetry with a first strain gauge r1 in lower left. According to the above, it is possible to cause the effects, to a set of the first strain gauges r1 that are arranged at positions of point symmetry, due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy. In order to realize this kind of arrangement of the first strain gauges r1, it is preferable that the spoke units 13 are arranged at positions of point symmetry having the center C as a symmetry center.
It should be noted that the number of the first strain gauges r1 included in the first resistor unit R1 is not limited to four as long as a plurality of the first strain gauges r1 are included. However, it is preferable that an even number of the first strain gauges r1 are included in the first resistor unit R1 in order to arrange the first strain gauges r1 point-symmetrically.
The second resistor unit R2 includes four second strain gauges r2 that are connected in series by using printed wiring (not shown in the figure). The second strain gauges r2 may be formed by printing a metal material on the insulation layer 2, or may be formed by attaching a metal foil on the insulation layer 2. Further, the second strain gauges r2 may be independent elements implemented in the insulation layer 2. In either case, the entire surface of the second strain gauges r2 is fixed to the strain generation body 1 to get strain in accordance with the strain of the insulation layer 2. According to the above structure, when load is applied to the strain generation body 1, the strain generation body 1 gets strain in accordance with the load, the insulation layer 2 gets strain together with the strain generation body 1, the second strain gauges r2 get strain together with the insulation layer 2, a resistor value of each of the second strain gauges r2 is changed in accordance with the strain, and a resistor value of the second resistor unit R2 is changed in accordance with the change of the resistor value of each of the second strain gauges r2. As a result, the output voltage V1 is changed in accordance with the load.
The plurality of the second strain gauges r2 are arranged in each of the plurality of the spoke units 13. In an example of FIG. 1, a single second strain gauge r2 is arranged in each of the spoke units 13. However, a plurality of second strain gauges r2 may be arranged in each of the spoke units 13. As described above, the spoke units 13 are parts having a relatively greater strain with respect to the torque in the strain generation body 1, and thus, by arranging the second strain gauges r2 in the spoke units 13, it is possible to cause the output voltage V1 to be relatively greatly changed with respect to the torque, and it is possible to accurately detect the torque.
Further, by arranging the second strain gauges r2 in each of the spoke units 13, it is possible to accurately detect the torque even in a case where the load is applied from a direction different from the rotational direction of the strain generation body 1. For example, in a case where a load is applied to the strain generation body 1 in a direction indicated by an arrow B in FIG. 1 (a direction different from the rotational direction), the second strain gauges r2 arranged in the spoke units 13 on the upper side of the strain generation body 1 are extended and the resistor value of the second strain gauges r2 increases, and the second strain gauges r2 arranged in the spoke units 13 on the lower side of the strain generation body 1 are contracted and the resistor value of the second strain gauges r2 decreases. In other words, changes of the resistor values of the second strain gauges r2 caused by the load in a direction indicated by an arrow B are canceled by each other. As a result, an effect to the resistor value of the second resistor unit R2 due to a load in a direction indicated by an arrow B is decreased and an output voltage V1 is output in accordance with the torque in the rotational direction, and thus, it is possible to accurately detect the torque based on the output voltage V1.
Further, it is preferable that the plurality of the second strain gauges r2 are arranged at a same interval. In an example of FIG. 1, four second strain gauges r2 are arranged at every 90 degrees. According to the above, changes of the resistor values of the second strain gauges r2 are uniformly canceled by each other regardless of the applied direction of the load. In order to realize this kind of arrangement of the second strain gauges r2, it is preferable that the spoke units 13 are arranged at a same interval.
Further, it is preferable that the plurality of the second strain gauges r2 are arranged on the same circumference centered on the center C. According to the above, it is possible to cause the effects to the plurality of the second strain gauges r2 due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy.
Further, it is preferable that the plurality of the second strain gauges r2 are arranged at positions of point symmetry having the center C as a symmetry center. In an example of FIG. 1, a second strain gauge r2 in upper left is arranged at a position of point symmetry with a second strain gauge r2 in lower right, and a second strain gauge r2 in upper right is arranged at a position of point symmetry with a second strain gauge r2 in lower left. According to the above, it is possible to cause the effects to a set of the second strain gauges r2 that are arranged at positions of point symmetry due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy. In order to realize this kind of arrangement of the second strain gauges r2, it is preferable that the spoke units 13 are arranged at positions of point symmetry having the center C as a symmetry center.
Further, a second strain gauge r2 is arranged on one side of a rotational direction viewed from a first strain gauge r1 in each of the spoke units 13. In each of the spoke units 13, a second strain gauge r2 is arranged on one side of a rotational direction, and a first strain gauge r1 is arranged on the other side of the rotational direction. According to the above arrangement, when a torque is applied to the strain generation body 1, the resistor value of the first strain gauge r1 changes in a direction opposite to a direction in which the resistor value of the second strain gauge r2 changes. By forming a half bridge circuit using the above-described first resistor unit R1 and the second resistor unit R2, and by outputting a voltage between the first resistor unit R1 and the second resistor unit R2 as the output voltage V1, it is possible to amplify the change of the output voltage V1 in accordance with a torque.
It should be noted that the number of the second strain gauges r2 included in the second resistor unit R2 is not limited to four as long as a plurality of the second strain gauges r2 are included. However, it is preferable that an even number of the second strain gauges r2 are included in the second resistor unit R2 in order to arrange the second strain gauges r2 point-symmetrically.
The third resistor unit R3 includes four third strain gauges r3 that are connected in series by using printed wiring (not shown in the figure). The third strain gauges r3 may be formed by printing a metal material on the insulation layer 2, or may be formed by attaching a metal foil on the insulation layer 2. Further, the third strain gauges r3 may be independent elements implemented in the insulation layer 2. In either case, the entire surface of the third strain gauges r3 is fixed to the strain generation body 1 to get strain in accordance with the strain of the insulation layer 2. According to the above structure, when load is applied to the strain generation body 1, the strain generation body 1 gets strain in accordance with the load, the insulation layer 2 gets strain together with the strain generation body 1, the third strain gauges r3 get strain together with the insulation layer 2, a resistor value of each of the third strain gauges r3 is changed in accordance with the strain, and a resistor value of the third resistor unit R3 is changed in accordance with the change of the resistor value of each of the third strain gauges r3. As a result, the output voltage V2 is changed in accordance with the load.
The plurality of the third strain gauges r3 are arranged in each of the plurality of the spoke units 13. In an example of FIG. 1, a single third strain gauge r3 is arranged in each of the spoke units 13. However, a plurality of third strain gauges r3 may be arranged in each of the spoke units 13. As described above, the spoke units 13 are parts having a relatively greater strain with respect to the torque in the strain generation body 1, and thus, by arranging the third strain gauges r3 in the spoke units 13, it is possible to cause the output voltage V2 to be relatively greatly changed with respect to the torque, and it is possible to accurately detect the torque.
Further, by arranging the third strain gauges r3 in each of the spoke units 13, it is possible to accurately detect the torque even in a case where the load is applied from a direction different from the rotational direction of the strain generation body 1. For example, in a case where a load is applied to the strain generation body 1 in a direction indicated by an arrow B in FIG. 1 (a direction different from the rotational direction), the third strain gauges r2 arranged in the spoke units 13 on the upper side of the strain generation body 1 are extended and the resistor value of the third strain gauges r3 increases, and the third strain gauges r3 arranged in the spoke units 13 on the lower side of the strain generation body 1 are contracted and the resistor value of the third strain gauges r3 decreases. In other words, changes of the resistor values of the third strain gauges r3 caused by the load in a direction indicated by an arrow B are canceled by each other. As a result, an effect to the resistor value of the third resistor unit R3 due to a load in a direction indicated by an arrow B is decreased and an output voltage V2 is output in accordance with the torque in the rotational direction, and thus, it is possible to accurately detect the torque based on the output voltage V2.
Further, it is preferable that the plurality of the third strain gauges r3 are arranged at a same interval. In an example of FIG. 1, four third strain gauges r3 are arranged at every 90 degrees. According to the above, changes of the resistor values of the third strain gauges r3 are uniformly canceled by each other regardless of the applied direction of the load. In order to realize this kind of arrangement of the third strain gauges r3, it is preferable that the spoke units 13 are arranged at a same interval.
Further, it is preferable that the plurality of the third strain gauges r3 are arranged on the same circumference centered on the center C. According to the above, it is possible to cause the effects to the plurality of the third strain gauges r3 due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy.
Further, it is preferable that the plurality of the third strain gauges r3 are arranged at positions of point symmetry having the center C as a symmetry center. In an example of FIG. 1, a third strain gauge r3 in upper left is arranged at a position of point symmetry with a third strain gauge r3 in lower right, and a third strain gauge r3 in upper right is arranged at a position of point symmetry with a third strain gauge r2 in lower left. According to the above, it is possible to cause the effects to a set of the third strain gauges r3 that are arranged at positions of point symmetry due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy. In order to realize this kind of arrangement of the third strain gauges r3, it is preferable that the spoke units 13 are arranged at positions of point symmetry having the center C as a symmetry center.
It should be noted that the number of the third strain gauges r3 included in the third resistor unit R3 is not limited to four as long as a plurality of the third strain gauges r3 are included. However, it is preferable that an even number of the third strain gauges r3 are included in the third resistor unit R3 in order to arrange the third strain gauges r3 point-symmetrically.
The fourth resistor unit R4 includes four fourth strain gauges r4 that are connected in series by using printed wiring (not shown in the figure). The fourth strain gauges r4 may be formed by printing a metal material on the insulation layer 2, or may be formed by attaching a metal foil on the insulation layer 2. Further, the fourth strain gauges r4 may be independent elements implemented in the insulation layer 2. In either case, the entire surface of the fourth strain gauges r4 is fixed to the strain generation body 1 to get strain in accordance with the strain of the insulation layer 2. According to the above structure, when load is applied to the strain generation body 1, the strain generation body 1 gets strain in accordance with the load, the insulation layer 2 gets strain together with the strain generation body 1, the fourth strain gauges r4 get strain together with the insulation layer 2, a resistor value of each of the fourth strain gauges r4 is changed in accordance with the strain, and a resistor value of the fourth resistor unit R4 is changed in accordance with the change of the resistor value of each of the fourth strain gauges r4. As a result, the output voltage V2 is changed in accordance with the load.
The plurality of the fourth strain gauges r4 are arranged in each of the plurality of the spoke units 13. In an example of FIG. 1, a single fourth strain gauge r4 is arranged in each of the spoke units 13. However, a plurality of fourth strain gauges r4 may be arranged in each of the spoke units 13. As described above, the spoke units 13 are parts having a relatively greater strain with respect to the torque in the strain generation body 1, and thus, by arranging the fourth strain gauges r4 in the spoke units 13, it is possible to cause the output voltage V2 to be relatively greatly changed with respect to the torque, and it is possible to accurately detect the torque.
Further, by arranging the fourth strain gauges r4 in each of the spoke units 13, it is possible to accurately detect the torque even in a case where the load is applied from a direction different from the rotational direction of the strain generation body 1. For example, in a case where a load is applied to the strain generation body 1 in a direction indicated by an arrow B in FIG. 1 (a direction different from the rotational direction), the fourth strain gauges r4 arranged in the spoke units 13 on the upper side of the strain generation body 1 are extended and the resistor value of the fourth strain gauges r4 increases, and the fourth strain gauges r4 arranged in the spoke units 13 on the lower side of the strain generation body 1 are contracted and the resistor value of the fourth strain gauges r4 decreases. In other words, changes of the resistor values of the fourth strain gauges r4 caused by the load in a direction indicated by an arrow B are canceled by each other. As a result, an effect to the resistor value of the fourth resistor unit R4 due to a load in a direction indicated by an arrow B is decreased and an output voltage V2 is output in accordance with the torque in the rotational direction, and thus, it is possible to accurately detect the torque based on the output voltage V2.
Further, it is preferable that the plurality of the fourth strain gauges r4 are arranged at a same interval. In an example of FIG. 1, four fourth strain gauges r4 are arranged at every 90 degrees. According to the above, changes of the resistor values of the fourth strain gauges r4 are uniformly canceled by each other regardless of the applied direction of the load. In order to realize this kind of arrangement of the fourth strain gauges r4, it is preferable that the spoke units 13 are arranged at a same interval.
Further, it is preferable that the plurality of the fourth strain gauges r4 are arranged on the same circumference centered on the center C. According to the above, it is possible to cause the effects to the plurality of the fourth strain gauges r4 due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy.
Further, it is preferable that the plurality of the fourth strain gauges r4 are arranged at positions of point symmetry having the center C as a symmetry center. In an example of FIG. 1, a fourth strain gauge r4 in upper left is arranged at a position of point symmetry with a fourth strain gauge r4 in lower right, and a fourth strain gauge r4 in upper right is arranged at a position of point symmetry with a fourth strain gauge r4 in lower left. According to the above, it is possible to cause the effects to a set of the fourth strain gauges r4 that are arranged at positions of point symmetry due to a load from a direction different from the rotational direction to be uniform, and it is possible to increase the cancellation accuracy. In order to realize this kind of arrangement of the fourth strain gauges r4, it is preferable that the spoke units 13 are arranged at positions of point symmetry having the center C as a symmetry center.
Further, a fourth strain gauge r4 is arranged on one side of a rotational direction viewed from a third strain gauge r3 in each of the spoke units 13. In each of the spoke units 13, a fourth strain gauge r4 is arranged on one side of a rotational direction, and a third strain gauge r3 is arranged on the other side of the rotational direction. According to the above arrangement, when a torque is applied to the strain generation body 1, the resistor value of the third strain gauges r3 changes in a direction opposite to a direction in which the resistor value of the fourth strain gauges r4 changes. By forming a half bridge circuit using the above-described third resistor unit R3 and the fourth resistor unit R4, and by outputting a voltage between the third resistor unit R3 and the fourth resistor unit R4 as the output voltage V2, it is possible to amplify the change of the output voltage V2 in accordance with a torque.
It should be noted that the number of the fourth strain gauges r4 included in the fourth resistor unit R4 is not limited to four as long as a plurality of the fourth strain gauges r4 are included. However, it is preferable that an even number of the fourth strain gauges r4 are included in the fourth resistor unit R4 in order to arrange the fourth strain gauges r4 point-symmetrically.
As described above, according to an embodiment of the present invention, the first strain gauges r1 are arranged in a plurality of spoke units 13, and thus, even in a case where load is applied to the strain generation body 1 from a direction different from a rotational direction, effects of the load are canceled among the plurality of the first strain gauges r1, and an error of the resistor value of the first resistor unit R1 generated by the load is reduced. The above reduction of an error of the resistor value of the first resistor unit R1 applies to the second resistor unit R2, the third resistor unit R3, and the fourth resistor unit R4 in the same way. Therefore, according to an embodiment of the present invention, it is possible to accurately output output voltages V1 and V2 in accordance with a torque, and to accurately detect the torque based on the output voltages V1 and V2 even in a case where load is applied to the strain generation body 1 from a direction different from the rotational direction of the strain generation body 1.
It should be noted that, in an embodiment of the present invention, it is possible that the third resistor unit R3 and the fourth resistor unit R4 are not included. Even in a case where the third resistor unit R3 and the fourth resistor unit R4 are not included, it is possible for the torque sensor 100 to accurately detect a torque based on the output voltage V1.
Further, it is not necessary for the shape of the outer ring-shaped unit 11 and the shape of the inner ring-shaped unit 12 to be a complete ring. A part of the ring may be omitted. In other words, it is only necessary for the outer ring-shaped unit 11 and the inner ring-shaped unit 12 to be connected via the spoke units 13 to form a single strain generation body 1.
Further, the present invention is not limited to embodiments described above, and may be combined with other elements. Various modifications may be possible without departing from the spirit of the present invention.
DESCRIPTION OF THE REFERENCE NUMERALS
- 1: strain generation body - 2: insulation layer - 3: conversion circuit - 11: outer ring-shaped unit - 12: inner ring-shaped unit - 13: spoke unit - 14: opening - 15: opening - 16: extension unit - 100: torque sensor - R1: first resistor unit - R2: second resistor unit - R3: third resistor unit - R4: fourth resistor unit - r1: first gauge element - r2: second gauge element - r3: third gauge element - r4: fourth gauge element
1. A torque sensor comprising: a strain generation body including an outer ring-shaped unit, an inner ring-shaped unit that shares a center with the outer ring-shaped unit, and a plurality of spoke units that connect the outer ring-shaped unit with the inner ring-shaped unit; an insulation layer provided on the strain generation body; a first resistor unit and a second resistor unit that are connected in series and that are provided on the insulation layer; and a first output terminal that is connected between the first resistor unit and the second resistor unit, wherein the first resistor unit includes a plurality of first gauge elements that are connected in series and that are provided in each of the plurality of the spoke units, and the second resistor unit includes a plurality of second gauge elements that are connected in series and that are provided in each of the plurality of the spoke units.
2. The torque sensor according to claim 1, wherein at least one of the plurality of the spoke units, the plurality of the first gauge elements, and the plurality of the second gauge elements is arranged at a same interval.
3. The torque sensor according to claim 1, wherein at least one of the plurality of the spoke units, the plurality of the first gauge elements, and the plurality of the second gauge elements is arranged at positions of point symmetry having the center as a symmetry center.
4. The torque sensor according to claim 1, the torque sensor further comprising: a third resistor unit and a fourth resistor unit that are connected in series and that are provided on the insulation layer; and a second output terminal that is connected between the third resistor unit and the fourth resistor unit, wherein the third resistor unit includes a plurality of third gauge elements that are connected in series and that are provided in each of the plurality of the spoke units, and the fourth resistor unit includes a plurality of fourth gauge elements that are connected in series and that are provided in each of the plurality of the spoke units.
5. The torque sensor according to claim 4, wherein at least one of the plurality of the spoke units, the plurality of the third gauge elements, and the plurality of the fourth gauge elements is arranged at a same interval.
6. The torque sensor according to claim 4, wherein at least one of the plurality of the spoke units, the plurality of the third gauge elements, and the plurality of the fourth gauge elements is arranged at positions of point symmetry having the center as a symmetry center.
7. The torque sensor according to claim 1, wherein the strain generation body includes an extension unit that extends from the outer ring-shaped unit toward the inner ring-shaped unit, or that extends from the inner ring-shaped unit toward the outer ring-shaped unit.
|
Violet L. PALIK, Plaintiff, v. F. David MATHEWS, Secretary of the Department of Health, Education and Welfare of the United States of America, Defendant.
Civ. No. 76-0-2.
United States District Court, D. Nebraska.
Nov. 19, 1976.
Vard R. Johnson, Omaha, Neb., for plaintiff.
Daniel E. Wherry, U. S. Atty., D. Neb., G. Roderic Anderson, Asst. U. S. Atty., D. Neb., Omaha, Neb., for defendant.
MEMORANDUM
DENNEY, District Judge.
Plaintiff instituted this action on January 6,1976, under § 205(g) of the Social Security Act (hereinafter referred to as the Act), 42 U.S.C. § 405(g), to review a final decision of the Secretary of the Department of Health, Education and Welfare which denied her claim for disability insurance benefits under the Act. Currently, pending before the Court are cross-motions for summary judgment pursuant to Rule 56, Fed.R. Civ.P.
I.
Plaintiff, Violet L. Palik, filed her application on October 11, 1972, to establish a period of disability and to obtain disability insurance benefits. Plaintiff’s application states that she was born September 6, 1920, and became unable to work in 1968 at the age of 48, because of bronchitis, asthma, and multiple allergies. On November 1, 1972, plaintiff changed the alleged date of onset to 1960.
Upon the denial of plaintiff’s claim by the Social Security Administration, plaintiff requested a hearing. A hearing was then conducted on March 14, 1975, wherein plaintiff was represented by counsel. The administrative law judge found that plaintiff was not under a “disability” as defined in the Social Security Act any time when she met the “earnings” requirement of law. The Appeals Council of the Social Security Administration affirmed the administrative law judge’s decision of November 7, 1975.
For insured status under the Act, 42 U.S.C. §§ 416(i)(3)(B) and 423(e)(1)(B), an individual is required to have 20 quarters of coverage in the 40-quarter period ending with the first quarter of disability. It is undisputed that Mrs. Palik last met this earnings requirement on June 30, 1964. Therefore, unlike most social security cases, the question here is not whether Mrs. Palik is currently disabled — the administrative law judge found that she was — but whether she was disabled some eight years prior to her application.
II.
Mrs. Palik has an eighth grade education. Between the years of 1952 and 1968, she intermittently held a number of jobs including seamstress, factory worker and general clerical employment.
Plaintiff’s early medical records indicate that she was hospitalized from April, 1946, to May, 1948, for tuberculosis. Mrs. Palik testified that from the time of her release from the sanitarium until the present, she has suffered progressively worse asthma attacks at intervals of once or twice a year. She further stated that in May or June of 1960 she suffered an asthma attack which resulted in her hospitalization. At the time of this attack, plaintiff was employed at Western Electric, Inc., filing burrs off of manufactured parts and supplies. According to her testimony, her physician advised her to quit her job at Western Electric because of the dust in the air. Plaintiff left Western Electric and did not seek employment again until 1965.
Mrs. Palik testified that in the 1960’s she had at least one or two asthma attacks while cleaning house, which lasted approximately two weeks.
Plaintiff testified that she attempted to return to work in 1964 at the behest of threats and beatings from her alcoholic husband. From 1965 until 1968, Mrs. Palik made seven attempts to find and keep a job. The jobs would typically last two or three weeks until Mrs. Palik would be forced to quit because of asthma attacks which generally resulted in her hospitalization.
In 1965, plaintiff earned only $130.52 and in 1966 she earned only $153.16. In 1967, she worked three or four months, and held three different jobs in 1968. She earned $1,084.00 in 1967 and $984.00 in 1968.
In addition to plaintiff’s testimony, the administrative record consists of medical records and evaluations. The record contains reports of 20 hospitalizations for Mrs. Palik from 1961 to 1972.
Dr. Donald Nilsson treated plaintiff from June 18, 1962, to September 15, 1966. He found her to be suffering from acute asthma, mild wheezing and increasing exertional dyspnea (shortness of breath). Dr. Nilsson found her to be allergic to a number of everyday items including dust, feathers, dog and cattle hair, and a number of molds and plants.
On October 27, 1964, plaintiff was hospitalized for epigastric pain. Final diagnoses of Dr. D. N. Mergens on November 11, 1964, were hypochlorhydria (insufficient production of hydrochloric acid in digestive system), trichomonas, bacterial vaginitis and endogenous depression. Plaintiff’s medical records during this period indicate she suffered from psychoneurosis.
Plaintiff was hospitalized following an attempted suicide in July, 1965, manifested by an overdosage of meprobamate and aspirin. In a hospital report on Mrs. Palik showing an admission date of September 14, 1965, when she had surgery for removal of a foreign body from the cecum and an appendectomy, Dr. Mergens noted under comments that “prognosis guarded in chronic psychoneurotic.” [Tr. 149].
During a 27 day period of hospitalization in 1969, Dr. Mergens, in consultation with three other physicians, had occasion to observe the patient closely and extensively. His final diagnosis was “psychoneurosis severe” and “cystourethrocele.” [Tr. 239]. Only three days later, the patient was again hospitalized by Dr. Mergens for eleven days with numerous complaints. His hospital report states:
This patient has a most severe and disabling psychoneurosis with depressive symptoms, anxiety features and will not except (sic) any psychiatric diagnosis or help. She will probably tend to continue to be admitted to the hospital because of various complaints. [Tr. 261],
On September 20, 1972, Dr. Robert Murray hospitalized the plaintiff for asthma. His final diagnosis was “bronchial asthma, diabetes millitis, hypothyroidism, and psychoneurosis.” [Tr. 185]. His synopsis at this time noted:
Patient is rehospitalized at this time for recurrent bronchial asthma precipitated primarily by extreme emotional stress due to marital problems at home. Extensive pulmonary evaluation was done by Dr. Lim with considerable improvement in the patient’s status while she was in the hospital. Emotional agitation, however, has been directly observed to reproduce attacks . . . . The patient was dismissed in a much improved condition. However, emotional stress may very well precipitate another attack. [Tr. 185].
III.
Disability is defined by 42 U.S.C. § 423(d)(1)(A) as the “inability to engage in any substantial gainful activity by reason of any medically determinable physical or mental impairment which can be expected to result in death or . . .to last for a continuous period of not less than twelve months.” An individual is disabled only if his impairments prevent his performing not only his previous work, but considering his age, education and experience, preclude “any other kind of substantial gainful work which exists in the national economy . . . .” 42 U.S.C. § 423(d)(2)(A). The findings of the Secretary are to be sustained if supported by substantial evidence in the record as a whole. Russell v. Secretary of Health, Education and Welfare, 540 F.2d 353, 356 (8th Cir. 1976), citing Celebrezze v. Bolas, 316 F.2d 498, 500-01, 507 (8th Cir. 1963). See also Brinker v. Weinberger, 522 F.2d 13, 16 (8th Cir. 1975); Klug v. Weinberger, 514 F.2d 423, 424 (8th Cir. 1975); Yawitz v. Weinberger, 498 F.2d 956, 959-60 (8th Cir. 1974); Garrett v. Richardson, 471 F.2d 598, 599-600 (8th Cir. 1972).
The issue in this case is not whether there is substantial evidence to support the Secretary’s decision to deny disability benefits to plaintiff, but whether the Hearing Examiner applied the regulations of the Secretary properly, whether he considered all the relevant evidence and whether he accorded proper weight to the claimant’s testimony.
Although Mrs. Palik described her impairment or illnesses in her application for disability insurance benefits as bronchitis, asthma, and allergies [Tr. 83], plaintiff’s counsel made specific reference in his opening statement before the administrative law judge that she was also claiming psychiatric disorders. [Tr. 49]. Even in federal court, we allow plaintiffs to amend complaints to conform to the evidence. Rule 15(a), Fed.R. Civ.P. Nevertheless, the administrative law judge considered asthma and pulmonary problems as Mrs. Palik’s primary impairment and made no findings as to plaintiff’s psychiatric impairments, despite the evidence in the record. Standing alone, or in conjunction with physical impairment, psychiatric disorders can qualify individuals for disability benefits. Murphy v. Gardner, 379 F.2d 1 (8th Cir. 1967); Marion v. Gardner, 359 F.2d 175 (8th Cir. 1966). Furthermore, in assessing disability, the Secretary must consider all complaints together. Gold v. Secretary of Health, Education and Welfare, 463 F.2d 38 (2nd Cir. 1972). The failure of the administrative law judge to make a finding upon plaintiff’s psychiatric disorder, together with her application for disability benefits which failed to state neurosis, leaves the reviewing court with the unavoidable inference that the administrative law judge failed to consider all of plaintiff’s complaints.
Plaintiff testified at length at the hearing. This Court held in Baldridge v. Weinberger, 383 F.Supp. 1241 (D.Neb.1974) that “[t]he hearing examiner may not disregard such subjective evidence because the pain, which is real to the claimant, may provide the basis for a disability even though the subjective symptoms are unsupported by objective medical evidence.” Id. at 1243. Nonetheless, the administrative law judge appears to have disregarded plaintiff’s subjective testimony as immaterial. The administrative law judge held as follows:
She then states she could not work regularly from 1960 until 1967 because of the asthma condition, returning to work because her husband (under the influence of alcohol) intimidated her and in effect forced her to return to work. Before discussing the credibility of this testimony, it is largely immaterial when evaluated by Social Security standards. The medical records during this period of time generally confirm the continuation of the chronic asthma, noting about the same number of acute episodes. [Tr. 33].
Mental “impairment may be medically determinable but, in few cases, could a conclusion of such impairment be supported by objective clinical findings.” Ross v. Gardner, 365 F.2d 554, 558 (6th Cir. 1966) (citation omitted). Plaintiffs testimony must be considered along with her medical history.
Finally, the administrative law judge placed great reliance on plaintiff’s 1967-68 work record. Pursuant to the authority granted him in Section 423(d)(4), the Secretary promulgated a Regulation for the evaluation of earnings from work. 20 C.F.R. § 404.1534(b) provides as follows:
An individual’s earnings from work activities averaging in excess of $140 a month shall be deemed to demonstrate his ability to engage in substantial gainful activity unless there is affirmative evidence that such work activities themselves establish that the individual does not have the ability to engage in substantial gainful activity under the criteria in §§ 404.-1532 and 404.1533 and paragraph (a) of this section.
Plaintiff contends that the administrative law judge failed to consider the evidence that her work activities themselves establish her inability to engage in substantial gainful employment. Plaintiff’s work records indicate that she worked at Indian Hills Inn 4-7 hours per day, 5 days per week from September, 1967, to July, 1968, and earned $1,084.09. The question which the Examiner failed to develop was whether Mrs. Palik’s short work days were the result of her inability to work. Mrs. Palik’s case “cannot be decided simply on the basis of [her] earnings, for her employment history is extraordinary.” Wilson v. Richardson, 455 F.2d 304 (4th Cir. 1972). From 1967 to 1968, she worked at five different jobs. “A social security judge acts as an examiner charged with developing the facts, Richardson v. Perales, 402 U.S. 389, 410, 91 S.Ct. 1420, 28 L.Ed.2d 842 (1971), and is under an affirmative duty to inquire into all the matters at issue. 20 C.F.R. § 404.927.” Coulter v. Weinberger, 527 F.2d 224, 229 (3rd Cir. 1975). There are exceptions to the amount of earnings test. For example, Section 404.1534(a) provides that:
Where an individual is forced to discontinue his work activities after a short time because his impairment precludes continuing such activities, his earnings would not demonstrate ability to engage in substantial gainful activity.
It is possible that Mrs. Palik’s sporadic activities may demonstrate not her ability but her inability to engage in substantial gainful activity.
The Court is thus confronted with several grave errors of law
which form the basis of the Hearing Examiner’s decision, and which constitute reversible error. The rule governing these cases has been clearly set forth in Ferran v. Flemming, 293 F.2d 568, 571 (C.A. 5), where the court stated:
“Our review is ordinarily, of course, limited to determining merely whether there is substantial evidence to support the administrative findings. But here, just as in the ‘clearly erroneous’ review of a judge’s findings, when the factfinder has failed to employ the proper legal standard in making its determination the finding may not stand. Mitchell v. Mitchell Truck Lines, 5 Cir., 1961, 286 F.2d 721; Henderson and Poole v. Flemming, 5 Cir., 1960, 283 F.2d 882; United States v. Williamson, 5 Cir., 1958, 255 F.2d 512; Mitchell v. Raines, 5 Cir., 1956, 238 F.2d 186. The facts must be evaluated by the administrator in the light or correct legal standards to entitle the administrative findings to the insulation of the substantial evidence test.” (Emphasis in text).
Branham v. Gardner, 383 F.2d 614, 626-627 (6th Cir. 1967).
As the facts have not yet been tested under the proper standards, the Court does not express any opinion on the ultimate decision to be reached. Despite the procedural safeguards a claimant enjoys and despite the attention the Department of Health, Education and Welfare devotes to social security claims, errors do occur and it is the function of judicial review to correct such errors. The administrative law judge’s failure to apply the relevant standards for determination of disability in the unusual circumstances in this case mandates reconsideration.
Accordingly, the case is remanded to the Secretary for further proceedings consistent with this opinion.
. 42 U.S.C. §§ 416(i), 423.
|
//! This is the popover for the dashboard
import React, { useRef, useState } from 'react'
import { Icon } from '@iconify/react'
import homeFill from '@iconify/icons-eva/home-fill'
import personFill from '@iconify/icons-eva/person-fill'
import settings2Fill from '@iconify/icons-eva/settings-2-fill'
// next
// import NextLink from 'next/link'
import { Link as GatsbyLink } from 'gatsby'
// material
import { alpha } from '@mui/material/styles'
import {
Box,
Avatar,
Button,
Divider,
MenuItem,
Typography,
} from '@mui/material'
import avatar_default from '../../static/mock-images/avatars/avatar_default.jpg'
// components
import MenuPopover from '../../components/MenuPopover'
import { MIconButton } from '../../components/@material-extend'
// ----------------------------------------------------------------------
const MENU_OPTIONS = [
{ label: 'Home', icon: homeFill, linkTo: '/dashboard/home' },
{ label: 'Profile', icon: personFill, linkTo: '/dashboard/account' },
{ label: 'Settings', icon: settings2Fill, linkTo: '/dashboard/cart' },
]
// ----------------------------------------------------------------------
export default function AccountPopover() {
const anchorRef = useRef(null)
const [open, setOpen] = useState(false)
const handleOpen = () => {
setOpen(true)
}
const handleClose = () => {
setOpen(false)
}
return (
<>
<MIconButton
ref={anchorRef}
onClick={handleOpen}
sx={{
padding: 0,
width: 44,
height: 44,
...(open && {
'&:before': {
zIndex: 1,
content: "''",
width: '100%',
height: '100%',
borderRadius: '50%',
position: 'absolute',
bgcolor: theme => alpha(theme.palette.grey[900], 0.72),
},
}),
}}
>
<Avatar alt="My Avatar" src={avatar_default} />
</MIconButton>
<MenuPopover
open={open}
onClose={handleClose}
anchorEl={anchorRef.current}
sx={{ width: 220 }}
>
<Box sx={{ my: 1.5, px: 2.5 }}>
<Typography variant="subtitle1" noWrap>
Guest User
</Typography>
{/* <Typography variant="body2" sx={{ color: 'text.secondary' }} noWrap>
email
</Typography> */}
</Box>
<Divider sx={{ my: 1 }} />
{MENU_OPTIONS.map(option => (
<GatsbyLink
// style={{ color: 'black' }}
style={{ textDecoration: 'none' }}
key={option.label}
to={option.linkTo}
>
<MenuItem
onClick={handleClose}
// sx={{ typography: 'body2', py: 1, px: 2.5 }}
sx={{
// color: theme => alpha(theme.primary.grey[900], 0.72),
color: theme => theme.palette.primary.main,
typography: 'body2',
py: 1,
px: 2.5,
}}
>
<Box
component={Icon}
icon={option.icon}
sx={{
mr: 2,
width: 24,
height: 24,
}}
/>
{option.label}
</MenuItem>
</GatsbyLink>
))}
<Box sx={{ p: 2, pt: 1.5 }}>
<Button fullWidth color="inherit" variant="outlined">
Logout
</Button>
</Box>
</MenuPopover>
</>
)
}
|
[Federal Register Volume 84, Number 237 (Tuesday, December 10, 2019)]
[Page 67487]
[FR Doc No: 2019-26514]
=======================================================================
-----------------------------------------------------------------------
POSTAL REGULATORY COMMISSION
[Docket Nos. MC2020-45 and CP2020-43; MC2020-46 and CP2020-44]
New Postal Products
AGENCY: Postal Regulatory Commission.
ACTION: Notice.
-----------------------------------------------------------------------
SUMMARY: The Commission is noticing a recent Postal Service filing for
the Commission's consideration concerning a negotiated service
agreement. This notice informs the public of the filing, invites public
comment, and takes other administrative steps.
DATES: Comments are due: December 12, 2019.
ADDRESSES: Submit comments electronically via the Commission's Filing
Online system at http://www.prc.gov. Those who cannot submit comments
electronically should contact the person identified in the FOR FURTHER
INFORMATION CONTACT section by telephone for advice on filing
alternatives.
FOR FURTHER INFORMATION CONTACT: David A. Trissell, General Counsel, at
202-789-6820.
SUPPLEMENTARY INFORMATION:
Table of Contents
I. Introduction
II. Docketed Proceeding(s)
I. Introduction
The Commission gives notice that the Postal Service filed
request(s) for the Commission to consider matters related to negotiated
service agreement(s). The request(s) may propose the addition or
removal of a negotiated service agreement from the market dominant or
the competitive product list, or the modification of an existing
product currently appearing on the market dominant or the competitive
product list.
Section II identifies the docket number(s) associated with each
Postal Service request, the title of each Postal Service request, the
request's acceptance date, and the authority cited by the Postal
Service for each request. For each request, the Commission appoints an
officer of the Commission to represent the interests of the general
public in the proceeding, pursuant to 39 U.S.C. 505 (Public
Representative). Section II also establishes comment deadline(s)
pertaining to each request.
The public portions of the Postal Service's request(s) can be
accessed via the Commission's website (http://www.prc.gov). Non-public
portions of the Postal Service's request(s), if any, can be accessed
through compliance with the requirements of 39 CFR 3007.301.\1\
---------------------------------------------------------------------------
\1\ See Docket No. RM2018-3, Order Adopting Final Rules Relating
to Non-Public Information, June 27, 2018, Attachment A at 19-22
(Order No. 4679).
---------------------------------------------------------------------------
The Commission invites comments on whether the Postal Service's
request(s) in the captioned docket(s) are consistent with the policies
of title 39. For request(s) that the Postal Service states concern
market dominant product(s), applicable statutory and regulatory
requirements include 39 U.S.C. 3622, 39 U.S.C. 3642, 39 CFR part 3010,
and 39 CFR part 3020, subpart B. For request(s) that the Postal Service
states concern competitive product(s), applicable statutory and
regulatory requirements include 39 U.S.C. 3632, 39 U.S.C. 3633, 39
U.S.C. 3642, 39 CFR part 3015, and 39 CFR part 3020, subpart B. Comment
deadline(s) for each request appear in section II.
II. Docketed Proceeding(s)
1. Docket No(s).: MC2020-45 and CP2020-43; Filing Title: USPS
Request to Add Priority Mail Contract 568 to Competitive Product List
and Notice of Filing Materials Under Seal; Filing Acceptance Date:
December 4, 2019; Filing Authority: 39 U.S.C. 3642, 39 CFR 3020.30 et
seq., and 39 CFR 3015.5; Public Representative: Christopher C. Mohr;
Comments Due: December 12, 2019.
2. Docket No(s).: MC2020-46 and CP2020-44; Filing Title: USPS
Request to Add Priority Mail Contract 569 to Competitive Product List
and Notice of Filing Materials Under Seal; Filing Acceptance Date:
December 4, 2019; Filing Authority: 39 U.S.C. 3642, 39 CFR 3020.30 et
seq., and 39 CFR 3015.5; Public Representative: Christopher C. Mohr;
Comments Due: December 12, 2019.
This Notice will be published in the Federal Register.
Darcie S. Tokioka,
Acting Secretary.
[FR Doc. 2019-26514 Filed 12-9-19; 8:45 am]
BILLING CODE 7710-FW-P
|
/**
* Utilitarian types
*/
export type Unpacked<T> = T extends Promise<infer U2> ? U2 : T;
|
[v2] Improve log output
A clear and concise description of what you want to happen.
Use-Case
When we have several scale object, it is very hard to identify the which is which. This is an example with Azure Storage Queue and RabbitMQ on the same keda.
Specification
Probably, we can add scaleObject name or scaler name might help.
Fixed by #1019
|
Talk:Rebecca Coleman Curtis
Trimmed
I did some cleaning so that the article did not read a like a résumé. -- KathrynLybarger (talk) 02:47, 13 June 2009 (UTC)
|
'use strict'
const button_tra = document.getElementById("button_tra");
const src_lang = document.getElementById("src_lang");
const target_lang = document.getElementById("target_lang");
const user_text = document.getElementById("user_text");
const donelist = document.getElementById("donelist");
const mylog = message => {
const e = document.createElement("li");
e.appendChild(document.createTextNode(message));
donelist.insertBefore(e, donelist.firstChild);
};
setOption(src_lang, langs);
setOption(target_lang, langs);
async function translate() {
const alert_msg = validateInput()
if (alert_msg) {
alert(alert_msg)
return -1;
}
fetch('https://sandbox-mt.mimi.fd.ai/machine_translation', {
method: 'POST',
headers: {
'Authorization': 'Bearer ' + access_token.value
},
body: new URLSearchParams({
text: user_text.value,
source_lang: src_lang.value,
target_lang: target_lang.value
}),
}).then(response => {
if (!response.ok) {
throw new Error();
}
return response.json()
}).then(translation => {
mylog(translation[0])
}).catch((error) => {
mylog(error)
})
}
function preventSetSameLangs() {
if (this.src_or_dst == 'src') {
let lang = getCurrentLang(src_lang)
if (isForeignLang(lang)) {
target_lang.selectedIndex = 1; // 1 == 'ja'
}
else {
target_lang.selectedIndex = 2; // 2 == 'en'
}
}
else if (this.src_or_dst == 'dst') {
let lang = getCurrentLang(target_lang)
if (isForeignLang(lang)) {
src_lang.selectedIndex = 1; // 1 == 'ja'
}
else {
src_lang.selectedIndex = 2; // 2 == 'en'
}
}
}
function getCurrentLang(langObj) {
let langNum = langObj.selectedIndex;
let lang = langObj.options[langNum].value;
return lang;
}
function isForeignLang(lang) {
return (lang != 'ja' ? true : false)
}
function validateInput(event) {
let alert_msg = '';
if (src_lang.selectedIndex === 0 || target_lang.selectedIndex === 0) {
alert_msg += '言語を選択してください。\n';
}
if (user_text.value === '') {
alert_msg += '文章を入力してください。';
}
return alert_msg
}
src_lang.addEventListener('change', { src_or_dst: 'src', handleEvent: preventSetSameLangs });
target_lang.addEventListener('change', { src_or_dst: 'dst', handleEvent: preventSetSameLangs });
button_tra.addEventListener('click', translate);
|
Using gts instead of eslint
I've been having some issues with eslint's configuration as it is configured as part of the gts module. Is there a specific reason for using gts instead of eslint, prettier, etc just like in the core repo?
As far as I remember gts was the tool of choice in the early OTel days. it was removed in core repo because of some dependency issues. There were other build setup changes done in core repo that time like using a single typescript project.
The idea was to do the same in contrib as followup but noone found the time to do this.
As far as I remember gts was the tool of choice in the early OTel days. it was removed in core repo because of some dependency issues. There were other build setup changes done in core repo that time like using a single typescript project.
The idea was to do the same in contrib as followup but noone found the time to do this.
I can create a PR for this. Is there anything else that should be done that was also changed in the core repo?
Can't remember in detail. I guess the only way is to compare the repos. Maybe browser tooling like webpack differ also. Maybe also typescript, lerna,...
But there is no need to create a single PR to cover everything. Usually such repo wide changes tend to be complicated/cumbersome even if you touch just a part.
Can't remember in detail. I guess the only way is to compare the repos. Maybe browser tooling like webpack differ also. Maybe also typescript, lerna,...
But there is no need to create a single PR to cover everything. Usually such repo wide changes tend to be complicated/cumbersome even if you touch just a part.
Agreed. Will start with a small PR for gts.
|
Fix for Issue #112 (interval-tree bug)
This PR should fix Issue #112.
Assuming the algorithm used is the one described in Cormon, Leirserson, Rivest book, each node (x) added to the interval tree should be assigned a max value (max[int[x]]) as well as an interval (int[x]). The previous version was assigning a max value of -Infinity, rather than max[int[x]].
Awesome, thanks for the catch and the fix!
|
function ddg_spice_in_theaters(rotten) {
if(rotten.movies.length > 0) {
console.log(rotten);
var query = DDG.get_query().toLowerCase().split(' ');
var mpaa;
var title = 'Currently In Theaters';
//Check if the user wants to filter by MPAA rating
for(var i = 0;i < query.length;i++) {
if(query[i] === 'r' || query[i] === 'pg' || query[i] === 'pg-13' || query[i] === 'g') {
mpaa = query[i].toUpperCase();
console.log(mpaa);
}
if(query[i] === 'opening') {
title = 'Opening Movies'
}
}
var out = '', length, executed = false, more = '', count = 0;
out += '<div style="movies"><ul>';
more += out;
//Get the movies
for(var i = 0;i < rotten.movies.length;i++) {
var movie = rotten.movies[i];
var rating;
//Check if the movie has ratings
if (movie.ratings.critics_score === -1) {
rating = "Not Yet Reviewed";
} else {
rating = movie.ratings.critics_score + '/100';
}
//Get cast of the movie
var starring = ' starring ' + movie.abridged_cast[0].name;
var hour = 0;
var min = 0;
if(movie.runtime >= 60) {
hour = Math.floor(movie.runtime / 60);
min = movie.runtime - (hour * 60);
} else {
min = movie.runtime;
}
//Display the movie
var bullet = '<li title="' + movie.synopsis + '"><a href="' + movie.links.alternate + '" title="' + movie.synopsis + '">'
+ movie.title +'</a>' + starring + ' ('
+ movie.mpaa_rating + ', ' + hour + 'hr ' + min + 'min) '
+ 'rated ' + rating
+ '</li>';
//Check if MPAA is available
if(mpaa) {
if(mpaa === movie.mpaa_rating) {
count++;
executed = true;
//If there are more than 5 items, move to the second array
if(count > 5) {
more += bullet;
} else {
out += bullet;
}
}
} else {
count++;
executed = true;
if(count > 5) {
more += bullet;
} else {
out += bullet;
}
}
}
//Check if it returned any results
if(!executed) {
return;
}
out += '</ul></div>';
var items = [[],[]];
items[0]['a'] = out;
items[0]['h'] = title;
items[0]['s'] = 'Rotten Tomatoes';
items[0]['u'] = 'http://www.rottentomatoes.com/movie/in-theaters/';
items[0]['force_big_header'] = true;
items[0]['f'] = 1;
if(count > 5) {
more += '</ul></div>';
items[1]['a'] = more;
items[1]['t'] = '+More movies';
items[1]['s'] = 'Rotten Tomatoes';
items[1]['u'] = 'http://www.rottentomatoes.com/movie/in-theaters/';
items[1]['force_big_header'] = true;
items[1]['f'] = 1;
}
items
nra(items);
}
}
|
<P> Blow was the final theatrical film directed by Demme to be released in his lifetime . </P> <P> A young George Jung and his parents Fred and Ermine live in Weymouth, Massachusetts . When George is ten years old, Fred files for bankruptcy, but tries to make George realize that money is not important . </P> <P> As an adult, George moves to Los Angeles with his friend "Tuna"; they meet Barbara, an airline stewardess, who introduces them to Derek Foreal, a marijuana dealer . With Derek's help, George and Tuna make a lot of money . Kevin Dulli, a college student back in Boston, visits them and tells them of the demand for marijuana in Boston . They start selling marijuana in Boston, buying marijuana directly from Mexico with the help of Santiago Sanchez, a Mexican drug lord . Two years later, George is caught in Chicago trying to import 660 pounds (300 kg) of marijuana and is sentenced to two years . After unsuccessfully trying to plead his innocence, George skips bail to take care of Barbara, who dies from cancer . Her death marks the disbanding of the group of friends; even his friend, Tuna, flees their vacation home in Mexico and is never seen again . </P> <P> While hiding from the authorities, George visits his parents . George's mother calls the police, who arrest him . George is sentenced to 26 months in a federal prison in Danbury, Connecticut . His cellmate Diego Delgado has contacts in the Medellín cocaine cartel and convinces George to help him go into business . Upon his release from prison, George violates his parole conditions and heads down to Cartagena, Colombia, to meet with Diego . They meet with cartel officer Cesar Rosa to negotiate the terms for smuggling 15 kilograms (33 lb) to establish "good faith". </P>
What did the girl in blow die from
|
// Copyright (c) Source Tree Solutions, LLC. All rights reserved.
// Licensed under the Apache License, Version 2.0. See License.txt in the project root for license information.
// Author: Joe Audette
// Created: 2016-10-19
// Last Modified: 2018-10-08
//
using cloudscribe.Core.IdentityServer.EFCore.Interfaces;
using cloudscribe.Core.IdentityServer.EFCore.Mappers;
using cloudscribe.Core.IdentityServerIntegration.Storage;
using IdentityServer4.Models;
using Microsoft.EntityFrameworkCore;
using System.Linq;
using System.Threading;
using System.Threading.Tasks;
namespace cloudscribe.Core.IdentityServer.EFCore
{
public class ClientCommands : IClientCommands, IClientCommandsSingleton
{
public ClientCommands(
IConfigurationDbContextFactory contextFactory
)
{
_contextFactory = contextFactory;
}
private readonly IConfigurationDbContextFactory _contextFactory;
public async Task CreateClient(string siteId, Client client, CancellationToken cancellationToken = default(CancellationToken))
{
cancellationToken.ThrowIfCancellationRequested();
var ent = client.ToEntity();
ent.SiteId = siteId;
using (var context = _contextFactory.CreateContext())
{
context.Clients.Add(ent);
await context.SaveChangesAsync().ConfigureAwait(false);
}
}
public async Task UpdateClient(string siteId, Client client, CancellationToken cancellationToken = default(CancellationToken))
{
if (client == null) return;
// since the Client doesn't have the ids of the scope entity child objects
// updating creates duplicate child objects ie Scopes and Secrets
// therefore we need to actually delete the found client
// and re-create it - we don't care about the storage ids
cancellationToken.ThrowIfCancellationRequested();
await DeleteClient(siteId, client.ClientId, cancellationToken).ConfigureAwait(false);
await CreateClient(siteId, client, cancellationToken).ConfigureAwait(false);
}
public async Task DeleteClient(string siteId, string clientId, CancellationToken cancellationToken = default(CancellationToken))
{
cancellationToken.ThrowIfCancellationRequested();
using (var context = _contextFactory.CreateContext())
{
var client = context.Clients
.Include(x => x.AllowedGrantTypes)
.Include(x => x.RedirectUris)
.Include(x => x.PostLogoutRedirectUris)
.Include(x => x.AllowedScopes)
.Include(x => x.ClientSecrets)
.Include(x => x.Claims)
.Include(x => x.IdentityProviderRestrictions)
.Include(x => x.AllowedCorsOrigins)
.FirstOrDefault(x => x.SiteId == siteId && x.ClientId == clientId);
context.Clients.Remove(client);
await context.SaveChangesAsync().ConfigureAwait(false);
}
}
}
}
|
## Corkboard Server
Corkboard Server is a simple Sinatra app using Datamapper and SQLite that
allows the saving, updating and retrieval of simple 'notes'. It's intended
as an example for learning how to use Sinatra as a fast-to-make web app
approach for iOS developers. Corkboard Server goes with Corkboard client to
make a small, functional mobile application.
### Features
* Illustrates creation of an API with Sinatra
* Shows how to create a data model using Datamapper and SQLite
* Shows how to write tests for the web application
### Install
You'll need Ruby 1.9.3 to run, and Bundler to install the necessary gems.
$ git clone https://github.com/oisin/corkboard_server_example.git
$ bundle
$ rackup
>> Thin web server (v1.5.0 codename Knife)
>> Maximum connections set to 1024
>> Listening on <IP_ADDRESS>:9292, CTRL+C to stop
Your simple corkboard server is now running on port 9292 on you local machine.
### Running the tests
Once you have the code installed, running the tests is a simple as
$ bundle
$ bundle exec ruby tests/corkboard_test.rb
Running the tests will produce a test coverage file `coverage/index.html` which shows
all the pieces of code that were hit during the test run.
### API
This example code has a simple API for creating, updating and deleting 'notes'.
*Add a note to the database:*
$ curl -X PUT -d '{"subject": "bacon", "content": "chunky"}' http://localhost:9292/note
if you get a 400 back, it means that you missed out on sending the right JSON. If you get a 201, then look for a single string in the response body - it will be the id of the note that was just created. You can use the id in the GET to retrieve what you just created.
*Retrieve a note from the database:*
$ curl -X GET http://localhost:9292/note/1
returns JSON representation of note with id '1':
{
"subject" : "Wibble wibble",
"content" : "Must dismantle wardrobe in spare room",
"date" : "2013-02-24T13:36:12+00:00"
}
The marshalling code for the Note is embedded in the Note model class, it's cunningly stored in a to_json method. If the note isn't in the database, you'll get a 404. A 200 means go unmarshal the JSON returned.
*Updating a note in the database:*
$ curl -X POST -d "subject=wibble&content=chunky" http://localhost:9292/note/1
will update the content of note 1. If you get a 404, there isn't a note 1. If you get a 400, then you haven't given any arguments in the body of the request, i.e. changes to be made to the note. It should be along the lines of
{
"subject" : "Wibble wibble",
"content" : "Must dismantle wardrobe in spare room",
}
or even
{
"subject" : "Wibble wibble",
}
or
{
"content" : "Must dismantle wardrobe in spare room",
}
i.e., you can change the subject or the content. Any other stuff in the request will be ignored if it is not understood.
If you get a 500, then the database hasn't managed to save the update. Doh. You are looking for a 200 here to say everything is fine.
*Deleting a note from the database:*
curl -X DELETE http://localhost:9292/note/1
Will remove note 1 from the database. If you are running this little example thru a webserver, and there is no reason why you should, so don't, then you might have an issue because many webservers aren't configured by default to DELETEs and even PUTs. You can workaround this by using a POST with an _method parameter on Rails and some other platforms, but for this trivial example, don't bother. Just run it natively as instructed.
If you get a 204 back, the note is gone. If you get a 404 back, then that note has been gone already. If you get a 500, then the database destroy operation failed, ho hum.
### Authors
- Maintained by [Oisín<EMAIL_ADDRESS>- Updated for Portland Code School by [Chuck Lauer<EMAIL_ADDRESS>
### License
Copyright (c) 2010 Oisin Hurley
See ASL20.txt in this directory.
|
Use simply 'python3' as custom interpreter
Description of your problem
I want to use the system-installed Spyder3 to work on code that runs unter (several different) virtualenv environments. (I cannot use a pip-installed newer Spyder version because of its Qt dependency.)
For this, I currently have to change Spyder's "Python interpreter" to the absolute path of the virtualenv's python3 executable each time I change the environment.
For faster changes between virtualenv environments (or beween working in a virtualenv or system environment), it would be useful to set the interpreter just to python3, such that it is found on the $PATH.
What steps will reproduce the problem?
Under Preferences -> Python interpreter, try to set the interpreter just to python3.
What is the expected output? What do you see instead?
I would expect that the new setting is accepted.
Instead, a dialog says "You selected an invalid Python interpreter [...]".
Please provide any additional information below
I have got a workaround:
When I close Spyder and manually edit spyder.ini to executable = python3, everything works fine (i.e. !which python correctly shows my virtualenv's python) until I open the Preferences dialog again.
Versions and main components
Operating system: Debian Stretch
The following are the system defaults (at the current update level):
Spyder Version: 3.1.3
Python Version: 3.5.3
Qt Version: 5.7.1
PyQt Version: 5.7
Dependencies
Please go to the menu entry `Help > Optional Dependencies` (or
`Help > Dependencies`), press the button `Copy to clipboard`
and paste the contents below:
jedi >=0.9.0 : 0.10.0 (OK)
matplotlib >=1.0 : 2.0.0 (OK)
nbconvert >=4.0 : 4.2.0 (OK)
numpy >=1.7 : 1.12.1 (OK)
pandas >=0.13.1 : 0.19.2 (OK)
pep8 >=0.6 : 1.7.0 (OK)
psutil >=0.3 : 5.0.1 (OK)
pyflakes >=0.6.0 : 1.3.0 (OK)
pygments >=2.0 : 2.2.0 (OK)
pylint >=0.25 : 1.7.4 (OK)
qtconsole >=4.2.0: 4.2.1 (OK)
rope >=0.9.4 : 0.10.5 (OK)
sphinx >=0.6.6 : 1.4.9 (OK)
sympy >=0.7.3 : None (NOK)
I think an easier way to solve this would be to maintain a list of the most recent (10?) used interpreters, so users can easily switch between them.
@jondo, what do you think?
This would only be a slight improvement.
Just having executable = python3 would make it unnecessary to touch the preferences at all. A Spyder launch in an "activated" environment would automatically get the right executable.
Since editing spyder.ini to just python3 works, why not allow this editing to also happen in the GUI?
It would seem that the enhancement suggested by @ccordoba12 , adding is a pop up list of the most recently used python backends, seems to be somewhat different to bug pointed out by @jondo , that the Preferences GUI does not allow them to add the system python3 installation as a valid interpreter, even though it would function fine; the only reason it needs to be changed every session is due to this reason, and would be entirely unnecessary if it were fixed; on the other hand, assuming it wasn't, a less resourceful user wouldn't be able to even add it in the first place as it would fail, and might not get added anyway as it was manually edited into the ini.
@jondo, if you have Spyder installed in every environment (as it seems the case), you don't need to change the Python interpreter every time you start Spyder. Simply using the default interpreter should pick up the interpreter in your environment.
No, as I wrote, I need to use the system-installed Spyder 3.1.3. I have tried installing Spyder in the environments, but this gives me an error about missing Qt libraries. I only have the system-installed Qt 5.7.1 available.
Then how do you expect that simply passing python3 would select the interpreter of your environment?
When I apply my workaround of directly editing spyder.ini to executable = python3, I see that this works: I can use the packages that are only installed in my environment. Also, !which python shows the correct path into my environment.
Can you please change this issue's title back? The new one does not reflect my problem.
We do some validations to detect if the executable you pass as a custom interpreter is really a Python interpreter. So that's why we need he full path of the executable.
If you manage to make those validations to work by simply passing python3, then we'll merge your work for sure.
What about internally replacing python3 by whatever is returned from which python3 before doing the validations?
Sounds good, but this is a specific case of yours, so sorry to say it but we don't plan to work on it.
However, as I said, we're welcome to receive PRs that fix it, in multiplatform way (e.g. there's no which on Windows).
I understand. As a note, on Windows the where command might work.
At least on my machine, it indeed returns the exact same results, in the same format, etc., as which does.
I'm having the same issue, how do you edit spyder.ini? Where is the file located?
@SreehariRamMohan ~/.spyder-py3/spyder.ini
I want to avoid global state, so I do not want to edit my Spyder preferences whenever I am switching between venvs. Fortunately, I found a solution:
In the Spyder preferences, I keep the Console -> Python executable at Default.
I launch Spyder within my venv as
python `which spyder3`
This way, the venv's python is used for Spyder's Python consoles.
(Reading https://github.com/firedrakeproject/firedrake/issues/1218, @ZhouleiJoeStone might also be interested in this.)
|
User:Tomouko
Today is: 28, August 2024
/My sandbox/
=About me=
My name is Tom O. Ouko. I am an author at a wikieducator workshop,MMUST, November 5-7, 2008
My family
I am a Kenyan, married with three children- two boys and one girl.
My professional background
As an editor:
* Scout for authors
* Work with authors to develop pubshable manuscripts
* Prepare copy upto pre-press
* Liaise with printers
As a lecturer:
Reseacrh interests include: media generally, communication
* Teach\lecture
* Supervision of students
* Examination
* Research
Consultancy work
* Publishing
* Media and Communication
Contact
Email<EMAIL_ADDRESS>or [email protected]
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.