Search results

>>> import vcs >>> import cdms2

import core.modules import core.modules.module_registry

<nowiki>from core.modules.vistrails_module import Module from widgets import MyConfigurationWidget

import vtk from vtk.util.colors import tomato

The server doesn't start because of an import problem. This can be fixed by replacing vistrails/gui/application_server.py in the import section (around line 27), add

...umes a vistrail exists which may introduce issues. We have the ability to import workflows from xml so we should be able to create a vistrail from the group ...in the registry list (although they must be in the registry); a user must import them into his own "My Subworkflows" in order to use them in his own work.

from core.modules.vistrails_module import Module, newModule, \ import core.packagemanager

...ges the way the path must be set up, and the syntax that has to be used to import VisTrails packages; safeties are in place to enable old packages that were

import core.modules.module_registry from core.modules.vistrails_module import Module, ModuleError

import platform >>> import vistrails as vt

import core.modules.module_registry from core.modules.vistrails_module import Module, ModuleError

* [RR] Export/import workflow to Python working! ** [RR] export/import with Python could reduce a lot of that friction by allowing 1) to edit work

import os

import os

...Oculus Rift S environment. But I don't actually understand why the Oculus import resulted in two quite different spinning motions, given that the starting A ...slates the xml-based COLLADA code into a format that the Oculus Rift S can import/read. This appears to indicate that the KG &#8212; and/or the Oculus Rift

** '''[https://www.vistrails.org/ticket/762 762](tbm)''' import sys package ** replace import statement to add "vistrails." prefix

*** allow users to import aliases, but don't write back to vistrail unless users wants to ** Import vistrail from DB is now very fast.

import os

** e.g. "import core.vistrail.module" becomes "import vistrails.core.vistrail.module" ** Also, for "import vistrails" style use of VisTrails, it would be nice to be able to specify w

...reality). A cursory online investigation suggests that we may be able to import OBJ-formatted files into the software algorithms that drive these two techn ...LADA ''Conformance Test Suite'' (CTS). The suite allows applications that import and export COLLADA to test against a large suite of examples, ensuring that

*** Updates print to functions 'from __future__ import print_function' *** Fixes relative imports (from __future__ import absolute_import)

** Add higher-level features like "Upgrade All" for (1), "Import Changes to My Subworkflows", etc. ...figuration widgets not as classes but rather some text that can be used to import the GUI elements only when using the GUI code. However, what would happen

*** When loading, ask 'Do you want to import package in bundle' if not already existing. ** [TE] import data into vistrails?, truncate based on a map from file locations to bundle

...e we explain what steps were followed as we attempted to figure out how to import such 3D scenes into the VR/AR environment offered by the Oculus Rift S. ...ed .dae file to a .glb format. <font color="red">This time, I was able to import the model into the Oculus Rift S, grab it, and place it into my Oculus Home

...Oculus_Rift_S_Environment|discussed below]], the Oculus Rift S system will import our COLLADA-based models only if each model file has been translated from a ...oes not accept COLLADA-formatted files directly. Instead, it is set up to import files that are in a ".glb" format, which is the binary version of a "GL Tra