Free alizee america software for linux

Because weather is important to you everyday... weather.com offers you instant local weather conditions, alerts, radar in motion, satellite maps, and forecasts all within your Firefox browser.

1-ClickWeather is a Firefox extension which enables users to quickly view current weather conditions and up to 5 days of forecast information within the browser and allows for instant access to detailed and customized weather content through clickable icons. All weather data in provided by weather.com.

In addition, the extension features color coded severe weather alerts from the National Weather Service and links to unique features available from weather.com.

All of the weather information displayed by 1-ClickWeather relates to a user-selected geographic location. This information includes:

Weather Videos - pre-selected weather video from weather.com. Choices include Top Story, Severe Weather Outlook, European travel forecast, US national forecast or a choice of one of four US regional forecasts.

Radar - animated in-motion Doppler radar image pre-selected by the user from one of nine US regions.

Satellite - satellite map pre-selected by the user for a defined international geographic region. Choices include Europe, Russia, Asia, Middle East, Africa, Canada, Mexico, Central America, and South America.

Quick Launch - up to 16 user-defined quick launch links to unique content on the weather.com website, including local 36-hour forecasts, local 10-day forecasts and links to customized lifestyle content such as Personal PetCasts, Baseball Game Day Forecasts and PollenCasts.

The FlightGear flight simulator project is an open-source, multi-platform, cooperative flight simulator development project. Source code for the entire project is available and licensed under the GNU General Public License.

The goal of the FlightGear project is to create a sophisticated flight simulator framework for use in research or academic environments, for the development and pursuit of other interesting flight simulation ideas, and as an end-user application. We are developing a sophisticated, open simulation framework that can be expanded and improved upon by anyone interested in contributing.

There are many exciting possibilities for an open, free flight sim. We hope that this project will be interesting and useful to many people in many areas.

FlightGear is a free flight simulator project. It is being developed through the gracious contributions of source code and spare time by many talented people from around the globe. Among the many goals of this project are the quest to minimize short cuts and "do things right", the quest to learn and advance knowledge, and the quest to have better toys to play with.

The idea for Flight Gear was born out of a dissatisfaction with current commercial PC flight simulators. A big problem with these simulators is their proprietariness and lack of extensibility. There are so many people across the world with great ideas for enhancing the currently available simulators who have the ability to write code, and who have a desire to learn and contribute. Many people involved in education and research could use a spiffy flight simulator frame work on which to build their own projects; however, commercial simulators do not lend themselves to modification and enhancement. The Flight Gear project is striving to fill these gaps.

There are a wide range of people interested and participating in this project. This is truly a global effort with contributors from just about every continent. Interests range from building a realistic home simulator out old airplane parts, to university research and instructional use, to simply having a viable alternative to commercial PC simulators.

Flight Dynamics Models

With FlightGear it is possible to choose between three primary Flight Dynamics Models. It is possible to add new dynamics models or even interface to external "proprietary" flight dynamics models:

1. JSBSim: JSBSim is a generic, 6DoF flight dynamics model for simulating the motion of flight vehicles. It is written in C++. JSBSim can be run in a standalone mode for batch runs, or it can be the driver for a larger simulation program that includes a visuals subsystem (such as FlightGear.) In both cases, aircraft are modeled in an XML configuration file, where the mass properties, aerodynamic and flight control properties are all defined.

2. YASim: This FDM is an integrated part of FlightGear and uses a different approach than JSBSim by simulating the effect of the airflow on the different parts of an aircraft. The advantage of this approach is that it is possible to perform the simulation based on geometry and mass information combined with more commonly available performance numbers for an aircraft. This allows for quickly constructing a plausibly behaving aircraft that matches published performance numbers without requiring all the traditional aerodynamic test data.

3. UIUC: This FDM is based on LaRCsim originally written by the NASA. UIUC extends the code by allowing aircraft configuration files instead and by adding code for simulation of aircraft under icing conditions.

UIUC (like JSBSim) uses lookup tables to retrieve the component aerodynamic force and moment coefficients for an aircraft... and then uses these coefficients to calculate the sum of the forces and moments acting on the aircraft.

Extensive and Accurate World Scenery Data Base

Over 20,000 real world airports included in the full scenery set.
Correct runway markings and placement, correct runway and approach lighting.
Taxiways available for many larger airports (even including the green center line lights when appropriate.)
Sloping runways (runways change elevation like they usually do in real life.)
Directional airport lighting that smoothly changes intensity as your relative view direction changes.
World scenery fits on 3 DVDs. (Im not sure thats a feature or a problem!) But it means we have pretty detailed coverage of the entire world.
Accurate terrain worldwide, based on the most recently released SRTM terrain data.) 3 arc second resolution (about 90m post spacing) for North and South America, Europe, Asia, Africa, and Australia.
Scenery includes all vmap0 lakes, rivers, roads, railroads, cities, towns, land cover, etc.
Nice scenery night lighting with ground lighting concentrated in urban areas (based on real maps) and headlights visible on major highways. This allows for realistic night VFR flying with the ability to spot towns and cities and follow roads.
Scenery tiles are paged (loaded/unloaded) in a separate thread to minimize the frame rate hit when you need to load new areas.

Accurate and Detailed Sky Model

FlightGear implements extremely accurate time of day modeling with correctly placed sun, moon, stars, and planets for the specified time and date. FlightGear can track the current computer clock time in order to correctly place the sun, moon, stars, etc. in their current and proper place relative to the earth. If its dawn in Sydney right now, its dawn in the sim right now when you locate yourself in virtual Sidney. The sun, moon, stars, and planets all follow their correct courses through the sky. This modeling also correctly takes into account seasonal effects so you have 24 hour days north of the arctic circle in the summer, etc. We also illuminate the correctly placed moon with the correctly placed sun to get the correct phase of the moon for the current time/date, just like in real life.

Flexible and Open Aircraft Modeling System

FlightGear has the ability to model a wide variety of aircraft. Currently you can fly the 1903 Wright Flyer, strange flapping wing "ornithopters", a 747 and A320, various military jets, and several light singles. FlightGear has the ability to model those aircraft and just about everything in between.

FlightGear has extremely smooth and fluid instrument animation that updates at the same rate as your out-the-window view updates (i.e. as fast as your computer can crank, and not artificially limited and chunky like in some sims.)

FlightGear has the infrastructure to allow aircraft designers to build fully animated, fully operational, fully interactive 3d cockpits (which even update and display correctly from external chase plane views.)

FlightGear realistically models real world instrument behavior. Instruments that lag in real life, lag correctly in FlightGear, gyro drift is modeled correctly, the magnetic compass is subject to aircraft body forces -- all those things that make real world flying a challenge.

FlightGear also accurately models many instrument and system failures. If the vacuum system fails, the HSI gyros spin down slowly with a corresponding degradation in response as well as a slowly increasing bias/error.

Moderate Hardware Requirements

The intention of FlightGear is to look nice, but not at the expense of other aspects of a realistic simulator. Our focus is not on competing in the "game" market and not on the ultra-flashy graphic tricks.

The result is a simulator with moderate hardware requirements to run at smooth frame rates. You can be reasonably happy on a $500-1000 (USD) machine (possibly even less if you are careful) and dont necessarily need $3000 (USD) worth of new hardware like you do with the many of the newest games.

That said, the more hardware you throw at FlightGear, the better it looks and runs, so dont feel like you have to chuck your expensive new hardware if you just purchased it. :-)

Internal Properties EXPOSED!

FlightGear allows users and aircraft designers access to a very large number of internal state variables via numerous internal and external access mechanisms. These state variables are organized into a convenient hierarchal "property" tree.

Using the properties tree it is possible to monitor just about any internal state variable in FlightGear. Its possible to remotely control FlightGear from an external script. You can create model animations, sound effects, instrument animations and network protocols for about any situation imaginable just by editing a small number of human readable configuration files. This is a powerful system that makes FlightGear immensely flexible, configurable, and adaptable.

Networking options

A number of networking options allow FlightGear to communicate with other instances of FlightGear, GPS receivers, external flight dynamics modules, external autopilot or control modules, as well as other software such as the Open Glass Cockpit project and the Atlas mapping utility.

A generic input/output option allows for a user defined output protocol to a file, serial port or network client.

A multi player protocol is available for using FlightGear on a local network in a multi aircraft environment, for example to practice formation flight or for tower simulation purposes.

The powerful network options make it possible to synchronize several instances of FlightGear allowing for a multi-display, or even a cave environment. If all instances are running at the same frame rate consistently, it is possible to get extremely good and tight synchronization between displays.

Flight Gear and its source code have intentionally been kept open, available, and free. In doing so, we are able to take advantage of the efforts of tremendously talented people from around the world. Contrast this with the traditional approach of commercial software vendors, who are limited by the collective ability of the people they can hire and pay. Our approach brings its own unique challenges and difficulties, but we are confident (and other similarly structured projects have demonstrated) that in the long run we can outclass the commercial "competition."

Contributing to Flight Gear can be educational and a lot of fun. A long time developer, Curtis Olson, had this to say about working on Flight Gear:

Personally, Flight Gear has been a great learning experience for me. I have been exposed to many new ideas and have learned a tremendous amount of "good stuff" in the process of discussing and implementing various Flight Gear subsystems. If for no other reason, this alone makes it all worth while.

BSFlite is a minimalistic, line-based AIM client for Unix.
Instead of having a full screen console interface, BSFlite employs a command line interface that allows your fingers to do all of the work without needlessly sifting through windows.
BSFlite runs on UNIX (including Linux, all of the BSDs, Solaris, etc.), Zeta (and possibly BeOS), Windows, DOS, Mac OS X, and Plan 9.
Well, minimalistic doesnt necessarily mean sparse. Lets call it, say, nimble. BSFlite supports most standard AIM features, with the notable exceptions of chat rooms and block lists.
For casual day-to-day chat, its perfect, if for nothing else than one important feature: once your fingers learn the commands, it doesnt matter if your brain remembers them or not. Youll be amazed at how efficiently you can juggle conversations with BSFlite. Seriously.
Main features:
- Runs on just about any UNIX machine of any speed
- Uses very few resources, even compared to other console clients
- Very portable codebase with BSD-licensed AIM library for use in your own projects
- Windows port with tiny binary size - put it on a floppy or USB stick and load it up when you need AIM at an Internet cafe or public terminal
- Works great with screen, so you can leave your AIM session logged in when youre not physically at your terminal
- Not affiliated with America Online in any way
Enhancements:
- Several memory leaks and bugs were fixed.
- Better color support and the ability to reconnect were added.
- A man page is now available.

DateTime is a date and time object.

SYNOPSIS

use DateTime;

$dt = DateTime->new( year => 1964,
month => 10,
day => 16,
hour => 16,
minute => 12,
second => 47,
nanosecond => 500000000,
time_zone => Asia/Taipei,
);

$dt = DateTime->from_epoch( epoch => $epoch );
$dt = DateTime->now; # same as ( epoch => time() )

$year = $dt->year;
$month = $dt->month; # 1-12 - also mon

$day = $dt->day; # 1-31 - also day_of_month, mday

$dow = $dt->day_of_week; # 1-7 (Monday is 1) - also dow, wday

$hour = $dt->hour; # 0-23
$minute = $dt->minute; # 0-59 - also min

$second = $dt->second; # 0-61 (leap seconds!) - also sec

$doy = $dt->day_of_year; # 1-366 (leap years) - also doy

$doq = $dt->day_of_quarter; # 1.. - also doq

$qtr = $dt->quarter; # 1-4

# all of the start-at-1 methods above have correponding start-at-0
# methods, such as $dt->day_of_month_0, $dt->month_0 and so on

$ymd = $dt->ymd; # 2002-12-06
$ymd = $dt->ymd(/); # 2002/12/06 - also date

$mdy = $dt->mdy; # 12-06-2002
$mdy = $dt->mdy(/); # 12/06/2002

$dmy = $dt->dmy; # 06-12-2002
$dmy = $dt->dmy(/); # 06/12/2002

$hms = $dt->hms; # 14:02:29
$hms = $dt->hms(!); # 14!02!29 - also time

$is_leap = $dt->is_leap_year;

# these are localizable, see Locales section
$month_name = $dt->month_name; # January, February, ...
$month_abbr = $dt->month_abbr; # Jan, Feb, ...
$day_name = $dt->day_name; # Monday, Tuesday, ...
$day_abbr = $dt->day_abbr; # Mon, Tue, ...

$epoch_time = $dt->epoch;
# may return undef if the datetime is outside the range that is
# representable by your OSs epoch system.

$dt2 = $dt + $duration_object;

$dt3 = $dt - $duration_object;

$duration_object = $dt - $dt2;

$dt->set( year => 1882 );

$dt->set_time_zone( America/Chicago );

$dt->set_formatter( $formatter );

DateTime is a class for the representation of date/time combinations, and is part of the Perl DateTime project. For details on this project please see http://datetime.perl.org/. The DateTime site has a FAQ which may help answer many "how do I do X?" questions. The FAQ is at http://datetime.perl.org/faq.html.

It represents the Gregorian calendar, extended backwards in time before its creation (in 1582). This is sometimes known as the "proleptic Gregorian calendar". In this calendar, the first day of the calendar (the epoch), is the first day of year 1, which corresponds to the date which was (incorrectly) believed to be the birth of Jesus Christ.

The calendar represented does have a year 0, and in that way differs from how dates are often written using "BCE/CE" or "BC/AD".

For infinite datetimes, please see the DateTime::Infinite module.

This is a Perl/Tk frontend to the tv programming database available at http://labs.zap2it.com, and uses the CPAN module XMLTV to do the fetching.
This is a multi-threaded perl application, which will download and display concurrently.
INSTRUCTIONS
1. You need to go to http://labs.zap2it.com and sign up for an account. You need to use the xmltv developer certificate code C< ZYZM-TE5O-SBUT > (Letter O) to register. When registering, I have found it is better to NOT answer anything with a blank or zero. Always give a "true" answer.
After registering, you must set up your configuration, and choose your service provider, and personal channel selection. Write down your given username and password.
Your registration will be good for 3 months, and can be renewed after re-filling out the questionaire.
2. You must install the XMLTV module from http://membled.com/work/apps/xmltv/ It comes with a very nice README file explaining what you need to do. If you have already done Step(1) above, you will need to run your areas grabber script from the xmltv distribution. For North America it is tv_grab_na_dd You must run your grabber script once, to configure and setup your .xmltv directory and configuration....so.... tv_grab_na_dd --configure
Answer the questions, and select UTC as your default time. That way, you download files in UTC time, and the display program will convert it to local time.
After running --configure, you should have file ~/.xmltv/tv_grab_na_dd.conf with your channels and username. To make the downloading of new files run without prompting for a password, put your password in ~/.xmltv/tv_grab_na_dd.conf. Your file should look similar to this:
username: zentara
password: xc78vjk3n4
timezone: UTC
lineup: MI21648:-
channel: 46 AMC
channel: 45 ARTS
channel: 62 BET
3. Run the ztk-tvguide script. If you dont have any XML files downloaded it will prompt you to Download files at the first run. Just click the Download button, and you will be asked "how many days forward?" Today is day 0, so 8 will get you 1 week ahead. If you already have a file for that day, it will not be downloaded again. If you need to redownload it, for some odd reason, just delete it manually from the xml storage location, which is ~/.xmltv/ztk_tvguide/
The display program is multi-threaded, so you can download and browse at the same time. There are 2 display indicators, one for downloading, and one for converting the xml.
Enhancements:
- This release fixes a UTC-to-local time conversion problem.
- The script now relies on xmltvs downloader script (and configuration file) to adjust to local time.
- You may need to edit your xmltv configuration file tv_grab_na_dd.conf to adjust your timezone offset from UTC to local.
- It also fixes a bug which could cause cross-linking of programs across days.

Google::Adwords::AccountService is a Perl module to interact with the Google Adwords AccountService API calls.

SYNOPSIS

use Google::Adwords::AccountService;
use Google::Adwords::AccountInfo;
use Google::Adwords::CoverageType;
use Google::Adwords::EmailPromotionsPreferences;
use Google::Adwords::CreditCard;
use Google::Adwords::Address;

my $service = Google::Adwords::AccountService->new();

# login to the Adwords server
$service->email($email)
->password($password)
->clientEmail($cemail)
->applicationToken($app_token)
->developerToken($dev_token);

# getAccountInfo
my $account = $service->getAccountInfo();
print "currencyCode : " . $account->currencyCode . "n";
print "descriptiveName : " . $account->descriptiveName . "n";

# getClientAccounts
my @emailaccounts = $service->getClientAccounts();
print "getClientAccounts : " . join(|, @emailaccounts) . "n";

# getCreditCard
my $creditcard = $service->getCreditCard();

# setLoginInfo
my $ret_setlogininfo= $service->setLoginInfo(email@example.com, toto);

# setLocalTimezone to brrr ...
my $ret_setlocaltimezone = $service->setLocalTimezone(America/Anchorage);

# setCreditCard
my $cc = Google::Adwords::CreditCard->new
->cardNumber(12345678912346)
->cardType(VISA)
->cardVerificationNumber(123)
->expirationMonth(1)
->expirationYear(2008);

my $addr = Google::Adwords::Address->new
->addressLine1(down the street)
->city(Paris)
->companyName(Up there)
->countryCode(FR)
->emailAddress(me@example.com)
->name(Up there)
->phoneNumber(+33112345678)
->postalCode(75020);

my $ret_setcreditcard = $service->setCreditCard($cc, $addr);

# createAdWordsAccount
my $emailPrefs = Google::Adwords::EmailPromotionsPreferences->new
->marketResearchEnabled(1)
->newsletterEnabled(1)
->promotionsEnabled(0);

my $covType = Google::Adwords::CoverageType->new
->optInContentNetwork(0)
->optInSearchNetwork(1);

my $ret = $service->createAdWordsAccount({
loginEmail => $loginEmail,
password => $password,
languagePreference => $lgPref,
emailPrefs => $emailPrefs,
currencyCode => $curCode,
cardInfo => $creditcard,
contactInfo => $address,
defaultAdsCoverage => $covType,
timeZoneId => $timeZoneId
});

# updateAccountInfo
$account->primaryBusinessCategory(Advertising, Marketing, SEO);
my $ret_updateaccountinfo = $service->updateAccountInfo($account);

This module provides an interface to the Google Adword AccountService API calls.

DateTime::Event::Sunrise is a Perl DateTime extension for computing the sunrise/sunset on a given day.

SYNOPSIS

use DateTime;
use DateTime::Event::Sunrise;

my $dt = DateTime->new( year => 2000,
month => 6,
day => 20,
);

my $sunrise = DateTime::Event::Sunrise ->sunrise (
longitude =>-118,
latitude =>33,
altitude => -0.833,
iteration => 1
);

my $sunset = DateTime::Event::Sunrise ->sunset (
longitude =>-118,
latitude =>33,
altitude => -0.833,
iteration => 1
);

my $tmp_rise = $sunrise->next( $dt );

my $dt2 = DateTime->new( year => 2000,
month => 12,
day => 31,
);

# iterator
my $dt_span = DateTime::Span->new( start =>$dt1, end=>$dt2 );
my $set = $sunrise->intersection($dt_span);
my $iter = $set->iterator;
while ( my $dt = $iter->next ) {
print ,$dt->datetime;
}

# is it day or night?
my $day_set = DateTime::SpanSet->from_sets(
start_set => $sunrise, end_set => $sunset );
print $day_set->contains( $dt ) ? day : night;

my $dt = DateTime->new( year => 2000, month => 6, day => 20, time_zone => America/Los_Angeles, );
my $sunrise = DateTime::Event::Sunrise ->new( longitude =>-118 , latitude => 33, altitude => -0.833, iteration => 1
);

my $tmp = $sunrise->sunrise_sunset_span($dt); print "Sunrise is:" , $tmp->start->datetime , "n"; print "Sunset is:" , $tmp->end->datetime;
my $dt1 = $sunrise->sunrise_datetime( $dt ); print "Sunrise is:" , $dt1->datetime , "n"; my $dt2 = $sunrise->sunset_datetime( $dt ); print "Sunset is:" , $dt2->datetime , "n";