https://github.com/alkasaliss/projetweb

Web interface for machine learning algorithms back to Back testing through three Frameworks : Renjin, Weka and SparkML
https://github.com/alkasaliss/projetweb

Last synced: about 2 months ago
JSON representation

Web interface for machine learning algorithms back to Back testing through three Frameworks : Renjin, Weka and SparkML

• Host: GitHub
• URL: https://github.com/alkasaliss/projetweb
• Owner: AlkaSaliss
• License: mit
• Created: 2018-03-22T23:08:38.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2018-03-29T14:59:32.000Z (almost 7 years ago)
• Last Synced: 2023-10-20T16:31:32.930Z (about 1 year ago)
• Language: CSS
• Homepage:
• Size: 896 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
Simple web-based interface for Back-To-Back Testing for machine learning algorithms

===============

Template for a simple Vaadin application that only requires a Servlet 3.0 container to run.

Pre-requisites : vaadin plug-in install

-----------------------

In eclipse IDE, go to 'help' menu, and then select 'eclipse market'. In the search bar type 'vaadin', and finally click the install button and follow the instructions.

For more detailed information, you can check this [tutorial for a quick introduction](https://www.youtube.com/watch?v=o93ofXBIkf8).

Workflow

----------------

To run this application on your local machine, follow these steps:

* Clone the git repository : 'git clone https://github.com/AlkaSaliss/ProjetWeb.git'

* Open the terminal where the git project is located and run the following command to comple the project: 'mvn install'

* To run the application, run 'mvn jetty:run' and open 'http://localhost:8080/' . And have fun.;)

To produce a deployable production mode WAR:

* change productionMode to true in the servlet class 'WebConfig.java' (nested in the UI class).

* run "mvn clean package".

* test the war file with "mvn jetty:run-war"

Advanced settings...

====================

Client-Side compilation

-------------------------

The generated maven project is using an automatically generated widgetset by default. 

When you add a dependency that needs client-side compilation, the maven plugin will 

automatically generate it for you. Your own client-side customizations can be added into

package "client".

Debugging client side code

  - run "mvn vaadin:run-codeserver" on a separate console while the application is running

  - activate Super Dev Mode in the debug window of the application

Developing a theme using the runtime compiler

-------------------------

When developing the theme, Vaadin can be configured to compile the SASS based

theme at runtime in the server. This way you can just modify the scss files in

your IDE and reload the browser to see changes.

To use the runtime compilation, open pom.xml and comment out the compile-theme 

goal from vaadin-maven-plugin configuration. To remove a possibly existing 

pre-compiled theme, run "mvn clean package" once.

When using the runtime compiler, running the application in the "run" mode 

(rather than in "debug" mode) can speed up consecutive theme compilations

significantly.

It is highly recommended to disable runtime compilation for production WAR files.

Using Vaadin pre-releases

-------------------------

If Vaadin pre-releases are not enabled by default, use the Maven parameter

"-P vaadin-prerelease" or change the activation default value of the profile in pom.xml .