Feature Request

To confirm you are on the correct branch, add the following the the end of ~/.bashrcsave it then either logout and login again or run from a terminal:

phillc54 wrote:

To confirm you are on the correct branch, add the following the the end of ~/.bashrc

 function parse_git_branch {
     git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/(\1) /'
 }
 PS1="\[\e[32m\]\$(parse_git_branch)\[\e[33m\]\h:\W \ \[\e[m\]"
 export PS1

save it then either logout and login again or run from a terminal:

source ~/.bashrc

Luckily I woke up a bit early today, so I had a few minutes before I have to leave for work.

Did the above, the "source ~/.bashrc" makes my terminal look funny now:

Any way to change that back?

At any rate, updated, ran it quick, it still does the exact same thing as last night.

phillc54 wrote:

Did a touristy day trip to Philly (mainly to see the Liberty Bell) and also to Intercourse several years ago.

You skipped the foreplay ???

tommylight wrote:

phillc54 wrote:

Did a touristy day trip to Philly (mainly to see the Liberty Bell) and also to Intercourse several years ago.

You skipped the foreplay ???

haha, yeah I was lookiing for it but no luck...

It will only show the git branch when you are in a valid git branch. If you don't like it remove the lines and run the source line again.

That is crazy, I cannot get it to go wrong. I will try on my machine tomorrow if I get time, I am only testing in sim mode.

phillc54 wrote:

It will only show the git branch when you are in a valid git branch. If you don't like it remove the lines and run the source line again.

No, it's ok, I just didnt know it was supposed to stay that way. It's good to know what branch I'm currently pointed at.

That is crazy, I cannot get it to go wrong. I will try on my machine tomorrow if I get time, I am only testing in sim mode.

Hmm, I'm not sure I know how to test in sim mode (to see if it would act normal in my sim mode vs a real machine).

As far as things that could be different, did you add Rod's Ohmic3.comp to the simulation you are running? That's about the only thing I could figure wouldn't be the same because. Off the cuff, I wouldnt know what difference that would make, but I guess we have to consider everything at this point.

snowgoer540 wrote:

As far as things that could be different, did you add Rod's Ohmic3.comp to the simulation you are running? That's about the only thing I could figure wouldn't be the same because. Off the cuff, I wouldnt know what difference that would make, but I guess we have to consider everything at this point.

No, I can't imagine that it would affect anything, all PlasmaC gets from it is the ohmic probe signal (I guess)

phillc54 wrote:

snowgoer540 wrote:

As far as things that could be different, did you add Rod's Ohmic3.comp to the simulation you are running? That's about the only thing I could figure wouldn't be the same because. Off the cuff, I wouldnt know what difference that would make, but I guess we have to consider everything at this point.

No, I can't imagine that it would affect anything, all PlasmaC gets from it is the ohmic probe signal (I guess)

Not sure either, but it does have output(s), because my hal connections file uses the or2 function to tie two outputs together so it turns the power supply on and off properly. I mean, I tend to agree, but at any rate, it is a variable.

If you want to try a sim, make a copy of your config directory. (with sim in the name to remind you) and copy the attached hal file and ini file into it.

phillc54 wrote:

If you want to try a sim, make a copy of your config directory. (with sim in the name to remind you) and copy the attached hal file and ini file into it.

Yea, I'll give it a go. It'll be interesting to see if it works normal in the sim for me. Thanks Phill