intermediate results
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2122
Ultimate Guitar 0.0.3
Ultimate Guitar is an amaroK script which search guitar tabs in ultimate-guitar.com. more>>
Ultimate Guitar is an amaroK script which search guitar tabs in ultimate-guitar.com. It shows the results within a browser (default: Konqueror).
<<less Download (0.009MB)
Added: 2006-08-01 License: Freeware Price:
1195 downloads
Yahoo::Search::Result 1.5.8
Yahoo::Search::Result is a class representing a single result from a Yahoo! search-engine query. more>>
Yahoo::Search::Result is a class representing a single result (single web page, image, video file, etc) from a Yahoo! search-engine query. (This package is included in, and automatically loaded by, the Yahoo::Search package.)
Package Use ^
You never need to use this package directly -- it is loaded automatically by Yahoo::Search.
Object Creation ^
Result objects are created automatically when a Response object is created (when a Request objects Fetch method is called, either directly, or indirectly via a shortcut such as Yahoo::Search->Query().
<<lessPackage Use ^
You never need to use this package directly -- it is loaded automatically by Yahoo::Search.
Object Creation ^
Result objects are created automatically when a Response object is created (when a Request objects Fetch method is called, either directly, or indirectly via a shortcut such as Yahoo::Search->Query().
Download (0.034MB)
Added: 2006-07-20 License: Perl Artistic License Price:
1194 downloads
Yahoo::Marketing::ForecastKeywordResponse 0.08
Yahoo::Marketing::ForecastKeywordResponse is an object to returns forecasted results for a set of keywords. more>>
Yahoo::Marketing::ForecastKeywordResponse is an object to returns forecasted results for a set of keywords.
SYNOPSIS
See http://ysm.techportal.searchmarketing.yahoo.com/docs/reference/dataObjects.asp for documentation of the various data objects.
new
Creates a new instance
METHODS
get/set methods
customizedResponseByAdGroup
defaultResponseByAdGroup
landscapeByAdGroup
get (read only) methods
<<lessSYNOPSIS
See http://ysm.techportal.searchmarketing.yahoo.com/docs/reference/dataObjects.asp for documentation of the various data objects.
new
Creates a new instance
METHODS
get/set methods
customizedResponseByAdGroup
defaultResponseByAdGroup
landscapeByAdGroup
get (read only) methods
Download (0.066MB)
Added: 2006-12-14 License: Perl Artistic License Price:
1044 downloads
Mail::Message::Head::ResentGroup 2.069
Mail::Message::Head::ResentGroup is a Perl module with header fields tracking message delivery. more>>
Mail::Message::Head::ResentGroup is a Perl module with header fields for tracking message delivery.
INHERITANCE
Mail::Message::Head::ResentGroup
is a Mail::Message::Head::FieldGroup
is a Mail::Reporter
SYNOPSIS
my $rg = Mail::Message::Head::ResentGroup->new(head => $head,
From => me@home.nl, To => You@tux.aq);
$head->addResentGroup($rg);
my $rg = $head->addResentGroup(From => me);
my @from = $rg->From;
my @rgs = $head->resentGroups;
$rg[2]->delete if @rgs > 2;
A resent group is a set of header fields which describe one intermediate step in the message transport. Resent groups have NOTHING to do with user activety; there is no relation to the users sense of creating reply, forward, or bounce messages at all!
<<lessINHERITANCE
Mail::Message::Head::ResentGroup
is a Mail::Message::Head::FieldGroup
is a Mail::Reporter
SYNOPSIS
my $rg = Mail::Message::Head::ResentGroup->new(head => $head,
From => me@home.nl, To => You@tux.aq);
$head->addResentGroup($rg);
my $rg = $head->addResentGroup(From => me);
my @from = $rg->From;
my @rgs = $head->resentGroups;
$rg[2]->delete if @rgs > 2;
A resent group is a set of header fields which describe one intermediate step in the message transport. Resent groups have NOTHING to do with user activety; there is no relation to the users sense of creating reply, forward, or bounce messages at all!
Download (0.57MB)
Added: 2007-02-22 License: Perl Artistic License Price:
974 downloads
Serp EasySurf 1.1.4
Serp EasySurf provides an easy to use extention that makes some modification in search engines result pages. more>>
Serp EasySurf provides an easy to use extention that makes some modification in search engines result pages.
An easy to use extention that makes some modification in search engines result pages (Google, MSN, Yahoo) and makes surfing in search engines easier!. Features: show numeration, add hotkeys, show results per page select, set|remove omitted results...
An easy to use extention that makes some modification in search engines result pages (Google, MSN, Yahoo) and makes surfing in search engines easier!. Features: show numeration, add hotkeys, show results per page select, set|remove omitted results filter.
<<lessAn easy to use extention that makes some modification in search engines result pages (Google, MSN, Yahoo) and makes surfing in search engines easier!. Features: show numeration, add hotkeys, show results per page select, set|remove omitted results...
An easy to use extention that makes some modification in search engines result pages (Google, MSN, Yahoo) and makes surfing in search engines easier!. Features: show numeration, add hotkeys, show results per page select, set|remove omitted results filter.
Download (0.012MB)
Added: 2007-04-04 License: MPL (Mozilla Public License) Price:
945 downloads
Taverna 1.5.1
Taverna is a distributed compute workflow components in Java. more>>
Taverna is a collection of workflow enactment and description components, including a high level language for workflows called Scufl (Simple Conceptual Unified Flow Language), a pure Java object model, parser to populate the model, and a set of views and controllers (including some Swing components to drop into your workflow-enabled applications). In order to actually run workflows you also need the myGrid workflow enactment engine.
Taverna core data models include the object representations of the workflow itself, all entities within the workflow (processors, ports, data links etc) and the model for the data values flowing along data links during a workflow enactment.
Taverna task extensions sit within an enactment engine - in this case FreeFluo - and provide concrete implementations of the abstract tasks specified by Processor objects within the workflow object model. It is these tasks which contain the logic required to contact web services, run local java classes and perform the other actions associated with their Processor entities.
Instances of the task extensions are created when a workflow and associated input objects are submitted through the Workflow Submission Interface. This interface may be an in process java method call or may be invoked across some transport such as SOAP in the case of a remote service based enactment engine. FreeFluo is capable of acting in both modes, the Taverna workbench incorporates an instance of the FreeFluo enactor to provide basic enactment services to users without a central workflow engine server.
The graphical user interface classes sit on a client machine and allow interaction with the core data model classes as well as with running workflow instance objects within an enactment engine. This allows workflow construction, editing and visualisation as well as enactor management and data browsing across the results and intermediate values within a workflow instance.
The storage interface is a plugable framework that allows external data and metadata stores to observe events within the workflow enactment service and collection information about those events. This could include a provenance collection plugin which watches the workflow enactment and records metadata about it in RDF form, or a storage plugin which streams results back to a relation database, possibly a Life Science Identifier (LSID) authority, as the enactment runs.
The LSID authority interface is a read only access point to data stored within a data store, and can potentially be used by the Taverna graphical user interface components to fetch results of previous workflows and make use of them as inputs to successive ones.
<<lessTaverna core data models include the object representations of the workflow itself, all entities within the workflow (processors, ports, data links etc) and the model for the data values flowing along data links during a workflow enactment.
Taverna task extensions sit within an enactment engine - in this case FreeFluo - and provide concrete implementations of the abstract tasks specified by Processor objects within the workflow object model. It is these tasks which contain the logic required to contact web services, run local java classes and perform the other actions associated with their Processor entities.
Instances of the task extensions are created when a workflow and associated input objects are submitted through the Workflow Submission Interface. This interface may be an in process java method call or may be invoked across some transport such as SOAP in the case of a remote service based enactment engine. FreeFluo is capable of acting in both modes, the Taverna workbench incorporates an instance of the FreeFluo enactor to provide basic enactment services to users without a central workflow engine server.
The graphical user interface classes sit on a client machine and allow interaction with the core data model classes as well as with running workflow instance objects within an enactment engine. This allows workflow construction, editing and visualisation as well as enactor management and data browsing across the results and intermediate values within a workflow instance.
The storage interface is a plugable framework that allows external data and metadata stores to observe events within the workflow enactment service and collection information about those events. This could include a provenance collection plugin which watches the workflow enactment and records metadata about it in RDF form, or a storage plugin which streams results back to a relation database, possibly a Life Science Identifier (LSID) authority, as the enactment runs.
The LSID authority interface is a read only access point to data stored within a data store, and can potentially be used by the Taverna graphical user interface components to fetch results of previous workflows and make use of them as inputs to successive ones.
Download (1.2MB)
Added: 2007-06-04 License: LGPL (GNU Lesser General Public License) Price:
911 downloads
GNU make 3.81
GNU make is a tool which controls the generation of executables and other non-source files of a program. more>>
GNU make is a tool which controls the generation of executables and other non-source files of a program from the programs source files.
Make gets its knowledge of how to build your program from a file called the makefile, which lists each of the non-source files and how to compute it from other files. When you write a program, you should write a makefile for it, so that it is possible to use Make to build and install the program.
Capabilities of Make
- Make enables the end user to build and install your package without knowing the details of how that is done -- because these details are recorded in the makefile that you supply.
- Make figures out automatically which files it needs to update, based on which source files have changed. It also automatically determines the proper order for updating files, in case one non-source file depends on another non-source file.
As a result, if you change a few source files and then run Make, it does not need to recompile all of your program. It updates only those non-source files that depend directly or indirectly on the source files that you changed.
- Make is not limited to any particular language. For each non-source file in the program, the makefile specifies the shell commands to compute it. These shell commands can run a compiler to produce an object file, the linker to produce an executable, ar to update a library, or TeX or Makeinfo to format documentation.
- Make is not limited to building a package. You can also use Make to control installing or deinstalling a package, generate tags tables for it, or anything else you want to do often enough to make it worth while writing down how to do it.
Make Rules and Targets
A rule in the makefile tells Make how to execute a series of commands in order to build a target file from source files. It also specifies a list of dependencies of the target file. This list should include all files (whether source files or other targets) which are used as inputs to the commands in the rule.
Here is what a simple rule looks like:
target: dependencies ...
commands
...
When you run Make, you can specify particular targets to update; otherwise, Make updates the first target listed in the makefile. Of course, any other target files needed as input for generating these targets must be updated first.
Make uses the makefile to figure out which target files ought to be brought up to date, and then determines which of them actually need to be updated. If a target file is newer than all of its dependencies, then it is already up to date, and it does not need to be regenerated. The other target files do need to be updated, but in the right order: each target file must be regenerated before it is used in regenerating other targets.
Advantages of GNU Make
GNU Make has many powerful features for use in makefiles, beyond what other Make versions have. It can also regenerate, use, and then delete intermediate files which need not be saved.
GNU Make also has a few simple features that are very convenient. For example, the -o file option which says ``pretend that source file file has not changed, even though it has changed. This is extremely useful when you add a new macro to a header file. Most versions of Make will assume they must therefore recompile all the source files that use the header file; but GNU Make gives you a way to avoid the recompilation, in the case where you know your change to the header file does not require it.
However, the most important difference between GNU Make and most versions of Make is that GNU Make is free software.
Enhancements:
- Major bugfixes
<<lessMake gets its knowledge of how to build your program from a file called the makefile, which lists each of the non-source files and how to compute it from other files. When you write a program, you should write a makefile for it, so that it is possible to use Make to build and install the program.
Capabilities of Make
- Make enables the end user to build and install your package without knowing the details of how that is done -- because these details are recorded in the makefile that you supply.
- Make figures out automatically which files it needs to update, based on which source files have changed. It also automatically determines the proper order for updating files, in case one non-source file depends on another non-source file.
As a result, if you change a few source files and then run Make, it does not need to recompile all of your program. It updates only those non-source files that depend directly or indirectly on the source files that you changed.
- Make is not limited to any particular language. For each non-source file in the program, the makefile specifies the shell commands to compute it. These shell commands can run a compiler to produce an object file, the linker to produce an executable, ar to update a library, or TeX or Makeinfo to format documentation.
- Make is not limited to building a package. You can also use Make to control installing or deinstalling a package, generate tags tables for it, or anything else you want to do often enough to make it worth while writing down how to do it.
Make Rules and Targets
A rule in the makefile tells Make how to execute a series of commands in order to build a target file from source files. It also specifies a list of dependencies of the target file. This list should include all files (whether source files or other targets) which are used as inputs to the commands in the rule.
Here is what a simple rule looks like:
target: dependencies ...
commands
...
When you run Make, you can specify particular targets to update; otherwise, Make updates the first target listed in the makefile. Of course, any other target files needed as input for generating these targets must be updated first.
Make uses the makefile to figure out which target files ought to be brought up to date, and then determines which of them actually need to be updated. If a target file is newer than all of its dependencies, then it is already up to date, and it does not need to be regenerated. The other target files do need to be updated, but in the right order: each target file must be regenerated before it is used in regenerating other targets.
Advantages of GNU Make
GNU Make has many powerful features for use in makefiles, beyond what other Make versions have. It can also regenerate, use, and then delete intermediate files which need not be saved.
GNU Make also has a few simple features that are very convenient. For example, the -o file option which says ``pretend that source file file has not changed, even though it has changed. This is extremely useful when you add a new macro to a header file. Most versions of Make will assume they must therefore recompile all the source files that use the header file; but GNU Make gives you a way to avoid the recompilation, in the case where you know your change to the header file does not require it.
However, the most important difference between GNU Make and most versions of Make is that GNU Make is free software.
Enhancements:
- Major bugfixes
Download (1.1MB)
Added: 2006-04-01 License: GPL (GNU General Public License) Price:
1322 downloads
MyBook World Edition Packages 0.0
MyBook World Edition Packages project collection provides pre-compiled packages for hacking Western Digital MyBook World Edition more>>
MyBook World Edition Packages project collection provides pre-compiled packages for hacking Western Digital MyBook World Edition, to improve performance and add new features.
At least intermediate Linux experience is required for playing with MyBook. Please, if you do not meet this requirement, ask someone experienced to help you. Otherwise there is a risk that you will brick your MyBook!
<<lessAt least intermediate Linux experience is required for playing with MyBook. Please, if you do not meet this requirement, ask someone experienced to help you. Otherwise there is a risk that you will brick your MyBook!
Download (MB)
Added: 2007-07-11 License: GPL (GNU General Public License) Price:
865 downloads
AxKit2::Transformer::XSP 1.1
AxKit2::Transformer::XSP Perl module contains eXtensible Server Pages. more>>
AxKit2::Transformer::XSP Perl module contains eXtensible Server Pages.
SYNOPSIS
< xsp:page
xmlns:xsp="http://apache.org/xsp/core/v1" >
< xsp:structure >
< xsp:import >Time::Piece< /xsp:import >
< /xsp:structure >
< page >
< title >XSP Test< /title >
< para >
Hello World!
< /para >
< para >
Good
< xsp:logic >
if (localtime->hour >= 12) {
< xsp:content >Afternoon< /xsp:content >
}
else {
< xsp:content >Morning< /xsp:content >
}
< /xsp:logic >
< /para >
< /page >
< /xsp:page >
XSP implements a tag-based dynamic language that allows you to develop your own tags, examples include sendmail and sql taglibs. It is AxKits way of providing an environment for dynamic pages. XSP is originally part of the Apache Cocoon project, and so you will see some Apache namespaces used in XSP.
Also, use only one XSP processor in a pipeline. XSP is powerful enough that you should only need one stage, and this implementation allows only one stage. If you have two XSP processors, perhaps in a pipeline that looks like:
... => XSP => XSLT => XSLT => XSP => ...
it is pretty likely that the functionality of the intermediate XSLT stages can be factored in to either upstream or downstream XSLT:
... => XSLT => XSP => XSLT => ...
This design is likely to lead to a clearer and more maintainable implementation, if only because generating code, especially embedded Perl code, in one XSP processor and consuming it in another is often confusing and even more often a symptom of misdesign.
Likewise, you may want to lean towards using Perl taglib modules instead of upstream XSLT "LogicSheets". Upstream XSLT LogicSheets work fine, mind you, but using Perl taglib modules results in a simpler pipeline, simpler configuration (just load the taglib modules in httpd.conf, no need to have the correct LogicSheet XSLT page included whereever you need that taglib), a more flexible coding environment, the ability to pretest your taglibs before installing them on a server, and better isolation of interface (the taglib API) and implementation (the Perl module behind it). LogicSheets work, and can be useful, but are often the long way home. That said, people used to the Cocoon environment may prefer them.
Result Code
You can specify the result code of the request in two ways. Both actions go inside a < xsp:logic > tag.
If you want to completely abort the current request, throw an exception:
throw Apache::AxKit::Exception::Retval(return_code => FORBIDDEN);
If you want to send your page but have a custom result code, return it:
return FORBIDDEN;
In that case, only the part of the document that was processed so far gets sent/processed further.
Debugging
If you have PerlTidy installed (get it from http://perltidy.sourceforge.net), the compiled XSP scripts can be formatted nicely to spot errors easier. Enable AxDebugTidy for this, but be warned that reformatting is quite slow, it can take 20 seconds or more on each XSP run for large scripts.
If you enable AxTraceIntermediate, your script will be dumped alongside the other intermediate files, with an extension of ".XSP". These are unnumbered, thus only get one dump per request. If you have more than one XSP run in a single request, the last one will overwrite the dumps of earlier runs.
<<lessSYNOPSIS
< xsp:page
xmlns:xsp="http://apache.org/xsp/core/v1" >
< xsp:structure >
< xsp:import >Time::Piece< /xsp:import >
< /xsp:structure >
< page >
< title >XSP Test< /title >
< para >
Hello World!
< /para >
< para >
Good
< xsp:logic >
if (localtime->hour >= 12) {
< xsp:content >Afternoon< /xsp:content >
}
else {
< xsp:content >Morning< /xsp:content >
}
< /xsp:logic >
< /para >
< /page >
< /xsp:page >
XSP implements a tag-based dynamic language that allows you to develop your own tags, examples include sendmail and sql taglibs. It is AxKits way of providing an environment for dynamic pages. XSP is originally part of the Apache Cocoon project, and so you will see some Apache namespaces used in XSP.
Also, use only one XSP processor in a pipeline. XSP is powerful enough that you should only need one stage, and this implementation allows only one stage. If you have two XSP processors, perhaps in a pipeline that looks like:
... => XSP => XSLT => XSLT => XSP => ...
it is pretty likely that the functionality of the intermediate XSLT stages can be factored in to either upstream or downstream XSLT:
... => XSLT => XSP => XSLT => ...
This design is likely to lead to a clearer and more maintainable implementation, if only because generating code, especially embedded Perl code, in one XSP processor and consuming it in another is often confusing and even more often a symptom of misdesign.
Likewise, you may want to lean towards using Perl taglib modules instead of upstream XSLT "LogicSheets". Upstream XSLT LogicSheets work fine, mind you, but using Perl taglib modules results in a simpler pipeline, simpler configuration (just load the taglib modules in httpd.conf, no need to have the correct LogicSheet XSLT page included whereever you need that taglib), a more flexible coding environment, the ability to pretest your taglibs before installing them on a server, and better isolation of interface (the taglib API) and implementation (the Perl module behind it). LogicSheets work, and can be useful, but are often the long way home. That said, people used to the Cocoon environment may prefer them.
Result Code
You can specify the result code of the request in two ways. Both actions go inside a < xsp:logic > tag.
If you want to completely abort the current request, throw an exception:
throw Apache::AxKit::Exception::Retval(return_code => FORBIDDEN);
If you want to send your page but have a custom result code, return it:
return FORBIDDEN;
In that case, only the part of the document that was processed so far gets sent/processed further.
Debugging
If you have PerlTidy installed (get it from http://perltidy.sourceforge.net), the compiled XSP scripts can be formatted nicely to spot errors easier. Enable AxDebugTidy for this, but be warned that reformatting is quite slow, it can take 20 seconds or more on each XSP run for large scripts.
If you enable AxTraceIntermediate, your script will be dumped alongside the other intermediate files, with an extension of ".XSP". These are unnumbered, thus only get one dump per request. If you have more than one XSP run in a single request, the last one will overwrite the dumps of earlier runs.
Download (0.63MB)
Added: 2007-07-30 License: Perl Artistic License Price:
816 downloads

Domain Grabber for Linux 0.9.1 Beta
It will essentially run a search and display the results in a list box. more>> This application was written using the Yahoo search API. It will essentially run a search and display the results in a list box. However the app has some unique features that make it very useful for anyone who needs to compile a long list of results or domain names (either random or based upon keywords).
Features:
* Can used specified keywords or generate random keywords
* Can retrieve up to 25,000 results for each search.
* Can strip the URL down and just return the Domain Names
* Excludes duplicate results
* Export the results to a plain text file.<<less
Download (1.32MB)
Added: 2009-04-26 License: Freeware Price:
180 downloads
mod_dirsize 0.1
mod_dirsize is an Apache module to calculate the disk space used for any virtual host on a server. more>>
mod_dirsize is an Apache module to calculate the disk space used for any virtual host on a server.
The results are displayed in KB using XML.
<<lessThe results are displayed in KB using XML.
Download (0.012MB)
Added: 2005-08-23 License: GPL (GNU General Public License) Price:
1523 downloads
PerlPoint::Parser 0.45
PerlPoint::Parser Perl module is a PerlPoint Parser. more>>
PerlPoint::Parser Perl module is a PerlPoint Parser.
SYNOPSIS
# load the module:
use PerlPoint::Parser;
# build the parser and run it
# to get intermediate data in @stream
my ($parser)=new PerlPoint::Parser;
$parser->run(
stream => @stream,
files => @files,
);
The PerlPoint format, initially designed by Tom Christiansen, is intended to provide a simple and portable way to generate slides without the need of a proprietary product. Slides can be prepared in a text editor of your choice, generated on any platform where you find perl, and presented by any browser which can render the chosen output format.
To sum it up, PerlPoint Software takes an ASCII text and transforms it into slides written in a certain document description language. This is, by tradition, usually HTML, but you may decide to use another format like XML, SGML, TeX or whatever you want.
Well, this sounds fine, but how to build a translator which transforms ASCII into the output format of your choice? Thats what PerlPoint::Parser is made for. It performs the first translation step by parsing ASCII and transforming it into an intermediate stream format, which can be processed by a subsequently called translator backend. By separating parsing and output generation we get the flexibility to write as many backends as necessary by using the same parser frontend for all translators.
PerlPoint::Parser supports the complete GRAMMAR with exception of certain tags. Tags are supported the most common way: the parser recognizes any tag which is declared by the author of a translator. This way the parser can be used for various flavours of the PerlPoint language without having to be modified. So, if there is a need of a certain new flag, it can quickly be added without any change to PerlPoint::Parser.
The following chapters describe the input format (GRAMMAR) and the generated stream format (STREAM FORMAT). Finally, the class methods are described to show you how to build a parser.
<<lessSYNOPSIS
# load the module:
use PerlPoint::Parser;
# build the parser and run it
# to get intermediate data in @stream
my ($parser)=new PerlPoint::Parser;
$parser->run(
stream => @stream,
files => @files,
);
The PerlPoint format, initially designed by Tom Christiansen, is intended to provide a simple and portable way to generate slides without the need of a proprietary product. Slides can be prepared in a text editor of your choice, generated on any platform where you find perl, and presented by any browser which can render the chosen output format.
To sum it up, PerlPoint Software takes an ASCII text and transforms it into slides written in a certain document description language. This is, by tradition, usually HTML, but you may decide to use another format like XML, SGML, TeX or whatever you want.
Well, this sounds fine, but how to build a translator which transforms ASCII into the output format of your choice? Thats what PerlPoint::Parser is made for. It performs the first translation step by parsing ASCII and transforming it into an intermediate stream format, which can be processed by a subsequently called translator backend. By separating parsing and output generation we get the flexibility to write as many backends as necessary by using the same parser frontend for all translators.
PerlPoint::Parser supports the complete GRAMMAR with exception of certain tags. Tags are supported the most common way: the parser recognizes any tag which is declared by the author of a translator. This way the parser can be used for various flavours of the PerlPoint language without having to be modified. So, if there is a need of a certain new flag, it can quickly be added without any change to PerlPoint::Parser.
The following chapters describe the input format (GRAMMAR) and the generated stream format (STREAM FORMAT). Finally, the class methods are described to show you how to build a parser.
Download (0.41MB)
Added: 2007-02-12 License: Perl Artistic License Price:
985 downloads
Race Timing 0.01
Race Timing lets you manage races by describing a race and the rules associated with it. more>>
Race Timing lets you manage races by describing a race and the rules associated with it. You can time the racers and provide realtime standing of the race participants.
You can manage various race events (pilot changes, refuelling, laps, intermediate sprints, etc.) and broadcast various information to the participants. Race Timing is best used with transponders, but manual operation is also provided.
<<lessYou can manage various race events (pilot changes, refuelling, laps, intermediate sprints, etc.) and broadcast various information to the participants. Race Timing is best used with transponders, but manual operation is also provided.
Download (1.1MB)
Added: 2006-07-12 License: GPL (GNU General Public License) Price:
1202 downloads
RAVE 1.9.9
RAVE (Retrospective Analysis and Visualization Engine) is a framework for generating complex analysis products. more>>
RAVE 1.9.9 is yet another excellent utility for everyone. RAVE stands for Retrospective Analysis and Visualization Engine which is a framework for generating complex analysis products.
RAVE caches the intermediate results of analytic tasks for later use in the same or different analyses. This improves performance by reducing duplicated effort when generating analytic results. RAVE users need to do nothing special in order to take advantage of this performance improvement.
The RAVE project provides tools to use RAVE interactively in a terminal, or to publish "live" RAVE analyses online as a network service for use in network-enabled applications.
CERT/NetSA has deployed RAVE to support analysis using the SiLK suite of flow analysis tools. They also distribute the libraries created to perform common flow analysis tasks using SiLK, such as efficiently using pipe-and-filter-based command-line tools from Python, dealing with heterogeneous data sources and efficiently retrieving time-series data.
Requirements:
- Python 2.4 or higher
Added: 2008-04-09 License: GPL Price: FREE
13 downloads
Dream DRM Receiver 1.6.25
Dream DRM Receiver is an implementation of Digital Radio Mondiale. more>>
Digital Radio Mondiale, also known as DRM, is a new digital radio standard for the long-, medium- and short-wave ranges.
The standard was formed by a consortium in co-operation with the International Telecommunication Union (ITU). The new system offers the radio stations and new service providers access to the multimedia age with small bit rates for large target areas and long distances.
The bandwidth of a DRM bandpass signal is less than 20 kHz and the number of carriers used in the OFDM-modulation is relatively small (max. 460). These features motivate a real-time software implementation of a DRM-receiver on a conventional personal computer (PC) using the sound card as the input and output device. A long, medium and short wave front-end with an intermediate frequency (IF) between 5 kHz and 15 kHz is used to receive the DRM signal.
Any commercial front-end with an IF of 455 kHz should be usable by adding a 455 kHz to 12 kHz adaptor (assumed the receiver bandwidth is sufficient for a DRM signal).
With this software project we intend to implement a working software receiver with, at least, the basic features. Since this project is created at a university and the fundamental idea of such an institution is to teach and stimulate the creativity, this source-code is free under the GNU-General Public License (GPL).
Dream is a development project which uses the open source model to improve DRM technology. The main aim of this project is to implement and test new research results on an existing system, whereby the synchronization and channel estimation is of special interest.
The programming-language is C++. The code runs under Microsoft Windows and Linux. Start of the project was June 2001.
Although this software is going to be distributed as free software under the terms of the GPL this does not mean that its use is free of rights of others. The use may infringe third party IP and thus may not be legal in some countries.
The intended audience of the Dream software are people who are interested in how to decode a DRM stream and want to learn from the algorithms used in this software and people who want to help us improving the performance of the receiver and the source code.
<<lessThe standard was formed by a consortium in co-operation with the International Telecommunication Union (ITU). The new system offers the radio stations and new service providers access to the multimedia age with small bit rates for large target areas and long distances.
The bandwidth of a DRM bandpass signal is less than 20 kHz and the number of carriers used in the OFDM-modulation is relatively small (max. 460). These features motivate a real-time software implementation of a DRM-receiver on a conventional personal computer (PC) using the sound card as the input and output device. A long, medium and short wave front-end with an intermediate frequency (IF) between 5 kHz and 15 kHz is used to receive the DRM signal.
Any commercial front-end with an IF of 455 kHz should be usable by adding a 455 kHz to 12 kHz adaptor (assumed the receiver bandwidth is sufficient for a DRM signal).
With this software project we intend to implement a working software receiver with, at least, the basic features. Since this project is created at a university and the fundamental idea of such an institution is to teach and stimulate the creativity, this source-code is free under the GNU-General Public License (GPL).
Dream is a development project which uses the open source model to improve DRM technology. The main aim of this project is to implement and test new research results on an existing system, whereby the synchronization and channel estimation is of special interest.
The programming-language is C++. The code runs under Microsoft Windows and Linux. Start of the project was June 2001.
Although this software is going to be distributed as free software under the terms of the GPL this does not mean that its use is free of rights of others. The use may infringe third party IP and thus may not be legal in some countries.
The intended audience of the Dream software are people who are interested in how to decode a DRM stream and want to learn from the algorithms used in this software and people who want to help us improving the performance of the receiver and the source code.
Download (0.80MB)
Added: 2006-09-12 License: GPL (GNU General Public License) Price:
774 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above intermediate results search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed