[OpenSPIM] [openspim] OpenSPIM

[Neil Anthony]

I concur!
I requested files 3 months ago and got lost in a discussion of file formats.
Pete, what file formats do you have available?

Thanks
Neil

On 11/19/2013 1:09 AM, HUANG, Chao-Hui wrote:
> Dear Luke,
>
> Appreciate for the arrangement. Truly appreciate.
>
> This is the file we found 
> (http://openspim.org/images/d/d1/Solidworks_build_up_3fps_cont_high_res.gif)
>
> Hopefully there is a solidwork file that is available for all users.
>
> Sincerely,
>
> Chao Hui
>
>
> On 19/11/2013 5:31 AM, Luke Stuyvenberg wrote:
>> Hi Chao Hui,
>>
>> I'm not sure that we have the entire assembly available for download, 
>> though I think that can be arranged. Our custom parts all have part 
>> files available on the parts list page, but I believe we used part 
>> files from the manufacturer for any part we didn't make ourselves. 
>> (If a part's SolidWorks file seems to be missing from the parts list, 
>> you can check 
>> http://openspim.org/index.php?limit=50&ilsearch=.stl&user=&title=Special%3AListFiles 
>> to see if it is uploaded on the wiki after all.)
>>
>>
>> I've forwarded your e-mail to our mailing list and to Pete Pitrone, 
>> who I believe knows more about the SolidWorks files -- he may be able 
>> to provide more information.
>>
>>
>> Pete: If you haven't already, could you please upload the completed 
>> assemblies? Probably they can be linked from 
>> http://openspim.org/Configurations -- thanks!
>>
>>
>> Hope this helps,
>> Luke
>>
>> On 11/17/13, "HUANG, Chao-Hui"  wrote:
>>> Dear Luke,
>>>
>>> Currently we are working on a project which is relevant to OpenSPIM. 
>>> I am wondering if you can kindly offer the solidworks source file of 
>>> OpenSPIM to us since we cannot fin any of them on the openspim web 
>>> site?
>>>
>>> Appreciate.
>>>
>>> Sincerely,
>>>
>>> Chao Hui
>>>
>>> On 30/5/2013 6:02 AM, Luke Stuyvenberg wrote:
>>>> Hi Chaohui,
>>>>
>>>> The classes from "3rdpartypublic\classext" should be identical to 
>>>> the classes in "bin_Win32\jars". The instructions say to use the 
>>>> files in classext because, before compiling mmstudio, they are not 
>>>> in bin_Win32 -- I think they are copied when mmstudio is compiled.
>>>>
>>>>
>>>> Compiling from source will download the latest binary executable, 
>>>> which might be why it doesn't match the executable in the zip file. 
>>>> The zip file is getting old, but I plan to replace it with a new 
>>>> version soon, which shouldn't have any of these problems.
>>>>
>>>>
>>>> The latest code from github shouldn't have this problem any more, 
>>>> and most users should be able to get rid of it by updating (Help -> 
>>>> Update Fiji).
>>>>
>>>>
>>>> Thank you for your help!
>>>>
>>>>
>>>> Sincerely,
>>>> Luke Stuyvenberg
>>>>
>>>>
>>>> On 05/29/13, HUANG Chao-Hui wrote:
>>>>> Hi Luke,
>>>>>
>>>>> Thanks for replying. I would like to provide more information 
>>>>> about the package.
>>>>>
>>>>> I am not sure but it might be because of inconsistent of the 
>>>>> source code. I've found it will have problems when using java 
>>>>> classes from 3rd party folder. I have some problems when I was 
>>>>> trying to compile it by my own (and yes I solved the not-to-snap 
>>>>> problem by build it from source code).
>>>>>
>>>>> Actually I even have to make some modification on the downloaded 
>>>>> source code. By following the instruction on OpenSPIM web site, it 
>>>>> will not generate the same binary executable as the mentioned zip 
>>>>> file. I think there are some inconsistent problem on the actual 
>>>>> souce code the source code you used to build the zip file, 
>>>>> including the 3rd party folder, perhaps different versions of the 
>>>>> jar files?), and the one which can be downloaded from the github.
>>>>>
>>>>> A more solid example is, when compiling, according to the 
>>>>> instruction, we have to import the classes from 
>>>>> ''3rdpartypublic\classext''. But when running it, I think the code 
>>>>> invoked the classes from jars folder in somewhere under 
>>>>> micromanager folder.
>>>>>
>>>>> I would like to suggest if that is possible, maybe it would be 
>>>>> better to to go for a full synchronization? Of course if you have 
>>>>> tested and verified the code from the github, this is not an issue 
>>>>> anymore.
>>>>>
>>>>> Sincerely,
>>>>>
>>>>> Chaohui
>>>>>
>>>>>
>>>>> On 29/5/2013 5:20 AM, Luke Stuyvenberg wrote:
>>>>>> Chaohui,
>>>>>>
>>>>>> Please pardon the delay in my reply. I tested the problem and 
>>>>>> it's just as you explained: the version of Micro-Manager in the 
>>>>>> ZIP file (1/31) won't snap an image more than once (though I 
>>>>>> found that by turning live mode on and then off again, it is 
>>>>>> possible to snap another image). I'm not certain what causes this 
>>>>>> problem, however, and it doesn't happen in the latest version 
>>>>>> (which is now on Github). You should be able to update the plugin 
>>>>>> using Help -> Update Fiji (Please be sure you get MMJ_.jar, 
>>>>>> MMCoreJ.jar, and any new DLL files as well.). Please let us know 
>>>>>> if this problem persists after updating!
>>>>>> We will hopefully be providing a new ZIP file soon as well, so 
>>>>>> that future users will not encounter this problem at all.
>>>>>>
>>>>>> Thanks,
>>>>>> Luke Stuyvenberg
>>>>>>
>>>>>> On 05/02/13, "HUANG, Chao-Hui" wrote:
>>>>>>> Dear Johnnaes,
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> May I ask if the OpenSPIM on Github is updated?
>>>>>>>
>>>>>>> Actually I really suggest to test the problem that I mentioned. 
>>>>>>> We've
>>>>>>> found that problem on PVCAM, and it can be happened either 64, 
>>>>>>> 32 bits
>>>>>>> on DemoCamera. Of course, if in the same configuration, it would 
>>>>>>> not be
>>>>>>> happened on your side, that will be another story :-)
>>>>>>>
>>>>>>> Sincerely,
>>>>>>>
>>>>>>> Chaohui
>>>>>>>
>>>>>>> On 29/04/2013 23:04, Johannes Schindelin wrote:
>>>>>>>> Hi Chaohui,
>>>>>>>>
>>>>>>>> On Mon, 29 Apr 2013, HUANG Chao-Hui wrote:
>>>>>>>>
>>>>>>>>> We are glad to see that the code will be updated soon.
>>>>>>>> Don't hold your breath, though ;-)
>>>>>>>>
>>>>>>>>> Just in the case that you might not aware. We found a problem 
>>>>>>>>> in 1/31
>>>>>>>>> binary version. When you click snap on the live window of MM, 
>>>>>>>>> you can
>>>>>>>>> only click one time. after the first time snap, the button is 
>>>>>>>>> not going
>>>>>>>>> to update the live view screen.
>>>>>>>>>
>>>>>>>>> This problem can be happened even using DemoCamera.
>>>>>>>>>
>>>>>>>>> Are you aware this?
>>>>>>>> No, I wasn't, and in fact, I did not have that problem. But 
>>>>>>>> then, I
>>>>>>>> haven't used the DemoCamera in a while...
>>>>>>>>
>>>>>>>> Ciao,
>>>>>>>> Johannes
>>>>>>>>
>>>>>>> -- 
>>>>>>> HUANG, Chao-Hui (Ph.D.)
>>>>>>> -----------------------
>>>>>>> Research Fellow
>>>>>>> Bioinformatic Institute, Agency for Science, Technology Research
>>>>>>> National University of Singapore
>>>>>>> Singapore Mobile: +65 92426558
>>>>>>> Singapore Office: +65 64788353
>>>>>>> Taiwan Mobile: +886 928338607
>>>>>>> Email 1: ch at mail2000.com.tw
>>>>>>> Email 2: huangch at bii.a-star.edu.sg
>>>>>>> WWW: http://web.bii-sg.org/~huangch/
>
>
> _______________________________________________
> OpenSPIM mailing list
> OpenSPIM at openspim.org
> http://openspim.org/mailman/listinfo/openspim
>