Creating a chatbot program that can learn as you interact

 



 ¡Hola! 
As we delve deeper into AI and machine learning saga, here is a very cool Python code that could help you create a small Chatbot program, that can 
a. Learn from you as you chat with it
b. Save information, so that when you reopen the program it can remember what it has learned for so long.
c. And it should be pretty fast to respond.
The below code is very basic and could be exercised to include more and more features as you go through it. 
And I used Python as my code; alternatively, you can also write the same using C#, if that's what you are comfortable with.
The algorithm:
I am creating a file called: questionBank.json and saving it as a physical file, and which starts with a couple of very basic questions:



I am chatting with my chatbot like this:


And when I ask it something it doesn't know:

So that when you ask it next time:


Pretty cool, eh? Let me show you, how this has been done.
Step 1: I am using Spyder3.11, as my IDE, but alternatively you can use anything that you're comfortable with: PyCharm, JuPyter, etc. 
Step 2: Open up your working folder location, and create a JSON file, with the name: "questionBank.json" and do close it. You can fill it up with certain dummy questions, but otherwise, you can leave it just blank.
Step 3: Start your code by importing from json:

Step 4: Create the following function that reads from our file, mentioned above and then loads it into a variable called 'data' and returns it (the keyword 'r' implies read):

Step 5: Create the following function that saves the content of the file in the working folder location (the keyword 'w' implies write).

Step 6: Create the following function that gets the input from the user, converting it into lowercase:

Step 7: Finally in the main method we can manipulate/call the above functions like this:
def main():
    data_file = 'qa_data.json'
    try:
        data = get_data(data_file)
    except FileNotFoundError:
        data = {}

    print("Hello and Welcome to the Q&A ChatBot!")

    while True:
        user_input = input("User: ").strip().lower()

        if user_input == 'exit':
            print("Ciao!")
            break

        answer = get_reply(user_input, data)

        if answer:
            print("Bot:", answer)
        else:
            print("Bot: Hey, I'm sorry, I don't know the answer to that question.")
            teach = input("Would you like to teach me?: ").strip().lower()
            if teach == 'yes' or teach== 'sure' or teach == 'why not':
                new_reply = input("What's the answer to that question?: ").strip()
                data[user_input] = new_reply
                save_file(data_file, data)
                print("Bot: Wow! Noted. Will remeber that!")
            else:
                print("Bot: OK, Please ask something else!")

if __name__ == "__main__":
    main()

Look at the code above. It straightforwardly keeps on reading the prompt from the user and looks up for answers from the file, and it then if it doesn't find them, it will save the answer. The user asks a question, it doesn't find any answer, it searches for any answer from the user that is like 'yes' or 'sure', it will ask what's the response to the question and will save it in the file.
So much for now, see you soon with more insights on Machine learning with Python.

Comments

Post a Comment

Popular posts from this blog

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec...
Read more

X++ : mistakes which developers commit the most

Image
   The most important thing is to remember where and when to write the code. a. Developers have an inherent habit of writing erratic select statements: select * from custTable where custTable.AccountNum == <SomeValue> Where in essence we need to make use of optimized choice of fields in the select statement. b. Making use of 'continue' keywords: While select custTrans where <someConditions> { if (cusTTrans.CustGroup != mappingTable.CustGroup) { continue; } } 'Continue' statements are precisely a very unhygienic way of designing your code. The above statement could have been easily ornamented by using exists/not exists joins. Using Continue statements would eventually result in a high performance impact. Also select statements should be made punctuated with a 'firstonly' clause -- just not from best practise standpoint, but also from performance considerations. c. Writing nested loops: This is a common mistake that perha...
Read more

Are you still using macros? Be sure you read this.

Image
  You still use a lot of macros in your code, don't you? Of course you should: Macros, as per Microsoft,  are p recompiler directives are processed before the code is compiled. The directives declare and handle macros and their values. The directives are removed by the precompiler so that the X++ compiler never encounters them. The X++ compiler only sees the sequence of characters written into the X++ code by the directives. However macros, are not quite recomended by Microsoft. They are slow, they can be subsequently deorectaed at any later time.  The Macros are  actually  a type of classes, only that they are not instantiated and not need be defined as classes. Hence runtime garbage collection could be a huge issue, consquently (a class when gets out of scope, gets garbage-collected owing to the destructor classes of DOT net instrumentation classes). Summing up, macrros are a bit old way of writing code. Use static classes instead. public static class MyIdenti...
Read more