Some time ago I found the following youtube video by Ricardo Oliveira of a small NXT plotter that crawls over a whiteboard. It has two strings that can be shortened through coils and with this, it controls its position on the whiteboard.
Here is a screenshot from the video.
The whole idea beh...
and still only 3 upvotes and no one dares to answer. I'm a bit disappointed, because I thought for a real proffesional LEGO engineer it is only a little work to reproduce such a simple design.
@R.M. I have a question about your git/mma guidelines. I'm having troubles understanding what is the workflow in case of having full development repository (with remote a) and "deployed" repository for users (remote b with only App/App.m structure).
@R.M. I mean, I'm not quite sure how to set it up with minimal effort. And how the "deployed" repository get's updates from main.
@R.M. btw I'm not a git ninja but I'm familiar with git
So the sidebar got stretched by about 30%. No problem. This entails a change to the network-provided ads (not visible above certain rep thresholds) and to the community ads. No problem. Some old ads ran with some extra whitespace while they were updated. No problem. We need to update all our comm...
@Kuba Good questions. I tried it but didn't really work out well (see the problems you ran into with IGraphM). I think I am not going to do this any more in the future. GitHub now allows uploading a "release". I'm going to have a script that builds this release and upload it manually when a new version comes out. I won't keep a deployed repo.
This should also fit with Workbench's workflow. In Workbench you build the package when it's ready: this generates the package structure and documentation. (No, I don't actually use that feature, but it makes sense.)
@Kuba The way I've done this is to keep my "dev repo" (A) in the development directory, and the "deployed repo" in $UserBaseDirectory/Applications/MyProject (B). When I want to make a release, I use a deploy script that converts the package from dev structure to deployed structure (which automatically goes to $UBD/Applications/MyProject by default) and then commit that to master. The downside of this approach is that you will have to maintain 2 repositories.
If you make both of them public, then the users might get confused as to which is the "real one". You'll also end up splitting Github issues between two repos. If you make A private and only B public, then you solve some of that problem but now it's hard for another person to contribute to your package because they're only seeing the deployed code.
This is why I suggested an "orphan branch" approach in my answer. This is what was done with MATLink. You can see that master does not have anything in common with develop and master serves as the deployed branch. This is so that if some users want to download the app using git clone and stay updated with git pull, then they will be able to do so easily.
This is also cumbersome though... you have to keep track of two different branches, make sure that they're in sync, etc. Right now, MATLink master and the most up-to-date zip file available for download are out of sync.
I've come around to the idea that having the development repo up and giving people the zip file is the best approach. If you've not yet settled on an approach, I would recommend what @Szabolcs is doing — using Github releases and attaching a zip file to it.
Ah. I suddenly found a problem where discrete Markov processes and associated functions as implemented in Mma are of great help exploring the problem. It would be quite painful if I'd have to figure out it all myself from the start.
@R.M. Thanks for explanation, I was afraid that there isn;t anything straigthforward. I read a little bit about submodules but this is not a solution either :/
Wolfram SystemModeler is a tool for multidomain analysis. One area with many multidomain applications is hydraulics: fluid power systems. Fluid power is one of three main methods of transmitting power. The other two are mechanical transmission, via gears and shafts, and electrical transmission, via wires. In SystemModeler, all three can be used at the same [...]
@R.M. I agree. I'm pretty sure it's just a simple lookup, so the answer is not at all mathematical. That was my answer over on math.se. I flagged it for moderator attention and I'm pretty sure they'll send it back. I'm not sure what happens next, though.
Some time ago I found the following youtube video by Ricardo Oliveira of a small NXT plotter that crawls over a whiteboard. It has two strings that can be shortened through coils and with this, it controls its position on the whiteboard.
Here is a screenshot from the video.
The whole idea beh...
