prompt-engineering VS alpaca-lora

An agent is a style of prompt that lets LLMs act as reasoning engines. It's also known as the ReAct pattern (which engineers are avoiding using for namespace collision reasions).

You can read a good intro example here: https://github.com/brexhq/prompt-engineering#react

Well, if developers get replaced by AI, then who are the managers going to manage :). I personally don't think AI is just going to replace us. The way we work will continue to change as new AI tools come out. I'm taking time to tinker with new tools and seeing how others do as well (e.g., I found Brex's tips and tricks for working with LLMs very insightful: https://github.com/brexhq/prompt-engineering).

I recognize there's plenty of catnip here when it comes to calling this "engineering" or not, however, whatever you want to call it (prompt fiddling?), the techniques are crucial if you want to achieve reasonably consistent output from current-state LLMs. As models improve concerns about context window limitations will be reduced and it will be easier to discern user intent.

These are good straight-to-the-point guides:

- Prompt Engineering by BrexHQ: https://github.com/brexhq/prompt-engineering

- OpenAI guidance: https://help.openai.com/en/articles/6654000-best-practices-f...

- https://devblogs.microsoft.com/dotnet/gpt-prompt-engineering...

- (great examples): https://www.deeplearning.ai/short-courses/chatgpt-prompt-eng...

tl;dr:

Brex's Prompt Engineering Guide (https://github.com/brexhq/prompt-engineering)

Here is a example: https://github.com/tloen/alpaca-lora/blob/main/finetune.py

In this blog post, I want to make it as simple as possible to fine-tune the LLaMA 2 - 7B model, using as little code as possible. We will be using the Alpaca Lora Training script, which automates the process of fine-tuning the model and for GPU we will be using Beam.

Implement the code in Llama LoRA repo in a script we can run locally

Hi all - relatively new to GitHub / programming in general, and I wanted to try to set up Alpaca Lora locally. Following the guide here: https://github.com/tloen/alpaca-lora

Follow up the popular work of u/tloen alpaca-lora, I wrapped the setup of alpaca_lora_4bit to add support for GPTQ training in form of installable pip packages. You can perform training and inference with multiple quantizations method to compare the results.

If instead you want to apply a LoRa to a pytorch model, a lot of people use this script to apply to LoRa to the 16 bit model and then quantize it with a GPTQ program afterwards https://github.com/tloen/alpaca-lora/blob/main/export_hf_checkpoint.py

There are a few papers on watermarking LLM output, but from what I have seen they all use complex methods of detection to allow the watermark to go unseen by the end user, only to be detected by algorithm. I believe that a more overt system of watermarking might also be beneficial. One simple method that I have tried is character substitution. For this model, I LORA finetuned openlm-research/open_llama_3b on the alpaca_data_cleaned_archive.json dataset from https://github.com/tloen/alpaca-lora/ modified by replacing all instances of the "." character in the outputs with a "ι" The results are pretty good, with the correct the correct substitutions being generated by the model in most cases. It doesn't always work, but this was only a LORA training and for two epochs of 400 steps each, and 100% substitution isn't really required.

I am kind of new to finetuning LLM's and am not able to understand what this option exactly refers to. I guess it has the same meaning as the "train_on_inputs" parameter of alpacalora though.

Read the paper and also: https://github.com/tloen/alpaca-lora