text:
How to Analyze Your Damages Under The Age Discrimination in Employment Act (ADEA)
The following is a synopsis of facts and quotes from Skalka v. Fernald Environmental Restoration Management Corp., 178 F.3d 414 (6th Cir. (Ohio) May 19, 1999). This case discusses, in detail, important issues arising in discrimination cases. This particular case was heard before the Court of Appeals for the Sixth Circuit, which is the appeals court that hears federal appeals from several states in the Southeastern United States.
This case was brought by four former employees who worked for FERMCO, a company engaged in the clean-up of uranium waste. FERMCO underwent a workforce reduction where employees were divided into peer groups, evaluated, and ranked. The employees at the bottom of certain lists were laid off. Skalka was one of four Remedial Support Operations employees (RSO's). The other three RSO's were all younger than Skalka, who was 54 at the time of his termination. Although Skalka received a nearly perfect score on his evaluation, he was terminated, and the other three were not. The reason FERMCO gave Skalka for his termination was that the particular department that he supported no longer needed an RSO, while the other departments each still needed one. Skalka argued that the person with the lowest rating should have been laid off and that he should have been moved to that person's position. The Plaintiffs in this litigation were, like Skalka, veteran employees. They, however, were ranked at the bottom of their respective group, and were fired as a result.
FERMCO conducted a statistical study of the effects of the layoffs and concluded that there was a possible disparate impact on older workers. FERMCO, however, argued that the difference in the number of older and younger workers laid off was negligible. The Defendant based this conclusion on the assumption that all groups should be equally affected. In contrast, the Plaintiffs asserted that, because of their greater experience, they should have been disproportionately unaffected by the layoffs.
The federal district court jury found that FERMCO had willfully discriminated against Skalka and one of the other Plaintiffs and gave those two a doubled back pay award and a front pay award. The jury rejected the other two Plaintiffs' claims. FERMCO appealed, claiming, among other things, that the damages had been calculated erroneously.
Below is the Court of Appeals for the Sixth Circuit's discussion on the damages available to Skalka.
The jury awarded Skalka $ 487,907 in back pay and $ 529,416 in front pay for his ADEA claim, as well as $ 225,000 for his contract claim. FERMCO has several complaints about these damages. As an initial matter, we reject its claim that the jury's decisions reflect "passion and prejudice." By FERMCO's own arguments the inflated damages awards are the result of errors rather than unprincipled anger at FERMCO.
In the absence of undue passion and prejudice on the part of the jury, we review for abuse of discretion the district court's refusal to grant a new trial based on excessive damages or a remittitur. See Roush v. KFC Nat'l Mngmnt. Co., 10 F. 3d 392, 397 (6th Cir. 1993), cert. denied, 513 U.S. 808 (1994). A verdict is not excessive unless it exceeds "'the maximum that a jury could reasonably find to be compensatory' for the plaintiff's loss." Id. (quoting In re Lewis, 845 F.2d 624, 635 (6th Cir. 1988)) Here, the district court refused to reduce the damages because the plaintiffs were able to offer a "tenable" explanation for the amounts. As FERMCO demonstrates in its brief, the jury clearly arrived at Skalka's back-pay figure by adding the stipulated amounts of salary and non-pension benefits to his projected pension without accounting for the amounts Skalka had received in early retirement benefits and in income from other employment. The plaintiffs' explanation for the damages incorporated the jury's clearest error, the failure to discount future pension benefits to present value. We therefore find it necessary to remand for the district court to calculate an appropriate remittitur and, if necessary, hold a retrial on the damages issue.
(1) Pension Benefits as Part of Back Pay
Over half of Skalka's "back-pay" award was compensation for pension benefits he eventually would have received if he had stayed at FERMCO until retirement. FERMCO argues that, by definition, payments expected in the future cannot be part of back pay. N3. The plaintiffs do not attempt to defend the inclusion of future payments in the back pay award, arguing only that FERMCO failed to object to jury instructions that defined back pay as including "pension benefits which a plaintiff would have received had the discrimination not occurred." FERMCO responds that the parties intended this to refer only to 401(k) payments that would have been made during the time before the trial.
The conversation at the charge conference clearly treated 401(k) payments as "part of the pension benefits," but it is not clear whether the parties were treating the future payments as back pay. The plaintiffs' closing argument discussed back pay, front pay, pension benefits, and 401(k) payments, in that order. The verdict form, however, had space only for back pay and front pay, leaving the jury to classify pension and 401(k) benefits as it saw fit. Although plaintiffs' counsel at one point referred to the claimed future pension benefits as "lost wages," this apparent slip of the tongue did not suffice to put FERMCO on notice that all pension benefits would be considered back pay. We conclude that FERMCO did not forfeit this issue and that only the portion of the damages that truly represents "back pay" should be doubled. Because $ 269,353 of the jury's "back-pay" award was compensation for Skalka's expected pension, that amount should be treated as front pay rather than back pay.
(2) Speculative Nature of Pension Benefits
FERMCO also argues that there was insufficient evidence to support the award of any pension benefits because those benefits were too speculative. FERMCO's argument on this point focuses on Conover, who in light of our holdings above is not entitled to any damages. FERMCO points out that the project was expected to last only ten to fifteen years and therefore would have ended before Conover turned 65. It claims that after the project is completed "'all personnel will move on to other employment or retirement.'" However, the document it cites for this proposition is rather vague. ("Whether such employees [will] have a continued presence at the [site] will depend upon the availability of other work for which they are qualified.").
Skalka was several years older than Conover and would have retired within the projected lifetime of the project. FERMCO's arguments that the pension component of the damages was speculative do not apply to him, and the jury was within its rights to award him damages for his lost pension. Thus, except as discussed in the next section, this portion of the award may stand as a component of front pay.
(3) Failure to Discount the Pension to Present Value
Perhaps because it erroneously treated the pension benefits as back pay, the jury failed to discount them to present value. The plaintiffs' justification of the damages to the district court made the same error, and they do not attempt to defend the error on appeal.
We have in the past been vigilant in correcting juries' failures to discount damages to present value. See e.g, Rodgers v. Fisher Body Div., Gen. Motors Corp., 739 F.2d 1102,1105-06 (6th Cir. 1984) (raising this issue sua sponte), cert. denied, 470 U.S. 1054, (1985). We therefore instruct the district court to apply an appropriate discount rate to the pension benefits in calculating the remittitur and carefully to instruct the jury on this issue if there is a re-trial.
(4) Failure to Reduce Back Pay to Account for Other Income
FERMCO claims that the jury unreasonably failed to subtract Skalka's early retirement benefits and money he earned through other employment from his back-pay award.
Skalka's back-pay award -- $ 218,554 once the future pension benefits are re-classified as front pay -- compensated him for his lost salary and benefits up until the time of the verdict. n4 FERMCO argues that this award should be reduced because, several months after his termination, Skalka secured a higher-paying position with another company. Skalka had a duty to mitigate his damages by seeking new employment, but the burden of proving reductions in Skalka's damages is on FERMCO. See Jackson v. City of Cookeville, 31 F.3d 1354, 1359 (6th Cir. 1994). Therefore, the remittitur calculated on remand should reflect Skalka's new employment to the extent that any rational jury would have found this income to be proven. We note that Skalka is not entitled to back pay for any period in which he earned an equal or higher salary than he would have earned at FERMCO, see, EEOC v. New York Times Board. Serv., Inc., 542 F.2d 356, 359 (6th Cir. 1976), but that his "excess" earnings are not to be subtracted from the back-pay award for the period of unemployment. See Matthews v. A-1, Inc., 748 F.2d 975, 978-79 (5th Cir. 1984); see also Darnell v. City of Jasper, 730 F.2d 653, 656-57 (11th Cir. 1984); Leftwich v. Harris-Stowe State College, 702 F.2d 686, 693-94 (8th Cir. 1983).
FERMCO also argues that Skalka's back-pay award should be reduced because he received early retirement benefits during the time between his termination and the trial. Such benefits, however, may constitute payments from a collateral source that are not properly subtracted from the damages awarded to a discrimination plaintiff. See Hamlin v. Charter Township of Flint, 165 F.3d 426, 432-36 (6th Cir. 1999). In Hamlin, we set out a test for determining whether pension benefits are collateral. See id. at 435. On remand, the district court should apply Hamlin to determine whether Skalka's retirement benefits received up until the time of trial should be subtracted from his back-pay award.
(5) Front Pay
FERMCO asserts in its brief that Skalka's front-pay award should be vacated:
Under the ADEA, "a substantial liquidated damage award may indicate that an additional award of front pay is inappropriate or excessive." Weaver v. Amoco Prod. Co., 66 F.3d 85,89 (5th Cir. 1995). But at the same time that the jury was giving Skalka and Conover inflated liquidated damage awards, it was also giving them huge front-pay awards. These front-pay awards should be vacated.
This argument is no longer applicable because our decision classifying Skalka's pension as front pay will have the effect of substantially reducing the "liquidated damages" (i.e., the doubled back pay to which Skalka is entitled because the jury found that FERMCO discriminated willfully). The remainder of this section of FERMCO's brief is devoted to Conover's claim, and the arguments are not applicable to Skalka. As FERMCO acknowledges, this circuit has held that the amount of front pay is for the jury to decide, see Roush, 10 F.3d at 398, and FERMCO has not pointed to any identifiable flaw in the jury's determination. Thus, when the district court determines the remittitur, it should allow the front-pay award to stand as determined by the jury, adjusted consistent with this opinion.
(6) Overlap Between ADEA and Contract Damages
FERMCO claims that it made no sense for the jury to award contract damages, since Skalka was fully compensated for his lost pay (past and future) through his ADEA damages. Although we have held that Skalka's contract claim fails as a matter of law, the plaintiffs' calculation of the damages makes the not unreasonable assumption that the jury simply chose to "allocate" some of the total damages to the contract claim. Therefore, in determining the remittitur, the district court should start with the total amount awarded, rather than just throwing out the contract damages. For example, under both claims the plaintiffs asked the jury to award damages for lost 401(k) payments. The damages figures for the ADEA claims suggest that the jury did not include 401(k) damages in its back-pay calculations, but it may have taken the 401(k) payments into account in the damages it allocated to the contract claim. The court's duty in calculating a remittitur is to determine the maximum amount the jury could reasonably have awarded. See Katch v. Speidel, Div. of Textron, Inc., 746 F.2d 1136, 1144 (6th Cir. 1984). Therefore, the remittitur should assume that the jury awarded damages for 401(k) payments at the rate requested by Skalka and that Skalka is entitled to 401(k) damages whether or not the jury lumped them into its contract claim award.
(7) Summary of Damages Issues
In summary, the district court's determination of the remittitur should take into account the following. Skalka's back-pay award properly includes the stipulated value of Skalka's salary and benefits less severance pay ($ 218,554), reduced to the extent required by his other employment and early retirement benefits. The front pay award may stand as determined by the jury, increased by an amount to compensate for Skalka's lost pension ($ 269,353 in future payments, which should be reduced to present value). In addition, the damages allocated by the jury to Skalka's contract claim may be re-allocated if appropriate to either back pay or front pay, to the extent that a reasonable jury could have awarded more on the ADEA claim. Finally, the back-pay award is doubled due to the finding of willfulness.
D. POST-JUDGMENT INTEREST
The parties dispute whether post-judgment interest on the jury's awards accrued from the date on which the district court entered an initial judgment memorializing the verdicts or from the later date on which the court entered a final, appealable judgment disposing of all claims. This question of statutory interpretation is one of first impression in this court and, so far as we are aware, in any federal court. We hold that interest runs from the date of the initial judgment.
N3 This issue is important to FERMCO because the back-pay award but not the front-pay award is doubled when the jury finds that the defendant's violation of the ADEA was willful.
N4 This figure reflects the stipulated value of Skalka's salary and benefits from the time of his termination until the time of the verdict, minus the amount he received as severance pay.


text:
Agent–Typically a citizen of a foreign country who has been recruited—by a CIA operations officer—to spy for the United States. A CIA agent is not an employee of the CIA, although he may receive money or other forms of payment in return for his services.
Ambassador–The US ambassador to a foreign country is an employee of the State Department and serves as a representative of the president of the United States. A CIA station chief is supposed to inform the ambassador of all CIA operations taking place in that foreign country.
BTC Pipeline—The acronym for the 1,100-mile-long Baku-Tbilisi-Ceyhan pipeline which transports oil from the Caspian Sea to the Mediterranean Sea via Azerbaijan, Georgia, and Turkey.
Camp Ashraf—A large camp in eastern Iraq, fifty miles from the border with Iran, that for years served as the headquarters of the Mojahedin-e Khalq (MEK), an Iranian resistance group. Saddam Hussein gave the camp to the MEK in 1986, but the new government in Iraq has taken steps to shut it down.
Case Officer—The same thing as a CIA operations officer; case officer is an older term, but is still often used.
Central Eurasia Division—The division within the CIA's National Clandestine Service that is believed to cover Russia and nations that were formerly a part of the Soviet Union.
DoD— Acronym for the US Department of Defense.
IAEA— Acronym for the International Atomic Energy Agency, a nuclear watchdog group affiliated with the United Nations.
KGB— Acronym for the komitet gosudarstvennoy bezopasnosti, which in Russian means Committee for State Security. The KGB was the intelligence agency of the Soviet Union and was disbanded when the Soviet Union collapsed in 1991.
Lada—A cheap, popular car produced in Russia.
MEK— Acronym for the Mojahedin-e Khalq (MEK), which means people's mojahedin. An armed Iranian resistance group.
National Clandestine Service—The part of the CIA that does the actual spying.
National Security Council—Comprised of the US president, vice president, national security advisor, secretary of state, secretary of defense, the director of the CIA, the director of national intelligence, and several other key members of the executive branch. The council is the principal forum used by the president and his team to consider foreign policy issues.
Near East Division—Officially known as the Near East and South Asia division. The division within the CIA's National Clandestine Service that is believed to cover the Middle East, Afghanistan, and Pakistan.
Niva—A four-wheel-drive version of a Lada, which is a cheap, popular car produced in Russia.
NOC—Acronym for nonofficial cover. A CIA NOC is a CIA operations officer serving in a foreign country without the security of a diplomatic cover identity.
Operations Officer—An employee of the CIA who works for the division of the CIA known as the National Clandestine Service.
Qods Force—The special operations division of Iran's Revolutionary Guard. Translates as Jerusalem force.
Revolutionary Guard—An elite Iranian military organization with its own army, navy and air force. It is separate from the regular Iranian military.
Seventh Floor—Shorthand for the leadership of the CIA, most of whom have offices on the seventh floor of CIA headquarters in Langley, Virginia.
Special Activities Division—A division within the CIA's National Clandestine Service that will often carry out paramilitary operations.
Station Chief—An employee of the CIA who oversees all CIA operations that take place within a particular country, or region within a country; a station chief would manage operations officers and consult closely with the ambassador.
The Colonel's Mistake by Dan Mayland
Content copyright © 2016. Dan Mayland. All rights reserved.

redpajama_set_name: RedPajamaCommonCrawl


text:
Q: Tablayout font not changing I want to add a font to the tablayout. The tabs are filled dynamically using Json.
Please suggest me how to add font to the tab headers.
This is the tablayout
private void setupPager() {
        viewPager.setAdapter(new CustomAdapter(getActivity().getSupportFragmentManager(),getContext()));
        tabLayout.setupWithViewPager(viewPager);
        Typeface tf = Typeface.createFromAsset(getActivity().getAssets(), "EdgeCaps.ttf");
        ViewGroup vg = (ViewGroup) tabLayout.getChildAt(0);
        int tabsCount = vg.getChildCount();
        for (int j = 0; j < tabsCount; j++) {
            ViewGroup vgTab = (ViewGroup) vg.getChildAt(j);
            int tabChildsCount = vgTab.getChildCount();
            for (int i = 0; i < tabChildsCount; i++) {
                View tabViewChild = vgTab.getChildAt(i);
                if (tabViewChild instanceof TextView) {
                    ((TextView) tabViewChild).setTypeface(tf);
                }
            }
        }
}

This is the adapter. Here tabnames is a string array filled by json parsing.
 private class CustomAdapter extends FragmentPagerAdapter {
        public CustomAdapter(FragmentManager supportFragmentManager, Context applicationContext) {
            super(supportFragmentManager);
        }

        @Override
        public Fragment getItem(int position) {
            Fragment fragment = new ItemsMenuFragment();
            return  fragment;
        }
        @Override
        public int getCount() {
            return tabNames.size();
        }

        @Override
        public CharSequence getPageTitle(int position) {
            return tabNames.get(position);
        }
    }

}
Can anyone help me to change the font of the tablayout.I have tried to use this in the setupPager but its not working.
 Typeface tf = Typeface.createFromAsset(getActivity().getAssets(), "EdgeCaps.ttf");
            ViewGroup vg = (ViewGroup) tabLayout.getChildAt(0);
            int tabsCount = vg.getChildCount();
            for (int j = 0; j < tabsCount; j++) {
                ViewGroup vgTab = (ViewGroup) vg.getChildAt(j);
                int tabChildsCount = vgTab.getChildCount();
                for (int i = 0; i < tabChildsCount; i++) {
                    View tabViewChild = vgTab.getChildAt(i);
                    if (tabViewChild instanceof TextView) {
                        ((TextView) tabViewChild).setTypeface(tf);
                    }
                }
            }

A: Not entirely sure what's going on in your code. But this class might help. All it does is set the all the TextViews inside a tab to EdgeCaps.tff whenever a new tab is added to the TabLayout.
Use it in place of a normal TabLayout and make sure that you've put your your EdgeCaps.tff font inside the "assets/fonts" directory of your project.

Here's an example of where the font file is meant to go (using Android Studio).

Code was modified from here to work with Android Support Library 23.3.0:
public class CustomFontTabLayout extends TabLayout {
    private Typeface mCustomTypeFace;

    public CustomFontTabLayout(Context context, AttributeSet attrs, int defStyleAttr) {
        super(context, attrs, defStyleAttr);
        initialise();
    }

    public CustomFontTabLayout(Context context) {
        super(context);
        initialise();
    }

    public CustomFontTabLayout(Context context, AttributeSet attrs) {
        super(context, attrs);
        initialise();
    }
    private void initialise()
    {
        // Note: Rename "EdgeCaps.tff" to whatever your font file is named.
        // Note that the font file needs to be in the assets/fonts/ folder.
        mCustomTypeFace = Typeface.createFromAsset(getContext().getAssets(), "fonts/EdgeCaps.tff");
    }

    @Override
    public void addTab(@NonNull Tab tab, boolean setSelected) {
        super.addTab(tab, setSelected);
        setTabTypeFace(tab);
    }

    @Override
    public void addTab(@NonNull Tab tab, int position, boolean setSelected) {
        super.addTab(tab, position, setSelected);
        setTabTypeFace(tab);
    }

    private void setTabTypeFace(Tab tab)
    {
        ViewGroup tabLayoutView = (ViewGroup)getChildAt(0);
        ViewGroup tabView = (ViewGroup) tabLayoutView.getChildAt(tab.getPosition());
        int tabViewChildCount = tabView.getChildCount();
        for (int i = 0; i < tabViewChildCount; i++) {
            View tabViewChild = tabView.getChildAt(i);
            // Find the TextView in the tab
            if (tabViewChild instanceof TextView) {
                TextView tabTextView = (TextView)tabViewChild;
                // Set the TextView's font
                tabTextView .setTypeface(mCustomTypeFace, Typeface.NORMAL);
            }
        }
    }
}

A: <style name="NavigationTab" parent="Widget.Design.TabLayout">
    <item name="tabBackground">@drawable/background_tab</item>
    <item name="tabSelectedTextColor">@color/primary_light</item>
    <item name="tabIndicatorColor">@color/blue</item>
    <item name="tabTextAppearance">@style/NavigationTabTextAppeareance</item>
</style>

<style name="NavigationTabTextAppeareance" parent="TextAppearance.Design.Tab">
    <item name="android:textColor">@color/primary_light</item>
    <item name="android:textSize">12sp</item>
</style>

Inside the TabLayout xml file. add this as style. change the fontsize according to what you want.

redpajama_set_name: RedPajamaStackExchange


Celebrate summer love and sunny skies! Avon Books is delighted to present this free e-book sampler, which includes excerpts from classic Avon tales as well as eight new or upcoming Avon and Avon Impulse novels, and a special introduction from bestselling author Susan Elizabeth Phillips.
None of these are complete stories. If I want to read jacket blurbs, I can browse on my own, thanks.


Onceit Coupon Code – BONDS Baby & Kids Up to 50% Off!
Founded in May 2010, OnceIt is one of New Zealand's fastest growing ecommerce stores. The stylish and innovative team are on a mission to provide New Zealanders with premium designer goods at insider prices.
With over 500 local and international brands there's no chance of being left out of style. Some of their favourite brands to work with are Stella McCartney, Sass & Bide, Ben Sherman, Bonds, Mons Royale, and Ecoya.
Become one of 400,000 loyal members today by using our exclusive invite code.


text:
La   Division d'Infanterie est une des divisions d'infanterie de l'armée polonaise durant la Seconde Guerre mondiale.

Création et différentes dénominations

Composition

Théâtres d'opérations
 1er septembre au  : Campagne de Pologne

Liens internes
 Liste des unités polonaises de la Seconde Guerre Mondiale
 Ordre de bataille lors de la campagne de Pologne (1939)

Division d'infanterie polonaise

redpajama_set_name: RedPajamaWikipedia


Very fast, friendly, and effective.
It was prompt and efficient. The employees seemed to be knowledgeable.
Very friendy and knowledgeable service man.
Very prompt on arrival after I phone, within 1 hour. Was very carefull putting down tarp on the floor and cleaning up when he left.


I'm trying to bring ajtcl to my MCU running MICO RTOS. but from the website https://allseenalliance.org/developer... I can not find how to do it. There is a lots of folds and files is depens on platform for AJTCL. So is alljoyn supports any RTOS? If yes, what I should do inside the ajtcl source package?
You can find a similar question to yours here.
Given that AllJoyn Thin Client implementation is a library that has been built on top of FreeRTOS, it should be possible to build it on top of MICO RTOS as well.
You would need to implement the target-specific RTOS / BSP wrappers that allow the creation of sockets, access to NVRAM and manipulate wireless peripheral, if available.
This link describing a different target board and a different RTOS might he helpful.


text:
/**
 * Created by guanbingchang
 */

class templateSvc  {
  constructor(Api,$location) {
    "ngInject";
    this.Api = Api;
    this.location = $location;
    this.baseUrl = "/role/";
  }

	addTemplate(params){
		return this.Api.post('/role/operate/act/save',params);
	}

//保存模板role/operate/act/save
  savetemplate(params){
  	 return this.Api.post(this.baseUrl + 'operate/act/save', params);
  }
  //显示所有模板 role/search
	getPageAllTempList(params){
		return this.Api.get(this.baseUrl + 'search',params);
	}
	//显示模板 根据名字
	getPageTempbyname(params){

		return this.Api.get(this.baseUrl + 'search/page/1/limit/10',{'templateName':params});
	}
	getTempList(id){
	    return this.Api.get('/template/detail',{});
	}
	//返回新建模板
	returnnewTemplate(){ //ok
     this.location.path("/template/add");
	}

  	//取消
	returnnewTemplate(){ //ok
   		// this.location.path("/template/add");
	}
  	/**
	 * [getDetail 详情]
	 */
	// /role/operate/act/detail/rid/'+params
	getDetail(params){
	    return this.Api.post(this.baseUrl+'/operate/act/detail/rid/'+ params.id, params);
	}

	postEdit(params){
		// debugger;

	    return this.Api.post(this.baseUrl+'operate/act/save/rid/'+params.rid, params);
	}
	changeStatus(params){
		console.log(params);
		//debugger;
		console.log('operate/act/update/rid/'+params.rid+/pause/+params.status);
	    return this.Api.get(this.baseUrl+'operate/act/update/rid/'+params.rid+/pause/+params.status);
	}
	//删除
	remove_role(params){
			console.log(params.rid);
		  return this.Api.post(this.baseUrl+'/operate/act/remove/rid/'+ params.rid, params);
	}

	getTree(type){
		var _type = 'sop';
		if(type){
			_type = type;
		}
		return this.Api.get('/role/operate/act/nodes/type/'+type);
	}
	//返回模板list
  returntemplist(){ //ok
     this.location.path("/template/list");
  }
}

export default templateSvc

redpajama_set_name: RedPajamaGithub


text:
Q: splitting a data.table, then modifying by reference I have a use-case where I need to split a data.table, then apply different modify-by-reference operations to each partition. However, splitting forces copying of each table.
Here's a toy example on the iris dataset:
#split the data
DT <- data.table(iris)
out <- split(DT, DT$Species)

#assign partitions to global environment
NAMES <- as.character(unique(DT$Species))
lapply(seq_along(out), function(x) {
assign(NAMES[x], out[[x]], envir=.GlobalEnv)})

#modify by reference, same function applied to different columns for different partitions
#would do this programatically in real use case
virginica[ ,summ:=sum(Petal.Length)]
setosa[ ,summ:=sum(Petal.Width)]

#rbind all (again, programmatic)
do.call(rbind, list(virginica, setosa))

Then I get the following warning:
 Warning message:
 In `[.data.table`(out$virginica, , `:=`(cumPedal, cumsum(Petal.Width))) :
  Invalid .internal.selfref detected and fixed by taking a copy of the whole table so that := can add this new column by reference.

I know this is related to putting data.tables in lists. Is there any workaround for this use case, or a way to avoid using split? Note that in the real case, I want to modify by reference programatically, so hardcoding a solution won't work.

A: Here's an example of using .EACHI to achieve what it sounds like you're trying to do:
## Create a data.table that indicates the pairs of keys to columns
New <- data.table(
  Species = c("virginica", "setosa", "versicolor"),
  FunCol = c("Petal.Length", "Petal.Width", "Sepal.Length"))

## Set the key of your original data.table
setkey(DT, Species)

## Now use .EACHI
DT[New, temp := cumsum(get(FunCol)), by = .EACHI][]
#      Sepal.Length Sepal.Width Petal.Length Petal.Width   Species  temp
#   1:          5.1         3.5          1.4         0.2    setosa   0.2
#   2:          4.9         3.0          1.4         0.2    setosa   0.4
#   3:          4.7         3.2          1.3         0.2    setosa   0.6
#   4:          4.6         3.1          1.5         0.2    setosa   0.8
#   5:          5.0         3.6          1.4         0.2    setosa   1.0
#  ---
# 146:          6.7         3.0          5.2         2.3 virginica 256.9
# 147:          6.3         2.5          5.0         1.9 virginica 261.9
# 148:          6.5         3.0          5.2         2.0 virginica 267.1
# 149:          6.2         3.4          5.4         2.3 virginica 272.5
# 150:          5.9         3.0          5.1         1.8 virginica 277.6

## Basic verification
head(cumsum(DT["setosa", ]$Petal.Width), 5)
# [1] 0.2 0.4 0.6 0.8 1.0
tail(cumsum(DT["virginica", ]$Petal.Length), 5)


You may not pay too much attention to what your right thumb (for right-handed golfers) does during the golf swing. But many everyday players take their grip with the right thumb right on top of the shaft in what many instructors call the 12 O'Clock position. In an effort to generate extra power for more distance, golfers will squeeze the club between this thumb and index finger to try to control the club. What happens instead is this squeezing move activates muscles that actually prevent the forearms from rotating all the way through impact, robbing you of power and distance.
Ben Hogan, in his legendary book "Five Lessons: The Modern Fundamentals of Golf," called the right thumb and index finger "swing-wreckers." Hogan advised, "gripping the club with the right thumb and forefinger off the shaft helps a golfer to accustom himself to the feeling of a strong, correct grip in which both hands work together as one unit." He recommended that golfers practice gripping and swinging with the right thumb and forefinger completely off the shaft to ingrain that feeling. Tom Lehman, Fred Couples, Brandt Snedeker are among the modern golfers who advocate practicing with the right thumb and forefinger off the shaft to promote the hands working together in the swing to increase clubhead speed.
Hogan says the two middle fingers apply most of the right-hand grip pressure. Most instructors and good players agree. Instead of resting directly on top of the shaft in the 12 O'Clock position, the right thumb should be in more of a relative 10 O'Clock position to the left of the shaft and resting on the tip of the right index finger. In that position, the right thumb can lend support without applying excess pressure to the shaft. Your forearms can rotate more freely through impact, allowing you to generate more power and add more distance.


Tis the season of gift giving! Pemberton Farms offers a large selection of fruit baskets, gourmet gift baskets, smoked meats, homemade chocolates, candies, gift towers, coffee cakes, roasted nuts, cheeses, New England-style gift baskets and lots more. Select from one of our top gifts below or view all our gifts one category at a time. Buying several gifts? Can't find the right item for you? Call us and let our experienced staff help you create the perfect gift for your holiday recipients.
Note: Due to Department of Agriculture Laws we are unable to send any gifts that contain fruit to Arizona or California. If you select a fruit gift to one of those two states we will contact a mutual gift company in that state and do our best to have one made a close to the one you select as possible. Contact us with any questions.


Ripple price declined recently below the $0.4520 support and tested $0.4000 against the US dollar.
There is a major bearish trend line formed with resistance at $0.4600 on the hourly chart of the XRP/USD pair (data source from Kraken).
The pair could correct higher, but the previous support at $0.4520 may act as a resistance.
Ripple price failed to hold gains against the US Dollar and Bitcoin. XRP/USD declined towards $0.4000 and it is currently correcting higher.
Yesterday, we saw how ripple price was resilient when bitcoin fell sharply against the US Dollar. However, buyers gave up later, resulting in a sharp decline below $0.4600 in the XRP/USD pair. The price declined below the $0.4520 and $0.4400 support levels. It even broke the $0.4200 support and settled below the 100 hourly simple moving average. A low was formed at $0.4011 and later the price started an upside correction.
The price recently moved above $0.4200 and the 23.6% Fib retracement level of the last drop from the $0.4933 high to $0.4011 low. However, there are many hurdles on the upside for buyers near the $0.4480 and $0.4500 levels. More importantly, the previous support at $0.4520 is likely to act as a strong resistance. Besides, there is a major bearish trend line formed with resistance at $0.4600 on the hourly chart of the XRP/USD pair. Therefore, if the price corrects higher from the current levels, it could find a strong barrier near $0.4520. Above $0.4520, the price could test $0.4720 and the 100 hourly SMA.
Looking at the chart, ripple price seems to be finding a decent support near $0.4000. Thus, the price may correct higher or consolidate in the short term above $0.4200 and $0.4300 before the next move.
Hourly RSI (Relative Strength Index) – The RSI for XRP/USD has recovered above the 40 level.


A friend once confided in me that she had had an abortion. She had two children and pregnancy hadn't been easy on her. Her doctors told her that continuing her latest pregnancy was risking her life. I could tell she was in pain and I didn't know what to say. No one had ever told me flat out about their abortion before. There is so much I should have said and done in that moment. But I didn't. Here's what you should do if your friend confides in you about her abortion.


Guthman Musical Instrument Competition 3/8/19 Click on the large image below to download a PDF of the deck.
moForte AUv3 Presentation 3/1/19 Click on the large image below to download a PDF of the deck.
Deck for the moForte Bish Bash presentation 2/28/19, Click on the large image below to download a PDF of the decks.
moForte ports Virtual Analog Synth to SHARC Audio Module using Faust.
Deck for the A3E workshop at NAMM 2019, "Faust on SHARC Audio Module", Jan 26, 2019 Click on the large image below to download a PDF of the decks.
Deck for workshop about "PAW Workshop Faust on SHARC Audio Module" 12/01/2018 Click on the large image below to download a PDF of the decks.


text:
Rocket Mortgage Classic officials eye big return from pandemic
More than 30,000 fans could attend some portion of this weekend's tournament at Detroit Golf ClubGETTY IMAGES
Rocket Mortgage Classic tournament officials in Year 3 of the event are "looking to make the equivalent of a come-from-behind, final-nine charge," having been dealt a "short window in which to rally and get things back to normal as normal can be," according to Tony Paul of the DETROIT NEWS. The third annual tournament -- which "drew huge galleries in the inaugural year as the PGA Tour returned to Michigan" for the first time since '09, and then "no galleries in the second year because of COVID-19" -- starts Thursday and runs through July 4 at Detroit Golf Club. Multiple days of "sellouts, almost certainly Friday and Saturday, are expected," despite having "only a third of the time to sell tickets" compared to '19. Conservatively, more than 30,000 fans "could attend at some point during the week," meaning it will be "almost certainly the most-attended sporting event in Michigan since the pandemic." Rocket Mortgage Classic Tournament Dir Jason Langwell said, "We say it's our third year, but in many ways, we've had three Year 1s. Every one's been different." Paul noted sponsors have "stuck with the tournament," which raised $2.7M for charity, including $2.4M for the RMC's "new COVID-19-inspired mission -- Changing the Course, which aims to end Detroit's digital divide" by '25. This is the third year of an initial four-year contract signed by Rocket Mortgage and the PGA Tour. Typically, when there is an extension on the PGA Tour, it "comes the week of the second-to-last year of the original deal." All indications are "pointing toward an extension for the tournament" (DETROIT NEWS, 6/26).
PREVIOUS Media Notes NEXT Wasserman golf agent John Mascatello passes away at 61
https://www.sportsbusinessjournal.com/Daily/Issues/2021/06/28/Events-and-Attractions/Rocket-Mortgage-Classic.aspx


Ordered mesostructured TiO2 thin films are employed in diverse applications ranging from catalysis and sensing, to photovoltaic and lithium-ion batteries. Experimentally these mesostructured thin films are fabricated via a sol–gel process coupled with evaporation-induced self-assembly of a supramolecular template, where the concentration of hydrogen chloride (HCl) and water play vital roles. We employ a soft, coarse-grained model of the amphiphilic template Brij58 and spherical particles, representing titanium–oxo clusters, to study the role of HCl and water in the formation of mesostructured TiO2 thin films. The template–cluster and cluster–cluster interactions are reflected in the interaction terms δNBP and εPP, respectively. The results show that a decrease in HCl (increase in εPP) leads to the formation of large mesopores due to the strong attraction between particles, giving rise to a high dispersity index (low order) of the thin films. However, a decrease in water (increase in δNBP) will compensate for the entropic attraction between particles, resulting in thin films with low dispersity index (high order). The variation of the dispersity index in the δNBP–εPP plane provides an intuitive understanding that the slow evaporation of HCl could drive the film towards a uniform mesoporous state, whereas fast evaporation pushes the film through a non-uniform phase. These results indicate that even if the mass proportion of the surfactants Brij58 and titanium precursors is the same in the initial solution, the final mesoporous structures could be diverse, which was confirmed by the controlled experiments. We also confirm the post-processing-towards-order strategy by making the particle rearrangement available by weakening the εPP. The outlined procedure paves the way for soft, coarse-grained models to understand the complex co-assembly of transition metal clusters and amphiphilic surfactants towards the rational design of highly ordered mesoporous structures.