Creating Log-normal distribution curves with Jstat using json data - json

There is no documentation for jStat. As of 2012-11-06 (per the documentation page): "The jStat API documentation is still being compiled."
I want to plot log-normal curves with JSON data. Can anyone who have worked on this throw some light on how to get started?

The project repo is at https://github.com/jstat/jstat
Current documentation for jStat is at http://jstat.github.com/
The webpage is using a version of jStat that is no longer worked on. The current project has focused on extending functionality so it is more easily integrated into your graphing library of choice. There is a simple UI repo (but hasn't been worked on much) at https://github.com/jstat/jstat-ui

Related

How load custom .net dll with accoreconsole.exe in Design Automation with all AutoCAD DLL's

I have created a AutoCAD custom .net dll for the desktop version which had some operation.
Adding multiple empty drawing documents.
Opening the existing drawing document and copying the required blocks in the newly created drawing document.
Performing some operation on them, discarding all the unnecessary drawing documents and saving one of them as an output drawing document.
I had a query regarding opening the existing document and adding the empty document using Design Automation API but I couldn't achieve it with Design Automation.
As I explored I found that only AcCoreMgd.dll and AcDbMgd.dl are allowed with accoreconsole.exe.
Load custom .net dll inside accoreconsole.exe
DLL's used by AutoCAD custom .net project for desktop version are (AcCoreMgd.dll,AcCui.dll,AcDbMgd.dll,AcMgd.dll,AcTcMgd.dll,AdUIMgd.dll)
I wanted to use all the above DLL's with Design Automation for AutoCAD.
Will you please let us know how we can use desktop versions like support in Design Automation for AutoCAD?
It is not possible to add other modules when working with Design Automation or AccCoreConsole. Please note AcCoreConsole is a Headless part of AutoCAD in other words no UI libraries are permitted. Following are the libaries that a crx app should bind.
Where XX - module version of AutoCAD release for more details
If you are developing a .NET module, you need to use following Nuget
ac1stXX.lib
acdbXX.lib
acdbmgd.lib
AcDbPointCloudObj.lib
acgeXX.lib
acgiapi.lib
acismobjXX.lib
AcMPolygonObjXX.lib
AcSceneOE.lib
axdb.lib
rxapi.lib
acbrXX.lib
acgexXX.lib
AdImaging.lib
AdIntImgServices.lib
AecModeler.lib
AsdkHlrApiXX.lib
acapp_crx.lib
AcCamera.lib
accore.lib
AcFdEval.lib
AcPublish_crx.lib
Why do you need to open mutilple documents ?, you can insert multiple blocks from different drawings in to Host drawing. Make modifications, save and send to your Server.

Which to use for Prismic project, prismic-javascript, #prismicio/client, prismic-dom, prismic-reactjs

Cant find a distinctive difference on their docs so asking here.
prismic-javascript or #prismicio/client or prismic-reactjs or prismic-dom
They all are npm packages.
Can someone explain the 4 separate packages and when to use one over the other.
My assumptions.
prismic-javascript is for connecting directly to the v2 api.
#prismicio/client is the same package as prismic-javascript. Still confused about this.
prismic-reactjs is just react components that you can pass data to
from prismic-javascript api results.
prismic-dom is used for plain vanilla JavaScript projects to render dom elements that you pass data to
from prismic-javascript api results.
Am I correct with the above assumptions ?
me, thanks for the question.
prismic-javascript is the old version, where #prismicio/client is version 4 of the library. I definitely see how that's confusing, I'm working on getting the references cleaned up so that's more straightforward.
prismic-dom contains helpers for things like rendering "Rich Text" fields to the DOM. They come from the API as JSON, so you need something like this to turn it into HTML.
prismic-reactjs is similar to prismic-dom, but turns Rich Text fields into JSX to work with React projects.
So if you're working on a vanilla JavaScript site, you'll use #prismicio/client + prismic-dom.
If you're working on a React app, you'll use #prismicio/client + prismic-reactjs.

Get output of InventorServer Engine as stp file or should I use ModelDerivative API?

Referring to the attached image taken from today's webinar:
(could someone with at least 10 reputation post this image: http://i.imgur.com/LwUHnce.png)
Once, for example, changed parameters, could my appPackage (i.e. changeParamsPlugin) do something like this?
doc.SaveAs(Path.GetDirectoryName(doc.FullDocumentName) + "\\" + outputFile + ".stp", True);
and then file be downloaded like this:
DownloadToDocs(resultUrl, AppProperties.OutputFile + AppProperties.StepExtension); // Output to MyDocuments
Or afterwards should I use model derivative API to translate output in a step file?
First thing to note on this is that Inventor in Design Automation is currently in Private Beta so using this in production is not currently available. If you're interested in exploring our private beta please contact me.
As far as guidance goes for this question, in general translations should be done with the ModelDerivative API in Forge. If you need "custom" work done prior to a translation then using Design Automation is the right way to go.
The AutoCAD "Engine" is available in production for Design Automation, while what you list above is the presentation I gave today with the disclaimer that this is not available in production.

Always include the latest version of custom Google Drive library

I'm trying to link a custom library to a document that will be copied and shared with many people. I want to have all documents link to the latest version of the library, so when I modify the library I don't have to access all the documents to change the link.
This is the scenario:
I created a simple single function library (e.g. library TestLib, function foo()), and saved a first version of it. Then I've created a SpreadSheet with a script that generates a user menu that calls function TestLib.foo(). I've linked version 1 of the library to the script. Now I want to make several copies of the document, one for each people who will need it. The problem is that these documents are linked to version 1 of the library. If I made a change to the library and create a version 2, I have to manually re-link all documents to the new version. That's gonna be lot of work...
Is there a way to have the script to always link to the latest version?
NOTE: the library project is shared in read-only mode (people won't collaborate with the code. They just call foo() from the menu when needed).
Thank!
MIX
I made a new test, trying to overtake the version "limitation" problem.
The idea is a little complicated, but promising. The spreadsheet calls a function in library LinkLib: this library will be saved in a single version and the source code will never modified. The library function simply calls a function on another library (MainLib), whom source code can change over time. Spreadsheet doesn't need to change the version of the linked library (there will never be new version of BaseLib source code), while BaseLib can change the version of MainLib linked if I made changes in MainLib's source code..
The problem is: changing the version of a linked resource is treated as a source code modification. So you need to save a new version of BaseLib to actually use an updated version of MainLib's function.
Hope this mess is somewhat clear...
It makes sense that the described version management behave like this. But damn, I'm still stuck with this problem...
this is possible but with a risk. simply use "development mode" for all documents using the library. whenever you update the library it will include the new code automatically.
the risks are that you will have to be careful to never save an intermediate/partial change as all changes need to not break anything. this can be tricky and is best to have a separate library copy to use when making and testing changes. once tested you may copy all files and "save all" together so the script doesnt have partial saves.
basically you lose the development facilities of using versions.
read more about library development mode in the official docs.

Uploading a file using TCL

I'm a newbie working on OpenACS architecture and need to upload a .xml file through TCL. I went through the documentation and tried to work around with the code mentioned here: http://wiki.tcl.tk/13675
However, I'm unable to understand the code and the copy-paste won't work. Could someone please suggest a easier working way to upload a file in TCL? A working code would be of great help.
I need to upload a file through a HTTP form(with input type file parameter) and I'm asking for server-side code.
OpenACS already has file uploading built in (assuming you're using the OpenACS form builder aka ad_form, template::form - it has many names!). The specific widget you need to use is template::widget::file
A worked example is in the General Comments package (see file-ae.adp, file-add.tcl and file-add-2.tcl):
http://cvs.openacs.org/browse/OpenACS/openacs-4/packages/general-comments/www/file-ae.adp?r=1.6
http://cvs.openacs.org/browse/OpenACS/openacs-4/packages/general-comments/www/file-add.tcl?r=1.4
http://cvs.openacs.org/browse/OpenACS/openacs-4/packages/general-comments/www/file-add-2.tcl?r=1.6
Specifically, look out for the 2 ad_page_contract parameters, and follow those variables down through the code:
upload_file:notnull
upload_file.tmpfile:tmpfile
Re-inventing network protocols is not so much worth in most cases, so I'd like to recommend using proven community libs. From my personal experience, I'm pretty glad to deal with libcurl (see http://curl.haxx.se/libcurl/tcl)