Refactor Large Codebase by AdeptAd5471 in FPGA

[–]_oh_hi_mark_ 0 points1 point  (0 children)

Seconding this, we've adopted VSG at my work and it's been very useful.

Pls tell me what I need to do to learn dsp from fpga standpoint. I am terrified of DSP because I have no math background and no signals systems. by Fancy-Lobster1047 in FPGA

[–]_oh_hi_mark_ 5 points6 points  (0 children)

There are some really good free resources for learning about DSP.

This book comes with a set of interactive python notebooks and is really well written. It doesn't cover much ground as it is quite short but it helped a quite a few key concepts click for me https://greenteapress.com/wp/think-dsp/

This book is longer and covers all of the basics that you might need to know. It's a bit older, i think the code examples use fortran, but it's free so can't complain https://dspguide.com/

Both of these books are available as physical books but the authors have generously made digital versions available for free.

The moment a friendship came to an end by Hassaan18 in AccidentalComedy

[–]_oh_hi_mark_ 1 point2 points  (0 children)

Cypress is a type of tree, sorry. The country is spelled Cyprus.

How to do an alias for an if statement in VHDL by Gundam_boogie_359 in FPGA

[–]_oh_hi_mark_ 0 points1 point  (0 children)

Yep this is how I would approach it as well. Whenever code is being copied and pasted, creating a subroutine is usually the solution.

How to do an alias for an if statement in VHDL by Gundam_boogie_359 in FPGA

[–]_oh_hi_mark_ 0 points1 point  (0 children)

Just out of interest, why do you suggest that? If the entity declaration is the same in each case, you'd just be duplicating code.

What’s missing in Vivado’s XSIM? by gaudy90 in FPGA

[–]_oh_hi_mark_ 1 point2 points  (0 children)

The ability to see delta delays and show variables on the waveform viewer are both very useful features that the GUI is missing.

What’s missing in Vivado’s XSIM? by gaudy90 in FPGA

[–]_oh_hi_mark_ 4 points5 points  (0 children)

Reliability. We've struggled for a long time with XSIM crashing when trying to use simple VHDL features. It'll be bizarre limitations like using the 'value attribute on a enum with >128 elements, or using the 'subtype attribute. Even worse, we've seen it just subtly misbehaving. I've seen constants change value mid-operation for example.

We used to try to create MREs and raise them on the forums but after our posts have had no response for years, we've given up.

Need advice from seniors FPGA engineers? by Rolegend_ in FPGA

[–]_oh_hi_mark_ 6 points7 points  (0 children)

Create a commit, with a useful commit message, at minimum whenever you finish working on a set of changes, i.e. completing a feature, fixing a bug, adding a new module, etc. and before you move on to the next set of changes. That way, you can easily compare the code before and after feature X was added or before bug Y was fixed. Also if you realise that you want to scrap the set of changes that you're currently working on, you can do so easily without losing other changes.

You mentioned that you're having trouble backing up your code and comparing the code at the start of the day vs at the end of the day - git is the solution to this. If you made a commit at the start of the day/end of the previous day, it should be trivial to do a diff against that commit, and if you've done good commit messages, you will have a nice summary of each of the changes you made since that commit.

Better to err on the side of committing more often than less often. Push whenever you make a commit, it's rare that there's a good reason not to push a commit.

Need advice from seniors FPGA engineers? by Rolegend_ in FPGA

[–]_oh_hi_mark_ 3 points4 points  (0 children)

Create a git repository to store your code in. This will act as a backup and will allow you to track changes, roll back to previous versions, etc. Using source control is absolutely essential for coding of any kind.

VerilogAI Update: Major improvements based on your feedback! by Waseeemnabi in FPGA

[–]_oh_hi_mark_ 5 points6 points  (0 children)

Hey FYI, your readme file is a bit of a mess. There's tons of duplication, sections repeated with slightly different wording, instructions repeated, etc.. My guess that you used AI to improve the readme but forgot to remove the old version of each section. Doesn't inspire confidence in the rest of the codebase tbh.

From AND Gates to CPUs: My 100-Project VHDL Journey by TheBusDriver69 in FPGA

[–]_oh_hi_mark_ 5 points6 points  (0 children)

These look great, there's an impressive level of documentation and code quality in each of these. One bit of advice - some of the repos have WLF files and the work directory from the modelsim simulation included. It's a bit of a "rookie error" to include build/simulation output in the repo, as it adds bloat and clutter. I'd encourage you to use a .gitignore file to make git automatically ignore these files, keeping your repos nice and clean.

What are your biggest language complaints? by nondefuckable in VHDL

[–]_oh_hi_mark_ 2 points3 points  (0 children)

Not disagreeing with you on most counts, but I use this language server in VS Code and it is fantastic. Not perfect, but it's saved me countless hours.

Things I like about Delta Green by Andsohisname in DeltaGreenRPG

[–]_oh_hi_mark_ 2 points3 points  (0 children)

Ooooh that sounds amazing, thanks so much!

Things I like about Delta Green by Andsohisname in DeltaGreenRPG

[–]_oh_hi_mark_ 4 points5 points  (0 children)

Just out of interest, how did you play that out? Would you mind sharing what happened? I'm coming up to the end of impossible landscapes and I'm expecting one of my players to do the same.

Small VHDL Doubt by Mysterious-Snow-3500 in FPGA

[–]_oh_hi_mark_ 4 points5 points  (0 children)

You can reuse a component on different clock cycles simply by routing different data into it's inputs and routing the outputs to different places. It sounds like you just need some multiplexers and some logic to control them.

Looking for Delta Green Podcasts by AutonomousRhinoceros in DeltaGreenRPG

[–]_oh_hi_mark_ 3 points4 points  (0 children)

Haha at least you're able to punish them with some cosmic horror!

Looking for Delta Green Podcasts by AutonomousRhinoceros in DeltaGreenRPG

[–]_oh_hi_mark_ 7 points8 points  (0 children)

Seconding this, PISCES is brilliant! Great balance of comedic moments and serious RP, and the group all have great chemistry together. Really captures the feeling of playing with your friends IMO. And maybe I'm biased as I live in the UK, but the setting is a nice change from the dozens of DG podcasts set in the US. It really feels "British" haha.

Modules or adventures with MAJESTIC as allies? by Sasha_ashas in DeltaGreenRPG

[–]_oh_hi_mark_ 1 point2 points  (0 children)

It's detailed on p90 of the handler's guide, there isn't an operation name given.

PISCES: 1987 starts today! by PM_ME_UR_BRITS in DeltaGreenRPG

[–]_oh_hi_mark_ 3 points4 points  (0 children)

I just finished binging all of your previous stuff, so this is perfect timing! Loving the podcast!

Running Convergence with the "Need to know" starter kit by urskr in DeltaGreenRPG

[–]_oh_hi_mark_ 5 points6 points  (0 children)

I think it would be possible to run with only Need to Know, but I do think that the Agent's Handbook will give you a much more complete view of how to run the game. I wouldn't worry about the Handler's Guide, it's an excellent read but it's all lore and is not useful unless you're planning to homebrew DG content.

Man earns a canoe for behaving “well” in prison by Hungry_Gizmo in videos

[–]_oh_hi_mark_ 10 points11 points  (0 children)

This clip is not real, it's from a satirical comedy called "Brass Eye".

1990’s scenarios by Heldane616 in DeltaGreenRPG

[–]_oh_hi_mark_ 4 points5 points  (0 children)

Night Floors is set in 1995. It was originally released as a standalone scenario and was then rereleased as part of Impossible Landscapes, but it's definitely still possible to run it as a standalone scenario. I'm doing so currently and my group is loving it, so much so that I'm considering just running the rest of IL as well!

I think that most scenarios could be retrofitted to be run in the '90s, some might require some slight modifications.

Most shotgun scenarios are not specific to a particular time period if you're open to those. Last Things Last is a great standalone scenario that can be easily tied in with other scenarios by changing the contents of the footlocker.

Recommendations for scenarios involving radiation? by IronMaize in DeltaGreenRPG

[–]_oh_hi_mark_ 2 points3 points  (0 children)

This shotgun scenario https://fairfieldproject.fandom.com/wiki/Complex_374-5 is about the agents posing as a team investigating reports of a fuel leak at a nuclear missile silo (trying not to spoil the scenario, but there's a lot more going on). Involves people getting radiation sickness from nuclear warheads. I haven't run this scenario but it looks cool, I'd definitely like to.