Virtual Learning Factory Toolkit
  • Virtual Learning Factory Toolkit
  • VLF Knowledge Base
    • Factory Data Model
      • OWL Classes
      • SPARQL Queries
      • SPARQL Updates
    • Instantiation of Factory Models
      • Assets
        • Assets in Spreadsheet
        • Assets in JSON
        • Assets in Ontology
      • 3D Models of Assets
        • 3D Models for Virtual Reality
      • Statechart
      • Animations
      • Data Repositories
        • Local Repository
        • Remote Repository
  • VLF Tools and Libraries
    • OntoGui
      • Modules
        • Control Panel
        • Individual Manager
        • System Design
        • Utilities
      • Personalization
    • OntoGuiWeb
      • Modules
        • Control Panel
        • SPARQL
        • Graphs OWL
        • Utilities
        • Asset Design
        • System Design
        • System Control
        • Performance Evaluation
        • MQTT Sync
        • Virtual Environment
        • Graphs Eng
        • StateChart
      • Personalization
    • jsimIO
      • How to start
      • JMT Overview
        • JSim
          • Model generation
          • Launch of the simulation
          • Reporting
        • Bibliography
    • VEB.js
      • Functionalities
      • Input/Output files
      • Integration with other software tools
      • Advanced Users
    • ApertusVR
    • MTM
      • How to start
      • Formalise the process
      • Prepare input data
      • Execution and results
    • MOST
      • How to start
      • Formalise the process
      • Prepare input data
      • Execution and results
    • RULA
      • How to start
      • Formalise the process
      • Prepare input data
      • Execution and results
    • OCRA
      • How to start
      • Prepare input data
      • Execution and results
  • Use Cases
    • Automated Assembly Line
    • Assets and Animations
    • Modelling of Factory Assets
      • Modelling of an Assembled Product
      • Modelling of a Workstation
      • 3D Modelling of a Workstation for Virtual Reality
    • Process Modelling
      • Modelling an Assembly Process
    • Modelling of a manufacturing system
      • Modelling in OntoGui
      • Modelling a Job Shop using OntoGui
      • Modelling of a Flow Shop using OntoGui
      • Modelling a Hybrid Flow Shop using OntoGui
      • Modelling an assembly system using OntoGui
    • Performance evaluation using jsimIO
      • Performance evaluation of a manufacturing system
        • Performance evaluation in Jsim
        • Performance evaluation of a Flow Shop using Jsim
        • Performance Evaluation of a Job Shop using JSim
        • Performance evaluation of a Hybrid Flow Shop using Jsim
        • Performance evaluation of an assembly system using Jsim
      • jsimIO Assembly
      • jsimIO Automatic
      • jsimIO Production
  • Classworks
  • Advanced Features
    • JMT model
      • Automatic generation of a JMT model
      • Automatic generation of animations
    • Enabling technologies
      • Node-RED
        • Node-RED tutorial
      • RDF libraries
Powered by GitBook
On this page
  • Scene
  • Animation
  • Environment
  • Configuration

Was this helpful?

  1. VLF Tools and Libraries
  2. VEB.js

Input/Output files

PreviousFunctionalitiesNextIntegration with other software tools

Last updated 2 years ago

Was this helpful?

Input files define the content of the , the , the setup, and the app . All input files can be specified using URL parameters. If not explicitly specified, VEB.js will try to load the animation, environment and configuration files of a scene according to the following convention. Given a scene file named scene.json, the convention is that the corresponding animation file is named scene_anim.json, the environment file scene_env.json, and the configuration file scene_config.json.

are provided in the Use Case section.

Scene

Scenes can be imported/exported from/to a .json file according to a .

Animation

The animation of the scene can be defined in a together with additional data (e.g. reusable animation sequences) stored as .

Environment

The environment setup is defined in a .json file according to a schema with the following root properties:

  • "cameras": an array defining cameras to navigate the scene. Each camera can be characterized by "id", "type" (e.g. "FlyCamera", "FreeCamera", "ArcRotateCamera", etc.), "position", "rotation", "speed".

  • "lights": an array defining sources of light in the scene. Each light can be characterized by "id", "type" (e.g. "HemisphericLight", "PointLight", etc.), "position" or "direction", "intensity".

  • "shadows": an object specifying how shadows are generated with properties "darkness", "bias", "environmentIntensity".

  • "datagen": definition of parameters for the generation of data, in particular screenshots. The poperty "cam" defines the movements of the ArcRotateCamera that points the selected mesh in terms of alpha, beta and radius. Alpha and beta are degrees (angles) with a starting value ("alphaMin", "betaMin"), a final value ("alphaMax", "betaMax") and an incremental step ("alphaStep", "betaStep"). The radius is calculated multiplying the diagonal of the selected asset bounding box by a factor that is specified with an initial value ("radiusFactorMin"), a final value ("radiusFactorMax") and an incremental step ("radiusFactorStep").

  • "env":

    • "skyboxTexture": texture to be used for a skybox environment (default "textures/studio.env")

    • "backgroundColor": color of the background defined as an array of floats representing the RGB values (default [0.2,0.2,0.3]

    • "groundTexture": texture to be used for the ground (absent by default)

    • "groundSize": array of integer values defining the width, height, and subdivision of the ground

Configuration

The app configuration is defined in a .json file according to a schema with the following root properties:

  • "endpoint": definition of the SPARQL endpoint to query/update an ontology. Its properties are:

    • "server": address of the server

    • "database": name of the database

    • "user": user

    • "psw": password

  • "repo": definition of the repositories that are relevant to load a VR scene

    • "model3d": repository of the 3D models

    • "animation": repository of the animation sequences

    • "sparqlDir": repository of the SPARQL query/update templates

  • "MQTT": definition of MQTT communication settings

    • "broker": URL of the broker

    • "sub_base_topics": array of base topics (that are customized with the addition of the scene name) for MQTT subscriptions

    • "pub_base_topics": array of base topics (that are customized with the addition of the scene name) for MQTT publishing

    • "QoS": quality of service (0, 1, 2)

Examples of input files
specific schema
.json file
scene
animation
environment
configuration
.txt files