![]() WARNING some basic tools produce results incompatible with version 1.00.XX Test-suite will fail due to changes in minctracc All files will be installed into /opt/minc/1.9.18 in order to co-exist with other versions of minc-toolkit This version includes ITK-4.13.0, latest version of Elastix, ANTs and C3D - all with minc support. Use this version if you need only basic minc tools (i.e register/Display/xdisp) or you are running a legacy image processing pipeline that does not require new tools. The standard minc-based programs are kept up-to date, but new experimental software is not included. 1.0.XX - is a legacy version that still includes all the latest versions of the minc tools, and several programs based on ITK 3.20.Also includes new experimental software based on ITK 4.XX and recent versions of ANTS and Elastix. 1.9.XX - includes the same standard minc-tools as version 1.0.XX, but sometimes with updated parameters (minctracc so far is the only such program).It includes most of the standard minc tools, Display, Register and a basic image processing pipeline based on the one developed for NIHPD project (standard_) Everything is currently installed in /opt/minc/VERSION, to avoid conflict with standard /usr/local/bic location. This toolkit contains most of the commonly used minc tools in one precompiled 32 and 64bit binary packages of Debian, Ubuntu, RedHat and Mac OS X. This software repository contains open-source tools developed at the McConnell Brain Imaging Centre, Montreal Neurological Institute The main documentation site for this repository is located at wikibooksĪlso, concise man pages for various minc tools are located at /man-pages SupportĬontact or if you have any questions MINC Tool Kit Additional software ported to support MINC file format.Really interesting, thanks! I'll look into that.BIC-MNI Software repository About the project Contents: > I ended up using which somehow manages to force tcp traffic through a socks5 proxy. You can file a proper issue about this at, I'd love to know what's going on there and get this fixed. Probably best to debug this outside of a HN thread though :-). It's always very hard to know if my configuration is representative of normal devs for any given language/tool. Maybe you have some other Go package manager configuration that conflicts with this? I'd be very interested to know about that if so, I'm sure there's others with the same thing. ![]() I just tested, and `go get /x/oauth2` seems to work fine for me, I can see all the requests being happily intercepted immediately: Ĭan you see the 500 in HTTP Toolkit, and any more info there (in the body or as an error at the top) related to that? Or can you see a "certificate rejected" message? If nothing turns up there at all then yes, something must be overriding the proxy configuration. > If you try to use go's package manager, example: `go get /x/oauth2` But I guess I can see why some like postman etc for exploration - so far i prefer swagger for that (or soapui for xml/soap - preferably running soapui under httpkit for the best of both worlds). I feel like postman etc is closer to println Debugging, while just intercepting the traffic is more like using a real debugger. Strongly considering purchasing httpkit - but so far I've just needed it occasionally. I don't know about altering requests "in flight" - I typically re-issue the request via curl or my application server (eg: rails console or debugger breakpoint). I find that httpkit (or just mitmproxy) often gives me decent insight to the actual requests. Either before or after a request is executed to add to the headers or parameters of the request or getting the results of the request. > One of the issues I found with http clients I looked into is that they often don't provide enough functionality to hook into the request process. Different response Httpie vs Httpx ( python ).Works well, lets you stay 100% open source, which is good for everybody and encourages contributions, and you can still make enough money to fund development (never going to make anybody a billionaire, but that's not the point). ) but it's a non-trivial hassle to fork everything and hook it all up, and means ongoing maintenance work to manage a fork forever, so at the price it's not really worth any serious professional's time (and I give out free licenses for everybody would contributes to the code anyway). Yes, anybody can fork the project and remove the payment checks (here. comfortably enough income as a solo bootstrapped project that I can work on open source full time) doing a freemium approach that's 100% open-source for ![]() This point is interesting, because it assumes the only way to do premium is with a closed-source version, losing the open-source benefits. Monetization via Paid Premium Version / Open Core
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |