Integrated Software for Imagers and Spectrometers v3. ISIS3 is a digital image processing software package to manipulate imagery collected by current and past NASA and International planetary missions.
Home Page: https://isis.astrogeology.usgs.gov
License: Other
We can handle dependency change in a channel like conda-forge by calling out exact versions of our dependencies, which we do now (see cmake branch's environment.yml file).
However, what do we do if requested package version is broken (see #446)?
How do we handle when a channel (e.g. conda-forge) hosts a specific version of a package we require and it has its label edited to something other than main?
What is conda-forge's process for dealing with broken labels? What does broken mean? Does it mean there is a known bug in curl7.55.1, or that conda-forge's build of that version is broken?
Should our version requirements be exact (X.Y.Z with build number), a little bit flexible (>= X.1. < X.2), or more generic?
How do other recipe maintainers, like conda-forge, handle dependency changes for their packages they host)?
MD5 related classes in lrowac2isis and lronac2isis are complete copies of each other. Should be moved into the ISIS api.
We need to finish our code review checklist for ISIS3. I've copied it out of our google doc and into the wiki so it's publicly available. Please take a minute and read it over. Any questions, comments, proposed edits can be discussed here.
Running findfeatures via isisminer and cluster jobs using isis3beta2018-09-18 (and I think last weeks run was under the beta public release - error there as well).
I get the following error for 7 images:
Program = findfeatures
Class = "PROGRAMMER ERROR"
Code = 3
Message = "Failed to get geometry mapping for
See example under /work/users/lweller/Isis3Tests/FindFeatures/GeometryError/. LOG file in the top directory is stdout/err captured via slurm (ignore the rsync failures - directories didn't exist).
The input fromlist, debuglog and isisminer _matcher.cmd files are under the subdirectory N1489047533_2_Network/. The match image with full path can be found in the LOG, print.prt and matcher.cmd files. Any reference file on my /scratch area have since been moved, but everything necessary to duplicate is available.
I have not tried to rerun these failed images outside the cluster environment, but I suspect they would fail as well on the astrovm.
Prerequisites:
Requirements:
There a some outstanding PR's into dev.
We should review these and see which ones should be isis3.6.0.
This issue can be worked on by multiple people. Tyler is currently iterating on the user-oriented installation guide (PR #443 ).
Update and review installation documentation for developers (in-house & external) and users.
The developer documentation is located on this GitHub's wiki.
The user documentation is our install guide hosted on our website (https://isis.astrogeology.usgs.gov)
User documentation:
Developer documentation:
Prerequisites:
Requirements:
The jigsaw test pole-ra-dec-w0-wDot-triaxial-radii is giving different output on different machines that are running MacOS 10.13. Prog27 and algol are giving the same output, while my machine is different.
Currently, a README.md file exists in the input saying that we know of this problem, however, it would be nice to know why this is happening. See the files below to see output.
Other output:
pole-ra-dec-w0-wDot-triaxial-radii_bundleout.txt
Prog27:
prog27Output.txt
This is piggybacking off of #350:
When I look at the base data area, I see that the translations are ~420k of test files, applications are 28K of text files, and icons are ~3MB of pngs. Why aren't we keeping these under version control with the source? If the concern is the pngs, we can convert to SVG.
If this were the case, @rbeyer could submit a PR (or we could PR in the fix just as easily) to address #350.
Also, the WarningTreeWidget in qisis/objs is being used in the Directory class but the on used for IPCE is not used at all.
I'm trying to build ISIS3 following the instructions in https://github.com/USGS-Astrogeology/ISIS3/wiki/Developing-ISIS3-with-cmake . At some point you say:
Set your ISISROOT to /the/path/to/your/build:
setisis .
But there is no command setisis in my current environment.
I could assume you are trying to say $ set ISISROOT ., and considering the reader is using csh, but to this point, I learned that assuming may not be a good idea.
So, what should I do with this
It looks like it was replaced with PolynomialUnivariate. I'm going to remove this and see if it breaks anything.
Hi there,
I'm attempting to follow the new installation instructions sent out with the e-mail today about the new release. When I enter:
conda install -c usgs-astrogeology isis3
I receive the following error message:
"Solving environment: failed
PackagesNotFoundError: The following packages are not available from current channels:
Current channels:
Any idea what might be causing the error, and how I might fix it?
Thanks, Catherine
See #435 for some discussion about CentOS 7.
This isn't about the code in this repo, but about the contents of one of the files in $ISIS3DATA, specifically: $ISIS3DATA/base/translations/pdsImageProjection.trn
In the 'TargetName' group, neither Pluto nor Charon appear. Its been three years since New Horizons flew by, maybe time for those to be in there.
Importfits.cpp/.h are virtually identical except for some minor differences. These should be consolidated somehow.
With the new cmake development environment linking fails on CentOS 7.x
commands:
cd ./isis
conda env create -n isis3 -f environment.yml
source activate isis3
mkdir build
cd build
cmake .. (cmake flags not included)
make
error:
[ 40%] Linking CXX shared library ../lib/libisis3.so
[ 40%] Built target isis3
Scanning dependencies of target voyager
[ 40%] Building CXX object objects/CMakeFiles/voyager.dir/voyager/objs/VoyagerCamera/VoyagerCamera.cpp.o
[ 40%] Linking CXX shared library ../lib/libvoyager.so
[ 40%] Built target voyager
Scannig dependencies of target voycal_app
[ 40%] Building CXX object objects/CMakeFiles/voycal_app.dir/voyager/apps/voycal/voycal.cpp.o
[ 40%] Linking CXX executable ../bin/voycal
../lib/libisis3.so: error: undefined reference to 'pcl::io::load(std::string const&, pcl::PolygonMesh&)'
../lib/libisis3.so: error: undefined reference to 'geos::io::WKTReader::read(std::string const&)'
../lib/libisis3.so: error: undefined reference to 'geos::io::WKTWriter::write(geos::geom::Geometry const*)'
../lib/libisis3.so: error: undefined reference to 'geos::geom::Coordinate::toString() const'
../lib/libisis3.so: error: undefined reference to 'geos::operation::valid::TopologyValidationError::toString()'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::internal::fixed_address_empty_string'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::internal::WireFormatLite::ReadBytes(google::protobuf::io::CodedInputStream*, std::string*)'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::io::CodedOutputStream::WriteStringWithSizeToArray(std::string const&, unsigned char*)'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::internal::AssignDescriptors(std::string const&, google::protobuf::internal::MigrationSchema const*, google::protobuf::Message const* const*, unsigned int const*, google::protobuf::MessageFactory*, google::protobuf::Metadata*, google::protobuf::EnumDescriptor const**, google::protobuf::ServiceDescriptor const**)'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::MessageFactory::InternalRegisterGeneratedFile(char const*, void (*)(std::string const&))'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::internal::WireFormatLite::WriteStringMaybeAliased(int, std::string const&, google::protobuf::io::CodedOutputStream*)'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::Message::GetTypeName() const'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::Message::InitializationErrorString() const'
../lib/libisis3.so: error: undefined reference to 'google::protobuf::internal::OnShutdownDestroyString(std::string const*)'
collect2: error: ld returned 1 exit status
make[2]: *** [objects/CMakeFiles/voycal_app.dir/build.make:290: bin/voycal] Error 1
make[1]: *** [CMakeFiles/Makefile2:2806: objects/CMakeFiles/voycal_app.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
The isis3 version is defined in 3 places that I could find:
isis/version contains the version number, date, and build status (alpha, beta, stable)isis/CMakeLists.txt contains VERSION, VERSION_DATE, and RELEASE_STAGE variablesisis/CMakeLists.txt hard-codes the library version number (libisis3.6.0.${SO})These should be consolidated so we don't have to maintain 3 places for versioning.
Also, the isis3_dependencies repo defines versioning for isis3 in its recipes/isis/meta.yaml file.
Using the conda dependencies, configuration fails with a FORTRAN_LIBRARY not defined error. Both the conda env and the underlying OS have libgfortran.so.3 installed. It looks like the error is being caused within the FindCholmod.cmake script.
Using a fresh install of anaconda on a new laptop running Fedora 28, I tried to create a conda environment using the environment.yml file in the ISIS3 directory of a fresh git clone and the error message below was the result.
Has anyone else used the environment.yml file to setup their environment or is everyone else using something internal? And, is there a specific version of conda I should be using? (I'm using 4.5.11)
(base) bash-4.4$ conda env create -f environment.yml -n ISIS3
Solving environment: failed
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<
Traceback (most recent call last):
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/exceptions.py", line 819, in __call__
return func(*args, **kwargs)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda_env/cli/main.py", line 74, in do_call
exit_code = getattr(module, func_name)(args, parser)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda_env/cli/main_create.py", line 108, in execute
installer.install(prefix, pkg_specs, args, env)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda_env/installers/conda.py", line 35, in install
unlink_link_transaction = solver.solve_for_transaction(prune=getattr(args, 'prune', False))
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/solve.py", line 518, in solve_for_transaction
force_remove, force_reinstall)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/solve.py", line 451, in solve_for_diff
final_precs = self.solve_final_state(deps_modifier, prune, ignore_pinned, force_remove)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/solve.py", line 180, in solve_final_state
index, r = self._prepare(prepared_specs)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/solve.py", line 592, in _prepare
self.subdirs, prepared_specs)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/index.py", line 215, in get_reduced_index
new_records = query_all(spec)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/index.py", line 184, in query_all
return tuple(concat(future.result() for future in as_completed(futures)))
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/subdir_data.py", line 95, in query
self.load()
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/subdir_data.py", line 149, in load
_internal_state = self._load()
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/subdir_data.py", line 246, in _load
_internal_state = self._process_raw_repodata_str(raw_repodata_str)
File "/home/kberry/anaconda3/lib/python3.7/site-packages/conda/core/subdir_data.py", line 369, in _process_raw_repodata_str
info['fn'] = fn
TypeError: 'NoneType' object does not support item assignment
`$ /home/kberry/anaconda3/bin/conda-env create -f environment.yml -n ISIS3`
environment variables:
CIO_TEST=<not set>
CONDA_AUTO_UPDATE_CONDA=false
CONDA_DEFAULT_ENV=base
CONDA_EXE=/home/kberry/anaconda3/bin/conda
CONDA_PREFIX=/home/kberry/anaconda3
CONDA_PROMPT_MODIFIER=(base)
CONDA_PYTHON_EXE=/home/kberry/anaconda3/bin/python
CONDA_ROOT=/home/kberry/anaconda3
CONDA_SHLVL=1
MANPATH=/usr/share/lmod/lmod/share/man:
MODULEPATH=/etc/modulefiles:/usr/share/modulefiles:/usr/share/modulefiles/Linux:/
usr/share/modulefiles/Core:/usr/share/lmod/lmod/modulefiles/Core
PATH=/home/kberry/anaconda3/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/b
in:/bin:/usr/local/sbin:/usr/sbin
REQUESTS_CA_BUNDLE=<not set>
SSL_CERT_FILE=<not set>
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
active environment : base
active env location : /home/kberry/anaconda3
shell level : 1
user config file : /home/kberry/.condarc
populated config files :
conda version : 4.5.11
conda-build version : 3.15.1
python version : 3.7.0.final.0
base environment : /home/kberry/anaconda3 (writable)
channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/free/linux-64
https://repo.anaconda.com/pkgs/free/noarch
https://repo.anaconda.com/pkgs/r/linux-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/pro/linux-64
https://repo.anaconda.com/pkgs/pro/noarch
package cache : /home/kberry/anaconda3/pkgs
/home/kberry/.conda/pkgs
envs directories : /home/kberry/anaconda3/envs
/home/kberry/.conda/envs
platform : linux-64
user-agent : conda/4.5.11 requests/2.19.1 CPython/3.7.0 Linux/4.18.10-200.fc28.x86_64 fedora/28 glibc/2.27
UID:GID : 76399:1800
netrc file : None
offline mode : False
An unexpected error has occurred. Conda has prepared the above report.
If submitted, this report will be used by core maintainers to improve
future releases of conda.
Would you like conda to send this report to the core maintainers?
This is in PR: #532. Was waiting on minor feedback to the other test in the PR, though.
It seems it would make a bit more sense to leave isisdeps to dependencies and move the recipe to build ISIS3 into this repo under a conda folder.
See Ticket 5521.
https://github.com/USGS-Astrogeology/ISIS3/wiki/Managing-Custom-ISIS-Dependencies-(WIP)
I have a PR opened for this: #532. Was hoping to get feedback on whether these tests should be parameterized? The PR includes the parameterized version of the tests, but I also have a non-parameterized approach in the code that is commented-out.
At
https://isis.astrogeology.usgs.gov/documents/InstallGuide/index.html
Where the instructions indicate to run isis3VarInit.py by specifying different arguments to isis3VarInit.py, the line reads:
./$CONDA_PREFIX/scripts/isis3VarInit --data-dir=[path to data directory] --test-dir=[path to test data directory]
Which has a few of issues:
Update README so it contains:
Information on where to install ISIS3 to for end-users ("If you are looking to install ISIS3 to run its applications, please see this installation guide"), which would point to our website's update installation guide.
Many repos have README's that tell developers how to get started setting up their environment to develop in the project, including installation of dependencies and compilation instructions (we have a lot of this information in the wiki already, so we could migrate that here).
It may be useful to put a link to the Contributing.md document for developers.
Feel free to comment for any ideas or suggestions.
Can this software be used to create a DEM using low altitude, < 400 ft, drone photos which are GPS geotagged?
If so are there any pipelines or usage examples?
Thanks
The current cronjob needs to be updated for testing the cmake branch.
When trying to set up the isis3 dependencies environment from our environment.yml file, the following error is issued:
ResolvePackageNotFound:
- curl==7.55.1=0Looking at conda-forge's curl packages, the linux-64/curl-7.55.1-0.tar.bz2 file has the broken label. All of the linux 7.55.1-0 versions have the broken label, so it will not be found by conda using our environment specification (conda looks for main label packages).
This can be fixed quickly by changing the version to a higher package version in the main label hosted by conda-forge.
However, this potentially brings up some questions. I'll post these in a separate issue.
Right now, findfeatures does very rudimentary checks for overlaps between images. This has been worked around by using isisminer's overlap calculations and filtering. In order to make findfeatures more usable without isiminer, and to help handle errors in isisminer configs more gracefully, we should add the ability to recheck image footprint overlaps in findfeatures.
This is coming largely from comments on #556
Title says it all:
% cat $ISISROOT/version~
3.6.0 # Public version number
10-26-2018 # Release date
beta # release stage (alpha, beta, stable)
It appears the PostgreSQL library is not installed in the Anaconda isis3 environment. This means database access in ISIS3 (and this environment) to PostgreSQL databases may be broken. Specifically, the runtime dependencies for the Qt SQL PostgreSQL driver are:
zion[326]: otool -L ~/miniconda3/envs/isis3/plugins/sqldrivers/libqsqlpsql.dylib
~/miniconda3/envs/isis3/plugins/sqldrivers/libqsqlpsql.dylib:
@rpath/../plugins/sqldrivers/libqsqlpsql.dylib (compatibility version 0.0.0, current version 0.0.0)
@rpath/libQt5Sql.5.dylib (compatibility version 5.9.0, current version 5.9.6)
/System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
@rpath/libQt5Core.5.dylib (compatibility version 5.9.0, current version 5.9.6)
**@rpath/libpq.5.dylib (compatibility version 5.0.0, current version 5.10.0)**
@rpath/libc++.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4)The highlighted PostgreSQL library (libpq) is nowhere to be found in the Python isis3 env. Looks like simply installing PostgreSQL will solve this problem.
FYI, Sqlite and MySQL looks to be intact.
Prerequisites:
Requirements:
address any major issues in the release candidate
Supports CentOS7 for development
Post notification about release in forum / news
Document this process as you go
It looks like /usgs/pkgs/isis3.6.0/isis/scripts/isis3Startup.sh is using the incorrect default for $ISISROOT and this is causing the wrong bin directory to be set. As I understand it, the correct default for $ISISROOT should be /usgs/pkgs/isis3.6.0/install
However, when I run source /usgs/pkgs/isis3.6.0/isis/scripts/isis3Startup.sh, my $PATH gets updated to include /usgs/pkgs/isis3/isis/bin, but this directory no longer exists in 3.6.0. As a result, I can't run any ISIS3 programs.
I haven't tested the analogous startup script for CSH, so I don't know if that script has the same issue. Either way, this should only affect internal USGS users because external users are expected to install 3.6.0 through conda. I have confirmed that this has broken PDS Services (MAP2 and POW).
Not entirely sure what the plans are for a binary distribution of ISIS3/cmake are (exclusively through Anaconda?) but it appears currently all the runtime library dependencies are linked to the Anaconda isis3 env install. Specifically, there are no runtime libraries or plugins in $ISISROOT/3rdParty. This may cause problems for system-wide distributions for ground data processing systems as the individual/account used to pull ISIS3 and install in a traditional setting may not be accessible in all situations causing runtime breakage.
I tested a potential solution on my Mac that moved aside the ~/miniconda/envs/isis3/lib to lib.org and then simlinked $ISISROOT/3rdParty/lib -> ~/miniconda/envs/isis3/lib.org (qview, after the move and before the simlink, failed as expected with a library load error). This worked great! Which means adding a “make dist” or “make deploy” target that simply copies/installs all of ~/miniconda/envs/isis3/lib and plugins to 3rdParty like was done before, or something similar, appears to work just fine.
I had the same issue with having to add the conda-forge channel, but once past that, the install step fails with a dependency conflict:
bash-3.2$ conda install -c usgs-astrogeology isis3
Solving environment: failed
UnsatisfiableError: The following specifications were found to be in conflict:
- isis3 -> armadillo==8.200.0 -> arpack -> *[track_features=blas_openblas]
- qtconsole
Use "conda info <package>" to see the dependencies for each package.
Not sure how to proceed. This is on MacOS 10.13.6 (High Sierra)
Prerequisites:
Requirements:
There is a lot of housekeeping to do because of simultaneously creating new infrastructure issues with GitHub issues and addressing existing Redmine issues.
Installed both Anaconda and ISIS.
ISIS worked perfect.
When trying to launch Spyder via the terminal, get the following wrong message:
——————————————————————————————————————
(base) 192:~ zhiyongxiao$ spyder
objc[8381]: Class RunLoopModeTracker is implemented in both /Applications/anaconda3/envs/python36/lib/libQt5Core.5.dylib (0x1097d0a80) and /ISIS3/isis/3rdParty/lib/QtCore.framework/Versions/5/QtCore (0xb16707980). One of the two will be used. Which one is undefined.
objc[8381]: Class NotificationReceiver is implemented in both /Applications/anaconda3/envs/python36/lib/libQt5Widgets.5.dylib (0xb0c82c1c8) and /ISIS3/isis/3rdParty/lib/QtWidgets.framework/Versions/5/QtWidgets (0xb16e71418). One of the two will be used. Which one is undefined.
objc[8381]: Class QCocoaPageLayoutDelegate is implemented in both /Applications/anaconda3/envs/python36/lib/libQt5PrintSupport.5.dylib (0xb12064ef0) and /ISIS3/isis/3rdParty/lib/QtPrintSupport.framework/Versions/5/QtPrintSupport (0xb169aaec0). One of the two will be used. Which one is undefined.
objc[8381]: Class QCocoaPrintPanelDelegate is implemented in both /Applications/anaconda3/envs/python36/lib/libQt5PrintSupport.5.dylib (0xb12064f40) and /ISIS3/isis/3rdParty/lib/QtPrintSupport.framework/Versions/5/QtPrintSupport (0xb169aaf10). One of the two will be used. Which one is undefined.
QObject::moveToThread: Current thread (0x7fa115c41eb0) is not the object's thread (0x7fffb1218380).
Cannot move to target thread (0x7fa115c41eb0)
You might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
This application failed to start because it could not find or load the Qt platform plugin "cocoa"
in "".
Available platform plugins are: cocoa, minimal, offscreen.
Reinstalling the application may fix this problem.
/Applications/anaconda3/envs/python36/bin/pythonw: line 3: 8381 Abort trap: 6 /Applications/anaconda3/envs/python36/python.app/Contents/MacOS/python "$@"——————————————————————————————————————
Please advice.
Notes from Trent
Not perfect sailing here for install. I am trying the new recipe on WSL (windows running Ubuntu 16.04.4 LTS). I usually have to fight a little but this time I am stuck on a QT issue.
Steps in notes.
I tried this:
sudo apt-get update
sudo apt install x11-apps
sudo apt-get install lxde
But now I get a QT error when it appears QT is nicely available.
libQt5Core.so.5: version `Qt_5.9' not found (required by qview)
I googled and found this:
sudo apt-get install qt5-default
this still doesn’t work. Here is my QT version
qmake --version
Using Qt version 5.9.6 in /home/thare/anaconda/envs/isis3/lib
At this point I am stuck…
BTW, there a few more minor comments in the file also. But I will try on a typical Linux system also. Perhaps an Ubuntu or Centos new VM.
Thus far I do like the new install environment. Perhaps we might need a Troubleshooting section (for those odd cases as we roll this out). Perhaps linked to a Github Wiki or ...? I think "library" hell (aka DLL hell) will be our biggest issue getting all these library quirks ironed out.
I may have more comments on the wording, but just wanted to get an initial "I am stuck" back to you all.
data: /work/users/lweller/Isis3Tests/FindFeatures/cvException
isisversion: isis3.6.0rc and isis3beta2018-09-18 where I initially encountered the problem via a cluster run. Was hoping this was a node thing....
error:
terminate called after throwing an instance of 'cv::Exception'
what(): /usgs/pkgs/local/v006/src/opencv/opencv-3.1.0/modules/core/src/lapack.cpp:798: error: (-215) type == CV_32F || type == CV_64F in function invert
./run.csh: line 2: 7791 Aborted (core dumped)
command:
findfeatures algorithm=fast/brief maxthreads=7 match=N1500060756_2_callptr.cub fromlist=N1500060756_2_callptr_fromlist.lis fastgeom=true geomtype=camera epitolerance=3.0 ratio=0.65 hmgtolerance=3.0 networkid=N1500060756_2_callptr pointid='N1500060756_2_callptr_?????' onet=N1500060756_2_callptr.net tolist=N1500060756_2_callptr_cubes.lis tonotmatched=N1500060756_2_callptr_notmatched.lis description='Create image-image control network' debug=true debuglog=N1500060756_2_callptr.log
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.