Coder Social home page Coder Social logo

hdi-project / atmseer Goto Github PK

View Code? Open in Web Editor NEW
170.0 170.0 38.0 4.17 MB

Visual Exploration of Automated Machine Learning with ATMSeer

Home Page: https://dai.lids.mit.edu/projects/atmseer/

Python 23.10% HTML 0.25% CSS 1.57% TypeScript 74.67% Shell 0.28% Dockerfile 0.13%

atmseer's People

Contributors

alexmfranklin avatar dependabot[bot] avatar dyuliu avatar jnzhihuoo1 avatar kveerama avatar micahjsmith avatar myaooo avatar novokaine avatar sergiu-ojoc avatar wangqianwen0418 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

atmseer's Issues

Error on datarun

Description

The datarun fails at this endpoint: /api/hyperpartitions?&datarun_id=5 [GET]

Expected Behavior

The datarun should give results for the uploaded dataset.

Actual Behavior

The datarun fails at this endpoint: /api/hyperpartitions?&datarun_id=5 [GET] throwing Internal Server Error. The corresponding error appearing on console is:

File "server/atm_server/api.py", line 137, in get_hyperpartitions return jsonify(fetch_hyperpartitions(dataset_id=dataset_id, datarun_id=datarun_id, nice=nice))

and

File "server/atm_server/utils.py", line 44, in default return {'type': o.type, 'range': o.range} AttributeError: 'IntHyperParameter' object has no attribute 'type'

Steps to Reproduce the Problem

  1. Upload test dataset e.g blood.csv.
  2. Select any configuration.
  3. Click Run

Specifications

  • ATMSeer Version: Latest pull.
  • Vagrant Version:
  • VirtualBox Version:
  • OS Version: Ubuntu 18.04

sqlalchemy InvalidRequestError

After the initial installation, uploading my dataset and creating a datarun, upon hitting Run, I get the following errors in my console:

    default: Traceback (most recent call last):
    default:   File "/vagrant/venv/lib/python3.5/site-packages/flask/app.py", line 1805, in full_dispatch_request
    default:     rv = self.dispatch_request()
    default:   File "/vagrant/venv/lib/python3.5/site-packages/flask/app.py", line 1791, in dispatch_request
    default:     return self.view_functions[rule.endpoint](**req.view_args)
    default:   File "/vagrant/server/atm_server/api.py", line 381, in dispatch_single_worker
    default:     start_worker(datarun_id)
    default:   File "/vagrant/server/atm_server/atm_helper/worker.py", line 193, in start_worker
    default:     datarun = db.get_datarun(datarun_id)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/atm/database.py", line 38, in call
    default:     result = func(db, *args, **kwargs)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/atm/database.py", line 358, in get_datarun
    default:     return self.session.query(self.Datarun).get(datarun_id)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/orm/session.py", line 1543, in query
    default:     return self._query_cls(entities, self, **kwargs)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/orm/query.py", line 168, in __init__
    default:     self._set_entities(entities)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/orm/query.py", line 200, in _set_entities
    default:     self._set_entity_selectables(self._entities)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/orm/query.py", line 231, in _set_entity_selectables
    default:     ent.setup_entity(*d[entity])
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/orm/query.py", line 4083, in setup_entity
    default:     self._with_polymorphic = ext_info.with_polymorphic_mappers
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/util/langhelpers.py", line 855, in __get__
    default:     obj.__dict__[self.__name__] = result = self.fget(obj)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/orm/mapper.py", line 2135, in _with_polymorphic_mappers
    default:     configure_mappers()
    default:   File "/vagrant/venv/lib/python3.5/site-packages/sqlalchemy/orm/mapper.py", line 3225, in configure_mappers
    default:     raise e
    default: sqlalchemy.exc.InvalidRequestError: One or more mappers failed to initialize - can't proceed with initialization of other mappers. Triggering mapper: 'mapped class Classifier->cl
assifiers'. Original exception was: Mapper 'mapped class Hyperpartition->hyperpartitions' has no property 'classifiers'
    default: [INFO] [12:29:44:werkzeug] 10.0.2.2 - - [03/Jun/2019 12:29:44] "GET /api/start_worker/1 HTTP/1.1" 500 -

404 error

messages in terminal are as below:

default: [INFO] [11:03:19:werkzeug] * Running on http://0.0.0.0:7777/ (Press CTRL+C to quit)
default: [INFO] [11:03:19:werkzeug] * Restarting with stat
default: [WARNING] [11:03:28:werkzeug] * Debugger is active!
default: [INFO] [11:03:28:werkzeug] * Debugger PIN: 137-297-764
default: [INFO] [11:03:29:werkzeug] 10.0.2.2 - - [18/Jun/2019 11:03:29] "GET / HTTP/1.1" 404 -
default: [INFO] [11:03:29:werkzeug] 10.0.2.2 - - [18/Jun/2019 11:03:29] "GET /favicon.ico HTTP/1.1" 404 -
default: No valid rules have been specified for JavaScript files
default: [INFO] [11:04:56:werkzeug] 10.0.2.2 - - [18/Jun/2019 11:04:56] "GET / HTTP/1.1" 404 -
default: [INFO] [11:05:29:werkzeug] 10.0.2.2 - - [18/Jun/2019 11:05:29] "GET / HTTP/1.1" 404 -

when I navigate to http://localhost:7779/, the browser shows 404 not found.
Is there any solution for this issue?
Thanks

sudo sh install-docker.sh

Description

debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

Specifications

  • ATMSeer Version:
  • Vagrant Version:
  • VirtualBox Version:
  • OS Version:

Cross Origin Resource Sharing is blocked while running application on ubuntu os in digital ocean server

Access to XMLHttpRequest at 'http://139.59.xx.xx:7777/api/new_datarun/85' from origin 'http://139.59.xx.xx:7779' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

The above error is coming after deploying application in digital ocean. Note: File upload is successful, but next requests are failing by CORS errors.

Any suggestion to resolve the issue is appreciated.
Thanks!

installation error on windows

Getting following error while running install.sh script on windows. Any resolution for this?

default: npm
    default:  WARN [email protected] requires a peer of ajv@^6.0.0 but none is installed. You must install peer dependencies yourself.
    default: npm
    default: WARN
    default:  optional
    default:  SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/rc/node_modules/minimist):
    default: npm
    default: WARN enoent
    default:  SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, open '/vagrant/node_modules/fsevents/node_modules/rc/node_modules/minimist/package.json.2605020691'
    default: npm WARN
    default:  optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
    default: npm WARN
    default:  notsup
    default:  SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
    default: npm ERR!
    default:  Maximum call stack size exceeded
    default: npm
    default: ERR! A complete log of this run can be found in:
    default: npm ERR!     /root/.npm/_logs/2019-06-12T10_03_16_977Z-debug.log
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'ubuntu/xenial64' version '20190605.0.0' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 7777 (guest) => 7777 (host) (adapter 1)
    default: 7779 (guest) => 7779 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 5.1.38
    default: VirtualBox Version: 6.0
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/jmotwani/ATMSeer
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running provisioner: vagrantstart (shell)...
    default: Running: C:/Users/jmotwani/AppData/Local/Temp/vagrant-shell20190612-164-1j9a70d.sh
    default: sh: 1: cross-env: not found
    default: npm
    default:
    default: ERR!
    default:
    default: file
    default:  sh
    default: npm
    default:
    default: ERR!
    default:
    default: code
    default:  ELIFECYCLE
    default: npm
    default:
    default: ERR!
    default:
    default: errno
    default:  ENOENT
    default: npm
    default:
    default: ERR!
    default:  syscall
    default:  spawn
    default: npm
    default: ERR!
    default:  [email protected] start: `cross-env PORT=7779 react-scripts-ts start`
    default: npm
    default:
    default: ERR! spawn ENOENT
    default: npm
    default:  ERR!
    default:
    default: npm
    default:
    default: ERR!
    default:  Failed at the [email protected] start script.
    default: npm
    default:
    default: ERR!
    default:  This is probably not a problem with npm. There is likely additional logging output above.
    default: npm ERR!
    default:  A complete log of this run can be found in:
    default: npm ERR!     /root/.npm/_logs/2019-06-12T10_03_53_255Z-debug.log
    default:  * Serving Flask app "server" (lazy loading)
    default:  * Environment: development
    default:  * Debug mode: on
    default: [INFO] [10:04:00:werkzeug]  * Running on http://0.0.0.0:7777/ (Press CTRL+C to quit)
    default: [INFO] [10:04:00:werkzeug]  * Restarting with stat
    default: Traceback (most recent call last):
    default:   File "server/atm_server/server.py", line 97, in <module>
    default:     start_server()
    default:   File "server/atm_server/server.py", line 92, in start_server
    default:     port=int(_args.port)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/flask/app.py", line 941, in run
    default:     run_simple(host, port, self, **options)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/werkzeug/serving.py", line 1007, in run_simple
    default:     run_with_reloader(inner, extra_files, reloader_interval, reloader_type)
    default:   File "/vagrant/venv/lib/python3.5/site-packages/werkzeug/_reloader.py", line 332, in run_with_reloader
    default:     sys.exit(reloader.restart_with_reloader())
    default:   File "/vagrant/venv/lib/python3.5/site-packages/werkzeug/_reloader.py", line 176, in restart_with_reloader
    default:     exit_code = subprocess.call(args, env=new_environ, close_fds=False)
    default:   File "/usr/lib/python3.5/subprocess.py", line 557, in call
    default:     with Popen(*popenargs, **kwargs) as p:
    default:   File "/usr/lib/python3.5/subprocess.py", line 947, in __init__
    default:     restore_signals, start_new_session)
    default:   File "/usr/lib/python3.5/subprocess.py", line 1551, in _execute_child
    default:     raise child_exception_type(errno_num, err_msg)
    default: OSError: [Errno 8] Exec format error
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

ATMSeer not working remotely on server after hosting

Description

ATMSeer is not working after deploying to derver and access it remotely and not locally. No 'Access-Control-Allow-Origin' header is present on the requested resource.

Expected Behavior

After clicking on run button all the output should be displayed and graphs should be seen. But after run button click error is coming.

Actual Behavior

CSV input data is uploaded but after that clicking on run button application is crashing.

Steps to Reproduce the Problem

  1. Simply upload the whole project to digital ocean server and run the application server.
  2. Then access the application with the server url on port 7779.
  3. upload CSV inuput data and then select datarun and click on run button. Then error comes after that.

Specifications

  • ATMSeer Version: latest version of master branch
  • Vagrant Version: 1.8.1
  • VirtualBox Version: ubuntu-xenial 16.04
  • OS Version: ubuntu 16.04

Documentation for the API's

Hi All,

I'm wondering whether there is some documentation or a roadmap for the API available. Of the endpoints, I'm interested in knowing what people think is relatively fixed, likely to change, or likely to be added.

I'm working on an integration of Trane, FeatureTools, and ATM (all HDI related libraries) and am trying to figure out whether it makes sense to use the API-Viz project, fork it and edit, or try to roll my own.

Thank you. I really appreciate any guidance or advice you can offer!
Al

error when running sh install.sh on mac os

I tried running the sh install.sh command but I got this error message:

Submodule path 'lib/atm': checked out '9dfe5d9c883efc37d285c852fcc92a02c6cdd945'
install.sh: line 7: vagrant: command not found
install.sh: line 8: vagrant: command not found

Running in Windows

Do you have any shell scripts or mechanisms that will run in windows? Or do I need to do this in a linux system?

Installation Error and Failure on Windows

Description

After installing VirtualBox and Vagrant, I cloned the repository and then executed the sh install.sh command in the terminal where I cloned the ATMSeer project.

Expected Behavior

Based on the instructions provided in the readme, I should've received the expected output indicating that ATMSeer is up and running, but I was not able to reach that point.

Actual Behavior

When attempting to install ATMSeer, I received the following message in my terminal:
default: /tmp/vagrant-shell: line 2: /vagrant/venv/bin/activate: No such file or directory
default: /tmp/vagrant-shell: line 5: python: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Additionally, when I attempted to run 'vagrant up' in the terminial, I received a similar error:
default: /tmp/vagrant-shell: line 2: /vagrant/venv/bin/activate: No such file or directory
default: /tmp/vagrant-shell: line 5: python: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Specifications

  • ATMSeer Version:
  • Vagrant Version: 2.2.5
  • VirtualBox Version: 6.0.8
  • OS Version: Windows 10

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.