--- layout: post title: Digital battlefield date: 2014-12-08 15:48:13.000000000 -08:00 categories: [] tags: [] status: publish type: post published: true meta: publicize_google_plus_url: https://plus.google.com/105504154595916021817/posts/D1TbXxH2WLe _rest_api_published: '1' _rest_api_client_id: "-1" _wpas_skip_facebook: '1' _wpas_skip_twitter: '1' _wpas_skip_linkedin: '1' _wpas_skip_tumblr: '1' _wpas_skip_path: '1' _wpas_done_9565331: '1' _publicize_done_external: a:1:{s:11:"google_plus";a:1:{s:21:"105504154595916021817";b:1;}} author: login: chrischang12 email<EMAIL_ADDRESS>display_name: chrischang12 first_name: '' last_name: '' ---
"Software is eating the world" and will continue to do so. That's why the battlefields for survival will shift from physical to digital. As a result, people will have to train themselves in the true universal language- programming languages. This is a good thing.
Net net, the more people who know how to program (even just the basics!) the better. Programming equates to problem solving. Software programs are not unlike puzzles in that you think through different scenarios and trade-offs and apply the proper action for your situation.
Before people can write programs however, they must first learn how to program. This step is where the true value, regardless if you become a programmer by trade or not, comes in. By learning to program, you must learn to think critically, rationally, and with applied consequence. Inevitably, you will be shaped by the process of learning that you otherwise may not have had to undergo. More people learning to think critically- this is one of the big victories for software.


Director Cosimo Di Giovanni
Greetings. I am Cosimo Di Giovanni, an honor student and also the President of the Business Leaders Club, Founder of the Student Economists Initiative, and Board Member of the SAIT-SCA Student Advisory. Like myself, many of our student members are already active leaders in the community and beyond. If you have the passion, we would be more than happy to guide you in your growth.
History
The Cosimo Group was founded in 1980 at a busy street corner by Wall Street and Main. Founded by two bright young businessmen, the organization quickly grew to become the biggest network of professionals and innovators in the world. Twenty years later, the organization expanded into universities where it became wildly popular with 30 different chapters sprouting up worldwide in less than a year.
Internships
Through the group, members are able to access a wide range of internship opportunities offered by alumni members. From tech startups to corporations, members are able to experience first-hand what it is like working in the real world.


Scream 3 -- the final cut: slash and learn
The third installment of any horror movie franchise is itself something of a zombie--a dead thing being forced to walk around, a re-animated corpse, just shuffling through the motions of life, pretending that the story which drives it is still vital, isn't just the first installment in a different setting, with a different cast and better effects. All the same, though, that third installment can't veer too far from what made the original successful. It is a franchise by now, after all; there has to recognizable features, characteristic 'franchise' traits. So it is with Wes Craven's Scream 3. Here we have Kevin Williamson's glib hip characters, all too aware of how intertextual their ongoing predicament is yet unable to get out of it, either. Next there's the trademark Ghostface slasher, who doesn't lumber around like Jason or change shapes like Freddy, but instead skulks about at high-speed, gets kicked a lot (a touch of verisimilitude for the doubters), and--most importantly--doesn't reveal his or her identity until the final frames, Scooby-Doo style. Thus everyone's a suspect, just as in Scream and Scream 2 , which fosters a tense, skeptical environment lightened time and again with comedy. Just when you think you know who the killer is, bam, that person dies gruesomely, someone makes a good joke about it, and then you're moving on, trying to deduce Ghostface's identity by elimination, if nothing else.
This is Sidney's (Nev Campbell) predicament: having to figure out who Ghostface is. Unlike the first two installments, though, this time she isn't in a sexually-charged, socio-academic setting, surrounding by friends who don't yet know they're fodder. Now she's done the Laurie Strode shtick, and isolated herself--insulated herself--taken an outpost in the woods, where she can see the bad guys coming from a long ways off (she hopes). The bad thing is, though, Ghostface saw H2O too, and is doing the Michael Myers thing, tracking her down, killing people to extract her location. Specifically, killing all the people involved with the making of "Stab 3," the movie-within-the movie which acts as commentary upon Scream 3 itself. Which is nice, yes, but too, familiar territory for Wes Craven. This is how he tried to inject new life into the Nightmare series (New Nightmare), after all, and, though it wasn't quite effective there, it does work here, if for no other reason than that it allows the Scream-formula to play itself out element by element, using as its excuse that it's modeled on the movie, and the movie itself was modeled on that initial event--which, for us, was the original Scream. Too, having all these sound-stages within sound-stages allows for some serious walk-ons: Parker Posey, Jenny McCarthy, Lance Henrikson, Patrick Dempsey, Carrie Fisher, Patrick Warburton (Seinfeld's Puddy), and, last but not least, Kevin Smith's Silent Bob and Jay. Add to this the usual suspects--'survivors' Courteney Cox, David Arquette, and Nev Campbell (as the heroin/e the horror audience is addicted to)--and Scream 3 has quite a retinue, each more killable than the last.
The big question with it, though, is does it still have enough juice, is it as powerful as the first installment? Because we all know that second, while decent, kind of lost it at the end, or, rather, when everyone was unmasked, it became apparent that we couldn't really have guessed it. Which insures the ending will be a surprise, yes, but does so with obfuscation instead of misdirection. And misdirection is what made the original Scream so good. Too, in talking about the third as compared to the first two, you have to take into account that to both be as original as the original and still remain 'faithful' to the original is a near-impossible task. That first Scream fundamentally changed commercial horror, by introducing some genre-awareness, and that same genre-awareness is what carried the second as well. All that meta-talk about the conventions of the sequel. Scream 3 continues the tradition, even resuscitating Randy (Jamie Kennedy) on videotape long enough for him to explain the trilogy they're in, how, as the trailer says, all bets are off.
And he's rights--the rules of the first two no longer hold. Scream 3 even goes so far as to hint at the 'real' supernatural (Sid's dead mom), which is perhaps it's one weak point. Well, one of two. The other is that, though you can't say for certain who Ghostface is going to be this time, you can nevertheless intuit who it's going to be in relation to the main characters, which is as specific as I can be without spilling many beans. That Scream 3 can still have still have beans to spill this late in the game is something of a feat, though, especially when it's kept itself to a minimum of contrivance. Most horror-series are just going through the motions by the third installment, troping around, playing the zombie, which is to say acting tired. Scream 3, however, shows few signs of fatigue. Maybe even a little reinvigoration, of all things, in the face of claims that, with the advent (success) of Blair Witch and Sixth Sense, the tennybopper slasher pic has run its course, is now making way for more mature horror, more cerebral horror, horror which reintroduces the supernatural which Scream and Phantoms disallowed. Lest we forget, though, horror is fundamentally about being young and scared, the 'safe' thrill of it all. However, if the naysayers are right, and Scream 3 is the last of its kind for a while, then the slasher pic couldn't have had a better send-off. Or, rather, send-up, which may have been Williamson's goal all along: by wearing the generic conventions on its sleeve throughout the trilogy, the Scream franchise pretty much insured that--even without Blair Witch and Sixth Sense--it would be the last of its kind. Any other teenybopper slasher pic which doesn't acknowledge those conventions and then do something with them will quite simply pale in comparison (e.g., I Know What You Did Last Summer, etc), be an insult to the audience of Randys Scream's cultured, who are already three steps ahead and grinning wide.
(c) Stephen Graham Jones, http://www.cinemuck.com
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


In 2020, with the devestating COVID pandemic, many sports fans have not been tunning into watch major sporting events. For the NBA Finals, the viewership has been decreasing since 2016 and has reached an average low of 7.5 million viewers this year, nearly half compared to the year before. Similarly, baseball’s World Series has seen a significant decrease from 2016 with just 9.7 million people tuning in to watch it. The NFL’s first Sunday night football game, which usually draws large numbers, has also been affected this year, although not as much. And, the UEFA Champions League Final, which is watched worldwide, has seen a slight decrease this year in average viewership.
Jon Lewis, who has been covering sports media and viewership for all major sports for 14 years, believes that the COVID pandemic and the lack of fans has had some effect on all the numbers. “I wouldn't say it's the primary factor, but in general it's a more subdued atmosphere. I do think the lack of fans did have some impact on it, I would imagine."
Sports viewership in major sports events in basketball, baseball, football, and soccer has been significantly low in recent years. This year, the number of people watching major sports events has gone down. The COVID pandemic may have affected the numbers this year due to the lack of fans attending games and due to the coverage that COVID was getting.
Sports Media Watch
Jon Lewis
Statista
LA Times


Code Quality Assurance¶
This page explains how to maintain the code quality of this repository. Currently, we do not have an automation to assure the following rules are satisfied, but this should be covered in the future.
Coding Style¶
This system is implemented in Python 3.6 and we basically follow PEP8 standard to unify the coding style. In addition, the following guides are defined by ourselves:
The max length of each line is 100 characters.
The indent size is 4 spaces and no tabs are allowed.
Specifically, we use pylint for coding style validation:
make lint
Look into the command in the Makefile, we can find that it uses a rc file under tests/lint/pylintrc. This file defines all coding style rules that will be checked by pylint. We require a perfect score rated by pylint and do not allow any pylint messages. It means everything specified in the rc file must be strictly followed.
Note
The rc file is slightly modified based on TVM but it can be changed based on the usage. Please discuss with the team before making any change to the file.
Type Checking¶
It is important to statically check types before running a Python package, because Python is basically type-free. Therefore, type annotation was introduced in Python 3 to help both developers and checking tools resolve as many type issues as possible before actual launching the program. In Merlin DSE, we use mypy to statically check types. We also do not allow any warning and error messages from mypy, but it is fine if they are from third-party packages.
make type
Note
mypy checks types passively. It will not check types if no type annotations in Python file. As a result, please make sure to at least add type annotations to method arguments, and then mypy will be triggered and provide further information for missing type annotations to other variables.
Auto-Formatting¶
We use yapf, an auto-formatting package open source by Google, to auto-format the code. Everyone should run this command before committing any changes. The formatting style is defined at tests/lint/yapf_style.cfg.
make format
Note
It is possible to have conflicts between yapf style and pylint style, so please make sure they are conflict-free when making changes to either files.
Unit Test and Code Coverage¶
We use pytest as the unit test framework and test code coverage. Use the following command to simply run all unit tests:
make unit_test
The unit test should take less than one minute and you will see a handy report to indicate the test results. If one or more tests were failed, you should go back to fix the problem and run the test again. Note that when you run the test again, it will only run the failed tests as we specified --lf in the Makefile.
In addition, we also use pytest to measure the code coverage:
make cov
The console output will indicate the number and percentage of coverage statements in each file and an overall coverage rate. Although we have not set a required coverage rate, it would be good to achieve more than 85% or 90% for an entire package.


This application is work in progress. The content is there just as a proof of concept. The ultimate goal is to create a library of sign language signs, where anyone can search for signs, browse, view, download or integrate the content in any way they want.
The main page can be used to search for any
kind of sign with free form search. For example you can
search for "bonjour". By default, the
results are shown as an HTML page. The same results can be
retrieved as JSON by
adding the format=json
query parameter or as
Atom / OpenSearch by
adding the format=atom
query parameter.
Each sign has a page where you can see all information about that sign. For example, the "bonjour" has its own page. This can again be viewed as JSON.
A Swagger endpoint is available to browse the available API endpoints and help you get familiar with the kind of information available on this application.


Welcome to Metro
This project was conceived on the 30 Sept 2004.
This site is highly temporary, so please check back soon, real soon.
Som initial resources;
Metro Home |
This project was conceived on the 30 Sept 2004.
This site is highly temporary, so please check back soon, real soon.
Som initial resources;


Please enter society name
Please select block manager
Please enter number of storeys
Please enter number of flats
Please enter address
Please parking availability
Please enter parking area.


Creating a Facebook App
In order to use the Facebook Connect module (FBC), you'll need to create a Facebook App on the Facebook site. The app will allow your site and Facebook to connect to each other. Facebook adjusts/changes their setup process very often, so this guide may not be exact.
- Login to Facebook with your usual Facebook account. Then create a Facebook App for your site on Facebook.
- Click on the Add a New App button.
- You'll be presented with a window that will ask you what kind of app you'd like to create. Select Website from the list.
- You'll then be taken to a new page that asks you to choose an existing App or type the name of a new one you'd like to create. At the top right area of the page, just click on Skip and Create App ID button.
- In the window that pops up, fill out the form and click Create App ID button.
- Facebook will likely load a CAPTCHA for you to solve. Then click Continue.
- You'll then be presented with an overview of your app. Click the Settings button on the navigation menu at the left.
- On the Settings page, fill out the form as necessary. For the App Domains field, enter the domain(s) you will be using FBC on.
- Click the + Add Platform button and select Website from the options. Fill out the Site URL fields with the site address you intend on using Facebook Connect on. Then click Save Changes button.
- Click the App Review button on the navigation menu on the left.
- On the App Review page, it gives you options to submit permission items for review. If you intend on using/requesting any information other than basic profile info, the users' email address and friends list, you'll need to work through this form. For example, if you wish to allow users to publish content such as EE comments to the users' Facebook profile (publish_actions), then you'll need to request permission from Facebook here. This is also the page where you can set your app to LIVE.
- Once you're done (or if you do not need to request any additional permissions), at the top of the page, click on the large radio option to make your app live.
- Go back to the main page by clicking the Dashboard button on the navigation menu on the left.
- Ensure that the status of the app is live (should see a green live circle).
- Take note of the App ID and App Secret code that Facebook has generated for you, as they need to be entered into your Preferences tab of the FBC control panel area. Leave this page open while you go to your EE control panel.
- In your ExpressionEngine control panel, go to the Preferences tab in the Facebook Connect module CP area:
- copy the App ID value into the Facebook App ID field.
- copy the App Secret value into the Facebook App Secret field.
- The rest of the settings for the Facebook app (on the Facebook page) are not important to the Facebook Connect module, but you can fill out some of them if you wish.


Load timeline example ...
Load graph example ...
type: xx
Debug ...
Parse && render ..
type: timeline css: - class: theClass data: "background: red" options: start: 2018-05-10 end: 2018-05-25 groups: - id: g1 content: Group1 - id: g2 content: Group2 items: - content: Hello here start: 2018-05-20 group: g1 className: theClass - content: EVENT
xx
start: 2018-05-15T13:30 group: g2 details: This is message - content: Range start: 2018-05-12 end: 2018-05-22 type: background group: g2 - content: Range2 start: 2018-05-10 end: 2018-05-15 type: background group: g1 - content: range3 start: 2018-05-09T19:20 end: 2018-05-12T01:44 group: g2
type: graph options: edges: { width: 2 } nodes: - id: n1 label: node1 group: g1 class: theClass - id: n2 label: node2 group: g1 - id: n3 label: node2 group: g2 shape: triangle edges: - { from: n1, to: n2 } - { from: n1, to: n3 } - { from: n3, to: n2 }


Game of Life
2014
This is a clone of John Conway’s Game of Life, made in java from scratch.
This is a very basic implementation, with its features including: the ability to play and pause the simulation, control the speed of the simulation, and a few presets of interesting patterns. Trying to avoid swing, I implemented my own buttons, and rendered the entire game using java.awt.
This was a school project for Computer Science 20 made in around a month of in-school time. Overall I’m pretty proud of how it turned out, given the short time frame, and my limited knowledge at the time.
You can download the game here
The source code can be found on GitHub.


Did Xbox Just Tease the Project Scarlett Release Date?
- Xbox publishes tweet celebrating the launch anniversary of the Xbox 360 and Xbox One.
- The date of Nov. 22 is a “big deal” for the company.
- Reading between the lines – is Project Scarlett arriving on Nov. 22, 2020?
Here’s a bit of light weekend speculation for you. Microsoft’s Xbox team may have given us the biggest hint yet about the launch date of the next-generation Project Scarlett – Nov. 22, 2020.
The official Xbox Twitter handle authored a tweet late yesterday to celebrate the anniversary of both the Xbox 360 and Xbox One consoles. These were released fourteen and six years ago yesterday, respectively.
Will Project Scarlett Launch on Nov. 22 Next Year?
The tweet emphasizes that the date of Nov. 22 is a “big deal” for the company, which leads us to speculate that Microsoft could stick to the established pattern of dropping new consoles on that date.
The official stance from Xbox is that Project Scarlett will land during the 2020 holiday season. Nov. 22 falls smack dab into the middle of that window, further adding weight to the notion that yesterday’s tweet was a not so subtle hint.
It’s worth saying this isn’t an explicit confirmation, but there’s a sense Microsoft wants us to read between the lines. The tweet isn’t penned in the past tense, but in the present, implying the date is currently a “big deal” because of Project Scarlett.
Jumping the Gun on Xbox’s Biggest Day
We’ll admit that anticipation may have gotten the better of us with all this. We can’t discount that the tweet is what it appears to be – a celebration of previous generational iterations of the console. In that case, a happy anniversary to Xbox.
Either way, the 12 months between now and the 2020 holiday season will invariably provide a firm answer to the question of when Project Scarlett will arrive. We’ll also finally get a proper name and a firm price point.
This article was edited by Josiah Wilmoth.


--- layout: post status: publish published: true title: Martyn Lovell on the Secure CRT author: display_name: Tomas Restrepo login: tomasr email<EMAIL_ADDRESS>url: http://winterdom.com/ author_login: tomasr author_email<EMAIL_ADDRESS>author_url: http://winterdom.com/ wordpress_id: 52 wordpress_url: http://winterdom.com/2006/04/martynlovellonthesecurecrt date: '2006-04-28 09:13:48 +0000' date_gmt: '2006-04-28 09:13:48 +0000' categories: - C++ tags: [] comments: [] ---
There's a video posted over on Channel
9 featuring Martyn Lovell
from the Visual C++ team talking about the Secure CRT. For
those of you still using C++ this might be interesting...


Missions is the first app built to showcase the DAV ecosystem.
It connects users looking to ship packages with autonomous drones. Users request drone services, drones bid for those services, and trustless cooperation is enabled by using the blockchain.
Current Status: Integration with the first drone partner (Copter Express) is underway.
Go to Missions App >> Visit our Github repository >>Current Status: Integration with the first drone partner (Copter Express) is underway.
Go to Missions App >> Visit our Github repository >>DAV connects drones and charging stations on an open network where they can buy and sell charging services using DAV tokens.
Current Status: A DAV Alliance member is currently deploying a network of charging stations in northern Italy. These stations will offer charging services through the DAV network in exchange for DAV tokens.
View Drone Charging Protocol >>DAV connects drones and service providers allowing them to buy and sell flight planning services on the DAV network, using DAV tokens.
Drones pass the waypoints of their planned trip, and the route planner bids to offer a service in exchange for DAV tokens. Once a mission has been awarded, the service provider returns a list of coordinates to fly through, so that the drone can reach its destination safely. This flight plan takes into consideration environmental, topographical, and regulatory considerations.
Current Status: An integration with a DAV Alliance member is in the final stages, so that the service can be offered in Nevada, USA starting May 2018.
View Route Planning Protocol >>Our Command Line Interface (CLI) tool was built to make developing applications and services that interact with DAV a much more pleasant experience. It allows developers to easily run a local testnet containing DAV contracts, generate identities secured by private and public keys and register them on the blockchain. This allows anyone to easily scaffold new projects or modify an existing one to interact with DAV, and more.
Current Status: Fully functioning testnet and Identity generation already used by Foundation projects. Work on connecting the registration functionality with the identity smart contract is in progress.
Visit our Github repository >>Our Developer Portal incorporates API documentation, communication protocols, and instructions for running our command line interface, local testnet, and block explorer.
Current Status: First communication protocols written. Preparing documentation for other developer tools is in process.
Visit our Developer Portal >>Our block explorer allows users to explore local Ethereum testnets. This eases development and debugging for developers building apps and services on top of DAV.
Current Status: Work is underway to package the block explorer enabling it to launch automatically from the DAV CLI Tools.
Visit our Github repository >>Mission Control serves as the discovery and communication layer that connects and keeps track of vehicles, users and services.
Current Status: Fully working for running simulated environments with drone deliveries. Currently being expanded to support the vehicles of our first partners.
Go to Missions App >> Visit our Github repository >>DAV and the California Maritime University are developing an autonomous boat called n3m0 (pronounced "Nemo"). n3m0 will receive and complete photography missions for students and be paid in DAV tokens. When n3m0 requires charging, it will pay DAV tokens to students in exchange for charging services. n3mo will demonstrate true autonomy by earning money and spending money to take care of its own needs; all in service of taking oceanographic measurements for the University.
Current Status: Boat is ready. Work on the onboard computer and the updates to Mission Control and Missions is in progress.
Visit our Github repository >>DAV and Husarion (a robotics prototyping platform) are developing a POC involving an autonomous robotic rover that will perform drone search and rescue missions. The rover will bid for missions to locate drones that have lost contact with their owners, go to their last known location, and then using its onboard lidar and computer vision find them and send back their exact coordinates.
Current Status: ROSBot’s computer vision algorithms are being updated to support identifying drones.
Learn more about ROSBot >>


Finding similar strings within large sets of strings is a problem many people run into. In a previous blog Super Fast String Matching I’ve explained a process of finding similar...
In the beginning there was spam. Cheap, unpersonalised, mass-sent junk mail, easily defeated by simple Bayesian Filters. Over the years spammers improved and an arms race between spammers and spam...
Traditional approaches to string matching such as the Jaro-Winkler or Levenshtein distance measure are too slow for large datasets. Using TF-IDF with N-Grams as terms to find similar strings transforms...
After moving to New York from the Netherlands I was relieved to find out that biking in Manhattan is actually pretty do-able. It’s not really as common as it is...
PySpark Dataframe Distribution Explorer I found myself using some half baked, quickly written functions to do data exploration in PySpark, every time using a similar but modified version of the...
I’m a bit later dot N L ikbenwatlater.nl (I’m a bit later dot N L) is a site I created to notify you when your train is delayed or cancelled....


--- title: Israel shot 002 date: 2004-01-03T00:00:00.000Z filepathOriginal: photos/IMG0002.jpg filepathThumbnail: photos/IMG0002.thumbnail.jpg filepathPreview: photos/IMG0002.preview.jpg ---
All of Academy 2 in the Jewish quarter. Very back: Moneypenny, Shtern. Back: Nimrod (in the teapot pose), Kos, Alana, Asher, Dane, Nim, Lani, Semii. Middle: Zeeks, Chad, Gemma, Emma, Baz, Nat?, Yoni, Ari, Jason. Front: Romy, Monica, Lisa, Michal, Marissa, Me, Lanzer.


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object com.mcc.ul.Status
public class Status
This class returns the status of a DAQ operation when called with getStatus().
The status reported will be associated with the subsystem used to instantiate
the class, for example (AiDevice
or
DioDevice
).
| Field Summary | |
|---|---|
int |
currentCount
The number of samples per channel that have been transferred. |
int |
currentIndex
The current sample index. |
int |
currentStatus
The status of the subsystem operation associated with the current instance as either Status.RUNNING or Status.IDLE. |
ErrorInfo |
errorInfo
ErrorInfo object that indicates the status of the operation. |
static int |
IDLE
A background process is not currently executing. |
static int |
RUNNING
A background process is currently executing. |
| Constructor Summary | |
|---|---|
Status()
Returns the operation status. |
| Method Summary |
|---|
| Methods inherited from class java.lang.Object |
|---|
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Field Detail |
|---|
public static final int IDLE
public static final int RUNNING
public int currentStatus
public int currentIndex
public int currentCount
public ErrorInfo errorInfo
ErrorInfo
object that indicates the status of the operation.
| Constructor Detail |
|---|
public Status()
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Aidan Beaumont
Hi, I'm Aidan. A 22-year-old medical student. This is a work-in-progress. Find me on LinkedIn.


A perfect number is a number for which the sum of its proper divisors is exactly equal to the number. For example, the sum of the proper divisors of 28 would be 1 + 2 + 4 + 7 + 14 = 28, which means that 28 is a perfect number.
A number n is called deficient if the sum of its proper divisors is less than n and it is called abundant if this sum exceeds n.
As 12 is the smallest abundant number, 1 + 2 + 3 + 4 + 6 = 16, the smallest number that can be written as the sum of two abundant numbers is 24. By mathematical analysis, it can be shown that all integers greater than 28123 can be written as the sum of two abundant numbers. However, this upper limit cannot be reduced any further by analysis even though it is known that the greatest number that cannot be expressed as the sum of two abundant numbers is less than this limit.
Find the sum of all the positive integers which cannot be written as the sum of two abundant numbers.
Given an upper bound: 28123，we could
all the positive integers which can be written as the sum of two abundant numbers
from itertools import combinations_with_replacement
def get_divisors(n):
divisors = [1]
d = 2
while pow(d, 2) < n:
if n % d == 0:
divisors.extend([d, n // d])
d += 1
if pow(d, 2) == n:
divisors.append(d)
return divisors
get_divisors(1)
get_divisors(12)
def get_abundant_numbers():
n = 1
while n <= 28123:
if sum(get_divisors(n)) > n:
yield n
n += 1
all_abundant_numbers = list(get_abundant_numbers())
print(all_abundant_numbers[:10])
print(all_abundant_numbers[-10:])
len(all_abundant_numbers)
def solve():
combi_abundant_number = combinations_with_replacement(all_abundant_numbers, 2)
sum_of_two_abundant_number = set(map(lambda c: c[0] + c[1], combi_abundant_number))
sum_of_two_abundant_number_le28123 = filter(lambda s: s <= 28123, sum_of_two_abundant_number)
return sum(range(28124)) - sum(sum_of_two_abundant_number_le28123)
solve()


what I would do in this case is manually replace the seed IP of CFEKBET1 in assetchains.json with 1 of these:
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",
"addr": "<IP_ADDRESS>:55453",


Support Literacy
Personalize a Lit2Go ePub Dedication Page
Thank you for your interest in pledging a gift to the USF College of Education Lit2Go Project. The finished ePub including your personalized dedication page will be available for public download from the Lit2Go website and from USF on iTunes U. After you submit this request, you will proceed to the USF Foundation Lit2Go page to finalize your gift. The ePub will not be created until after your gift is finalized.
In order to create your personalized dedication page, please provide the following information:
For more information about supporting the Lit2Go Programs and our epubs please contact: Gigi Laird at .
The donor’s dedication page shall appear with the EPub audio book for a period of time coextensive with the time USF shall offer the Lit2Go program. The content of the dedication page shall be subject to approval of USF.


In order to make sure that web request ends up in the correct handler function a router is often used. 'routr' is a package implementing a simple but powerful routing functionality for R based servers. It is a fully functional 'fiery' plugin, but can also be used with other 'httpuv' based servers.
| Version: | 0.3.0 |
| Imports: | R6, httpuv, assertthat, uuid, utils, reqres, stringi, tools, digest |
| Suggests: | testthat, covr, fiery |
| Published: | 2017-10-26 |
| Author: | Thomas Lin Pedersen [aut, cre] |
| Maintainer: | Thomas Lin Pedersen <thomasp85 at gmail.com> |
| BugReports: | https://github.com/thomasp85/routr/issues |
| License: | MIT + file LICENSE |
| URL: | https://github.com/thomasp85/routr#routr |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| In views: | WebTechnologies |
| CRAN checks: | routr results |
| Reference manual: | routr.pdf |
| Package source: | routr_0.3.0.tar.gz |
| Windows binaries: | r-devel: routr_0.3.0.zip, r-release: routr_0.3.0.zip, r-oldrel: routr_0.3.0.zip |
| OS X binaries: | r-release: routr_0.3.0.tgz, r-oldrel: routr_0.3.0.tgz |
| Old sources: | routr archive |
Please use the canonical form https://CRAN.R-project.org/package=routr to link to this page.


Everything started when Zebulon discovered that he had a doppelgänger who was a serious baseball aficionado .


The auto keyword deducts the type of your variable. For example, 'auto x = 4;' is equal to 'int x = 4;'
Very important: always initialize the value of the auto variable. If you don't, you will get a compiler error.
Download exampleThe auto keyword deducts the type of your variable. For example, 'auto x = 4;' is equal to 'int x = 4;'
Very important: always initialize the value of the auto variable. If you don't, you will get a compiler error.
Download example


McLaren Elva Will Still Be Street Legal Without A Windshield
The windshield will be required in certain states but it doesn't look as special.
by Jared RosenholtzMcLaren just pulled the wraps off its latest Ultimate Series hypercar, the Elva. Powered by a twin-turbo V8 producing 803 horsepower and 590 lb-ft of torque, the Elva should be even faster than the previous Ultimate Series car, the Senna, due to its lightweight construction. McLaren is estimating a 0-62 mph time of under three seconds and no matter what the final top speed ends up being, it should feel pretty mad doing it without a windshield or roof (depending on where you live).
Other recent hypercars without a windshield include the Ferrari SP1 and SP2, which are not street legal in the United States due to safety regulations. But unlike the two Ferraris, McLaren will offer the Elva with an optional windshield and the company says the car has been homologated for all major markets. A McLaren spokesperson has told CarBuzz that you can order the car without a windshield and "the laws vary depending on the state."
All of the initial press photos of the Elva showed the car without a windshield but now the UK automaker has released a single image (pictured above) of what it will look like with the optional windshield in place. McLaren tells us the windshield will be "available at no cost" and it will "make some tweaks to the aero" to accommodate the new piece of glass.
Straight from the photo, we can already see the scoop in the hood will be deleted with the windshield in place. The Elva's Active Air Management System is designed to direct the air through the nose out of the vent on the clamshell hood and over the cockpit. Perhaps the glass windshield renders this system irrelevant, which is why it no longer has the vent on the hood.
You Might Also Like
Depending on where you live in the US, you may not have a choice of whether or not you can order the Evla without a windshield. But if you do live in a state or country that does allow it, we highly suggest ordering your car as McLaren initially intended. The windshield car is still a beautiful piece of machinery but part of the "wow factor" is taken away. If you can, opt for the car without a windshield and get a nice racing helmet painted to match your $1.69 million hypercar.


Arduino is an open-source hardware and software company, project and user community that designs and manufactures single-board microcontrollers and microcontroller kits for building digital devices and interactive objects that can sense and control both physically and digitally. Its products are licensed under the GNU Lesser General Public License (LGPL) or the GNU General Public License (GPL),[1] permitting the manufacture of Arduino boards and software distribution by anyone.
Arduino boards are available commercially in preassembled form or as do-it-yourself (DIY) kits.
Arduino board designs use a variety of microprocessors and controllers. The boards are equipped with sets of digital and analog input/output (I/O) pins that may be interfaced to various expansion boards or breadboards (shields) and other circuits.
The boards feature serial communications interfaces, including Universal Serial Bus (USB) on some models, which are also used for loading programs from personal computers. The microcontrollers are typically programmed using a dialect of features from the programming languages C and C++. In addition to using traditional compiler toolchains, the Arduino project provides an integrated development environment (IDE) based on the Processing language project.
The Arduino project started in 2005 as a program for students at the Interaction Design Institute Ivrea in Ivrea, Italy,[2] aiming to provide a low-cost and easy way for novices and professionals to create devices that interact with their environment using sensors and actuators. Common examples of such devices intended for beginner hobbyists include simple robots, thermostats and motion detectors.
The name Arduino comes from a bar in Ivrea, Italy, where some of the founders of the project used to meet. The bar was named after Arduin of Ivrea, who was the margrave of the March of Ivrea and King of Italy from 1002 to 1014
Shields
Arduino and Arduino-compatible boards use printed circuit expansion boards called shields, which plug into the normally supplied Arduino pin headers.Shields can provide motor controls for 3D printing and other applications, Global Positioning System (GPS), Ethernet, liquid crystal display (LCD), or breadboarding (prototyping). Several shields can also be made do it yourself (DIY).
Software
A program for Arduino hardware may be written in any programming language with compilers that produce binary machine code for the target processor. Atmel provides a development environment for their 8-bit AVR and 32-bit ARM Cortex-M based microcontrollers: AVR Studio (older) and Atmel Studio (newer)
IDE
The Arduino integrated development environment (IDE) is a cross-platform application (for Windows, macOS, Linux) that is written in the programming language Java. It originated from the IDE for the languages Processing and Wiring. It includes a code editor with features such as text cutting and pasting, searching and replacing text, automatic indenting, brace matching, and syntax highlighting, and provides simple one-click mechanisms to compile and upload programs to an Arduino board. It also contains a message area, a text console, a toolbar with buttons for common functions and a hierarchy of operation menus. The source code for the IDE is released under the GNU General Public License, version 2.
The Arduino IDE supports the languages C and C++ using special rules of code structuring. The Arduino IDE supplies a software library from the Wiring project, which provides many common input and output procedures. User-written code only requires two basic functions, for starting the sketch and the main program loop, that are compiled and linked with a program stub main() into an executable cyclic executive program with the GNU toolchain, also included with the IDE distribution. The Arduino IDE employs the program avrdude to convert the executable code into a text file in hexadecimal encoding that is loaded into the Arduino board by a loader program in the board's firmware.
Sketch
A sketch is a program written with the Arduino IDE.[57] Sketches are saved on the development computer as text files with the file extension .ino. Arduino Software (IDE) pre-1.0 saved sketches with the extension .pde.
A minimal Arduino C/C++ program consists of only two functions:[58]
setup(): This function is called once when a sketch starts after power-up or reset. It is used to initialize variables, input and output pin modes, and other libraries needed in the sketch.
loop(): After setup() function exits (ends), the loop() function is executed repeatedly in the main program. It controls the board until the board is powered off or is rese


User’s Guide for macOS with Stata and R
Table of Contents
3.2 Navigating StatTag for macOS
3.3 Interacting with the StatTag for macOS interface
5.3 Formatting after insertion
Appendix A. Future Enhancements
Appendix C. Frequently Asked Questions
Let’s Stay in Touch!
The StatTag team appreciates all feedback and would love to hear from you!
In particular:
1. Did you find StatTag easy to use? Was it intuitive?
2. Did StatTag function as expected? Were you able to incorporate your working statistical package code? Were you able to tag documents?
3. Did you encounter any errors? If so, what happened? Can you tell us how to reproduce them?
Please email your feedback to<EMAIL_ADDRESS>You can also reach us on Twitter: http://twitter.com/openstattag
Open and Free
StatTag is open source and provided for free, courtesy of Northwestern University under a grant by the National Institutes of Health.
Visit us on GitHub: http://github.com/stattag
StatTag is user-friendly software that integrates statistical code with document preparation in Microsoft Word. StatTag facilitates reproducible research by connecting Word documents, such as a manuscript, to associated statistical code. Word documents prepared with StatTag are reproducible dynamic documents: statistical results in the document can be automatically updated if either statistical code or data change. In addition, StatTag allows statistical code to be edited directly from Microsoft Word.
StatTag is provided as a free app written in Objective-C. Once installed, StatTag is accessible from the Word toolbar or through the standalone application. This user’s guide covers use of StatTag within a macOS environment for Microsoft Word partnered with:
· Stata (StataCorp. 2015. Stata Statistical Software: Release 14. College Station, TX: StataCorp LP),
· R (R Foundation for Statistical Computing. 2015. R version 3.5.1. Vienna, Austria), and
· R Markdown (R Studio. 2016. R Studio Inc.: R version 3.5.1. Vienna, Austria)
StatTag requires the following
· macOS 10.10 and above
· Microsoft Word 2016
· One or more supported statistical applications
o Stata 13 and above
o R
o R Markdown (R Studio, R)
Note: StatTag should work with Microsoft Word 2011, but for this release we do not supply a toolbar for more user-friendly integration.
1. Download the StatTag software file at http://www.stattag.org
2. Install the software by simply dragging and dropping the program in your Applications directory.
3. Enable the StatTag Toolbar for Word
(1) Launch StatTag (StatTag will automatically launch Microsoft Word if it is not already running)
(2) On first launch, StatTag should prompt you to install a Word toolbar
(3) You will need to close and restart Word in order for the Word toolbar to activate
Note: If you should wish to remove or reinstall the toolbar for Word, you can do so from within StatTag via the “StatTag” menu’s “Install Word Toolbar” and “Remove Word Toolbar” options.
StatTag will link any code file written for supported statistical applications (Stata (.do), R (.R) R Markdown (.Rmd)) with your Word document, run the code file from Word, and insert any tagged results.
There are three main steps to using StatTag:
1. Link code file(s). Connect a Word document to files containing statistical code (i.e. .do or .R file).
2. Create tags. Annotate the code files to tag results, tables, or figures that are of interest.
3. Insert tags. Instruct StatTag where to insert those results within the Word document itself.
Note: We recommend that you begin with a code file that already contains your working statistical code and generates the results of interest. With StatTag, it is possible to write your statistical code directly from Word, but not as convenient as writing your code files in the statistical program’s editor.
Note: This guide uses example code files to explain the use of StatTag. The example code files are available from https://github.com/StatTag/Simple-Code-Examples, along with raw data and a Word document ready for tags to be embedded. To follow along with the User Guide, open the Word document.
A Word document represents the “hub” for your team’s document authoring. Word provides the document formatting and editing tools.
A Code File is text file with commands that are intended to run in any of the supported statistical applications (currently Stata, R, R Markdown, and possibly Matlab or other programs in future releases)). A code file is the source file that your project or study uses to compute findings from data sets. With StatTag, code files are “linked” to Microsoft Word documents so that they can be imported and used. The code files are read so that you can identify sections that produce output that you wish to embed in Word.
A Tag is a unit of statistical output from your Code File that you would like to treat as a unique, reproducible data element. Tags in your code file(s) identify numbers, tables, figures, or verbatim output (raw output from the statistical program console) that you would like to embed in your Word document.
A tag is defined by three components, which make up the “identity” for a tag:
· Code File: The source statistical code file where the tag is defined
· Tag name: The unique, user-friendly name for a tag
· Tag format: The combination of attributes that define how a tag’s output should be formatted within a Microsoft Word document
StatTag for macOS performs the same functions as StatTag for Windows, but with a user interface more consistent with macOS. There are fewer buttons, but all of StatTag’s core capabilities.
We suggest installing the StatTag toolbar for Microsoft Word. It makes interaction with StatTag easier and more reliable. The StatTag toolbar has two groups of buttons which provide quick access to key functions
|
|
Code Files |
Opens the Code Files Manager. See “Code Files Manager” below in Section 3.3. |
|
Tags |
Opens the Tag Manager. See “Tag Manager” below in Section 3.3. |
|
|
|
View Tag |
After selecting a Tag, clicking on this icon will open the Tag definition editor. See “Tag Editor” below in Section 3.3. |
|
Settings |
Opens the Settings window. See “Settings” below. |
|
|
About |
Opens the About window. See “About” below. |
|
|
Help |
Opens StatTag’s help documentation. See “Help” below. |
The Settings window controls aspects of StatTag’s operation.
This button opens an interface to enable logging which controls generation of a log file that can be used for troubleshooting. This is disabled by default, but if you encounter errors and would like to request assistance please do the following: (1) enable the debug file, by checking the box, which will write a plain text file to your computer; (2) run your program to generate the errors, and; (3) send the debug file to<EMAIL_ADDRESS>The About icon will open a window containing the version number of StatTag that you are using, and information regarding citation, usage, and licenses related to StatTag.
The Help icon will open the User Guide from within Word. If you need additional help or support, email<EMAIL_ADDRESS>or visit the StatTag website at http://sites.northwestern.edu/stattag/ to interact with the user community.
Within the StatTag application, the Help menu has two options.
The core content from this document can be found under the “Help” menu. It provides an overview of StatTag’s key concepts and the basic steps to get started.
StatTag provides sample code files for several statistical applications as well as sample Microsoft Word documents to demonstrate their use. The samples are stored online and distributed via GitHub (https://github.com/StatTag/Simple-Code-Examples).
Users can download and extract these sample files from directly within StatTag.
1. Ensure your computer is connected to the Internet.
2. Select “Download Latest StatTag Samples” from the “Help” menu.
3. Review the location where the samples will be downloaded. By default this is your “Downloads” directory. You may change this location to any folder you can access.
4. Click “Install Samples”
In addition to the Word Toolbar, StatTag installs as an independent application, with its own interface. The interface organizes four panels.
|
Word Document Browser |
Displays a list of documents currently open in Microsoft Word. |
|
|
|
|
Tag Summary Dashboard |
Provides an overview of each Word document’s tags. |
|
|
|
|
Code Files Manager |
Lists the code files associated with your active Word document. |
|
|
|
|
Tag Manager |
An interface to insert tags, work with existing tags, and remove tags from the active Word document. |
All Microsoft Word documents currently open on your computer will be displayed here. Clicking on a Word document will activate it in StatTag, loading all code files and associated tag information in the other panels.
This panel will show summary information for any tags in the active Word document. It will display any of three options, depending on what is in your document:
· “All Tags” – A count of the active tags available from code files linked to your Word document. Clicking on “All Tags” will open a list of all Tags currently available for use in your Code Files.
· “Unlinked Tags” – Tags which are used in your Word document, but which are not found in any of the linked code files. Clicking on “Unlinked Tags” will open a list of the tags which are in your Word document, but cannot be found in your project’s accessible Code Files.
· “Duplicate Tags” – Any tag names that are reused within the same code file. Clicking on “Duplicate Tags” will open a list of Tag names which are duplicated either within or across your Code Files. See “Duplicate Tags” below.
· “Overlapping Tags” - Tags can overlap if the code is edited outside of StatTag and a tag becomes embedded within another tag.
The Code Files function enables linking one or more code files with your Word document. The first step to using StatTag is to connect your Word document with your statistical code. Note that it is possible to connect multiple code files to one Word document, and you may use code files from Stata, R, and/or R Markdown in a single document. This panel will show any code files currently linked to you active Word document.
You can:
· View a list of code files currently associated with your document
· Attach or remove code files using the macOS-standard (+) and (-)(delete) buttons
· Attach or remove code files by dragging/dropping code files into the StatTag code file list from Finder
Note: You can connect multiple code files to a single Word document.
Clicking on a code file or selecting multiple code files will cause the Tags Manager to display tags associated with the selected code file(s). From the activity panel, tags can be managed (define, add, remove), inserted, and refreshed.
The Tag Manager has the following components:
A. Defined Tags
i. All tags defined in the code file(s) are displayed. Tags are shown for all code files actively selected in the Code Files pane.
B. Add or Remove
i. These functions are used to define new tags (+) or remove tag(s) (-) from the code file(s)
C. Insert and Update
i. These functions are used to insert or refresh selected tags.
The tag editor drives interaction with StatTag. It is where tags are defined within a referenced code file and information is added to enable StatTag to link output to your Microsoft Word document. Selecting the Add (+) button or double clicking on an existing tag will open the Tag Editor.
The Tag Editor has the following components:
A. Code File
i. If you have only 1 code file linked to your Word document, this will be automatically selected in the drop down menu
ii. If you have 2 or more code files linked to your document, use the drop down menu to select the code file you are using to make the new tags.
B. Text editor
i. The statistical code may be edited directly though StatTag. Any changes you make are made to the file itself and are saved once you press the “Save” button.
C. Tag Name
ii. The tag name is the unique name of the result of interest, and should only be used once within each code file to identify a result. StatTag will warn you if you try to use a tag name more than once.
iii. The tag name can contain any string of characters including special characters (with the exception of the pipe, |) and spaces.
D. Result Type
i. This section informs StatTag if the tag will be a value, figure, table, or verbatim output.
ii. More information on tags for tables, figures and verbatim output is provided in Section 4.
E. Format
i. Formatting options are specific to the type of result inserted.
ii. More information on formatting is provided in Section 5.
The Tag Manager will become active when a code file is selected or the “All Tags” option is selected in the Tag Summary panel. Selecting one or more code files will filter the list of displayed tags.
Tags in your code file(s) identify numbers, tables, figures, or verbatim output (i.e. raw output from the statistical program console) that you would like to embed in your Word document. Tags can be inserted through StatTag, using the following instructions, or for the more advanced user, can be directly written into your code files using a text editor of the user’s choice. Tags are specifically formatted text that Stata or R interpret as comments, but that allows StatTag to pull results into Word.
1. Activate the Tag Manager by clicking on a Code File or selecting All Tags
2. Click on the add (+)(⌘+) button.
3. The Tag Editor window opens showing the statistical code.
4. After a tag has been defined, click Save or Save and define another.
Information on adding tags is described in greater detail in Section 4.3.
1. Activate the Tag panel by clicking on a Code File or selecting All Tags
2. Select the tag(s) you wish to remove from the code file by clicking on them once
3. Click on the remove (-)(delete) button.
Tip: To select multiple tags hold the (shift) key while clicking and selecting a range of tags
1. Activate the Tag panel by clicking on a Code File or selecting All Tags
2. Select the tag you wish to modify by double-clicking on the tag to open the Tag Editor
3. Modify the tag settings and select save
1. Select one or more tags in the tag list.
2. Click on the “Insert X Tag Placeholders” button.
3. This action inserts a placeholder for the tag, which consists of the tag name in brackets (e.g. “[my tag name]”) in your Word document. This allows you to insert many tags without ever running the statistical code file.
4. You will see a progress bar while the tags process and, finally, feedback if there were issues.
1. Select one or more tags in the tag list.
2. Click on the “Update X Tag Results” button.
3. This action will run the code file and fills in placeholders (or updates existing tags) within the Word document.
4. You will see a progress bar while the tags process and, finally, feedback if there were issues.
When inserting figure tags, Microsoft Word 2016 will prompt you to allow it to access the related figure graphic. This is by design. Microsoft Word 2016 for macOS uses a security technology known as the “Apple Sandbox.” It is designed to help protect users and prevents applications from arbitrarily accessing files on the user’s computer.
When StatTag asks Microsoft Word 2016 to insert a figure / image, the Apple Sandbox obligates Word to first obtain permission to access the image on user’s computer. Apple’s security system asserts itself as a “stop sign” before allowing Word to proceed.
Word will notify the user of the request and ask that they authorize access to the file:
Once you click on the image and hits the “Select” button, a window will open and the requested file will be presented. You must then click “Grant Access” to allow Word to insert the image.
This is done once per file. After the user has authorized Microsoft Word to access a file, that decision is stored for future use. Subsequent requests to access that file from within Microsoft Word are automatically approved. If a figure is refreshed or another code file references the same file, the no further approval is required.
A Tag is a unit of statistical output from your Code File that you would like to treat as a unique, reproducible data element. Tags in your code file(s) identify numbers, tables, figures, or verbatim output (raw output from the statistical program console) that you would like to embed in your Word document.
A tag is defined by three components, which make up the “identity” for a tag:
· Code File: The source statistical code file where the tag is defined
· Tag name: The unique, user-friendly name for a tag
· Tag format: The combination of attributes that define how a tag’s output should be formatted within a Microsoft Word document
Tag names should be unique within code files and, ideally, unique across the document (although the latter is not required, it’s suggested to avoid potential confusion and so that it’s easier for users to quickly identify tags). Four types of results can be tagged.
|
Type |
|
or |
|
Numeric Values |
display |
Any command that returns a value |
|
Tables |
matrix list |
Any command that returns a data frame, matrix, vector or list |
|
Figures |
graph export |
pdf, win.metafile, png, jpeg, bmp, postscript |
|
Verbatim |
Any Code |
Any Code |
Tip: When using an R Markdown file, the code must be contained within “code chunks”. Inline code is not supported by StatTag. If an R Markdown code file has the same file name and pathway as an R code file, you should rename one or the other.
In order to return results from your statistical analysis to Word, your results must be created and either printed to the results window of your statistical program or to file through one of the above commands, and encapsulated in a tag. Other lines in your statistical code should not be encapsulated by tags, as they may cause errors.
Values are returned to StatTag and then inserted into Word with the display (Stata) command or R commands that return a number. The display command is used in Stata code to print strings or scalar values to the results window. This command will not return data in any other format, such as a matrix or table.
The display command is typically used in Stata code with the return command to retrieve stored results, or with local or global macro variables.
R commands that return a single value (e.g., print) may be used. If the value returned has more than one element (such as a vector), only the first element will be used.
Tables are returned to Word with the matrix list (Stata) command or R commands that return a collection of values.
The matrix list command is used in Stata code to print a matrix to the results window. The matrix list command is typically used after creation of a matrix with the mkmat, matrix define, estout, or estimates table commands.
R commands that return a collection of values (data frame, matrix, vector, or list) can be used as table results by StatTag.
Figures are returned to Word with the graph export (Stata) command or common file format commands other than pdf (R).
The graph export command is used in Stata code to save a graph or figure to file outside of Stata, the location of which is specified by the user. StatTag will retrieve the file to insert into Word. The graph export command expects a pathway and file name to be specified along with the file format, and the replace option to overwrite an existing file as required. The command will export the last graph rendered in Stata.
The win.metafile, png, jpeg, bmp and postscript commands are used by R to save a graph or figure to a file outside of R, the location of which is specified by the user. StatTag will retrieve the file to insert into Word. StatTag cannot currently return a document generated with pdf.
Verbatim results echo any printed output within the statistical program. Inserted output will be formatted text in a text box. The inserted text may be further formatted in Word.
Tagging code as verbatim in Stata will result in the insertion of any output printed to the Stata results screen.
Tagging code as verbatim in R will result in the insertion of any output printed to the R console.
A tag always starts with **>>>ST:Value(Label=" ")and may contain additional information based on the type of tag (number, table, or figure) it identifies. The tag always ends with **<<<. Examples of tags for a numeric value, a table, a figure and verbatim output are listed below.
**>>>ST:Value(Label=" ", Type="")
code
**<<<
**>>>ST:Table(Label="",Type="",AllowInvalid=True,Decimals=0,Thousands=False)
code
**<<<
**>>>ST:Figure(Label="")
code
**<<<
**>>>ST:Verbatim(Label="")
code
**<<<
If tags are made through StatTag, the text (“***>>> …. **<<<”) will be written into your statistical code by the plug-in. The Label, Type and Table parameters are inserted with the opening and closing tags by StatTag. For the more advanced user, you can also directly write tags into your statistical code. If written by hand in the statistical code, you must write both the opening and closing tags, and provide a tag name for each tag.
Note: Tags cannot be nested within each other. A tag should encapsulate exactly one keyword command (i.e. display, matrix list, etc.)
Tags are defined and inserted through the Tag Manager.
To define a tag:
1. Click on the add (+) button in the Tag Manager to open the Tag Editor.
2. Highlight the line of code containing the desired line of code (i.e. for a value: display or R command).
Tip: To highlight, click between the line number and the start of the line of code. Clicking in this margin will highlight the line of code in purple. In the R example below, this location is outlined in red. You can sometimes select multiple lines, but as best practice, select only the line(s) containing the result of interest.
3. If your selection of code does not include a recognized keyword, StatTag will print an error in the bottom right of the text editor. This applies only to SAS and Stata code files.
Tip: If you get a warning that the section of code you have highlighted cannot output to StatTag, double check the instructions in the selection pane. These will tell you what commands you should highlight.
4. Use the formatting window to make any changes to the way in which the result is displayed. By default, the result will be displayed as it is in the statistical program. For example, our selections to display or print() will insert these numbers to the Word document using the default formatting from Stata and R respectively.
5. Click either “Save” or “Save and Define Another”. If “Save” is chosen, the tag will be saved, as will any edits to the statistical code. The Tag editor window will close, and return to the Tag Manager. If “Save and Define Another” is selected, the tag will be saved, as will any edits to the statistical code. The Tag editor window will remain open and all selections will be reset for you to define your next tag.
6. Use the Add (+) icon as often as needed to create tags for all of your statistical results.
Tags are inserted from the Tag Manager. Tags can be inserted more than one time within a document. Tags are always inserted at the location of the cursor, although they can be copied and pasted elsewhere once inserted.
To insert a saved tag:
1. Within the Tag Manager, select the tag of interest by clicking once on it. Clicking twice will open the tag in the Tag Editor window.
2. With the cursor in the Word file where you want the tag inserted, click ‘Insert 1 Selected Tag’. This action inserts a placeholder for the tag, which consists of the tag name in brackets (e.g. “[my tag name]”) in your Word document. This allows you to insert many tags without ever running the statistical code file.
3. Insert as many tags as you wish repeating the steps above.
Tip: Multiple tags can be selected at one time.
4. To fill in the values for the tags, within the Tag Manager, select all the tags you wish to fill in. Click “Update X Selected Tags”. This action executes the code file silently and returns the results within the placeholders in Word.
Tags can be updated at any time from the Tag Manager by selecting them and clicking “Update X Selected Tags”.
Tip: From the Tag Manager, select the peek () to quickly view the code associated with a tag without opening the Tag Editor.
Once saved, all tags will be listed in the Tag Manager. From this dialog box, the user can change how tags are formatted and updated, or can remove them entirely.
To manage tags:
1. Open the Tag Manager
2. All saved tags are depicted in the Tag Manager by their tag name with information about how they have been defined. From this dialog box, new tags can be defined, and existing tags can be edited or removed.
3. To edit a tag, double click on the tag. This opens the statistical code window, showing the highlighted tag. The options for this tag can be edited through the dialog box.
Note: Tag properties can be edited either through the dialog box using the clickable and selectable tag properties options or by editing the tag itself through either the statistical program or a text editor.
4. To remove a tag, select the tag you wish to remove. Then click “Remove 1 Tag”.
Note: Removing tags will delete the tag notation in your statistical code. Removing tags will not delete inserted text, tables or figures from your Word document. However, those results will no longer be tagged. They will not be updated when code is rerun or the document is open.
When a tag is created, its format should be specified accordingly. Options may be selected for either Values or Tables. There are no formatting options for Figures or Verbatim.
Values can be formatted by default (per the exact statistical output), as a number with a specific number of decimal places, as a date/time combination, or as a percentage with a specific number of decimal places. Formatting is selected from the drop down list.
Matrices and tables are inserted to Word through StatTag using different mechanisms depending on the statistical software used. By default, where data are blank or missing, a “.” is returned in the particular cell. This behavior can be changed for either the document (document properties) or the user (user settings) so that the returned value is a missing character or another default character. Tables use field formatting, and text cannot currently be wrapped within a cell.
Currently, if any formatting is specified, the formatting is applied to the entire table. Formatting options include specification of the number of decimal places and inclusion of a comma separator for thousands places, which will be applied to all numerical data in the table.
Once inserted to Word, the dimensions (rows and columns) of a table should not be modified in the statistical program (e.g. removing rows or columns) or in the tag editor, as this can cause errors when updating the results. If you change the dimensions of a table, you should delete the table from Word and insert the tagged table again. However, once a table is inserted, you may manually add rows/columns in Word as long as these rows or columns do not need to contain tagged results. For example, you may add a header row, a footnote row, or a spacer row.
Tip: Data from individual cells in an inserted table can be copied elsewhere within the Word document text, and will retain their linkage to the original data. For example, to include a p-value from a table in the text, copy the result from the table and paste into the text. When the table is updated, the value in the text will be updated as well.
Once inserted, values and tables can be formatted using Word text formatting options, such as changing fonts, bolding, or italicizing. Updating the tags will not affect the applied formatting in Word.
Tags can also be copy and pasted, or cut and pasted to other parts of the text, and will retain their linkage to the statistical code. If your tag is copied or inserted in multiple locations, updates within your statistical code will update every instance of the tag within your text.
Tip: Tags can be deleted from the text. Deleting the tag from the text will not delete the tag syntax within your statistical code. To delete the syntax, use the “Remove tags” option in the Manage Tags dialog box.
If there are any issues with your code or tags, they will be showing in the Tag Summary Dashboard.
There are three troubleshoot options provided: (1) linking unlinked tags, and (2) removing duplicate tags, and (3) removing overlapping tags.
1. Tags can become unlinked if the statistical code is unlinked from the Word document, or if the statistical code is edited outside of StatTag and the notations are modified. For example, code could become unlinked if the code file (.do, .sas or .R) is moved to new location without changing the code file path in StatTag.
2. Tag names can be duplicated within statistical code if the code is edited outside of StatTag and a tag name is inadvertently duplicated.
3. Tags can overlap if the code is edited outside of StatTag and a tag becomes embedded within another tag.
Tags can become “unlinked” if the statistical code is unlinked from the Word document, or if the statistical code is edited outside of StatTag and the StatTag notations are modified. For example, code could become unlinked if the code file (.do, .R, or .Rmd) is moved to new location without changing the code file path in StatTag.
When a tag is “unlinked,” it means that StatTag can no longer connect a field from within the Word document to a tag in a code file. This presents a risk to the veracity of the document. As code files change or other findings within the document are updated, these “unlinked” tags will be frozen in time and no longer kept in sync with other findings. Additionally, unlinked tags preclude the ability to capitalize on one of the central reproducibility features of StatTag – insight into the source of the data element from the published finding. From the StatTag toolbar in Word, readers can click on a field and view the code that was used in its generation.
There are two scenarios that can lead to an Unlinked Tag
1) Inaccessible Code File
a. If a tag was inserted into the Word document, but the related source code file is no longer accessible, the tag is considered “unlinked” as its definition cannot be accessed
2) The tag’s definition is no longer accessible within a Code File
a. If a tag was inserted into the Word document, but has since been removed from a code file (or the tag name removed or changed outside of StatTag), the field in the Word document cannot be linked to a given tag
In order to determine if there are Unlinked Tags in your document, select the “Check Unlinked Tags” option in the tag dashboard. This will start the process of validating your StatTag Word document, including detecting if any of the existing tags are no longer accessible.
StatTag will detect Unlinked Tags and alert users to them within the Tag Dashboard. Users can then take one of a few actions.
· Act on the code file and all related tags
o Link to a Different Code File. Link a missing code file to a new location. This will relink all related tags found in Microsoft Word to the new code file.
o Remove Unlinked Tags from Word Document. Remove all of the Code File’s unlinked tags from the Microsoft Word document. Existing Microsoft Word fields will be updated to reflect a “[REMOVED]” placeholder for easier visual identification.
· Act on an individual tag
o Link to a Different Code File. Identical to the code file action, except limited to this individual tag.
o Remove Unlinked Tag from Word Document. Identical to the code file action, except limited to this individual tag.
StatTag will alert you to inaccessible code files (broken paths). In order to re-link a code file to its updated path you should simply click on the “missing” code file in your code file list. StatTag will provide you the opportunity to re-link to a code file of your choosing. Additionally, you might also choose to remove (-)(delete) the code file then add (+) it back to your document.
StatTag relies on a tag’s code file and name to create a unique identity. If two tags share the same name within the same code file, StatTag cannot differentiate them when communicating between a code file and Microsoft Word. StatTag refers to this name reuse as a “duplicate” tag.
There are two kinds of duplicate tags:
1) Name reused within the same code file.
a. For a single code file “my code file.do” we have
i. A tag named “My Important Finding” (number, linked to lines 1-10)
ii. A tag named “My Important Finding” (date, linked to lines 98-99)
2) Name reused across separate code files.
a. Code file “my code file.do” we have
i. A tag named “An Incredible Result” (number, percent, linked to line 25)
b. Code file “my other code file.do” we have
i. A tag named “An Incredible Result” (number, percent, linked to line 33)
Duplicate tags within the same code file must be changed. Duplicate tags within the same code file will cause an error.
Duplicate tags across two different code files are treated as warnings because they are potentially confusing. It is strongly suggested you change one of the tag names if possible.
Duplicate tags within the same code file will be automatically detected by StatTag and then listed on the Tag Dashboard. Clicking on the “Duplicate Tags” dashboard item will load the details in the main activity panel.
To resolve a duplicate tag:
1) Click on “Duplicate Tags” in the Tag Dashboard
2) The activity panel will display the details of the duplicate tags, grouped by the related code file(s). You can click on the eye icon to “peek” at the code and quickly review the tag.
3) Double-click on one of the tags to open the tag editor
4) Rename the tag in the tag editor and then save
Review the duplicate tags by selecting “Duplicate Tags” in the Tag Dashboard
Do a quick inspection of the tags by “peeking” at an individual tag’s code.
One you have selected a tag you wish to rename, double-click the tag in the list to open the Tag Editor. Provide a new name and save the tag.
StatTag doesn’t allow a tag to be defined within another tag. If this occurs, StatTag cannot determine which lines of code should be run for each tag. StatTag refers to this as “overlapping” tags.
Overlapping tags will be automatically detected by StatTag and then listed on the Tag Dashboard. Clicking on the “Overlapping Tags” dashboard item will load the details in the main activity panel.
To resolve overlapping tags:
1) Click on “Overlapping Tags” in the Tag Dashboard
2) The activity panel will display the details of the overlapping tags, grouped by each set of tags that are overlapping. You can click on the eye icon to “peek” at the code and quickly review the tags.
3) Select the tag you wish to keep from the drop-down list next to the group name
|
Error |
Solution |
|
A tag displays [NO RESULT] instead of a value |
StatTag returns this value when the plug-in does not capture any information from the statistical program. If your tag returns this result, complete these steps: 1. Close the statistical program if it is open. 2. Check to ensure the tag encapsulates a keyword command. 3. Check to ensure the statistical code is running correctly. Run the code in the native software and check for any errors or warnings. 4. Review any files created on disk to ensure they contain the expected output, and they are created each time the code is run. |
|
My document takes a long time to update |
Inserting and updating tables can take a long time due to the number of fields. |
|
Could not communicate with R |
StatTag locates R software through the Registry Key. If your R Software was installed by a third party (e.i. an IT administrator) then the registry key may be located under a different account. |
|
Warning is displayed when a tag is defined |
If a red warning notice is given, you have not highlighted a keyword command in your code. Check to ensure you have selected the right option of Value, Table, or Figure, and you have highlighted a section of code containing the corresponding command. |
|
Looping |
Tags must be standalone, and should not be embedded within a loop. |
|
Embedded Tags |
Tags should not encapsulate other tags. |
|
My tag from R inserts but is blank |
Try encapsulating your R command with the “print” function. For example, summary output from a regression model may not show up as verbatim output with “summary(myModel)” as the tagged code, but “print(summary(myModel))” should work. |
Development of StatTag and this user’s guide was supported, in part, by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number UL1TR001422. The content is solely the responsibility of the developers and does not necessarily represent the official views of the National Institutes of Health.
StatTag was inspired in part by the Stata Automation Report project:
Lo Magno, G.L. (2013). Sar: Automatic generation of statistical reports using Stata and Microsoft Word for Windows. The Stata Journal, 13(1); 39-64.
StatTag makes use of the following open source projects (licenses in Appendix B):
· Scintilla - http://www.scintilla.org/
· CHCSVParser - https://github.com/davedelong/CHCSVParser
· XlsxReaderWriter - https://github.com/renebigot/XlsxReaderWriter
Use of these projects does not imply endorsement of StatTag by the respective project owners, or endorsement of the use of these projects by Northwestern University.
This is a very early test version of StatTag. Some features are incomplete or not yet implemented.
· Word Toolbar (Microsoft Word 2011)
o The toolbar for Word 2011 is not supported
· Logging
o Currently logging minimal information
On macOS it is possible to run both Microsoft Word 2011 and Microsoft Word 2016 at the same time. In this case StatTag will not necessarily know which you intended to use. Both may be installed, but only one should be actively running if you wish to use StatTag.
On the macOS version of StatTag it is not possible to disable access to Microsoft Word while a document is being updated. Should a document be modified or closed while StatTag is inserting or updating tags, undesirable issues may occur. Users should refrain from interacting with the active Microsoft Word document until StatTag is finished inserting or updating tags.
Currently, “native” (non-formatted) dates are not properly interpreted by StatTag. If you wish to use a Stata-based date in StatTag you may format it as a string and tag it as a StatTag “date” tag. StatTag should then be able to properly utilize the date in your Word document.
You may see the macOS “spinning beach ball” due to slow performance when accessing StatTag’s code files or tags from the Microsoft Word toolbar. This will be resolved in subsequent releases.
Currently, launching StatTag will cause Microsoft Word to launch if it is not already running. This will be addressed in subsequent releases.
During tag inserts and updates you will see the screen refresh as StatTag moves from tag to tag to update values. This is due to the way Microsoft Word functions on macOS.
On macOS, when StatTag runs a code file in an external statistical program such as Stata, that external application will launch and come to the foreground of the user’s desktop. This is by design. By default, Apple security policies cause external applications to become visible when asked to do work. When StatTag requests other applications run a code file, those applications must visibly launch.
The MIT License (MIT)
Copyright (c) 2016, Northwestern University, All Rights Reserved
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
License for Scintilla and SciTE
Copyright 1998-2003 by Neil Hodgson<EMAIL_ADDRESS>All Rights Reserved
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.

CHCSVParser
Copyright (c) 2014 Dave DeLong
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The MIT License (MIT)
Copyright (c) 2014 René BIGOT
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
What is StatTag?
StatTag is an open source, free plug-in that integrates document preparation in Microsoft Word with statistical code, results and data. Using StatTag gives you the ability to embed statistical output in Microsoft Word documents, and edit R, R Markdown, SAS, Stata or Python code from within a Word document.
Why use StatTag?
Using StatTag will allow you to modify a dataset or analysis without transcribing and re-copying the results into a manuscript or table.
How is StatTag different than other programs for producing dynamic documents?
StatTag takes the idea of a dynamic document to the next level. Within Word you can:
· Embed statistical outputs such as estimates, tables and figures into a document
· See and edit the code behind output with one click
· Update individual or collective output with one click
How do I use StatTag?
A step-by-step guide for downloading and using StatTag is available in our User’s manual – available for macOS or Windows.
What software is StatTag compatible with?
|
Windows |
|
|
Mac |
|
Where can I get StatTag?
Click here to download the software for free.
Should I cite StatTag?
Yes. Click here for our citation.
Is StatTag free to use?
Yes. StatTag is made available under the MIT License, which allows free use.
Is StatTag open source?
Yes. The source code for StatTag can be found on our GitHub page: https://github.com/stattag
Can I use StatTag with multiple code files?
Yes. StatTag can be used with multiple code files at the same time, and can be used with .R, .Rmd, .sas, .do, and .py files all at once.
What happens if I save a file in a different location?
StatTag saves the pathway of the code file. When the file is moved, StatTag will alert you that the file needs to be re-linked, and will direct you how to do so. Refer to section 6.0 in the Users Guides for macOS or Windows.
Can I see all the Tags in a document?
Yes. Tags are highlighted when you click on them.
Can I edit my statistical code from Word?
Yes. StatTag will open your statistical code within Word in a text editing window. You can make and save changes to the statistical code from within Word. We recommend, however, that you begin with a code file that already contains your working statistical code and generates the results of interest.
I am collaborating with others on a manuscript. Who can do what? Can a collaborator without StatTag open or modify the Word document? If my collaborator works on the document, can I still edit the statistical code?
|
If a person has… |
Then a person can… |
||
|
Review/edit manuscript text |
View code associated with a tag |
Insert or update a tag |
|
|
Microsoft Word |
ü |
û |
û |
|
+StatTag and code |
ü |
ü |
û |
|
+StatTag and code and data |
ü |
ü |
ü |
My research team uses a mix of Mac and Windows machines. Can we all work on the same manuscript?
StatTag works seamlessly across both operating systems, and collaborators using Windows and macOS may pass files back and forth. The user, regardless of OS, will only need to re-link code files to Word documents using the StatTag user interface.
Do tags remain even as new versions of a Word document are being saved?
Yes, tagging carries over to new versions of Word documents. In fact, tags within the document are carried across different saved versions of the document, across operating systems, and across users with or without StatTag installed.
Can we still track changes and merge documents with StatTag?
Yes, results entered by StatTag will work with Microsoft Word’s “Track Changes” feature, even if your collaborators aren’t using StatTag. Any changes to the tags (formatting changes, deleting, updates) will show up as a change in your Word document. If you have multiple documents from collaborators, you can still use Word’s merge feature to consolidate the changes.
What if I rename my files?
StatTag has built in capability for renaming or moving files. The Word document can be renamed as needed without severing connection to the accompanying code file(s). If the code file(s) are renamed or moved, StatTag will detect and facilitate re-mapping to the new code file(s) through the user interface. Refer to section 6.0 in the Users Guides for macOS or Windows.
What about data security (e.g. PII, PHI)?
StatTag does not store a copy of your data or the statistical code.
Can I insert more than one tag at a time?
Yes. From the Tag Manager window press and hold the Shift key to click and select a range of tags.
How does StatTag work with R Markdown?
When using an R Markdown file, code identified for a tag must be contained within a “code chunk.” Inline code is not supported by StatTag. If an R Markdown code file has the same file name and pathway as an R code file, you should rename one or the other.
When I tried to insert a tag, it showed [NO RESULT]. What do I do?
StatTag returns this value when the plug-in does not capture any information from the statistical program. This is likely a problem with the code itself. Refer to section 6.0 in the Users Guides for macOS or Windows.
When I tried to insert a tag, it returned blank data. What do I do?
Run the code in the native software and check to make sure the result is created without errors. Refer to section 6.0 in the Users Guides for macOS or Windows.
Why does my document take a while to update?
Inserting and updating tables can take a long time due to the number of fields.
What about loops?
Tagged code must stand alone, and cannot be embedded within a loop.
I installed StatTag, but I don’t see it in the toolbar. What do I do?
Check in your program files to ensure StatTag is installed. If installed, refer to section 6.0 in the Users Guides for macOS or Windows.
I need help, what should I do?
The user’s guide for macOS and Windows provides step-by-step instructions for using StatTag as well as tips for troubleshooting. Video tutorials on generating and updating tags are also available. If neither of these resources offer an answer to your question, please email the StatTag team for assistance, StatTag@northwestern.edu.


{{announcement?.type}}
{{announcement?.description}}
{{announcement?.from}}
1">
{{'+' + ((announcement?.links?.length)-1 + ' Weblinks')}}
{{'(' +announcement?.attachments[0]?.mimetype + ','}}
{{announcement?.attachments[0]?.size + ')'}}
1" class="marginTop">
{{'+' + ((announcement?.attachments?.length)-1 + ' ' + ' Attachments')}}


Class StringObject
LightnCandy class for Object property access on a string.
public
|
|
public
|
protected
|
$string
|
LightnCandy class for Object property access on a string.
public
|
|
public
|
protected
|
$string
|


This section discusses the various ways that you may contribute to the project. Firstly:
You are now in a position to make a real difference. Even if you don’t feel up to writing code yet, there are a variety of other ways that you can contribute, from reporting issues to testing patches to contributing documentation:
Last but not least, please remember that despite the online nature of the Xcore open source project and the human contact abstraction that results from that fact, it is important to realize that there are real people at the end of all contributions. Treat all other community members as you would expect to be treated. Review the contribution, not the contributor; don’t annoy others, and don’t become easily annoyed yourself.


{% extends "base.html" %} {% block title%}Cost Analysis{% endblock %} {% block content%}
| Node Type | {% for each_instance_type in all_instance_types %}{{each_instance_type}} | {% endfor%}
|---|---|
| Run Analysis | {% for each_instance_type in all_instance_types %}{% if analyzed_instance_types[each_instance_type] %} Analyze {% endif %} | {% endfor%}
| Analysis Status | {% for each_instance_type in all_instance_types %}{% endfor%} |
| Actual Cost ($) | {% for each_instance_type in all_instance_types %}{% endfor%} |
*The actual cost charged by EC2 is by hour
time(min) vs. instance |
cost($) vs. instance |


No more flat and dull websites. I will make the page come to life.
RESPONSIVE
Website will run smoothly regardless of user device.
LAG FREE
A light page with smooth interactions and a user-friendly UI.
Who am I?
I am currently a student at YRGO, studying Web development.
Thus far I've focused on learning HTML, CSS, PHP and Javascript.
Future skills will also inlude C#, Laravel, React and much more.


Note
You are reading the most recent edition of this documentation which content the latest available version.
FitELP Documentation¶
FitELP is a tool specifically designed to perform spectral emission-line fits with multiple gaussian components in echelle or long-slit data. The actual fitting procedure is based on the Non-Linear Least-Square Minimization and Curve-Fitting (LMFIT) package, https://lmfit.github.io/lmfit-py/ (Newville et al. 2014, https://doi.org/10.5281/zenodo.11813).
The Python code was designed for the analysis of the internal kinematics of star-forming regions using echelle data. However, it can be used to model any emission-lines in both in echelle and longslit spectroscopy.
FitELP allows you to:
- Modelling all individual emission-lines profiles with multiple-gaussian components.
- Visualise the individual fit of the emission-lines profiles with/without residuals.
- Perform an kinematic analysis of each target.
- Produces pdf and latex tables with the results for each ion on each gaussian component:
- radial velocities, velocity dispersion, fluxes, emission measure (EM), and global flux, with the corresponding errors.
- Average of radial velocities and velocity dispersion with the corresponding errors.
- H-alpha luminosity and the corresponding Star Formation Rate (SFR) base on Calzetti et al.(2000) equation, abscissa and ordinate values of the BPT-NII diagnostic diagram.
- Visualise the different BPT diagnostic diagrams.
- Produces latex tables with the flux, continuum, equivalent width, with the corresponding errors and for each ion.
Note
The code is currently still in development, and there may be many issues present. Contact the authors for assistance.
Contribute¶
- Issue Tracker: https://github.com/daniel-muthukrishna/FitELP/issues
- Source Code: https://github.com/daniel-muthukrishna/FitELP
Support¶
If you are having issues, please let us know by submitting a GitHub issue at https://github.com/daniel-muthukrishna/FitELP/issues
License¶
The project is licensed under the MIT license.


University of Portsmouth Room Explorer App
Portsmouth Uni
Room
Explorer App
Uni of Portsmouth
Home
Make a booking
Explore the room
Advance search
Student Allowance
Room requirements
Projector
Allowed eating
Toilet in the building
How many people are attending it?
Enter valid number of students
How much demand should it have
Select
Option 1
Option 2
Option 3
Any particular building
Select
Option 1
Option 2
Option 3
Disabled Access